LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-30-2011, 08:27 AM   #1
lghizoni
Member
 
Registered: Dec 2011
Location: Denmark
Distribution: Slackware, Debian
Posts: 102

Rep: Reputation: Disabled
Slackware 13.37 initialization monitor goes off


Hello,

I've been a Ubuntu user for a while, but now I'm trying to go with Slackware to get more serious.

I installed Slackware 13.37 on my machine, wich is a Dell XPS L502X, Intel i7-2670QM.

But now, in Slackware initialization the monitor goes off automaticaly and doesn't come back it all! Then I initializaed it again, this time choosing lilo, and putting 'linux init 3 nomodeset', wich works fine.

In the installation I didn't choose the default graphic resolution, choosing the 1024 configuration. I also chose the xfce desktop.

Also, the boot takes too long to initialize. Is that normal?

Can someone help me with that? I don't want to always have to choose lilo and enter 'linux init 3 nomodeset'.

Sorry, I'm a new Slackware user.
 
Old 12-30-2011, 08:33 AM   #2
lghizoni
Member
 
Registered: Dec 2011
Location: Denmark
Distribution: Slackware, Debian
Posts: 102

Original Poster
Rep: Reputation: Disabled
Slackware 13.37 boot very slow

Hello,

I've been a Ubuntu user for a while, but I want to go with Slackware to get more serious.

I installed Slackware 13.37 64 bits with no problems in my machine, wich is a Dell XPS L502X, Intel i7-2670QM.

When I boot the system, it takes too long to initialize, with long text lines os output.

Is that normal? Because it takes more than 1 minute to initialize.

Can someone, please, help me?

Sorry, I'm a new Slack user.
 
Old 12-30-2011, 08:38 AM   #3
BlackRider
Member
 
Registered: Aug 2011
Posts: 295

Rep: Reputation: 101Reputation: 101
I think you should be able to edit /etc/lilo.conf and configure the default parameters.

For example, if your lilo.conf contains something like this:

Code:
  image = /boot/vmlinuz-2.6.37.6
  root = /dev/sda1
  initrd = /boot/initrd.gz
  label = Slackware
  append = "quiet resume=/dev/sda1"
  read-only
You can add your desired parameters to the "append" section
Code:
append = "quiet resume=/dev/critdata/critswap [option1] [option2] [etc]"
Then, run lilo as root, so the changes are made effective.

EDIT: You can configure your resolution ensuring that there is an vga option active in your lilo.conf. The file contains a lot of examples, you just have to uncomment the one you need:
Code:
# VESA framebuffer console @ 1024x768x256
# I UNCOMMENT THIS ONE BECAUSE IT IS THE ONE I WANT!!
vga = 773  
# Normal VGA console
#vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769

Last edited by BlackRider; 12-30-2011 at 08:42 AM.
 
Old 12-30-2011, 08:48 AM   #4
kkady32
Member
 
Registered: Dec 2010
Distribution: Slackware64-current
Posts: 115

Rep: Reputation: 42
add "compact" in lilo.conf
 
Old 12-30-2011, 11:15 AM   #5
jimmy_page_89
Member
 
Registered: Sep 2010
Location: Turin (Italy)
Distribution: Slackware 14.2
Posts: 51

Rep: Reputation: 4
Quote:
Originally Posted by kkady32 View Post
add "compact" in lilo.conf
And don't forget to execute
Code:
# lilo -v
:P
 
Old 12-30-2011, 11:33 AM   #6
gegechris99
Senior Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 15.0 64bit
Posts: 1,161
Blog Entries: 5

Rep: Reputation: 392Reputation: 392Reputation: 392Reputation: 392
Are you using a generic kernel or the default huge kernel?

If you are using the huge kernel, try installing the generic kernel as indicated in CHANGES_AND_HINTS.TXT. Don't forget to create the initrd file by following the instructions in the indicated file:

Quote:
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd.
 
Old 12-30-2011, 12:27 PM   #7
gilead
Senior Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,141

Rep: Reputation: 168Reputation: 168
Is it pausing for long periods of time at any point? You can modify the start-up scripts to run some commands in the background.
 
Old 12-30-2011, 01:24 PM   #8
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Member response

Hi,

Quote:
Originally Posted by gegechris99 View Post
Are you using a generic kernel or the default huge kernel?

If you are using the huge kernel, try installing the generic kernel as indicated in CHANGES_AND_HINTS.TXT. Don't forget to create the initrd file by following the instructions in the indicated file:
Changing to the generic from the huge will not decrease the boot time that much. Even if you do choose to use the generic with a initrd your gain may be in the milli-seconds.

To get response you might consider 'SSD' along with as much RAM as possible then setup tmpfs.

Last edited by onebuck; 12-30-2011 at 01:25 PM.
 
Old 12-30-2011, 01:41 PM   #9
lghizoni
Member
 
Registered: Dec 2011
Location: Denmark
Distribution: Slackware, Debian
Posts: 102

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by BlackRider View Post
I think you should be able to edit /etc/lilo.conf and configure the default parameters.

For example, if your lilo.conf contains something like this:

Code:
  image = /boot/vmlinuz-2.6.37.6
  root = /dev/sda1
  initrd = /boot/initrd.gz
  label = Slackware
  append = "quiet resume=/dev/sda1"
  read-only
You can add your desired parameters to the "append" section
Code:
append = "quiet resume=/dev/critdata/critswap [option1] [option2] [etc]"
Then, run lilo as root, so the changes are made effective.

EDIT: You can configure your resolution ensuring that there is an vga option active in your lilo.conf. The file contains a lot of examples, you just have to uncomment the one you need:
Code:
# VESA framebuffer console @ 1024x768x256
# I UNCOMMENT THIS ONE BECAUSE IT IS THE ONE I WANT!!
vga = 773  
# Normal VGA console
#vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
Ok, thank you very much!

Now, how do I edit /etc/lilo.conf? In terminal using gedit? Something like that?

And in 'append = "quiet resume=/dev/critdata/critswap [option1] [option2] [etc]"[/CODE]' what are the [option1] [option2] [etc] parameters? What should I do?

And how do I configure the resolution? Where do I do this?

Sorry for lots of questions.
 
Old 12-30-2011, 02:17 PM   #10
lghizoni
Member
 
Registered: Dec 2011
Location: Denmark
Distribution: Slackware, Debian
Posts: 102

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jimmy_page_89 View Post
And don't forget to execute
Code:
# lilo -v
:P
Thank you very much!

Now, do I add "compact" editing lilo.conf? And in wich part of the doc?

Also, do I run lilo -v in shell?

Sorry for lots of questions.
 
Old 12-30-2011, 02:42 PM   #11
bruinshockey
Member
 
Registered: Dec 2010
Location: Chilliwack, BC
Distribution: Slackware 14.1 64 Bit
Posts: 34

Rep: Reputation: 10
you must edit /etc/lilo.conf as root and add the compact line here

boot = /dev/sda
compact

save and exit then run lilo -v in a shell

Last edited by bruinshockey; 12-30-2011 at 02:44 PM.
 
Old 12-30-2011, 02:56 PM   #12
honeybadger
Member
 
Registered: Aug 2007
Location: India
Distribution: Slackware (mainly) and then a lot of others...
Posts: 855

Rep: Reputation: Disabled
Try doing this. Login as root and run 'pkgtool'. It will give you some option one of them would be to run the init scripts again. This time when you select boot mode select textmode. Then run 'startx' or 'startxfce' and you should be able to see the screen. In case you do not then run 'xorgconf' as root and just keep hitting enter until it ends and then run 'startx'. Once you get the desktop you will find prefrences -> administration and then you would be able to set the monitor in a gui mode.
Hope this helps.
 
Old 12-30-2011, 03:14 PM   #13
lghizoni
Member
 
Registered: Dec 2011
Location: Denmark
Distribution: Slackware, Debian
Posts: 102

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bruinshockey View Post
you must edit /etc/lilo.conf as root and add the compact line here

boot = /dev/sda
compact

save and exit then run lilo -v in a shell
Thank you!! It works fine now!

Can I ask just one more question?

In Slackware apresentation I have the alternatives:

"Select an OS to boot, or hit <TAB> for a LILO prompt"

About the OS, I just have Linux, and if I press <ENTER>, it starts Slackware, but then suddenly the monitor goes off automaticaly and doesn't come back!

The same thing happens if I press <TAB> for LILO prompt and just run Linux.

The only way till now is to run 'linux init 3 nomodeset' in LILO.

Do anyone know what's the problem? I don't want to need to go for a LILO prompt and run 'linux init 3 nomodeset' everytime.

Thanks.
 
Old 12-30-2011, 03:16 PM   #14
onebuck
Moderator
 
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,925
Blog Entries: 44

Rep: Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159Reputation: 3159
Member response

Hi,

Welcome to LQ & Slackware!

Two good references SlackwareŽ Essentials & SlackwareŽ Basics
that will help you.

Another useful resource would be 'Slackware-Links'. More than just SlackwareŽ links!

You will find the following tutorial useful;
Quote:
excerpt from sticky 'So you want to be a Slacker! What do I do next?';

'New tutorials for installing and configuring Slack ' is a thread for a great tutorial: http://genek.net/LinuxAdventures/ins...allation1.html by 2handband. I recommend that all should look at this new tutorial for Slackware. Great for everyone!
http://genek.net/LinuxAdventures/sysadmin/index.html << new temp link

Newbies will learn a lot by following the sections within. As for the experienced users, it's a good place for us to recommend corrections or suggest areas that concern you. I for one participate with 2handband on subjects that I'm interested in: Slackware! Several other members have participated.
HTH!
 
Old 12-30-2011, 03:21 PM   #15
BlackRider
Member
 
Registered: Aug 2011
Posts: 295

Rep: Reputation: 101Reputation: 101
Quote:
Now, how do I edit /etc/lilo.conf? In terminal using gedit? Something like that?
Any text editor which you could easily use as root will suffice. For simple administrative tasks you can invoke nano.

Code:
$ su -c 'nano /etc/lilo.conf'
Quote:
And in 'append = "quiet resume=/dev/critdata/critswap [option1] [option2] [etc]"[/CODE]' what are the [option1] [option2] [etc] parameters? What should I do?
The "[options]" were just meant to show you that you can append any booting option you want, and it will be considered a "default". For example, you can pass the "nomodeset" option.

Quote:
And how do I configure the resolution? Where do I do this?
They are set somewhere in /etc/lilo.conf

Quote:
Try doing this. Login as root and run 'pkgtool'. It will give you some option one of them would be to run the init scripts again.
It is another idea, but running the install scripts again is basically going to automatically comment/uncomment the "vga" options as I told in my first post.

Last edited by BlackRider; 12-30-2011 at 03:24 PM.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Intro to the new user, Slackware user since 10.0 doctornetwork LinuxQuestions.org Member Intro 2 11-17-2010 09:37 AM
Longtime Linux User, new Slackware user Keynone LinuxQuestions.org Member Intro 1 02-27-2009 01:25 PM
slackware 12 installed multiple problems mostly with user flip_flop Linux - Newbie 4 08-17-2007 07:43 AM
problems with gnome when I change a user's user ID phil.d.g Slackware 5 12-21-2004 03:51 AM
Slackware 10 cdrom/dvd user access problems beyondzero Slackware 7 06-27-2004 05:21 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:30 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration