View Single Post
  #3   (View Single Post)  
Old 2nd January 2009
bogd bogd is offline
New User
 
Join Date: Dec 2008
Posts: 7
Default

Quote:
Originally Posted by jggimi View Post
Question: Was this delay present when you booted the GENERIC kernel, or does it appear only when use use the GENERIC.MP kernel?
Yes. But that's another problem. When I booted the GENERIC kernel, the whole system would go unresponsive a few seconds after starting Xmms (that I got with pkg_add). The only thing I could do was to forcibly shut it down. Then I ended up with an unusable pkg_add.

This guy seemed to have the same problem I did: http://fixunix.com/bsd/87339-screwed-up-pkg_add.html

Wiping out /usr/local and /var/db/pkg did not help solving the pkg_add problem and starting Xmms would freeze everything again. None of this occurred under GENERIC.MP

Quote:
Originally Posted by jggimi View Post
Question: Did this delay happen with the RAMDISK (/bsd.rd) kernel, too?
Yes.

Quote:
Originally Posted by jggimi View Post
It is possible that you might obtain additional information on your console (and dmesg) during the hardware probes by booting in verbose mode.
dmesg | more gives:
Code:
i probe returned 0
>>> probing for ehci*
>>> ehci probe returned 0
>>> probing for cbb*
>>> cbb probe returned 0
>>> probing for skc*
>>> skc probe returned 0
>>> probing for mskc*
>>> mskc probe returned 0
>>> probing for puc*
>>> puc probe returned 0
>>> probing for wi*
>>> wi probe returned 0
>>> probing for an*
>>> an probe returned 0
>>> probing for iwi*
>>> iwi probe returned 0
>>> probing for wpi*
>>> wpi probe returned 0
>>> probing for iwn*
>>> iwn probe returned 0
>>> probing for cmpci*
>>> cmpci probe returned 0
byte 529
The beginning seems to be missing if not other portions as well. Is there a way to view it fully?

Thanks for your help.

Last edited by bogd; 2nd January 2009 at 06:35 PM.
Reply With Quote