From: "Mathieu Lonjaret" <lejatorn@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] plan 9 on an IBM eserver 325
Date: Thu, 24 Apr 2008 10:49:09 +0200 [thread overview]
Message-ID: <3c63b6f1073049f0bc708b86d9eba88c@ipgp.jussieu.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
Hello 9fans,
I've recently acquired such a machine (bi proc opteron) and I thought
it'd be nice if I can make a cpu server out of it and hook it up on the
net at work so that it can be made available for the 9fans out there.
I've tried booting on an iso I fetched yesterday, but 9load was not so
happy about it; here's what it printed at boot (possibility of typoes
not totally excluded):
ELCR: 0C80
apm ax=f000 cx=f000 dx=40 di=ffff ebx=5d84 esi=-1
initial probe, to find plan9.ini... dev A0 port 1F0 config 0040 capabilities 2F00 mwdma 0007 udma 407F
dev A0 port 170 config 85C0 capabilities 2F00 mwdma 0007 udma 0407
FLAGS=10282 TRAP=6 ECODE=0 PC=3
AX 00000000 BX 80815d78 CX 00000000 DX 800fdfc0
SI 00001022 DI 00000024 BP 0000746b
CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
CR0 80000011 CR2 0000000 CR3 0000c000
panic: exception/interrupt 6
Erik said I should try with a 9load from may 2007 or earlier, so I was
wondering if anyone of you had one handy, or if there's a way to obtain
one easily (mounting an old snapshot?)? Or any other suggestion to have
the iso booting a bit further?
Also do you think there's any chance I can have plan9 working on
this machine or are there any other incompatibilities I have not yet
discovered? (I know about the unsupported broadcom NICs, but that should
be fixable by plugging another NIC). Am I simply better off installing
Linux with inferno on top of it?
Any other suggestion?
Here's more information about the machine (and the output of lspci -vn
is attached):
http://www.amdboard.com/ibm_eserver_325_specifications.html
Thanks,
Mathieu.
[-- Attachment #2: Type: text/plain, Size: 4022 bytes --]
00:06.0 Class 0604: 1022:7460 (rev 07)
Flags: bus master, 66Mhz, medium devsel, latency 115
Bus: primary=00, secondary=01, subordinate=01, sec-latency=68
I/O behind bridge: 00002000-00002fff
Memory behind bridge: fc100000-fdffffff
Capabilities: [c0] #08 [0086]
Capabilities: [f0] #08 [8000]
00:07.0 Class 0601: 1022:7468 (rev 05)
Subsystem: 1022:7468
Flags: bus master, 66Mhz, medium devsel, latency 0
00:07.1 Class 0101: 1022:7469 (rev 03) (prog-if 8a [Master SecP PriP])
Subsystem: 1014:7469
Flags: bus master, medium devsel, latency 64
I/O ports at 1020 [size=16]
00:07.2 Class 0c05: 1022:746a (rev 02)
Subsystem: 1014:746a
Flags: medium devsel, IRQ 255
I/O ports at 1000 [size=32]
00:07.3 Class 0680: 1022:746b (rev 05)
Subsystem: 1014:746b
Flags: medium devsel
00:0a.0 Class 0604: 1022:7450 (rev 12)
Flags: bus master, 66Mhz, medium devsel, latency 64
Bus: primary=00, secondary=02, subordinate=02, sec-latency=64
Memory behind bridge: fe000000-fe0fffff
Capabilities: [a0] PCI-X non-bridge device.
Capabilities: [b8] #08 [8000]
Capabilities: [c0] #08 [004a]
00:0a.1 Class 0800: 1022:7451 (rev 01) (prog-if 10)
Subsystem: 1022:7451
Flags: bus master, medium devsel, latency 0
Memory at fc000000 (64-bit, non-prefetchable) [size=4K]
00:0b.0 Class 0604: 1022:7450 (rev 12)
Flags: bus master, 66Mhz, medium devsel, latency 64
Bus: primary=00, secondary=03, subordinate=03, sec-latency=64
Capabilities: [a0] PCI-X non-bridge device.
Capabilities: [b8] #08 [8000]
00:0b.1 Class 0800: 1022:7451 (rev 01) (prog-if 10)
Subsystem: 1022:7451
Flags: bus master, medium devsel, latency 0
Memory at fc001000 (64-bit, non-prefetchable) [size=4K]
00:18.0 Class 0600: 1022:1100
Flags: fast devsel
Capabilities: [80] #08 [2101]
Capabilities: [a0] #08 [2101]
Capabilities: [c0] #08 [2101]
00:18.1 Class 0600: 1022:1101
Flags: fast devsel
00:18.2 Class 0600: 1022:1102
Flags: fast devsel
00:18.3 Class 0600: 1022:1103
Flags: fast devsel
00:19.0 Class 0600: 1022:1100
Flags: fast devsel
Capabilities: [80] #08 [2101]
Capabilities: [a0] #08 [2101]
Capabilities: [c0] #08 [2101]
00:19.1 Class 0600: 1022:1101
Flags: fast devsel
00:19.2 Class 0600: 1022:1102
Flags: fast devsel
00:19.3 Class 0600: 1022:1103
Flags: fast devsel
01:00.0 Class 0c03: 1022:7464 (rev 0b) (prog-if 10)
Subsystem: 1014:7464
Flags: bus master, medium devsel, latency 64, IRQ 19
Memory at fc100000 (32-bit, non-prefetchable) [size=4K]
01:00.1 Class 0c03: 1022:7464 (rev 0b) (prog-if 10)
Subsystem: 1014:7464
Flags: bus master, medium devsel, latency 64, IRQ 19
Memory at fc101000 (32-bit, non-prefetchable) [size=4K]
01:05.0 Class 0300: 1002:4752 (rev 27)
Subsystem: 1014:0240
Flags: bus master, stepping, medium devsel, latency 64, IRQ 16
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
I/O ports at 2000 [size=256]
Memory at fc102000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=128K]
Capabilities: [5c] Power Management version 2
02:01.0 Class 0200: 14e4:1648 (rev 03)
Subsystem: 1014:02a6
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 24
Memory at fe010000 (64-bit, non-prefetchable) [size=64K]
Memory at fe000000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
02:01.1 Class 0200: 14e4:1648 (rev 03)
Subsystem: 1014:02a6
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 25
Memory at fe030000 (64-bit, non-prefetchable) [size=64K]
Memory at fe020000 (64-bit, non-prefetchable) [size=64K]
Capabilities: [40] PCI-X non-bridge device.
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
next reply other threads:[~2008-04-24 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 8:49 Mathieu Lonjaret [this message]
2008-04-24 11:41 ` erik quanstrom
2008-04-24 12:37 ` Mathieu Lonjaret
2008-04-24 12:46 ` erik quanstrom
2008-04-29 10:09 ` Mathieu Lonjaret
2008-04-29 11:31 ` erik quanstrom
2008-04-29 12:16 ` lejatorn
2008-04-29 12:16 ` erik quanstrom
2008-04-29 12:51 ` Mathieu Lonjaret
2008-04-24 14:17 ` Federico G. Benavento
2008-04-24 12:18 ` a
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=3c63b6f1073049f0bc708b86d9eba88c@ipgp.jussieu.fr \
--to=lejatorn@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).