Hi,

This is actually a combo drive it has DVD read only and it has CDR/W

It always worked fine in both Slack 10.2 and Slack current with 2.4
kernel. With 2.4 kernel in /etc/lilo.conf I ran: append="hdd=ide-scsi"

I think it was /dev/sr0 with 2.4 kernel.

I removed that append="hdd=ide-scsi line from lilo.conf for 2.6 kernel
and ran /sbin/lilo

Now in Slackware-current it acted up with the testing kernel 2.6.16.9 but
then I got it working by changed the /dev/cdrom link and/.or edited /etc/fstab

upgradepkg the testing kernel to the recent 2.6.16.16 now runs super.

But the mentioned CDR/W combo unit now does not work once again.

I don't know where to look now. Hopefully someone knows more than I and can
share. Here's the error and dmesg:

root@AB60R:~# !222
mount -t iso9660 /dev/cdrom /mnt/cdrom
mount: block device /dev/cdrom is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@AB60R:~# !240
mount -t iso9660 /dev/hdd /mnt/cdrom
mount: block device /dev/hdd is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

root@AB60R:~# dmesg | tail
cdrom: hdd: mrw address space DMA selected
attempt to access beyond end of device
hdd: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=hdd, iso_blknum=16, block=16
cdrom: hdd: mrw address space DMA selected
attempt to access beyond end of device
hdd: rw=0, want=68, limit=4
isofs_fill_super: bread failed, dev=hdd, iso_blknum=16, block=16
root@AB60R:~#

--
abc alan_cu

Alan_C <mtbr0228AT@sbcglobalDOT.net> writes:

> Hi,
>
> This is actually a combo drive it has DVD read only and it has CDR/W

[ . . ]
> upgradepkg the testing kernel to the recent 2.6.16.16 now runs super.
>
> But the mentioned CDR/W combo unit now does not work once again.

Doh! It appears that I got ahold of a bad CD disk.

Inserted a known good cd disk and it works fine.

Burned a cd and it works fine. (though a caution came up from I guess
cdrecord about the 2.6 kernel) I wonder if this is all ironed out
nowadays, cdrecord versus 2.6 kernel?

Inserted the same cd disk that previously had error brings the same error.

--
abc alan_cu

On Tue, 16 May 2006 05:18:56 +0000, Alan_C wrote:

>> But the mentioned CDR/W combo unit now does not work once again.

> Doh! It appears that I got ahold of a bad CD disk.

> Inserted a known good cd disk and it works fine.

> Burned a cd and it works fine. (though a caution came up from I guess
> cdrecord about the 2.6 kernel) I wonder if this is all ironed out
> nowadays, cdrecord versus 2.6 kernel?

Yeah it is. One think you don't have to use scsi-emulation with 2.6
kernels.

With 10.2 I'd go to linuxpackages.net - Search on the term dvd...

You'll get about 6-8 hits. Some aren't included and are necessary for
burning DVD's.

As far as k3b goes you can always check what is needed by drilling
down into the kde menus...

k3b > Settings > Configure > Programs

That should be enough for you to iron out the niggles.

Now myself I almost always compile k3b from source. Yes there have been
buggy versions of k3b and cdrecord both. Before I do a compile I always do
a backup and grab latest versions of cdrecord, etc

I've been using k3b for years and years - Before Pat included it and
before it was widely known. While I've had problems a time or two with
the precompiled binary, the compiled version works smooth as silk with
maybe exceptions 1-2 times out of 20.