David Elliott wrote:
> Well, I have it hacked well enough that I can use the drive now.
>
> I can tell you right now that it's not the drive that's preventing you
> from accessing past the LBA capacity, it's Linux. Somewhere in the
> kernel there is a check to make sure you don't try to access sectors
> past the capacity of the drive. Well, when Linux thinks the capacity
> of the drive is 66055248 instead of 80041248 then you run into
> problems and get tons of IO errors!
>
DAMNIT... Sorry, wrong, the dd crapped ou anyway at 48737112 (IO error),
which if you add the starting partition offset of 17318133 gives you
66055245.
ARGH... I can only theorize that either A) The drive is actually causing
the IO error, or B) Linux is checking lba_capacity somewhere, and we
should fix that variable too.
Right now I am half tempted to disable all drives in the BIOS (so that I
can undo the limits jumper) and make some sort of floppy that can load up
a new BIOS (maybe a slightly hacked version of EZ-BIOS), that will then
be able to boot onto the 40 GB drive. Can anyone say "open source the
BIOS code please so we can fix stupid shit like this!" ??
-Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:12 EST