-   Slackware (
-   -   Is it possible to slow boot messages down? (

clifford227 09-29-2012 06:22 PM

Is it possible to slow boot messages down?

Im trying to install Slack 14 to my netbook, but part way in and after some scrolling of text, the screen goes black.

Is there a way of finding out what went wrong?

yilez 09-29-2012 06:25 PM

I believe that the pause|break key is what you're looking for, but it has been a while since I tried it out.

NyteOwl 09-29-2012 06:30 PM

It may be a video driver issue, or soemthing else. What netbook, chipset?

bnguyen 09-29-2012 06:45 PM

Did it happen with you all the time? I sometimes have the same issue on an rather old laptop, but not always. Maybe newer kernels do not work well with some old hardware.

My solution for this was installing a GUI log-in manager (I used slim). It always appeared at the end of the boot process.

About your question in the title, I believe you can use ctrl-s/ctrl-q combinations.

clifford227 09-29-2012 06:48 PM

Its a Samsung N102s using the Intel Cedarview (GMA3600) PowerVR 545 graphics core. I know there was a problem with this chip and kernel support, but I thought it had been resolved in 3.2x kernels.

*EDIT* Although reading this:


make sure CONFIG_DRM_GMA500 and CONFIG_DRM_GMA3600 is on in kernel
I may have to set those kernel options.

But Im not sure how to do that, without first being in the system.

syg00 09-29-2012 09:48 PM

You have my sympathy. I (unfortunately) have responsibility for a netbook that uses the GMA500. What a bloody fiasco (on Intels behalf IMHO). Alan Cox' recent work with the driver are starting to bear fruit, but it's a crap chip - hopefully yours is better.
Try nomodeset on the kernel line to see if a basic VESA display will get you the messages.

TobiSGD 09-29-2012 10:09 PM

I just looked and the 3.2 config does not have the GMA3600 option at all, but in the config files for the huge kernels in /testing it is enabled by default. So after trying it with the nomodeset option I would recommend to go for the 3.5 kernel instead of 3.2.

qweasd 09-29-2012 10:44 PM

A really slow computer will do it.

clifford227 09-30-2012 03:42 AM

On the Lilo screen I did 'boot: slackware.14 nomodeset'

(slackware.14 being my install name).

It started the boot process, but unfortunatey it produces the black screen also.

How would I go about installing the newer 3.5 kernel?

*EDIT* I've compiled a kernel before so that shouldnt be a problem, its just getting into the system to do it. I need to use the slackware install dvd, can you give me any advice on that?

clifford227 09-30-2012 06:36 AM

I've downloaded the 3.5.4 kernel form and moved and decompressed that into to a folder on my install's root partition.

I've also transfer the 3.5.4 huge kernel config from the slackware dvd into the decompressed kernel folder.

However, when I try to build the kernel by typing 'make', it gives me an error:


bash: make: command not found

TobiSGD 09-30-2012 08:16 AM

Do I understand that right that you can boot from the install-DVD without that problem? If so, chroot into the installed system, then start the compile action, install the new kernel and don't forget to run lilo after you have changed lilo.conf.

clifford227 09-30-2012 09:21 AM


Yes I can boot from the install DVD to access my root partition.

I will look into chroot.

Woodsman 09-30-2012 01:42 PM

Not exactly related but the huge kernel will lock hard on my system with my TV card installed. Has done that for years with all past releases. The only way I can boot into my system with the huge kernel is either remove the card or blacklist the module. I have no problem with a custom built kernel.

I share this because you might be experiencing something similar, although not necessarily a TV card. :)

Didier Spaier 09-30-2012 03:02 PM

I guess it is a conflicting drivers problem, of the kind that using a generic kernel usually can solve. But of course you knew that before I did...

All times are GMT -5. The time now is 09:13 PM.