Re: stm (was Console resolution (Was Viewing bootup message))
On Fri, 27 Feb 1998, Benoit Goudreault-Emond wrote: [snip] Hmm, I used to have that running with my tseng et4000, but when I went to my new s3 virge, It died completely... anyway, 80x34 is fine... 80x25 is just too large... I hate DOS so much... :) Died how? Don't forget that you absolutely HAVE to load fonts if you use any S3 based card in text mode at high refresh rates (you probably knew that, but one never knows). Mainly the display gets screwed around... I was loading fonts, although I didn'nt know I _had_ to. Are there any particular fonts that have to be used? I cant remember what I was using. Michael Beattie ([EMAIL PROTECTED]) --- WinErr: 016 Error buffer overflow - Too many errors encountered. Additional errors may not be displayed or recorded. --- Debian GNU/Linux Ooohh You are missing out! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: stm (was Console resolution (Was Viewing bootup message))
[snip] Hmm, I used to have that running with my tseng et4000, but when I went to my new s3 virge, It died completely... anyway, 80x34 is fine... 80x25 is just too large... I hate DOS so much... :) Died how? Don't forget that you absolutely HAVE to load fonts if you use any S3 based card in text mode at high refresh rates (you probably knew that, but one never knows). -- Benoit Goudreault-Emond Reply to: [EMAIL PROTECTED] PGP public key fingerprint: 11 43 A9 04 7C 11 41 44 5F FC 69 B1 B6 0A ED 78 E-mail me to receive the actual public key. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: stm (was Console resolution (Was Viewing bootup message))
On Thu, 26 Feb 1998, Benoit Goudreault-Emond wrote: [A heck of a lot clipped] I hope that will be of some use to you. Apparently not... I am beginning to think I need to raise some money for a new monitor.. :( limits: 30-50 horiz 50-75 Vert Oh well... Well, you can change the first number on the modeline, I beleive it's the dot clock. Lowering that will allow you to drive the monitor at a lower synch rate. 'Sides, I had a monitor which had about the same specs once, and I ran @ 100x37 but at ~70 Hz, IIRC. You should be able to do the same (hint: you should be able to drive the 100x37 mode at the same frequency you drive your monitor when in 800x600 graphical mode). Unfortunately, I don't know what happened to that particular configuration. Sorry. Hmm, I used to have that running with my tseng et4000, but when I went to my new s3 virge, It died completely... anyway, 80x34 is fine... 80x25 is just too large... I hate DOS so much... :) Again, be darn careful when fooling around with SVGATextMode. Keep one console with stm 80x25 ready, and your finger on the monitor's off switch. :) I think that goes without saying... Michael Beattie ([EMAIL PROTECTED]) --- WinErr: 006 Malicious error - Desqview found on drive --- Debian GNU/Linux Ooohh You are missing out! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: stm (was Console resolution (Was Viewing bootup message))
On Sun, 22 Feb 1998, Benoit Goudreault-Emond wrote: As a matter of interest, who is using SVGATextMode with an S3 ViRGE and a 1024x768 capable monitor? if I try to go above 80x30, the characters on the left hand side of the screen get all screwy, and sometimes the left of the screen is cut off at the 10thish column and is repeated from there... So I use LILO to give me 80x34 :) Any Ideas? I am. My own text mode is [EMAIL PROTECTED] My settings: --- snip --- ChipSet S3 ClockChip S3Virge Option XFAST_DRAM # The following line might be what you're missing... Option S3_HSText option 16color # You may be missing this as well -- apparently, you must make sure to # load fonts at high frequencies Option LoadFont FontProg /usr/bin/setfont FontPath /usr/lib/kbd/consolefonts # The following font is not in the package -- I grabbed it off sunsite's # console fonts pack. FontSelect sans-16 8x16 9x16 8x15 9x15 # The following fonts were kept as default -- I don't use them FontSelect Cyr_a8x14 8x14 9x14 8x13 9x13 FontSelect 8x12alt.psf 8x12 9x12 8x11 9x11 FontSelect Cyr_a8x88x8 9x8 8x7 9x7 FontSelect Cyr_a8x32 8x32 9x32 8x31 9x31 FontProg /usr/bin/setfont -u def.uni HorizSync 30-66 VertRefresh 50-110 DefaultMode 80x25 80x25 28.3640 680 776 800400 412 414 449 font 9x16 # # This is the mode I use. I had to mess with the first, second, fourth # and fifth values to center. I basically tried until I got something # reasonable, so I can't really give some hints besides keep a console # with stm 80x25 always ready at the prompt, and your finger on the # monitor's power off switch (just in case you give bad settings) # custom 55 800 878 922 1042615 615 616 650 font 8x16 --- snip --- I hope that will be of some use to you. Apparently not... I am beginning to think I need to raise some money for a new monitor.. :( limits: 30-50 horiz 50-75 Vert Oh well... Michael Beattie ([EMAIL PROTECTED]) --- WinErr: 012 System crash - We are unable to figure out our own code. --- Debian GNU/Linux Ooohh You are missing out! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: stm (was Console resolution (Was Viewing bootup message))
[A heck of a lot clipped] I hope that will be of some use to you. Apparently not... I am beginning to think I need to raise some money for a new monitor.. :( limits: 30-50 horiz 50-75 Vert Oh well... Well, you can change the first number on the modeline, I beleive it's the dot clock. Lowering that will allow you to drive the monitor at a lower synch rate. 'Sides, I had a monitor which had about the same specs once, and I ran @ 100x37 but at ~70 Hz, IIRC. You should be able to do the same (hint: you should be able to drive the 100x37 mode at the same frequency you drive your monitor when in 800x600 graphical mode). Unfortunately, I don't know what happened to that particular configuration. Sorry. Again, be darn careful when fooling around with SVGATextMode. Keep one console with stm 80x25 ready, and your finger on the monitor's off switch. :) -- Benoit Goudreault-Emond Reply to: [EMAIL PROTECTED] PGP public key fingerprint: 11 43 A9 04 7C 11 41 44 5F FC 69 B1 B6 0A ED 78 E-mail me to receive the actual public key. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
On Mon, Feb 23, 1998 at 10:32:47PM +0800, Lindsay Allen wrote: I have spent quite some time on this one. Reverting to the bo svgatextmode does not help. The thing that makes the difference is the particular font chosen. If I use 80x25, 80x25x9 or 80x25x8 I can still scroll right back to the bios messages. But if I use 116x34x9 I cannot scroll back at all. It appears, then, that a significant change of font causes a reset. Maybe there is not enough video ram to have any scroll-back? I have a 2MB card and at 100x37 (and 110Hz thanks to SVGATextmode :-) ) I can press S-Up about six or seven times. Adrian email: [EMAIL PROTECTED] | Debian Linux - www.debian.org http://www.poboxes.com/adrian.bridgett | Because bloated, unstable PGP key available on public key servers | operating systems are from MS -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Console resolution (Was Viewing bootup message)
On Sat, 21 Feb 1998, Bill Leach wrote: William R. Ward wrote: [snip] I've never seen much point in svgatextmode, personally - you can get 80x50 from LILO, isn't that enough? The 80x50 LILO can give me, also gives me 8x8 pixel characters. Using SVGATextMode I have 116x51 using 16x9 pixel characters. Readable characters are enough reason for me. I'm all for giving everyone as many options as practical but SVGATextMode is one that I plan on leaving off of my system. Quite fortunately, for me, after running Linux of several flavors for years, I finally opted to make xdm start on boot. Good thing, SVGA Text Mode failed miserably (with the default configuration) but of course X worked fine. I even tried booting into single user before playing around with SVGA Text Mode just to see if it was possible. Turns out that a serious problem with SVGA Text Mode is about as bad as a problem with BASH (assuming BASH is your default shell of course). But if you haven't configured SVGATextMode properly it shouldn't start at all at boot time. First configure it and be confident that it really works on your hardware, then make it start at boot time. Also, if you are unable to read the console, it still is a console. Log in blindly and type stm 80x25, and you should get the default 80x25 mode. Additionally, I either never could quite figure the thing out properly but when switching to a console under SVGA Text Mode from X the last row of pixels was lost on ALL console screens. To me it just seemed to quirky but will readily admit that except for 1) the potental inconvenience of not being able to get a console at all and 2) the quirky behaviour I experienced going to consoles from X, SVGA Text Mode can give you some really wonderful console displays on a high resolution monitor. 1) is solved by not doing things too fast, 2) is probably a timing problem that can be solved by tuning the video mode. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: stm (was Console resolution (Was Viewing bootup message))
On Mon, 23 Feb 1998, Remco Blaakmeer wrote: On Sat, 21 Feb 1998, Bill Leach wrote: William R. Ward wrote: [snip] I've never seen much point in svgatextmode, personally - you can get 80x50 from LILO, isn't that enough? The 80x50 LILO can give me, also gives me 8x8 pixel characters. Using SVGATextMode I have 116x51 using 16x9 pixel characters. Readable characters are enough reason for me. [snip] But if you haven't configured SVGATextMode properly it shouldn't start at all at boot time. First configure it and be confident that it really works on your hardware, then make it start at boot time. As a matter of interest, who is using SVGATextMode with an S3 ViRGE and a 1024x768 capable monitor? if I try to go above 80x30, the characters on the left hand side of the screen get all screwy, and sometimes the left of the screen is cut off at the 10thish column and is repeated from there... So I use LILO to give me 80x34 :) Any Ideas? Michael Beattie ([EMAIL PROTECTED]) --- Documentation - The worst part of programming. --- Debian GNU/Linux Ooohh You are missing out! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: stm (was Console resolution (Was Viewing bootup message))
As a matter of interest, who is using SVGATextMode with an S3 ViRGE and a 1024x768 capable monitor? if I try to go above 80x30, the characters on the left hand side of the screen get all screwy, and sometimes the left of the screen is cut off at the 10thish column and is repeated from there... So I use LILO to give me 80x34 :) Any Ideas? I am. My own text mode is [EMAIL PROTECTED] My settings: --- snip --- ChipSet S3 ClockChip S3Virge Option XFAST_DRAM # The following line might be what you're missing... Option S3_HSText option 16color # You may be missing this as well -- apparently, you must make sure to # load fonts at high frequencies Option LoadFont FontProg /usr/bin/setfont FontPath /usr/lib/kbd/consolefonts # The following font is not in the package -- I grabbed it off sunsite's # console fonts pack. FontSelect sans-16 8x16 9x16 8x15 9x15 # The following fonts were kept as default -- I don't use them FontSelect Cyr_a8x14 8x14 9x14 8x13 9x13 FontSelect 8x12alt.psf 8x12 9x12 8x11 9x11 FontSelect Cyr_a8x88x8 9x8 8x7 9x7 FontSelect Cyr_a8x32 8x32 9x32 8x31 9x31 FontProg /usr/bin/setfont -u def.uni HorizSync 30-66 VertRefresh 50-110 DefaultMode 80x25 80x25 28.3640 680 776 800400 412 414 449 font 9x16 # # This is the mode I use. I had to mess with the first, second, fourth # and fifth values to center. I basically tried until I got something # reasonable, so I can't really give some hints besides keep a console # with stm 80x25 always ready at the prompt, and your finger on the # monitor's power off switch (just in case you give bad settings) # custom 55 800 878 922 1042615 615 616 650 font 8x16 --- snip --- I hope that will be of some use to you. -- Benoit Goudreault-Emond Reply to: [EMAIL PROTECTED] PGP public key fingerprint: 11 43 A9 04 7C 11 41 44 5F FC 69 B1 B6 0A ED 78 E-mail me to receive the actual public key. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
On Sat, 21 Feb 1998, Nathan E Norman wrote: On 20 Feb 1998, William R. Ward wrote: : Lindsay Allen [EMAIL PROTECTED] writes: : On Tue, 10 Feb 1998, Hamish Moffatt wrote: : On Mon, Feb 09, 1998 at 09:11:27PM -0500, [EMAIL PROTECTED] wrote: :How can you view the entire list of messeges that show when you boot into :linux? It all either scrolls by too fast or too much read/decipher as it :rolls off the top. Is there a file that mirrors that output or someway I :can re-direct it to a file for perusal? : : dmesg will show you the kernel stuff, eg dmesg | less. Most of : it is in the logs in /var/log too. There's no way (that I know of) : to see all the non-kernel stuff. : : I could shift/page right back to the bios messages after startup until I : upgraded svgatextmode (currently Version: 1.8-4.) Now I cannot go back : past whatever is on the screen when svgatextmode starts. Has anyone got a : fix for this? : : I've never seen much point in svgatextmode, personally - you can get : 80x50 from LILO, isn't that enough? Sure, if you've got a 15 monitor, and have never used a 132 column monitor. However, this argumant is pointless as it doesn't fulfill the purpose of the list - address the user's question. At any rate, I believe the new version of stm resets the screen when it starts, so that gpm will work as advertised (if you start gpm, then start stm, and don't send a SIGWINCH (iirc) to gpm, it still thinks you're in a 80x25 window. Ugly) I suppose this reset is causing your inability to scroll back. I'm not a master with stm, gpm, but I think there is a way to _not_ run stm on one of your consoles. Is there? If you don't use gpm, you could comment out the reset program in the stm config file ... or, even if you do use gpm you could try this. I'll try it out on my Compaq monday at work. Until then, this is mostly conjecture. HTH, I have spent quite some time on this one. Reverting to the bo svgatextmode does not help. The thing that makes the difference is the particular font chosen. If I use 80x25, 80x25x9 or 80x25x8 I can still scroll right back to the bios messages. But if I use 116x34x9 I cannot scroll back at all. It appears, then, that a significant change of font causes a reset. Thanks to all who helped. I guess I'll have to accept things as they are. Lindsay =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen [EMAIL PROTECTED] Perth, Western Australia voice +61 8 9316 248632.0125S 115.8445Evk6lj Debian Unix =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Console resolution (Was Viewing bootup message)
The 80x50 LILO can give me, also gives me 8x8 pixel characters. Using SVGATextMode I have 116x51 using 16x9 pixel characters. Readable characters are enough reason for me. I don't even remember what I am using in lilo but I am quite happy with it (bully for me). But if you haven't configured SVGATextMode properly it shouldn't start at all at boot time. First configure it and be confident that it really works on your hardware, then make it start at boot time. Maybe it shouldn't start but it DID start. I was more than surprised as I am all but certain that I did NOT explicitely choose to install SVGATextMode when in dselect. In any event it did install and the next time the machines was booted, consoles were fouled up. Upon reading the docs for the program and experiementing with it, I got it to work except for the corruption following a switch from X. I remember that there were some comments about switching back and forth and I am pretty sure that I tried at least some suggestions but to no avail. The 'bigger issue' to me was that even though I was pleased with flexibility provided for consoles, I don't like the idea of something that 'messes' with the console that can break single user mode. Thus, there was not much motivation for me to try to track down the X - SVGATextMode corruption. If I really felt a strong need to use it though, I would play around with how it is started so that it would not start automagically when in single user mode. While such a change is probably 'brutally simple', insuring that future updates of the package file did not 'undo' the change is, I think, not trivial. -- best, -bill [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from a 1996 Micro$loth ad campaign: The less you know about computers the more you want Micro$oft! See! They do get some things right! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Console resolution (Was Viewing bootup message)
William R. Ward wrote: [snip] I've never seen much point in svgatextmode, personally - you can get 80x50 from LILO, isn't that enough? I'm all for giving everyone as many options as practical but SVGATextMode is one that I plan on leaving off of my system. Quite fortunately, for me, after running Linux of several flavors for years, I finally opted to make xdm start on boot. Good thing, SVGA Text Mode failed miserably (with the default configuration) but of course X worked fine. I even tried booting into single user before playing around with SVGA Text Mode just to see if it was possible. Turns out that a serious problem with SVGA Text Mode is about as bad as a problem with BASH (assuming BASH is your default shell of course). Additionally, I either never could quite figure the thing out properly but when switching to a console under SVGA Text Mode from X the last row of pixels was lost on ALL console screens. To me it just seemed to quirky but will readily admit that except for 1) the potental inconvenience of not being able to get a console at all and 2) the quirky behaviour I experienced going to consoles from X, SVGA Text Mode can give you some really wonderful console displays on a high resolution monitor. -- best, -bill [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] from a 1996 Micro$loth ad campaign: The less you know about computers the more you want Micro$oft! See! They do get some things right! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
On 20 Feb 1998, William R. Ward wrote: : Lindsay Allen [EMAIL PROTECTED] writes: : On Tue, 10 Feb 1998, Hamish Moffatt wrote: : On Mon, Feb 09, 1998 at 09:11:27PM -0500, [EMAIL PROTECTED] wrote: :How can you view the entire list of messeges that show when you boot into :linux? It all either scrolls by too fast or too much read/decipher as it :rolls off the top. Is there a file that mirrors that output or someway I :can re-direct it to a file for perusal? : : dmesg will show you the kernel stuff, eg dmesg | less. Most of : it is in the logs in /var/log too. There's no way (that I know of) : to see all the non-kernel stuff. : : I could shift/page right back to the bios messages after startup until I : upgraded svgatextmode (currently Version: 1.8-4.) Now I cannot go back : past whatever is on the screen when svgatextmode starts. Has anyone got a : fix for this? : : I've never seen much point in svgatextmode, personally - you can get : 80x50 from LILO, isn't that enough? Sure, if you've got a 15 monitor, and have never used a 132 column monitor. However, this argumant is pointless as it doesn't fulfill the purpose of the list - address the user's question. At any rate, I believe the new version of stm resets the screen when it starts, so that gpm will work as advertised (if you start gpm, then start stm, and don't send a SIGWINCH (iirc) to gpm, it still thinks you're in a 80x25 window. Ugly) I suppose this reset is causing your inability to scroll back. I'm not a master with stm, gpm, but I think there is a way to _not_ run stm on one of your consoles. Is there? If you don't use gpm, you could comment out the reset program in the stm config file ... or, even if you do use gpm you could try this. I'll try it out on my Compaq monday at work. Until then, this is mostly conjecture. HTH, -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 phone: (605) 334-4454 fax: (605) 335-1173 mailto://[EMAIL PROTECTED] http://www.midco.net PGP Key ID: 0xA33B86E9 - Public key available at keyservers PGP Key fingerprint: CE03 10AF 3281 1858 9D32 C2AB 936D C472 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
Lindsay Allen [EMAIL PROTECTED] writes: On Tue, 10 Feb 1998, Hamish Moffatt wrote: On Mon, Feb 09, 1998 at 09:11:27PM -0500, [EMAIL PROTECTED] wrote: How can you view the entire list of messeges that show when you boot into linux? It all either scrolls by too fast or too much read/decipher as it rolls off the top. Is there a file that mirrors that output or someway I can re-direct it to a file for perusal? dmesg will show you the kernel stuff, eg dmesg | less. Most of it is in the logs in /var/log too. There's no way (that I know of) to see all the non-kernel stuff. I could shift/page right back to the bios messages after startup until I upgraded svgatextmode (currently Version: 1.8-4.) Now I cannot go back past whatever is on the screen when svgatextmode starts. Has anyone got a fix for this? I've never seen much point in svgatextmode, personally - you can get 80x50 from LILO, isn't that enough? --Bill. -- William R Ward Bay View Consulting http://www.bayview.com/~hermit/ [EMAIL PROTECTED] 1803 Mission St. #339voicemail +1 408/479-4072 [EMAIL PROTECTED] Santa Cruz CA 95060 USA pager +1 408/458-8862 PGP Key 0x2BD331E5; Public key at http://www.bayview.com/~hermit/pubkey.txt - The government of the United States of America is not in any sense founded upon the Christian Religion. - John Adams -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Viewing bootup message
How can you view the entire list of messeges that show when you boot into linux? It all either scrolls by too fast or too much read/decipher as it rolls off the top. Is there a file that mirrors that output or someway I can re-direct it to a file for perusal? Thanks, Chris '\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\ Live on Real Audio Thursday nights 8-11 EST http://www.uvm.edu/~wruv T-SNAKE [EMAIL PROTECTED] ICQ UIN:1868354 A DJ on a mission CROSSFADE RECORDS http://www.crossfade.com/ Drug free techno ,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/'\,/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
On Mon, Feb 09, 1998 at 09:11:27PM -0500, [EMAIL PROTECTED] wrote: How can you view the entire list of messeges that show when you boot into linux? It all either scrolls by too fast or too much read/decipher as it rolls off the top. Is there a file that mirrors that output or someway I can re-direct it to a file for perusal? dmesg will show you the kernel stuff, eg dmesg | less. Most of it is in the logs in /var/log too. There's no way (that I know of) to see all the non-kernel stuff. Note that scroll lock will pause the display. Hamish -- Hamish Moffatt, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
[EMAIL PROTECTED] wrote: How can you view the entire list of messeges that show when you boot into linux? It all either scrolls by too fast or too much read/decipher as it rolls off the top. Is there a file that mirrors that output or someway I can re-direct it to a file for perusal? Thanks, Chris You are looking for the command: dmesg Pipe it through your favoriate pager: dmesg | more dmesg | less etc. Keith -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
On Mon, 9 Feb 1998, tsnake wrote: How can you view the entire list of messeges that show when you boot into linux? It all either scrolls by too fast or too much read/decipher as it rolls off the top. Is there a file that mirrors that output or someway I can re-direct it to a file for perusal? Thanks, Chris Although dmesg and /var/log/messages are useful, the best method of seeing *everything* is to use Shift-PageUp/Down. This is always present in VCs just so long as you look before you switch to another VC (which throws away everything above the top of the screen). -- David Wright, Open University, Earth Science Department, Milton Keynes MK7 6AA U.K. email: [EMAIL PROTECTED] tel: +44 1908 653 739 fax: +44 1908 655 151 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Viewing bootup message
On Tue, 10 Feb 1998, Hamish Moffatt wrote: On Mon, Feb 09, 1998 at 09:11:27PM -0500, [EMAIL PROTECTED] wrote: How can you view the entire list of messeges that show when you boot into linux? It all either scrolls by too fast or too much read/decipher as it rolls off the top. Is there a file that mirrors that output or someway I can re-direct it to a file for perusal? dmesg will show you the kernel stuff, eg dmesg | less. Most of it is in the logs in /var/log too. There's no way (that I know of) to see all the non-kernel stuff. I could shift/page right back to the bios messages after startup until I upgraded svgatextmode (currently Version: 1.8-4.) Now I cannot go back past whatever is on the screen when svgatextmode starts. Has anyone got a fix for this? Note that scroll lock will pause the display. Hamish Lindsay =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen [EMAIL PROTECTED] Perth, Western Australia voice +61 8 9316 248632.0125S 115.8445Evk6lj Debian Unix =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
