Could someone explain these error messages from FC2 dmesg?

[Joe(theWordy)Philbrook]

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

Unfortunately booting with CDs (music or data) in the cd drives don't
appear to make any difference... (same errors)

And it also doesn't prevent k3b from refusing to recognize the cd-rw
drive until after it declines to add the device and is then refreshed.

Which it the real annoyance here...

Basically I have wait for the k3b's drivescanning process to time out 3
times in a row...

1) When it fails to recognize the cd-rw on it's start-up scan.
2) When it tries to add /dev/hdb and claims not to find anything to add.

And finally {Only after the step 2 has been attempted will 3) succeed}

3) When {after 2)} a refresh (rescan) will finally find the cd-rw...
   
   
And finally k3b can burn to it's hearts content. Once it believes in
the drive it just plain works...

I had hoped that the dmesg errors would be a clue to how to prevent
k3b's time consuming necessity...

Fact is, If I'm not in the middle of something else, it's quicker to
reboot FC1 or MDK and use XCDROAST with the scsi emulation, then reboot
back into FC2 than it is to get k3b to recognize the dang cd-rw drive.
If FC2's xcdroast didn't fail when ever I selected any of the modes from
which I can write data tracks. I'd probably just give up on k3b...

<sigh>

Well anyway, Thanks for the help.
   

- -- 
|   ---   ___
|   <0>   <->	   Joe (theWordy) Philbrook
|	^		J(tWdy)P
|    ~\___/~	     <<jtwdyp at ttlc.net>>

It would appear that on Jul 17, Joe(theWordy)Philbrook did say:

> 
> It would appear that on Jul 16, Yang Xiao did say:
> 
> > 
> > Hi,
> > try put a cd in the drive and see if you still see the errors during
> > boot, I think it was addressed earlier(can't remember exactly where),
> > that it's smartd trying to check removable media and complains when
> > there's no media in the drive.
> > However, I only saw it when using the packaged kernel 2.6.5-1.358 from
> > FC2, once I upgraded to 435, the error went away.
> > Yang
> 
> Thanks for the advice. Will try that. Perhaps that would also solve the
> problem getting the cd-rw recognized by k3b as well. When I know if it
> makes any difference I'll post an update.
> 
> Thanks
> 


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

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

iD8DBQFA+WD0RZ/61mwhY94RArWmAJ9RiNJ9YzWPkcTGWyoKdU3T4UKAMgCgtU/0
MZE4uGlMGbRdUk+Bu8odP9Q=
=bdtM
-----END PGP SIGNATURE-----