Re: virt terminal font problem
On 09/05/2011 06:21 PM, Roger Leigh wrote: On Mon, Sep 05, 2011 at 04:12:31PM -0400, Whit Hansell wrote: Please select the size of the font for the Linux console. Simple │ │ integers corresponding to fonts can be used with all console drivers. │[snip] Some general points: - You need modesettting, so don't disable it. KMS and radeondrmfb are the future, and so it makes no sense to disable, especially when it's a massive improvement on what came before. It will soon (if not already, depending upon the driver), be required to use KMS to run X11 and Wayland. - Font setting works whether you are using a VGA console, framebuffer console or KMS with radeondrmfb. The only differences are limitations in the fontsizes you can load. VGA for example has limited space to store a font, which limits you to IIRC 8×16. OTOH, the framebuffer permits much bigger fonts (I'm using 28×14 for example with KMS and radeondrmfb, and 32×16 also works). [snip] Regards, Roger Roger, Thanks for your help. With your suggestions and guidance I finally got it done. It was confusing but finally got figured out. Using the correct setting in modesetting as you recommended and have a 24 X 16 font size after a bit of fumbling w. iterations of variables. My little mind was goin' somewhat @#$%^^* but got it done w. your most helpful suggestions and guidance. And I learned more about linux too thanks to you. Cheers and regards, Whit -- 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/4e66561b.4050...@comcast.net
Re: virt terminal font problem
On Sun 04 Sep 2011 at 21:17:14 -0400, Whit Hansell wrote: Has anyone any knowledge of manipulating font size in Virt Term in Wheezy? Any help will be appreciated. It is not an imperative as I can and do use the gnome terminal program but it would be nice to be able to use the Virtual Terminal because once in a while. Your first port of call should be 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/20110905080019.GM28063@desktop
Re: virt terminal font problem
[Having to resend this as I originally only sent it to Ivan - this is to the user group] Thanks for the reply Ivan. Shawn mentioned trying dpkg-reconfigure console-setup so I tried that first and got nowhere but it did give me a notice when I set it in certain setups, as in VGA. It came up w. this notice. Please select the size of the font for the Linux console. Simple │ │ integers corresponding to fonts can be used with all console drivers. │ │ The number then represents the font height (number of scan lines). │ │ Alternatively, the font may be represented as HEIGHTxWIDTH; however, │ │ such font specifications require the kbd console package (not │ │ console-tools) plus framebuffer (and the RadeonFB kernel driver for │ │ framebuffer does not support them either). │ │ │ │ Font heights can be useful for figuring out the real size of the symbols │ │ on the console. For reference, the font used when the computer boots has │ │ size 16. So, on the next page I set the font size to 16 and rebooted just for grins and it made no difference. But on your suggestion, I looked at etc/modprobe.d and found. root@greatstar:/etc/modprobe.d# cat radeon-kms.conf options radeon modeset=1 I'm guessing that if I change the options radeon modeset from 1 to 0, then the radeon drivers won't load on reboot. Then the standard framebuffers situation would occur? BTW my video driver is onboard and is an ATI RV610 if that helps at all. Do you think I'm correct in the idea of changing the modeset from 1 to 0 and would I have problems by doing so? Thanks for your help. I know i sound goofy but I did a safe upgrade today in the midst of this mess and a cups file was upgraded and it hosed my printing up. So far I have printed from the web and can get noting but black, not blank, but black pages. G YOu can understand why I'm a bit spooky. G Thanks for your help Ivan. I really appreciate it. Whit On 09/05/2011 01:25 AM, Ivan Shmakov wrote: Whit Hansellskippe...@comcast.net writes: […] I had a problem when I purchased a new monitor, an LCD, and it required me to put vga=785 at the end of the Kernel line in menu.list file in order to get any video out of the Virtual Terminal (F1-6). Now that I have reinstalled w. Wheezy, I have the Virtual Terminal but the font size is extremely tiny. I cannot see it well at all and I have a vision problem to start with. Newer Linux userland VT tools' default is to use video card's graphics mode via a framebuffer console driver, instead of the text mode, which was the older default. My guess is that blacklisting the framebuffer drivers in modprobe.d(5) will allow one to use the text mode as before, but I haven't tried it yet. (I currently have no access to a hardware running Wheezy.) It's also possible to use the Terminus fonts (as of console-terminus, IIRC), e. g.: $ setfont -f /usr/share/consolefonts/Uni3-TerminusBold28x14.psf.gz Depending on the actual screen resolution, a font of up to 32x16 pixel size may be chosen. This problem w. terminal starts after boot when it gets to a certain point, I'm assuming init.d, but not sure. While it's trying to check hardware items it's fine, the standard 80 X 25 large font terminal screen. Then all of a sudden it changes to the small/tiny font … And it's the time the framebuffer drivers get loaded. and just before it brings up the splash screen, it sometimes messes up the whole screen and puts across the top of the screen garbled lines for just a second, then the splash screen pops up and I have no problem logging in. Note also that since newer reboot(8) doesn't go through the BIOS (it only reinitializes the kernel), the screen will be garbled at reboot as well. […] -- 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/4e652d2f.1090...@comcast.net
Re: virt terminal font problem
Thank you Brian . I did the dpkg reconfigure console-setup but none of the various iterations I tried worked. I have replied to Ivan's suggestion asking a question about making a change to a file in modprobe.d. I did find a notice in the reconfugure deal re framebuffers and that the driver I seem to be using is the problem. Again thanks for your suggestion. Much appreciated. Whit On 09/05/2011 04:00 AM, Brian wrote: On Sun 04 Sep 2011 at 21:17:14 -0400, Whit Hansell wrote: as anyone any knowledge of manipulating font size in Virt Term in snip Your first port of call should be 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/4e652f46.3030...@comcast.net
Re:[SOLVED] virt terminal font problem
Ivan and group. I went ahead and tried resetting the radeon modeset] to 0 which is linux for [OFF], and voila' it worked. Shazaam! What do you know. I was afraid I was going to hose it all up but nope, it came up just like it was 'sposed to. Ivan, thank you for your help, so much. I'd gone nuts trying to google the answer to this mess and you directed me to the correct procedure. I've been upgrading wheezy almost every day and it seems like once a week there is a group of messages that I had never received before in Lenny stating that I needed more radeon drivers or firmware or something and I had even hunted to see if I could find them but no joy there either. So hopefully since I'm not loading the radeon driver anymore, at least the radeonFB one I am guessing, maybe I won't get those messages any longer. Again, Ivan thank you. You were a great help. Whit On 09/05/2011 04:12 PM, Whit Hansell wrote: [Having to resend this as I originally only sent it to Ivan - this is to the user group] Thanks for the reply Ivan. Shawn mentioned trying dpkg-reconfigure console-setup so I tried that first and got nowhere but it did give me a notice when I set it in certain setups, as in VGA. It came up w. this notice. Please select the size of the font for the Linux console. Simple │ │ integers corresponding to fonts can be used with all console drivers. │ │ The number then represents the font height (number of scan lines). │ │ Alternatively, the font may be represented as HEIGHTxWIDTH; however, │ │ such font specifications require the kbd console package (not │ │ console-tools) plus framebuffer (and the RadeonFB kernel driver for │ │ framebuffer does not support them either). │ │ │ │ Font heights can be useful for figuring out the real size of the symbols │ │ on the console. For reference, the font used when the computer boots has │ │ size 16. So, on the next page I set the font size to 16 and rebooted just for grins and it made no difference. But on your suggestion, I looked at etc/modprobe.d and found. root@greatstar:/etc/modprobe.d# cat radeon-kms.conf options radeon modeset=1 I'm guessing that if I change the options radeon modeset from 1 to 0, then the radeon drivers won't load on reboot. Then the standard framebuffers situation would occur? BTW my video driver is onboard and is an ATI RV610 if that helps at all. Do you think I'm correct in the idea of changing the modeset from 1 to 0 and would I have problems by doing so? Thanks for your help. I know i sound goofy but I did a safe upgrade today in the midst of this mess and a cups file was upgraded and it hosed my printing up. So far I have printed from the web and can get noting but black, not blank, but black pages. G YOu can understand why I'm a bit spooky. G Thanks for your help Ivan. I really appreciate it. Whit On 09/05/2011 01:25 AM, Ivan Shmakov wrote: Whit Hansellskippe...@comcast.net writes: […] I had a problem when I purchased a new monitor, an LCD, and it required me to put vga=785 at the end of the Kernel line in menu.list file in order to get any video out of the Virtual Terminal (F1-6). Now that I have reinstalled w. Wheezy, I have the Virtual Terminal but the font size is extremely tiny. I cannot see it well at all and I have a vision problem to start with. Newer Linux userland VT tools' default is to use video card's graphics mode via a framebuffer console driver, instead of the text mode, which was the older default. My guess is that blacklisting the framebuffer drivers in modprobe.d(5) will allow one to use the text mode as before, but I haven't tried it yet. (I currently have no access to a hardware running Wheezy.) It's also possible to use the Terminus fonts (as of console-terminus, IIRC), e. g.: $ setfont -f /usr/share/consolefonts/Uni3-TerminusBold28x14.psf.gz Depending on the actual screen resolution, a font of up to 32x16 pixel size may be chosen. This problem w. terminal starts after boot when it gets to a certain point, I'm assuming init.d, but not sure. While it's trying to check hardware items it's fine, the standard 80 X 25 large font terminal screen. Then all of a sudden it changes to the small/tiny font … And it's the time the framebuffer drivers get loaded. and just before it brings up the splash screen, it sometimes messes up the whole screen and puts across the top of the screen garbled lines for just a second, then the splash screen pops up and I have no problem logging in. Note also that since newer reboot(8) doesn't go through the BIOS (it only reinitializes the kernel), the screen will be garbled at reboot as well. […] -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive:
Re: virt terminal font problem
On Mon, Sep 05, 2011 at 04:12:31PM -0400, Whit Hansell wrote: Please select the size of the font for the Linux console. Simple │ │ integers corresponding to fonts can be used with all console drivers. │ │ The number then represents the font height (number of scan lines). │ │ Alternatively, the font may be represented as HEIGHTxWIDTH; however, │ │ such font specifications require the kbd console package (not │ │ console-tools) plus framebuffer (and the RadeonFB kernel driver for │ │ framebuffer does not support them either). │ │ │ │ Font heights can be useful for figuring out the real size of the symbols │ │ on the console. For reference, the font used when the computer boots has │ │ size 16. So, on the next page I set the font size to 16 and rebooted just for grins and it made no difference. But on your suggestion, I looked at etc/modprobe.d and found. root@greatstar:/etc/modprobe.d# cat radeon-kms.conf options radeon modeset=1 I'm guessing that if I change the options radeon modeset from 1 to 0, then the radeon drivers won't load on reboot. Then the standard framebuffers situation would occur? BTW my video driver is onboard and is an ATI RV610 if that helps at all. Do you think I'm correct in the idea of changing the modeset from 1 to 0 and would I have problems by doing so? Thanks for your help. I know i sound goofy but I did a safe upgrade today in the midst of this mess and a cups file was upgraded and it hosed my printing up. So far I have printed from the web and can get noting but black, not blank, but black pages. G YOu can understand why I'm a bit spooky. G Some general points: - You need modesettting, so don't disable it. KMS and radeondrmfb are the future, and so it makes no sense to disable, especially when it's a massive improvement on what came before. It will soon (if not already, depending upon the driver), be required to use KMS to run X11 and Wayland. - Font setting works whether you are using a VGA console, framebuffer console or KMS with radeondrmfb. The only differences are limitations in the fontsizes you can load. VGA for example has limited space to store a font, which limits you to IIRC 8×16. OTOH, the framebuffer permits much bigger fonts (I'm using 28×14 for example with KMS and radeondrmfb, and 32×16 also works). - No need to reboot; just all /etc/init.d/console-setup start after editing /etc/default/console-setup, to see if it works. - Run setfont by hand to test font loading. That's all the above is doing. This tells you if the console is capable of loading the specific font. Example: setfont /usr/share/consolefonts/Uni2-TerminusBold20x10.psf.gz Try it with all the font files for e.g. Uni2-TerminusBold and see if there's a size limit. If there is, make sure that you're using an appropriately-configured console, e.g. these are mine: % dmesg | grep drmfb [9.046243] fbcon: radeondrmfb (fb0) is primary device [9.485097] fb0: radeondrmfb frame buffer device % fbset -i mode 1920x1200 geometry 1920 1200 1920 1200 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode Frame buffer device information: Name: radeondrmfb Address : 0xd0142000 Size: 9216000 Type: PACKED PIXELS Visual : TRUECOLOR XPanStep: 1 YPanStep: 1 YWrapStep : 0 LineLength : 7680 Accelerator : No Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Re: [SOLVED]virt terminal font problem
And thank you too Brain. You helped too as going to reconfigure gave me the info about the radeonFB problem I had mentioned in the mail to Ivan. Great help. And I will look more often to the reconfigure situation as a possible cure for problems in the future more often. I'd used it before on various things and it helped but since Wheezy is so new in so many ways, I felt there had to be another answer. And actually had not even thought about it. Thanks again. Your aid is very much appreciated. whit On 09/05/2011 04:21 PM, Whit Hansell wrote: Thank you Brian . I did the dpkg reconfigure console-setup but none of the various iterations I tried worked. I have replied to Ivan's suggestion asking a question about making a change to a file in modprobe.d. I did find a notice in the reconfugure deal re framebuffers and that the driver I seem to be using is the problem. Again thanks for your suggestion. Much appreciated. Whit On 09/05/2011 04:00 AM, Brian wrote: On Sun 04 Sep 2011 at 21:17:14 -0400, Whit Hansell wrote: as anyone any knowledge of manipulating font size in Virt Term in snip Your first port of call should be 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/4e654b7e.4060...@comcast.net
Re: [SOLVED] virt terminal font problem
[Please don't top-post. Thanks.] On Mon, Sep 05, 2011 at 06:17:57PM -0400, Whit Hansell wrote: Ivan and group. I went ahead and tried resetting the radeon modeset] to 0 which is linux for [OFF], and voila' it worked. Shazaam! What do you know. I was afraid I was going to hose it all up but nope, it came up just like it was 'sposed to. Ivan, thank you for your help, so much. I'd gone nuts trying to google the answer to this mess and you directed me to the correct procedure. I've been upgrading wheezy almost every day and it seems like once a week there is a group of messages that I had never received before in Lenny stating that I needed more radeon drivers or firmware or something and I had even hunted to see if I could find them but no joy there either. So hopefully since I'm not loading the radeon driver anymore, at least the radeonFB one I am guessing, maybe I won't get those messages any longer. Have you got firmware-linux installed and updated your initramfs? % dpkg --get-selections | grep firmware-linux firmware-linux install firmware-linux-free install firmware-linux-nonfree install Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Re: virt terminal font problem
On 09/05/2011 06:24 PM, Roger Leigh wrote: [Please don't top-post. Thanks.] On Mon, Sep 05, 2011 at 06:17:57PM -0400, Whit Hansell wrote: Ivan and group. I went ahead and tried resetting the radeon modeset] to 0 which is linux for [OFF], and voila' it worked. Shazaam! What do you know. I was afraid I was going to hose it all up but nope, it came up just like it was 'sposed to. Ivan, thank you for your help, so much. I'd gone nuts trying to google the answer to this mess and you directed me to the correct procedure. I've been upgrading wheezy almost every day and it seems like once a week there is a group of messages that I had never received before in Lenny stating that I needed more radeon drivers or firmware or something and I had even hunted to see if I could find them but no joy there either. So hopefully since I'm not loading the radeon driver anymore, at least the radeonFB one I am guessing, maybe I won't get those messages any longer. Have you got firmware-linux installed and updated your initramfs? % dpkg --get-selections | grep firmware-linux firmware-linux install firmware-linux-free install firmware-linux-nonfree install Regards, Roger Thanks, I do now. I previously had only the firmware-linux-free... Cheers. Whit -- 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/4e65639f.70...@comcast.net
virt terminal font problem
Maybe someone can help me here. I've googled all over and cannot find an answer to my problem. I had been running Lenny before Squeeze went stable, then installed Wheezy testing because I wanted to get back to running testing again instead of stable. I've been running Debian Linux since 2002, and since approx 2004, been running testing until Lenny became stable. I had heard that there were going to be a bunch of changes in Squeeze/testing and did not want to take a chance of having a Problem w. the new testing so stayed w. Lenny when it went stable. I had a problem when I purchased a new monitor, an LCD, and it required me to put vga=785 at the end of the Kernel line in menu.list file in order to get any video out of the Virtual Terminal (F1-6). Now that I have reinstalled w. Wheezy, I have the Virtual Terminal but the font size is extremely tiny. I cannot see it well at all and I have a vision problem to start with. This problem w. terminal starts after boot when it gets to a certain point, I'm assuming init.d, but not sure. While it's trying to check hardware items it's fine, the standard 80 X 25 large font terminal screen. Then all of a sudden it changes to the small/tiny font and just before it brings up the splash screen, it sometimes messes up the whole screen and puts across the top of the screen garbled lines for just a second, then the splash screen pops up and I have no problem logging in. That is no real problem because it still boots fine and I have dmesg if I need it using the gnome terminal program. But I do like to use the Virtual Terminal (F1-6) and when I go into any of them, I end up w. the tiny font. There is no menu.list anymore. Wheezy has changed the boot setup. It is so different and Wheezy is so new that I can't find anyone else who is having the same problem who has figured out how to correct the problem. I would try to send this in as a bug but I don't really think it's a bug. I think it's an anomoly, or if it is a bug it sure is not important enough to cause a stir at a bug fest. Has anyone any knowledge of manipulating font size in Virt Term in Wheezy? Any help will be appreciated. It is not an imperative as I can and do use the gnome terminal program but it would be nice to be able to use the Virtual Terminal because once in a while. Thanks in advance and cheers. Whit -- 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/4e64231a.7000...@comcast.net
Re: virt terminal font problem
Whit Hansell skippe...@comcast.net writes: […] I had a problem when I purchased a new monitor, an LCD, and it required me to put vga=785 at the end of the Kernel line in menu.list file in order to get any video out of the Virtual Terminal (F1-6). Now that I have reinstalled w. Wheezy, I have the Virtual Terminal but the font size is extremely tiny. I cannot see it well at all and I have a vision problem to start with. Newer Linux userland VT tools' default is to use video card's graphics mode via a framebuffer console driver, instead of the text mode, which was the older default. My guess is that blacklisting the framebuffer drivers in modprobe.d(5) will allow one to use the text mode as before, but I haven't tried it yet. (I currently have no access to a hardware running Wheezy.) It's also possible to use the Terminus fonts (as of console-terminus, IIRC), e. g.: $ setfont -f /usr/share/consolefonts/Uni3-TerminusBold28x14.psf.gz Depending on the actual screen resolution, a font of up to 32x16 pixel size may be chosen. This problem w. terminal starts after boot when it gets to a certain point, I'm assuming init.d, but not sure. While it's trying to check hardware items it's fine, the standard 80 X 25 large font terminal screen. Then all of a sudden it changes to the small/tiny font … And it's the time the framebuffer drivers get loaded. and just before it brings up the splash screen, it sometimes messes up the whole screen and puts across the top of the screen garbled lines for just a second, then the splash screen pops up and I have no problem logging in. Note also that since newer reboot(8) doesn't go through the BIOS (it only reinitializes the kernel), the screen will be garbled at reboot as well. […] -- FSF associate member #7257 Coming soon: Software Freedom Day http://mail.sf-day.org/lists/listinfo/ planning-ru (ru), sfd-discuss (en) -- 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/86wrdn7e7c@gray.siamics.net
