kernel didn't create /dev/hdc and /dev/hdd

punk · 2004-12-01 14:16:55

[root@myhost ~]# uname -a
Linux myhost 2.6.9-ARCH #1 SMP Tue Oct 26 11:33:54 PDT 2004 i686 AMD Athlon(tm) XP 3000+ AuthenticAMD GNU/Linux
[root@myhost ~]# ls /dev/hd*
/dev/hda /dev/hda2 /dev/hda4 /dev/hdb1 /dev/hdb4
/dev/hda1 /dev/hda3 /dev/hdb /dev/hdb2
[root@myhost ~]# cat /proc/ide/hdc/model
RICOH DVD+RW MP5240
[root@myhost ~]# cat /proc/ide/hdd/model
PLEXTOR CD-R PX-W2410A
[root@myhost ~]# ls /proc/ide/
amd74xx drivers hda/ hdb/ hdc/ hdd/ ide0/ ide1/

what should i do ?

kakabaratruskia · 2004-12-01 14:35:47

maybe they're in /dev/cdroms.

punk · 2004-12-01 14:50:33

[root@myhost ~]# ls /dev/cdrom
ls: /dev/cdrom: No such file or directory
[root@myhost ~]# ls /dev/cdroms
ls: /dev/cdroms: No such file or directory

and some more info:

[root@myhost ~]# ls /dev/discs/
disc0 disc1

[root@myhost ~]# lspci -v
00:00.0 Host bridge: nVidia Corporation: Unknown device 01e0 (rev c1)
Subsystem: Asustek Computer, Inc.: Unknown device 80ac
Flags: bus master, 66Mhz, fast devsel, latency 0
Memory at a0000000 (32-bit, prefetchable) [size=512M]
Capabilities: [40] AGP version 3.0
Capabilities: [60] #08 [2001]

00:00.1 RAM memory: nVidia Corporation: Unknown device 01eb (rev c1)
Subsystem: Asustek Computer, Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel

00:00.2 RAM memory: nVidia Corporation: Unknown device 01ee (rev c1)
Subsystem: Asustek Computer, Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel

00:00.3 RAM memory: nVidia Corporation: Unknown device 01ed (rev c1)
Subsystem: Asustek Computer, Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel

00:00.4 RAM memory: nVidia Corporation: Unknown device 01ec (rev c1)
Subsystem: Asustek Computer, Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel

00:00.5 RAM memory: nVidia Corporation: Unknown device 01ef (rev c1)
Subsystem: Asustek Computer, Inc.: Unknown device 80ac
Flags: 66Mhz, fast devsel

00:01.0 ISA bridge: nVidia Corporation: Unknown device 0060 (rev a4)
Subsystem: Asustek Computer, Inc.: Unknown device 80ad
Flags: bus master, 66Mhz, fast devsel, latency 0
Capabilities: [48] #08 [01e1]

00:01.1 SMBus: nVidia Corporation: Unknown device 0064 (rev a2)
Subsystem: Asustek Computer, Inc.: Unknown device 0c11
Flags: 66Mhz, fast devsel, IRQ 23
I/O ports at e400 [size=32]
Capabilities: [44] Power Management version 2

00:02.0 USB Controller: nVidia Corporation: Unknown device 0067 (rev a4) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 22
Memory at cd087000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2

00:02.1 USB Controller: nVidia Corporation: Unknown device 0067 (rev a4) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 21
Memory at cd082000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2

