Could someone explain these error messages from FC2 dmesg?

Fri Jul 16 05:34:25 UTC 2004

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

The error messages do not appear when I boot the same hardware with FC1.

<Begin  extract from dmesg>
<snip>
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:07.1
    ide0: BM-DMA at 0xff00-0xff07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xff08-0xff0f, BIOS settings: hdc:DMA, hdd:DMA
hda: ST340810A, ATA DISK drive
hdb: CD-RW IDE2410, ATAPI CD/DVD-ROM drive
Using cfq io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: Maxtor 6Y060L0, ATA DISK drive
hdd: DVD-ROM OEM316B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 hda: hda1 hda2 < hda5 hda6 hda7 > hda3 hda4
hdc: max request size: 128KiB
hdc: 120103200 sectors (61492 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
 hdc: hdc1 hdc2 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 > hdc3 hdc4
hdb: ATAPI 40X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
<snip>
hdb: command error: status=0x51 { DriveReady SeekComplete Error }
hdb: command error: error=0x54
end_request: I/O error, dev hdb, sector 0
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev hdd, sector 1437824
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev hdd, sector 0
<snip>
<End  extract from dmesg>

It would seem that FC2 thinks my cd drives are sick. But I don't get any
errors from actual operation of them. They just don't scan well.

I'd like to mention that in FC1 both the dvd-rom on hdd and the cd-rw on 
hdb=ide-scsi work fine with xcdroast. But for FC2 I found that I could
only burn music cd's with xcdroast.  I also found that trying to boot
the FC2 kernel with "hdb=ide-scsi" was a bad idea...  

Thus I tried k3b, which is able to burn data cd's on it as /dev/hdb.
However, the first time I start k3b after any reboot of FC2 It spends a
ridiculous amount of time scanning the ide drives. And never recognized
the cd-rw until/unless after I attempt to "add" the device /dev/hdb it
spends another long wait and tells me it can't find any device to add. Yet
AFTER I try to add it, the refresh button will make it appear in the "Setup
Devices" screen with the following values:

<snip>
CDWRITER IDE2410
 |-System device name:	/dev/hdb
 |-Interface type:	ATAPI
 |-Vendor:		CDWRITER
 |-Description:		IDE2410
 |-Version:		A23
 |-Writes CDs:		yes
 |-Writes CD/RWs:	yes
 |-Reads DVDs:		no
 |-Writes DVD-R(W)s:	no
 |-Writes DVD+R(W)s:	no
 |-Buffer Size:		2.0 MB
 |-Max write speed:	0
 |-Cdrdao driver:	auto
 |-CD-Text capable:	auto
 |-Supports Burnfree	yes
 |-Write modes:		SAO: TAO: RAW: SAO/R16: RAW/R96P: RAW/R96R
 <SNIP>

Once that happens I can burn CDs with k3b...

I should also mention that data CDs are only supported by this drive in
any of the raw modes. (Which it doesn't like for music CDs?) And that with
xcdroast music CDs burn in DAO mode.

I have burned several iso images with kb3 on FC2 under the above
conditions. In every case I was able to verify that the resulting cd was
a perfect copy, by way of doing a "copy cd" to file only and comparing
the md5sum of both the source iso file and the resulting k3b_0.iso file.
Also there have been zero errors reported during any of the burns.
They just don't scan well under FC2... 

This wouldn't be so bad if I knew how to get k3b to believe it's own
~/.kde/share/config/k3brc file and forgo rescanning the drives.

<snip>
[Devices]
Device1=/dev/hdd,DVD-16X,OEM316B,8400,0,auto,auto
Device2=/dev/hdb,CDWRITER,IDE2410,7000,0,auto,auto
<snip>
[image writing]
burnproof=true
data_track_mode=auto
image type=auto
last written image=$HOME/com/dnlo/testkb3burndata.iso
multisession=false
simulate=false
verify_data=false
writer_device=/dev/hdb
writing_app=Auto
writing_mode=raw
writing_speed=0
<snip>

I'm not even sure what the problem is. I sure don't know how to fix it.
Any/all clues will be appreciated.

- -- 
|      ?           ?		
|			
|        -=-   -=-	 I'm NOT clueless...    	
|        <?>   <?>    	But I just don't know.  	
|            ^          Joe (theWordy) Philbrook           
|           ---  	     J(tWdy)P
|			  <jtwdyp at ttlc.net> 
|      ?           ?		

   ##############################################################
   # You can find my public gpg key at http://pgpkeys.mit.edu/  #
   ##############################################################

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA92gwRZ/61mwhY94RAnn4AJ43isJInGhLGgL0x7lAvvq+9kn8PwCdHGFH
CTpGaIxNbhS3dWho1xyAvt8=
=vK0K
-----END PGP SIGNATURE-----