LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 08-26-2007, 05:35 PM   #1
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Northern Half of Florida
Distribution: PCLinuxOS on one home machine, Debian Buster on the other. I forget what's on the laptops.
Posts: 146

Rep: Reputation: 28
No console when booting new-compiled kernel 2.6.22.5


Hello all,

About a month ago, I borked my system. Grub wasn't using the /boot partition; instead, it was using the root / partition to pull its files. Took me a while to realize this. Once I did, I ran a few commands I found to "fix" it and wound up hosing Grub. Tried some rescue stuff from various LiveCDs, once I found one with Grub on it, and long story short I wound up hosing the entire O/S to the point of reinstall. Don't ask.

Anywhoo, got to a bootable CLI install of Debian 3.1r4 last night.

I just last night/early this morning downloaded and untarred kernel 2.6.22.5 from kernel.org. I configged; made bzImage, modules, modules_install; copied bzImage to /boot, System.map to /boot/System.map-2.6.22.5, and edited Grub; and booted.

It gets to the end of runlevel 1, and right before (or after??) it would normally go to runlevel 2, it just seems to stop.

The system is actually running; it just appears to have hung. Fortunately, CTL-ALT-DEL still works. Scanning logs, I've determined that the console is not being found. Excerpt from /var/log/syslog:

Aug 26 16:50:53 localhost init: open(/dev/console): \
No such file or directory
Aug 26 16:51:05 localhost last message repeated 12 times

On the screen during boot, the last thing I see is:

NET: Registered protocol family 10
lo: Disabled Privacy Extensions

...which is shown in the syslog, followed immediately by the /dev/console line. When booting a working (old, stock) kernel, in /var/log/syslog, it will go on after "Disabled Privacy Extensions" to IPv6, some CRON, some xfs, more CRON, then a bunch of udev lines. I think this is important. Then goes back and forth between udev and xfx-xtt lines.


I have, as far as I can tell, udev enabled in my new kernel. I found on the net the advice (in a thread somewhere titled "I hate you Greg") about using "MAKEDEV update" and "MAKEDEV console" from a LiveCD to recreate the /dev entries. I did this with no benefit.


I believe it to be udev/sysfs/devfs related, but AFAIK I have udev set in the kernel so it should work fine. I've been googling for over two hours now (spread out over the past 10) and I'm not coming up with anything concrete.

Any help would be greatly appreciated.

I would use the older kernel, but my sadomasotechnical nature demands that I suffer through the brand new of the new, and I have a few things that require building from source (madwifi is one, nVidia module, a couple others I can't recall off the top of my head) since I have never been successful at getting .deb packages to work with these. That makes upgrading in the future more difficult, so I prefer to do it once -- now -- for all that stuff if I can. I'll probably stick with this kernel for a couple of years once it's up.

I'd like to get the new kernel working so I can get my Atheros WiFi working (only have to compile MadWiFi once for new kernel, vise once for old then again for new). Then I can more easily acquire X.org to upgrade from XFree86 like I did before I borked my system a month ago (x.org isn't on Debian Sarge CDs; only XFree86). After X.org is installed, I can do the nVidia driver thing, and then update the rest of my system once all that is working.

Thanks for reading and any help you can provide.

I think I can provide log files if need be. Just say which ones.

CJ Chitwood
 
Old 08-26-2007, 06:24 PM   #2
blackhole54
Senior Member
 
Registered: Mar 2006
Posts: 1,896

Rep: Reputation: 61
You could compare the .config files from the working and non-working kernels and see if you could find a difference that sounds like it might be related. Like you, I suspect it has something to do with udev.
 
Old 08-26-2007, 06:32 PM   #3
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Northern Half of Florida
Distribution: PCLinuxOS on one home machine, Debian Buster on the other. I forget what's on the laptops.
Posts: 146

Original Poster
Rep: Reputation: 28
Quote:
Originally Posted by blackhole54 View Post
You could compare the .config files from the working and non-working kernels

Thanks for the suggestion. That would work if I had the .config of the running kernel. I should have noted in my OP that the currently running kernel is the one installed with Debian Sarge, and does not (that I can see) have the .config included since the source wasn't installed with it, and AFAICT it doesn't have that "kernel .config support" turned on where I can view it in /proc (unless I'm looking in the wrong spot).

It's possible that the kernel source package will have the same configs used by the currently running kernel. I'll look into whether that's a possibility. Thanks for that thought...

Any other thoughts still welcome



PS: At the moment, I'm recompiling a kernel that I was running before I borked the machine, and if that works, I might just keep with that one. It's 2.6.19. FWIW, I've also noticed a few errors in building. They come at different points, and if I make clean before starting over, it will go fine the second time through. I've had my CPU, an AMD AthlonXP 1600 naturally running around 1250 MHz, clocked around 1600 MHz making it report itself as an AthlonXP 2000. It normally runs around 2500 BogoMIPs, but overclocked, it's been doing about 3000. At this speed, the highest the CPU ever gets is 74 degrees Celsius, and even that's only after a VERY long time of intensive work (SETI, for one).

I think that some of the milder errors (unexplainable segfaults only when compiling, e.g., when under a decent load for extended amounts of time) may have been caused by not just it being overclocked, however mildly, but by *improper* overclocking whereas my memory, etc. settings were not tweaked to fit.

I'm running it at normal speed now, with more conservative memory settings (I had researched these earlier today) and it just finished making bzImage with no segfaults etc. at all.

Last edited by CJ Chitwood; 08-26-2007 at 06:41 PM. Reason: PostScript/Afterthought
 
Old 08-26-2007, 06:39 PM   #4
blackhole54
Senior Member
 
Registered: Mar 2006
Posts: 1,896

Rep: Reputation: 61
See if a copy of the config file is in your /boot directory. It will probably not be a hidden file and will likely be called something like config-2.6.xxx.
 
Old 08-26-2007, 07:10 PM   #5
CJ Chitwood
Member
 
Registered: Dec 2006
Location: Northern Half of Florida
Distribution: PCLinuxOS on one home machine, Debian Buster on the other. I forget what's on the laptops.
Posts: 146

Original Poster
Rep: Reputation: 28
Duh! I should have thought of that, thank you! I've been copying bzImages and System maps into that folder all day -- you'd think I'd have pulled a file listing once!


It is there, so I will compare them.


Also, I just booted 2.6.19.1, so if I can't get 2.6.22 working, at least I've got my old kernel back. I think I can get it from here.

Thanks a lot!

CJ
 
  


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 On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
errors while booting a custom compiled kernel can't figure out wich module? krmane Linux - Kernel 1 08-18-2006 02:09 AM
Cross compiled kernel-2.6.13 for x86-64 arch stops booting under Slackware-10.1 Basel Slackware 4 09-09-2005 01:57 PM
problems booting compiled 2.6.11 kernel monkeyman2000 Debian 7 05-28-2005 08:16 PM
Compiled Custom Kernel booting problem _flaab_ Mandriva 3 11-13-2003 07:34 AM
console resolution will not change for newly compiled kernel meat-head Linux - Newbie 3 05-09-2002 10:55 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 04:18 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration