LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 03-10-2007, 11:07 PM   #1
shattered_maul
LQ Newbie
 
Registered: Mar 2007
Posts: 3

Rep: Reputation: 0
Freezing Issues on Slackware 11.0


Hello everyone,

This is my first time posting. I recently downloaded Slackware 11.0 and installed it. The first thing I attempted was to compile kernel 2.6.20.1. I copied the kernel-2.6.20.1 folder from my windows NTFS partition to /usr/src. I then deleted the linux link which pointed to the 2.4.33.3 kernel folder which was currently being used. After creating a new linux link to the 2.6.20.1 kernel folder, I entered it. The next step I attempt is to run “make menu config”, however, the system sometimes hard freezes. The cursor stops blinking and there is no reaction to keyboard input, linux becomes completely unresponsive. I’ve left it alone for an entire hour and the screen didn’t chance, it was as though it were frozen in place. It also freezes when I try just the “make” right afterwards. After reinstalling a few times and several attempts, I could never get past the second make. It would always freeze on either “make menu config” or just “make”.

I ‘m curious if there’s a step I’m forgetting or if I’m setting things up improperly.

Some info on my system:
-I never set up X, I’m attempting this right after running setup and rebooting; so everything is done via the console. I do select 1024x768x255 during setup.

-I selected a usb mouse during setup.

-I skipped the kernel selection step so only the 2.4.33.3 kernel which the boot cd enviorment utilized was used.

-I have 3 partitions on my one HD: NTFS, ext3, and swap (2 gigs)

-My hardware: ABit NV8, Athlon64 3400+, 2x 1gb Corsair (ran memtest86 over night with no problems, over 7 passes), 150gig IDE HD, DVD Drive, GeForce7900GT, usb mouse, usb keyboard

Any suggestions would be much appreciated.
 
Old 03-10-2007, 11:33 PM   #2
XGizzmo
Member
 
Registered: Mar 2007
Distribution: Slackware
Posts: 264

Rep: Reputation: 68
First things first its "make menuconfig" not "make menu config"
Next I would start off with a known working config like the one on your cd/dvd in /kernels/test26.s/config.
I would run make mrproper in /usr/src/linux-2.6.20.1 this step will delete any existing .config so if you need to keep the old .config back it up somewhere.
copy your .config back or grab the one off the cd/dvd and run "make old config"
and keep hitting enter to accept the default answers, then do your "make menuconfig". If it hangs again see if control c breaks you out.
 
Old 03-11-2007, 12:02 AM   #3
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Apparently, from what I've read, it is unwise to put the new kernel source into the usr/src/ directory.
I'm unclear on the details, but I've followed the rules and everything works fine.
I use 2.6.20, and have no problems with it; compiled it lots of times.
The path I use is /usr/src/source/2.6.20

Also, don't delete the old symlink at the start, there's no need. Wait till the compile is done and all went well, THEN change your symlinks, including the one in usr/src/ which will point to (using my example) /usr/src/source/2.6.20

As the user above noted, it's 'make menuconfig'. First (usually unnecessary the first time) type 'make clean' and for subsequent builds, if you want to start totally fresh, use 'make mrproper' after make clean.
Incase menuconfig continues to not work, try 'make xconfig' instead; it does the same thing, just with a different (and easier to read IMO) interface.
 
Old 03-11-2007, 04:08 PM   #4
Ilgar
Member
 
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 14.1, Slackware64 14.1
Posts: 930

Rep: Reputation: 96
Also, you can try

ctrl+alt+[f1..f6]

to switch between different consoles. It's very unlikely that you had a freeze there, Ctrl+c would probably save you.

On the other hand, i don't know why you didn't get this:
Quote:
bash-3.1# make menu config
make[1]: Nothing to be done for `/usr/src/linux-2.6.20/scripts/Kbuild.include'.
make[1]: *** No rule to make target `menu'. Stop.
make: *** [menu] Error 2
 
Old 03-12-2007, 06:03 PM   #5
shattered_maul
LQ Newbie
 
Registered: Mar 2007
Posts: 3

Original Poster
Rep: Reputation: 0
Sorry, there was a typo. I wasn't typing "make menu config", but "make menuconfig". I accidentally put the extra space. This hasn't been the first time I've had odd freezing issues with Linux. I also have them in windows. That's why I decided to try Slackware. I had hopped that the stability many people say it has would be my saving grace.

I haven't yet been able to pin down the problem, however. Because my system has demonstrated this hard freezing on multiple operating systems, it all the more affirms my fears that it's a hardware problem. The most obvious culprit would be some sort of dis-functionality with my RAM, though memtest86 has never reported any sort of error. I've tried various voltage and timing settings in my BIOS to no avail as well. I've heard of problems with some socket 754 motherboards; that the design of many socket 754 architectures contain various "bugs", or that there are incompatibility issues with my hardware.

