LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel Upgrade (http://www.linuxquestions.org/questions/slackware-14/kernel-upgrade-4175462879/)

tronayne 05-21-2013 09:52 AM

Kernel Upgrade
 
Don't want to hijack the earlier thread but I've gotten older and dumber by the day and I'm wondering (before I do it!)...

I'm running four servers, two 64-bit, two 32-bit, all with the default SMP kernel and nothing much messed with (so, no initrd or any of that stuff). The two 32-bit boxes are headless; I access them with SSH from my main work station.

I downloaded all the patches and did the upgradepkg *.t?z thing, all that went smoothly, no runs, no drips, no errors on one of them and am up to the point of reboot.

I'm not too clear on one thing -- /etc/lilo.conf looks right, the content of /boot looks right but the trouble reported at http://www.linuxquestions.org/questi...5/#post4955408 is making me pause. I'm thinking that I should not need to run lilo (although I don't think it'll hurt) and I can live without the sever for a day or two if necessary.

Is it really necessary to wait (a little late for that server, but for the other three)?

Is there a real problem with the default kernel update?

tronayne 05-21-2013 10:40 AM

Ah-ha!

Tried to boot it, failed, booted from the DVD, went looking, found that /etc/rc.modules was linked to rc.modules-3.2.29-smp instead of rc.modules-3.2.45-smp.

Fixed that. Hooked up a display. Booted it.

Works fine.

ruario 05-21-2013 12:08 PM

Quote:

Originally Posted by tronayne (Post 4955775)
I'm thinking that I should not need to run lilo (although I don't think it'll hurt)

You always need to run lilo if you do a kernel upgrade.

EDIT: Or is that your way of saying that you might not want/need to upgrade?

P.S. For the benefit of anyone stumbling across this [SOLVED] thread, the fact that the symlink /etc/rc.modules pointed to rc.modules-3.2.29-smp instead of rc.modules-3.2.45-smp is a red herring, as the files are identical.

allend 05-21-2013 12:43 PM

From /etc/rc.d/rc.S
Code:

# This loads any kernel modules that are needed.  These might be required to
# use your ethernet card, sound card, or other optional hardware.
# Priority is given first to a script named "rc.modules.local", then
# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".
# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY
# rc.modules script the machine will run, so make sure it has everything in
# it that you need.

Maintaining a symlink rc.modules -> rc.modules-$FULL_KERNEL_VERSION is just a convenience for editing/viewing these days.

tronayne 05-21-2013 12:44 PM

Quote:

Originally Posted by ruario (Post 4955863)
You always need to run lilo if you do a kernel upgrade.

EDIT: Or is that your way of saying that you might not want/need to upgrade?

P.S. For the benefit of anyone stumbling across this [SOLVED] thread, the fact that the symlink /etc/rc.modules pointed to rc.modules-3.2.29-smp instead of rc.modules-3.2.45-smp is a red herring, as the files are identical.

Well, I did run lilo and the thing wouldn't boot, just sat there. Did boot it from the DVD, did change the symlink, shut it down, removed the disk and it did boot and is running. Why, I don't know, but the proof of the pudding is that it's running and everything that needs to work is, red herring or not. Must be sumpin' else, but dang if I know what 'cause I didn't touch anything else.

Must be Magic someone said!

I'm not being flippant, nor am I accusing anybody of false reporting of anything. Mine works, I'm happy and that's that.

tronayne 05-23-2013 07:32 AM

To all who took the time and effort to contribute to this thread:

Excuse my stupid-head; some of us get off on a tangent and can't see the trees for the forest every now and again, and, well, it happens to me more and more these days, dang it. Hate getting old, but consider the alternative, eh.

Anyway. My two data base serves, Dell Dimension 8400's, came with Radeon graphics cards. Completely forgot that they're still in there, those (they're never hooked up to a display). My 64-bit boxes are all ordered without any sooper-dooper graphics; Intel only (they look at you funny when you tell 'em you don't want proprietary graphics 'cause you don't wanna deal with those problems). These guys are all for working, not playing, and Intel works just fine.

So, anyway, of course the kernel update worked on the 342-bit boxes, and of course the rc.modules files are identical (duh!), and of course the 64-bit boxes did the black screen thing (well, only the laptop because it's the test bed because I really don't care all that much if it works; it sits on a shelf most of the time). If I'd waited a day there would not have been a problem but when you're on a quest you haven't got the sense that good Lord gave lettuce and just jump off the bridge into the rushing waters below.

So, this morning, there's the kernel rebuild with the Intel fix sitting at OSU, Pat's notice in the change log, other folks' in the other thread saying that it works, and ruaio's fixes (thank you for those) being withdrawn in favor of Pat's and all appears to well that ends.

You'd think I'd have learned by now, eh?

ruario 05-23-2013 10:26 AM

It happens to all of us! ;)

That said, regarding this:

Quote:

Originally Posted by tronayne (Post 4957185)
ruaio's fixes (thank you for those) being withdrawn in favor of Pat's and all appears to well that ends.

I think you mean ponce's fixes (well ponce's patched/fixed kernel).

tronayne 05-23-2013 02:42 PM

Quote:

Originally Posted by ruario (Post 4957301)
It happens to all of us! ;)

That said, regarding this:



I think you mean ponce's fixes (well ponce's patched/fixed kernel).

Oh, dammit! Yes, I meant ponce's patched fixes!

Sorry about that.

mlpa 05-26-2013 06:24 PM

After updating for the last version of the kernel (3.2.45-2) a graphical issue has appeared.
When I log out from XFCE the monitor becomes black. And the tty terminal does no appear.

I have a Ati 5730 card, and the latest version of catalyst drivers.

Does anyone have a similar issue?

ahzthecat 06-03-2013 01:12 AM

Oh please tell me that fixing the symlink isn't a red herring...

I ran the kernel update yesterday on my Slackware 14 32bit system (Lenovo G555 AMD Dual Core laptop) and now I have a system that boots, I can log in at the tty prompt, but when I start X I get an unresponsive system. No mouse no keyboard no input device recognition of any sort.

Here's what I did.
First, run all pending updates (Firefox, Ruby, Thunderbird)
Next, run the xorg updates
Next, reread the readmes about the kernel patch
Next, run the firmware update
Next, run the Kernel update
Last, run Lilo and reboot

There is a message about /lib/modules/3.2.45-smp not found in the boot sequence output.

I have edited lilo to point directly at the new kernel, but the end result is the same, an unresponsive x session.


What do you think? How should I go about fixing my Slack?

ahzthecat 06-03-2013 04:13 AM

Oh heck.

I edited my lilo.conf to point at the old kernel (vmlinuz-smp-generic-3.2.29-smp), ran lilo, then rebooted. Now I have kernel panic and a system that won't boot. I've gone from kinda busted to waaaaay busted.

I can boot from the install DVD, but don't know where to go from there.
I don't want to have to reinstall...so many complicated sbopkg apps...

Help?

kkady32 06-03-2013 04:52 AM

http://blog.tpa.me.uk/2009/09/29/re-...kware-boot-cd/

zordrak 06-03-2013 05:17 AM

Use the link kkady32 provided above to add a LILO boot entry for (or replace the current one with) the hugesmp kernel. Then you can boot into the system again and start fixing what went wrong.

Make sure next time to keep an extra entry for the huge kernel in the LILO config so you can always boot into it if you screw up a kernel.

ahzthecat 06-03-2013 06:27 AM

Ahhh. Big piles of relief. I added a lilo entry for the huge-3.2.29 kernel and booted from that. Seems to be okay. What in the heck went wrong, I wonder?

Next step is to get a newer kernel rocking on this box. I've got a dual core processor so I need an SMP kernel, right?

ahzthecat 06-03-2013 06:51 AM

Good news everyone, after rebooting I ran slackpkg update and upgrade. The patch was applied successfully and now I'm back up to speed and up to date.

Thanks for your help!


All times are GMT -5. The time now is 06:54 PM.