erik quanstrom wrote:
On Sun Mar 6 22:33:33 EST 2011, stanley.lie...@gmail.com wrote:
9atom's 9load prints "%d e820 entries" on boot. is that number 0?
found 7 e8s0 entries
Then it freezes.
it's not the e820 code, then. it's either falling over initializing the
console, or it's falling over probing devices for the .ini file.
after e820, 9load starts up the console and probes devices looking
for a .ini file.
i would think the odds are good that 9load has found an i/o port
that should not be touched. devices are probed in this order
floppy. ether, cd, sd.
i don't really have a kvm setup, but if it's possible, you might try
removing devices (espeically ethernet devices) from a copy of 9load
until you find something that boots, then add 'em back in till it doesn't.
sounds tedious, no? :-)
- erik
Well I've got some other observations of interest.
As I mentioned, I installed with *noe820scan=1 successfully.
I was in the middle of configuring and playing around when I realized I
had no ethernet car. bind -a '#l' /dev returned 'no free devices'.
The vps has an e1000 card (PRO/1000) plugged into it, so I naively put
"ether0=type=igbe" in plan9.ini.
Now it hangs right where 9load would normally say "no ethernet devices
found" or something similar.
How odd.
-Jack
