Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I got a new motherboard/processor/ram combo after the sound on my old motherboard died, and at some point, I noticed that my system could no longer make it through the night. It also crashes sometimes while I'm using it. I'm running Debian-testing-amd64.
When I say crashing, I mean total system lock. If it's after a night (long period of no use), the screen stays in suspend mode. No matter what, I can't input to the machine using keyboard, mouse, or connect to any servers my machine is running (including ssh).
I ran a 16-hour memtest+ session which returned no errors (and didn't crash overnight). Trying to copy a DVD also brought my system to its knees swiftly and harshly.
could it be a power issue? is 380 enough for all of your hardware?
do you have ethernet/audio/video/other cards installed? if so try running the system with its bare essentials and use process of elimination. if you have onboard video,network,audio, uninstall all of those cards and use the onboard ones and try something that makes it crash, such as burning a DVD, etc.
hope it helps.
Here's a little wrinkle, why I don't think it's hardware related: I dual boot, and I've run windows for days at a time with no locks. It hasn't happened AT ALL in windows. I thought the problem could be related to my IDE and SATA (boot) drives not playing well together, so I removed the IDE drives and ran boot-drive only. No dice, I crashed about 5 minutes ago. I haven't tried a reinstall yet because something that can lock the kernel is almost certainly very low level, and will probably end up being installed when I reinstall.
I don't know whether I have either, but I think I have ACPI. Something in my bios mentions S1 vs S3 standby state. The system also crashes occasionally when I'm doing something mundane (browsing the web, system not under load, not much else open). My temps are normal (<40C on the core), and I don't overclock.
I reach the 30-boot fsck limit for my filesystems fairly quickly because of this, so I see a lot of file system checks in the bootup. I remember them failing a few times, but I don't remember much about the error messages or anything. Could some file system black hole be causing this?
sorry i dont know whats going on, hope someone else can help.
but for troubleshooting restart into single user mode, or run 'init 3' i think it is for single user (check man page), or just kill X (ctrl alt backspace) and run a program, say 'top' and let it sit there to see how long it stays running for. if that succeeds for 'longer than normal' times then i think it narrows it down a bit.
even though you dont think its a hardware problem it could be a 'linux not able to communicate properly with hardware'-software problem. disable the NIC (ifconfig eth0 down) or unplug all drives but the boot drive, disable onboard sound or unplug your sound card if any..
top stayed running for two and a half days, so I looked into X as the problem. I switched to the NV module to see if my nvidia driver was suspect, and the system stopped being able to boot into X. I decided to flatten, and ran into a new and even scarier problem. At this point, I realized that I had been running 2.6.18, and the latest in testing was 2.6.17. I had done my mixed sources without a pin. Oops.
Here's the thread describing my new issue (keyword, kernel oops): link