Any Slackerz out there running 2.6.0-test2 having problems with their CDRW?

I'm certain my CDRW is detected and configured properly:

Whenever I try to burn something either with cdrecord in cli, or K3b/gcombust, the drive fails to spin-up and eventually times-out.

I'm guessing this is an issue with the 2.6.0-test2 kernel itself, as I don't have this problem with 2.4.21. This will all eventually be moot point once 2.6 reaches final, but it would just be nice to have full functionality now. Other than that, everything else works!

There could be so many reasons why it doesnt work for you atm. Maybe a wrong Y/N/M option at compile time, maybe not loading a vital modules, maybe a spelling mistake in a config file, maybe not using the correct kernel tools for >2.4 making. Have you searched online for other mentions of such a problem?

I installed the modutils and module-init packages for the 2.6 kernel from Linuxpackages, compiled the kernel first as monolithic, then as modular, but nothing seemed to get my CDRW to write.

I've searched online, but no reference to problems with CDRWs (perhaps yet).

As I mentioned, everything else works splendid (GF3 w/44.96 dets, SoundBlaster Live! w/alsa, USB MS Intellimouse optical, VIA KT400 chipset).

My 2.6 kernel boots without any error messages, and the system has been stable. The CDRW works fine for everything else except writing.

Hello,

under root account :

What's the output of "cdrecord --scanbus" ?

Never mind. 2.6.0-test3 solved the problem. Now everything INCLUDING the CDRW works perfectly now!

I suggest that anyone having problems with 2.6.0-test series go out and download the 2.6.0-test3 source.