Results 1 to 9 of 9
I have a computer with DesktopBSD v1.6 installed on it. It is reaching a level of configuration where I am content with it, it is just that I need to ...
- 01-03-2008 #1Linux User
- Join Date
- Dec 2004
- Posts
- 323
Why the need to restart the computer?
I have a computer with DesktopBSD v1.6 installed on it. It is reaching a level of configuration where I am content with it, it is just that I need to restart the computer twice all the time: whenever I switch the computer off and back on again, it will halt at the splash screen, the only remedy left is the reset button. In other words I always need to restart the computer twice. Why? More importantly: where do I start looking for causes and solutions?
Thanks in advance
- 01-09-2008 #2Linux Newbie
- Join Date
- Jul 2007
- Location
- Here. There. Anywhere.
- Posts
- 150
I don't use BSD, but just an idea...
is there an option to view processes during boot("verbose mode," perhaps)? It would be useful to see what is going on during boot when it freezes.
Otherwise, I would not no where to even look except to see what you are doing/changing before you have to reboot twice.
- 01-18-2008 #3
I am also unfamiliar with BSD, but I have another suggestion. A friend of mine was having similar issues (Always required to boot then reboot before anything would load) and after quite a bit of digging he found that this was a known problem with his motherboard/ram interaction. I would think that this type of thing is rare, but when errors occur for no apparent reason it sometimes pays off to check out those types of rare problems.
Good luck and if find any error logs then you can post them here for more help on the software side.
- 01-20-2008 #4Linux User
- Join Date
- Dec 2004
- Posts
- 323
Thanks for the response. If I try a reboot in verbose mode, mainly elf messages show and the computer hangs at the following line:
ehci0: [GIANT LOCKED]
Any ideas? How do I create error logs?
- 01-22-2008 #5Linux User
- Join Date
- Dec 2004
- Posts
- 323
The workaround that seems to work is to type in "shutdown now" in the console. This is far from ideal, but still useable since the console is open a lot.
- 02-10-2008 #6Just Joined!
- Join Date
- Jun 2007
- Location
- Adrift in an ever-expanding universe, quietly contemplating the wondrous and the inevitable.
- Posts
- 82
Just an educated guess, but I think it probably has something to do with your usb controller, or one of your usb devices. You might try disconnecting everything usb (unless of course your keyboard is usb), then try booting up. If it does, then you know to look to one of the devices. Is this an older mobo? One with an earlier implementation of usb perhaps? Just fishing for possibilities here.
qv
- 02-18-2008 #7Linux User
- Join Date
- Dec 2004
- Posts
- 323
questio verum: thank you for your reply and the mobo is relatively new, forgot which it was, but it has an AMD dual core on it and was purchased around sep 2006. There is no USB device connected, there are 2 front side USB ports (unused) and 4 rear side USB ports (also unused).
- 11-25-2008 #8Just Joined!
- Join Date
- Nov 2008
- Posts
- 18
How did this keep you from having to boot up twice? Did it stop hanging after that?The workaround that seems to work is to type in "shutdown now"
I was trying a new OpenBSD version and was trying to find out how you are supposed to power down the computer. It boots up to a console, as you mentioned, and after a Windows manager session, it goes back to a console. From the login console, how do you shut it down?
- 11-25-2008 #9Linux User
- Join Date
- Dec 2004
- Posts
- 323
Just hit the main switch. On the computer where this issue surfaces, there is no soft shutdown.


Reply With Quote
