From: "James P. Kinney III" <jkinney@localnetsolutions.com>
To: palinux <parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Firmware upgraded, STI console problem
Date: 12 Dec 2001 14:34:35 -0500 [thread overview]
Message-ID: <1008185675.31094.49.camel@archimedes.localnetsolutions.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
My C160 is running the old, broken, no-working-pci, firmware version
2.1. The ftp://us-ffs.external.hp.com/firmware_patches/hp/cpu/ lists the
latest version (PF_CC2X0061) as 6.1.
So I upgraded my firmware. Still no sti console nor X on frame buffer. I
can see in /proc that the frame buffers are running (stifb). When X
starts, it fails on a framebuffer call.
When IPL
dmesg mentions: Dino: No PCI devices enabled.
Also, my processor is listed in firmware and docs as a PA8000. So why
not 64-bit cpu. If I boot the 2.4.16-64 kernel, it hangs after the
"branching" messege screen.
--
James P. Kinney III \Changing the mobile computing world/
President and COO \ one Linux user /
Local Net Solutions,LLC \ at a time. /
770-493-8244 \.___________________________./
GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
<jkinney@localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-12-12 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 19:34 James P. Kinney III [this message]
2001-12-12 19:57 ` [parisc-linux] Firmware upgraded, STI console problem Matthew Wilcox
2001-12-12 20:39 ` Grant Grundler
2001-12-12 20:50 ` Tom
2001-12-12 21:02 ` Matthew Wilcox
[not found] ` <1008218517.2031.1.camel@crudball>
2001-12-13 5:20 ` Matthew Wilcox
2001-12-13 14:21 ` Ryan Bradetich
2001-12-14 18:58 ` 735 and SCSI (was: Re: [parisc-linux] Firmware upgraded, STI console problem) Phil Anderson
2001-12-14 22:55 ` Richard Hirst
2001-12-17 5:43 ` Ryan Bradetich
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=1008185675.31094.49.camel@archimedes.localnetsolutions.com \
--to=jkinney@localnetsolutions.com \
--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