-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 31 December 2002 12:37, Carlos E. R. wrote:

Search for "scsi" in the sdb; the first article is titled "Multiple Detection of IDE CD-Recorder". Carlos: Thanks that seemed to clear up the multiple devices, but I think I may still have a small problem . See the 4th line down in my startup log and the errors in the System log. Are these a problem or not.

Start up log: <6>Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak. <4>ide-floppy driver 0.99.newide <6>SCSI subsystem driver Revision: 1.00 <3>kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 <6>md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. <6>NET4: Linux TCP/IP 1.0 for NET4.0 <6>IP Protocols: ICMP, UDP, TCP, IGMP <6>IP: routing cache hash table of 4096 buckets, 32Kbytes <6>TCP: Hash tables configured (established 32768 bind 65536) <6>Linux IP multicast router 0.06 plus PIM-SM <6>NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. <5>RAMDISK: Compressed image found at block 0 <6>Freeing initrd memory: 247k freed <4>VFS: Mounted root (ext2 filesystem). <4>hdc: no flushcache support <4>hdd: no flushcache support <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: TOSHIBA Model: DVD-ROM SD-M1612 Rev: 1004 <4> Type: CD-ROM ANSI SCSI revision: 02 <4> Vendor: LITE-ON Model: LTR-16101B Rev: TS0N <4> Type: CD-ROM ANSI SCSI revision: 02 <7>sd_attach() <7>sd_attach() <4>reiserfs: found format "3.6" with standard journal System log: Dec 31 17:54:40 linux su: pam_unix2: session started for user root, service su Dec 31 17:54:44 linux kernel: cdrom: open failed. Dec 31 17:54:44 linux kernel: cdrom: open failed. Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 64 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 66 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 68 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 70 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 72 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 74 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 76 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 78 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 64 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 66 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 68 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 70 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 72 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 74 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 76 Dec 31 17:54:44 linux kernel: ide-scsi: hdc: unsupported command in request queue (0) Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:00 (hdc), sector 78 Dec 31 17:54:44 linux kernel: cdrom: open failed. - -- Yours, Ralph. It said Use Windows XP or better, so I installed SuSE-Linux 8.1 Register Linux User 168814 ICQ #49993234 AIM ralphdewitt jabber.org ralphdewitt GPG Public Key available at http://www.keyserver.net Key id = 3097 3BC4 Kernel version 2.4.19-4GB Current Linux uptime: 12 days 2 hours minutes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+Ek6wmmsm1DCXO8QRAm5hAKCj99ZMhxdS/KsBkMv5PsK3U+PviQCeLEQF d12UuvGd7eNlDOzDJvpPgYU= =dmWZ -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 01 January 2003 18:20, Carlos E. R. wrote:

This is different...

...

Dec 31 17:54:44 linux kernel: end_request: I/O error, dev 16:40 (hdd), sector 64 Dec 31 17:54:44 linux kernel: ide-scsi: hdd: unsupported command in request queue (0)

Is there a cdrom in the hdd unit? Try a different one, a comercial one containing data (not music); for example, one of the suse cds. I assume hdd is the cdrom or recorder unit, the one you use ide-scsi for.

Beats me... Carlos: No there is nothing in the any of the devices. They are both empty.

Yours, Ralph. It said Use Windows XP or better, so I installed SuSE-Linux 8.1 Register Linux User 168814 ICQ #49993234 AIM ralphdewitt jabber.org ralphdewitt GPG Public Key available at http://www.keyserver.net Key id = 3097 3BC4 Kernel version 2.4.19-4GB Current Linux uptime: 1 days 3 hours 54 minutes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+E9KWmmsm1DCXO8QRAlMfAKCyShReV0Bu9FtYei1Kthjk07hntgCgo+Ln AtWwswwjJE1uhjFvsybHIDI= =0Q0S -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 02 January 2003 12:46, Carlos E. R. wrote:

Ahhh! Then, ignore it. Some program, perhaps the kde desktop is trying to foolishly mount the cdrom. If you can later put a CD and read it, just ignore that error msg :-) Carlos: Thanks very much for your help.

Yours, Ralph. It said Use Windows XP or better, so I installed SuSE-Linux 8.1 Register Linux User 168814 ICQ #49993234 AIM ralphdewitt jabber.org ralphdewitt GPG Public Key available at http://www.keyserver.net Key id = 3097 3BC4 Kernel version 2.4.19-4GB Current Linux uptime: 1 days 23 hours 34 minutes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+FOb8mmsm1DCXO8QRAuZVAKCcUt0+3h6kEU/IpfNfekEnPfNLbQCfZ01f tAJKoQaj56uOOYclIOSdguI= =uR8S -----END PGP SIGNATURE-----

At 03-01-03, Ralph De Witt wrote:

...

Carlos: Thanks very much for your help. Carlos: I have done some more looking and have found that I can not play cd's with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 02 January 2003 17:27, Ralph De Witt wrote: the DVD, and cannot get to the cdrw. In Grub on the kernnel line I have only hdd=ide-scsi listed. My dvd, and cdrw are both ide drives. In the hardware info area of yast2, the DVD is listed as /dev/sr0, and the CDRW is listed as /dev/sr1 this in the CDROM section. The above is repeated in the SCSI section. My Desktop DVD icon is pointed to /dev/cdreacorder, and the Desktop CD-R icon is pointed to /dev/cdrom. In my /dev directory I see links for cdrom, cdrom1, cdrecorder, and dvd devices, but lack the skill to find out what they point to. In the media directory I have cdrom, cdrom1,cdrecorder, and dvd subdirectories. Can you help me sort this all out. Hopefully if we can get the links to the right devices and any extra removed then it will all work. Looks like the install went worst then the multiple repeats of the devices we fixed. This is possible the cause of the other errors I was seeing.

Ralph, 1st: If hdd is your DVD then there must be another hd.. for your CDRW (or vice versa). In the kernel line you must list both devices; so hdd=ide-scsi AND hd?=ide-scsi (you have to find out the correct "letter" for "?") Because of the ide-scsi emulation these two drive-id's will be changed into sr0 and sr1. 2nd : Your /dev/cdrom , /dev/cdrom1, /dev/cdrecorder and /dev/dvd must point to the correct "device entry" in /dev. You must use the command : ln -sf /dev/xxx /dev/yyy, where xxx is the physical device assignment and yyy the logical device name. E.g. to link /dev/cdrom to sr1, the command should be : ln -sf /dev/sr1 /dev/cdrom When you take a look in /dev, the entry for cdrom should then look like : cdrom 0 B Mime type 2001-09-24 03.54 rw------- root root /dev/sr1 This must be done for all devices that you need to use. By the way, have you looked at the instructions in SuSE's Support Database article "IDE CD Writer" ? I found that very helpful, but there is one error in that article; they refer to /dev/sdc0 where you should read /dev/sr0 Success. ------------------------------ Jan Elders Nuenen the Netherlands

On Saturday 04 January 2003 6:21 am, Carlos E. R. wrote:

...

CD-R icon is pointed to /dev/cdrom. In my /dev directory I see links for cdrom, cdrom1, cdrecorder, and dvd devices, but lack the skill to find out what they point to. In the media directory I have cdrom, cdrom1,cdrecorder, and dvd subdirectories. Can you help me sort this all out. Hopefully if we

Hi, If you use KDE and Konqueror to look at files, finding out what the links link to is easy. Merely place your cursor over the link -don't click it- and then look down at the bottom of the Konqi window and you will see something like the folloiwng: cdrom->/dev/sr1 If you have placed the cursor over a device driver you will see something like: cbm Character Device If the file is a text file you will see something like: ncsd.conf(1.4KB) Plain Text Wave your cursor around and see what it gets you. HTH, RA

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday 04 January 2003 04:21, Carlos E. R. wrote:

The 03.01.03 at 02:48, Ralph De Witt wrote:

...

Carlos: I have done some more looking and have found that I can not play cd's with the DVD, and cannot get to the cdrw. In Grub on the kernnel line I have only hdd=ide-scsi listed. My dvd, and cdrw are both ide drives. In the hardware info area of yast2, the DVD is listed as /dev/sr0, and the CDRW is listed as /dev/sr1 this in the CDROM section. The above is repeated in the SCSI section. My Desktop DVD icon is pointed to /dev/cdreacorder, and the Desktop CD-R icon is pointed to /dev/cdrom. In my /dev directory I see links for cdrom, cdrom1, cdrecorder, and dvd devices, but lack the skill to find out what they point to. In the media directory I have cdrom, cdrom1,cdrecorder, and dvd subdirectories. Can you help me sort this all out. Hopefully if we can get the links to the right devices and any extra removed then it will all work. Looks like the install went worst then the multiple repeats of the devices we fixed. This is possible the cause of the other errors I was seeing.

Ok, I don't know about the automatics, but I do know about the "manual" way. First, browse your boot file ("less /var/log/boot.msg"). Note the line "Kernel command line", something like this:

<4>Kernel command line: root=/dev/hdb6 hdc=ide-scsi hdd=ide-scsi vga=791 <4>ide_setup: hdc=ide-scsi <4>ide_setup: hdd=ide-scsi

<4>Kernel command line: root=/dev/hda1 hdd=ide-scsi max_scsi_luns=1 vga=791 <4>ide_setup: hdd=ide-scsi <6>Initializing CPU#0

This will confirm what parameters we actually pass to the kernel. Later, comes the HD detection, something like this:

<4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <4>ICH2: IDE controller on PCI bus 00 dev f9 <4>ICH2: chipset revision 18 <4>ICH2: not 100%% native mode: will probe irqs later <4> ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA <4> ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA <4>hda: ST360020A, ATA DISK drive <4>hdb: ST340810A, ATA DISK drive <4>hdc: IDE DVD-ROM 16X, ATAPI CD/DVD-ROM drive <4>hdd: CR-48X8TE, ATAPI CD/DVD-ROM drive

<6>Uniform Multi-Platform E-IDE driver Revision: 6.31 <4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <4>VP_IDE: IDE controller on PCI bus 00 dev 89 <6>PCI: Hardcoded IRQ 14 for device 00:11.1 <4>VP_IDE: chipset revision 6 <4>VP_IDE: not 100%% native mode: will probe irqs later <4>VP_IDE: Unknown VIA SouthBridge, contact Vojtech Pavlik <4>hda: MAXTOR 4K080H4, ATA DISK drive <4>hdc: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive <4>hdd: LITE-ON LTR-16101B, ATAPI CD/DVD-ROM drive

So, in my case, this confirms that my DVD is phisically hdc, and the cdwriter is hdd. But, as I configured ide-scsi for both (as confirmed by the kernel parameter lines above), I find the scsi emulation further down on that log file:

<4>hdc: no flushcache support <4>hdd: no flushcache support <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: IDE Model: DVD-ROM 16X Rev: 1.06 <4> Type: CD-ROM ANSI SCSI revision: 02 <4> Vendor: MITSUMI Model: CR-48X8TE Rev: 1.1E <4> Type: CD-ROM ANSI SCSI revision: 02 <7>sd_attach() <7>sd_attach()

<4>hdc: no flushcache support <4>hdd: no flushcache support <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: TOSHIBA Model: DVD-ROM SD-M1612 Rev: 1004 <4> Type: CD-ROM ANSI SCSI revision: 02 <4> Vendor: LITE-ON Model: LTR-16101B Rev: TS0N <4> Type: CD-ROM ANSI SCSI revision: 02 <7>sd_attach() <7>sd_attach()

So, I have confirmation that both drives are using ide-scsi emulation. In fact, the only one that needs it is the recorder; but if you want to make cd - cd copies, the reader has to use ide-scsi as well. At least, xcdroast complained. However, you could set the dvd as a normal ide device instead. I'll assume ide-scsi for both.

Now, try to run "scan_scsi.linux" (package "cdda2wav"):

nimrodel:~ # scan_scsi.linux Host: scsi0 Channel: 00 Id: 00 Lun: 00 CD-ROM -> /dev/sg0 Host: scsi0 Channel: 00 Id: 01 Lun: 00 CD-ROM -> /dev/sg1

/dev/sg0 is the hdc (DVD) /dev/sg1 is hdd (cdwriter)

linux:/home/ralph # scan_scsi.linux Host: scsi0 Channel: 00 Id: 00 Lun: 00 CD-ROM -> /dev/sg0 Host: scsi0 Channel: 00 Id: 01 Lun: 00 CD-ROM -> /dev/sg1 linux:/home/ralph #

So... what links should we make? I have these:

cdrecorder -> scd1 cdrom -> scd1 dvd -> scd0

Ok so far. I am going to stop the process here for now. If I am correct in reading the stuff from my system the only parameter I have passed to the kernel is hdd=ide_scsi (this is my cd-rw), yet it is telling me that both hdc (which is my dvd) and hdd (which is my cd-rw) are being scsi emulated. Is this correct? Now when I look in /dev is see links for cdrom, cdrom1, cdrecorder, and dvd. But I do not have sufficent knowledge to know what they are pointing. Should these links be deleted? I also have 4 directories in /media. cdrom, cdrom1, cdrecorder, and dvd. I feel/think that cdrom1 was some how created in error. Should that one be deleted? Now when we create the links is dvd and cdrom linked to the dvd hdc, and cdrecorder linked only to sr0? Before we do any linking how do we get hdc to be just ide, and not scsi emulated. (I have no need to do cd to cd-rw copying at this time.

(use the command "ls -l /dev/cdr*" and "ls -l /dev/dvd*"). If you don't feel confortable with the comand line, use mc (Midnight Comander) on a text console or terminal: it is similar to the old Norton Comander for MsDos and quite powerfull. Under the "File" menu you can create or edit symlinks (don't use hardlinks, ie, plain links, they are more difficult to keep track off).

Note: scd0 is equivalent to sr0, which is to be deprecated, the docs say. I have a doubt about the recorder, I'll have to test something.

Now, permissions... in order to write CDs, you will need write permissions. But, desktops like gnome or kde change these everytime you log in.

Cd sound. Well... the gnome player insists on using the cdrom, even if I change it to dvd. Too bad. Neither does kscd, complains of permissions.

:-? Ok, I have:

nimrodel:/dev # l scd0 brw-r----- 1 root disk 11, 0 Sep 9 22:24 scd0

Mmm... my normal user doesn't belong to group disk, so for a quick change I'll change it to:

brw-rw---- 1 root audio 11, 0 Sep 9 22:24 scd0

Now, the gnome app keeps complaining, but not kscd. Good! I have J.S. Bach "Chromatische Fantasie & Fuge" playing from the DVD set as ide-scsi :-)

Just an idea: there has to be an internal audio cable conected from the dvd to the sound device for play back; some installers neglect to put it.

Audio cable is hooked up.

I hope the above is not too confusing, I feel a bit sleepy today :-)

I am getting tired and yes I have gotten somewhat confused, but things are also a little clearer, I made comments in the middle of things along with all the questions I could think of. Hope I do not confuse you too much. - -- Yours, Ralph. It said Use Windows XP or better, so I installed SuSE-Linux 8.1 Register Linux User 168814 ICQ #49993234 AIM ralphdewitt jabber.org ralphdewitt GPG Public Key available at http://www.keyserver.net Key id = 3097 3BC4 Kernel version 2.4.19-4GB Current Linux uptime: 1 days 3 hours 12 minutes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+FuRCmmsm1DCXO8QRAuO6AJ43HaxGHBW1W9mHf/mjoXinTY7rBQCfZ/mJ QFpKRlx9BHAf/j+QLjExjIs= =GoUh -----END PGP SIGNATURE-----

The 03.01.04 at 05:40, Ralph De Witt wrote:

<4>Kernel command line: root=/dev/hda1 hdd=ide-scsi max_scsi_luns=1 vga=791 <4>ide_setup: hdd=ide-scsi <6>Initializing CPU#0

<6>Uniform Multi-Platform E-IDE driver Revision: 6.31 <4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <4>VP_IDE: IDE controller on PCI bus 00 dev 89 <6>PCI: Hardcoded IRQ 14 for device 00:11.1 <4>VP_IDE: chipset revision 6 <4>VP_IDE: not 100%% native mode: will probe irqs later <4>VP_IDE: Unknown VIA SouthBridge, contact Vojtech Pavlik <4>hda: MAXTOR 4K080H4, ATA DISK drive <4>hdc: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive <4>hdd: LITE-ON LTR-16101B, ATAPI CD/DVD-ROM drive

<4>hdc: no flushcache support <4>hdd: no flushcache support <6>scsi0 : SCSI host adapter emulation for IDE ATAPI devices <4> Vendor: TOSHIBA Model: DVD-ROM SD-M1612 Rev: 1004 <4> Type: CD-ROM ANSI SCSI revision: 02 <4> Vendor: LITE-ON Model: LTR-16101B Rev: TS0N <4> Type: CD-ROM ANSI SCSI revision: 02 <7>sd_attach() <7>sd_attach()

linux:/home/ralph # scan_scsi.linux Host: scsi0 Channel: 00 Id: 00 Lun: 00 CD-ROM -> /dev/sg0 Host: scsi0 Channel: 00 Id: 01 Lun: 00 CD-ROM -> /dev/sg1 linux:/home/ralph #

Ok so far. I am going to stop the process here for now. If I am correct in reading the stuff from my system the only parameter I have passed to the kernel is hdd=ide_scsi (this is my cd-rw), yet it is telling me that both hdc (which is my dvd) and hdd (which is my cd-rw) are being scsi emulated. Is this correct?

Yes. It suprises me, but yes, you are getting scsi emulation for both devices.

