Why did you change the CDROM assignment SuSE?

newer
Sorry: masquerading timeouts set...

Jerry Kreps

10 Mar 2001 10 Mar '01

05:52

In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0 Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0 Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device... I have no trouble firing YaST or YaST2, so they must be using some sort of driver on the fly. Here is what vdir /dev/cd* shows: brw-rw---- 1 root disk 19, 128 Jan 19 02:36 /dev/cdouble0 brw-rw---- 1 root disk 19, 129 Jan 19 02:36 /dev/cdouble1 lrwxrwxrwx 1 root root 3 Feb 24 20:01 /dev/cdrom -> hdd brw-r----- 1 root disk 24, 0 Jan 19 02:36 /dev/cdu535 I suspect that YaST is using /dev/cdu535. BUT when I do: mount -t iso9660 -r /dev/cdu535 /cdrom I get the message: "mount: the kernel does not recognize /dev/cdu535 as a block device (maybe `insmod driver'?) " I've never ventured into mk_nod territory, SuSE so help me out here. JLK

Show replies by date

Avi Schwartz

10 Mar 10 Mar

06:09

New subject: [SLE] Why did you change the CDROM assignment SuSE?

Jerry, why do you think there is something wrong? If your CDROM is an IDE cdrom then /dev/hdx is correct. In my case the cdrom is /dev/hdc. It was always the case and /dev/cdrom is a link that is created for convinience. Avi --On Friday, March 09, 2001 23:52:15 -0600 Jerry Kreps wrote:

...

In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

I have no trouble firing YaST or YaST2, so they must be using some sort of driver on the fly.

Here is what vdir /dev/cd* shows: brw-rw---- 1 root disk 19, 128 Jan 19 02:36 /dev/cdouble0 brw-rw---- 1 root disk 19, 129 Jan 19 02:36 /dev/cdouble1 lrwxrwxrwx 1 root root 3 Feb 24 20:01 /dev/cdrom -> hdd brw-r----- 1 root disk 24, 0 Jan 19 02:36 /dev/cdu535

I suspect that YaST is using /dev/cdu535. BUT when I do: mount -t iso9660 -r /dev/cdu535 /cdrom I get the message: "mount: the kernel does not recognize /dev/cdu535 as a block device (maybe `insmod driver'?) "

I've never ventured into mk_nod territory, SuSE so help me out here. JLK

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!

Jerry Kreps

06:26

New subject: [SLE] Why did you change the CDROM assignment SuSE?

On Saturday 10 March 2001 00:09, you wrote:

...

Jerry, why do you think there is something wrong? If your CDROM is an IDE cdrom then /dev/hdx is correct. In my case the cdrom is /dev/hdc. It was always the case and /dev/cdrom is a link that is created for convinience.

Mine is: lrwxrwxrwx 1 root root 3 /dev/cdrom -> hdd and it doesn't work: Because in three years I've used the same box and cdrom with SuSE and it NEVER BEFORE set up the fstab entry as /dev/hdd /cdrom auto ro,noauto,user,exec 0 0 that is, with /dev/hdd. It has ALWAYS been /dev/cdrom /cdrom iso9660 ro,noauto,user,exec 0 0 Further, previously, it's ALWAYS worked with either YaST or a music CD. YaST and YaST2 don't have any trouble accessing the CDROM, but I cannot play music CD because of the error msg shown below. "mount: the kernel does not recognize /dev/hdd as a block device (maybe `insmod driver'?) " which is the same error msg I get when I try sonycd or cdu535 or cdu31a, which is what my CD actually is. Also, the node number don't correspond to cd devices. JLK

...

Avi

--On Friday, March 09, 2001 23:52:15 -0600 Jerry Kreps

wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

I have no trouble firing YaST or YaST2, so they must be using some sort of driver on the fly.

Here is what vdir /dev/cd* shows: brw-rw---- 1 root disk 19, 128 Jan 19 02:36 /dev/cdouble0 brw-rw---- 1 root disk 19, 129 Jan 19 02:36 /dev/cdouble1 lrwxrwxrwx 1 root root 3 Feb 24 20:01 /dev/cdrom -> hdd brw-r----- 1 root disk 24, 0 Jan 19 02:36 /dev/cdu535

I suspect that YaST is using /dev/cdu535. BUT when I do: mount -t iso9660 -r /dev/cdu535 /cdrom I get the message: "mount: the kernel does not recognize /dev/cdu535 as a block device (maybe `insmod driver'?) "

