I modified /etc/grub.conf on my ThinkPad W700 to show the boot-up process as text. I did this by commenting out "hiddenmenu" and removing "rhgb" and "quiet" from the kernel spec line. The W700 has trouble with a tickless kernel in F12 and needs "nohz=off". The first stanza is shown below.
The W700 has an nVidia display and uses the nouveau driver. Immediately after the menu screen in F10 and F11 I'd see 4 penguins (quad core) as the initialization began. It was kinda neat, but in F12 there's just black space where those penguins would be. Where'd they go? Is this an artifact of the nouveau driver?
#boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu # # Kernel 0 title Fedora 12 (Constantine) [Update 3] (2.6.31.9-174.fc12.x86_64) root (hd0,0) kernel /vmlinuz-2.6.31.9-174.fc12.x86_64 ro root=UUID=blah-blah-blah LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us nohz=off initrd /initramfs-2.6.31.9-174.fc12.x86_64.img
--Doc Savage Fairview Heights, IL
On Wed, Dec 30, 2009 at 10:24 AM, Robert G. (Doc) Savage dsavage@peaknet.net wrote:
I modified /etc/grub.conf on my ThinkPad W700 to show the boot-up process as text. I did this by commenting out "hiddenmenu" and removing "rhgb" and "quiet" from the kernel spec line. The W700 has trouble with a tickless kernel in F12 and needs "nohz=off". The first stanza is shown below.
The W700 has an nVidia display and uses the nouveau driver. Immediately after the menu screen in F10 and F11 I'd see 4 penguins (quad core) as the initialization began. It was kinda neat, but in F12 there's just black space where those penguins would be. Where'd they go? Is this an artifact of the nouveau driver?
#boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz #hiddenmenu # # Kernel 0 title Fedora 12 (Constantine) [Update 3] (2.6.31.9-174.fc12.x86_64) root (hd0,0) kernel /vmlinuz-2.6.31.9-174.fc12.x86_64 ro root=UUID=blah-blah-blah LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us nohz=off initrd /initramfs-2.6.31.9-174.fc12.x86_64.img
These are two guesses but you may try turning off kernel mode setting (appends nomodeset to the kernel parameters I believe) and if that doesn't work try adding a VESA mode, something like "vga=..." I'm not sure what resolution you want to run but try "vga=ask" the first time and pick the one you like the most. If you're happy with it change the parameter to "vga=0x<mode>". I found out the hard way that you need to put "0x" on the front of whichever mode you choose.
Richard
Richard Shaw wrote:
try adding a VESA mode, something like "vga=..." I'm not sure what resolution you want to run but try "vga=ask" the first time and pick the one you like the most. If you're happy with it change the parameter to "vga=0x<mode>". I found out the hard way that you need to put "0x" on the front of whichever mode you choose.
either a hex value or a decimal value may be passed.
"0x" is used if you pass a hex value, else value passed will be taken as being a decimal value.
some basic resolution codes, in decimal, are:
colors bits 640x480 800×600 1024×768 1152×864 1280×1024 1600×1200 256 8 vga=769 vga=771 vga=773 vga=353 vga=775 vga=796 32K0 vga=784 vga=787 vga=790 vga=354 vga=793 vga=797 65K0 16 vga=785 vga=788 vga=791 vga=355 vga=794 vga=798 16M7 24 vga=786 vga=789 vga=792 vga=795 vga=799
this page has charts for passing hex values with a few decimal thrown in;
http://wiki.antlinux.com/pmwiki.php?n=HowTos.VgaModes
if you have "kernel source package" installed, you should find info in;
/usr/src/linux/Documentation/fb/vesafb.txt
hth.
g wrote:
Richard Shaw wrote:
try adding a VESA mode, something like "vga=..." I'm not sure what resolution you want to run but try "vga=ask" the first time and pick the one you like the most. If you're happy with it change the parameter to "vga=0x<mode>". I found out the hard way that you need to put "0x" on the front of whichever mode you choose.
either a hex value or a decimal value may be passed.
"0x" is used if you pass a hex value, else value passed will be taken as being a decimal value.
It's not *quite* that simple, that the way it works on the command line passed to the kernel. However, if you use VGA=ask, those numbers are hex and 0x is neither needed nor accepted.Ste 300
some basic resolution codes, in decimal, are:
colors bits 640x480 800×600 1024×768 1152×864 1280×1024 1600×1200 256 8 vga=769 vga=771 vga=773 vga=353 vga=775 vga=796 32K0 vga=784 vga=787 vga=790 vga=354 vga=793 vga=797 65K0 16 vga=785 vga=788 vga=791 vga=355 vga=794 vga=798 16M7 24 vga=786 vga=789 vga=792 vga=795 vga=799
this page has charts for passing hex values with a few decimal thrown in;
http://wiki.antlinux.com/pmwiki.php?n=HowTos.VgaModes
if you have "kernel source package" installed, you should find info in;
/usr/src/linux/Documentation/fb/vesafb.txt
In addition, with recent kernels, you have to start doing anything interesting with "nomodeset" before you can use vga= or it's useful friends video= and xdriver=
Example of everything all at once, use vesa and see penguins: nomodeset vga=0x318 video=vesafb xdriver=vesa
This allows you to use alternate framebuffer and X drivers, and trade the high performance and low reliability of some modern kernel drivers for the slow stability of vesa.
Bill Davidsen wrote:
In addition, with recent kernels, you have to start doing anything interesting with "nomodeset" before you can use vga= or it's useful friends video= and xdriver=
most recent kernel i am using is kernel-2.6.31.5-127.fc12.i686 because kernel-2.6.31.6-145.fc12.i686 and kernel-2.6.31.6-166.fc12.i686 are giving boot problems.
because i like to see boot info, i 'init 1' on first boot of a new install to change 'grub.conf'.
i '#' out 'splashimage=' and 'hiddenmenu', then i remove 'rhgb' and 'quiet' from kernel argument and add 'vga=794', for a '53 rows x 120 columns' screen.
so i have never seen dancing penguins 'op' was desiring. my passing along of 'vga=' was so that he would have an idea of what was available.
so i do appreciate your information of 'nomodeset' and rest in case i get desires for 'anything interesting'. [i consider boot info 'informative'.]
g writes:
Richard Shaw wrote:
try adding a VESA mode, something like "vga=..." I'm not sure what resolution you want to run but try "vga=ask" the first time and pick the one you like the most. If you're happy with it change the parameter to "vga=0x<mode>". I found out the hard way that you need to put "0x" on the front of whichever mode you choose.
either a hex value or a decimal value may be passed.
"0x" is used if you pass a hex value, else value passed will be taken as being a decimal value.
some basic resolution codes, in decimal, are:
colors bits 640x480 800×600 1024×768 1152×864 1280×1024 1600×1200 256 8 vga=769 vga=771 vga=773 vga=353 vga=775 vga=796 32K0 vga=784 vga=787 vga=790 vga=354 vga=793 vga=797 65K0 16 vga=785 vga=788 vga=791 vga=355 vga=794 vga=798 16M7 24 vga=786 vga=789 vga=792 vga=795 vga=799
Maybe, maybe not. I have several laptops here. Each one produces a different list of possible VGA modes.
Your actual VGA modes depend solely on your video BIOS. I looked, and I was unable to find any way to obtain a list of supported video modes from userspace. The boot time prompt is the only time yu see them.
Sam Varshavchik wrote:
g writes:
Richard Shaw wrote:
try adding a VESA mode, something like "vga=..." I'm not sure what resolution you want to run but try "vga=ask" the first time and pick the one you like the most. If you're happy with it change the parameter to "vga=0x<mode>". I found out the hard way that you need to put "0x" on the front of whichever mode you choose.
either a hex value or a decimal value may be passed.
"0x" is used if you pass a hex value, else value passed will be taken as being a decimal value.
some basic resolution codes, in decimal, are:
colors bits 640x480 800×600 1024×768 1152×864 1280×1024 1600×1200 256 8 vga=769 vga=771 vga=773 vga=353 vga=775 vga=796 32K0 vga=784 vga=787 vga=790 vga=354 vga=793 vga=797 65K0 16 vga=785 vga=788 vga=791 vga=355 vga=794 vga=798 16M7 24 vga=786 vga=789 vga=792 vga=795 vga=799
Maybe, maybe not. I have several laptops here. Each one produces a different list of possible VGA modes.
Your actual VGA modes depend solely on your video BIOS. I looked, and I was unable to find any way to obtain a list of supported video modes from userspace. The boot time prompt is the only time yu see them.
True, I guess, but I have never found on which didn't support 0x305, 0x303, or 0x301, 1024x768, 800x600, and 640x480 at 8 bit. You only need to get it up, the X vesa driver will let you tune it after.
Note, I'm not advising against "vga=ask" but there are a few modes which work widely if you know your vertical resolution limit.
On Thu, 2009-12-31 at 12:15 -0500, Bill Davidsen wrote:
Sam Varshavchik wrote:
g writes:
Richard Shaw wrote:
Many thanks to all, but after trying all of the suggested VESA alternatives I've concluded that the nouveau driver sans penguins is vastly superior. Setting vga=0x37d for a starting text screen with a 1920x1200x32 resolution displayed the four penguins, but when startup switched to graphical mode the screen went solid black. Using the vesafb driver fixed that, but the result is S-L-O-W.
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
--Doc Savage Fairview Heights, IL
2009/12/31 Robert G. (Doc) Savage dsavage@peaknet.net:
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
-- Sam
Oh boy... LOL
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
-- Sam
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On Thu, 31 Dec 2009, Sam Sharpe wrote:
2009/12/31 Robert G. (Doc) Savage dsavage@peaknet.net:
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
I think the penguins will last longer than the polar bears. For sure they will last longer than the golden toads.
On Thursday 31 December 2009, Michael Hennebry wrote:
On Thu, 31 Dec 2009, Sam Sharpe wrote:
2009/12/31 Robert G. (Doc) Savage dsavage@peaknet.net:
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
I think the penguins will last longer than the polar bears.
Considerably longer.
For sure they will last longer than the golden toads.
And that is sad. How many and where, of the latter do we have?
Gene Heskett wrote:
On Thursday 31 December 2009, Michael Hennebry wrote:
For sure they will last longer than the golden toads.
And that is sad. How many and where, of the latter do we have?
possibly none, according to;
http://www.petermaas.nl/extinct/speciesinfo/goldentoad.htm
and,
http://animaldiversity.ummz.umich.edu/site/accounts/information/Bufo_perigle...
On Friday 01 January 2010, g wrote:
Gene Heskett wrote:
On Thursday 31 December 2009, Michael Hennebry wrote:
For sure they will last longer than the golden toads.
And that is sad. How many and where, of the latter do we have?
possibly none, according to;
http://www.petermaas.nl/extinct/speciesinfo/goldentoad.htm
and,
http://animaldiversity.ummz.umich.edu/site/accounts/information/Bufo_perigl enes.html
Rather sounds like we should shed a tear. Can we blame man for meddling in the weather that apparently sealed their fate?
To put this back a little closer of on topic, do we have a usb monitoring tool that can detect and name the processes that are apparently fighting over a device plugged into a semi remote usb hub, a 7 port gizmo plugged into one of the mobo ports?
On Fri, 2010-01-01 at 02:01 -0500, Gene Heskett wrote:
To put this back a little closer of on topic, do we have a usb monitoring tool that can detect and name the processes that are apparently fighting over a device plugged into a semi remote usb hub, a 7 port gizmo plugged into one of the mobo ports?
Gene,
To do this you really should open a new thread with its own subject. What you're looking for probaby has nothing to do with the behavior of the nouveau video driver.
--Doc Savage Fairview Heights, IL
On Thursday 31 December 2009, Sam Sharpe wrote:
2009/12/31 Robert G. (Doc) Savage dsavage@peaknet.net:
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
-- Sam
Chuckle. Careful there Sam, that sort of satire is catching. Unforch, there may be a grain of truth to it.
2009/12/31 Gene Heskett gene.heskett@verizon.net:
On Thursday 31 December 2009, Sam Sharpe wrote:
2009/12/31 Robert G. (Doc) Savage dsavage@peaknet.net:
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
-- Sam
Chuckle. Careful there Sam, that sort of satire is catching. Unforch, there may be a grain of truth to it.
May I be the first (as I live at the centre of Time) to wish you all a Happy New Year.
Lets hope Global Warming means I can get a nice tan this year ;o)
-- Sam
On Thursday 31 December 2009, Sam Sharpe wrote:
2009/12/31 Gene Heskett gene.heskett@verizon.net:
On Thursday 31 December 2009, Sam Sharpe wrote:
2009/12/31 Robert G. (Doc) Savage dsavage@peaknet.net:
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
Global Warming - it's destroying the Penguin's habitats. Ask Al Gore... he'll back me up.
-- Sam
Chuckle. Careful there Sam, that sort of satire is catching. Unforch, there may be a grain of truth to it.
May I be the first (as I live at the centre of Time) to wish you all a Happy New Year.
Lets hope Global Warming means I can get a nice tan this year ;o)
-- Sam
Unforch Sam, with the tan comes skin cancer... Ask me how I know. (but I still go w/o a shirt most of the summer anyway)
Robert G. (Doc) Savage wrote:
On Thu, 2009-12-31 at 12:15 -0500, Bill Davidsen wrote:
Sam Varshavchik wrote:
g writes:
Richard Shaw wrote:
Many thanks to all, but after trying all of the suggested VESA alternatives I've concluded that the nouveau driver sans penguins is vastly superior. Setting vga=0x37d for a starting text screen with a 1920x1200x32 resolution displayed the four penguins, but when startup switched to graphical mode the screen went solid black. Using the vesafb driver fixed that, but the result is S-L-O-W.
If your LCD display is like most of mine, it takes a moment to change mode when the scan rate changes. The penguins come up early, it's possible that the display misses them. Note, I'm throwing that out for discussion, not stating it as a fact.
The nouveau driver is a big improvement over nv, but it apparently lacks the ability to display core penguins after the startmenu. As I speculated in my original post, this seems to be an artifact of the nouveau driver. Considering the alternatives, I can accept that.
--Doc Savage Fairview Heights, IL
Sam Varshavchik wrote:
Maybe, maybe not. I have several laptops here. Each one produces a different list of possible VGA modes.
actually, maybe so.
'vga mode' actually applies to crt, cathode ray tube, displays. laptops came along long after crt and because of being 'solid state' [ss] design, laptop screens and solid state monitors have their own dot pattern array, as apposed to phosphor dot pattern, and sweep rates. which gives them their own vga *emulation* modes.
i can not comment on ibm's early multi window red led flat screen monitor because i never saw any tech spec for them. they were large and impressive.
Your actual VGA modes depend solely on your video BIOS.
which is different between *crt* and *ss* displays.
I looked, and I was unable to find any way to obtain a list of supported video modes from userspace. The boot time prompt is the only time yu see them.
*userspace*
-
Bill Davidsen -
Chris W Tucker -
g -
Gene Heskett -
Michael Hennebry -
Richard Shaw -
Robert G. (Doc) Savage -
Sam Sharpe -
Sam Varshavchik