I've decided to stop trying to fix the problem. After almost an entire of trying to sort out the issues with no luck, I've simply started to save up for a new system. It makes for a nice excuse to splurge on new motherboard, processor, and memory.

Thank you everyone, for your help.
 
Old 03-12-2007, 07:44 PM   #6
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 13.37 Android 4.0
Posts: 2,248

Rep: Reputation: 46
Quote:
Apparently, from what I've read, it is unwise to put the new kernel source into the usr/src/ directory.
huh? Where did you get this bit of nonsense?


It sounds like you are having a hardware problem, most likely thermal related.
 
Old 03-12-2007, 08:27 PM   #7
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
For completeness, that "nonsense" comes from Linus Torvalds:

http://linuxmafia.com/faq/Kernel/usr...x-symlink.html
 
Old 03-12-2007, 08:41 PM   #8
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 13.37 Android 4.0
Posts: 2,248

Rep: Reputation: 46
Quote:
Originally Posted by piete
For completeness, that "nonsense" comes from Linus Torvalds:

http://linuxmafia.com/faq/Kernel/usr...x-symlink.html
Ah, ok, I understand where you got that nonsense from now. In all honesty I can understand why Linus feels that way but in truth it's highly unlikely to cause any real problem and it only relates to the /usr/src/linux link anyway. In all the years I've been running Slack it's never caused a problem.

If you're really worried about it you can simply make sure the link point to whatever source glibc was compiled against. I'll restate this one more time, I've never ever had it cause any problem at all.
 
Old 03-13-2007, 02:37 PM   #9
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Thank you piete for that clarification.
For the record, for clarity, and for the benefit of those who may like to jump first and ask questions later, I restate that I also have not had problems using the usr/src/ path for my kernel compiles. Far as I am concerned, /usr/src/this/that/theotherthing is still in the path /usr/src/ and while I haven't had problems using it, others may, hence the inclusion of Linus' 'nonsense' (which anyone who's used Slack for 'many years' surely has encountered before).
And alas, after reading AND CONSIDERING FOR A MOMENT the further details provided by the original poster, I tend to agree with masonm: any such problem which persists across multiple OS's is very likely hardware related.
 
Old 03-15-2007, 03:08 PM   #10
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 13.37 Android 4.0
Posts: 2,248

Rep: Reputation: 46
To Piete

piete;

I extend my most sincere apology for my obviously poor choice of words in the recent Freezing Issues On Slackware 11 thread (I was actually trying to be funny but failed miserably). I didn't mean to insult you.

I injured my back recently and have been under the influence of some pretty powerful drugs. Not an excuse by any means, merely an explanation. Please accept my apology as I never intended to insult you.

I'm well aware of Pat's thinking regarding kernel headers and such, but just have never had it be an issue for me.
 
Old 03-15-2007, 03:48 PM   #11
piete
Member
 
Registered: Apr 2005
Location: Havant, Hampshire, UK
Distribution: Slamd64, Slackware, PS2Linux
Posts: 465

Rep: Reputation: 44
Hey! I really appreciate the open apology, it means a lot, but I wasn't expecting one and took no offense =)

I'm looking back at the post myself and I came off a bit pretentious myself. I didn't post a follow up simply because I didn't think anyone in that thread (or anyone who came looking later) needed a full-blown explanation of headers and so on. It's just the way I feel threads should work: you get in, you post your piece and then you get out with a sense of "job done"! I try to leave my own opinions at the door and solve whichever problem is immediate - in this case, she wasn't sure where she read it and you hadn't seen the post (or didn't make the connection). So, I got in, I sorted that problem and left again =D

Sorry to hear you're under medication, I hope it's helping your back.

For those wondering "WTH?" the thread in question is here: http://www.linuxquestions.org/questi...d.php?t=536428 and GrapefruiTgirl said:

Quote:
Apparently, from what I've read, it is unwise to put the new kernel source into the usr/src/ directory.
For completeness, I put my sources all over the place because I'm a messy pup, but generally in /root/src or similar (depends which PC i'm hacking at the time) since that's the only user who can update the kernel, and I have the graphics drivers and any patches in there too. The question of "Where should I put my kernel source?" is really a double edged sword.

* Put it in /usr/src and the many programs that want a preconfigured source tree (especially for anything that wants to build/insert a module) can find it pretty easily since, by convention, the tree is located there. So you make your life easier with compiling everything else.
* Put it anywhere else and you have to start messing with options for pointing at the kernel sources, assuming the program can see the directory (/root/src is hardly globally viewable!), but it's not in the main directory structure and isn't outside of the package management system.

I think, really, it's the symlink that's a problem, and I understand it's not really needed anymore, since newer stuff should be looking in /lib/modules/<version>/source for the location of the source tree no /usr/src/<version>. I take a perverse pleasure in keeping stuff out of the install that's not registered with the package manager, so suddenly wading around in /usr/src seems like a bad idea to me, especially since you can build the kernel as a user just like every other source you'll get a hold of, and you're inherantly (in /) messing around as root outside of the safeish environment of the home directory.

Note the two symlinks for my build & source directories:

Code:
administrator@Melchior:~$ ls /lib/modules/2.6.14.3/ -l 
total 160
lrwxrwxrwx  1 root root    25 2005-12-07 14:34 build -> /home/root/linux-2.6.14.3
drwxr-xr-x  9 root root  4096 2005-12-08 19:08 kernel/
drwxr-xr-x  2 root root  4096 2006-07-20 13:56 misc/
-rw-r--r--  1 root root 28334 2007-01-17 13:08 modules.alias
-rw-r--r--  1 root root    69 2007-01-17 13:08 modules.ccwmap
-rw-r--r--  1 root root 20609 2007-01-17 13:08 modules.dep
-rw-r--r--  1 root root   147 2007-01-17 13:08 modules.ieee1394map
-rw-r--r--  1 root root   206 2007-01-17 13:08 modules.inputmap
-rw-r--r--  1 root root    81 2007-01-17 13:08 modules.isapnpmap
-rw-r--r--  1 root root 28673 2007-01-17 13:08 modules.pcimap
-rw-r--r--  1 root root 24453 2007-01-17 13:08 modules.symbols
-rw-r--r--  1 root root 28606 2007-01-17 13:08 modules.usbmap
lrwxrwxrwx  1 root root    25 2005-12-08 19:08 source -> /home/root/linux-2.6.14.3
Anyway, keep on Slacking =)

