Date: Tue, 21 Mar 2000 23:01:54 -0500 From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: freebsd-questions@FreeBSD.ORG Subject: Re: Problem Booting 4.0R Floppy (ATA Driver?) Message-ID: <20000321230154.E85043@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <20000316234728.G64407@cc942873-a.ewndsr1.nj.home.com>; from cjc@cc942873-a.ewndsr1.nj.home.com on Thu, Mar 16, 2000 at 11:47:28PM -0500 References: <20000315183902.A60236@cc942873-a.ewndsr1.nj.home.com> <20000316234728.G64407@cc942873-a.ewndsr1.nj.home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
To hell with any last semblances of netiquette! I'm going to followup my own folloup to my own message! Ealier today, I got the announcement of the new release of 4.0-RELEASE from Jordan. "Ah-ah!" I thought, "The solution to my troubles! So my pleas for help did not fall upon deaf ears!" Or at least, I thought I was not the only one having troubles. With anticipation of bringing my familiar old Pentium machine back to life, I quickly downloaded the kern.flp and mfsroot.flp and wrote them on the old, troublesome 4.0 floppies. I booted the kern.flp; no problems there, but there had not been before. I put in the mfsroot.flp when asked and watch the little bar spin until I get to the kernel configuration. I quickly went through the configuration menu removing devices that I do not need, save the changes, and after a deep breath... I hit 'Y' to save the changes and continue... *click* And cccckkkeeeeeerrrrrrrraaaaaaaassssssssshhhhhhhhh... I get the same @#$% error that I quoted below. Now, I try to get fancy. I rebooted from floppies and disabled the first IDE controller in the kernel configuration since it is the one with two devices, and it is not even the one with the disk I want to put BSD on. But no joy, I get the same error. Finally, just for kicks, I disabled _both_ IDE controllers in the kernel configuration, but I _still_ got the error I quote below. It still splurts out the atapci0 stuff and panics. So... Anyone, anyone at all, have any ideas what I can do? Has anyone else seen this to prove that I am not in the keeper of a cruel and evil machine possesed by some dark daemon? Thanks for reading my follow up to my follow up to my own message. On Thu, Mar 16, 2000 at 11:47:28PM -0500, Crist J. Clark wrote: > I hate to follow up to my own post, but I could use some help here, > and I suspect I'm getting lost in the flood of 4.0R update > questions. So, I am going go ahead and follow up my own post. > > To test if the boot floppies I made off of my CD were OK, I tried them > in another machine. I used an even older machine, an i486DX, another > Gateway. I got to the kernel config, cleaned out things I did not have > (kept the usual suspects plus aha0), and went to boot. This machine > booted up and went into sysinstall just fine. > > That makes me think my boot floppies are definately OK. It leaves me > wondering why the distributed GENERIC kernel is then panicing when I > boot on the other system. I'd look into possibly rebuilding a kernel, > but (a) I don't know where to start to solve my problem and (b) I > don't have a 4.0R system to build on since I am having trouble with > the machine I was planning to use for the first 4.0R. > > Anyone have ideas? > > > On Wed, Mar 15, 2000 at 06:39:26PM -0500, Crist J. Clark wrote: > > I am trying to install FreeBSD 4.0-RELEASE on one of my "toy" > > machines, an ol' P5-66 from Gateway. I first tried the 'make world' > > approach last night, but managed to wedge the machine into a pretty > > much unusable state when the installworld kept failing in the middle. > > > > Anyway, I downloaded the 4.0-RELEASE and burned it in a CD. The > > machine won't boot from CD, so I made the floppies. However, the > > kernel won't boot, it panics. Here is the last few lines of kernel > > messages (this is after the visual config which seems to work[0]), > > > > atapci0: <RZ 100? ATA controller !WARNING! buggy chip data loss possible> port 0x3f4-0x3f7,0x1f0-0x1f7 at device 1.0 on pci0 > > atapci0: Busmastering DMA not supported > > panic: resource_list_alloc: resource entry is busy > > Uptime: 0s > > Automatic reboot in 15 seconds - press a key on the console to abort > > > > I'm assuming that the panic has someting to do with the ominous > > message with the atapci0 info? Then again... maybe not. > > > > The system worked without a hitch in 3.x-STABLE (until I mucked up the > > upgrade). I saw some caveats about some disk drivers, but it didn't > > look like an Intel RZ1000 would be a problem. > > > > Any help? > > > > [0] One thing I did notice in the visual config, no ex0 device. Is > > that an intentional deletetion or is something else going on? > > -- > > Crist J. Clark cjclark@home.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > -- > Crist J. Clark cjclark@home.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000321230154.E85043>