I that I know is that the upgraded kernel doesn't play at all nicely with the latest fglrx driver-it won't even install

We will probably spend more time discussing the necessity of rebuilding an initrd than it would take to simply do it.

However, if the modules were the same, then why did Pat release a new modules package? That implies that there might/should be some difference. Me? I like my system to come up when I reboot it versus muttering bad words when it doesn't because I cut a corner during an upgrade. YMMV.

Most likely he was just following his usual procedure for putting new kernel packages out and didn't give it much thought. I would have done the same.

Also, like you I would always update the kernel and modules as a pair, regardless of whether I thought it was technically necessary or not.

Just to be clear, I was not suggesting that anyone shouldn't, I was just wondering out-loud about whether it was 'technically' necessary.

lol. I wish I hadn't said anything now! ;)

I don't know about anybody else, but like I said, mine's working OK with the new generic kernel and the old initrd.

:D

Aww, come on. I want to argue about it some more! (not really)

I ran when I first installed slackware on this computer and for some reason it didn't pick up on all the modules needed for the initrd to boot. I know how to find the modules, I just got lazy and took the gamble. If it had been a version change, I wouldn't have took the gamble, on second thought, maybe I will on the next version change just to see what would happens, this is a play toy anyways and not a production machine.

That hasn't been my experience at all. On my test system (which has a 4850) the only recent recompile I had to do was against the X update. The kernel update didn't cause even a slight hiccup.

So... during the "slackpkg upgrade-all" process, where is the opportunity to configure the kernel? Now I'm afraid to run it.

There isn't an opportunity to configure the kernel because slackpkg is installing a pre-compiled kernel. There is no reason to configure it.

Near as I can figure, rob.rice confused the official Slackware kernels (which is what slackpkg deals in) with a kernel from kernel.org, which you would have to configure and compile.

No problem on my end, attribute this to PEBKAC.

I finally got around to installing the updated kernel packages. I did recreate my initrd, just because it seems the right thing to do (although it probably isn't necessary :) ), and then I reran lilo.

No problems. Everything is okay on my computer.

Regards,

I got the message
 

I manually upgraded the kernel to 2.6.35.5, because that's how I do it, and sound works; however I did receive the "KDE detected that one or more internal sound devices were removed" message. I'm using xfce4. I think the message occurred during the first run of digikam. Instead of choosing the "manage" option, I chose the "forget" option. And apparently it did, because there was no audio after that.

Upon reboot, audio was back, and the message has yet to recur, even when opening digikam.

hmm.