From: Andy Walker <squawker@start.no>
To: parisc <parisc-linux@parisc-linux.org>
Subject: [parisc-linux] 0.9.3 on a B132L
Date: Fri, 14 Dec 2001 09:24:30 +0100 (CET) [thread overview]
Message-ID: <1008318270.3c19b73ecfadb@nyepost.start.no> (raw)
Hi folks,
First of all, thanks for all the hard work that has gone into 0.9.3. Excellent!
I've got a couple of observations and/or questions. Apologies for the lack
of dmesg output etc. - I'm at work and the workstation is at home.
I have a B132L, with the Visualize EG, GRAPHICS(0), on board frame buffer
(that's Gecko, if I'm not mistaken) and a 4071B in the GSC slot, GRAPHICS(2)
(this thing is Coral in the dmesg output I believe).
Previously, when playing around with 0.9.2 I had set the display path to
GRAPHICS(0), as the 4071B was unsupported. As it turned out, the PS/2
keyboard problems forced me to use a serial console in the end anyway, but
at least the EG seemed to be supported.
So yesterday I booted up 0.9.3 in this configuration. The messages started
to appear on the screen, then stopped after the 'if you don't see anything
more' message. In a flash of inspiration, I moved the monitor cable to the
4071B, and lo and behold, all the output was there! The dmesg shows that
its finding the 4071B before the EG, and using that as the console display
even though the display path is set to GRAPHICS(0). Is this expected behaviour
at this point in time, or is there something fishy going on.
Switching the display path to GRAPHICS(2) fixed things - 0.9.3 booted and
displayed on the 4071B.
So far so good. Installation seemed to go mostly ok - I have two disks on
the FW-Diff controller in this box. I guess I should be specifying the
burst:3 parameter to avoid disk corruption.
The other problem I've experienced is keyboard lockup with the message
'LASI PS/2 keyboard timeout' scrolling up the screen. I was using a
generic PS/2 keyboard at the time. Seems to kick in when the machine
is installing from the cd and I'm messing about on another virtual
console - although that is really just speculation. I can stick the B132L
on the net tonight and log in to see what's going on next time the lockup
occurs - anything in particular I should be looking for?
Regards,
-Andy
------------------------------------------------------------
Få din egen @start.no-adresse gratis på http://www.start.no/
next reply other threads:[~2001-12-14 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 8:24 Andy Walker [this message]
2001-12-14 14:11 ` [parisc-linux] Network bootproblem with 712/80 Tommi Aihkisalo
2001-12-14 14:37 ` Peter Mottram
2001-12-20 15:15 ` Richard Hirst
2001-12-20 20:10 ` Helge Deller
-- strict thread matches above, loose matches on Subject: below --
2001-12-14 14:41 [parisc-linux] 0.9.3 on a B132L Andy Walker
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=1008318270.3c19b73ecfadb@nyepost.start.no \
--to=squawker@start.no \
--cc=parisc-linux@parisc-linux.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.