LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   udev 064 still problematic (https://www.linuxquestions.org/questions/slackware-14/udev-064-still-problematic-347041/)

xushi 07-26-2005 03:46 PM
udev 064 still problematic
 
Contrary to what pat said in his recent changelog
Quote:
a/udev-064-i486-1.tgz: Upgraded to udev-064. With the help of two new
lines in udev.rules, and a symlink added in /etc/hotplug.d/default that
used to be added by earlier versions of hotplug, udev-064 appears to be
working! Thanks to Piter Punk for the rules and Kris Karas for the link.
Udev 064 doesn't like my usb devices anymore. I can mount my iriver and SD cards, and they get registered,

Code:
  Vendor: GENERIC  Model: USB Storage-CFC  Rev: 010D
  Type:  Direct-Access                      ANSI SCSI revision: 00
Attached scsi removable disk sdb at scsi6, channel 0, id 0, lun 0
  Vendor: GENERIC  Model: USB Storage-MMC  Rev: 010D
  Type:  Direct-Access                      ANSI SCSI revision: 00
SCSI device sdc: 62720 512-byte hdwr sectors (32 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 00 00 00
sdc: assuming drive cache: write through
SCSI device sdc: 62720 512-byte hdwr sectors (32 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 00 00 00
sdc: assuming drive cache: write through
 /dev/scsi/host6/bus0/target0/lun1: p1
Attached scsi removable disk sdc at scsi6, channel 0, id 0, lun 1
  Vendor: GENERIC  Model: USB Storage-MSC  Rev: 010D
  Type:  Direct-Access                      ANSI SCSI revision: 00
Attached scsi removable disk sdd at scsi6, channel 0, id 0, lun 2
usb-storage: device scan complete
And
Code:
usb-storage: waiting for device to settle before scanning
  Vendor: TOSHIBA  Model: MK4004GAH        Rev: JC00
  Type:  Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 78126048 512-byte hdwr sectors (40001 MB)
sda: assuming drive cache: write through
SCSI device sda: 78126048 512-byte hdwr sectors (40001 MB)
sda: assuming drive cache: write through
 /dev/scsi/host7/bus0/target0/lun0: p1
Attached scsi disk sda at scsi7, channel 0, id 0, lun 0
usb-storage: device scan complete
But when trying to mount,
Code:
mount: special device /dev/sda1 does not exist
And indeed,
Code:
:/dev# ls /dev
adsp@    hda      mem        ram2@    tty0@  tty26@  tty43@  tty60@  vcsa1@
agpgart@  hda1      misc/      ram3@    tty1@  tty27@  tty44@  tty61@  vcsa2@
audio@    hda2      mixer@    ram4@    tty10@  tty28@  tty45@  tty62@  vcsa3@
cdrom@    hda3      null      ram5@    tty11@  tty29@  tty46@  tty63@  vcsa4@
cdrom0@  hdc      nvidia0    ram6@    tty12@  tty3@  tty47@  tty7@    vcsa5@
console  initctl|  nvidia1    ram7@    tty13@  tty30@  tty48@  tty8@    vcsa6@
core@    input/    nvidiactl  ram8@    tty14@  tty31@  tty49@  tty9@    vcsa7@
cpu/      kmem      port      ram9@    tty15@  tty32@  tty5@  urandom  vmmon
dsp@      kmsg      ppp        random  tty16@  tty33@  tty50@  vc/      vmnet0
dvd@      log=      ptmx      raw/    tty17@  tty34@  tty51@  vcc/    vmnet1
dvd0@    loop/    pts/      rd/      tty18@  tty35@  tty52@  vcs@    vmnet2
fb/      loop0@    ram0@      rtc@    tty19@  tty36@  tty53@  vcs1@    vmnet3
fb0@      loop1@    ram1@      shm/    tty2@  tty37@  tty54@  vcs2@    vmnet4
fd@      loop2@    ram10@    snd/    tty20@  tty38@  tty55@  vcs3@    vmnet5
fd0      loop3@    ram11@    sound/  tty21@  tty39@  tty56@  vcs4@    vmnet6
fd1      loop4@    ram12@    stderr@  tty22@  tty4@  tty57@  vcs5@    vmnet7
fd2      loop5@    ram13@    stdin@  tty23@  tty40@  tty58@  vcs6@    vmnet8
fd3      loop6@    ram14@    stdout@  tty24@  tty41@  tty59@  vcs7@    vmnet9
full      loop7@    ram15@    tty      tty25@  tty42@  tty6@  vcsa@    zero
Haven't tried burning a cd yet.. So take care when upgrading.

Nille_kungen 07-26-2005 05:18 PM
Well this are the things we have to live with if we use current.
But thanks for the warning.

xushi 07-27-2005 05:55 AM
Hmm, my apologies, but i'm not sure if i rebooted my machine after updating udev or not..

Now after updating again, all my usb devices work.. So i can confirm that to me, udev 064 works well, and its safe enough for others to try.

On a side note, i'm on 2.6.12.3

satinet 07-27-2005 06:16 AM
We've all been there!

On a udev note. My devices are created as /dev/sda1-2-3 etc. Fine.

But in KDE i want this to show as a pen drive rather than a disk drive (i'm selecting show mounted and unmounted devices on my desktop). Is there a way to make KDE feel this is a usb stick icon rather than a disk drive (with the disk drive icon).

hardly a killer, but i'm just being harsh with my slackware install at the moment. want it 100% nice.

thanks

keefaz 07-27-2005 08:41 AM
How does KDE do the distinction between a pen drive and a disk drive ?
Does it recognize custom udev rules or do you tell about ide disk vs usb ?

satinet 07-27-2005 10:39 AM
Hmm, yes.

I'm really not sure, so that's why i posted. I'm presuming it recognises it from it's naming convention in udev. namely sda1 which i guess is in fact a SCSI disk.

But i would love to be corrected. Anyone know how KDE does this? and why usb devices have to be like SCSI devices in the latest kernel?

Thanks

Nille_kungen 07-27-2005 02:14 PM
Hmm that i don't know but maybe it uses the same as proc like
cat /proc/ide/hdc/media
cdrom
On my system.
But i actually got no idea how KDE does it.


All times are GMT -5. The time now is 11:35 AM.