On Tue, 22 Nov 2005 21:45:22 +0100, bobby <noone@nowhere.dk> wrote:

>Dear Loki Harfagr,
>
>The "scsi" option gets my cd audio player working
>again, which it would before. So that is at least
>a small success. I haven't tried burning yet because
>all I get from cdrecord is:
>
> Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
> cdrecord: Warning: Running on Linux-2.6.13
> cdrecord: There are unsettled issues with Linux-2.5 and newer.
> cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.

Oh my... Jörg Schilling spat the dummy last year (?) and is still
bleeding, there's a different way to burn CDs. I think you need to
be root now. (I run a mixed system, create .iso in slack, burn with
Nero on winxp over localnet, not burn 'em under slack, yet).

Grant.

bobby wrote:

> Jeg ha ikke proevet skriver i nu, men CD spiler virker ikke uden options.

Could you be a bit more specific, "doesn't work" is probably the worst place
to start helping you.
--
Thomas O.

This area is designed to become quite warm during normal operation.

Le Tue, 22 Nov 2005 21:45:22 +0100, bobby a écrit*:

> Dear Loki Harfagr,
>
> The "scsi" option gets my cd audio player working
> again, which it would before. So that is at least
> a small success. I haven't tried burning yet because
> all I get from cdrecord is:
>
> Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 Jörg Schilling
> cdrecord: Warning: Running on Linux-2.6.13
> cdrecord: There are unsettled issues with Linux-2.5 and newer.
> cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
>
> So we run from one problem into the next. I guess
> that I'll have to check up on new versions of this
> program.

Well, did you run into a problem yet ?
The warning in cdrecord is an old stuff imprinted from the time
Jörg got very angry at the stubborness of some people in the lkml (and dev)
the only trouble I have at the time is with the 12the tree of K3B which
get lost in discovering udev'ices and that's most probably not related.
You'll may have to chmod +s your cdrtools (or sudo them) as the conflict
is in the choice of userspace/kernelspace between the kernel devs and Jörg.

If you have a rewritable CD you can make some tests to check if you have
a problem.
Something like :
# cdrecord blank=fast dev=/dev/hdc

should tell you about what's remaining to solve :-)

You may also try this test :
----------------
# cdrdao scanbus
Cdrdao version 1.1.9 - (C) Andreas Mueller <andreas@daneb.de>
SCSI interface library - (C) Joerg Schilling
....
ATA:1,0,0 MATSHITA, UJDA730 DVD/CDRW, 1.00
----------------

Then you would now test :
# cdrecord blank=fast dev=ATA:1,0,0

(according to the listing from cdrdao scanbus!)

> Merci,
> Jan

Jeg kan ikke snakke Nork mais c'est gentil d'avoir
écrit "Merci" en français ;-)

Hi everybody,

I've been away for a while because I played too
much with my 2.6.13 kernel installation. Somehow
I messed up the MBR of my harddisk (I know that
they always worn against installing lilo on the
MBR, now I know why). After finding the time to
start all over again with the installation, I
think that found the actual problem.

Both my CD devices had their jumpers set to
"master". This never gave me problems before, but,
now the "SETUP" program on the installation disk
thought it found the slackware disk in the other
drive than it actaully was. Trying again it found
the right drive. Don't ask me how it works. Manual
selection worked perfectly of course.

Anyway, the way I did it now (in case anybody
wants to know):

I made the system dual boot with the 2.4.31
kernel on another partition than the 2.6.13
kernel.

I gave the "hdc=ide-scsi hdd=ide-scsi"
options for the old kernel and the "hdc=scsi
hdd=scsi" options for the new.

Everything seems to be operating to normally now.
The drives are accessible as "/dev/sr0" and
"/dev/sr1", as I expected.

All people who reacted, thanks again. I learned
a bit more linux stuff and that is always useful.

Jan

On 2005-11-27, bobby <noone@nowhere.dk> wrote:
> Hi everybody,
>

Hi

<snip>
> I gave the "hdc=ide-scsi hdd=ide-scsi"
> options for the old kernel and the "hdc=scsi
> hdd=scsi" options for the new.
>
> Everything seems to be operating to normally now.
> The drives are accessible as "/dev/sr0" and
> "/dev/sr1", as I expected.
>
> All people who reacted, thanks again. I learned
> a bit more linux stuff and that is always useful.
>
> Jan

You do not need any appends in lilo to use your burners with a 2.6.x kernel.
just access then via their device node.


--
Best Regards,

Mike Reynolds