I'm in Linux trouble .. again!

[Horsepower]

I was running Red Hat 7 just fine, then auto-update showed a newer kernel. I installed it and now my nic, sound, and usb do not work. I am still real new at Linux, looked at some faq's about "compile" and am totally confused. Newbie style help needed.

 

[bubba]

look at your /etc/lilo.conf file, then look at the contents of the /boot directory. Is lilo pointing to the right kernel?

 

[MGMorden]

You are probably going to have to compile a new kernel either from official sources or from Redhat distributed sources (which I think should have been put into place when you upgraded, but I'm just guessing). To do this go to /usr/src/linux and type 'make menuconfig', and then use that interface to compile in support for your stuff either as modules (good idea), or if you want directly into the kernel (not so good, as it increased the kernel size). Then type 'make dep', 'make bzlilo', 'make modules', and finally 'make modules_install'. With luck you should be up and running with all your stuff again.

 

[Horsepower]

Bubba .. looked at that file, it was pointing to the old kernel. I modified it with pico, still boots to the old one. MG .. went to that directory, but there's no "Linux" there's usr/src/redhat but that command doesn't work.

 

[MGMorden]

If it was pointing to the old kernel and you modified it with pico then you have to type 'lilo' after you save lilo.conf for the settings to take effect. As for the linux not being there, that means you don't have the sources. If after running lilo your machine boots I wouldn't worry about getting them (until you've gotten a little more advanced, and then you're REALLY gonna want to setup your own kernel instead of getting a pre-built one).

 

[DFB]

After you modified lilo.conf did you remember to run LILO again? I tend to forget to do so (and it must be done for changes to take effect).

 

[bubba]

horsepower, you did the right thing, but (as the others mentioned) you just have to type 'lilo' as root to reset lilo on your system.

That oughta clear things up.

 

[Horsepower]

I get "command not recognized" when typing "lilo" as root.

 

[bubba]

then do a '/sbin/lilo'

If this happens again type 'locate lilo' and it will tell you where the command (in this case lilo) is and you can run it from there.

 

[BOFH]

Remember there is a major difference between

su

and

su -

 

[Horsepower]

su and su - ????

 

[BOFH]

do a man on su. it allows you to take over the identy of another user. if you do su - it will also load their profile including path

 

[Horsepower]

OK I guess the RedHat version on running LILO is /sbin/lilo -v .. from that I get a fatal error that there is no image of the newer kernel, it does show other lines pertaining to it though.

 

[GT1999]

Related question..

BOFH- What's the difference between /bin/su - and just "su -"? Machines at work running Slackware I have to type /bin/su - to get into root but my Slackware box, just su - works, not /bin/su -

Also, know how I can make a message at the top of the screen when somebody telnets to my machines IP addy? thx..

 

[BOFH]

Geekish Thoughts

The difference is that you have it in your $PATH on your home box, but no in your work box

 

[Horsepower]

Well I used the Red Hat cd to repair the install, now I'm back to the old kernel and everything works. I will refrain from this crap that is over my head.

 

[BOFH]

why don't you try reading this link next time before you do it again

http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html

 

[Horsepower]

Thank you, BofH, but if you notice there's nothing there about Red Hat 7. This update showed up on the Red Hat update agent. I assumed that (like the 20 or so updates I did on the system before <none being kernel>.. ) it would install automagically. I have also read many posts/sites that talk about a compiling bug in RH7, but who knows what actually went wrong.

 

[BOFH]

I don't think the procedure has changed all that much. The Update Agent is just running the RPM commands AFAIK. It does not run lilo. Also there is no compile big.