Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Go through the system logs and see if there's anything. System logs are in '/var/log'. Mostly 'syslog' and 'messages' will be of interest. They are timestamped to aid in knowing when the message was given. You should be able to find when it crashed or hung.
That 'suspend mode' stuff may be exactly where the problem lies. Different hardware configurations, particularly between laptops and desktops, as well as the method of suspend (to disk vs to ram) can pose problems unless/until configured properly.
As suggested earlier, start with the system logs and see if anything stands out. If the problem never occurs again since you changed the sleep mode in the BIOS, chances are good that that had something to do with it.
To experiment, change the BIOS back the way it was, and if/when the machine hangs again, reboot and check the logs right away, and you will probably see something near the end of the log(s) before the reboot.
Something else worth noting, as that some BIOSes, (such as my AMI BIOS on my MSI motherboard) have hidden options, which you can usually access by pressing some function key while on certain BIOS screens. These options can affect how a system operates, and possibly cause lockups or other weird behavior.
In my BIOS, pressing F4 on a certain page makes appear an option for disabling the 'C1E CPU advanced halt state' which is apparently known to not work well under some conditions. I have it disabled.
Other things to consider are overclocking (if doing so) and any other BIOS settings that may contribute to system instability.
Continue what you are doing for the time being, as this stuff is somewhat lower on the list of priorities for the time being, in diagnosing the problem, but it's just something to keep in mind for future reference..
I used Google and searched for that error message you posted about the hda-intel driver.
There are numerous reports/threads from other Ubuntu users, who also have VIA mainboards, and who reported similar problem to you.
Try the same: Google that error message you got, and read through the Ubuntu forum threads and the like. There may already be a patch or update for your kernel, which fixes the issue.
The DHCP messages are nothing indicating that they are related to the lockup, IMHO.
2 things you might try:
1) boot the machine with "noapic" or "acpi=off" on the boot command line, and see if there is any difference.
2) if there is hardware you are not using on your motherboard, such as an onboard modem, or built-in sound card, disable them in the BIOS, at least temporarily. This will at least get them out of the equation for the time being.
If the machine works fine by doing any of the above, we can begin to narrow it down to one device, or one kernel module, causing the problem.
NOTE - in reply to your post # 12, if messing with network hardware causes the problem to come and go, then maybe there is a conflict between the driver(s) being used to drive the network hardware. But you need to go about plugging and unplugging and testing, in an orderly manner not just randomly unplugging stuff and guessing.
If the machine is in a working state, and you cannot make it lock up, great. Note how it is configured and what is plugged in or enabled. THEN, try ONE thing at a time, and give the machine ample opportunity to lock up, before trying something else. Otherwise we will get nowhere.
Last edited by GrapefruiTgirl; 05-04-2008 at 12:53 PM.
that's what i'm doing =) though i don't "wait" for lock-up i'm trying to set up the machine so i can do other stuff but i can't cuz i can't put the machine under the TV (HTPC) cuz of this, so when i thought the lock-ups was gone, i simply pulled out the cord to eth0 (this was not randomly, i first do cord, then the dvd, then seal the computer case, then put it back where it belongs) but at step 1, pull out the cord, it locks up fairly quickly, within 2 minutes inside gnome envirement.. atm, i've been inside for 10mins now, fully loaded with css server, vent, torrent, firefox, with eth0 cord plugged in.. i can be wrong, but that's what i'm experiencing right now heh..
Patience is a virtue, particularly while trying to diagnose weird issues like this.
If you are in a rush, you may as well set the machine in a state that you know works, and leave it until you have the time to mess with it.
I don't understand why you would need to have the case open for any of this though. Can you not access the ethernet cables otherwise?
Anyhow, you may also find more info than I can provide, by searching the Ubuntu forum here on LQ, or as mentioned earlier, using Google to find similar reports from other users. I don't use Ubuntu, nor do I have an HTPC, so anything very specific to those subjects could be better addressed by an experienced Ubuntu user. I prefer a more 'simple' Linux..
Last edited by GrapefruiTgirl; 05-04-2008 at 01:13 PM.