View previous topic :: View next topic |
Author |
Message |
skerb1 n00b
Joined: 14 Dec 2004 Posts: 24
|
Posted: Fri Jul 01, 2005 2:36 pm Post subject: Strange Device |
|
|
Hi All,
I just recently noticed a strange sda device on my system (there are no disk devices attatched other than my 2 hard drives hda and hdb).
I am using udev and kernel 2.6.12.2
Does anyone have an idea what this device is?
Code: |
# ls -al /dev/sda
brw-rw---- 1 root disk 8, 0 Jul 1 00:07 /dev/sda
|
Code: |
#dmesg
<snip>
input: AT Translated Set 2 keyboard on isa0060/serio0
input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:11.2-2.2
Adding 522104k swap on /dev/hda4. Priority:-1 extents:1
EXT3 FS on hda2, internal journal
Vendor: Model: Rev:
Type: Direct-Access ANSI SCSI revision: 00
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
usb-storage: device scan complete
nvidia: module license 'NVIDIA' taints kernel.
<snip>
|
Code: |
# udevinfo -a -p /block/sda
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':
SUBSYSTEM="block"
SYSFS{dev}="8:0"
SYSFS{range}="16"
SYSFS{removable}="1"
SYSFS{size}="0"
SYSFS{stat}=" 0 0 0 0 0 0 0 0 0 0 0"
follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:11.2/usb1/1-1/1-1:1.0/host0/target0:0:0/0:0:0:0':
BUS="scsi"
ID="0:0:0:0"
DRIVER="sd"
SYSFS{device_blocked}="0"
SYSFS{iocounterbits}="32"
SYSFS{iodone_cnt}="0x14"
SYSFS{ioerr_cnt}="0x13"
SYSFS{iorequest_cnt}="0x14"
SYSFS{max_sectors}="240"
SYSFS{model}=".2"
SYSFS{queue_depth}="1"
SYSFS{queue_type}="none"
SYSFS{rev}="0-00"
SYSFS{scsi_level}="3"
SYSFS{state}="running"
SYSFS{timeout}="30"
SYSFS{type}="0"
SYSFS{vendor}="linux.so"
|
Code: |
# lsmod
Module Size Used by
snd_seq_midi 6688 0
snd_emu10k1_synth 6720 0
snd_emux_synth 33920 1 snd_emu10k1_synth
snd_seq_virmidi 5760 1 snd_emux_synth
snd_seq_midi_emul 6592 1 snd_emux_synth
snd_pcm_oss 47072 0
snd_mixer_oss 16832 1 snd_pcm_oss
snd_seq_oss 31360 0
snd_seq_midi_event 6144 3 snd_seq_midi,snd_seq_virmidi,snd_seq_oss
snd_seq 47376 8 snd_seq_midi,snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_oss,snd_seq_midi_event
snd_emu10k1 109572 2 snd_emu10k1_synth
snd_rawmidi 19744 3 snd_seq_midi,snd_seq_virmidi,snd_emu10k1
snd_seq_device 6988 7 snd_seq_midi,snd_emu10k1_synth,snd_emux_synth,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
snd_ac97_codec 78264 1 snd_emu10k1
snd_pcm 79688 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer 20036 3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc 7620 2 snd_emu10k1,snd_pcm
snd_util_mem 3328 2 snd_emux_synth,snd_emu10k1
snd_hwdep 7008 2 snd_emux_synth,snd_emu10k1
snd 44516 15 snd_emux_synth,snd_seq_virmidi,snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
soundcore 7136 1 snd
asb100 22228 0
i2c_viapro 6608 0
i2c_sensor 2944 1 asb100
nvidia 3705284 12
|
|
|
Back to top |
|
|
Sorcerer'sApprentice Tux's lil' helper
Joined: 15 Jan 2005 Posts: 121 Location: Jesus College, Cambridge, England
|
Posted: Fri Jul 01, 2005 2:49 pm Post subject: |
|
|
All USB flash drives/external hard disks and any card readers (eg. Compact Flash) will appear as sd* drives. It may be any of those, otherwise I haven't a clue. _________________ "One of the major problems encountered in time travel is not that of accidentally becoming your own father or mother ... The major problem is quite simply one of grammar..."
Douglas Adams |
|
Back to top |
|
|
skerb1 n00b
Joined: 14 Dec 2004 Posts: 24
|
Posted: Fri Jul 01, 2005 8:13 pm Post subject: |
|
|
Figured it out...
It seems that my udev rule for my flash card reader is failing when going to 2.6.12
In 2.6.11 there was no problem and a /dev/flash was created, but now it is not being created anymore
I filed a bug with the kernel since the device is not being read correctly anymore by sysfs |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|