SW12.2 bootup problems

paddeo · 12-15-2008, 05:45 PM

Did a fresh install of 12.2 today and on bootup with huge-smp-2.6.27.7 my display stays blank and then my machine starts to reboot. I have to revert to the 2.6.24.7 kernel to get it to boot, but then I get a bunch of errors about not being able to find the 2.6.24.7 modules which aren't there, and also
losing my network, printer, and sound. I tried reinstalling everything but the new kernel refuses to boot.

Any thoughts would be appreciated.

arubin · 12-16-2008, 04:40 AM

A long shot but this reminds me of the problems I had installing 12.0 on a new laptop. Trying a different kernel version solved the problem.

http://www.linuxquestions.org/questi...58#post2991658

onebuck · 12-16-2008, 07:47 AM

Hi,

Code:

excerpt from 'CHANGES_AND_HINTS.TXT';

As stated earlier, it is recommended that you use one of the generic kernels
  rather than the huge kernels; the huge kernels are primarily intended as 
  "installer" and "emergency" kernels in case you forget to make an initrd.
  For most systems, you should use the generic SMP kernel if it will run, 
  even if your system is not SMP-capable.  Some newer hardware needs the 
  local APIC enabled in the SMP kernel, and theoretically there should not be
  a performance penalty with using the SMP-capable kernel on a uniprocessor 
  machine, as the SMP kernel tests for this and makes necessary adjustments.
  Furthermore, the kernel sources shipped with Slackware are configured for
  SMP usage, so you won't have to modify those to build external modules
  (such as NVidia or ATI proprietary drivers) if you use the SMP kernel.

You should be using the generic kernel as suggested. The documentation is there so you should read it to be informed.

arubin · 12-16-2008, 08:06 AM

I also wonder what kernel is being used during the installation process. If the kernel works ok during installation wouldn't one expect it to be ok on booting?

onebuck · 12-16-2008, 06:46 PM

Hi,

Quote:

Originally Posted by arubin

I also wonder what kernel is being used during the installation process. If the kernel works ok during installation wouldn't one expect it to be ok on booting?

I suggest that you read the linked text in my reply above.

Woodsman · 12-16-2008, 10:04 PM

I discovered a way to stall the huge kernel too: https://www.linuxquestions.org/quest...26#post3378026.

Do you boot with the 'quiet' boot parameter? If you do then delete that parameter and you might be able to notice when the system stalls. In my case the system froze hard.

You should be able to use the huge kernel after installing. I have been doing that repeatedly for a couple of months while testing Current. I am doing that right now in a virtual machine with Slackware Current.

One quick trick you can try is to temporarily prevent rc.udev from running at bootup (chmod -x /etc/rc.d/rc.udev.) Your system will be in no condition to run all of your hardware, but you should be able to confirm that you can boot with the huge kernel. If you get that far then start looking fro cranky modules.

shadowsnipes · 12-17-2008, 11:38 AM

Did you copy over the new rc.udev file? The old one cannot be used as mentioned in the CHANGES_AND_HINTS.TXT. Please see the upgrade HowTo in my signature. Even though you did a fresh install many of the tasks you need to do/check are the same.