LinuxQuestions.org
Help answer threads with 0 replies.
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 07-09-2007, 03:38 PM   #1
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Slackware 12 boot error revisited


Hi,

Slackware 12.0 'Invalid module format' post I had a few problems with module symbols and 'Invalid module format'. I had blacklisted the symbol specific modules kernel errors. I attempted to blacklist the 'sunrpc.ko & lockd.ko' modules to no avail. So I decided to re-compile.

A good practice, I kept my known working kernel & specifics intact in my 'lilo.conf'. I modified the '/usr/src/linux/.config' to suit my needs. I then modified the '/usr/src/linux/Makefile' > 'EXTRAVERSION = .51-smp' so as to create a unique compile. I then do a compile. Do the setup for the new kernel image.

I rid myself of the problems, so it seems. I do most of my maintenance remotely (ssh), I went to the server room and decided to look at the new box at the console. Some of my devices were not recognized. Simple omission(s). At least I think so. So I reboot to start the old kernel, vmlinuz-generic-smp-2.6.21.5-smp. Well I got a kernel panic.

No biggy! Just reboot the new one. More devices dropped, /dev/sda2.
Created the initrd with;
Code:
#mkinitrd -c -k 2.6.21.5-smp -m ext3 -f ext3 -r /dev/hdb3
I edited the lilo.conf to include the initrd;

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.21.5-smp
  initrd = /boot/initrd.gz
  root = /dev/hda3
  label = Linux
  read-only
# Linux bootable partition config ends
Notice that I don't use the link to vmlinuz in boot!
Do a 'lilo -v -t -b /dev/hda' to test, no errors.
The do a 'lilo -v -b /dev/hda3', writes 'MBR'

I then went to the /etc/modprobe.d/blacklist an removed all the before added modules via commenting out;

Code:
excerpt /etc/modprobe.d/blacklist;
#07-09-07 15:00
#comment out all to check a suspicion
#
#07-08-07 gws 15:30
#boot error message;
# system trying to load the USB modules
# which are already compiled into the "smp" kernel,
# "ohci-ecd" and "ehci-ecd"
#blacklist ohci-ecd
#blacklist ehci-ecd
#blacklist uhci-hcd
#blacklist ehci-hcd
#blacklist usbhid
#blacklist usb_storage
#blacklist i2c_core
#blacklist i2c_viapro
#
#07-08-07 gws 17:30
#still no-joy will re-compile to see
#blacklist sunrpc
#blacklist lockd
Now, here's the kicker. I reboot and no module symbol errors. No 'Invalid module format' for the 'sunrpc.ko & lockd.ko. The '/lib/modules/2.6.21.5-smp/' was never touched. A 'dep -a' was done on the first reboot. The devices were recognized with no problems.

The system is fully functional at this moment.

'rworkman', any ideas? The module dependency's were updated. But what would cause the symbols not to invoke the kernel use error message since nothing was changed with the original modules and kernel. The system is back to the original known state, at least I think so. I revert to the original except for the 'mkinitrd' and lilo.conf update.

Any help, suggestions?

edit: correct some grammar & spell errors

Last edited by onebuck; 07-10-2007 at 07:39 AM.
 
Old 07-11-2007, 10:17 AM   #2
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,559

Rep: Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351Reputation: 1351
That's exactly the behavior that I would expect. :-)
To clarify, and maybe I wasn't clear originally, those invalid symbols and -EEXIST errors should only occur if you're using the huge{,smp} kernels due to the fact that the affected modules are actually built into those kernels. On the generic{,smp} kernels, the modules should (and do, according to your latest round) load without problems, as that's how they're intended to work.
In short, if you were not using one of the huge* kernels when you had the previous errors, I have no idea - that's unexplainable in my mind :/
 
Old 07-12-2007, 09:18 AM   #3
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,922

Original Poster
Blog Entries: 44

Rep: Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158Reputation: 3158
Hi,

Thanks for the response. I was using the smp kernels at all times. I really don't see why this occurred myself. I'm going to go through another install on this very machine to see if the problem comes up again. I wish to find out the problem and not pass on this one.
 
  


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
Slackware 10.2 hda2 error on boot (Bad or Duplicate Block) PastorFrederick Linux - Newbie 2 10-08-2005 08:37 AM
Slackware 10.2 hda2 error on boot PastorFrederick Slackware 1 10-07-2005 01:33 PM
Slackware 10.1 freezes at boot time without an error penguin_asylum Slackware - Installation 1 03-13-2005 01:55 PM
Slackware EBDA error on boot? sigma957 Slackware 1 07-20-2004 10:19 AM
Isolinux error during Slackware 9 install Boot RadicalGrande Slackware 3 07-09-2003 02:13 PM

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

All times are GMT -5. The time now is 03:53 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
Open Source Consulting | Domain Registration