On Thu, Jan 20, 2005 at 08:45:45PM -0800, Lance Lucas wrote: > Hello all, I am writing here because I have exhausted all other search > methods and problem solving skills I have. I run Debian Sid/Unstable on > an Asus/P4 machine. It also has (and runs w/o problems) XP Pro and Suse > 9.2. My main hard drive is the IDE1 Master, and Debian is installed to > hda4 on ext3. My optical drive is IDE2 Master, and I also have another > drive serving additional swap space at IDE2 slave. Here is > my /etc/fstab: > > # swap devices > /dev/hda2 swap swap pri=42 0 0 > /dev/hdd1 swap swap pri=42 0 0 > # boot devices > /dev/hda4 / ext3 defaults 1 1 > # proc devices > proc /proc proc defaults 0 0 > # other OS's > /dev/hda3 /mnt/suse92 reiserfs defaults 1 2 > /dev/hda1 /mnt/windows ntfs defaults 0 0 > # removable media > /dev/fd0 /mnt/floppy auto noauto,exec,rw,user 0 0 > /dev/hdc /mnt/cdrom iso9660 noauto,exec,ro,user 0 0 > Try putting ide-cd in /etc/modules and add "hdc=cdrom" to your kernel boot parameters. > However, /dec/hdc is not created by udev at boot. It just doesn't > exist. However, /.dev/hdc does exist (as does, it seems, a list of > basically all devices theoretically possible). So I tried > mounting /.dev/hdc, and this occurs: > > llucas@rivera:~$ ls /dev/hd* > /dev/hda /dev/hda2 /dev/hda4 /dev/hdd1 > /dev/hda1 /dev/hda3 /dev/hdd /dev/hdd2 > llucas@rivera:~$ su > Password: > rivera:/home/llucas# mount -t iso9660 /.dev/hdc /mnt/cdrom -o > fs=iso9660,ro > mount: wrong fs type, bad option, bad superblock on /.dev/hdc, > missing codepage or other error > In some cases useful info is found in syslog - try > dmesg | tail or so > > rivera:/home/llucas# ls /dev/hd* > /dev/hda /dev/hda2 /dev/hda4 /dev/hdd /dev/hdd2 > /dev/hda1 /dev/hda3 /dev/hdc /dev/hdd1 > rivera:/home/llucas# > > So, for some reason, mounting /.dev/hdc throws the mount error, and then > udev creates /dev/hdc, which is automounted (and whatever media is in is > played in gnome). > > Why is /dev/hdc not created at boot, and why does this odd series of > events lead to its creation? Suse 9.2 also uses udev and creates the > device properly every time, for what it's worth...hopefully meaning > there is a solution. > > Thank you for any help anyone can provide and sorry if I have omitted > any information. > > Lance Lucas > debianuser@mantle.g-status.com > > > > -- Jerome
Attachment:
signature.asc
Description: Digital signature