You are not logged in.

#1 2004-06-10 14:01:48

vor_lord
Member
From: Fort Collins, Colorado, USA
Registered: 2004-06-10
Posts: 52

mount: special device /dev/cdroms/cdrom0 does not exist

I am new to Arch--so far I'm very happy with it (past experience is mostly Red Hat, Fedora, and Debian).  I do have a couple of remaining problems, and I'm trying to put my questions in the appropriate forums for each one.

I am having a problem, where I do not have entries in /dev for my dvd/cd combo drive.

/etc/fstab:

/dev/cdroms/cdrom0     /mnt/cd   iso9660   ro,user,noauto,unhide   0      0
/dev/cdroms/cdrom0     /mnt/dvd  udf       ro,user,noauto,unhide   0      0

dmesg:

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: LITE-ON COMBO SOHC-5232K, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
SiI3112 Serial ATA: IDE controller at PCI slot 0000:01:0b.0
SiI3112 Serial ATA: chipset revision 2
SiI3112 Serial ATA: 100% native mode on irq 201
    ide2: MMIO-DMA , BIOS settings: hde:DMA, hdf:DMA
    ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
hde: ST3120026AS, ATA DISK drive
ide2 at 0xf889f080-0xf889f087,0xf889f08a on irq 201
hdg: no response (status = 0xfe)
hdg: no response (status = 0xfe), resetting drive
hdg: no response (status = 0xfe)

Notice I have SATA (the hdg: no response thing takes forever to time out--don't know what it thinks it's finding there, but that isn't my primary problem).  My combo drive is hda, and it worked fine during install.

I've searched a long time in the forums, and could only find one post which seemed similar:
http://bbs.archlinux.org/viewtopic.php? … ght=devfsd

but that is from a long time ago, and I didn't understand what the solution actually was  sad

If I look at /dev/ide, I don't see anything except for my SATA drive:

.
|-- hd
|   |-- c2b0t0u0 -> ../host2/bus0/target0/lun0/disc
|   |-- c2b0t0u0p1 -> ../host2/bus0/target0/lun0/part1
|   |-- c2b0t0u0p10 -> ../host2/bus0/target0/lun0/part10
|   |-- c2b0t0u0p2 -> ../host2/bus0/target0/lun0/part2
|   |-- c2b0t0u0p5 -> ../host2/bus0/target0/lun0/part5
|   |-- c2b0t0u0p6 -> ../host2/bus0/target0/lun0/part6
|   |-- c2b0t0u0p7 -> ../host2/bus0/target0/lun0/part7
|   |-- c2b0t0u0p8 -> ../host2/bus0/target0/lun0/part8
|   `-- c2b0t0u0p9 -> ../host2/bus0/target0/lun0/part9
`-- host2
    `-- bus0
        `-- target0
            `-- lun0
                |-- disc
                |-- part1
                |-- part10
                |-- part2
                |-- part5
                |-- part6
                |-- part7
                |-- part8
                `-- part9

At this point I'm not sure what to try.  There is no /dev/cdroms directory at all.

I do have:

[root@strongbad dev]# ls -l cdrom 
lr-xr-xr-x  1 root root 8 Jun  9 23:08 cdrom -> /dev/hda
[root@strongbad dev]# ls -l /dev/hda
ls: /dev/hda: No such file or directory

I did not make any links by hand--I'm devfs ignorant  :oops:

Can anyone help me out?

Offline

#2 2004-06-11 02:37:58

Cobalt
Member
Registered: 2004-06-05
Posts: 10

Re: mount: special device /dev/cdroms/cdrom0 does not exist

I do have:
Code:

[root@strongbad dev]# ls -l cdrom

lr-xr-xr-x  1 root root 8 Jun  9 23:08 cdrom -> /dev/hda
[root@strongbad dev]# ls -l /dev/hda
ls: /dev/hda: No such file or directory

Hmmm..this is bizzare, where'd the symlink come from if it points to a nonexistent file?

Also, have you tried just mounting /dev/cdrom (probably wont work..but hey). Let's see, what else, /dev/cdrom points to /dev/hda, but 2.6 kernels dont really use that anymore, instead they use /dev/discs/discX/partY . So maybe even try mounting /dev/discs/disc0/part1 (or something along those lines) . Play around with that and see what happens...make sure you're trying it with a disc in the drive (i've done sillier things and wondered for days about it).

Offline

#3 2004-06-11 05:20:05

vor_lord
Member
From: Fort Collins, Colorado, USA
Registered: 2004-06-10
Posts: 52

Re: mount: special device /dev/cdroms/cdrom0 does not exist

SOLVED!

I had hda=ide-scsi in my boot params.  Removing this made everything happy (although having it was necessary under 2.4).

Lesson learned--don't pretend I know what I'm doing mucking around with the grub config...

Offline

#4 2004-06-11 15:00:26

vor_lord
Member
From: Fort Collins, Colorado, USA
Registered: 2004-06-10
Posts: 52

Re: mount: special device /dev/cdroms/cdrom0 does not exist

vor_lord wrote:

SOLVED!

I had hda=ide-scsi in my boot params.  Removing this made everything happy (although having it was necessary under 2.4).

Although now this probably means I won't be able to use it to burn CDs... am I right?

Offline

#5 2004-06-11 15:08:57

sarah31
Member
From: Middle of Canada
Registered: 2002-08-20
Posts: 2,975
Website

Re: mount: special device /dev/cdroms/cdrom0 does not exist

depends what kernel you are using. if you are using 2.6.x then yes if you are using 2.4.xx i don't know but probably not.


AKA uknowme

I am not your friend

Offline

#6 2004-06-11 19:48:15

vor_lord
Member
From: Fort Collins, Colorado, USA
Registered: 2004-06-10
Posts: 52

Re: mount: special device /dev/cdroms/cdrom0 does not exist

sarah31 wrote:

depends what kernel you are using. if you are using 2.6.x then yes if you are using 2.4.xx i don't know but probably not.

I'm using 2.6 so I think I should be ok.

Offline

#7 2004-06-11 21:59:19

sarah31
Member
From: Middle of Canada
Registered: 2002-08-20
Posts: 2,975
Website

Re: mount: special device /dev/cdroms/cdrom0 does not exist

yes you will be just fine. there is a tutorial either on this forum or on the wiki on how to burn without using the scsi emulation modules. (basically you have to make sure you have the current cdrecord (the devel verison if i am not mistaken) and then it is just a matter of referring to your device properly in the cdrecord options (if you use a gui these options are usually in the configuration somewhere).

for example if you use the commandline for burning:

cdrecord -v -speed=52 dev=ATAPI:0,1,0 more options /path/to/some.iso


AKA uknowme

I am not your friend

Offline

Board footer

Powered by FluxBB