00:02.2 USB Controller: nVidia Corporation: Unknown device 0068 (rev a4) (prog-if 20 [EHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 20
Memory at cd083000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] #0a [2080]
Capabilities: [80] Power Management version 2

00:04.0 Ethernet controller: nVidia Corporation: Unknown device 0066 (rev a1)
Subsystem: Asustek Computer, Inc.: Unknown device 80a7
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 22
Memory at cd086000 (32-bit, non-prefetchable) [size=4K]
I/O ports at d000 [size=8]
Capabilities: [44] Power Management version 2

00:05.0 Multimedia audio controller: nVidia Corporation nForce MultiMedia audio [Via VT82C686B] (rev a2)
Subsystem: Asustek Computer, Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 21
Memory at cd000000 (32-bit, non-prefetchable) [size=512K]
Capabilities: [44] Power Management version 2

00:06.0 Multimedia audio controller: nVidia Corporation nForce MultiMedia audio [Via VT82C686B] (rev a1)
Subsystem: Asustek Computer, Inc.: Unknown device 8095
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 20
I/O ports at d400 [size=256]
I/O ports at d800 [size=128]
Memory at cd080000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2

00:08.0 PCI bridge: nVidia Corporation: Unknown device 006c (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
Prefetchable memory behind bridge: cc000000-ccffffff

00:09.0 IDE interface: nVidia Corporation: Unknown device 0065 (rev a2) (prog-if 8a [Master SecP PriP])
Subsystem: Asustek Computer, Inc.: Unknown device 0c11
Flags: bus master, 66Mhz, fast devsel, latency 0
I/O ports at f000 [size=16]
Capabilities: [44] Power Management version 2

00:0c.0 PCI bridge: nVidia Corporation: Unknown device 006d (rev a3) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: c8000000-c9ffffff

00:0d.0 FireWire (IEEE 1394): nVidia Corporation: Unknown device 006e (rev a3) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 809a
Flags: bus master, 66Mhz, fast devsel, latency 0, IRQ 22
Memory at cd084000 (32-bit, non-prefetchable) [size=2K]
Memory at cd085000 (32-bit, non-prefetchable) [size=64]
Capabilities: [44] Power Management version 2

00:1e.0 PCI bridge: nVidia Corporation: Unknown device 01e8 (rev c1) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 32
Bus: primary=00, secondary=03, subordinate=03, sec-latency=32
Memory behind bridge: ca000000-cbffffff
Prefetchable memory behind bridge: c0000000-c7ffffff

01:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11)
Subsystem: Hauppauge computer works Inc. WinTV/GO
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at cc000000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2

01:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)
Subsystem: Hauppauge computer works Inc. WinTV/GO
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at cc001000 (32-bit, prefetchable) [size=4K]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2

02:01.0 Ethernet controller: 3Com Corporation: Unknown device 9201 (rev 40)
Subsystem: Asustek Computer, Inc.: Unknown device 80ab
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at c000 [size=128]
Memory at c9000000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [dc] Power Management version 2

03:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0281 (rev a1) (prog-if 00 [VGA])
Flags: bus master, 66Mhz, medium devsel, latency 248, IRQ 19
Memory at ca000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0

phrakture · 2004-12-01 16:10:01

wow, that's interesting.... try the devfs path... /dev/discs/disc0/partX and /dev/disc/disc1/partX.... are you using udev or devfs? If udev, check the rules.udev file in /etc/udev/rules/ (this file basically creates the device files for udev)

punk · 2004-12-01 16:18:40

here it is .

[root@myhost linux-2.6.9-ARCH]# cat /etc/udev/rules.d/udev.rules
#
# This ruleset should provide a DevFS-compatible device tree.
#

# There are a number of modifiers that are allowed to be used in some of the
# fields. See the udev man page for a full description of them.

# pty and tty legacy devices
KERNEL="pty[a-z][a-z,0-9]*", NAME="legacy/%k"
KERNEL="tty[a-z][a-z,0-9]*", NAME="legacy/%k"

# ide block devices
BUS="ide", KERNEL="hd*", PROGRAM="/etc/udev/ide-devfs.sh %k %b %n", NAME="%k", S YMLINK="%c{1} %c{2}"

# md block devices
KERNEL="md[0-9]*", NAME="md/%n"

# device-mapper
KERNEL="device-mapper", NAME="mapper/control"

# floppy devices
KERNEL="fd[0-9]*", NAME="fd%n", SYMLINK="floppy/%n"

# tty devices
KERNEL="tty[0-9]*", NAME="vc/%n"
KERNEL="ttyS[0-9]*", NAME="tts/%n", SYMLINK="ttyS%n"
KERNEL="ttyUSB[0-9]*", NAME="tts/USB%n"

# vc devices
KERNEL="vcs", NAME="vcc/0"
KERNEL="vcs[0-9]*", NAME="vcc/%n"
KERNEL="vcsa", NAME="vcc/a0"
KERNEL="vcsa[0-9]*", NAME="vcc/a%n"

# v4l devices
KERNEL="video[0-9]*", NAME="v4l/video%n"
KERNEL="radio[0-9]*", NAME="v4l/radio%n"
KERNEL="vbi[0-9]*", NAME="v4l/vbi%n"
KERNEL="vtx[0-9]*", NAME="v4l/vtx%n"

# dm devices (ignore them)
KERNEL="dm-[0-9]*", NAME=""

# i2c devices
KERNEL="i2c-[0-9]*", NAME="i2c/%n", SYMLINK="%k"

# loop devices
KERNEL="loop[0-9]*", NAME="loop/%n", SYMLINK="%k"

# ramdisks
KERNEL="ram[0-9]*", NAME="rd/%n", SYMLINK="%k"

# framebuffer devices
KERNEL="fb[0-9]*", NAME="fb/%n", SYMLINK="%k"

# misc
KERNEL="rtc", NAME="misc/%k", SYMLINK="%k"
KERNEL="psaux", NAME="misc/%k", SYMLINK="%k"
KERNEL="agpgart", NAME="misc/%k", SYMLINK="%k"
KERNEL="rtc", NAME="misc/%k", SYMLINK="%k"
KERNEL="psaux", NAME="misc/%k", SYMLINK="%k"
KERNEL="uinput", NAME="misc/%k", SYMLINK="%k"

# alsa devices
KERNEL="controlC[0-9]*", NAME="snd/%k"
KERNEL="hw[CD0-9]*", NAME="snd/%k"
KERNEL="pcm[CD0-9cp]*", NAME="snd/%k"
KERNEL="midi[CD0-9]*", NAME="snd/%k"
KERNEL="timer", NAME="snd/%k"
KERNEL="seq", NAME="snd/%k"

# oss devices
KERNEL="audio*", NAME="sound/%k", SYMLINK="%k"
KERNEL="dmmidi", NAME="sound/%k", SYMLINK="%k"
KERNEL="dsp*", NAME="sound/%k", SYMLINK="%k"
KERNEL="midi*", NAME="sound/%k", SYMLINK="%k"
KERNEL="mixer*", NAME="sound/%k", SYMLINK="%k"
KERNEL="sequencer*", NAME="sound/%k", SYMLINK="%k"

# input devices
KERNEL="mice", NAME="input/%k"
KERNEL="mouse*", NAME="input/%k"
KERNEL="event*", NAME="input/%k"
KERNEL="js*", NAME="input/%k"
KERNEL="ts*", NAME="input/%k"

# USB devices
KERNEL="hiddev*", NAME="usb/%k"
KERNEL="auer*", NAME="usb/%k"
KERNEL="legousbtower*", NAME="usb/%k"
KERNEL="dabusb*", NAME="usb/%k"
BUS="usb", KERNEL="lp[0-9]*", NAME="usb/%k"

# netlink devices
KERNEL="route", NAME="netlink/%k"
KERNEL="skip", NAME="netlink/%k"
KERNEL="usersock", NAME="netlink/%k"
KERNEL="fwmonitor", NAME="netlink/%k"
KERNEL="tcpdiag", NAME="netlink/%k"
KERNEL="nflog", NAME="netlink/%k"
KERNEL="xfrm", NAME="netlink/%k"
KERNEL="arpd", NAME="netlink/%k"
KERNEL="route6", NAME="netlink/%k"
KERNEL="ip6_fw", NAME="netlink/%k"
KERNEL="dnrtmsg", NAME="netlink/%k"
KERNEL="tap*", NAME="netlink/%k"

# CAPI devices
KERNEL="capi", NAME="capi20", SYMLINK="isdn/capi20"
KERNEL="capi*", NAME="capi/%n"

# Network devices
KERNEL="tun", NAME="net/%k"

# raw devices
KERNEL="raw[0-9]*", NAME="raw/%k"
[root@myhost linux-2.6.9-ARCH]#

punk · 2004-12-01 18:13:20

please help, i need to get my optical drives running

i didn't make any modifications to the default kernel/udev configuration

if i can't solve this, how can i install lilo+kernel2.4 ? (it worked back then)

phrakture · 2004-12-01 19:25:03

oh, they're both optical drives? didn't catch that.... modprobe ide-cd

edit:
if that doesn't work, output

# dmesg | grep -i hdc

and

# dmesg | grep -i hdd

here...

what does your boot params look like? do you have hdc=ide-scsi and hdd=ide-scsi?

punk · 2004-12-01 19:35:12

[root@myhost ~]# modprobe ide-cd
FATAL: Module ide_cd not found.

[root@myhost ~]# dmesg | grep -i hdc
Kernel command line: auto BOOT_IMAGE=arch ro root=301 hdc=ide-scsi hdd=ide-scsi
ide_setup: hdc=ide-scsi
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hdc: RICOH DVD+RW MP5240, ATAPI CD/DVD-ROM drive
[root@myhost ~]# dmesg | grep -i hdd
Kernel command line: auto BOOT_IMAGE=arch ro root=301 hdc=ide-scsi hdd=ide-scsi
ide_setup: hdd=ide-scsi
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hdd: PLEXTOR CD-R PX-W2410A, ATAPI CD/DVD-ROM drive

sarah31 · 2004-12-01 19:49:19

did you add your user to the optical group? there was a news release somewhere about this. .....

http://www.archlinux.org/news.php#106

phrakture · 2004-12-01 19:57:18

errr sorry modprobe ide-scsi...

mattux · 2004-12-01 20:05:27

i think you didn´t need the kernel that hdc is a scsi-device ... the ide-scsi driver is broken in the 2.6* (or?)

try to change your lilo / grub config and remove the " hdc=ide-scsi "

mattux

punk · 2004-12-01 20:09:39