I've never ventured into mk_nod territory, SuSE so help me out here. JLK

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

Avi Schwartz

06:36

New subject: [SLE] Why did you change the CDROM assignment SuSE?

Mine is setup as: /dev/hdc /cdrom auto ro,noauto,user,exec 0 0 lrwxrwxrwx 1 root root 3 Jan 20 05:10 /dev/cdrom -> hdc brw-rw-rw- 1 root disk 22, 0 Jan 19 02:36 /dev/hdc Avi --On Saturday, March 10, 2001 00:26:19 -0600 Jerry Kreps wrote:

...

On Saturday 10 March 2001 00:09, you wrote:

...
Jerry, why do you think there is something wrong? If your CDROM is an IDE cdrom then /dev/hdx is correct. In my case the cdrom is /dev/hdc. It was always the case and /dev/cdrom is a link that is created for convinience.

Mine is: lrwxrwxrwx 1 root root 3 /dev/cdrom -> hdd and it doesn't work:

Because in three years I've used the same box and cdrom with SuSE and it NEVER BEFORE set up the fstab entry as /dev/hdd /cdrom auto ro,noauto,user,exec 0 0 that is, with /dev/hdd. It has ALWAYS been /dev/cdrom /cdrom iso9660 ro,noauto,user,exec 0 0

Further, previously, it's ALWAYS worked with either YaST or a music CD.

YaST and YaST2 don't have any trouble accessing the CDROM, but I cannot play music CD because of the error msg shown below. "mount: the kernel does not recognize /dev/hdd as a block device (maybe `insmod driver'?) " which is the same error msg I get when I try sonycd or cdu535 or cdu31a, which is what my CD actually is.

Also, the node number don't correspond to cd devices. JLK

...
Avi

--On Friday, March 09, 2001 23:52:15 -0600 Jerry Kreps

wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

I have no trouble firing YaST or YaST2, so they must be using some sort of driver on the fly.

Here is what vdir /dev/cd* shows: brw-rw---- 1 root disk 19, 128 Jan 19 02:36 /dev/cdouble0 brw-rw---- 1 root disk 19, 129 Jan 19 02:36 /dev/cdouble1 lrwxrwxrwx 1 root root 3 Feb 24 20:01 /dev/cdrom -> hdd brw-r----- 1 root disk 24, 0 Jan 19 02:36 /dev/cdu535

I suspect that YaST is using /dev/cdu535. BUT when I do: mount -t iso9660 -r /dev/cdu535 /cdrom I get the message: "mount: the kernel does not recognize /dev/cdu535 as a block device (maybe `insmod driver'?) "

I've never ventured into mk_nod territory, SuSE so help me out here. JLK

-- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!

Jerry Kreps

06:46

New subject: [SLE] Why did you change the CDROM assignment SuSE?

Mine is the same except for hdd. Now, I CAN read vfat cds like Street Atlas. I just can play iso9660 cds JLK On Saturday 10 March 2001 00:36, you wrote:

...

Mine is setup as:

/dev/hdc /cdrom auto ro,noauto,user,exec 0 0

lrwxrwxrwx 1 root root 3 Jan 20 05:10 /dev/cdrom -> hdc brw-rw-rw- 1 root disk 22, 0 Jan 19 02:36 /dev/hdc

Avi

--On Saturday, March 10, 2001 00:26:19 -0600 Jerry Kreps

wrote:

...
On Saturday 10 March 2001 00:09, you wrote:

...
Jerry, why do you think there is something wrong? If your CDROM is an IDE cdrom then /dev/hdx is correct. In my case the cdrom is /dev/hdc. It was always the case and /dev/cdrom is a link that is created for convinience.

Mine is: lrwxrwxrwx 1 root root 3 /dev/cdrom -> hdd and it doesn't work:

Because in three years I've used the same box and cdrom with SuSE and it NEVER BEFORE set up the fstab entry as /dev/hdd /cdrom auto ro,noauto,user,exec 0 0 that is, with /dev/hdd. It has ALWAYS been /dev/cdrom /cdrom iso9660 ro,noauto,user,exec 0 0

Further, previously, it's ALWAYS worked with either YaST or a music CD.

