Re: Setting a console resolution
>> In addition, on the computer with the Matrox-adapter running >> something as simple as 'dmesg -T' is really really slow. It literally >> takes several seconds while the text scrolls on the screen. >> The thing is, I do not really care about fancy framebuffer resolution and >> graphics on the console. I just want fairly big text that scrolls >> without hiccups, even in 640x480 :P >[...] > It is true that "video=800x600" works, but "video=800x600x32" (what the > OP had tried) does not. The color depth, if any, has to be preceded by > a '-' sign, i.e. "video=800x600-32", see Documentation/fb/modedb.txt[1]. The OP may wish to specify colour depth; but probably *not* 32, because: * fbcon uses memcpy, so on x86 at least it occupies CPU/RAM cycles. If you have an Atom (or a Celeron, like me), it can end up quite slow. * memcpy speed correlates roughly linearly to the amount copied * The memory required to display a screen of pixels scales with colour depth. * If you do not specify, _the default is 32 bits per pixel on mgag200_ (on a 2MB G200SE it might default to 16 - see mgag200_driver_load) If you just want console/ncurses, 8-bit is probably fine, and four times as fast! And if it's not enough you can still reduce the resolution a bit. Here is the kernel (and real) time to run 'dmsg' on a 1280x1024 160x64 character framebuffer running on a Celeron G16510T@2.3Ghz: 8-bit - 2.660 sec 16-bit - 4.707 sec [seems broken here, looked super-dim] 24-bit - 8.074 sec 32-bit - 11.353 sec 24-bit is likely falling out of cache, but even then it has an edge over 32-bit. My own video kernel parameters are: video=1280x1024R-8@75 consoleblank=0 drm.debug=0xe The R [reduced blanking] and/or M flags can be useful if if your screen supports either or both of these timing modifications, and you're looking for a higher resolution from the more limited chips in the G200 range the other parameters stop it blanking out after a while, and return useful information in dmesg / kern.log as to why certain modes are not working. [If anyone's struggling with an early MGA-G200SE with 2MB RAM, there's also a kernel patch available to reduce colour depth for validation, although the 'drm_pci_init(, _pci_driver)' bit should now be 'pci_register_driver(_pci_driver)' - https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg191567.html ] > Rather than changing the display resolution, I would use a bigger font. > The console-setup-linux package ships various fonts with up to 32x16 > pixels in the /usr/share/consolefonts directory which can be tried out > with setfont(1) and set in /etc/default/console-setup. Might well help. I use a 8x16 font to pack more onscreen (possibly over several panels, with 'screen'), but I guess it depends on your vision and screen. As it's a VGA input, be sure to tune pixel clock (coarse) and phase (fine) along with the other 'Display' settings on your monitor, it can make a big difference - you may find smaller text is readable after all. -- Laurence "GreenReaper" Parry https://greenreaper.co.uk/
Re: Setting a console resolution
On 2017-12-28 16:53 +, Brian wrote: > On Thu 28 Dec 2017 at 17:12:47 +0100, henrik i wrote: > >> A small update. I did some more testing on the system with Intel 3600 >> graphics, and at least one working solution was to blacklist the module: >> >> In /etc/modprobe.d/whatever.conf >> blacklist gma500_gfx >> >> This enabled me to use the following lines in /etc/default/grub >> GRUB_GFXMODE=1024x768@60 >> GRUB_GFXPAYLOAD_LINUX=keep >> >> Then run update-grub as always. For some reason, this works for resolution >> change for both grub and the console. I guess this is because vesafb is now >> in use. I wish it was possible to change the resolution with the 'native' >> modules, but have not found the right documentation on the video= syntax >> (if it works at all). As mentioned, it did not work with setting it in grub. > > I have a machine with an nvidia card. 'video=800x600' added to the linux > line at boot time works satisfactorily. Can also be done via grub in > /etc/default. It is true that "video=800x600" works, but "video=800x600x32" (what the OP had tried) does not. The color depth, if any, has to be preceded by a '-' sign, i.e. "video=800x600-32", see Documentation/fb/modedb.txt[1]. Rather than changing the display resolution, I would use a bigger font. The console-setup-linux package ships various fonts with up to 32x16 pixels in the /usr/share/consolefonts directory which can be tried out with setfont(1) and set in /etc/default/console-setup. Cheers, Sven 1. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/fb/modedb.txt
Re: Setting a console resolution
On Thu 28 Dec 2017 at 17:12:47 +0100, henrik i wrote: > A small update. I did some more testing on the system with Intel 3600 > graphics, and at least one working solution was to blacklist the module: > > In /etc/modprobe.d/whatever.conf > blacklist gma500_gfx > > This enabled me to use the following lines in /etc/default/grub > GRUB_GFXMODE=1024x768@60 > GRUB_GFXPAYLOAD_LINUX=keep > > Then run update-grub as always. For some reason, this works for resolution > change for both grub and the console. I guess this is because vesafb is now > in use. I wish it was possible to change the resolution with the 'native' > modules, but have not found the right documentation on the video= syntax > (if it works at all). As mentioned, it did not work with setting it in grub. I have a machine with an nvidia card. 'video=800x600' added to the linux line at boot time works satisfactorily. Can also be done via grub in /etc/default. -- Brian.
Re: Setting a console resolution
A small update. I did some more testing on the system with Intel 3600 graphics, and at least one working solution was to blacklist the module: In /etc/modprobe.d/whatever.conf blacklist gma500_gfx This enabled me to use the following lines in /etc/default/grub GRUB_GFXMODE=1024x768@60 GRUB_GFXPAYLOAD_LINUX=keep Then run update-grub as always. For some reason, this works for resolution change for both grub and the console. I guess this is because vesafb is now in use. I wish it was possible to change the resolution with the 'native' modules, but have not found the right documentation on the video= syntax (if it works at all). As mentioned, it did not work with setting it in grub. With regards, Henrik On Thu, Dec 28, 2017 at 12:48 PM, henrik i <whocar...@gmail.com> wrote: > Hi, > > I got two computers that usually run headless, but from time to time I > might need to troubleshoot from the console. When I do this, I just connect > a plain VGA cable to my 1920x1200 Dell monitor. Just upgraded to Stretch > with kernel 4.9 and noticed that no matter what I do, the console > resolution is 1920x1200. In addition, on the computer with the > Matrox-adapter running something as simple as 'dmesg -T' is really really > slow. It literally takes several seconds while the text scrolls on the > screen. > > The thing is, I do not really care about fancy framebuffer resolution and > graphics on the console. I just want fairly big text that scrolls without > hiccups, even in 640x480 :P > > I have tried setting the resolution in /etc/default/grub: > GRUB_GFXMODE=1024x768x32 > GRUB_GFXPAYLOAD_LINUX=keep > > Then running update-grub. The only thing that changes, is the grub-menu > resolution, nothing else. I think the resolutions I have tried should be > supported, given the output from 'vbeinfo' in Grub. I also gave a couple of > kernel parameters a try, like video=1024x768x32. Even tried vga= and > nomodeset, but I think doing this is deprecated. None of these methods seem > to work. > > I believe the resolution is set through KMS, Kernel Mode Setting. Maybe I > just need to blacklist some modules? > > I know the onboard graphic cards are quite cheap, the Intel one is not > even made/supported by Intel :P Here is some output taken from lspci and > dmesg: > > 1. > 04:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA > G200eW WPCM450 (rev 0a) > Subsystem: Super Micro Computer Inc X9SCM-F Motherboard > Kernel driver in use: mgag200 > Kernel modules: mgag200 > > [ 12.997224] [drm] Initialized > [ 13.150842] fbcon: mgadrmfb (fb0) is primary device > [ 13.870421] mgag200 :04:03.0: fb0: mgadrmfb frame buffer device > [ 13.888499] [drm] Initialized mgag200 1.0.0 20110418 for :04:03.0 > on minor 0 > > 2. > 00:02.0 VGA compatible controller: Intel Corporation Atom Processor > D2xxx/N2xxx Integrated Graphics Controller (rev 09) > Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated > Graphics Controller > Kernel driver in use: gma500 > Kernel modules: gma500_gfx > - probably Intel 3600 graphics? (Not really Intel) > > [7.592556] [drm] Initialized > [7.987711] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [8.007901] [drm] No driver support for vblank timestamp query. > [8.682025] fb: switching to psbdrmfb from VESA VGA > [8.740893] fbcon: psbdrmfb (fb0) is primary device > [9.598838] gma500 :00:02.0: fb0: psbdrmfb frame buffer device > [9.613364] [drm] Initialized gma500 1.0.0 20140314 for :00:02.0 on > minor 0 > [ 32.791633] [drm:cdv_intel_dp_complete_link_train [gma500_gfx]] > *ERROR* failed to train DP, aborting > > With regards, > Henrik >
Setting a console resolution
Hi, I got two computers that usually run headless, but from time to time I might need to troubleshoot from the console. When I do this, I just connect a plain VGA cable to my 1920x1200 Dell monitor. Just upgraded to Stretch with kernel 4.9 and noticed that no matter what I do, the console resolution is 1920x1200. In addition, on the computer with the Matrox-adapter running something as simple as 'dmesg -T' is really really slow. It literally takes several seconds while the text scrolls on the screen. The thing is, I do not really care about fancy framebuffer resolution and graphics on the console. I just want fairly big text that scrolls without hiccups, even in 640x480 :P I have tried setting the resolution in /etc/default/grub: GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=keep Then running update-grub. The only thing that changes, is the grub-menu resolution, nothing else. I think the resolutions I have tried should be supported, given the output from 'vbeinfo' in Grub. I also gave a couple of kernel parameters a try, like video=1024x768x32. Even tried vga= and nomodeset, but I think doing this is deprecated. None of these methods seem to work. I believe the resolution is set through KMS, Kernel Mode Setting. Maybe I just need to blacklist some modules? I know the onboard graphic cards are quite cheap, the Intel one is not even made/supported by Intel :P Here is some output taken from lspci and dmesg: 1. 04:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) Subsystem: Super Micro Computer Inc X9SCM-F Motherboard Kernel driver in use: mgag200 Kernel modules: mgag200 [ 12.997224] [drm] Initialized [ 13.150842] fbcon: mgadrmfb (fb0) is primary device [ 13.870421] mgag200 :04:03.0: fb0: mgadrmfb frame buffer device [ 13.888499] [drm] Initialized mgag200 1.0.0 20110418 for :04:03.0 on minor 0 2. 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09) Subsystem: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller Kernel driver in use: gma500 Kernel modules: gma500_gfx - probably Intel 3600 graphics? (Not really Intel) [7.592556] [drm] Initialized [7.987711] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [8.007901] [drm] No driver support for vblank timestamp query. [8.682025] fb: switching to psbdrmfb from VESA VGA [8.740893] fbcon: psbdrmfb (fb0) is primary device [9.598838] gma500 :00:02.0: fb0: psbdrmfb frame buffer device [9.613364] [drm] Initialized gma500 1.0.0 20140314 for :00:02.0 on minor 0 [ 32.791633] [drm:cdv_intel_dp_complete_link_train [gma500_gfx]] *ERROR* failed to train DP, aborting With regards, Henrik
Re: text-mode : console : resolution : vga 80x25 : how to set?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, Oct 06, 2017 at 05:45:07PM +0530, Mayuresh Kathe wrote: > On 2017-10-06 05:30 PM, Darac Marjal wrote: > >On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote: > >>i tried my level best to do it, but have failed. > >>i used 'dpkg-reconfigure console-setup' and followed the > >>appropriate steps, but yet my console's screen resolution > >>is way to high. not that it's a big problem, just an > >>irritant, the text is usually too tiring to read. > >> > >>can i be helped? > > > >Yes. Presumably your system is using "kernel mode setting", wherein > >the kernel is able to set the resolution of the screen. This results, > >as you note, in a high-resolution console. > > would there be any simple way (instead of recompiling the kernel) to > disable that kernel mode setting for the resolution? This should be possible from the Linux kernel "command line", which you can append in the boot loader line. Try appending "nomodeset" to the boot line in grub (go into grub menu, press "e" on the entry you are going to boot, go one down for the kernel line, press "e" again to edit, append the "nomodeset", with space separator. Then ENTER to close the edit and "b" to boot). Depending on your video module you have to append other incantations, see e.g. [1]. Once you know it is working you can add it to the grub config to make it permanent. Cheers [1] https://wiki.archlinux.org/index.php/Kernel_mode_setting#Disabling_modesetting - -- t -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnXdswACgkQBcgs9XrR2kZbiQCfWZtMOuLuvoemJ9V8yvHk1wpK QJAAn2lCrx1KPfqQ8vuzNkhdxKokWxsY =LvW8 -END PGP SIGNATURE-
Re: text-mode : console : resolution : vga 80x25 : how to set?
Mayuresh Kathe composed on 2017-10-06 15:00 (UTC+0530): > i tried my level best to do it, but have failed. > i used 'dpkg-reconfigure console-setup' and followed the > appropriate steps, but yet my console's screen resolution > is way to high. not that it's a big problem, just an > irritant, the text is usually too tiring to read. > can i be helped? A rather simpler method than Darac suggested is to make the vttys use a lower density mode, accepting the default size 16 font. Include the mode you want on the kernel cmdline, either directly in the kernel: e.g. video=1280x800@60 or vga=normal, or indirectly using native Grub2 commands, according to the man page using /etc/default/grub's GRUB_GFXMODE_LINUX= and/or GRUB_GFXMODE=. If Plymouth is installed, purging it might also be of use. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: text-mode : console : resolution : vga 80x25 : how to set?
On 2017-10-06 05:30 PM, Darac Marjal wrote: On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote: i tried my level best to do it, but have failed. i used 'dpkg-reconfigure console-setup' and followed the appropriate steps, but yet my console's screen resolution is way to high. not that it's a big problem, just an irritant, the text is usually too tiring to read. can i be helped? Yes. Presumably your system is using "kernel mode setting", wherein the kernel is able to set the resolution of the screen. This results, as you note, in a high-resolution console. would there be any simple way (instead of recompiling the kernel) to disable that kernel mode setting for the resolution? thanks, ~mayuresh
Re: text-mode : console : resolution : vga 80x25 : how to set?
On Fri, Oct 06, 2017 at 03:00:50PM +0530, Mayuresh Kathe wrote: i tried my level best to do it, but have failed. i used 'dpkg-reconfigure console-setup' and followed the appropriate steps, but yet my console's screen resolution is way to high. not that it's a big problem, just an irritant, the text is usually too tiring to read. can i be helped? Yes. Presumably your system is using "kernel mode setting", wherein the kernel is able to set the resolution of the screen. This results, as you note, in a high-resolution console. You want to display 25 rows of 80 columns in your console, however, console-setup doesn't allow you to set that directly. Instead, you need to choose a font size. I *think* that the sizes here are listed in terms of pixels. So, you need to find an appropriate size. Let's assume that you have a WUXGA screen (1920x1080). Starting with the vertical resolution, you have 1080 pixels and you want to fit 25 rows of pixels in there. That's 1080/25=43.2 pixels. Let's round that down to 40. Horizontally, you have 1920 pixels and want to fit 80 characters there. That's 1920/80=24. So you're looking for a font that's 24x40 pixels. Next up, you'll notice that console-setup doesn't offer fonts that go that large, so you'll have to make your own. Start with an OpenType font of your choice and install the 'otf2bdf' and 'bdf2psf' packages. Finally, this page[1] suggests the following incantations (24 point font at 120 dpi should result in a font 40 dots high): otf2bdf -r 120 -p 24 -c C /path/to/OpenType.otf | sed -e \ "s/AVERAGE_WIDTH.*/AVERAGE_WIDTH 80/" > NewFont.bdf bdf2psf NewFont.bdf /usr/share/bdf2psf/standard.equivalents \ /usr/share/bdf2psf/required.set+/usr/share/bdf2psf/useful.set 256 \ NewFont.psf Finally, gzip this to, say /usr/share/consolefonts/Lat15-NewFont-24x40.psf.gz and you should be able to select it with debconf (If not, you may have to manually play with the 'setfont' command) [1] https://unix.stackexchange.com/questions/161890/how-can-i-make-a-psf-font-for-the-console-from-a-otf-one thanks, ~mayuresh -- For more information, please reread. signature.asc Description: PGP signature
text-mode : console : resolution : vga 80x25 : how to set?
i tried my level best to do it, but have failed. i used 'dpkg-reconfigure console-setup' and followed the appropriate steps, but yet my console's screen resolution is way to high. not that it's a big problem, just an irritant, the text is usually too tiring to read. can i be helped? thanks, ~mayuresh
Re: capturing console resolution from auto-detection for when KVM switched away?
On Mon 14 Nov 2011 at 21:48:05 -0500, Dan B. wrote: When I boot with my monitor connected (through a KVM), I end up with high-resolution virtual consoles (67 rows by 240 columns). However, when I boot with the KVM switched away, then since the kernel/etc. can't auto-detect my monitor, I get lower resolutions (48 rows by 128 columns, or 25 by 80 once). Have you got that the right way round? My experience is that with a KVM the monitor's EDID may not get passed to the computer. Of course, I'd like to force it to use the higher resolution regardless of which computer my KVM is switched to when this computer boots. Something like video=DVI-1:1280x1024 as a kernel parameter (when KMS is used) works for me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2015091601.GL2852@desktop
Re: capturing console resolution from auto-detection for when KVM switched away?
Brian wrote: On Mon 14 Nov 2011 at 21:48:05 -0500, Dan B. wrote: When I boot with my monitor connected (through a KVM), I end up with high-resolution virtual consoles (67 rows by 240 columns). However, when I boot with the KVM switched away, then since the kernel/etc. can't auto-detect my monitor, I get lower resolutions (48 rows by 128 columns, or 25 by 80 once). Have you got that the right way round? My experience is that with a KVM the monitor's EDID may not get passed to the computer. I think so. Note that _both_ of my cases are with a KVM: the first is when the KVM is switched to (connecting the monitor, etc., to) the computer I'm talking about, and one is when the KVM is switched away from the computer I'm talking about (switched to an otherwise unrelated computer). (I'm not talking about the case of having the monitor connected directly to the computer.) Of course, I'd like to force it to use the higher resolution regardless of which computer my KVM is switched to when this computer boots. Something like video=DVI-1:1280x1024 as a kernel parameter (when KMS is used) works for me. What tools (commands) are there in console-data or console-tools or whatever for getting (and changing) the console video settings? Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec28d55.3010...@kempt.net
Re: capturing console resolution from auto-detection for when KVM switched away?
On Tue 15 Nov 2011 at 11:03:33 -0500, Dan B. wrote: What tools (commands) are there in console-data or console-tools or whatever for getting (and changing) the console video settings? dpkg-reconfigure console-setup -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2015165451.GO2852@desktop
capturing console resolution from auto-detection for when KVM switched away?
What command shows the virtual console video mode (specifically, the information needed to set it to that mode if it's in a different mode)? When I boot with my monitor connected (through a KVM), I end up with high-resolution virtual consoles (67 rows by 240 columns). However, when I boot with the KVM switched away, then since the kernel/etc. can't auto-detect my monitor, I get lower resolutions (48 rows by 128 columns, or 25 by 80 once). Of course, I'd like to force it to use the higher resolution regardless of which computer my KVM is switched to when this computer boots. Thanks, Daniel -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ec1d2e5.1040...@kempt.net
Re: capturing console resolution from auto-detection for when KVM switched away?
On Lu, 14 nov 11, 21:48:05, Dan B. wrote: What command shows the virtual console video mode (specifically, the information needed to set it to that mode if it's in a different mode)? When I boot with my monitor connected (through a KVM), I end up with high-resolution virtual consoles (67 rows by 240 columns). However, when I boot with the KVM switched away, then since the kernel/etc. can't auto-detect my monitor, I get lower resolutions (48 rows by 128 columns, or 25 by 80 once). Anything interesting in dmesg? Of course, I'd like to force it to use the higher resolution regardless of which computer my KVM is switched to when this computer boots. I seem to recall that for KMS this is done via kernel parameters. Hope this helps, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Console resolution
On 18/02/11 20:11, Sven Joachim wrote: On 2011-02-18 20:22 +0100, Dom wrote: On 18/02/11 18:24, Camaleón wrote: To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau b) nvidia propietary driver c) vesa/fb d) nv (obsolete but still available, AFAICT) d) is the only option that worked for one of my machines. It used to run the nvidia driver, but stopped working when I upgraded it to squeeze and it tried to use the nouveau driver. My bad. I've checked that machine and remembered that I got nouveau to work once I'd removed all traces of the nvidia driver. The problem I had didn't relate to the display at all. That bit worked. However the mythtv backend segfaulted on one of the nvidia libraries. I don't know why the backend would even be touching video related stuff. It works fine with nouveau, and I'll stick with that. I'll be upgrading that box to Wheezy soon and see if I can get it to work properly with nouveau then. To make it clear, upgrading to Wheezy will be uninteresting for quite some time, because it will have the same nouveau version as Squeeze for the next few months. If you want to test a newer version, you need to upgrade the X stack as well as the kernel to the sid versions. Yes. I've been running the current testing on most of my systems for quite a few years now. In fact, since I found that the the only working video driver for my laptop (trident) was in lenny when lenny was testing. I've since moved my mythtv box to Wheezy without problems, and I don't anticipate any major ones in future. However, I'm not daft and I do regular backups of all my systems. Dom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d676bb0.8070...@rpdom.net
Re: Console resolution
On Vi, 18 feb 11, 19:22:07, Dom wrote: d) is the only option that worked for one of my machines. It used to run the nvidia driver, but stopped working when I upgraded it to squeeze and it tried to use the nouveau driver. Removing all traces of the nvidia driver and just using nouveau caused problems (I can't remember what they were now), but when I changed to the nv driver it was fine. One thing to consider is that nvidia-glx in lenny is version 173 of the driver, while squeeze it's 195. 195 has dropped support for some chipsets supported by 173, which means squeeze users might have to switch to the respective nvidia-glx-legacy package. Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Console resolution
On Fri, 18 Feb 2011 13:49:33 -0500, Paul Cartwright wrote: To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau so, what is this, why would I want it? It's another driver available for your card. It is open source and it uses reverse engineering techniques to provide 3D acceleration. Nvidia (the company) does not support it. (...) d) nv (obsolete but still available, AFAICT) I don't know if nv is still available in squeeze, I would imagine it is, but I hope I never have to use it! Why not? It used to be good enough for many of us and a couple of years ago, it was the only free alternative for nvidia cards. It provides only 2D acceleration and for that reason the nuvó project was started. Nv was getting direct support from Nvidia (the company). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.19.12.27...@gmail.com
Re: Console resolution
On Fri, 18 Feb 2011 19:56:50 +0100, Pier Paolo wrote: 2011/2/18 Camaleón What is what you tried hard, exactly? from rescue mode chrooting to recompile kernel after a not even system-base-install alternate cd netinstall. Booting from hard disk resulted in complete unusable system with vt blanked out I asked what you tried hard for the easy way, what steps did you follow and what errors did you get. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.19.12.31...@gmail.com
Re: Console resolution
2011/2/19 Camaleón noela...@gmail.com On Fri, 18 Feb 2011 19:56:50 +0100, Pier Paolo wrote: 2011/2/18 Camaleón What is what you tried hard, exactly? from rescue mode chrooting to recompile kernel after a not even system-base-install alternate cd netinstall. Booting from hard disk resulted in complete unusable system with vt blanked out I asked what you tried hard for the easy way, what steps did you follow and what errors did you get. Can't recall exactly... some procedure from the wiki; i think i blacklisted nouveau, and tried to install kernel-nvidia something, but substantially that won't prevent nouveau from loading and messing up console. i think actually the problem was nouveaufb than the xorg driver itself. But as now i'm running the modified kernel, so maybe that problem could be already resolved for my system (discrete nvidia 8400m i think: don't have here the hardware...) Greetings, Bye! -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.19.12.31...@gmail.com
Re: Console resolution
On Sat, 19 Feb 2011 14:55:55 +0100, Pier Paolo wrote: 2011/2/19 Camaleón I asked what you tried hard for the easy way, what steps did you follow and what errors did you get. Can't recall exactly... some procedure from the wiki; i think i blacklisted nouveau, and tried to install kernel-nvidia something, but substantially that won't prevent nouveau from loading and messing up console. Installing nvidia drivers (from debian non-free) should automatically perform the steps to disable nouveau (nvidia-kernel-common package cares about that). If that didn't work for you, you should have filled a bug report. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.19.14.09...@gmail.com
Re: Console resolution
2011/2/19 Camaleón noela...@gmail.com On Sat, 19 Feb 2011 14:55:55 +0100, Pier Paolo wrote: 2011/2/19 Camaleón I asked what you tried hard for the easy way, what steps did you follow and what errors did you get. Can't recall exactly... some procedure from the wiki; i think i blacklisted nouveau, and tried to install kernel-nvidia something, but substantially that won't prevent nouveau from loading and messing up console. Installing nvidia drivers (from debian non-free) should automatically perform the steps to disable nouveau (nvidia-kernel-common package cares about that). If that didn't work for you, you should have filled a bug report. It seems I missed my duties lst time! Beg your pardon... :-) But i'll have some spare time next week... expect a pair of install-report and maybe something! Greetings, thanks -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.19.14.09...@gmail.com
Re: Console resolution
On Sat, 19 Feb 2011 15:17:15 +0100, Pier Paolo wrote: 2011/2/19 Camaleón Can't recall exactly... some procedure from the wiki; i think i blacklisted nouveau, and tried to install kernel-nvidia something, but substantially that won't prevent nouveau from loading and messing up console. Installing nvidia drivers (from debian non-free) should automatically perform the steps to disable nouveau (nvidia-kernel-common package cares about that). If that didn't work for you, you should have filled a bug report. It seems I missed my duties lst time! Beg your pardon... :-) Okay... but no until you start sending text-based e-mails ;-) But i'll have some spare time next week... expect a pair of install-report and maybe something! Good! Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.19.14.26...@gmail.com
Re: Console resolution
On Thu, 17 Feb 2011 20:07:51 -0500, Chris Brennan wrote: I am not new to the linux way of things but I am new to the debain way of things and I have some questions that need to be answered. To start, I need to ket rid of nouveau as it's screwing with uvesafb (produces an 'Error -22'). (...) By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.18.12.41...@gmail.com
Re: Console resolution
2011/2/18 Camaleón noela...@gmail.com On Thu, 17 Feb 2011 20:07:51 -0500, Chris Brennan wrote: I am not new to the linux way of things but I am new to the debain way of things and I have some questions that need to be answered. To start, I need to ket rid of nouveau as it's screwing with uvesafb (produces an 'Error -22'). (...) By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. At least in Debian Lenny and Fedora 12 it was not so simple as said in debian wiki or by you; i tried hard to find the easy way, but it turns out that recompile the kernel without support for staging drivers / nouveau was the sensefull thing, even if pretty hard to mantain in fedora. donnow about squeeze now. (running ati) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.18.12.41...@gmail.com
Re: Console resolution
El 2011-02-18 a las 10:33 -0500, Chris Brennan escribió: On Fri, Feb 18, 2011 at 7:41 AM, Camaleón wrote: By installing nvidia driver, nuvó should not be loaded. the non-free nvidia driver script/installer dies, complaining that nouveau is present and needs to be removed first, this is what I need to know how to do. I've tried my usual linux methods with no success (and no real point reiterating them here). Suffice it to say, I *NEED* to know the debian/debian-correct way of doing this as my methods have proven unsuccessful. Nvidia's own installer (the one you get when downloading the driver from nvidia site) needs some things to be before installing it: One is you drop your X session and the other is that you have to disable nuvó, yes (additional -and well explained- information can be found here): http://us.download.nvidia.com/XFree86/Linux-x86/260.19.36/README/installdriver.html But you can also install the Nvidia driver by using Debian's own packages which should automatically disable nuvó+KMS. http://wiki.debian.org/NvidiaGraphicsDrivers Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. KMS? What is this? where is nouveau.modeset=0 set? In what file? KMS stands for Kernel Mode Setting, a new way for the kernel to manage the graphics of the system... well, sort of :-P http://wiki.debian.org/KernelModesetting In brief, newer kernels enable by default the kernel mode setting so if you need to disable it, you can append the aforementioned line to Grub's menu at boot time. P.S. Please keep in mind, I am trying to learn the debian-way of doing things so please be explicit when offering hints. Reading the wiki helps a lot ;-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110218155047.ga6...@stt008.linux.site
Re: Console resolution
Camaleón wrote: El 2011-02-18 a las 10:33 -0500, Chris Brennan escribió: On Fri, Feb 18, 2011 at 7:41 AM, Camaleón wrote: By installing nvidia driver, nuvó should not be loaded. the non-free nvidia driver script/installer dies, complaining that nouveau is present and needs to be removed first, this is what I need to know how to do. I've tried my usual linux methods with no success (and no real point reiterating them here). Suffice it to say, I *NEED* to know the debian/debian-correct way of doing this as my methods have proven unsuccessful. Nvidia's own installer (the one you get when downloading the driver from nvidia site) needs some things to be before installing it: One is you drop your X session and the other is that you have to disable nuvó, yes (additional -and well explained- information can be found here): http://us.download.nvidia.com/XFree86/Linux-x86/260.19.36/README/installdriver.html and you need to install the kernel-headers package. Hugo But you can also install the Nvidia driver by using Debian's own packages which should automatically disable nuvó+KMS. http://wiki.debian.org/NvidiaGraphicsDrivers Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. KMS? What is this? where is nouveau.modeset=0 set? In what file? KMS stands for Kernel Mode Setting, a new way for the kernel to manage the graphics of the system... well, sort of :-P http://wiki.debian.org/KernelModesetting In brief, newer kernels enable by default the kernel mode setting so if you need to disable it, you can append the aforementioned line to Grub's menu at boot time. P.S. Please keep in mind, I am trying to learn the debian-way of doing things so please be explicit when offering hints. Reading the wiki helps a lot ;-) Greetings, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ijmah7$95b$2...@dough.gmane.org
Re: Console resolution
On Fri, 18 Feb 2011 17:40:40 +0100, Pier Paolo wrote: 2011/2/18 Camaleón By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. At least in Debian Lenny and Fedora 12 it was not so simple as said in debian wiki or by you; That's hard to believe... Lenny's stock kernel does not enable KMS at all ;-) i tried hard to find the easy way, but it turns out that recompile the kernel without support for staging drivers / nouveau was the sensefull thing, even if pretty hard to mantain in fedora. donnow about squeeze now. (running ati) What is what you tried hard, exactly? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.18.17.41...@gmail.com
Re: Console resolution
On 02/18/2011 07:41 AM, Camaleón wrote: By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. Greetings, wow, I just looked at my new Squeeze xorg.conf device section. What is the nouveau, and should we be using/not using it?? Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor # [bool] #Option HWcursor # [bool] #Option NoAccel# [bool] #Option ShadowFB # [bool] #Option UseFBDev # [bool] #Option Rotate # [str] #Option VideoKey # i #Option FlatPanel # [bool] #Option FPDither # [bool] #Option CrtcNumber # i #Option FPScale# [bool] #Option FPTweak# i #Option DualHead # [bool] Identifier Card0 Drivernvidia Option Coolbits1 Option AddARGBGLXVisualstrue Option TripleBufferfalse VendorName nVidia Corporation BoardName G72 [GeForce 7300 LE] BusID PCI:1:0:0 EndSection -- Paul Cartwright -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d5eb4dc.1020...@pcartwright.com
Re: Console resolution
On Fri, 18 Feb 2011 13:05:16 -0500, Paul Cartwright wrote: On 02/18/2011 07:41 AM, Camaleón wrote: By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. wow, I just looked at my new Squeeze xorg.conf device section. What is the nouveau, and should we be using/not using it?? Section Device (...) Drivernvidia ^^ You are not using nuvó at all but the nvidia driver :-) To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau b) nvidia propietary driver c) vesa/fb d) nv (obsolete but still available, AFAICT) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.18.18.24...@gmail.com
Re: Console resolution
Drivernvidia ^^ You are not using nuvó at all but the nvidia driver:-) right, I knew that. To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau so, what is this, why would I want it? b) nvidia propietary driver c) vesa/fb d) nv (obsolete but still available, AFAICT) I don't know if nv is still available in squeeze, I would imagine it is, but I hope I never have to use it! -- Paul Cartwright -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d5ebf3d.3060...@pcartwright.com
Re: Console resolution
2011/2/18 Camaleón noela...@gmail.com On Fri, 18 Feb 2011 17:40:40 +0100, Pier Paolo wrote: 2011/2/18 Camaleón By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. At least in Debian Lenny and Fedora 12 it was not so simple as said in debian wiki or by you; That's hard to believe... Lenny's stock kernel does not enable KMS at all ;-) i tried hard to find the easy way, but it turns out that recompile the kernel without support for staging drivers / nouveau was the sensefull thing, even if pretty hard to mantain in fedora. donnow about squeeze now. (running ati) What is what you tried hard, exactly? from rescue mode chrooting to recompile kernel after a not even system-base-install alternate cd netinstall. Booting from hard disk resulted in complete unusable system with vt blanked out Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.02.18.17.41...@gmail.com
Re: Console resolution
On Fri, 18 Feb 2011 10:21:30 -0500 (EST), Chris Brennan wrote: On Thu, Feb 17, 2011 at 8:33 PM, Stephen Powell zlinux...@wowway.comwrote: Blacklisting a module only prevents udev from loading it. That's because when udev loads a module it uses the -b switch of the modprobe command. However, when the X server loads a module, it does not use the -b switch of modprobe. They key is to get the X server to not load it. Well, even w/ nouveau in /etc/modpoobrobe.d/blacklist.conf, it is still being loaded by the kernel at boot. I need to ax nouveau first as this is screwing up my console resolution as well as not displaying things in X correctly (unreadable in fact, but I am able to drop back to console and cleanly terminate X w/ '/etc/init.d/kdm stop'. First of all, please reply to the list for the benefit of others following the thread and so that the list archives can keep the thread tied together (by using the In-Reply-To field in the message headers). You sent this as a private e-mail. I'm putting it back on the list where it belongs. Second, are you sure that you blacklisted it correctly? I don't recommend that you edit the Debian-supplied file /etc/modprobe.d/blacklist.conf, or any other Debian-supplied file in this directory, as that could change with a future package upgrade. What I did was create a file called /etc/modprobe.d/local.conf. (The file name can be anything, but the extension must be .conf.) Its contents are as follows: blacklist nouveau options nouveau modeset=0 The first statement prevents udev from loading the module. The second statement sets KMS off in case the module somehow gets loaded anyway. The X server won't use the xserver-xorg-video-nouveau driver if KMS is off. Also, make sure that /etc/modprobe.conf does NOT exist. If it does, it will override the files in the /etc/modprobe.d directory. Finally, you must re-build your initial RAM file system, since these files are included in the initial RAM file system. After making the above changes, issue update-initramfs -uk `uname -r` Then run your boot loader installer, if necessary. Then shutdown and reboot. Do all this as root of course. I couldn't use nouveau either because my monitor requires an interlaced video mode. The nouveau driver apparently doesn't support interlacing, or at least the version I tried at the time did not. Create a file called /etc/X11/xorg.conf and put the following in it: Section Device Identifier Configured Video Device Driver nv EndSection If your video card chipset is old enough to be supported by the free nv driver, which Nvidia no longer maintains, this should work. If the nv driver won't work, you can try a more generic driver, such as vesa. Sadly, the GeForce Mobile card in my laptop will only work with the non-free drivers from nVidia. I did get the free drivers to work a few times w/ Fedora Core 9 - 12 but I never figured out how. It should work with the vesa driver. All modern video cards are supposed to be vesa-capable. Just change nv to vesa in the /etc/X11/xorg.conf file as I outlined above. Of course, performance will not be great, since it is unaccelerated, but at least it will give you a functional desktop to work with until you can get the proprietary drivers working. I saw in another post that you are thinking of compiling a custom kernel. I don't think it will be necessary to do that. But if you need or want to compile a custom kernel, here's a link that explains the Debian way (or at least one Debian way) to compile a custom kernel. It even has an example which includes the proprietary Nvidia drivers. (See the section titled A Specific Example.) http://users.wowway.com/~zlinuxman/Kernel.htm -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1975628731.910775.1298056809644.javamail.r...@md01.wow.synacor.com
Re: Console resolution
On 18/02/11 18:24, Camaleón wrote: On Fri, 18 Feb 2011 13:05:16 -0500, Paul Cartwright wrote: On 02/18/2011 07:41 AM, Camaleón wrote: By installing nvidia driver, nuvó should not be loaded. Also, by disabling KMS (nouveau.modeset=0) nuvó should not load. wow, I just looked at my new Squeeze xorg.conf device section. What is the nouveau, and should we be using/not using it?? Section Device (...) Drivernvidia ^^ You are not using nuvó at all but the nvidia driver :-) To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau b) nvidia propietary driver c) vesa/fb d) nv (obsolete but still available, AFAICT) d) is the only option that worked for one of my machines. It used to run the nvidia driver, but stopped working when I upgraded it to squeeze and it tried to use the nouveau driver. Removing all traces of the nvidia driver and just using nouveau caused problems (I can't remember what they were now), but when I changed to the nv driver it was fine. I'll be upgrading that box to Wheezy soon and see if I can get it to work properly with nouveau then. Oddly, another similar box works fine with either the nvidia driver or nouveau. I'm not doing anything with it right now, because I like being able to watch MythTV. ;-) Dom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d5ec6df.80...@rpdom.net
Re: Console resolution
On 2011-02-18 20:22 +0100, Dom wrote: On 18/02/11 18:24, Camaleón wrote: To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau b) nvidia propietary driver c) vesa/fb d) nv (obsolete but still available, AFAICT) d) is the only option that worked for one of my machines. It used to run the nvidia driver, but stopped working when I upgraded it to squeeze and it tried to use the nouveau driver. Removing all traces of the nvidia driver and just using nouveau caused problems (I can't remember what they were now), but when I changed to the nv driver it was fine. I'll be upgrading that box to Wheezy soon and see if I can get it to work properly with nouveau then. To make it clear, upgrading to Wheezy will be uninteresting for quite some time, because it will have the same nouveau version as Squeeze for the next few months. If you want to test a newer version, you need to upgrade the X stack as well as the kernel to the sid versions. Oddly, another similar box works fine with either the nvidia driver or nouveau. What matters are the graphics card and the monitor (the latter usually only if it's broken, e.g. reporting no or wrong EDID). Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aahtayrw@turtle.gmx.de
Re: Console resolution
On Fri, 18 Feb 2011 13:49:33 -0500 (EST), Paul Cartwright wrote: Camaleón wrote: You are not using nuvó at all but the nvidia driver:-) right, I knew that. To make this a bit more clear, nvidia card owners can run either: a) KMS+nouveau ... so, what is this, why would I want it? The nvidia driver offers both 2D and 3D acceleration. But it is non-free. The nv driver is free, but does not offer 3D acceleration. It generally does offer 2D acceleration though. Nvidia's historical position on the nv driver is that they offer it so the user will have a driver to use during installation. It can then be upgraded to the nvidia driver after installation. But they dropped support for the nv driver about a year ago, I think. The rationale is that the user can use the vesa driver during installation and then install the nvidia driver after installation. That did not set well with those who wish to use all free software. With nv, they at least got 2D acceleration. With vesa, I don't think there's even 2D acceleration. The nouveau driver is an attempt to create a free driver that offers both 2D and 3D acceleration. Since Nvidia stubbornly refuses to publish the specs, the nouveau driver had to be reverse-engineered. It doesn't support all modes of all nvidia chipsets, but a number of them do seem to work with the nouveau driver. You would want the nouveau driver if you wanted 3D acceleration but didn't want to use proprietary, non-free software, such as the nvidia driver. If you already have the nvidia driver installed, and it is working for you, you probably don't want to switch to nouveau. b) nvidia propietary driver c) vesa/fb d) nv (obsolete but still available, AFAICT) I don't know if nv is still available in squeeze, I would imagine it is, but I hope I never have to use it! It is still available in Squeeze, and in Wheezy also, and I use it. I'll tell you why. My video card is an old one. It has a RIVA TNT2 / TNT2 Pro chipset. This chipset supports interlaced video modes. My monitor requires an interlaced video mode. I cannot use the proprietary nvidia driver because I would need the 71xx-series driver to support a chipset this old, and Nvidia has not enhanced this driver series to support the release of the X server that runs under Squeeze. And they have no plans to do so. I cannot use the nouveau driver because it does not work with interlaced video modes. (Or at least it did not the last time I checked.) I could use the vesa driver, I suppose, but it does not offer 2D acceleration. So the nv driver is my choice. It supports my chipset, it supports interlaced video modes on my chipset, and it at least offers 2D acceleration. If I have made any factually incorrect statements, someone please correct me. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/417885689.915242.1298067686538.javamail.r...@md01.wow.synacor.com
Console resolution
I am not new to the linux way of things but I am new to the debain way of things and I have some questions that need to be answered. To start, I need to ket rid of nouveau as it's screwing with uvesafb (produces an 'Error -22'). I added it to /etc/modprobe.d/blacklist.conf but it's still being loaded. Nouveau is also only using the top-left quarter of my laptop's display and it's rather annoying. Once I can get rid of Nouveau I can then work on getting my nvidia driver loaded and I can use X ... as it stans nouveau is also not working correctly with X ... I get a very corrupt display but otherwise functional, just very hard to see. P.S. I tried hitting freenode/#debian but they were utterly useless in trying to actually help, people there were actually rather rude to me, I was told more then once to search google (which btw offered no real solutions). -- Did you know... If you play a Windows 2000 CD backwards, you hear satanic messages, but what's worse is when you play it forward ...it installs Windows 2000 -- Alfred Perlstein on chat at freebsd.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktingr6auzaxor_g_nay+gyozagkbtnjkr7krq...@mail.gmail.com
Re: Console resolution
On Thu, 17 Feb 2011 20:07:51 -0500 (EST), Chris Brennan wrote: I am not new to the linux way of things but I am new to the debain way of things and I have some questions that need to be answered. To start, I need to ket rid of nouveau as it's screwing with uvesafb (produces an 'Error -22'). I added it to /etc/modprobe.d/blacklist.conf but it's still being loaded. Blacklisting a module only prevents udev from loading it. That's because when udev loads a module it uses the -b switch of the modprobe command. However, when the X server loads a module, it does not use the -b switch of modprobe. They key is to get the X server to not load it. Nouveau is also only using the top-left quarter of my laptop's display and it's rather annoying. Once I can get rid of Nouveau I can then work on getting my nvidia driver loaded and I can use X ... as it stans nouveau is also not working correctly with X ... I get a very corrupt display but otherwise functional, just very hard to see. I couldn't use nouveau either because my monitor requires an interlaced video mode. The nouveau driver apparently doesn't support interlacing, or at least the version I tried at the time did not. Create a file called /etc/X11/xorg.conf and put the following in it: Section Device Identifier Configured Video Device Driver nv EndSection If your video card chipset is old enough to be supported by the free nv driver, which Nvidia no longer maintains, this should work. If the nv driver won't work, you can try a more generic driver, such as vesa. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/869835930.895303.1297992819198.javamail.r...@md01.wow.synacor.com
Re: Console resolution
I am not new to the linux way of things but I am new to the debain way of things and I have some questions that need to be answered. To start, I need to ket rid of nouveau as it's screwing with uvesafb (produces an 'Error -22'). I added it to /etc/modprobe.d/blacklist.conf but it's still being loaded. Nouveau is also only using the top-left quarter of my laptop's display and it's rather annoying. Once I can get rid of Nouveau I can then work on getting my nvidia driver loaded and I can use X ... as it stans nouveau is also not working correctly with X ... I get a very corrupt display but otherwise functional, just very hard to see. P.S. I tried hitting freenode/#debian but they were utterly useless in trying to actually help, people there were actually rather rude to me, I was told more then once to search google (which btw offered no real solutions). . This is from my install notes, may not be for the version of Debian you have installed, but hope it helps Tim. --- nvidia drivers I did this with lenny 5.x got this info from http://wiki.debian.org/NvidiaGraphicsDrivers make sure non-free is included in the /etc/apt/sources.list file remember to apt-get update after changing the sources file run the script at the following location to find out which drivers to use http://wiki.debian.org/NvidiaGraphicsDrivers?action=AttachFiledo=viewtarget=nvidia-versions.sh assuming you can use all / default drivers (My current card can) then do apt-get install module-assistant nvidia-kernel-common m-a auto-install nvidia-kernel-source apt-get install nvidia-glx in /etc/X11/xorg.conf add the line to the Device section Driver nvidia restart X and test, you want to see direct rendering: Yes with: glxinfo | grep rendering -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ecd26527873559c6cbf66c8b801eb82c.squirrel@192.168.1.100
Re: Re: Re: console resolution
On Wed, Jan 27, 2010 at 09:17:51PM +0200, Andrei Popescu wrote:
On Sun,24.Jan.10, 14:22:22, Nima Azarbayjany wrote:
I was able to achieve the desired resolution of 1280x800 (equivalent
to, I think, 0x361) by manually editing grub.cfg but the grub menu
does not show correctly. It only fills the left top quarter of the
screen and parts of it cannot be seen. The rest was fine (the boot
up of linux I mean) with a good resolution. I will try setting the
resolutions separately, i.e., not using gfxpayload=keep.
Are you running update-grub2 after editing the files? See below for the
files I changed.
As far as I can tell this is due to the background image being too small
and the text is now black on black. Try using a bigger picture ;)
I struck that also using grub2-splashimages. The fix is to edit
/etc/grub.d/00_header:
...
case ${platform}:${GRUB_TERMINAL} in
pc:gfxterm)
# Make the font accessible
prepare_grub_to_access_device `${grub_probe} --target=device
${GRUB_FONT_PATH}`
cat EOF
if font `make_system_path_relative_to_its_root ${GRUB_FONT_PATH}` ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
terminal gfxterm
fi
...
See where set gfxmode=640x480, that allows the menu to be 640x480
(which the grub2-splashimages mentions in
/usr/share/doc/grub2-splashimages/README) while setting:
GRUB_CMDLINE_LINUX=vga=791
in /etc/default/grub allows the kernel to boot in the higher res.
This is on Lenny and everything is working fine.
Looks like a bug in /usr/share/doc/grub2-splashimages/README where it
says to run update-grub, that should be update-grub2.
--
Chris.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: Re: console resolution
On Tue, Feb 02, 2010 at 01:50:23AM +1300, Chris Bannister wrote: Looks like a bug in /usr/share/doc/grub2-splashimages/README where it says to run update-grub, that should be update-grub2. Arrrgh ... I see that: fischer:~# less /usr/sbin/update-grub2 #!/bin/sh -e exec update-grub Sorry about the noise. -- Chris. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Fri,22.Jan.10, 15:38:55, Nima Azarbayjany wrote: Hi, I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. Latest grub in sid now sets gfxpayload=keep. This means that whatever (valid) resolution you set in /etc/default/grub with the GRUB_GFXMODE parameter it will be kept also for the linux console. You can expect it to arrive in testing in about 9 days http://release.debian.org/migration/testing.pl?package=grub-pc Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: Re: Re: console resolution
On Sun,24.Jan.10, 14:22:22, Nima Azarbayjany wrote: I was able to achieve the desired resolution of 1280x800 (equivalent to, I think, 0x361) by manually editing grub.cfg but the grub menu does not show correctly. It only fills the left top quarter of the screen and parts of it cannot be seen. The rest was fine (the boot up of linux I mean) with a good resolution. I will try setting the resolutions separately, i.e., not using gfxpayload=keep. As far as I can tell this is due to the background image being too small and the text is now black on black. Try using a bigger picture ;) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
Re: console resolution
e5ylm-7ry...@gated-at.bofh.it e5zy9-cm...@gated-at.bofh.it e5axg-2q7...@gated-at.bofh.it e5eet-7l...@gated-at.bofh.it On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote: [..] I don't know if my video card takes care of that, but I find that moving the cursor, scrolling, etc. is noticeably faster on a framebuffer console than on the vga console. Mind you, since the vesa driver does not support my display's native 1400x1050, I use the atyfb driver. So I'm not sure how it would handle if I used the vga=xxx modes. do you know if there is still a limitation of using the nvidia framebuffer and the nvidia binary driver ? [..] -- You will be the victim of a bizarre joke. :-) I the above question the bizarre joke, or was this meant as a reply to a different post? Sorry didn't see this reply. The thread was about frame buffer and console resolution (atleast where I jump on). I was just asking weather or not there was still and issue with the proprietary nvidia X driver and the nv framebuffer driver - I remember before you could not use both at the same time, wondering if the same was try now I am presuming you have mistaken my signature for more than it is CJ signature.asc Description: Digital signature
Re: console resolution
s. keeling wrote: Jeffrey Cao jcao.li...@gmail.com: On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote: I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. For the new grub, edit the file /etc/default/grub, add the following line: GRUB_CMDLINE_LINUX=vga=xxx And then run 'update-grub' to update /boot/grub/grub.cfg Isn't it strange that we now need to `update-grub`, when having to run lilo was such a hardship before? That does it. I'm going back to lilo. Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot menu, grumble, mumble, ... Grr. Hi grumpy, update-grub is only needed when configuration is manually edited, which seems fair to me as I don't see grub poling it's configuration scripts every few minutes to see if the volatile user made some change. We sure lost a bit of user-friendliness having several configuration to edit instead of just the menu.lst from grub-legacy, I guess that's the price to pay for flexibility, but judging by the number of messages about grub-legacy problems all over the Internet it's wasn't that much user-friendly anyway... Can't comment on OpenBSD, maybe a filesystem compatibility problem ? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
Okay... I finally got it to work. I set two different resolutions, that is, I did not use gfxpayload=keep. Thanks all. Nima -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
tv.deb...@googlemail.com tv.deb...@googlemail.com: s. keeling wrote: Isn't it strange that we now need to `update-grub`, when having to run lilo was such a hardship before? Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot menu, grumble, mumble, ... Grr. Hi grumpy, It's a fair cop. :-| update-grub is only needed when configuration is manually edited, My complaint is neither grub-legacy nor grub2 ever pick up my OBSD install, yet /etc/grub.d/40_custom is there and describes it, and /boot/grub/menu.lst is there to upgrade from. aptitude reinstall $blah never gets OBSD into the boot menu. Never works (not complaining, just reporting; I'll check bugs.debian.org for similar when I've time). Can't comment on OpenBSD, maybe a filesystem compatibility problem ? Debian's fdisk manages it (type a6 OpenBSD). I'll keep banging my head on it. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Mon, Jan 25, 2010 at 10:26:45PM EST, s. keeling wrote: [..] My complaint is neither grub-legacy nor grub2 ever pick up my OBSD install, yet /etc/grub.d/40_custom is there and describes it, and /boot/grub/menu.lst is there to upgrade from. Just be aware that auto-detecting kernels is not done by grub, but by a separate utility called os-prober. The os-prober conmprises a bunch of shell scripts, which you will have to read to investigate further, since it ships with absolutely zero documentation. Due in part to these aspects, but mostly because I have a bunch of legacy systems that have all kind of unmaintained junk in the grub part of their /boot directory, I have removed os-prober and entered my stuff manually in /etc/grub/40-custom on the system where the active grub dwells so I know what I'm doing. CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
My complaint is neither grub-legacy nor grub2 ever pick up my OBSD
install, yet /etc/grub.d/40_custom is there and describes it, and
/boot/grub/menu.lst is there to upgrade from.
From
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/432254
I finally got the boot into FreeBSD to work.
Here's what I put in 40_custom before running update-grub:
...
menuentry freebsd {
set root=(hd0,2,a)
chainloader +1
boot
}
So the root specification is based on the FreeBSD slice (number) and
partition (letter) method of specifying a partition, as in the legacy
GRUB, except that the primary partition (slice) numbering starts at
1 rather than 0.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: Re: console resolution
I was able to achieve the desired resolution of 1280x800 (equivalent to,
I think, 0x361) by manually editing grub.cfg but the grub menu does not
show correctly. It only fills the left top quarter of the screen and
parts of it cannot be seen. The rest was fine (the boot up of linux I
mean) with a good resolution. I will try setting the resolutions
separately, i.e., not using gfxpayload=keep.
Are you making all the changes that have been suggested?
In short:
In
/etc/default/grub
add
GRUB_GFXPAYLOAD=keep
on the line after
GRUB_GFXMODE=resolution
In
/etc/grub.d/00_header
add
if [ x${GRUB_GFXPAYLOAD} = x ] ; then GRUB_GFXPAYLOAD=640x480 ; fi
on the line after
if [ x${GRUB_GFXMODE} = x ] ; then GRUB_GFXMODE=640x480 ; fi
In
/etc/grub.d/00_header
add
set gfxpayload=${GRUB_GFXPAYLOAD}
on the line after
set gfxmode=${GRUB_GFXMODE}
Run
update-grub
or
update-grub2
I did install grub-legacy at some point but removed it almost
immediately. I have reinstalled the grub-pc package and done everything
to make sure it's a clean install not mixed with grub-legacy. It seems
to be so.
This could mean your grub install is somehow broken, try to renew it
from scratch, not mixing both grub-pc (grub2) and grub-legacy. Or
maybe you have typos somewhere in the variables so that they are not
picked up by update-grub (you can also call grub-mkconfig -o
/boot/grub/grub.cfg for grub-pc).
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: Re: console resolution
On Sun, Jan 24, 2010 at 05:52:22AM EST, Nima Azarbayjany wrote: I was able to achieve the desired resolution of 1280x800 (equivalent to, I think, 0x361) by manually editing grub.cfg but the grub menu does not show correctly. It only fills the left top quarter of the screen and parts of it cannot be seen. The rest was fine (the boot up of linux I mean) with a good resolution. I will try setting the resolutions separately, i.e., not using gfxpayload=keep. I was able to get everything grub2 to work in about a couple of hours hanging out at freenode.net/#grub and I never looked back. CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
Jeffrey Cao jcao.li...@gmail.com: On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote: I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. For the new grub, edit the file /etc/default/grub, add the following line: GRUB_CMDLINE_LINUX=vga=xxx And then run 'update-grub' to update /boot/grub/grub.cfg Isn't it strange that we now need to `update-grub`, when having to run lilo was such a hardship before? That does it. I'm going back to lilo. Grumble, mumble, wtf doesn't OpenBSD ever show up in the grub* boot menu, grumble, mumble, ... Grr. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://blinkynet.net/comp/uip5.html Linux Counter #80292 - -http://www.faqs.org/rfcs/rfc1855.htmlPlease, don't Cc: me. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Sat, Jan 23, 2010 at 01:15:39AM EST, Chris Jones wrote: [..] I the above question the bizarre joke, or was this meant as a reply to a different post? s/I the above/Is the above/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
Nima Azarbayjany wrote:
set gfxpayload=keep will tell Grub2 to hand off the graphics settings
to the kernel, which if configured properly will carry them forward.
There are some other settings to tweak as well, insmod vbe and whatnot
in the appropriate file, but that's about the gist of it. The nice
thing is it makes for very smooth transitions when switching from
terminal to x, as the display settings (if correctly configured) are
already applied, thus, no ugly flashing of the screen and delay.
Best,
Arthur
Would you please explain how and where to insert this into Grub's
configuration? I played with /etc/default/grub and update-grub but no
success.
Jeffrey Cao wrote in another post that grub2 can support the traditional
vga kernel option by means of editing /etc/default/grub and adding the
line
GRUB_CMDLINE_LINUX=vga=xxx
and then running update-grub to update /boot/grub/grub.cfg. But I
haven't tried it myself. I'm not going to de-install lilo and install
grub2 to find out. But next time I try a Squeeze install from scratch,
I might give it a try.
I tried this one but it too didn't work. It says that vga=xxx is
deprecated.
Jeffrey Cao wrote in another post that grub2 can support the traditional
vga kernel option by means of editing /etc/default/grub and adding the
line
GRUB_CMDLINE_LINUX=vga=xxx
and then running update-grub to update /boot/grub/grub.cfg. But I
haven't tried it myself. I'm not going to de-install lilo and install
grub2 to find out. But next time I try a Squeeze install from scratch,
I might give it a try.
This one did not work as well.
I guess I'm going to install grub1 for now.
Nima
Hi, I use a slightly different way, I put:
GRUB_GFXMODE=1440x900 640x480
in /etc/defaults/grub (native resolution first, fall-back one isn't
necessary, it's the default).
Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
(around line 80):
[...]
if loadfont `make_system_path_relative_to_its_root ${GRUB_FONT_PATH}` ; then
set gfxmode=${GRUB_GFXMODE}
set gfxpayload=keep here it is
insmod gfxterm
insmod ${GRUB_VIDEO_BACKEND}
if terminal_output gfxterm ; then true ; else
[...]
It's working for me on Debian Squeeze and Ubuntu, but needs to be
updated if 00_header is overwritten during update (not often). It's just
a workaround until gfxpayload= is picked up in /etc/default/grub.
My 2 cents.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On 2010-01-22 at 18:11:38 -0500, Chris Jones wrote: PIII 650MHz - 386M of RAM - ATI Rage Mobility (Mach64). That is *lightning fast* compared to my slowest machine, a PII 266 MHz with a very slow hard drive. And the saddest thing is, until about three years ago, it was my fastest machine! The bottom line is this: with a true text-mode virtual console, the conversion of characters to pixels on the screen is done in the video hardware itself. The main CPU doesn't have to do it. That's what the video card's text mode is designed to do, and it does it very well. In graphics mode the conversion from characters to pixels is done by the main CPU chip. My philosophy is to let the video hardware do what it was designed to do and free the main CPU chip for other uses. There are times when graphics mode is needed, of course. But editing text or perusing text isn't one of them. To each his own. Peace. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: console resolution
It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?
Hi, I use a slightly different way, I put:
GRUB_GFXMODE=1440x900 640x480
in /etc/defaults/grub (native resolution first, fall-back one isn't
necessary, it's the default).
Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
(around line 80):
[...]
if loadfont `make_system_path_relative_to_its_root ${GRUB_FONT_PATH}` ; then
set gfxmode=${GRUB_GFXMODE}
set gfxpayload=keep here it is
insmod gfxterm
insmod ${GRUB_VIDEO_BACKEND}
if terminal_output gfxterm ; then true ; else
[...]
It's working for me on Debian Squeeze and Ubuntu, but needs to be
updated if 00_header is overwritten during update (not often). It's just
a workaround until gfxpayload= is picked up in /etc/default/grub.
My 2 cents.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: console resolution
It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?
Are you making all the changes that have been suggested?
In short:
In
/etc/default/grub
add
GRUB_GFXPAYLOAD=keep
on the line after
GRUB_GFXMODE=resolution
In
/etc/grub.d/00_header
add
if [ x${GRUB_GFXPAYLOAD} = x ] ; then GRUB_GFXPAYLOAD=640x480 ; fi
on the line after
if [ x${GRUB_GFXMODE} = x ] ; then GRUB_GFXMODE=640x480 ; fi
In
/etc/grub.d/00_header
add
set gfxpayload=${GRUB_GFXPAYLOAD}
on the line after
set gfxmode=${GRUB_GFXMODE}
Run
update-grub
or
update-grub2
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
tv.debian wrote:
Hi, I use a slightly different way, I put:
GRUB_GFXMODE=1440x900 640x480
in /etc/defaults/grub (native resolution first, fall-back one isn't
necessary, it's the default).
Then in /etc/grub.d/00_header I add gfxpayload=keep to this section
(around line 80):
[...]
if loadfont `make_system_path_relative_to_its_root ${GRUB_FONT_PATH}`
; then
set gfxmode=${GRUB_GFXMODE}
set gfxpayload=keep here it is
insmod gfxterm
insmod ${GRUB_VIDEO_BACKEND}
if terminal_output gfxterm ; then true ; else
[...]
It's working for me on Debian Squeeze and Ubuntu, but needs to be
updated if 00_header is overwritten during update (not often). It's just
a workaround until gfxpayload= is picked up in /etc/default/grub.
My 2 cents.
Nima Azarbayjany wrote:
It's weird but it's not working for me. Somehow update-grub (as well as
update-grub2, in case they are different) ignore all modifications to
/etc/default/grub. I'm giving up. Should I report a bug?
[I re-arranged the message in chronological order to remove top posting]
This could mean your grub install is somehow broken, try to renew it
from scratch, not mixing both grub-pc (grub2) and grub-legacy. Or
maybe you have typos somewhere in the variables so that they are not
picked up by update-grub (you can also call grub-mkconfig -o
/boot/grub/grub.cfg for grub-pc).
No need to Cc me, I am all eyes on the list.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
console resolution
Hi, I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. Thanks. Nima :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote: Hi, I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. For the new grub, edit the file /etc/default/grub, add the following line: GRUB_CMDLINE_LINUX=vga=xxx And then run 'update-grub' to update /boot/grub/grub.cfg Jeffrey -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
Hi, On Fri, Jan 22, 2010 at 1:08 PM, Nima Azarbayjany i.adore.deb...@gmail.comwrote: Hi, I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. Seem like gfxpayload is the substitute, but now I can't find where is the doc (it doesn't appear in kernel-parameters.txt). Regards,
Re: console resolution
Nima Azarbayjany wrote at 2010-01-22 06:08 -0600: I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. I removed 'vga=' and now I get a full 1400x1050 on a T61 (using linux-source-2.6.32). Excellent! signature.asc Description: Digital signature
Re: console resolution
On 2010-01-22 at 08:26:27 -0500, Jeffrey Cao wrote: On 2010-01-22, Nima Azarbayjany i.adore.deb...@gmail.com wrote: Hi, I have recently installed Squeeze on my laptop and most things seem to work fine right now. I used to add vga=xxx to the kernel parameters line to adjust the console resolution but this is now deprecated as a message printed at the startup says. What should be passed to the kernel instead of, for example, vga=0x361? Let me add that I have upgraded the kernel to 2.6.32 from sid. For the new grub, edit the file /etc/default/grub, add the following line: GRUB_CMDLINE_LINUX=vga=xxx And then run 'update-grub' to update /boot/grub/grub.cfg Thanks, Jeffrey. I routinely use the vga option too, and I couldn't get it to work with grub2 either. To avoid confusion between grub2 and grub1, I decided to go back to lilo. The next time I do a Squeeze install from scratch, I'll your suggestion a try. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On 2010-01-22 at 09:00:54 -0500, Javier Barroso wrote: Seem like gfxpayload is the substitute, but now I can't find where is the doc (it doesn't appear in kernel-parameters.txt). The vga kernel option is a strange option. It's really more of a bootloader option than a kernel option. The bootloader itself has to have support for it. The actual change of video mode is done by means of a video BIOS call. This is an old-fashioned DOS-style interrupt call, which must be done in real mode. I believe the bootloader itself makes the call, while it is still running in real mode. The bootloader switches to protected mode prior to passing control to the kernel. Somehow, the kernel is told what the video mode is, so that it can allocate the proper amount of memory for a virtual terminal buffer, but I don't believe that the kernel itself actually makes the video BIOS call. That's the way it worked under lilo and grub1 anyway. This is for text-mode virtual consoles. I'm really going out on a limb when I talk about grub2, since I only used it for a very short time, but I seem to remember that gfxpayload sets the video mode for grub itself. I don't think it applies to the kernel proper. The doc for grub2, such as it is, is at http://www.gnu.org/software/grub/grub-2.en.html. I gave up on grub2 rather quickly and went back to lilo when I couldn't get the vga option to work; so I know very little about it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Fri, Jan 22, 2010 at 10:03 AM, Stephen Powell zlinux...@wowway.comwrote: On 2010-01-22 at 09:00:54 -0500, Javier Barroso wrote: Seem like gfxpayload is the substitute, but now I can't find where is the doc (it doesn't appear in kernel-parameters.txt). I'm really going out on a limb when I talk about grub2, since I only used it for a very short time, but I seem to remember that gfxpayload sets the video mode for grub itself. I don't think it applies to the kernel proper. The doc for grub2, such as it is, is at http://www.gnu.org/software/grub/grub-2.en.html. I gave up on grub2 rather quickly and went back to lilo when I couldn't get the vga option to work; so I know very little about it. set gfxpayload=keep will tell Grub2 to hand off the graphics settings to the kernel, which if configured properly will carry them forward. There are some other settings to tweak as well, insmod vbe and whatnot in the appropriate file, but that's about the gist of it. The nice thing is it makes for very smooth transitions when switching from terminal to x, as the display settings (if correctly configured) are already applied, thus, no ugly flashing of the screen and delay. Best, Arthur
Re: console resolution
On 2010-01-22 at 12:08:56 -0500, Arthur Machlas wrote: set gfxpayload=keep will tell Grub2 to hand off the graphics settings to the kernel, which if configured properly will carry them forward. There are some other settings to tweak as well, insmod vbe and whatnot in the appropriate file, but that's about the gist of it. The nice thing is it makes for very smooth transitions when switching from terminal to x, as the display settings (if correctly configured) are already applied, thus, no ugly flashing of the screen and delay. So then this is designed to work with framebuffer graphics mode virtual consoles, right? That wouldn't help me. I prefer the traditional hardware text mode virtual consoles. That's why I use the vga option and lilo. I've even configured lilo to do all of its own output in text mode. Jeffrey Cao wrote in another post that grub2 can support the traditional vga kernel option by means of editing /etc/default/grub and adding the line GRUB_CMDLINE_LINUX=vga=xxx and then running update-grub to update /boot/grub/grub.cfg. But I haven't tried it myself. I'm not going to de-install lilo and install grub2 to find out. But next time I try a Squeeze install from scratch, I might give it a try. For now, I'm very happy with my old friend lilo. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Fri, 2010-01-22 at 13:08 -0500, Stephen Powell wrote: snip Jeffrey Cao wrote in another post that grub2 can support the traditional vga kernel option by means of editing /etc/default/grub and adding the line GRUB_CMDLINE_LINUX=vga=xxx and then running update-grub to update /boot/grub/grub.cfg. But I haven't tried it myself. I'm not going to de-install lilo and install grub2 to find out. snip? I've succesfully used that method to set the screen mode on several Debian Squeeze computers with grub2. That method is currently the only real way, as there is not a clean way to configure gfxpayload yet. (You have to manually patch the Grub scripts, because it hasn't been applied it to the version which Debian ships.) -- Tixy -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Re: console resolution
set gfxpayload=keep will tell Grub2 to hand off the graphics settings to the kernel, which if configured properly will carry them forward. There are some other settings to tweak as well, insmod vbe and whatnot in the appropriate file, but that's about the gist of it. The nice thing is it makes for very smooth transitions when switching from terminal to x, as the display settings (if correctly configured) are already applied, thus, no ugly flashing of the screen and delay. Best, Arthur Would you please explain how and where to insert this into Grub's configuration? I played with /etc/default/grub and update-grub but no success. Jeffrey Cao wrote in another post that grub2 can support the traditional vga kernel option by means of editing /etc/default/grub and adding the line GRUB_CMDLINE_LINUX=vga=xxx and then running update-grub to update /boot/grub/grub.cfg. But I haven't tried it myself. I'm not going to de-install lilo and install grub2 to find out. But next time I try a Squeeze install from scratch, I might give it a try. I tried this one but it too didn't work. It says that vga=xxx is deprecated. Jeffrey Cao wrote in another post that grub2 can support the traditional vga kernel option by means of editing /etc/default/grub and adding the line GRUB_CMDLINE_LINUX=vga=xxx and then running update-grub to update /boot/grub/grub.cfg. But I haven't tried it myself. I'm not going to de-install lilo and install grub2 to find out. But next time I try a Squeeze install from scratch, I might give it a try. This one did not work as well. I guess I'm going to install grub1 for now. Nima -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Fri, Jan 22, 2010 at 01:08:23PM EST, Stephen Powell wrote: [..] So then this is designed to work with framebuffer graphics mode virtual consoles, right? That wouldn't help me. I prefer the traditional hardware text mode virtual consoles. Just curious, but what's wrong with using a framebuffer console? CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On 2010-01-22 at 15:50:02 -0500, Chris Jones wrote: On Fri, Jan 22, 2010 at 01:08:23PM EST, Stephen Powell wrote: So then this is designed to work with framebuffer graphics mode virtual consoles, right? That wouldn't help me. I prefer the traditional hardware text mode virtual consoles. Just curious, but what's wrong with using a framebuffer console? There's nothing wrong with using a framebuffer virtual console, and there's nothing right about using a traditional hardware text mode virtual console. It's a matter of preference. I prefer a hardware text mode virtual console for a number of reasons, but one of them is that it performs better, particularly on the ancient under-powered hardware that I tend to use! For example, screen scrolling is quite snappy on a text mode virtual console, but on a framebuffer virtual console it can be sluggish, depending on processor speed. Besides, if I am editing text, doesn't it make sense to use text mode? Isn't that what text mode was created to do? I'm not against GUI interfaces, per se. They have their uses. And I do use them. But if I'm going to be doing some serious text editing, I always switch to a text mode virtual console and do my editing there. I don't try to convert others to my way of thinking. If they want to use a GUI interface for everything, that's fine with me. But I do resent it when the movers and shakers try to eliminate every last vestige of text mode from the system. Text mode is simply the fastest and most efficient way to edit and peruse text. Surprise, surprise! In fact, I support quite a number of machines that don't even have X installed. Why use a frame buffer virtual console under those conditions? All it does is consume resources and slow things down. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Fri, Jan 22, 2010 at 04:47:29PM EST, Stephen Powell wrote: I prefer a hardware text mode virtual console for a number of reasons, but one of them is that it performs better, particularly on the ancient under-powered hardware that I tend to use! PIII 650MHz - 386M of RAM - ATI Rage Mobility (Mach64). For example, screen scrolling is quite snappy on a text mode virtual console, but on a framebuffer virtual console it can be sluggish, depending on processor speed. I don't know if my video card takes care of that, but I find that moving the cursor, scrolling, etc. is noticeably faster on a framebuffer console than on the vga console. Mind you, since the vesa driver does not support my display's native 1400x1050, I use the atyfb driver. So I'm not sure how it would handle if I used the vga=xxx modes. [..] All it does is consume resources and slow things down. Everything has a price, keeping in mind that it might use fewer CPU cycles if the video card is put to good use. Thank you for your comments, CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: console resolution
On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote: On Fri, Jan 22, 2010 at 04:47:29PM EST, Stephen Powell wrote: [snip] I don't know if my video card takes care of that, but I find that moving the cursor, scrolling, etc. is noticeably faster on a framebuffer console than on the vga console. Mind you, since the vesa driver does not support my display's native 1400x1050, I use the atyfb driver. So I'm not sure how it would handle if I used the vga=xxx modes. do you know if there is still a limitation of using the nvidia framebuffer and the nvidia binary driver ? [..] All it does is consume resources and slow things down. Everything has a price, keeping in mind that it might use fewer CPU cycles if the video card is put to good use. Thank you for your comments, CJ -- You will be the victim of a bizarre joke. signature.asc Description: Digital signature
Re: console resolution
On Fri, Jan 22, 2010 at 09:39:50PM EST, Alex Samad wrote: On Fri, Jan 22, 2010 at 06:11:38PM -0500, Chris Jones wrote: [..] I don't know if my video card takes care of that, but I find that moving the cursor, scrolling, etc. is noticeably faster on a framebuffer console than on the vga console. Mind you, since the vesa driver does not support my display's native 1400x1050, I use the atyfb driver. So I'm not sure how it would handle if I used the vga=xxx modes. do you know if there is still a limitation of using the nvidia framebuffer and the nvidia binary driver ? [..] -- You will be the victim of a bizarre joke. :-) I the above question the bizarre joke, or was this meant as a reply to a different post? CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
changing console resolution?
well, since i've completely failed to get x working beyond a messed up 640x480 res that flickers and uses really wacky colors on this machine... is there a way to change the console resolution to somthing a little higher? or someone who has a thinpad 365XD w/ an active matrix screen could respond, and say that it works perfectly for them... here's how ;) right..
Re: changing console resolution?
On Sat, Jan 20, 2001 at 12:55:30AM -0800, forrest wrote: well, since i've completely failed to get x working beyond a messed up 640x480 res that flickers and uses really wacky colors on this machine... is there a way to change the console resolution to somthing a little higher? or someone who has a thinpad 365XD w/ an active matrix screen could respond, and say that it works perfectly for them... here's how ;) right.. Maybe there is an easier way but you can stick - vga = ask into your /etc/lilo.conf Reboot and you will be asked to make a choice. It may take a few reboots (that is the part I don't like). Then once you have decided which number your going with you would put - vga = number in /etc/lilo.conf Remember to run /sbin/lilo. hth, kent -- I'd really love ta wana help ya Flanders but... Homer Simpson
Re: changing console resolution?
On Sat, Jan 20, 2001 at 12:55:30AM -0800, forrest wrote: :well, since i've completely failed to get x working beyond a messed up :640x480 res that flickers and uses really wacky colors on this :machine... is there a way to change the console resolution to somthing a :little higher? : :or someone who has a thinpad 365XD w/ an active matrix screen could :respond, and say that it works perfectly for them... here's how ;) There's probably some magic number for vga= in /etc/lilo.conf, and (if my viao is any indication) ask probably won't show it as an option... Your best source of info for this and the X problem is the Linux Laptop page http://www.cs.utexas.edu/users/kharker/linux-laptop/ -Jon
Re: changing console resolution?
on Sat, Jan 20, 2001 at 12:55:30AM -0800, forrest ([EMAIL PROTECTED]) wrote: well, since i've completely failed to get x working beyond a messed up 640x480 res that flickers and uses really wacky colors on this machine... is there a way to change the console resolution to somthing a little higher? svga modes may help you, as suggested. Also look at SVGATextMode. There's new stuff in the framebuffer support which accomplishes similar results by different means. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpJnt9HiHG5w.pgp Description: PGP signature
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: 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: 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] .
