From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucio De Re To: 9fans@cse.psu.edu Subject: Re: [9fans] waserror()/nexterror() Message-ID: <20040116204209.V25947@cackle.proxima.alt.za> References: <887916726fef37e3c6950c109038f988@terzarima.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from jmk@plan9.bell-labs.com on Fri, Jan 16, 2004 at 10:37:06AM -0500 Date: Fri, 16 Jan 2004 20:42:10 +0200 Topicbox-Message-UUID: bb470b54-eacc-11e9-9e20-41e7f4b1d025 On Fri, Jan 16, 2004 at 10:37:06AM -0500, jmk@plan9.bell-labs.com wrote: > > For some time Plan 9 on sources had the 'coherence' variable in pc/devarch.c > initialised to to something that wouldn't work on an x86 that didn't have the > CPUID instruction, e.g. the 386 and most 486. I attempted to fix it a few weeks > ago, if your kernel has the current devarch.c, fns.h and l.s and still doesn't > work, let me know. > Thank, Jim, it helped considerably. Not enough for a successful boot, just yet, but definitely the kernel startup has proceeded much further. I figure that the SiS is not a properly grown up P5. Cpuidentify(), however, seems to think it is, so when it sets "tsc", it blows the chip out the water. I added a t->family = 4; to skip that section and I have made good progress. Let me post here the last words... cpu0: 511MHz SiS SiS SiS P5 (cpuid: AX 0x0505 Dx 0x800111) ELCR: 8820 pcirouting: BIOS workaround: PCI.0.1.2 at pin 4 link 65 irq 15 -> 5 pcirouting: BIOS workaround: PCI.0.13.0 at pin 1 link 65 irq 5 -> 15 #l0: rtl8139: 10 Mbps port 0xE200 irq 15: 0090DC0276DF 8356 free pages, 33424K bytes, 151824K swap root is from (il, tcp)[il]: It fails spectacularly (long stack dump, if there is an error message, it has been flushed off the screen) as soon as I press Enter. Ah, that was because I omitted "ethermedium" in the kernel. It's better now. I'd like to know what the BIOS workarounds are, as well as the later complaint that something isn't a DMA bus mastering device (just ahead of the VGA complaint that it does not cope with the SiS chipset :-( And no USB device, apparently, either. That would be a real show stopper. I'll post a few diagnostics tomorrow, I'm losing concentration. To summarise, I can log in, connect to the file server, read the IDE drive that oughtn't top be there, really, but I can't really perform any terribly useful operations just yet. Without graphics, however, the device is really a dead duck. ++L