- Piete.
 
Old 03-15-2007, 04:08 PM   #12
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 13.37 Android 4.0
Posts: 2,248

Rep: Reputation: 46
I have a couple of place I tend to put my sources. If they're kernel related or dependent I tend to put them in /usr/src, but if they're just apps and such I have my own /src under my home directory. It helps me keep them straight.

There are still a few things that still look for that /usr/src/linux link but they're becoming fewer and fewer. I pretty much always keep that link pointing at my most current kernel source tree. Maybe I've just been lucky but in over 10 years it's never created any sort of problem for me although I can imagine that it possible could under the right circumstances. But in that case it's easy enough to create another one for that instance.
 
Old 03-15-2007, 07:36 PM   #13
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Since I was mixed up in that thread, I figured I'd add my two cents here, just as another reference for users wondering if there is a 'right' or 'wrong' place to put sources.
Masonm and Piete have done a good job of explaining the issue I had initially raised about /usr/src/ being a historically bad place for kernel sources, and thanks to them both for pointing out 'where in the world' it had been that I read that, and why it might be so.

Personally, I put everything except kernel code in my /var/cache/packages/<right-here> area, for simplicity, and so I can always find the source and any files that were packaged with anything I have installed. Also, I regularly backup var/cache/ so I always have all the packages I have accumulated, regardless of how I installed them.
For kernels, I use /usr/src/source/<2.x.x.x> which I also backup regularly. All the kernel sources I have are saved here, and their config files I have made, in folders named numerically by kernel release number, and I compile them in here too.

PS- That was very sweet of you Masonm, apologizing to Piete, and sets a good example! We all have bad days, that's for sure, and sometimes our tongues get the better of us.
I too wish you to get better soon; back pain can be hellish, and very trying on ones' patience.

Take care all!
SV

Last edited by GrapefruiTgirl; 03-15-2007 at 07:37 PM.
 
Old 03-15-2007, 08:50 PM   #14
masonm
Senior Member
 
Registered: Mar 2003
Location: Following the white rabbit
Distribution: Slackware64 13.37 Android 4.0
Posts: 2,248

Rep: Reputation: 46
Thanks, but hardly sweet. Just the gentlemanly thing to do when one is in the wrong.
 
Old 03-15-2007, 10:21 PM   #15
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,277

Rep: Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587Reputation: 587
Smile

Quote:
Originally Posted by masonm

I injured my back recently and have been under the influence of some pretty powerful drugs. Not an excuse by any means, merely an explanation. Please accept my apology as I never intended to insult you.
Very sorry to hear that you've hurt yourself, masonm! I hurt my back 20 years ago and still have lingering effects from that incident. I know how truly painful a bad back can be. I hope that you're recovering well!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Lagging & freezing issues Waltman19xx Fedora 1 12-03-2006 11:14 AM
Acer 230XV keyboard/freezing issues tougher Linux - Laptop and Netbook 4 10-10-2006 03:42 AM
Slackware freezing alot? Garibaldi3489 Slackware 21 01-27-2005 05:40 PM
Eth0 and freezing issues on new mandrake install Inexactitude Mandriva 4 05-31-2004 01:04 AM
Fluxbox/freezing issues Wynd Linux - General 3 04-28-2003 08:45 PM


All times are GMT -5. The time now is 05:35 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration