Date: Thu, 5 Apr 2007 12:25:07 +0200 From: Ben Stuyts <ben@altesco.nl> To: freebsd-hardware@freebsd.org Subject: Re: Can't boot after adding tx2plus card Message-ID: <4502CA4F-7474-494B-B037-661AF76A88B5@altesco.nl> In-Reply-To: <Pine.NEB.4.62.0704041934150.2169@users.757.org> References: <041C14B4-EEAB-44CF-A3BA-A8EB3D3BA504@altesco.nl> <AE2E1847-0D04-4E7D-A278-91209597F0D2@altesco.nl> <Pine.NEB.4.62.0704041934150.2169@users.757.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 Apr 2007, at 01:37, telmnstr@757.org wrote: >> Any ideas what else I can try? > > I hit something similiar... basically, your card comes up first, so > you would need to customize your fstab and perhaps kernel regarding > the change in boot devices. > > My hack was nassssty. Basically, we changed the first few bytes in > the firmware image for the promise ultra-ATA card, so that the > system bios wouldn't recognize it... reflashed the firmware > (basically killing it). Then NetBSD saw the card once it was > booting, but the onboard card was picked up first. > > We had 3 x ultraATA cards on top of whatever was in the system, and > the # of drives was to change all the time... > > See if you can disable the onboard Promise BIOS.... probably not. No, I can't disable the BIOS. Your solution (if I could reproduce it...) would seem to work. If I disconnect all drives from the TX2plus, but boot with the card still installed, booting works fine, and FreeBSD sees the card. > Promise was of no help, and their flash utility checksummed the > firmware so it had to be hacked. I no longer have access to any of > that, and a co-worker helped with it as he had experience with the > promise cards and knew that the first few bytes of the firmware are > what the system bios sees when it scans for other bioses to execute. Nice hack! Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4502CA4F-7474-494B-B037-661AF76A88B5>