Using cdrecord on 2.6.9

[Tim Wunder]

On Friday 22 October 2004 11:04 pm, someone claiming to be Kurt Wall wrote:
> On Fri, Oct 22, 2004 at 10:52:18PM -0400, Tim Wunder took 44 lines to write:
> > On Friday 22 October 2004 10:34 pm, someone claiming to be Kurt Wall 
wrote:
> > > Okay, how the heck do I use cdrecord on kernel 2.6.9? I know that
> > > "hdd=ide-scsi" has gone away in the 2.6 kernel, replaced by "hdd=scsi".
> > > The kernel at least saw this boot param, as this snippet from dmesg
> > > shows:
>
> [le snip]
>
> > Damn! Never mind that "--scanbus" comment. Aparently it makes no
> > difference with cdrecord.
>
> No problem.
>
> > What's the output of lsmod|grep scsi?
> > Mine's:
> > # lsmod|grep scsi
> > scsi_mod              105361  2 sr_mod,sg
>
> # lsmod | egrep scsi
> scsi_mod               83776  2 sr_mod,sg
>
> > #cdrecord -scanbus (and --scanbus) works fine for me. But I'm on kernel
> > 2.6.7
>
> I'll build the drivers into the kernel and see if that fixes things.
>
> Thanks for the help.

NP
But I doubt I helped...

FWIW, hdb=scsi does not appear as a boot parameter in my grub.conf (aka 
menu.lst). Using a pre-built FC2 kernel, so I doubt any drivers were built 
into the kernel.

I no longer use cdrecord proper, but the K3B GUI. K3B identifies my CD writing 
device as /dev/hdb. 
cdrdao version: 1.1.8
cdrecord version: 2.1a34

dmesg no longer provides anything helpful...

CD burning has always just worked for me <shrug>...burned the 4 FC3Test3 CD's 
the other night with no problems.

Tim

-- 
Fedora Core 2, Kernel 2.6.7-1.494.2.2,  KDE 3.3.1, Xorg 6.7.0
 23:00:01 up 23 days,  1:42, 20 users,  load average: 0.04, 0.18, 0.18
It's what you learn after you know it all that counts