LinuxQuestions.org
Visit Jeremy's Blog.
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 08-22-2006, 01:35 PM   #1
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 200

Rep: Reputation: 30
2.4.33.1 kernel won't boot


I just compiled and installed the 2.4.33.1 kernel. This I think is my 10th kernel compile, so I am still relatively new. When I try to boot, here is the lengthy error message I see:
Code:
 An error occurred during the root filesystem check.  You will now be given a chance to log into the file system in single user mode to fix the problem.

If you are using the ext2 filesystem, running the 'e2fsck -v -y <partition>' might help.
Then machince code scrolls. Then I see:
Code:
 Attempt to remount root device as read-write failed! This is going to cause serious problems.  If you're using the UMSDOS filesystem, you **MUST** mount the root partition read-write with 'rw' flag to Loadlin:

loadlin vmlinuz root=/dev/hda1 rw (replace /dev/hda1 with your root device)

Normal bootdisks can be made to mount a system read-write with the rdev command: rdev -R /dev/fd0 0

You can also get into your system by using a boot disk with a comman dlike this on the LILO promt line: (change the root partition name as needed)

LILO: mount root /dev/hda1 rw

Please press ENTER to continue, then reboot and use onr of the above methods to get into your machince and start looking for the problem.
Here is my lilo.conf:
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
compact
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = normal
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda3
  label = Linux-2.4.31 
  read-only
# Linux bootable partition config ends
image = /boot/bzImage-2.6.17.3
  root = /dev/hda3
  label = Linux-2.6.17.3
  append = "noresume"
  read-only
image = /boot/bzImage-2.4.32
  root = /dev/hda3
  label = Linux-2.4.32
  read-only
image = /boot/bzImage-2.4.33.1 
  root = /dev/hda3 
  label = Linux-2.4.33.1
  read-only
Here is what the lspci command produces:
Code:
invert@314:~$ su
Password: 
root@314:/home/invert# lspci
00:00.0 Host bridge: Intel Corporation 82845G/GL[Brookdale-G]/GE/PE DRAM Controller/Host-Hub Interface (rev 01)
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
01:05.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
01:07.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 09)
root@314:/home/invert# exit
exit
invert@314:~$
Here is the link to the .config I used to compile my kernel: http://pastebin.com/773366

I updated to -current one or two days ago.

edit1:added lilo.conf + lspci + .config contents

Last edited by Drone4four; 08-22-2006 at 01:44 PM.
 
Old 08-22-2006, 01:44 PM   #2
chess
Member
 
Registered: Mar 2002
Location: 127.0.0.1
Distribution: Slackware, OpenBSD, FreeBSD
Posts: 732

Rep: Reputation: 173Reputation: 173
I don't know if this is the same issue or not, but Pat mentioned that 2.4.33.1 was not working with current. From the -current changelog a few days ago (8/19):

"k/kernel-source-2.4.33-noarch-2.tgz:
Updated the default .config to include SATA support.
Oh, and yes I did see 2.4.33.1. Thanks for letting me know ;-), but that
kernel does not seem to be booting here so I'll stick with 2.4.33 for now."
 
Old 08-22-2006, 01:48 PM   #3
Franklin
Senior Member
 
Registered: Oct 2002
Distribution: Slackware, Windows 7
Posts: 1,253

Rep: Reputation: 55
The new kernel naming convention does not seem to agree with the 2.4 kernel series.
This was discussed on the alt.os.linux.slackware group. It's being worked on. There is a patch I believe. Check the group either directly, through google groups, or by linuxpackages.net.

Not sure the link will be correct.

google-link
 
Old 08-22-2006, 02:47 PM   #4
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 200

Original Poster
Rep: Reputation: 30
Thanks you two. That clarifies things for me. =D
 
Old 08-23-2006, 12:16 AM   #5
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,928

Rep: Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182
Here's Pat reply of my emails

Quote:
> Hi Pat,
>
> updated kernel 2.4.33.2 has arrived. Maybe this version will boot > on your machine and others as well since Willy has reverted some
> commits on it

No, it will boot because I spent an entire day fixing an issue in glibc
that was the boot problem. It wasn't the kernel.

And yes, I know about 2.4.33.2. I've been in frequent contact with
Willy over the last week. My name is even in the kernel's release
announcement (along with an explanation of the glibc issue)...
 
Old 08-23-2006, 04:53 AM   #6
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 200

Original Poster
Rep: Reputation: 30
I just compiled 2.4.33.2. I get the same error as before. Do you think the error occurs becasue I miss configured my kernel? Or does it crash becasue of the same error Pat V talks about for 2.4.33.1?

I used the same config script as before (see the above pastebin link). My new lilo.conf looks like this:
Code:
  # LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
compact
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = normal
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/hda3
  label = Linux-2.4.31 
  read-only
# Linux bootable partition config ends
image = /boot/bzImage-2.6.17.3
  root = /dev/hda3
  label = Linux-2.6.17.3
  append = "noresume"
  read-only
image = /boot/bzImage-2.4.32
  root = /dev/hda3
  label = Linux-2.4.32
  read-only
image = /boot/bzImage-2.4.33.1
  root = /dev/hda3 
  label = Linux-2.4.33.1
  read-only
image = /boot/bzImage-2.4.33.2
  root = /dev/hda3
  label = Linux-2.4.33.2
  read-only
 
Old 08-24-2006, 06:41 PM   #7
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 200

Original Poster
Rep: Reputation: 30
There's all this talk about a fix for glibc should enable 2.4.33.1/2 to boot. I just upgraded to current (again). I'll brb (hopefully) on the new kernel.

edit: 2.4.33.1 and 2.4.33.2 still will not boot. I really think the problem is unrelated to the glibc fix delivered by Pat V. The problem I think has to do with the incorrect way in which i compiled my kernel.

Last edited by Drone4four; 08-24-2006 at 06:47 PM.
 
Old 08-24-2006, 06:47 PM   #8
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,402

