7:56 a.m.
Hi,
I have two types of USB card reader. One is an internal 7 in 1 job and
the other is an external 8 in 1 (on the laptop). Both are recognised by
hal when I run hal-device-manager, yet neither will read any cards I put
into them.
I'm using kernel 2.6.11-1.1275_FC4 on both machines with hal 0.5.1-1.
Do I need to report this as a kernel or hal bug into bugzilla?
USB printing is fine.
TTFN
Paul
--
"In an urban society, everything connects. Each person's needs are fed
by the skills of many others. Our lives are woven together in a fabric.
But the connections that make society strong also make it vulnerable." -
Threads, BBC-TV 1984
10:49 a.m.
On Sun, 2005-05-01 at 13:56 +0100, Paul wrote:
Hi,
I have two types of USB card reader. One is an internal 7 in 1 job and
the other is an external 8 in 1 (on the laptop). Both are recognised by
hal when I run hal-device-manager, yet neither will read any cards I put
into them.
I'm using kernel 2.6.11-1.1275_FC4 on both machines with hal 0.5.1-1.
Do I need to report this as a kernel or hal bug into bugzilla?
It's most probably this one
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=156167
David
5:24 p.m.
On 5/1/05, Paul <paul(a)all-the-johnsons.co.uk> wrote:
Hi,
I have two types of USB card reader. One is an internal 7 in 1 job and
the other is an external 8 in 1 (on the laptop). Both are recognised by
hal when I run hal-device-manager, yet neither will read any cards I put
into them.
Do you have selinux in enforcing mode? Are you seeing avc errors
related to hal being generated in /var/log/messages when plugging in
that external reader or when inserting media into that external
reader? There was a recent issue identified with selinux targetted
policy that was keeping hal from operating correctly.
-jef
6:54 p.m.
Hi,
Do you have selinux in enforcing mode?
Targetted. Had too many problems in the past with enforcing mode.
Are you seeing avc errors
related to hal being generated in /var/log/messages when plugging in
that external reader or when inserting media into that external
reader?
/var/log/messages is showing absolutely nothing on this machine
(internal USB card reader) and the external card reader is showing this
(snipped a bit)
May 2 00:47:12 T8 kernel: usb 1-2: new high speed USB device using
ehci_hcd and address 4
May 2 00:47:12 T8 kernel: scsi2 : SCSI emulation for USB Mass Storage
devices
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: SCSI device sda: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sda: Write Protect is off
May 2 00:47:17 T8 kernel: sda: assuming drive cache: write through
May 2 00:47:17 T8 kernel: SCSI device sda: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sda: Write Protect is off
May 2 00:47:17 T8 kernel: sda: assuming drive cache: write through
May 2 00:47:17 T8 kernel: sda:
May 2 00:47:17 T8 kernel: Attached scsi removable disk sda at scsi2,
channel 0, id 0, lun 0
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: Attached scsi removable disk sdb at scsi2,
channel 0, id 0, lun 1
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: SCSI device sdc: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sdc: Write Protect is off
May 2 00:47:17 T8 kernel: sdc: assuming drive cache: write through
May 2 00:47:17 T8 kernel: SCSI device sdc: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sdc: Write Protect is off
May 2 00:47:17 T8 kernel: sdc: assuming drive cache: write through
May 2 00:47:17 T8 kernel: sdc:
May 2 00:47:17 T8 kernel: Attached scsi removable disk sdc at scsi2,
channel 0, id 0, lun 2
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: Attached scsi removable disk sdd at scsi2,
channel 0, id 0, lun 3
May 2 00:47:18 T8 scsi.agent[12366]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0
May 2 00:47:18 T8 scsi.agent[12369]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:1
May 2 00:47:18 T8 scsi.agent[12372]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:2
May 2 00:47:18 T8 scsi.agent[12375]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:3
May 2 00:47:19 T8 kernel: audit(1114991239.933:0): avc: denied
{ connectto } for pid=12437
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.938:0): avc: denied
{ connectto } for pid=12438
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.944:0): avc: denied
{ connectto } for pid=12439
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.949:0): avc: denied
{ connectto } for pid=12440
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:43 T8 su(pam_unix)[12467]: session opened for user root by
paul(uid=500)
There was a recent issue identified with selinux targetted
policy that was keeping hal from operating correctly.
Not sure what's going on here, though it does look like it could be the
problem with the FC4 blocker on...
TTFN
Paul
--
"In an urban society, everything connects. Each person's needs are fed
by the skills of many others. Our lives are woven together in a fabric.
But the connections that make society strong also make it vulnerable." -
Threads, BBC-TV 1984
4:11 a.m.
On Mon, 2005-05-02 at 00:54 +0100, Paul wrote:
Hi,
> Do you have selinux in enforcing mode?
Targetted. Had too many problems in the past with enforcing mode.
> Are you seeing avc errors
> related to hal being generated in /var/log/messages when plugging in
> that external reader or when inserting media into that external
> reader?
/var/log/messages is showing absolutely nothing on this machine
(internal USB card reader) and the external card reader is showing this
(snipped a bit)
May 2 00:47:12 T8 kernel: usb 1-2: new high speed USB device using
ehci_hcd and address 4
May 2 00:47:12 T8 kernel: scsi2 : SCSI emulation for USB Mass Storage
devices
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: SCSI device sda: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sda: Write Protect is off
May 2 00:47:17 T8 kernel: sda: assuming drive cache: write through
May 2 00:47:17 T8 kernel: SCSI device sda: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sda: Write Protect is off
May 2 00:47:17 T8 kernel: sda: assuming drive cache: write through
May 2 00:47:17 T8 kernel: sda:
May 2 00:47:17 T8 kernel: Attached scsi removable disk sda at scsi2,
channel 0, id 0, lun 0
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: Attached scsi removable disk sdb at scsi2,
channel 0, id 0, lun 1
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: SCSI device sdc: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sdc: Write Protect is off
May 2 00:47:17 T8 kernel: sdc: assuming drive cache: write through
May 2 00:47:17 T8 kernel: SCSI device sdc: 246016 512-byte hdwr sectors
(126 MB)
May 2 00:47:17 T8 kernel: sdc: Write Protect is off
May 2 00:47:17 T8 kernel: sdc: assuming drive cache: write through
May 2 00:47:17 T8 kernel: sdc:
May 2 00:47:17 T8 kernel: Attached scsi removable disk sdc at scsi2,
channel 0, id 0, lun 2
May 2 00:47:17 T8 kernel: Vendor: Generic Model: STORAGE DEVICE
Rev: 0125
May 2 00:47:17 T8 kernel: Type: Direct-Access
ANSI SCSI revision: 00
May 2 00:47:17 T8 kernel: Attached scsi removable disk sdd at scsi2,
channel 0, id 0, lun 3
May 2 00:47:18 T8 scsi.agent[12366]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:0
May 2 00:47:18 T8 scsi.agent[12369]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:1
May 2 00:47:18 T8 scsi.agent[12372]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:2
May 2 00:47:18 T8 scsi.agent[12375]: disk
at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/host2/target2:0:0/2:0:0:3
May 2 00:47:19 T8 kernel: audit(1114991239.933:0): avc: denied
{ connectto } for pid=12437
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.938:0): avc: denied
{ connectto } for pid=12438
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.944:0): avc: denied
{ connectto } for pid=12439
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.949:0): avc: denied
{ connectto } for pid=12440
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:43 T8 su(pam_unix)[12467]: session opened for user root by
paul(uid=500)
> There was a recent issue identified with selinux targetted
> policy that was keeping hal from operating correctly.
Not sure what's going on here, though it does look like it could be the
problem with the FC4 blocker on...
I was having USB problems as well which I eventually tracked down to HAL
failing to start. The reason that HAL was failing was SELinux. I am
now running:
selinux-policy-targeted-1.23.13-4
hal-0.5.1-1
kernel-smp-2.6.11-1.1226_FC4
and USB seems to be working.
Keith.
7:15 a.m.
On 5/1/05, Paul <paul(a)all-the-johnsons.co.uk> wrote:
Hi,
> Do you have selinux in enforcing mode?
Targetted. Had too many problems in the past with enforcing mode.
I think you are confused. Trargetted/Strict can be set to enforcing
or permissive.
So targetted is enabled but is it set to enforcing or permissive?
check /etc/sysconfig/selinux
And you are definitely getting selinux related messages about hal. Go
back at take a look
at your log again... those avc messages, which were similar to what I
was seeing. As soon as I put selinux in permissive mode, hal started
working again. I'm expecting to see a selinux targetted policy update
package to correct the problem.
-jef
Here is the bit in your log concerning selinux and hal interaction.
May 2 00:47:19 T8 kernel: audit(1114991239.938:0): avc: denied
{ connectto } for pid=12438
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.944:0): avc: denied
{ connectto } for pid=12439
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
May 2 00:47:19 T8 kernel: audit(1114991239.949:0): avc: denied
{ connectto } for pid=12440
exe=/usr/libexec/hald-probe-storagepath=@
/tmp/hald-local/dbus-CBHQFkOJaq
scontext=system_u:system_r:hald_t tcontext=system_u:system_r:hald_t
tclass=unix_stream_socket
2:36 p.m.
søn, 01.05.2005 kl. 14.56 skrev Paul:
Hi,
I have two types of USB card reader. One is an internal 7 in 1 job and
the other is an external 8 in 1 (on the laptop). Both are recognised by
hal when I run hal-device-manager, yet neither will read any cards I put
into them.
I'm using kernel 2.6.11-1.1275_FC4 on both machines with hal 0.5.1-1.
Do I need to report this as a kernel or hal bug into bugzilla?
USB printing is fine.
TTFN
Paul
I have experienced having to plug in the cardreader (or unplug/plug)
*after* inserting card, or else nothing happens.
Pretty hard to do on an internal one, though...
Kyrre
6934
days inactive
6935
days old
6 comments
5 participants
participants (5)
-
David Zeuthen -
Jef Spaleta -
Keith Sharp -
Kyrre Ness Sjobak -
Paul F. Johnson