Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

fail to install 4.4 on omnibook 500

0 views
Skip to first unread message

Guido van Rooij

unread,
Nov 23, 2001, 5:32:21 PM11/23/01
to
I got an omnibook 500 today but it completely fails to install FreeBSD.
I have it with a floppy drive. Booting from kern and mfsroot goes fine,
but just after probing ad0, the system kind of hangs.
I disabled all unnecessaryy devices and upgraded the BIOS.

With 'kind of hangs' I mean that ctrl-alt-del does not work, and
also scroll lock will not work (though the scrolllock led is turned on).
Ctrl-alt-esc gives the No debugger in kernel message and that is about it.

Does anyone recogize this? Anyone has other options?

(I do not have a cd or dvd drive with it).

-Guido

To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message

jay

unread,
Nov 23, 2001, 5:43:36 PM11/23/01
to
i have an omnibook 500 and that happened to me as well.
i dimly remember booting from the 4.3 install disks and in the
install options specifying 4.4 as the release to install.

=jay

Brooks Davis

unread,
Nov 23, 2001, 5:58:23 PM11/23/01
to
On Fri, Nov 23, 2001 at 11:32:11PM +0100, Guido van Rooij wrote:
> I got an omnibook 500 today but it completely fails to install FreeBSD.
> I have it with a floppy drive. Booting from kern and mfsroot goes fine,
> but just after probing ad0, the system kind of hangs.
> I disabled all unnecessaryy devices and upgraded the BIOS.
>
> With 'kind of hangs' I mean that ctrl-alt-del does not work, and
> also scroll lock will not work (though the scrolllock led is turned on).
> Ctrl-alt-esc gives the No debugger in kernel message and that is about it.
>
> Does anyone recogize this? Anyone has other options?

There seems to be an odd interaction with the 4.4 keyboard probe and
some BIOS versions. If you use the keyboard (say, to select the floppy
as a boot device) the system will detect the keyboard. Otherwise, it
doesn't and boots to the serial console. I haven't had any problems
with current and 4.3 worked as well. I think a BIOS upgrade helped, but
I can't remember for sure since current didn't have problems.

-- Brooks

--
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4

Guido van Rooij

unread,
Nov 23, 2001, 6:05:36 PM11/23/01
to
On Fri, Nov 23, 2001 at 02:57:59PM -0800, Brooks Davis wrote:
>
> There seems to be an odd interaction with the 4.4 keyboard probe and
> some BIOS versions. If you use the keyboard (say, to select the floppy
> as a boot device) the system will detect the keyboard. Otherwise, it
> doesn't and boots to the serial console. I haven't had any problems
> with current and 4.3 worked as well. I think a BIOS upgrade helped, but
> I can't remember for sure since current didn't have problems.
>

That doesn't explian why I dont even get the message about the boot device
and why sysinstall does not start...

Najib Ninaba

unread,
Nov 23, 2001, 10:02:04 PM11/23/01
to
Hello,

You might want to add in a couple of settings in the boot loader before
booting. Press the spacebar enter into the boot loader while it's counting
down to boot. Insert these two lines at the ok prompt:

set hw.pcic.intr_path="1"
set hw.pcic.irq="0"

And then type boot to resume the booting sequence. That should solve the
installation phase.

Regards,
Najib Ninaba

On Fri, Nov 23, 2001 at 11:32:11PM +0100, Guido van Rooij wrote:

--
Najib Ninaba
"Life's unfair - but having the root password helps!"
--
PGP fingerprint
B338 7EC2 B737 3BAA 03B1 38C7 0832 B6CF 160F 496E
--
To verify the signature, get my PGP public key at
http://www.keyserver.net/en/ KeyID:0x160F496E

Guido van Rooij

unread,
Nov 24, 2001, 4:25:44 PM11/24/01
to
On Sat, Nov 24, 2001 at 11:01:04AM +0800, Najib Ninaba wrote:
> Hello,
>
> You might want to add in a couple of settings in the boot loader before
> booting. Press the spacebar enter into the boot loader while it's counting
> down to boot. Insert these two lines at the ok prompt:
>
> set hw.pcic.intr_path="1"
> set hw.pcic.irq="0"
>
> And then type boot to resume the booting sequence. That should solve the
> installation phase.
>
Yep it does. Thanks. I checked the ERRATE file, but the above hint was in the
RELEASE-NOTES which I did not read ;-()
0 new messages