Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!news.alpha.net!news.mathworks.com!uhog.mit.edu!bloom-beacon.mit.edu!gatech!howland.reston.ans.net!Germany.EU.net!EU.net!ieunet!news.ieunet.ie!jkh From: jkh@whisker.hubbard.ie (Jordan K. Hubbard) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD 2.0R fails on npx 387 Date: 04 Dec 1994 03:26:04 GMT Organization: Jordan Hubbard Lines: 28 Distribution: world Message-ID: <JKH.94Dec4032604@whisker.hubbard.ie> References: <T54mwc2w165w@oasys.pc.my> NNTP-Posting-Host: whisker.hubbard.ie In-reply-to: othman@oasys.pc.my's message of Wed, 30 Nov 94 12:37:16 MAL In article <T54mwc2w165w@oasys.pc.my> othman@oasys.pc.my (Othman bin Hj. Ahmad) writes: When it detects the devices, its details are not given, like io address and interrupt number, causing me to have difficulty in diagnosing the error. Sometimes the IRQ no could be correct but not its io address. dmesg is your friend, and will show you all these boot messages after you've come up. In case of extreme duress, booting with the `-c' flag and typing "ls" is also a good way of seeing what's up. Once you're all the way up, you can also see what *probed* successfully by typing `lsdev'. I'd say that we've provided a fair number of diagnostic utilities for inspecting the state of affairs on your system! :-) SABAH is Heaven. Perpetual Clear Blue Sky, Sea and Mountains near modern civilisations, but how long will this last? Are you still working for the tourist board? Perhaps you could work to get us all a group-rate at one of those 4-star hotels you mention in your other .sigs? :-) Jordan -- Jordan K. Hubbard FreeBSD core team Clams are your friends