YaST and YaST2 don't have any trouble accessing the CDROM, but I cannot play music CD because of the error msg shown below. "mount: the kernel does not recognize /dev/hdd as a block device (maybe `insmod driver'?) " which is the same error msg I get when I try sonycd or cdu535 or cdu31a, which is what my CD actually is.

Also, the node number don't correspond to cd devices. JLK

...
Avi

--On Friday, March 09, 2001 23:52:15 -0600 Jerry Kreps

wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

I have no trouble firing YaST or YaST2, so they must be using some sort of driver on the fly.

Here is what vdir /dev/cd* shows: brw-rw---- 1 root disk 19, 128 Jan 19 02:36 /dev/cdouble0 brw-rw---- 1 root disk 19, 129 Jan 19 02:36 /dev/cdouble1 lrwxrwxrwx 1 root root 3 Feb 24 20:01 /dev/cdrom -> hdd brw-r----- 1 root disk 24, 0 Jan 19 02:36 /dev/cdu535

I suspect that YaST is using /dev/cdu535. BUT when I do: mount -t iso9660 -r /dev/cdu535 /cdrom I get the message: "mount: the kernel does not recognize /dev/cdu535 as a block device (maybe `insmod driver'?) "

I've never ventured into mk_nod territory, SuSE so help me out here. JLK

Álvaro A. Novo

06:21

New subject: [SLE] Why did you change the CDROM assignment SuSE?

On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...

In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd Here's my /var/log/boot.msg (snipped): <4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63 Yours shouldn't be that different. Hope it helps, _____________ Alvaro Novo SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

Jerry Kreps

06:40

New subject: [SLE] Why did you change the CDROM assignment SuSE?

Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6> Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd). The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work. JLK ... On Saturday 10 March 2001 00:21, you wrote:

...

On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

Avi Schwartz

06:42

New subject: [SLE] Why did you change the CDROM assignment SuSE?

But you don't mount music CDs. Avi --On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps wrote:

...

Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!

Jerry Kreps

06:51

New subject: [SLE] Why did you change the CDROM assignment SuSE?

I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked. JLK On Saturday 10 March 2001 00:42, you wrote:

...

But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

Avi Schwartz

07:06

New subject: [SLE] Why did you change the CDROM assignment SuSE?

My dmesg shows message pretty similar to yours: ide0: BM-DMA at 0x1c00-0x1c07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x1c08-0x1c0f, BIOS settings: hdc:DMA, hdd:pio hda: IBM-DJSA-232, ATA DISK drive hdc: MATSHITADVD-ROM SR-8175, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: 62506080 sectors (32003 MB) w/1874KiB Cache, CHS=4134/240/63 hdc: ATAPI 24X DVD-ROM drive, 512kB Cache Uniform CD-ROM driver Revision: 3.12 The only difference I see is the driver revision number but I doubt it is the problem. Avi --On Saturday, March 10, 2001 00:51:34 -0600 Jerry Kreps wrote:

...

I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-- Avi Schwartz Get a Life, avi@CFFtechnologies.com Get Linux!

Álvaro A. Novo

07:20

New subject: [SLE] Why did you change the CDROM assignment SuSE?

On Saturday 10 March 2001 01:06, Avi Schwartz wrote:

...

My dmesg shows message pretty similar to yours:

I'm no expert, but it seems that Jerry's dmesg has a difference that may explain is problem Avi's

...

ide0: BM-DMA at 0x1c00-0x1c07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x1c08-0x1c0f, BIOS settings: hdc:DMA, hdd:pio

Jerry's

...

...
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio

Alvaro's

...

ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio

NOTICE that Avi's and mine have "hdc:DMA", while jerry "hdd:pio" -- the message both I and Avi get for hdd (our empty bays)... (all hdX are pio for Jerry) It seems BIOS related, but unfortunately I don't know how to move from here. I hope someone can shed some light! _____________ Alvaro Novo SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 1:17am up 7:14, 3 users, load average: 0.04, 0.49, 0.58

Tor Sigurdsson

11:58

New subject: [SLE] Why did you change the CDROM assignment SuSE?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok, I have heard about desperate, but this has jsut become ridiculous..... Try: ln -s /dev/hdd /dev/cdrom now start kscd, xmcd or some other CD playing application. And.. enjoy. - -tosi Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...

