Kernel 2.4.13pre1 on powerpc. I can no longer mount HFS-formatted cdroms.
The last kernel I'm sure it worked fine is 2.4.7
Oct 20 23:58:51 Jay kernel: ll_rw_block: device 0b:00: only 2048-char blocks
implemented (512)
Oct 20 23:58:51 Jay kernel: hfs_fs: unable to read block 0x00000002 from dev
0b:00
Oct 20 23:58:51 Jay kernel: hfs_fs: Unable to read superblock
Oct 20 23:58:51 Jay kernel: ll_rw_block: device 0b:00: only 2048-char blocks
implemented (512)
Oct 20 23:58:51 Jay kernel: hfs_fs: unable to read block 0x00000000 from dev
0b:00
Oct 20 23:58:51 Jay kernel: hfs_fs: Unable to read block 0.
Bye.
> Kernel 2.4.13pre1 on powerpc. I can no longer mount HFS-formatted cdroms.
> The last kernel I'm sure it worked fine is 2.4.7
Mount it over loopback device. We at some point need to make that bit
transparent.
on 22/10/01 4:44 PM, Alan Cox at [email protected] wrote:
>
>> Kernel 2.4.13pre1 on powerpc. I can no longer mount HFS-formatted cdroms.
>> The last kernel I'm sure it worked fine is 2.4.7
>
> Mount it over loopback device.
Why has that become necessary?
-Hollis
> on 22/10/01 4:44 PM, Alan Cox at [email protected] wrote:
> >
> >> Kernel 2.4.13pre1 on powerpc. I can no longer mount HFS-formatted cdroms.
> >> The last kernel I'm sure it worked fine is 2.4.7
> >
> > Mount it over loopback device.
>
> Why has that become necessary?
Primarily because the glue in the middle isnt covering up for your CD-ROM
any more.
Alan
On Mon, Oct 22, 2001 at 11:51:51PM +0100, Alan Cox wrote:
>
> > on 22/10/01 4:44 PM, Alan Cox at [email protected] wrote:
> > >
> > >> Kernel 2.4.13pre1 on powerpc. I can no longer mount HFS-formatted cdroms.
> > >> The last kernel I'm sure it worked fine is 2.4.7
> > >
> > > Mount it over loopback device.
> >
> > Why has that become necessary?
>
> Primarily because the glue in the middle isnt covering up for your CD-ROM
> any more.
No, really. What's changed to break HFS cdrom support?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
Tom Rini wrote:
> No, really. What's changed to break HFS cdrom support?
Based on the messages and glancing over the hfs code, I would guess
that the CD-ROM block device driver used to fake accessing the drive
at any random block size. The hfs code depends on being able to use
a particular block size (512) and if the driver for the block device
doesn't support it, stuff breaks.
(super.c lines 394-416/491 byte 10778/12361 87%)
/* set the device driver to 512-byte blocks */
set_blocksize(dev, HFS_SECTOR_SIZE);
To be more flexible, the hfs code shouldn't force a hard coded block size.
Brad Boyer
[email protected]