Rep: Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647
Pat patched glibc for Slackware 10.2 already (see http://www.slackware.com/changelog/stable.php?cpu=i386 Tue Aug 22 15:20:32 CDT 2006). Have faith, it will most likely be fixed in -current too, soon(ish).

Eric
 
Old 08-24-2006, 06:52 PM   #9
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 200

Original Poster
Rep: Reputation: 30
Quote:
Originally Posted by Alien Bob
Pat patched glibc for Slackware 10.2 already (see http://www.slackware.com/changelog/stable.php?cpu=i386 Tue Aug 22 15:20:32 CDT 2006). Have faith, it will most likely be fixed in -current too, soon(ish).

Eric
Is this glibc patch in current or am I to get this patch elsewhere?
 
Old 08-24-2006, 09:26 PM   #10
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,928

Rep: Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182Reputation: 1182
here's a reply from Pat itself

Quote:
Willy Sudiarto Raharjo wrote:
> Hi Pat,
>
> i saw an update on the -stable changelog, but the -current
> wasn't updated with the patched glibc. Will it be there in
> few hours or so??

Probably, but on -current there's a lot more to the issue as I have to upgrade all the kernels, and then compile glibc against the latest 2.6.x kernel. It was all ready to go, and then 2.6.17.11 shipped. It should be ready today, but it could be late. Hard to say for sure...

> The kernel problem lies to the kernel naming?? I thought
> Willy never thought about that when he generate the 2.4.33.x > new naming

He shouldn't have had to. The problem was that glibc only cared about 3 kernel numbers and it knew to get rid of things like -pre1, or -rc3 (with a '-'), and would see 2.4.33-1 as 2.4.33. However, for 4 part kernel versions w.z.y.z, it would cut the wrong end off. 2.4.33.2 was being seen as version 4.33.2, so then glibc would figure the kernel had NPTL support.

I talked Willy out of changing the naming scheme because it wasn't his bug, and working around it like that wasn't the right way to fix the issue IMHO. Anyway, glibc without the patch probably also thinks 2.6.17.11 is 6.17.11, but that matters a lot less there. :-)

Take care,

Pat
 
Old 08-25-2006, 05:12 AM   #11
Drone4four
Member
 
Registered: Feb 2006
Distribution: Ubuntu, Slackware. Gentoo
Posts: 200

Original Poster
Rep: Reputation: 30
Thanks willysr, that explains ALOT. It looks like we'll have to wait a few days for -current to be updated with the corrected glibc.

edit:sp

Last edited by Drone4four; 08-27-2006 at 11:19 AM.
 
Old 08-25-2006, 05:48 AM   #12
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,402

Rep: Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647Reputation: 5647
Quote:
Originally Posted by Drone4four
It looks like we'll have to wait a few days for -current to be updated with the updated glibc.
FYI: It is already there: Slackware 11 Release Candidate 3 with the glibc update, and LOTS of other exciting stuff.

Eric
 
Old 08-26-2006, 08:20 AM   #13
linuxhippy
Senior Member
 
Registered: Sep 2004
Location: Philadelphia, PA
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,205

Rep: Reputation: 47
I'm not sure what the solution is or what download link is being referred to. I just compiled kernel 2.4.33.2 using my 2.4.31 .config file. It doesn't boot and I get the same error as above. Please help!
 
Old 08-26-2006, 07:17 PM   #14
linuxhippy
Senior Member
 
Registered: Sep 2004
Location: Philadelphia, PA
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,205

Rep: Reputation: 47
Is this the solution?

http://slackware.it/en/pb/package.ph....4.33.2-i486-1
http://slackware.it/en/pb/package.ph....33.2-noarch-1
http://slackware.it/en/pb/package.ph....4.33.2-i386-1

They're from the Slackware current packages page....would they boot on Slack 10.2?
 
Old 08-26-2006, 07:28 PM   #15
win32sux
LQ Guru
 
Registered: Jul 2003
Location: Los Angeles
Distribution: Ubuntu
Posts: 9,870

Rep: Reputation: 379Reputation: 379Reputation: 379Reputation: 379
Quote:
Originally Posted by linuxhippy
I'm not sure what the solution is or what download link is being referred to. I just compiled kernel 2.4.33.2 using my 2.4.31 .config file. It doesn't boot and I get the same error as above. Please help!
the solution is to patch your glibc source code and recompile, or install a patched glibc binary package... FYI this is the patch for glibc 2.3.5 that was used for slackware 10.2:
Code:
--- ./sysdeps/unix/sysv/linux/dl-osinfo.h.orig	2004-12-16 21:31:50.000000000 -0600
+++ ./sysdeps/unix/sysv/linux/dl-osinfo.h	2006-08-21 23:00:49.000000000 -0500
@@ -53,6 +53,9 @@
 	int parts;							      \
 	char *cp;							      \
 	struct utsname uts;						      \
+	int dotsfound = 0;						      \
+	int versionindex = 0;						      \
+	char *choppoint;						      \
 									      \
 	/* Try the uname syscall */					      \
 	if (__uname (&uts))					      	      \
@@ -72,8 +75,34 @@
 	else								      \
           buf = uts.release;						      \
 									      \
+	/* We are only interested in the first three kernel numbers, so */    \
+	/* chop off anything past that: */				      \
+									      \
+	choppoint = buf;						      \
+	while (1)							      \
+	  {								      \
+	    versionindex++;						      \
+	    if (versionindex == 63) break;				      \
+	    if (*choppoint == '.') dotsfound++;				      \
+	    choppoint++;						      \
+	    if (dotsfound == 2)						      \
+	    {								      \
+	      if (*choppoint == '0' || *choppoint == '1'		      \
+		|| *choppoint == '2' || *choppoint == '3'		      \
+		|| *choppoint == '4' || *choppoint == '5'		      \
+		|| *choppoint == '6' || *choppoint == '7'		      \
+		|| *choppoint == '8' || *choppoint == '9')		      \
+		continue;						      \
+	      else							      \
+	        {							      \
+	          *choppoint = 0;					      \
+	          break;						      \
+	        }							      \
+	    }								      \
+	  }								      \
+									      \
 	/* Now convert it into a number.  The string consists of at most      \
-	   three parts.  */						      \
+	   three parts.  Now it does, anyway.  ;-)  */			      \
 	version = 0;							      \
 	parts = 0;							      \
 	cp = buf;
your best bet is to simply download and install the latest glibc packages from the /patches directory on the FTP server...

ftp://ftp.slackware.com/pub/slackwar...ches/packages/

Last edited by win32sux; 08-26-2006 at 07:31 PM.
 
  


Reply

Tags
kernel, slackware


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
DSL Kernel Wont detect Flash drive on boot, cant boot =( Javahulk Linux - General 1 03-24-2005 03:59 PM
Kernel update boot problems, no boot loader StaticSage Red Hat 2 01-09-2004 07:05 AM
CAVEAT: /boot/kernel.h & how not to clobber your kernel sources (Conectiva, Red Hat) JCCyC LinuxQuestions.org Member Success Stories 0 08-07-2003 08:49 AM
Kernel Compile Boot Loader? boot disk? SPMcRuube Linux - Newbie 3 12-03-2002 08:02 PM
What to do with /boot/System.map on dual Kernel boot? cathodion Linux - General 2 05-17-2002 12:19 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:01 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration