Re: Results with 2.2.15-2000-06-10
I also got the same keyboard error, (really using the boot floppies)
on an IPX 40megRAM/270MegHD/. (The c,d,m rescue and driver disks)
I also could not do the make a bootdisk, step in dbbootstrap, I could not
capture the screen output of superformat, but here is a bit of my messages
file:
Jun 30 09:17:17 (none) user.err dbootstrap[28]: Please place a bl
ank floppy disk in the first floppy disk drive, and press ENTER.
Jun 30 09:17:18 (none) user.debug dbootstrap[28]: umount: No such
file or directory
Jun 30 09:17:18 (none) user.debug dbootstrap[28]: umount: Invalid
argument
Jun 30 09:17:20 (none) user.info dbootstrap[28]: write_boot_flopp
y: found floppy of size 1600
Jun 30 09:17:20 (none) user.info dbootstrap[28]: formatting flopp
y with cmd 'export LD_LIBRARY_PATH="/target/lib:/target/usr/lib";
/target/usr/bin/superformat /dev/fd0 hd'
Jun 30 09:17:21 (none) user.err dbootstrap[28]: Creation of a boo
t floppy failed. Please make sure that the floppy was not write-p
rotected, and that you put it in the first dr
Jun 30 09:17:31 (none) user.err dbootstrap[28]: Please place a bl
ank floppy disk in the first floppy disk drive, and press ENTER.
Jun 30 09:17:31 (none) user.debug dbootstrap[28]: umount: No such
file or directory
Jun 30 09:17:32 (none) user.debug dbootstrap[28]: umount: Invalid
argument
Jun 30 09:17:32 (none) user.info dbootstrap[28]: write_boot_flopp
y: found floppy of size 1600
Jun 30 09:17:32 (none) user.info dbootstrap[28]: formatting flopp
y with cmd 'export LD_LIBRARY_PATH="/target/lib:/target/usr/lib";
/target/usr/bin/superformat /dev/fd0 hd'
Jun 30 09:17:32 (none) user.err dbootstrap[28]: Creation of a boo
t floppy failed. Please make sure that the floppy was not write-p
rotected, and that you put it in the first dr
I didn't try to install vfat, since I don't need it, but I'll try running
modconf, to see if I can replicate Kurt Mosiejczuk's problem. I did install
nfsd, without problem, but on boot I got these errors:
(the erros actually came from the messages file on the ramdisk, but after
reboot the same undefined symbols were reported. I'm not familiar enough
with sparc hardware to know what these modules do, but some like
/misc/b1pci.o are being problematic because my system does not have a pci
bus, assuming that's what the pci here is refering to. When I get the kernel
source downloaded, I'll see what is what.
--no problems adding the fat module after the install.
Jun 30 08:43:33 (none) user.info dbootstrap[28]: installing kernel and
modules from /dev/fd0
Jun 30 08:45:33 (none) user.info dbootstrap[28]: kernel and modules install
successful
Jun 30 08:50:47 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/b1dma.o
Jun 30 08:50:47 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/b1pci.o
Jun 30 08:50:47 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/c4.o
Jun 30 08:50:47 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/eicon.o
Jun 30 08:50:48 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/hisax.o
Jun 30 08:50:48 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/icn.o
Jun 30 08:50:48 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/sc.o
Jun 30 08:50:48 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/t1isa.o
Jun 30 08:50:48 (none) user.info dbootstrap[28]: depmod: *** Unresolved
symbols in /lib/modules/2.2.15
/misc/t1pci.o
Jun 30 08:53:07 (none) user.info dbootstrap[28]: configured modules; modconf
returned 0
During the apt step it upgraded modconf, during its configuration, it said
"architechture specific config file not found, using defaults".
Earlier, I got my system into a weird state, it was slink 2.1r3 and I
dist-upgraded, before reading the upgrade page (ie I still had a 2.0 kernel)
it crapped out when trying to install the libc upgrade, but when I tried to
install a current kernel .deb, it would not accept it, hence the boot
floppies. Oh well, that will teach me to RTFM once in a while.
Gregg
From: Kurt Mosiejczuk <kurt@csh.rit.edu>
To: debian sparc <debian-sparc@lists.debian.org>
Subject: Results with 2.2.15-2000-06-10
Date: Thu, 29 Jun 2000 12:44:36 -0400 (EDT)
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
--
To UNSUBSCRIBE, email to debian-sparc-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Reply to: