device issues with 'hald'

spir denis.spir at
Thu Nov 19 12:49:30 GMT 2009

Seems to half-work now!

After having run "hald --verbose=yes" while answering first response to my initial post, for any reason I tried again "solid-hardware list" which now runs. "lshal" runs, too. (But I can hardly imagine how to find proper info in such massive outputs.)

Cds and sub sticks now more or less (see below) are caught by the GUI, notified in the device notifier and show in Dolphin.
But there are still a few remaining issues.

.0. Why?
Why does it work now, not before my last manips, not yesterday when I did exactly the same things? What has changed, precisely? As long as we cannot answer this, issues can come back seemingly randomly.

.1. External cdrom (via usb) is mounted as /media/floppy1

.2. Cdrom content randomly shown or not
The same issue as before upgrading to kde 4.3.2: in dolphin I need to change folder several times before cd content is shown. If not enough, need to take off and put back the cd physically.

.3. Music cd content not shown at all

.4. Not all memory sticks work fine
I have 2 sticks, one (with important data) does not work at all.

I suspect the source is that the one that is recognised had been once virus-infected when used by a friend, so that I formatted it (ext3). But the not-working one is probably in fat32 (as they are often so formatted by default). So, if I'm right, hal (or any other component in the chain between dmesg and gui) is unable to handle "alien" filesystems.

The one that works not is still seen by dmesg:

[21101.204045] usb 1-6: new high speed USB device using ehci_hcd and address 13
[21101.338734] usb 1-6: configuration #1 chosen from 1 choice
[21101.339105] scsi17 : SCSI emulation for USB Mass Storage devices
[21101.339314] usb-storage: device found at 13
[21101.339318] usb-storage: waiting for device to settle before scanning
[21106.336304] usb-storage: device scan complete
[21106.337020] scsi 17:0:0:0: Direct-Access     JetFlash Transcend 4GB    8.07 PQ: 0 ANSI: 2
[21106.337810] sd 17:0:0:0: Attached scsi generic sg3 type 0
[21106.370686] sd 17:0:0:0: [sdb] 7843840 512-byte logical blocks: (4.01 GB/3.74 GiB)
[21106.372316] sd 17:0:0:0: [sdb] Write Protect is off
[21106.372322] sd 17:0:0:0: [sdb] Mode Sense: 03 00 00 00
[21106.372325] sd 17:0:0:0: [sdb] Assuming drive cache: write through
[21106.394619] sd 17:0:0:0: [sdb] Assuming drive cache: write through
[21106.394627]  sdb: unknown partition table
[21106.947324] sd 17:0:0:0: [sdb] Assuming drive cache: write through
[21106.947337] sd 17:0:0:0: [sdb] Attached SCSI removable disk

The line saying "unknown partition table" may be a key hint. But why did it work before updating?


This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list