LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 05-24-2003, 03:56 PM   #1
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Rep: Reputation: 0
2.4.20-13.9 kernal question.


I should also post in success stories as the Redhat 9 distro installed flawlessly on my Athlon 700 system. All plugins installed smoothly.

The problem I have now is when I did a update to the existing 2.4.20-6 to the 2.4.20-13.9 kernal, I cannot mount data or music cd's. Rebooting into the original kernal they mount successfully.

Anybody have any ideas?

note: I have checked several cdrom drives to eliminate the possibility of a defective drive.
 
Old 05-24-2003, 07:49 PM   #2
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
Check modules

Check to see if /lib/modules/2.4.20-13.9 exists.

If so, then check /lib/modules/2.4.20-13.9/modules.dep to see if the proper CD modules are listed.
 
Old 05-24-2003, 09:17 PM   #3
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Original Poster
Rep: Reputation: 0
Re: Check modules

Quote:
Originally posted by jailbait
Check to see if /lib/modules/2.4.20-13.9 exists.
Yes... It does exist.

Quote:
Originally posted by jailbait
If so, then check /lib/modules/2.4.20-13.9/modules.dep to see if the proper CD modules are listed.
modules.dep exists.... And appears to be identical to the other kernel version modules.dep. The same drivers are listed in both.

I believe the cdrom is enabled... but the actual media (cd) is not identified as being loaded in the cdrom. (no moutable media detected?) type of error. If you need the exact error I will be more than happy to reboot into the other kernel and quote it.

I really appreciate your help... So far, from the little that I have used Linux, I'm quite impressed.
And this forum has been great in bringing me up to speed. Thank you for taking time in helping me.
 
Old 05-24-2003, 09:37 PM   #4
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
boot parameters?

If you are using a cd-rw then you need to pass the kernel a parameter that says append="hdb=ide-scsi" where hdb is the address where your cd resides. This parameter is passed by your bootloader, either grub or lilo, to your kernel when the kernel is booted. It is possible that your boot loader is passing the parameter to the old kernel but not the new one.

If you are using lilo you can check /etc/lilo.conf to see if both kernels are
booted correctly. I don't know what the equivalent grub file is.
 
Old 05-24-2003, 10:12 PM   #5
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Original Poster
Rep: Reputation: 0
No cd-rw... just a plain jane cdrom.
The lilo.conf file is as follows:

boot="/dev/hda"
prompt
timeout="50"
message=/boot/message
root=/dev/hdb2
default=2.4.20-6

image="/boot/vmlinuz-2.4.20-13.9"
label="2.4.20-13.9"
root="/dev/hdb2"
read-only
initrd="/boot/initrd-2.4.20-13.9.img"

image="/boot/vmlinuz-2.4.20-6"
label="2.4.20-6"
root="/dev/hdb2"
read-only
initrd="/boot/initrd-2.4.20-6.img"

image=/usr/src/linux/arch/i386/boot/bzImage
label="Linux_Compiled"
root=/dev/hdb2
read-only
optional

other=/dev/hda1
label="Windows95"


For now, I have the default set to the original kernel.
 
Old 05-24-2003, 10:27 PM   #6
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
Not that it solves your problem but just to let you know - red hat network work auto updating to the 13.9 caused me no end of problems too although not your particular one. Mozilla crashing, no sound. network not shutting down etc. Basically there is something seriously flawed in the update - and amongst other things RPM causing madness was enough to make me dump it - Slackware here I am - my questions will be forthcoming
 
Old 05-24-2003, 11:27 PM   #7
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
experiment with cdrom.o

I see nothing in your /etc/lilo.conf file to show why your two kernels treat the cdrom differently. I went to the following web site which describes your
2.4.20-13.9 kernel in detail looking for differences in the way that the cd is
handled.

http://ftp.wss.yale.edu/rpm2html/rh9...13.9.i386.html

I found the following note in the changelog:
* Mon Jan 22 2001 Erik Troan <ewt@redhat.com>
- switched ide-cd back to a module in all x86 kernels

I assume this to mean that in 2.4.20.6 the plain jane cd-rom driver,
cdrom.o, is compiled into the kernel but in 2.4.20-13.9 cdrom.o is a loadable module. But I could be mistaken and it is loadable in both kernels.

To check whether this assumption is correct you could look for the following two loadable modules:
/lib/modules/2.4.20-6/kernel/drivers/cdrom/cdrom.o
/lib/modules/2.4.20-13.9/kernel/drivers/cdrom/cdrom.o

Then perform the following experiment on both kernels:
------------------------------------------------------
boot

Log in as root

Issue the lsmod command which will list all of the loadable modules that are actually loaded. Modules that are compiled into the kernel will not appear in the lsmod list. Write down the result

Mount, or try to mount, the cd.

Issue the lsmod command. Write down the result.
-----------------------------------------------------

If cdrom.o is not being loaded either at boot or at mount in kernel 2.4.20-13.9 then we are on the right track.

If cdrom.o is not being loaded then the most likely culprit is a bad
/boot/vmlinuz-2.4.20-13.9.img

I am going to bed.
 
Old 05-25-2003, 12:35 PM   #8
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
If cdrom.o is not being loaded either at boot or at mount in kernel 2.4.20-13.9 then we are on the right track.
cdrom.o loads in both kernels when the cdrom attempts to mount.

It does not load in either kernel at boot.

As an experiment (I'm still somewhat clueless with the workings of Linux) I renamed the driver in 2.4.20-13.9 and copied the old kernel driver over. Did a reboot... this time around nothing would load. Is the cdrom.o driver unique to each kernel version? Could the new driver be corrupt?
 
Old 05-25-2003, 06:15 PM   #9
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
compile a kernel?

----------------------------------------------------
Is the cdrom.o driver unique to each kernel version?

A driver might be the same from one kernel version to the next
or it could be different.

What is unique is each kernel compile. The driver modules and
the kernel must all be compiled togather in the same compile.
So any loadable module that you copy from one compiled kernel to
another is extremely unlikely to work, even if they
are the same release number.
----------------------------------------------------
Could the new driver be corrupt?

Possibly, the only way to tell is to recompile the kernel
and try again.
----------------------------------------------------

The modules.dep file tells the kernel what loadable modules are
available.

The .img file is where the compiler puts the displacements of the
various kernel entry points so that the loadable modules can
communicate with kernel routines just as if the loadable modules
were compiled into the kernel. With this arrangement the loadable
modules, such as cdrom.o, can be compiled as part of the kernel or
as loadable and work either way.

By process of elimination we are getting to the point where
the only thing that has not been checked out is the .img file.
The only way that I can think of to check out the .img file
is to recompile the exact same kernel source and see if the new
kernel works.

Looking_Lost gave some evidence that the process of loading
modules was broken in his 2.4.20.13.9 kernel. The things that he
cited as not working are things that most people would run as
loadable modules.

So maybe Red Hat put out a badly compiled kernel. That is not
certain at this point. You might check the Red Hat support page
for problems with 2.4.20.13.9. But I think the next step in the
debug process is to abandon your 2.4.20.13.9 and compile a kernel.
You could download the Red Hat source for 2.4.20.13.9 and compile it
yourself. Or you could download the 2.4.20 kernel (latest stable)
source from:

http://www.kernel.org/

and configure and compile it yourself.

kernel 2.4.21 is up to rc3 and is close to having a final release.
Red Hat might compile and release 2.4.21 kernels. Or you
could download 2.4.21 and compile it yourself when it is available.

The first time you compile a kernel yourself it is a real job
because you have to configure every single kernel option, many
of which you never even heard of before. After your first compile things
are a lot easier because you are just making changes to an existing
configuration and your changes are in areas you are working with.

Once you get a kernel compiled then installing it is very similar
to the way that you installed 2.4.20.13.9

Last edited by jailbait; 05-25-2003 at 06:20 PM.
 
Old 05-25-2003, 08:38 PM   #10
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Original Poster
Rep: Reputation: 0
Compiling a kernel.... Hmm... I don't think my skill level with Linux is that good yet, but I'm willing to try.

How about I reinstall the Redhat rpm first. I have a feeling the update may have been flawed.
If this is the case, I will need to "uninstall the updated kernel". Is there a procedure for this? I have already downloaded the rpm but the install fails giving me the message that the package is already installed.

btw - I really do appreciate your help! I have most definitely learned valuable lessons from your posts and hope to learn more.
 
Old 05-25-2003, 08:54 PM   #11
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
man rpm

Look at the options in man rpm, specifically:
rpm -e packagename
rpm -U filename

Read the entire man rpm while you are at it, if you have the patience.
 
Old 05-26-2003, 12:24 PM   #12
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Original Poster
Rep: Reputation: 0
Quote:
Read the entire man rpm while you are at it, if you have the patience.
Won't hit the bestsellers list anyday soon, but read it anyway.

Used the following to repair the kernel install:
rpm -i --replacepkgs kernel-2.4.20-13.9.i386.rpm

Used the [e] switch too. Most definitely something wrong with that kernel. Will most likely send RH a bug report.

I want to thank you all for your help and I will most definitelty start reading up on how to compile my own kernel.

Again Thank you!
Til Later, Peace
 
Old 06-03-2003, 01:38 PM   #13
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
Red Hat advisory

Red Hat has reported a lot of bugs in their athlon kernels, including 2.4.20-13.9.

http://linuxtoday.com/security/2003060302326SCRHSW
 
Old 06-03-2003, 08:14 PM   #14
Jmagick
LQ Newbie
 
Registered: May 2003
Distribution: RH 9
Posts: 12

Original Poster
Rep: Reputation: 0
Thanks... I downloaded the new kernel, but still have the same problem.

Got to thinking about why it doesn't work correctly with my cdrom...
Both kernel upgrades were for the athlon processor (I have a 700mhz athlon processor in my machine) How would I find which rpm was used in the original installation? There are 3 rpms on the distro disk ie- i586, i686, and athlon. The reason why I'm asking, the motherboard was sent to me to test a couple of years ago. Was very new and cutting edge at the time. Is it possible the i686 rpm was used in the original installation and correctly indentifies the motherboard?

Just a thought...

Again thanks for checking!
 
Old 06-03-2003, 09:27 PM   #15
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
Try rpm

I assume that you are still using the original installed kernel because you could not get the replacement to work.

You can use the following command:

rpm -qa | less

to find the name of every rpm package installed. Look through the names and see if you can find the name of the original kernel package that you installed.
 
  


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
kernal/boot question milesstandish Fedora 1 07-04-2005 04:17 PM
Fedora 3 and latest kernal question MagusYilie Linux - Distributions 3 04-28-2005 01:31 PM
Kernal modules on a Newly Compiled Kernal sethgeekx86 Slackware 4 05-04-2004 12:08 AM
Help! Configuring Kernal failed, GRUB can't boot new kernal, help! sabaka Linux - Newbie 4 09-16-2003 10:12 PM
Kernal Question HoRrIdPrObLeMs Linux - Newbie 1 03-19-2002 04:37 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 01:50 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