Bug 84522 - There are no hard disk icons inside "My Computer"
Summary: There are no hard disk icons inside "My Computer"
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Final
Hardware: Other All
: P5 - None : Normal
Target Milestone: ---
Assignee: Kay Sievers
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-18 20:45 UTC by Filippos Papadopoulos
Modified: 2006-02-08 19:11 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
lshal output (41.28 KB, text/plain)
2005-10-09 13:36 UTC, Filippos Papadopoulos
Details
HAL log (265.01 KB, text/plain)
2005-10-11 22:41 UTC, Filippos Papadopoulos
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Filippos Papadopoulos 2005-05-18 20:45:03 UTC
I have 2 windows partitions (one NTFS and one FAT) and 3 Linux ones (REISER 
for /, swap, and ext2 for /boot ) . Some of them are created inside an extended 
one. My hard disk is SCSI. 
Inside "My Computer" (hmm i have seen that name again somewhere...) there is no 
icon for the hard disk. This happens in KDE. 
 
On the other hand in GNOME (Computer icon) there appear icons for the windows 
partions (C: and D: ) and for the / partition, which is normal. 
 
So, there must a problem in KDE (SuSE watcher/plugger ?)
Comment 1 Dirk Mueller 2005-09-07 07:47:10 UTC
works for me with beta4 
Comment 2 Filippos Papadopoulos 2005-10-08 23:56:38 UTC
Well today i have installed SUSE 10.0 (boxed version) and the same thing 
happens. Note that this bug happens only in my PC with the SCSI disk. My other 
PC (IDE disk) and my laptop dont suffer from this bug... 
Comment 3 Stephan Kulow 2005-10-09 08:36:20 UTC
Can you attach the output of lshal here? 
Comment 4 Filippos Papadopoulos 2005-10-09 13:36:41 UTC
Created attachment 52042 [details]
lshal output
Comment 5 Stephan Kulow 2005-10-09 14:10:40 UTC
there is no disk in that. So it's a hotplug bug 
Comment 6 Danny Al-Gaaf 2005-10-11 15:13:15 UTC
I can't reproduce this here. HAL should know all scsi disks. Please do this:

- stop hal with 'rchal stop'
- hald --retain-privileges --daemon=no --verbose=yes > /tmp/log_hal 2>&1
- wait 20 seconds
- stop hal (with Crtl + c)
- attach the generated file /tmp/log_hal to this bugreport
Comment 7 Filippos Papadopoulos 2005-10-11 22:41:21 UTC
Created attachment 53793 [details]
HAL log
Comment 8 Danny Al-Gaaf 2005-10-12 09:43:02 UTC
There are many messages about missing parent device in the hotplug event:

01:35:15.681 [I] blockdev.c:547: block_add: sysfs_path=/sys/block/sda dev=/dev/
sda is_part=0, parent=0x00000000
01:35:15.681 [I] blockdev.c:458: get_luks_uuid: device_file=/dev/sda
01:35:15.681 [I] blockdev.c:589: Ignoring hotplug event - no parent
01:35:15.681 [I] blockdev.c:547: block_add: sysfs_path=/sys/block/sda/sda6 dev=/
dev/sda6 is_part=1, parent=0x00000000
01:35:15.681 [I] blockdev.c:458: get_luks_uuid: device_file=/dev/sda6
01:35:15.681 [I] blockdev.c:589: Ignoring hotplug event - no parent

Maybe a udev problem? 

@hare: could you take a look at the bug/problem?
Comment 9 Hannes Reinecke 2005-10-17 10:25:16 UTC
No, I think it's more a HAL problem. Anyway, Kay will know.
Comment 10 Kay Sievers 2005-10-17 10:46:46 UTC
What does:
  ls -l /sys/block/sda
and:
  find /sys/block
print?
Comment 11 Filippos Papadopoulos 2005-10-17 20:36:40 UTC
> ls -l /sys/block/sda

-r--r--r--  1 root root 4096 2005-10-17 23:35 dev
lrwxrwxrwx  1 root root    0 2005-10-17 23:35 device -> ../../devices/platform/host0/target0:0:6/0:0:6:0
drwxr-xr-x  3 root root    0 2005-10-18 02:20 queue
-r--r--r--  1 root root 4096 2005-10-17 23:35 range
-r--r--r--  1 root root 4096 2005-10-17 23:35 removable
drwxr-xr-x  2 root root    0 2005-10-17 23:20 sda1
drwxr-xr-x  2 root root    0 2005-10-17 23:20 sda2
drwxr-xr-x  2 root root    0 2005-10-17 23:20 sda3
drwxr-xr-x  2 root root    0 2005-10-17 23:20 sda4
drwxr-xr-x  2 root root    0 2005-10-17 23:20 sda5
drwxr-xr-x  2 root root    0 2005-10-17 23:20 sda6
-r--r--r--  1 root root 4096 2005-10-17 23:35 size
-r--r--r--  1 root root 4096 2005-10-17 23:35 stat