I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQE6qhbR6mRH+PEpr2YRAm6VAJ9T8zS58jBW0Rp+CAGKGD265pwsVACfW92+ 4OiVeHLM1cdzSdQkFjol5vU= =2Fqv -----END PGP SIGNATURE-----

Jerry Kreps

13:45

New subject: [SLE] Why did you change the CDROM assignment SuSE?

That link was alredy there. JLK On Saturday 10 March 2001 05:58, Tor Sigurdsson wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

- -tosi

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQE6qhbR6mRH+PEpr2YRAm6VAJ9T8zS58jBW0Rp+CAGKGD265pwsVACfW92+ 4OiVeHLM1cdzSdQkFjol5vU= =2Fqv -----END PGP SIGNATURE-----

Mikke Mattsson

13:57

New subject: SV: [SLE] Why did you change the CDROM assignment SuSE?

Have you tried simply rewriting the fstab file so it reads like it used to before you upgraded? ----- Ursprungligt meddelande ----- Från: "Jerry Kreps" Till: "Tor Sigurdsson" Kopia: Skickat: den 10 mars 2001 14:45 Ämne: Re: [SLE] Why did you change the CDROM assignment SuSE? That link was alredy there. JLK On Saturday 10 March 2001 05:58, Tor Sigurdsson wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

Jerry Kreps

15:08

New subject: SV: [SLE] Why did you change the CDROM assignment SuSE?

That was the first trick I tried. No joy. JLK On Saturday 10 March 2001 07:57, you wrote:

...

Have you tried simply rewriting the fstab file so it reads like it used to before you upgraded?

----- Ursprungligt meddelande ----- Från: "Jerry Kreps" Till: "Tor Sigurdsson" Kopia: Skickat: den 10 mars 2001 14:45 Ämne: Re: [SLE] Why did you change the CDROM assignment SuSE?

That link was alredy there. JLK

On Saturday 10 March 2001 05:58, Tor Sigurdsson wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

Jerry Kreps

13:52

New subject: [SLE] Why did you change the CDROM assignment SuSE?

My cdrom is ok. The problem arose when I fired Grip to rip some more Motzart and it said it couldn't find my CD. So I fired Kscd<2> and it gave the same message. So, I thought my fstab was messed up and thats when I found the /hdd thing. In 7.0 and prior versions of SuSE my fstab had only /dev/cdrom /cdrom as the device and mount point, and the /dev directory didn't have any link to /hdd. So, I thought SuSE had messed up. On a lark I started trying other cd players. None of them worked except Kscd<1>. I am going to check their configs and see why then don't see either /dev/cdrom or /hdd. JLK On Saturday 10 March 2001 05:58, you wrote:

...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

- -tosi

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote:

...
In SuSE 7.0 what used to be in /etc/fstab was /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0

Here is what SuSE 7.1 put into /etc/fstab for my cdrom: /dev/hdd /cdrom auto ro,noauto,user,exec 0 0

Obviously, my cdrom is not a harddisk so /dev/hdd is not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQE6qhbR6mRH+PEpr2YRAm6VAJ9T8zS58jBW0Rp+CAGKGD265pwsVACfW92+ 4OiVeHLM1cdzSdQkFjol5vU= =2Fqv -----END PGP SIGNATURE-----

Anders Johansson

14:57

New subject: [SLE] Why did you change the CDROM assignment SuSE?

Have you checked the permissions on /dev/hdd? Music CD players need permission to read the raw device HTH Anders On Saturday 10 March 2001 14:52, Jerry Kreps wrote:

...

My cdrom is ok. The problem arose when I fired Grip to rip some more Motzart and it said it couldn't find my CD. So I fired Kscd<2> and it gave the same message. So, I thought my fstab was messed up and thats when I found the /hdd thing. In 7.0 and prior versions of SuSE my fstab had only /dev/cdrom /cdrom as the device and mount point, and the /dev directory didn't have any link to /hdd. So, I thought SuSE had messed up. On a lark I started trying other cd players. None of them worked except Kscd<1>.

I am going to check their configs and see why then don't see either /dev/cdrom or /hdd. JLK

On Saturday 10 March 2001 05:58, you wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

