From mboxrd@z Thu Jan  1 00:00:00 1970
From: quanstro@quanstro.net (erik quanstrom)
Date: Sun, 20 Mar 2011 12:57:58 -0400
Subject: [9fans] New venti install won't boot after 05:00 crash
In-Reply-To: <86ipvdkdcu.fsf@cmarib.ramside>
References: <78a8a30056dea494c98ebd88b9d4b744@gmx.de>
	<f19cb1715f98ba181589cf00ca16aef4@brasstown.quanstro.net>
	<864o6zur7k.fsf@cmarib.ramside> <867hbvkvzf.fsf@cmarib.ramside>
	<6e0ff0c146dd7ec4c2a5272e8ae20dc0@ladd.quanstro.net>
	<86ipvdkdcu.fsf@cmarib.ramside>
Message-ID: <987a8b28e8ffea8e761ac322de44a2af@brasstown.quanstro.net>
Topicbox-Message-UUID: bdaadefc-ead6-11e9-9d60-3106f5b1d025

> As a workaround, I tried putting "echo dma on > /dev/sdC0/ctl" in
> termrc.  This was sufficient to keep a fossil-only install from failing.
> But, even *with* this workaround, a fossil+venti install would still
> return i/o errors.  That's probably because fossil calls venti before
> init calls termrc.  Even wrapping init in a shell script probably
> wouldn't get DMA turned on soon enough to make venti happy, but your
> kernel did the trick.

great work.

i do want to point out that your trick to get the fossil-only install
going is not going to be reliable.  it relies on the boot process winning
a race that it is likely to lose; you'll need to run the 9atom kernel
regardless.

does anything think that it's a mistake to default dma on?

- erik