> find /sys/block

/sys/block
/sys/block/md0
/sys/block/md0/stat
/sys/block/md0/size
/sys/block/md0/removable
/sys/block/md0/range
/sys/block/md0/dev
/sys/block/hdc
/sys/block/hdc/queue
/sys/block/hdc/queue/iosched
/sys/block/hdc/queue/iosched/max_depth
/sys/block/hdc/queue/iosched/slice_idle
/sys/block/hdc/queue/iosched/slice_async_rq
/sys/block/hdc/queue/iosched/slice_async
/sys/block/hdc/queue/iosched/slice_sync
/sys/block/hdc/queue/iosched/back_seek_penalty
/sys/block/hdc/queue/iosched/back_seek_max
/sys/block/hdc/queue/iosched/fifo_expire_async
/sys/block/hdc/queue/iosched/fifo_expire_sync
/sys/block/hdc/queue/iosched/queued
/sys/block/hdc/queue/iosched/quantum
/sys/block/hdc/queue/scheduler
/sys/block/hdc/queue/max_sectors_kb
/sys/block/hdc/queue/max_hw_sectors_kb
/sys/block/hdc/queue/read_ahead_kb
/sys/block/hdc/queue/nr_requests
/sys/block/hdc/device
/sys/block/hdc/stat
/sys/block/hdc/size
/sys/block/hdc/removable
/sys/block/hdc/range
/sys/block/hdc/dev
/sys/block/hdb
/sys/block/hdb/queue
/sys/block/hdb/queue/iosched
/sys/block/hdb/queue/iosched/max_depth
/sys/block/hdb/queue/iosched/slice_idle
/sys/block/hdb/queue/iosched/slice_async_rq
/sys/block/hdb/queue/iosched/slice_async
/sys/block/hdb/queue/iosched/slice_sync
/sys/block/hdb/queue/iosched/back_seek_penalty
/sys/block/hdb/queue/iosched/back_seek_max
/sys/block/hdb/queue/iosched/fifo_expire_async
/sys/block/hdb/queue/iosched/fifo_expire_sync
/sys/block/hdb/queue/iosched/queued
/sys/block/hdb/queue/iosched/quantum
/sys/block/hdb/queue/scheduler
/sys/block/hdb/queue/max_sectors_kb
/sys/block/hdb/queue/max_hw_sectors_kb
/sys/block/hdb/queue/read_ahead_kb
/sys/block/hdb/queue/nr_requests
/sys/block/hdb/device
/sys/block/hdb/stat
/sys/block/hdb/size
/sys/block/hdb/removable
/sys/block/hdb/range
/sys/block/hdb/dev
/sys/block/sda
/sys/block/sda/queue
/sys/block/sda/queue/iosched
/sys/block/sda/queue/iosched/max_depth
/sys/block/sda/queue/iosched/slice_idle
/sys/block/sda/queue/iosched/slice_async_rq
/sys/block/sda/queue/iosched/slice_async
/sys/block/sda/queue/iosched/slice_sync
/sys/block/sda/queue/iosched/back_seek_penalty
/sys/block/sda/queue/iosched/back_seek_max
/sys/block/sda/queue/iosched/fifo_expire_async
/sys/block/sda/queue/iosched/fifo_expire_sync
/sys/block/sda/queue/iosched/queued
/sys/block/sda/queue/iosched/quantum
/sys/block/sda/queue/scheduler
/sys/block/sda/queue/max_sectors_kb
/sys/block/sda/queue/max_hw_sectors_kb
/sys/block/sda/queue/read_ahead_kb
/sys/block/sda/queue/nr_requests
/sys/block/sda/sda6
/sys/block/sda/sda6/stat
/sys/block/sda/sda6/size
/sys/block/sda/sda6/start
/sys/block/sda/sda6/dev
/sys/block/sda/sda5
/sys/block/sda/sda5/stat
/sys/block/sda/sda5/size
/sys/block/sda/sda5/start
/sys/block/sda/sda5/dev
/sys/block/sda/sda4
/sys/block/sda/sda4/stat
/sys/block/sda/sda4/size
/sys/block/sda/sda4/start
/sys/block/sda/sda4/dev
/sys/block/sda/sda3
/sys/block/sda/sda3/stat
/sys/block/sda/sda3/size
/sys/block/sda/sda3/start
/sys/block/sda/sda3/dev
/sys/block/sda/sda2
/sys/block/sda/sda2/stat
/sys/block/sda/sda2/size
/sys/block/sda/sda2/start
/sys/block/sda/sda2/dev
/sys/block/sda/sda1
/sys/block/sda/sda1/stat
/sys/block/sda/sda1/size
/sys/block/sda/sda1/start
/sys/block/sda/sda1/dev
/sys/block/sda/device
/sys/block/sda/stat
/sys/block/sda/size
/sys/block/sda/removable
/sys/block/sda/range
/sys/block/sda/dev
/sys/block/loop7
/sys/block/loop7/stat
/sys/block/loop7/size
/sys/block/loop7/removable
/sys/block/loop7/range
/sys/block/loop7/dev
/sys/block/loop6
/sys/block/loop6/stat
/sys/block/loop6/size
/sys/block/loop6/removable
/sys/block/loop6/range
/sys/block/loop6/dev
/sys/block/loop5
/sys/block/loop5/stat
/sys/block/loop5/size
/sys/block/loop5/removable
/sys/block/loop5/range
/sys/block/loop5/dev
/sys/block/loop4
/sys/block/loop4/stat
/sys/block/loop4/size
/sys/block/loop4/removable
/sys/block/loop4/range
/sys/block/loop4/dev
/sys/block/loop3
/sys/block/loop3/stat
/sys/block/loop3/size
/sys/block/loop3/removable
/sys/block/loop3/range
/sys/block/loop3/dev
/sys/block/loop2
/sys/block/loop2/stat
/sys/block/loop2/size
/sys/block/loop2/removable
/sys/block/loop2/range
/sys/block/loop2/dev
/sys/block/loop1
/sys/block/loop1/stat
/sys/block/loop1/size
/sys/block/loop1/removable
/sys/block/loop1/range
/sys/block/loop1/dev
/sys/block/loop0
/sys/block/loop0/stat
/sys/block/loop0/size
/sys/block/loop0/removable
/sys/block/loop0/range
/sys/block/loop0/dev
/sys/block/ram15
/sys/block/ram15/stat
/sys/block/ram15/size
/sys/block/ram15/removable
/sys/block/ram15/range
/sys/block/ram15/dev
/sys/block/ram14
/sys/block/ram14/stat
/sys/block/ram14/size
/sys/block/ram14/removable
/sys/block/ram14/range
/sys/block/ram14/dev
/sys/block/ram13
/sys/block/ram13/stat
/sys/block/ram13/size
/sys/block/ram13/removable
/sys/block/ram13/range
/sys/block/ram13/dev
/sys/block/ram12
/sys/block/ram12/stat
/sys/block/ram12/size
/sys/block/ram12/removable
/sys/block/ram12/range
/sys/block/ram12/dev
/sys/block/ram11
/sys/block/ram11/stat
/sys/block/ram11/size
/sys/block/ram11/removable
/sys/block/ram11/range
/sys/block/ram11/dev
/sys/block/ram10
/sys/block/ram10/stat
/sys/block/ram10/size
/sys/block/ram10/removable
/sys/block/ram10/range
/sys/block/ram10/dev
/sys/block/ram9
/sys/block/ram9/stat
/sys/block/ram9/size
/sys/block/ram9/removable
/sys/block/ram9/range
/sys/block/ram9/dev
/sys/block/ram8
/sys/block/ram8/stat
/sys/block/ram8/size
/sys/block/ram8/removable
/sys/block/ram8/range
/sys/block/ram8/dev
/sys/block/ram7
/sys/block/ram7/stat
/sys/block/ram7/size
/sys/block/ram7/removable
/sys/block/ram7/range
/sys/block/ram7/dev
/sys/block/ram6
/sys/block/ram6/stat
/sys/block/ram6/size
/sys/block/ram6/removable
/sys/block/ram6/range
/sys/block/ram6/dev
/sys/block/ram5
/sys/block/ram5/stat
/sys/block/ram5/size
/sys/block/ram5/removable
/sys/block/ram5/range
/sys/block/ram5/dev
/sys/block/ram4
/sys/block/ram4/stat
/sys/block/ram4/size
/sys/block/ram4/removable
/sys/block/ram4/range
/sys/block/ram4/dev
/sys/block/ram3
/sys/block/ram3/stat
/sys/block/ram3/size
/sys/block/ram3/removable
/sys/block/ram3/range
/sys/block/ram3/dev
/sys/block/ram2
/sys/block/ram2/stat
/sys/block/ram2/size
/sys/block/ram2/removable
/sys/block/ram2/range
/sys/block/ram2/dev
/sys/block/ram1
/sys/block/ram1/stat
/sys/block/ram1/size
/sys/block/ram1/removable
/sys/block/ram1/range
/sys/block/ram1/dev
/sys/block/ram0
/sys/block/ram0/stat
/sys/block/ram0/size
/sys/block/ram0/removable
/sys/block/ram0/range
/sys/block/ram0/dev
/sys/block/fd0
/sys/block/fd0/queue
/sys/block/fd0/queue/iosched
/sys/block/fd0/queue/iosched/max_depth
/sys/block/fd0/queue/iosched/slice_idle
/sys/block/fd0/queue/iosched/slice_async_rq
/sys/block/fd0/queue/iosched/slice_async
/sys/block/fd0/queue/iosched/slice_sync
/sys/block/fd0/queue/iosched/back_seek_penalty
/sys/block/fd0/queue/iosched/back_seek_max
/sys/block/fd0/queue/iosched/fifo_expire_async
/sys/block/fd0/queue/iosched/fifo_expire_sync
/sys/block/fd0/queue/iosched/queued
/sys/block/fd0/queue/iosched/quantum
/sys/block/fd0/queue/scheduler
/sys/block/fd0/queue/max_sectors_kb
/sys/block/fd0/queue/max_hw_sectors_kb
/sys/block/fd0/queue/read_ahead_kb
/sys/block/fd0/queue/nr_requests
/sys/block/fd0/device
/sys/block/fd0/stat
/sys/block/fd0/size
/sys/block/fd0/removable
/sys/block/fd0/range
/sys/block/fd0/dev