- -tosi

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote: > In SuSE 7.0 what used to be in /etc/fstab was > /dev/cdrom /cdrom iso9660 > ro,noauto, user, exec 0 0 > > Here is what SuSE 7.1 put into /etc/fstab for my cdrom: > /dev/hdd /cdrom auto > ro,noauto,user,exec 0 0 > > Obviously, my cdrom is not a harddisk so /dev/hdd is > not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQE6qhbR6mRH+PEpr2YRAm6VAJ9T8zS58jBW0Rp+CAGKGD265pwsVACfW92+ 4OiVeHLM1cdzSdQkFjol5vU= =2Fqv -----END PGP SIGNATURE-----

Jerry Kreps

15:07

New subject: [SLE] Why did you change the CDROM assignment SuSE?

It's rw for the group "disk" and I'm in that group. When I tried to rip my Mozart cds last night Grip couldn't see the CDROM. I tried KDE2 Kscd and neither could it. As it turns out I can play cds ok using the KDE1 Kscd player. The KDE2 Kscd player is broken. When I wouldn't play I looked at the /dev/cdrom entry and saw that it was a link to /dev/hdd, which wasn't the way my previous installs of SuSE were set up. I haven't figured out why Grip won't see the CDROM yet. JLK On Saturday 10 March 2001 07:52, you wrote:

...

My cdrom is ok. The problem arose when I fired Grip to rip some more Motzart and it said it couldn't find my CD. So I fired Kscd<2> and it gave the same message. So, I thought my fstab was messed up and thats when I found the /hdd thing. In 7.0 and prior versions of SuSE my fstab had only /dev/cdrom /cdrom as the device and mount point, and the /dev directory didn't have any link to /hdd. So, I thought SuSE had messed up. On a lark I started trying other cd players. None of them worked except Kscd<1>.

I am going to check their configs and see why then don't see either /dev/cdrom or /hdd. JLK

On Saturday 10 March 2001 05:58, you wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

- -tosi

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote:

...
On Friday 09 March 2001 23:52, Jerry Kreps wrote: > In SuSE 7.0 what used to be in /etc/fstab was > /dev/cdrom /cdrom iso9660 > ro,noauto, user, exec 0 0 > > Here is what SuSE 7.1 put into /etc/fstab for my > cdrom: /dev/hdd /cdrom auto > ro,noauto,user,exec 0 0 > > Obviously, my cdrom is not a harddisk so /dev/hdd is > not a correct device...

It's correct, it's the slave of the secondary IDE "port"; in my case, my CD-RW is /dev/hdc the master of the secondary IDE... and while my CDROM worked it was /dev/hdd

Here's my /var/log/boot.msg (snipped):

<4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4>ide1 at 0x170-0x177,0x376 on irq 15 <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) w/2048KiB Cache, CHS=1245/255/63

Yours shouldn't be that different.

Hope it helps, _____________ Alvaro Novo

SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 12:20am up 6:17, 4 users, load average: 1.16, 0.76, 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQE6qhbR6mRH+PEpr2YRAm6VAJ9T8zS58jBW0Rp+CAGKGD265pwsVACfW92+ 4OiVeHLM1cdzSdQkFjol5vU= =2Fqv -----END PGP SIGNATURE-----

Peter B. Van Campen

17:21

New subject: [SLE] Why did you change the CDROM assignment SuSE?

Jerry, This is probably why it seems that GRIP is not working: This article at SLASHDOT; http://slashdot.org/articles/01/03/10/006217.shtml ; tells that "GRACENOTE CDDB" service is refusing service to GRIP and other players and devices that have NOT bought a license to "GRACENOTE CDDB" service. ............................................... Pete VC Jerry Kreps wrote:

...

It's rw for the group "disk" and I'm in that group.

When I tried to rip my Mozart cds last night Grip couldn't see the CDROM. I tried KDE2 Kscd and neither could it.

As it turns out I can play cds ok using the KDE1 Kscd player. The KDE2 Kscd player is broken. When I wouldn't play I looked at the /dev/cdrom entry and saw that it was a link to /dev/hdd, which wasn't the way my previous installs of SuSE were set up. I haven't figured out why Grip won't see the CDROM yet. JLK

On Saturday 10 March 2001 07:52, you wrote:

...
My cdrom is ok. The problem arose when I fired Grip to rip some more Motzart and it said it couldn't find my CD. So I fired Kscd<2> and it gave the same message. So, I thought my fstab was messed up and thats when I found the /hdd thing. In 7.0 and prior versions of SuSE my fstab had only /dev/cdrom /cdrom as the device and mount point, and the /dev directory didn't have any link to /hdd. So, I thought SuSE had messed up. On a lark I started trying other cd players. None of them worked except Kscd<1>.

