From owner-freebsd-advocacy Thu Sep 28 18:49:45 2000 Delivered-To: freebsd-advocacy@freebsd.org Received: from angmar.mel.vet.com.au (angmar.mel.vet.com.au [203.103.154.62]) by hub.freebsd.org (Postfix) with ESMTP id E9F1C37B423 for ; Thu, 28 Sep 2000 18:49:31 -0700 (PDT) Received: from anduril.mel.vet.com.au (anduril.mel.vet.com.au [203.103.154.58]) by angmar.mel.vet.com.au (Postfix) with ESMTP id F41FF5A334; Fri, 29 Sep 2000 12:49:15 +1100 (EST) Received: (from ulmo@localhost) by anduril.mel.vet.com.au (8.9.3/8.9.3) id MAA14423; Fri, 29 Sep 2000 12:49:05 +1100 Date: Fri, 29 Sep 2000 12:49:05 +1100 From: "Lachlan O'Dea" To: Garance A Drosihn Cc: Dag-Erling Smorgrav , advocacy@FreeBSD.ORG Subject: Re: FreeBSD won't run on newer IBM laptops Message-ID: <20000929124904.B14341@vet.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.9i In-Reply-To: ; from drosih@rpi.edu on Thu, Sep 28, 2000 at 06:13:25PM -0400 X-Operating-System: Linux 2.2.14-5.0 i686 Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Sep 28, 2000 at 06:13:25PM -0400, Garance A Drosihn wrote: [ dual boot works for RPI ] > I encourage people to voice their opinions with IBM, of course, > but if you already OWN a T20, and you would like to use it with > freebsd, then you might want to try setting it up with a dual- > boot configuration. > > My second guess is that we (RPI) were just plain lucky... :-) It sounds like you were lucky. I spent a great deal of time trying to get FreeBSD working on my T20. I was fortunate that a colleague had a 600E, so whenever it refused to boot, I swapped the hard drive into the 600E and used a sector editor to remove the FreeBSD slice (yes, this was very laborious). The machine came with Windows 2000 installed, and I was trying to install FreeBSD as the second OS. I tried both the FreeBSD boot manager and partition magic, but it simply would not work. > It might be that we should not say "recognize type 165", > but instead should say "recognize a WINDOWS partition, > and if there IS NO WINDOWS partition, then do not look > for a windows-suspension partition". Ahh, so that was the problem. I had noticed that it was not just the partition type that mattered. If you make a normal FAT partition and manually change the type to 165 the machine will still boot. The partition actually needed to have FreeBSD installed on it for the problem to occur. I also tried installing FreeBSD and changing the partition type to 255, and the machine would not boot. So it seems any "unusual" partition type could potentially have a problem. I also tried installing FreeBSD and then changing the partition type to NTFS. The BIOS then booted happily, but the FreeBSD bootloader didn't get past first base. Anyway, after spending hours on this, I ended up taking the quick and easy path and put Redhat 6.2 on it. :-((( -- Lachlan O'Dea Computer Associates Pty Ltd Webmaster Vet - Anti-Virus Software http://www.vet.com.au/ Vet 10.2 Forever! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message