Results with 2.2.15-2000-06-10
I've been able to do the install on 2 IPXs and one SS2 so far.
(Well, one IPX hasn't finished, I'll explain below)
I wanted to share my results and the glitches I found.
I've used the tftpboot.img to netboot all these machines. Mainly
because the floppy drives on at least two of them don't seem to
work =(
All machines have 32MB of memory but have differing size hard
drives.
Anyway, on to the details.
The first error I found was right after selecting a keymap.
I picked the top entry, the US QWERTY sun keymap. Right after I
got "Error loading the keymap /sun/sunkeymap.map from /etc/sunkeymaps.tgz"
The system didn't seem to mind though and I went on. Things
went peachy until Configuring Device Driver Modules.
Basically, I can't load ANY modules during this phase. They all
show up as installable. But every one gives the following
error message:
"Note: /target/etc/modules.conf is more recent than
/lib/modules/2.2.15/modules.dep
modprobe: Can't locate modules fat"
Replace fat with the appropriate module name, that's just the first
one I tried. I suppose I didn't try ALL of them, but I did try
fat, nfsd, rarp, openpromfs, st and sg. None worked.
But, I kept going... most of that stuff wasn't necessary to finish
the install.
anXious seems like it could be VERY neat. However, it doesn't seem
to understand Suns at all well. It asked me about what type my mouse
was, but there was no option for a sun mouse. It also started
asking me about what modes I wanted to run, the sync rates for my
monitor, etc. A cool tool, but it shows it definitely wasn't started
with Suns in mind.
The big problem I found on my last time through was installation after
the task selection screen (I used "simple"). The keyboard will not
respond to anything other than switching virtual consoles when in the
first virtual console. Whereas apt stops to ask you if you'd like to
continue, this brings the install to a dead stop. I managed to work around
it by killing the processes and doing a "apt-get dselect-upgrade" on the
second virtual console. Perhaps a clue to the problem is the fact that
when apt spits out the list it's going to install, there seems to be
a cr/lf translation issue, in that each line only seems to get the LF and
not a CR.
One other problem I've run across on the last of the three systems I'm
trying is SILO doesn't seem to want to install. When I try to run it
by hand in the second virtual console it says "Can't find second stage
loader /boot/second.b". Whereas the floppy doesn't work on this machine,
the offer to make a boot floppy doesn't do me much good =)
So, Maybe some of this stuff is already known, but I thought I give my
results so hopefully this next test cycle will be the last =)
--Kurt
Reply to: