SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As the title says my system has been freezing all day, if I manage to close programs I cannot open them again unless I reboot my system.
I was going to try to update my system to see if that would help but the following message popup in the terminal.
Code:
Message from syslogd@home at Tue Mar 20 23:42:05 2012 ...
home kernel: [ 906.834129] general protection fault: 0000 [#1] SMP
Message from syslogd@home at Tue Mar 20 23:42:05 2012 ...
home kernel: [ 906.834134] last sysfs file: /sys/devices/system/cpu/present
Message from syslogd@home at Tue Mar 20 23:42:05 2012 ...
home kernel: [ 906.834207] Stack:
Message from syslogd@home at Tue Mar 20 23:42:05 2012 ...
home kernel: [ 906.834217] Call Trace:
Message from syslogd@home at Tue Mar 20 23:42:05 2012 ...
home kernel: [ 906.834249] Code: 66 66 90 48 8d 5f 08 49 89 f4 4c 89 e6 48 89 df e8 42 d7 46 00 48 85 c0 48 89 c1 74 3a 48 8b 38 48 85 ff 74 29 40 f6 c7 01 75 df <8b> 57 08 4c 8d 47 08 85 d2 74 d4 8d 72 01 89 d0 f0 0f b1 77 08
Can someone tell me what it is and possibly what may be wrong with my system? I'm using Slackware 13.37 xfce and have not changed or updated my system in anyway.
If you can't, try removing one of the RAM sticks and see if it helps (with the computer powered down, obviously). If it doesn't work, try the other RAM stick. If you have only one RAM stick, then try one that you might have lying around.
Last edited by H_TeXMeX_H; 03-21-2012 at 09:30 AM.
Currently running memtest86 v4.0 and there seems to be over 10000 errors, how would I fix them and how would I distinguish which RAM stick is causing the problem assuming it is the RAM?
Take one out, run test, then repeat with the other should tell you which RAM is bad. If they both show up bad, try them in another PC if possible because it could be your motherboard.
150000+ errors now, am currently testing each stick separately. Now errors so far, dont think testing the RAM in another PC is an option, only have the 1 here.
Found the culprit, it was a RAM stick and the others seem to be fine. Download to 5GB now
Slackware disappeared from my Grub menu list so I booted into Fedora and ran "grub2-mkconfig -o boot/grub2/grub.cfg" to recreate the grub.cfg file, that has picked up Win7 and Fedora but not slackware.
I run "os-prober" and get
Quote:
os-prober
rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy
/dev/sdc1:Windows 7 (loader):Windows:chain
rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy
rmdir: failed to remove `/var/lib/os-prober/mount': Device or resource busy
What does that mean and how can I get Grub to show all my distros/OSs?
The bad thing about having a faulty RAM is that it sometimes doesn't have visible consequences (like error-messages or crashes) at first, but nonetheless corrupts the filesystem or the files on the disk, especially when installing/upgrading programs. In that case even a backup made earlier can be useless, just because it also may be corrupted. I would recommend to re-install to have a known-good system. Just my personal opinion.
Make sure to run 'fsck' on the partition that you were trying to boot, probably the slackware partition.
Also, make sure the RAM is still in dual-channel mode or triple-channel with newer Intel systems. You need sets of RAM sticks of equivalent sizes in the respective memory banks. See the manual or wiki.
Why is this so hard??? Everything seems to be running fine now apart from the audio, I have no sound. I try configuring via "alsaconf" but it doesn't want to work.
I have a Xonar D2X sound card which was working perfectly fine first, grrr just want to take out the card and throw it away with my speakers.
Why is this so hard??? Everything seems to be running fine now apart from the audio, I have no sound. I try configuring via "alsaconf" but it doesn't want to work.
Don't run alsaconf. It's only for ISA cards.
BTW, I also am going through the process of testing all my RAM sticks one by one, and the first one I tested turned out to be bad too. Memtest just froze when the "pass" percentage reached 31%. I had assumed that the lockups I'd been getting were the fault of NVidia's Linux drivers. And then I got a "write to invalid memory location" bluescreen in Windows..
Why is this so hard??? Everything seems to be running fine now apart from the audio, I have no sound. I try configuring via "alsaconf" but it doesn't want to work.
I have a Xonar D2X sound card which was working perfectly fine first, grrr just want to take out the card and throw it away with my speakers.
You might have a second sound device (like the HDMI port on a video card). You can check with "alsamixer" to see which is loaded. Also running "alsaconf" can tell you how many are detected and will allow you to select one (1). Check lsmod to see if the module is loading. If you had any file system corruption, you might have to delete all sound file configs and start over.
------------
(1) Sorry, dugan, alsaconf is not just for ISA cards. It detects my PCI Soundblaster cards just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.