Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - General
User Name
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.


  Search this Thread
Old 03-30-2012, 09:00 AM   #16
LQ Newbie
Registered: Mar 2012
Distribution: Slackware
Posts: 24

Rep: Reputation: 3

Just for the record, I use an ATI video card with 4 screens and all the 10 or so linux distros I tried all worked without any problems.
Old 03-30-2012, 09:30 AM   #17
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: slackware64-current, fedora ,Xubuntu, others
Posts: 6,644

Rep: Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375Reputation: 1375
Have you tried adding noapci nomodeset to the boot options when the cd first boots? I have a laptop with two ati hybrid graphic cards and had to use the nomodeset option with just about every distro I use
Old 03-30-2012, 10:00 AM   #18
Registered: Sep 2009
Location: Geogia, USA
Distribution: Ubuntu, Debian, Live CDs
Posts: 213

Rep: Reputation: 39

Originally Posted by colorpurple21859 View Post
Have you tried adding noapci nomodeset to the boot options when the cd first boots? I have a laptop with two ati hybrid graphic cards and had to use the nomodeset option with just about every distro I use
I second that. The noapci and nomodeset options are available on most live CDs. Some live distros come with a help screen that describes boot options. It's usually F2 or F3 (check the distro documentation). You could try hitting Tab at the very beginning, as soon as you see the boot prompt, but BEFORE it starts to load the OS. Doing that should allow you to edit the actual boot command, so you can try any number of options. I've been down this road before, where some oddball motherboard doesn't like Linux. IMHO, as long as your data is backed up, and you have enough cash, keep going until your computer dies completely (only a suggestion, do it at your own risk)
Old 03-30-2012, 11:35 AM   #19
Registered: Jan 2005
Location: Central Florida 20 minutes from Disney World
Distribution: SlackwareŽ
Posts: 13,864
Blog Entries: 41

Rep: Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044Reputation: 3044
Member response


I would think any boot option to pass kernel parameters would be available when you have a 'boot:' prompt screen selection. Not dependent on the distribution but dependent on the loader configuration;
excerpt from 'man bootparm';
       bootparam - Introduction to boot time parameters of the Linux kernel

       The  Linux kernel accepts certain 'command-line options' or 'boot time parameters' at the moment it is started.  In general this is used
       to supply the kernel with information about hardware parameters that the kernel would not be  able  to  determine  on  its  own,  or  to
       avoid/override the values that the kernel would otherwise detect.

       When  the kernel is booted directly by the BIOS (say from a floppy to which you copied a kernel using 'cp zImage /dev/fd0'), you have no
       opportunity to specify any parameters.  So, in order to take advantage of this possibility you have to use software that is able to pass
       parameters, like LILO or loadlin.  For a few parameters one can also modify the kernel image itself, using rdev, see rdev(8) for further

       The LILO program (LInux LOader) written by Werner Almesberger is the most commonly used.  It has the ability to  boot  various  kernels,
       and  stores  the configuration information in a plain text file.  (See lilo(8) and lilo.conf(5).)  LILO can boot DOS, OS/2, Linux, Free-
       BSD, UnixWare, etc., and is quite flexible.

       The other commonly used Linux loader is 'LoadLin' which is a DOS program that has the capability to launch a Linux kernel from  the  DOS
       prompt (with boot-args) assuming that certain resources are available.  This is good for people that want to launch Linux from DOS.

       It  is  also very useful if you have certain hardware which relies on the supplied DOS driver to put the hardware into a known state.  A
       common example is 'SoundBlaster Compatible' sound cards that require the DOS driver to twiddle a few mystical registers to put the  card
       into  a  SB  compatible  mode.  Booting DOS with the supplied driver, and then loading Linux from the DOS prompt with loadlin avoids the
       reset of the card that happens if one rebooted instead.

   The Argument List
       The kernel command line is parsed into a list of strings (boot arguments) separated by spaces.  Most of the boot args take the form of:


       where 'name' is a unique keyword that is used to identify what part of the kernel the associated values (if any) are  to  be  given  to.
       Note  the  limit of 10 is real, as the present code only handles 10 comma separated parameters per keyword.  (However, you can reuse the
       same keyword with up to an additional 10 parameters in unusually complicated situations, assuming the setup function supports it.)
Most of the sorting goes on in linux/init/main.c.  First, the kernel checks to see if the argument  is  any  of  the  special  arguments
       'root=', 'nfsroot=', 'nfsaddrs=', 'ro', 'rw', 'debug' or 'init'.  The meaning of these special arguments is described below.

       Then  it walks a list of setup functions (contained in the bootsetups array) to see if the specified argument string (such as 'foo') has
       been associated with a setup function ('foo_setup()') for a particular device or part of the kernel.  If you passed the kernel the  line
       foo=3,4,5,6  then  the kernel would search the bootsetups array to see if 'foo' was registered.  If it was, then it would call the setup
       function associated with 'foo' (foo_setup()) and hand it the arguments 3, 4, 5 and 6 as given on the kernel command line.

       Anything of the form 'foo=bar' that is not accepted as a setup function as described above is then interpreted as an  environment  vari-
       able to be set.  A (useless?) example would be to use 'TERM=vt100' as a boot argument.

       Any  remaining  arguments  that  were not picked up by the kernel and were not interpreted as environment variables are then passed onto
       process one, which is usually the init program.  The most common argument that is passed to the init process is the word 'single'  which
       instructs init to boot the computer in single user mode, and not launch all the usual daemons.  Check the manual page for the version of
       init installed on your system to see what arguments it accepts.
Do a 'man bootparm' to see the parameters.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
can't install linux... ay distribution... PLZ HELP dvdriper Linux - Newbie 3 02-03-2008 09:27 AM
how to install a software in the linux system from some other distribution?? ashmita04 Linux - General 3 08-03-2007 05:21 AM
can i install two kinds of linux distribution ztdep Linux - Software 4 10-20-2006 05:59 AM
best linux distribution to install a software modem bastin_gh Linux - Hardware 3 07-02-2005 09:17 PM
Install more one Linux distribution on the same PC May1950 Linux - Newbie 2 03-13-2004 11:58 AM > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 03:47 PM.

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