Comment 12 Kay Sievers 2005-10-21 12:15:28 UTC
No idea how to dig into it without access to the box. May be kernel
sysfs problem with the scsi driver, not sure. What kind of scsi controller
is in this box?
Comment 13 Filippos Papadopoulos 2005-10-21 12:37:27 UTC
My controller is Initio-9100UW.
See also
https://bugzilla.novell.com/show_bug.cgi?id=84136
Comment 14 Kay Sievers 2005-10-21 13:04:06 UTC
What's the output of:
  udevinfo -a -p /block/sda
Comment 15 Filippos Papadopoulos 2005-10-21 19:31:38 UTC
udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

device '/sys/block/sda' has major:minor 8:0
  looking at class device '/sys/block/sda':
    KERNEL=="sda"
    SUBSYSTEM=="block"
    SYSFS{dev}=="8:0"
    SYSFS{range}=="16"
    SYSFS{removable}=="0"
    SYSFS{size}=="71687340"
    SYSFS{stat}=="   20113    23336  1075586   757560    14439    29489   351476  2298432        0   131024  3057156"

follow the "device"-link to the physical device:
  looking at the device chain at '/sys/devices/platform/host0/target0:0:6/0:0:6:0':
    BUS=="scsi"
    ID=="0:0:6:0"
    DRIVER=="sd"
    SYSFS{device_blocked}=="0"
    SYSFS{iocounterbits}=="32"
    SYSFS{iodone_cnt}=="0x8708"
    SYSFS{ioerr_cnt}=="0x1"
    SYSFS{iorequest_cnt}=="0x8708"
    SYSFS{model}=="IC35L036UWD210-0"
    SYSFS{queue_depth}=="1"
    SYSFS{queue_type}=="none"
    SYSFS{rev}=="S5BS"
    SYSFS{scsi_level}=="4"
    SYSFS{state}=="running"
    SYSFS{timeout}=="30"
    SYSFS{type}=="0"
    SYSFS{vendor}=="IBM     "

  looking at the device chain at '/sys/devices/platform/host0/target0:0:6':
    BUS==""
    ID=="target0:0:6"
    DRIVER=="unknown"

  looking at the device chain at '/sys/devices/platform/host0':
    BUS==""
    ID=="host0"
    DRIVER=="unknown"

  looking at the device chain at '/sys/devices/platform':
    BUS==""
    ID=="platform"
    DRIVER=="unknown"

Comment 16 Forgotten User zhFaldehF_ 2005-12-24 17:37:46 UTC
Right click the "My Computer" icon, and go to properties:

Make sure in KDE it is set to media:/ (under URL) and in Gnome it is set to device:/

If you do not switch KDM to your primary manager, this will happen. 
Comment 17 Kay Sievers 2006-02-08 19:11:02 UTC
Sorry no idea how to debug this remotely. Closing the bug.