modprobe ide-scsi solved the problem
now i have /dev/sr0 and /dev/sr1 from where i can acess my drives
thank you !

sarah31 wrote:

did you add your user to the optical group? there was a news release somewhere about this. .....
http://www.archlinux.org/news.php#106

i instaled 0.7 beta 2
and then upgrade with:
pacman -S --refresh
pacman -S -u

but that didn't create the optical and audio groups (maybe because i had previously added slocate group manualy ? slocate package didn't add the group "slocate" to /etc/group)
then i had to add them manualy and then add root and my user to them
and that still didn't solve my problem

punk · 2004-12-01 20:17:04

even more weird

i start k3b with a cd mounted on /dev/sr1 and only /dev/sr1 is detected (adding /dev/sr0 doesn't work)

i start k3b with a cd mounted on /dev/sr0 and only /dev/sr0 is detected (adding /dev/sr1 doesn't work)

i start k3b with both drives with cds mounted and k3b detects them both !

b0uncer · 2004-12-03 09:16:22

I've had some problems with my cds too...everything worked nicely in somewhere around 2.6.6 or something. then I went and upgraded to 2.6.8, which worked almost well - though my usb stick had problems. upgrade to 2.6.9 helped, but my cd-r (and -rw) drives did not function any more - a patch to 2.6.10-rc1 helped and made everything work, except that occasionally the cd-rom drives (also rw) do not work. usb works like magic now.

I have not got any answer what makes my /dev/cdroms/cdrom0 and cdrom1 disappear (plus their symlinks and everything that might point to them) at boot sometimes (not every time!). taking hdX=ide-scsi worked for the first time, but now that it's off, my pc still tends to "lose" those drives once in a while if I happen to boot. and when they are back, if they are, the permissions are reseted again - with no obvious, visible reason. funny? I don't think so...I've triple checked every config file of udev, grub and kernel (and modprobe etc. etc. etc.) and everything ought to be fine. my only thought is now, that something in my kernel must be broken. or then I have some green little monsters crawling around my linux installation, doing some funky stuff...hehe

I'm waiting for a new stable (not a patch) version of the linux kernel, hoping it works. if not, then I'm afraid I'll have to downgrade to 2.6.6 or even 2.4 - the whole 2.6 kernel sucks, it won't play 3d anymore with my card, my devices are missing or not functioning, I have problems with usb and so on. I was even unable to enable framebuffer with 2.6 - made my kernel panic, no matter what I tried.

something _really_ is wrong with 2.6 series...hopefully new kernel would save me. or older.

phrakture · 2004-12-03 15:19:32

b0uncer wrote:

something _really_ is wrong with 2.6 series...hopefully new kernel would save me. or older.

you can't blame the kernel for your problems... it works perfect for 95% of us... the other 4% have minor problems.... if you have problems, it's most likely your configuration...

for instance:

b0uncer wrote:

the whole 2.6 kernel sucks, it won't play 3d anymore with my card

3d has nothing to do with the kernel... 3d support is a different module which either comes with X or the vendor (in the case of nvidia)

b0uncer wrote:

I have problems with usb

modprobe the correct modules.... check the newsletter of search the forums...

Arch Linux

#1 2004-12-01 14:16:55

kernel didn't create /dev/hdc and /dev/hdd

#2 2004-12-01 14:35:47

Re: kernel didn't create /dev/hdc and /dev/hdd

#3 2004-12-01 14:50:33

Re: kernel didn't create /dev/hdc and /dev/hdd

#4 2004-12-01 16:10:01

Re: kernel didn't create /dev/hdc and /dev/hdd

#5 2004-12-01 16:18:40

Re: kernel didn't create /dev/hdc and /dev/hdd

#6 2004-12-01 18:13:20

Re: kernel didn't create /dev/hdc and /dev/hdd

#7 2004-12-01 19:25:03

Re: kernel didn't create /dev/hdc and /dev/hdd

#8 2004-12-01 19:35:12

Re: kernel didn't create /dev/hdc and /dev/hdd

#9 2004-12-01 19:49:19

Re: kernel didn't create /dev/hdc and /dev/hdd

#10 2004-12-01 19:57:18

Re: kernel didn't create /dev/hdc and /dev/hdd

#11 2004-12-01 20:05:27

Re: kernel didn't create /dev/hdc and /dev/hdd

#12 2004-12-01 20:09:39

Re: kernel didn't create /dev/hdc and /dev/hdd

#13 2004-12-01 20:17:04

Re: kernel didn't create /dev/hdc and /dev/hdd

#14 2004-12-03 09:16:22

Re: kernel didn't create /dev/hdc and /dev/hdd

#15 2004-12-03 15:19:32

Re: kernel didn't create /dev/hdc and /dev/hdd

Board footer