I use a acer Travelmate 6493 whith slackware64 14 and i was affected by the same problem.
I've appended to my lilo.conf the nomodeset and with that i've succeeded to log in in console mode, and run slackpkg update and slackpkg upgrade-all.
then i use the command /usr/share/mkinitrd/mkinitrd_xommand_generator.sh -k 3.2.45 | bash and run lilo again after deleting the nomodeset in lilo.conf.
After reboot the problem was solved.

Dell Inspiron 1750, (64-bit laptop), wget the rebuilt kernel packages from OSU, upgradepkg *.t?z, run lilo, init 6, run level 3 comes up like normal, startx does it's thing, all is well that ends.

Well, I decided to try the updated 3.2.45 kernel packages but the issue I had (see quote below) still remains. I guess my problem isn't related after all.

I'm going back to the 3.8.13 kernel for now.

Same here - system is a i3-based Lenovo x121e.

Actually this problem appeared before 3.2.45, because not too long ago I upgraded my other i5-based system from 3.2.29 to 3.2.44 (hoping it would fix an unrelated USB problem - it didn't), resulting in lots of graphical glitches in XFCE and a full system freeze after about a day of usage.

Back to 3.2.29 for me.

You could also try out the latest 3.4 series on 14.0. In extra/ there is already a config file for 3.4.

I considered that but since the 3.8 series is working well I haven't bothered testing 3.4 yet but sure it is certainly another option. I'm also slightly put off by the comments in Pat's README. I have no idea if that or any other issues are fixed, so it seems safer to stick with 3.8 series that is already fairly well tested by the -current users.

Really a shame however that these regressions have slipped into the 3.2 series. This isn't something Pat should have to worry about.

P.S. I think you meant testing/, rather than extra/.

I was just reading through some of the backlog in the ##slackware irc channel. It sounds like one of the users there has the same problem that Cesare and I do.

Note: The above is edited, just to include the key points

Unfortunately, I was away at the time so I could not suggest he try the latest 3.8.13 kernel from -current.

Out of curiosity I tried the 3.4.47 kernel using Pat's generic config from testing. No X freezes, however my wireless card wasn't working automatically as it was under 3.8.13, meaning I had to install broadcom-sta to get it to work (I was also using broadcom-sta under 3.2.29). Additionally, my machine does not suspend on closing the laptop lid as it does with the 3.2.x and 3.8.x kernels, so I'll reckon I'll just go back to 3.8.13 again.

After successful upgrade of a 64-bit Dell Inspiron 1750 (and two 32-bit Dell Dimension 8400's) to 3.2.45 (from the "Intel-fixed" packages with wget ftp://ftp.osuosl.org/pub/slackware/s...linux-3.2.45/* -- the 64-bit boxes have Intel 4 Series graphics, the 32-bit boxes have old ATI Radeon X300SE cards -- I upgraded my main work system, a Dell Optiplex 780. The 32-bit boxes have 4G RAM, the 64-bit have 8G RAM (which doesn't matter one way or the other).

No problems: reinstalled VirtualBox-4.2.12-84980-Linux_amd64.run (the kernel modules, of course, went bye-bye with the upgrade), no need to reinstall Oracle_VM_VirtualBox_Extension_Pack-4.2.12-84980.vbox-extpack or redo the Guest Additions (they're in the virtual machine, not in the system). USB stuff works just fine, everything else works just fine, PostgreSQL and MySQL work just fine.

I do keep my systems at stable, applying all patches as they come along, so I'm running the default huge kernel; I don't mess with the kernel (so no initrd problems) -- just run lilo and away we go.

No runs, no drips, no errors; I'm a happy camper -- wasn't too overjoyed with the "Intel problem," but what the heck, stuff happens.

Everything works if you let it.

Exactly the same here with an i3-based box with mini-ITX Intel board.

With kernel 3.2.29 I experienced system freezes, which seemed to be related to USB. Since upgrading to 3.2.45 I have Xorg issues and eventually system freezes with both Xfce and KDE, while everything seem to be fine in runlevel 3.

Now I'm going to try Patrick Volkerding's config for 3.4.x, or maybe I'll go straight to -current 3.8.13.

Philip

The -current kernel (3.8.13) is working really nicely for me.

Thank you ruario, I'm compiling a huge 3.4.47 right now, but I think I'll try 3.8.13 as well. I guess the pre-compiled 3.8.13 image won't work on 14.0, right? Did you re-compile it using the config file found in current or did you edit your own?

Kind regards,
Philip

I only complied 3.4.47 (generic) since there is no package, for 3.8.13 I just used the packages from -current on 14.0. No problems.

EDIT: I also compiled up 3.9.4 and it seemed fine as well.

1 members found this post helpful.

Totally noob question... but can I upgrade my kernel to 3.8.13 without upgrading everything else to current? I just want to find the best and most stable kernel for my machine while sticking with stable Slackware64-14.

You can, but if you use the kernels in -current you'll be unable to compile kernel modules for it, since the kernel won't load modules compiled with a different version of gcc. If this is a concern, it is pretty easy to install the kernels from -current and then recompile the kernel and modules from one of the config files and switch to the newly compiled versions.

3 members found this post helpful.