I am going to check their configs and see why then don't see either /dev/cdrom or /hdd. JLK

On Saturday 10 March 2001 05:58, you wrote:

...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

- -tosi

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

JLK

On Saturday 10 March 2001 00:42, you wrote:

...
But you don't mount music CDs.

Avi

--On Saturday, March 10, 2001 00:40:36 -0600 Jerry Kreps

wrote:

...
Here is my boot.msg snippet: ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio <4> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio <4> hda: WDC AC32100H, ATA DISK drive <4> hdb: WDC AC21200H, ATA DISK drive <4> hdc: WDC AC26400R, ATA DISK drive <4> hdd: CD-ROM CDU311, ATAPI CDROM drive <4> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 <4> ide1 at 0x170-0x177,0x376 on irq 15 <4> hda: Disabling (U)DMA for WDC AC32100H <4> hda: DMA disabled <6> hda: WDC AC32100H, 2014MB w/128kB Cache, CHS=1023/64/63 <6> hdb: WDC AC21200H, 1222MB w/128kB Cache, CHS=621/64/63, DMA <6> hdc: WDC AC26400R, 6149MB w/512kB Cache, CHS=13328/15/63, (U)DMA <4> hdd: ATAPI 8X CD-ROM drive, 256kB Cache <6> Uniform CD-ROM driver Revision: 3.11 <6>

Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

JLK

....

On Saturday 10 March 2001 00:21, you wrote: > On Friday 09 March 2001 23:52, Jerry Kreps wrote: > > In SuSE 7.0 what used to be in /etc/fstab was > > /dev/cdrom /cdrom iso9660 > > ro,noauto, user, exec 0 0 > > > > Here is what SuSE 7.1 put into /etc/fstab for my > > cdrom: /dev/hdd /cdrom auto > > ro,noauto,user,exec 0 0 > > > > Obviously, my cdrom is not a harddisk so /dev/hdd is > > not a correct device... > > It's correct, it's the slave of the secondary IDE "port"; > in my case, my CD-RW is /dev/hdc the master of the > secondary IDE... and while my CDROM worked it was /dev/hdd > > Here's my /var/log/boot.msg (snipped): > > <4> ide0: BM-DMA at 0xd800-0xd807, BIOS settings: > hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xd808-0xd80f, > BIOS settings: hdc:DMA, hdd:pio <4>hda: IBM-DTLA-307045, > ATA DISK drive <4>hdb: Maxtor 51024U2, ATA DISK drive > <6>VP_IDE: Calibrating PCI clock ... 32.76 MHz > <4>hdc: ZIPCD 4x650, ATAPI CD/DVD-ROM drive > <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > <4>ide1 at 0x170-0x177,0x376 on irq 15 > <6>hda: 90069840 sectors (46116 MB) w/1916KiB Cache, > CHS=5606/255/63 <6>hdb: 20010816 sectors (10246 MB) > w/2048KiB Cache, CHS=1245/255/63 > > Yours shouldn't be that different. > > Hope it helps, > _____________ > Alvaro Novo > > SuSE 7.1 -=- Kernel 2.4.2-4 -=- KDE 2.1 > 12:20am up 6:17, 4 users, load average: 1.16, 0.76, > 0.41

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQE6qhbR6mRH+PEpr2YRAm6VAJ9T8zS58jBW0Rp+CAGKGD265pwsVACfW92+ 4OiVeHLM1cdzSdQkFjol5vU= =2Fqv -----END PGP SIGNATURE-----

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-- =============================== Peter B.Van Campen Peter_B@vancampen.org =============================== -- <>

Chris Reeves

18:02

New subject: [SLE] Why did you change the CDROM assignment SuSE?

See further down... Jerry Kreps wrote:

...

It's rw for the group "disk" and I'm in that group.

When I tried to rip my Mozart cds last night Grip couldn't see the CDROM. I tried KDE2 Kscd and neither could it.

As it turns out I can play cds ok using the KDE1 Kscd player. The KDE2 Kscd player is broken. When I wouldn't play I looked at the /dev/cdrom entry and saw that it was a link to /dev/hdd, which wasn't the way my previous installs of SuSE were set up. I haven't figured out why Grip won't see the CDROM yet.

On Saturday 10 March 2001 07:52, you wrote:

...
My cdrom is ok. The problem arose when I fired Grip to rip some more Motzart and it said it couldn't find my CD. So I fired Kscd<2> and it gave the same message. So, I thought my fstab was messed up and thats when I found the /hdd thing. In 7.0 and prior versions of SuSE my fstab had only /dev/cdrom /cdrom as the device and mount point, and the /dev directory didn't have any link to /hdd. So, I thought SuSE had messed up. On a lark I started trying other cd players. None of them worked except Kscd<1>.

I am going to check their configs and see why then don't see either /dev/cdrom or /hdd.

On Saturday 10 March 2001 05:58, you wrote:

...
Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

...
...
Now, my CDROM is indeed the slave of ide1 BUT, NEVER, before 7.1 has SuSE refered to it as /hdd in the fstab. I've check my previous copies of fstab and they all refer to /dev/cdrom (which was NOT a link to hdd).

I would agree that in the past /etc/fstab has referred to /dev/cdrom. However, I'm sure /dev/cdrom has been a link to /dev/hdd (in your case) for a while. For example, my SuSE 6.1 machine has /dev/cdrom as a link, as does my 7.0 installation. Maybe it's just me, but I'm sure it has been that way for a while.

...

...
...
...
...
...
The fact remains that while YaST and YaST2 have no trouble accessing the SuSE CDs, I can't play a music CD because I can't mount it. I've tried to inmod and modprove cdu31a, sonycd and cdu535. None work.

These are drivers for special, proprietry, CD-ROM type things.

...

...
...
...
...
...
On Saturday 10 March 2001 00:21, you wrote: > On Friday 09 March 2001 23:52, Jerry Kreps wrote: > > In SuSE 7.0 what used to be in /etc/fstab was > > /dev/cdrom /cdrom iso9660 > > ro,noauto, user, exec 0 0 > > > > Here is what SuSE 7.1 put into /etc/fstab for my > > cdrom: /dev/hdd /cdrom auto > > ro,noauto,user,exec 0 0 > > > > Obviously, my cdrom is not a harddisk so /dev/hdd is > > not a correct device...

You could always change your /etc/fstab entry to /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0 as before. Check permissions, etc. as mentioned before, but I'm fairly certain there's some other problem here. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\

Jerry Kreps

19:33

New subject: [SLE] Why did you change the CDROM assignment SuSE? SOLVED!

Even though I was a member of the group 'disk', which I thought would give me group rw rights to /dev/hdd, I discovered that I was wrong. Being in the 'disk' group didn't give me rw access. I discovered this by accident when, as root, I was testing out a fresh copy of cdparanoia. It worked! So, I tried the old copy and it worked to! Suddenly, Grip could see the CDROM. So, Chris, I added a+rw to /dev/hdd and I can use Grip as me. Thanks! Now I have to go back and see what it is about group priviledges that I don't understand. Anyone got a pair of functioning neurons they can sell me? My pair seems to have broken down and the replacement factory has shut down too! JLK On Saturday 10 March 2001 12:02, you wrote:

...

See further down...

Jerry Kreps wrote:

...
It's rw for the group "disk" and I'm in that group.

When I tried to rip my Mozart cds last night Grip couldn't see the CDROM. I tried KDE2 Kscd and neither could it.

As it turns out I can play cds ok using the KDE1 Kscd player. The KDE2 Kscd player is broken. When I wouldn't play I looked at the /dev/cdrom entry and saw that it was a link to /dev/hdd, which wasn't the way my previous installs of SuSE were set up. I haven't figured out why Grip won't see the CDROM yet.

On Saturday 10 March 2001 07:52, you wrote:

...
My cdrom is ok. The problem arose when I fired Grip to rip some more Motzart and it said it couldn't find my CD. So I fired Kscd<2> and it gave the same message. So, I thought my fstab was messed up and thats when I found the /hdd thing. In 7.0 and prior versions of SuSE my fstab had only /dev/cdrom /cdrom as the device and mount point, and the /dev directory didn't have any link to /hdd. So, I thought SuSE had messed up. On a lark I started trying other cd players. None of them worked except Kscd<1>.

I am going to check their configs and see why then don't see either /dev/cdrom or /hdd.

On Saturday 10 March 2001 05:58, you wrote:

...
Ok, I have heard about desperate, but this has jsut become ridiculous.....

Try: ln -s /dev/hdd /dev/cdrom

now start kscd, xmcd or some other CD playing application. And.. enjoy.

Þann laugardagur 10 mars 2001 06:51 skrifaðir þú:

...
I know! It just shows you how desparate you get when something doesn't work!!! None of my music cd players work! Neither does Grip. In fact, it was Grip's failure to sense my cdrom when I fired it with Motzart in it that clued me to the fact that something was wrong. I next tried to just play the CD using the serveral players. None worked.

...
> Now, my CDROM is indeed the slave of ide1 BUT, NEVER, > before 7.1 has SuSE refered to it as /hdd in the fstab. > I've check my previous copies of fstab and they all > refer to /dev/cdrom (which was NOT a link to hdd).

I would agree that in the past /etc/fstab has referred to /dev/cdrom. However, I'm sure /dev/cdrom has been a link to /dev/hdd (in your case) for a while. For example, my SuSE 6.1 machine has /dev/cdrom as a link, as does my 7.0 installation. Maybe it's just me, but I'm sure it has been that way for a while.

...
...
...
...
...
> The fact remains that while YaST and YaST2 have no > trouble accessing the SuSE CDs, I can't play a music CD > because I can't mount it. I've tried to inmod and > modprove cdu31a, sonycd and cdu535. None work.

These are drivers for special, proprietry, CD-ROM type things.

...
...
...
...
...
> On Saturday 10 March 2001 00:21, you wrote: >> On Friday 09 March 2001 23:52, Jerry Kreps wrote: >> > In SuSE 7.0 what used to be in /etc/fstab was >> > /dev/cdrom /cdrom iso9660 >> > ro,noauto, user, exec 0 0 >> > >> > Here is what SuSE 7.1 put into /etc/fstab for my >> > cdrom: /dev/hdd /cdrom >> > auto ro,noauto,user,exec 0 0 >> > >> > Obviously, my cdrom is not a harddisk so /dev/hdd >> > is not a correct device...

You could always change your /etc/fstab entry to /dev/cdrom /cdrom iso9660 ro,noauto, user, exec 0 0 as before.

Check permissions, etc. as mentioned before, but I'm fairly certain there's some other problem here.

Bye, Chris

Chris Reeves

19:51

New subject: [SLE] Why did you change the CDROM assignment SuSE? SOLVED!

Jerry Kreps wrote:

...

Even though I was a member of the group 'disk', which I thought would give me group rw rights to /dev/hdd, I discovered that I was wrong. Being in the 'disk' group didn't give me rw access. I discovered this by accident when, as root, I was testing out a fresh copy of cdparanoia. It worked! So, I tried the old copy and it worked to! Suddenly, Grip could see the CDROM.

So, Chris, I added a+rw to /dev/hdd and I can use Grip as me. Thanks!

Now I have to go back and see what it is about group priviledges that I don't understand.

That is strange. It should work, as I understand it, but maybe I need to look into it a bit more.

...

Anyone got a pair of functioning neurons they can sell me? My pair seems to have broken down and the replacement factory has shut down too!

Bit short myself. Sorry, but if I let you have one, I'm sure the other would get a bit lonely ;-)

...

On Saturday 10 March 2001 12:02, you wrote:

...
Jerry Kreps wrote:

...
It's rw for the group "disk" and I'm in that group.

Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\

Philipp Thomas

19 Mar 19 Mar

03:38

New subject: [SLE] Why did you change the CDROM assignment SuSE?

* Jerry Kreps (jerrykreps@jlkreps.net) [20010310 16:07]:

...

The KDE2 Kscd player is broken. When I wouldn't play I looked at the /dev/cdrom entry and saw that it was a link to /dev/hdd, which wasn't the way my previous installs of SuSE were set up.

For as far as I remember (and that's SuSE 4.4.3 :), it has *always* been a link pointing to the actual device (like /dev/scdX or /dev/hdX). Philipp -- Penguins shall save the dinosaurs -- Handelsblatt about Linux on S/390

8440

Age (days ago)

8449

Last active (days ago)

List overview

Download

22 comments

9 participants

participants (9)

Anders Johansson
Avi Schwartz
Chris Reeves
Jerry Kreps
Mikke Mattsson
Peter B. Van Campen
Philipp Thomas
Tor Sigurdsson
Álvaro A. Novo