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.
So I rebooted by means of the 12.1 dvd and issued upgradepkg --reinstall to all packages in the "a" and "l" series. There were complaints about a segmetation fault after each single package install. After rebooting the problem still existed.
What should I do? Is reinstalling Slackware 12.1 the only way out?
You should check your memory first. You can use memtest86, run it for a good duration if possible.
Then check the libs, drivers/modules and of course restore from your backup if needed. You did do a backup right?
Code:
excerpt from 'man ldconfig';
NAME
/sbin/ldconfig - configure dynamic linker run time bindings
SYNOPSIS
/sbin/ldconfig [ -nNvXV ] [ -f conf ] [ -C cache ] [ -r root ] direc-
tory ...
/sbin/ldconfig -l [ -v ] library ...
/sbin/ldconfig -p
DESCRIPTION
ldconfig creates the necessary links and cache to the most recent
shared libraries found in the directories specified on the command
line, in the file /etc/ld.so.conf, and in the trusted directories (/lib
and /usr/lib). The cache is used by the run-time linker, ld.so or ld-
linux.so. ldconfig checks the header and filenames of the libraries it
encounters when determining which versions should have their links
updated.
...
Segmentation faults can be caused by several things. Memory, filesystem errors or even program corruption to name a few. You could have problems with the hdd subsystem. It's hard to diagnose with the information your provided.
As I stated earlier I would check my memory then check the filesystem via the install cd1/dvd to run 'fsck' on the filesystem in question. By using the install cd/dvd you will perform the maintenance as a single user on the filesystem in question. As for the hdd subsystem you can use the manufacture diagnostic disk(s) or use a LiveCD such as 'SystemRescueCd' or 'UBCD Ultimate Boot CD' to test the hdd.
These links and others can be found at 'Slackware-Links'. More than just Slackware® links!
Actually the segmaentation fault occurred after I messed with my optical drives. That is, I have two of them: a dvd and a cd burner. My old dvd writer failed, so I bought a new one and replaced it. The drive set a secondary master is at the slot nearest to motherboard on the 80-conductor cable, and the drive that is secondary slave is on the other slot now. The jumpers are set appropriately. dma is on on all hard drives. The new drive seems all roght as I am currently burning dvds with it.
May I have caused this with the replacement of the hard drives? I also noticed that on one of the boots right after the replacement I had a fsck error on my /usr partition. Now no such error occurs.
As everything except ldconfig seems to work ok now I will not reinstall until the new 12.2.
I ran memtest. It seemed to finish the check within 39 seconds according to its own timer. As I have no experience with memtest I am not sure if the test passed ok. No errors were found. Should the test take a bit longer? After the 39 seconds passed the program seemed frozen: it did not respond to the keyboard. I had to reset the machine manually to get out of it.
I tried running fsck on the partition corresponding to /usr, which is /dev/hdb8 on my system, but it was refused because the partition is busy. I tried this in runlevel 1 but the partition was still busy
Memtest86 should run until you stop it. You can press the 'esc' to reboot. If the memtest did freeze then you do have a possible memory problem. I would power down the system and remove the memory sticks. Clean the edges with some 20# typing paper cut into one inch strips folded in half and use denatured alcohol. Swipe in one direction, one strip per wipe. Don't re-use the strips.
If you think the edge connector is dirty then use a thin plastic card (old credit card). Fold a strip of paper over the edge, wet it with denatured alcohol, push into connector then remove. You will need to use multiple strips for each connector.
Replace your memory with care not to touch the edge, your skin oil will cause problems.
Run memtest again, let it run through several passes. The pattern will change for each pass so you should see the change in the upper right screen. The pass count will increase for each pass with the pattern test changing for each one. You should put the system case back in the run condition, close it. This way you will be running the test in the working environment. I like to run memtest86 overnight unless a problem jumps out initially then you can swap out the stick in question.
As for 'fsck', I stated you will need to run it in single user mode. The best way is to use the install cd/dvd to boot. Don't mount it. Just run the 'fsck /dev/your_device', it should test for the filesystem and perform the maintenance. You can do the 'fsck.filesystem' to specify since 'fsck' is just a frontend.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
I would power down the system and remove the memory sticks. Clean the edges with some 20# typing paper cut into one inch strips folded in half and use denatured alcohol. Swipe in one direction, one strip per wipe.
In the past I have had success using a pencil eraser to clean memory stick contacts. Onebuck's method is probably superior though.
I would also recommend grounding yourself before touching any components to eliminate static. I usually just touch an exposed part of the computer's earthed case and have never had problems but I know people who have that haven't discharged static first.
In the past I have had success using a pencil eraser to clean memory stick contacts. Onebuck's method is probably superior though.
I would also recommend grounding yourself before touching any components to eliminate static. I usually just touch an exposed part of the computer's earthed case and have never had problems but I know people who have that haven't discharged static first.
I would not use a eraser to clean a edge connector. The eraser is abrasive plus it will leave oil. You would be better off to just remove and reset the memory.
I still think cleaning is a good option. I like to use 'Chromilin R' after cleaning which is a contact dressing but very expensive. Not readily available except from specialty suppliers.
The grounding technique should be observed whenever one is working with any electronics used today, especially MOS based. A good wrist strap can be purchased at Radio Shack or improvise with a 10 MΩ resistor, wire (comfortable length) and two small alligator clips. Just solder the wire to one end of the resistor then solder a small alligator clip to the other end of the resistor. Solder another alligator clip to the loose end of the wire. You can now clip the wire to your wrist watch band or just wrap the wire in a loop over your wrist then clip so the clip is in contact with your skin. Then clip the resistor clip to the chassis. That way you will be at the same potential as the chassis. The resistor will provide you with isolation but a ground path for a charge.
Your skin resistance is generally in the 10KΩ to 150KΩ range but not enough to provide isolation. This value varies between individuals.
BTW, you should not be wearing panty hose!
Seriously, your body and what you wear can build a charge along with environmental conditions. So static handling methods should be observed. I've seen people (ladies) who caused a lot of damage in a office with poor environmental controls that would cause high static conditions that did destroy some equipment. Mostly from poor handling and people who didn't observe the above technique(s).
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
I would not use a eraser to clean a edge connector. The eraser is abrasive plus it will leave oil.
Here (in th UK) we often have two kinds of eraser supposedly one for ink which is very abrasive and one for pencil which is soft and not that abrasive. I used to use to softer version. I concur with the oil idea though.
Researching this a bit more I have found many people think it's OK and many don't. It's the first time I've heard negative comments on this and as I tend to err on the side of caution I probably would use alternative methods from now on and retract my recommendation.
I've been in the industry since the sixties. The eraser trick has been alive for that long. That doesn't make it right. The gold layer on edge connectors today is no where near the layer on the old connectors. A few wipes will remove or cause integrity problems when a eraser is used.
The rag content for the 20# paper is just high enough to provide a good wipe when whetted with a good agent.
I ran memtests and hard drive tests for hours. none of them gave a sign of error.
Finally I reinstalled 12.1. I still have now idea what caused the ldconfig problem. Probably a filesystem corruption. I was with reiserfs, now I have switched to jfs as the thread on filesystems in this forum does suggest that it is superior.
From now on I will keep a backup of my system, not only of my data.
I would like to get some advice from you on good backup practices. I have heard something about backuping a whole partition with the powerful command dd ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.