All of lore.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Beattie <mbeattie@sable.ox.ac.uk>
To: ultralinux@vger.kernel.org
Subject: Re: Mixed news: new UP 1.0.9 on Ultra5
Date: Wed, 04 Nov 1998 14:50:28 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-91019453222899@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-90976646926603@msgid-missing>

Jakub Jelinek writes:
> > 
> > I retried installing on my Ultra5 today with Jakub's latest UP 1.0.9
> > update that he put there on Monday. The installation went fine right
> > up until it tried to make a boot disk. I put a floppy in the drive,
> > hit "Yes, make a boot disk" and the kernel log on VC 4 came up with:
> >     <4>floppy0: probe failed...
> >       (12 lines of the above)
> >     <4>end_request: I/O error, dev 02:00 (floppy), sector 0
> >     <7>VFS: Disk change detected on device 02:00
> > and the cycle then repeated indefinitely "probe failed" x 12 etc).
> > I killed the "bask mkbootdisk" process but the genromfs process
> > stuch in D state. That kept the loop device busy so that the
> > following "install SILO bootloader" couldn't do its
> > "insmod /modules/loop.o" and thus failed.
> 
> This is strange. My PCI fd (fdthree) works just fine, and I doubt there are
> more types of floppies on PCI machines. I know SBUS floppy is broken at the
> moment, but that's about it. Was the floppy working fine for you with
> previous kernels ever?

This is the first Linux kernel I've been able to try on it. It has
Solaris on it but, on thinking about it, I don't think I've ever
needed to use the diskette drive. I'll do some experiments. It
definitely is an fdthree.

> > I redid the installation from scratch and this time chose not to
> > make a boot diskette. Everything seemed to install perfectly this
> > time and at the "Congratulations...hit return to reboot" I did so.
> > Booting went fine up until the
> >     Adding swap...
> > line at which point there was a pause (30 secs to 1 minute perhaps)
> > before it went on with
> >     Swansea...
> >     IPX...
> >     sunhme.c:v1.2 ...
> >     eth0: HAPPY MEAL...
> >     eth0: Link is up using internal transceiver at 10Mb/s, Half Duplex
> > and then hung. Hitting the CapsLock key lit the light (I don't know if
> > that's relevant on sparc arch).
> 
> This is strange. Was the machine visible on the network (ie. could you ping
> to it)? Were interrupts going? What was the machine doing
> ({shift,alt,ctrl}+scroll lock)? Was Stop+A working? (go should work in these
> kernels already).

In hindsight, I suspect it had booted OK, but events happened as
follows: I powered down and up and it hung after printing the
    CMD646: MDMA enable
message. At this point the machine really did hang: Ctrl-ScrollLock
showed just three processes running: kernel tasks. I then power
cycled it again and tried again. This time it got past that message
and did the same as the previous time: sitting there doing nothing
after the "eth0: Link is up" line. Hitting Ctrl-ScrollLock from time
to time showed fsck running and then other things started. It ended
up with the usual kflushd, atd, crond stuff running and a single
getty. I could indeed ping it across the network and telnet to it to
get a login prompt. With only a root account, that was no good though.
Since the single getty clearly wasn't running on tty1 I went and got a
dumb terminal and plugged that in and, sure enough, could log in as
root there. Success! /etc/inittab has only one getty entry for console
and no others which semi-explains it. What's left to explain is why it
made /dev/console as a serial console. Now I *had* been using a
serial console (ttyb) for Solaris but using it to boot Linux came up
with the error
    Can't init console on serial line
(That's from the scrawl in my notebook so may be wrong). So then I did
    setenv output-device screen
    setenv input-device keyboard
    reset
from the boot prom and all my attempts at installing Linux were then
using the screen/keyboard. Perhaps something somewhere still "knows"
(incorrectly) that I want a serial console?

The upshot is that I now have a running, working Linux on the Ultra5
which should make it easier to debug some of the problems I've been
having. I'll try out the floppy drive and put back in the sunswift
hme/scsi card which had network problems during an attempted install.

--Malcolm

-- 
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services

  parent reply	other threads:[~1998-11-04 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-30 16:52 Mixed news: new UP 1.0.9 on Ultra5 Malcolm Beattie
1998-10-30 17:30 ` David Andrew - Sun MDE
1998-10-30 17:36 ` Hine,C
1998-11-03 14:52 ` Hine,C
1998-11-03 15:27 ` Jakub Jelinek
1998-11-04 12:40 ` Malcolm Beattie
1998-11-04 14:50 ` Malcolm Beattie [this message]
1998-11-04 15:29 ` Hine,C
1998-11-04 16:40 ` Jakub Jelinek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ultrasparc-91019453222899@msgid-missing \
    --to=mbeattie@sable.ox.ac.uk \
    --cc=ultralinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.