According to Christoph Hammann: While burning my CPU.
>
> Hello Richard,
> Thanks for answering so promptly. I followed your suggestion and here is
> my dmesg, see attachment.
> Does this mean I have a faulty drive or can it be amended?
> It would be very kind of you to help,again.
>
>
> --
>
> See you,
>
> Christoph Hammann
>
> #########################################################
> # (-; too freaking busy feigning computer literacy ;-) #
> #######################################################
>
>
>
> G4KLX/GW4PTS AX.25 for Linux. Version 0.35 for Linux NET3.035 (Linux 2.0)
> G4KLX NET/ROM for Linux. Version 0.6 for AX25.035 Linux 2.0
^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you a radio Ham ??? You have the protocols compiled.
> Partition check:
> hda: hda1 hda2 hda3 hda4
> hdb:hdb: set_multmode: status=0x51 { DriveReady SeekComplete Error }
> hdb: set_multmode: error=0x04 { DriveStatusError }
> hdb1 hdb2 hdb3
Well i have the same type of H/D like you a ST34321A, 4103MB w/128kB Cache,
Now the BIG differance is the geometry mine is, CHS=8894/15/63
What i think you have done is let your BIOS "auto detect" it, you need to
set it as LBA, the geometry linux detects is the same as described on the
cover of the H/D. Read the part about the jumper setting for "only detect a
certain amount of the drive" that maybe set wrong also.
I have the same error messages from my disk about set_multimode, as it is my
secondary device and is not yet in full use, i dont know how to rectify it,
i have been to lazy to RTFM, however i have booted from it, installed Redhat
5.1, Suse-5.1 slackware 3.5 and they all install (without a hick) and boot
ok and further more it does what i want it to do.
--
Regards Richard.
[EMAIL PROTECTED]
