From: Chris Jantzen <chris-parisc@maybe.net>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] C180 not booting Sarge kernel
Date: Thu, 21 Nov 2002 14:09:30 -0800 [thread overview]
Message-ID: <20021121220930.GF23152@maybe.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0211210831370.23497-100000@wolf.alaskatech> <20021121135754.GA3811@systemhalted>
On Thu, Nov 21, 2002 at 08:57:54AM -0500, Carlos O'Donell wrote:
> > FYI, my sarge-based C180 has not been able to boot 2.4.19-32_18 or _22.1;
> > I have to interact with IPL and fall back to 2.4.18_62.2. It gets as
> > far as the "...if this is the last message you see..." and I never hear
> > from it again, even on the network. And I think after a very very long
> > time, it falls back to firmware. At least, I see DHCP requests coming
> > out of it after a while. (I only just hooked up serial console to
> > interact with IPL after getting no response. No I don't boot it up too
> > often, it's a "side project".)
>
> HP hardware is occasionally quirky :}
>
> > Also, "uname -a" segfaults.
>
> That bug got squashed in unstable. You'll see the fix soon.
>
> > I'll try unplugging the GSC and EISA cards plugged into it tomorrow.
> > I'll also try letting it just sit there under supervision and see what
> > really happens.
>
> Good idea :)
> If it doesn't work, get back to the list.
Well, after leaving 22.1 running, it does appear to come up after a
while. About 20 minutes. I am rather certain 18 never booted. Taking all
the expansion cards out does not make any difference.
After doing this, it occurred to me that maybe this was the bus walk
issue that I had ignored on the mailing list from a week ago. :-)
On Thu, Nov 21, 2002 at 08:34:38AM -0900, Tom wrote:
> "They" swear this has a fix in 2.5, but I just let it take it's time and
> all seems happy...
Well, we'll have to keep on them, eh? :-)
While I have somebody's attention: I have some EISA 3c597's that I'd
like to use in this machine. I carefully compile the kernel module with
the same parameters and install it and all I ever get is:
ryoko:~# modprobe 3c59x
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
3c59x: 3Com EISA 3c590 Vortex 10Mbps at 0x1000. Vers LK1.1.16
ccio-dma.c:638: Assertion dev failed!
Kernel panic: dev
Message from syslogd@ryoko at Thu Nov 21 09:47:32 2002 ...
ryoko kernel: Kernel panic: dev
I don't get any kind of "HMPC" or register dump or anything else. Just
sits there and stops responding.
Is it ever possible that these cards would work in PA-RISC? They
certainly fit in the slot (;-)), and don't have any x86 code on them. Or
do I need to buckle down and buy a replacement backplane and go PCI?
--
chris jantzen kb7rnl =-> __O
Insert witty comment here. _`\<,_
http://www.maybe.net/ (*)/ (*)
next prev parent reply other threads:[~2002-11-21 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 9:01 [parisc-linux] C180 not booting Sarge kernel Chris Jantzen
2002-11-21 13:57 ` Carlos O'Donell
2002-11-21 22:09 ` Chris Jantzen [this message]
2002-11-21 22:42 ` Matthew Wilcox
2002-11-21 17:34 ` Tom
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=20021121220930.GF23152@maybe.net \
--to=chris-parisc@maybe.net \
--cc=parisc-linux@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox