From: Robby <rtr@blueyonder.co.uk>
To: 9fans@cse.psu.edu
Subject: [9fans] Problem booting a standalone cpu/auth server after pull
Date: Mon, 20 Jan 2003 12:33:13 +0000 [thread overview]
Message-ID: <lIRW9.1877$kv3.11919580@news-text.cableinet.net> (raw)
Hi,
I have recently (last week) updated my distribution via pull. I wasn't
sure if I need to rebuild my standalone cpu/auth kernel, so I went ahead
and did that. The only change in my CONF file was the addition of the
bootdir section. Everything built fine, I copied the kernel into /386 and
/n/9fat, updated my /n/9fat/plan9.ini to allow me to boot the new kernel,
and on rebooting it hangs after the following:
....Plan9 from Bell Labs
ELCR: 0C00
dev A0 port 1F0 config 0C5A capabilities 0B00 mwdma 0407 udma 0007
dev B0 port 1F0 config 045A capabilities 2B00 mwdma 0407 udma 003F
dev A0 port 1F0 config 85C0 capabilities 0F00 mwdma 0203
using sdC0!9fat!plan9.ini
.. [-rtr: choose my new kernel]
found /386/9mypccpuauth
739740+607728+105364=1452832
entry: 0x80100020
cpu0: 210MHz GenuineIntel PentiumPro (cpuid: AX 0x0619 DX 0xFBFF)
ELCR: 0C00
#l0: i82775: 100Mbps port 0xFF40 irq 10: 00A0C94988C9
22615 free pages, 90460K bytes, 730460K swap
I am probably missing out something somewhere. Any help is appreciated.
My plan9.ini looks like this:
[menu]
menuitem=cpuauth, Standalone CPU Authentication Server
menuitem=cpuauthold, Old Standalone CPU Authentication Server
menuitem=term, Terminal
menudefault=cpuauth, 10
[cpuauth]
bootfile=sdC0!fs!/386/9mypccpuauth
[cpuauthold]
bootfile=sdC0!fs!/386/9mypccpuauth.old
[term]
bootfile=sdC0!fs!/386/9pcdisk
[common]
bootdisk=local!#S/sdC0/fs
*nomp=1
distname=plan9
partition=new
ether0=type=elnk3
mouseport=ps2
monitor=multisync
vgasize=1280x1024x8
And my mypccpuauth CONF file is this:
dev
root
cons
arch
pnp pci
env
pipe
proc
mnt
srv
dup
rtc
ssl
tls
bridge log
sdp thwack unthwack
cap
kprof
realtime realtimesub edf
ether netif
ip arp chandial ip ipv6 ipaux iproute netlog nullmedium pktmedium ptclbsum386 inferno
draw screen vga vgax
mouse mouse
vga
sd
floppy dma
audio dma
pccard
i82365 cis
uart
usb
link
apm apmjump
ether82557 pci
ethermedium
netdevmedium
loopbackmedium
misc
archmp mp apic
sdata pci sdscsi
uarti8250
uartpci
vgas3 +cur vgasavage
ip
il
tcp
udp
ipifc
icmp
icmp6
gre
ipmux
esp
rudp
port
int cpuserver = 1;
boot cpu boot #S/sdC0/
il
local
bootdir
bootmypccpuauth.out boot
/386/bin/ip/ipconfig
factotum.hack factotum
/386/bin/disk/kfs
Thanks,
Robby
next reply other threads:[~2003-01-20 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 12:33 Robby [this message]
2003-01-20 13:54 ` Fco.J.Ballesteros
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='lIRW9.1877$kv3.11919580@news-text.cableinet.net' \
--to=rtr@blueyonder.co.uk \
--cc=9fans@cse.psu.edu \
/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).