Now when I look in /dev is see links for cdrom, cdrom1, cdrecorder, and dvd. But I do not have sufficent knowledge to know what they are pointing. Should these links be deleted?

Er... no. I see you know already, Richard told you how; you have: | My links are: | dvd->hdc Block Device (Link) | cdrom->sr1 Block Device (Link) | cdrom1->sr0 Block Device (Link) | cdrecorder->sr0 Block Device (Link) The comand line way is simply "ls -l /dev/cdr* /dev/dvd". In my case, the output is: cer@nimrodel:~> ls -l /dev/cdr* /dev/dvd lrwxrwxrwx 1 root root 4 2003-01-04 12:46 /dev/cdrecorder -> scd1 lrwxrwxrwx 1 root root 4 2002-11-07 19:37 /dev/cdrom -> scd1 lrwxrwxrwx 1 root root 4 2003-01-04 12:49 /dev/dvd -> scd0

I also have 4 directories in /media. cdrom, cdrom1, cdrecorder, and dvd. I feel/think that cdrom1 was some how created in error. Should that one be deleted?

You could if you like, or you could leave it. Let me see... I'd sugest you: 1) Change the "cdrecorder" link to "sr1", as I understand that the writer is the second device. 2) You may leave the "cdrom" and "cdrom1" links. The first one is the writer unit, the second one is the dvd by another name. Try them, they should work. 3) Change the "dvd" link to "sr0". Alternatively, convince the kernel not to use emulation for that unit... but, for the moment, I don't know how O:-) - and anyway, it might be easier not to. Now, how do you change the links? Well... I suppose konkeror should be able to do it, but I don't like to start an X session as root. Anyway, I normally use gnome, and as I tried konqeror right now to see if it could edit links, it crashed. So... you might use mc on a terminal, as I mentioned the other day, or the comand line: use whichever makes you feel more confortable. The last would be like this (as root): cd /dev rm dvd (delete file or link) ln -s sr0 dvd (create symbolic link) rm cdrecorder ln -s sr1 cdrecorder

Now when we create the links is dvd and cdrom linked to the dvd hdc, and cdrecorder linked only to sr0?

Er... I got a bit lost here :-) The links are just a trick to access the real devices (sr0, hdc or whatever) with names that are meaningfull to us. In the rest of the system everything else refers to "/dev/cdrom" instead of the real device where it is; this way, if we decide to use it as hdc or as sr0 we need only to change the link and it will work everywere.

Before we do any linking how do we get hdc to be just ide, and not scsi emulated. (I have no need to do cd to cd-rw copying at this time.

True... but if it works, don't touch it O:-) I mean, the kernel seems to want it that way, and I feel your system was configured that way, except that it got it a bit bad. You'd end with yast not working, because it remembers that before the dvd was sr0... (it can be corrected, of course). And anyway, the real reason is, I don't know how to convince your kernel O:-) it shouldn't be doing it that way (by the parameters you pass it).

...

Audio cable is hooked up.

...

I hope the above is not too confusing, I feel a bit sleepy today :-)

I am getting tired and yes I have gotten somewhat confused, but things are also a little clearer, I made comments in the middle of things along with all the questions I could think of. Hope I do not confuse you too much.

The thing is that you need, as user, access to the cdrom device in order to play a music CD. Normally the device will have read/write permission only for root (or not, depending on an automatism I don't fully understand). If you can't play a CD on the dvd, after doing the above corrections, check the permissions on /dev/sr0 -- Cheers, Carlos Robinson

The 03.01.04 at 19:15, Ralph De Witt wrote:

On Saturday 04 January 2003 17:47, Carlos E. R. wrote:

...

You could if you like, or you could leave it. Let me see... I'd sugest you: Decided not to fight it any more added the hdc=ide-scsi to the kernel line in grub

I thought it would be easier... So, now you have: cdrecorder --> sr1 cdrom --> sr1 cdrom1 --> sr0 dvd --> sr0

changed the dvd link to sr0 also changed the desktop icon for dvd to point to /dev/dvd, and the cd-r icon to point to /dev/cdrecorder.

Ok, that way if you sometime in the future change the devs links, the desktop will need no change.

...

The thing is that you need, as user, access to the cdrom device in order to play a music CD. Normally the device will have read/write permission only for root (or not, depending on an automatism I don't fully understand). If you can't play a CD on the dvd, after doing the above corrections, check the permissions on /dev/sr0 tried to play audio cd using kscd nothing happened got this in console:

ralph@linux:~> kscd CDTEXT INFO: use GET_FEATURY_LIST(0x46)... CDTEXT ERROR: GET_FEATURY_LIST(0x46) not implemented or broken. ret = -1! CDTEXT INFO: GET_FEATURY_LIST(0x46) ignored. It's OK, becose many CDROMS don't implement this featury CDTEXT INFO: try to read, how long CDTEXT is? CDTEXT ERROR: READ_TOC(0x43) with format code 0x05 not implemented or broken. ret = -1! CDTEXT INFO: free_cdtext_info() called ralph@linux:~>

Let me compare with mine; I get: cer@nimrodel:~> kscd & [1] 536 cer@nimrodel:~> DCOPServer up and running. CDTEXT INFO: use GET_FEATURY_LIST(0x46)... CDTEXT INFO: try to read, how long CDTEXT is? CDTEXT INFO: CDTEXT is a 7 byte(s) long CDTEXT INFO: try to read CDTEXT CDTEXT INFO: read 7 byte(s) of CDTEXT CDTEXT INFO: free_cdtext_info() called CDTEXT ERROR: invalid packet at 0x00000000: 0x 00 00 00 08 20 00 6D 00 B0 F3 14 08 C9 00 00 00 94 CF The error I get is different, but it works. It seems you get more errors :-(

permissions for sr0, and sr1 is set to -rw------- the user is set to my user name (ralph) and the group is set to disk. Hope this helps a little bit more.

Yes, that is correct. You know that you can change in kscd the device used por playing, so you can use the cdrecorder and check if that one works. If that is so, we have half the thing working: it might be that you dvd can not play music. Mine, for example, can not read data cds. I think I read some thing about your IRQs mentioned on another mail... I'll check. | <6>Real Time Clock Driver v1.10e | <6>Uniform Multi-Platform E-IDE driver Revision: 6.31 | <4>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx | <4>VP_IDE: IDE controller on PCI bus 00 dev 89 | <6>PCI: Hardcoded IRQ 14 for device 00:11.1 Ah, this. "Harcoded", why? In the mother board? By the Bios? :-? | <4>VP_IDE: chipset revision 6 | <4>VP_IDE: not 100%% native mode: will probe irqs later | <4>VP_IDE: Unknown VIA SouthBridge, contact Vojtech Pavlik Something here, but I don't know what it means exactly. I think I had that some time ago. | <4>hda: MAXTOR 4K080H4, ATA DISK drive | <4>hdc: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive | <4>hdd: LITE-ON LTR-16101B, ATAPI CD/DVD-ROM drive | <4>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 | <4>ide0: probed IRQ 14 failed, using default. | <4>ide1 at 0x170-0x177,0x376 on irq 15 And this, the probing for the IDE irq fails, so it assumes that it is standard. I could be a fault of the driver, or maybe not. Did you tune your bios settings? You could perhaps set them at "default safe settings" or something like that, to see if it solve anything. Maybe not, so if you are bored or in an ivestigative mood, you could try. But carefully :-) There is a saying in telephony, something like "Does the beast work? Then do not even look at it!" X-) -- Cheers, Carlos Robinson

The 03.01.05 at 19:18, Ralph De Witt wrote:

On Sunday 05 January 2003 12:36, Carlos E. R. wrote:

...

Yes, that is correct. You know that you can change in kscd the device used por playing, so you can use the cdrecorder and check if that one works. If that is so, we have half the thing working: it might be that you dvd can not play music. Mine, for example, can not read data cds Carlos: I have tested the ability to create data cd's with K3B and it works very well, K3B rocks. I tried playing a music cd and that did not work.

Some programs need access to the /dev/sg? device as well, which is not normally allowed for users.

I also have upgraded to the K-athlon 167 kernel that was available on the update site. The only thing bad is that I lost the Nvidia drivers and had to

Everytime to change the kernel you have to update the nvidia kernel driver to match the kernel; it should do recompiling it (/usr/src/kernel-modules/nv_glx/README).

revert to the nv non commercial driver. I did not try installing from source and compiling only tryed the rpm's and that did not work. Thank you for all your hard work, I have learned much thanks to you.

Welcome :-) -- Cheers, Carlos Robinson

The 03.01.05 at 19:20, Ralph De Witt wrote:

I have not changed bios defaults execpt to increase fsb speed to 133 from the default 100 and changing boot options to include the cdrom. Other than those it it a straight default setup of this MOBO.

Perhaps you could try going back to 100 and thus see if the errors dissapear... just to know it helps or not. -- Cheers, Carlos Robinson