From owner-freebsd-current Sun Nov 28 2:54:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 92D7B14CE7 for ; Sun, 28 Nov 1999 02:54:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA98732; Sun, 28 Nov 1999 02:55:06 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199911281055.CAA98732@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Douglas Kuntz" Cc: current@FreeBSD.ORG Subject: Re: Boot error In-reply-to: Your message of "Fri, 26 Nov 1999 15:31:02 EST." <000c01bf384d$2824c980$29100218@micronetinfo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Nov 1999 02:55:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok...for hardware, all I have in the machine is: > A Linksys 10/100 ethernet (uses pn0) > A SCSI card (uses bt0) > A S3 Virge video card > A FIC VA-503+ motherboard w/ 32meg PC66 sdram and a K6-2 400 > the only thing changed between the 2 machines was the other was a Shuttle > Socket 370 motherboard, and a Celeron 366 cpu. > Everything was moved from one case/motherboard to the other > case/motherboard. > The kernel had "ata" compiled in, the options for my hardware, and the basic > floppy and video, nothing that I though was unusual. > > Sorrry about the way I typed before...I actually talk like that (or worse) > half the time, and I have to remember when to talk/type normally. This still doesn't answer the second half of the question. It used to work, then it stopped. What did you change? > Doug > > ----- Original Message ----- > From: "Mike Smith" > To: "Douglas Kuntz" > Cc: > Sent: Friday, November 26, 1999 3:32 AM > Subject: Re: Boot error > > > > > > First things first; try using English for your problem reports. A large > > slice of the community that might be able to answer your questions don't > > use it as their first language, and by using leet-speek you immediately > > eliminate them as a source of help. > > > > > Before I go do a fresh SNAP install, I wanted to see if there was an > easier > > > way to fix this problem... > > > My -current box was a celeron...I had to switch the celeron and mboard > to my > > > windoze machine to get a vidcard werkin...I recompiled the kernel to > 486, > > > 586, and 686, and moved the HD, the cards, etc, over to the K6-2 400 I > > > had...now, everytime at boot, before it even prompts for which OS to > start, > > > it has a bootloader problem...if I recall it was something like: > > > BTX 1.0.0 BTX Loader 1.0.1 > > > then "System Halted" > > > > > > I tried the fixit floppy, etc, and that partially worked, but locked > when it > > > was mounting the filesystem. > > > I'm sorry that I cant provide any more info...I only have 1 monitor and > cant > > > copy/paste between 2 pcs. > > > > I'm sorry, but without a lot more information all I can say is "you done > > something wrong". > > > > You might start with an exhaustive list of the relevant hardware in the > > actual system in question, followed by the actual set of physical changes > > which took it from "working" to "not working". We're not telepathic, and > > we don't have the time to hunt you down and steal all your hardware to > > solve your own problems, so you're going to have to help us out here. > > > > -- > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message