Charles Fultz wrote:
> Okay, using the ISO image:
> -rw-r--r-- 1 2119 220 107347968 Jan 5 07:31 mini-install.iso
>
> I have _finally_ gotten a successful install on a Sparc5 with a head
> and keyboard. No keyboard problems whatsover.
>
> Now, I will build a new 2.2.18 kernel with PCI support and see if it
> hoses things up.
I'm sure everyone is calling their bookie to place bets that it will
hose up :-)
Once absolutely confirmed, I think this should be treated as a kernel
issue and reported. Ideally it should be able to detect whether the
PCI is in use or not and apply itself only if applicable, like any
good driver should. If they can't make it do that, then the configure
description should be updated to say something like "Does not work on
many non-PCI systems, so choose this only for just PCI based Sparc
machines".
> Charles
>
> P.S.
> I don't know if it's disk related or not,
> but during mke2fs and swapon sometimes I
> would get a Segmentation fault error and
> would not be able to do anything with the
> hard drive after that. I had to reboot.
> This was only during install. Any ideas?
I'm guessing some partitioning issues, but I don't know enough to be
specific. If it happened to me I'd have to go exploring to see what
it might be. This is one of those cases which has made me adopt the
practice of always doing a full drive zero-out before installing a
new system on it (especially if it's a different kind of system).
Many people think I'm silly for doing that, but in practice I have
apparently avoided lots of problems by doing this. I recently
installed OpenBSD on an Intel box. I did zero-out the drive first
as per my usual practice. While doing the install, I goofed up the
partitioning and decided to just start over, and pressed the reset
button. Apparently the disklabel program wrote a partial label by
that point, but not a complete enough one to be useful. When the
loader from the CD came up again, apparently it looked at the HD
label and got so confused it locked up in a hard loop. I had to
go back and zero-out the MBR again (I presumed the rest of the HD
was still zero). This did fix it.
Anyway, if you can zero out the first few sectors of the HD and
start from scratch, it may be the fix needed here. Of course do
NOT do this if there are other things on the drive to keep.
-- ----------------------------------------------------------------- | Phil Howard - KA9WGN | Dallas | http://linuxhomepage.com/ | | phil-nospam@ipal.net | Texas, USA | http://phil.ipal.org/ | -----------------------------------------------------------------
This archive was generated by hypermail 2b30 : Thu Sep 19 2002 - 11:00:02 PDT