Wookey writes:
> Botting from the floppy is fine and the install goes much as expected
> until the powertec driver is loaded. If the ZIP drive is pluged in it
> gets stuck in a loop going round and round. I can't find the bit of paper
> I wrote the diagnostic details for that one on now, but once I get a
> working system I can fiddle with the powertec driver to work out what the
> problem is....unplugging the drive means things proceed as expected.
I guess that the zip drive is making an illegal SCSI state transition
(most SCSI devices firmware is pretty poor, and it's virtually impossible
to write a driver which will talk to everything if you don't have everything
to test against).
> So, ignoring that glitch we continue and I get to the package selection
> section (stage 6 IIRC). First I get an error 'unable to read header at
> 604440'.
That means that the installer is unable to read one of the package headers
fron the RedHat/RPMS directory. This message is generated by a bit of
over-simplified code - it should tell you the filename if possible.
It sounds like one of the .rpm files is corrupted.
> message it goes back to the select packages to install window, and I am
> stuck going round and round in a loop, never being able to install any
> packages.
Does it say anything on the logging ttys?
> Anyone got any idea why? Sometimes I see errors in one of the virtual
> terminals about 'scsi.h:incomplete transfer detected....' which makes me
> suspicious.
This message is generated when the Linux kernel believes that it should
read x bytes, but the command completed successfully after reading x - n
bytes, where n > 0.
You may argue that this is an error, and I would agree with that - I used
to get corruption on the AcornSCSI interface which was caused by this.
Unfortunately, to tell whether it is a serious message, you've left off
the command information.
Currently, the FAS216 driver (the core of the powertec driver) does not
retry the command (I have found that CDRs don't like that).
> Is the powertec driver not happy and is this preventing the
> installer from installing? Have people sucessfully used this
> driver or shouod I assume it's broken?
It's definitely not seriously broken - the following devices work ok on it:
- Syquest SQ3270S 270MB removable drive
- Maxtor LXT213SY hard drive
- Quantum fireball 1040S hard drive
- Matshita CW7502 CDR
- Toshiba XM3301TA CD ROM drive
> Having got to this stage I could do a manual installation of some basic
> RPMs except that I can't find the rpm program anywhere in the initial
> filesystem. Is it there?
No - it is integrated into the installer itself (so that there is actually
some space left on the disks for one, and so that there is some memory
left in the machine after loading the disks.
> System 2:
> ROS 3.71, 17Mb (16+1), ARM 700 +FPA 10
> Drives: motherboard IDE: 4Gb WD caviar 34000
>
> On this system I cannot boot from a floppy with
> !linux -bootkernel ADFS::0
That's expected - the name after -bootkernel is the RISC OS filename of the
kernel. ADFS::0 is not. It won't report an error, because RISC OS does allow
you to open and read from "ADFS::0".
This would explain why your following attempts also failed.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
