From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2fba2a7ca9d962d85979de12fa36fd4c@quanstro.net> From: erik quanstrom Date: Tue, 11 Aug 2009 12:26:52 -0400 To: 9fans@9fans.net In-Reply-To: <3BBB12CF4EFF4040B38542759379E3CD027920@XMAIL.asuch.cas.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] oh, no! (again) Topicbox-Message-UUID: 41c36666-ead5-11e9-9d60-3106f5b1d025 > > First of all, thank you very much for your work, Eric ! you're welcome. unfortunately, so far we haven't made any progress. > > this is a jmicron bug. i haven't yet had in my possession a jmicron > > controller, so this will be interesting, but the new driver does have > > code to work around this very issue. > > My fault. I forwarded the 'Plan 9 Hardware Specification Page' to the computer enterprise who assembled my comp. Apparently, he ignored the 'Chipset' paragraph. > Thank you very much for your effort, indeed, i've verified that i see exactly what you see on my intel atom machine. including the d0 errors, so there's something reazlly hinky going on. after replacing the kernel and 9load in 9fat:, however, my machine boots up just fine. i don't know where it's getting the 9pcf that it's putting in 9fat. it doesn't appear to be the same as /386/9pcf from the cd. (there's only one.) as soon as i figure that out, this will probablly all work. - erik