[arch-general] successful pacman -Syu w/new kernal26: Now have microscopic console font :-(
Sigh... I just did a pacman -Syu. It updated lots of stuff. The only issues listed in my pacman.log were: While: updating keystore /etc/ssl/certs/java/cacerts... ignored import, signature not available: /etc/ssl/certs/COMODO_Certification_Authority.pem keytool error: java.security.NoSuchAlgorithmException: SHA384withECDSA Signature not available And a warning about my manually managed separate primary boot partition not being mounted... Which will never be mounted during *_any_* Linux distro's upgrade process... I compared /boot and /mnt/boot grub entries, verified that the vmlinuz and kernel.img filenames hadn't changed, Then copied the vmlinuz, and both kernal.img files from /boot, to /mnt/boot And rebooted... As far as I can see (so far) the only real issue I have with my upgraded Arch system is that the size of my console fonts has drastically been reduced... Once the gui started, all the X font sizes were just fine. But my eyes hurt just trying to read the console well enough to login to run startx... The next thing I did was to edit MY grub's kernel line to include: vga=normal, and rebooted. But partway through the boot messages the screen still clears and the font size becomes painfully small. Next, Even though I've never had to bother with framebuffer before (I prefer the normal sized console font, and I don't like pretty pictures on my screen until AFTER I run startx...) I read the "FRAMEBUFFER RESOLUTION SETTINGS" comments in the /boot/grub/menu.lst file. And that led me to the framebuffer section of the grub wiki file. Which in turn led to my installing hwinfo from aur on this amd_64 laptop. 02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.mrzO17IxmKC Hardware Class: framebuffer Model: "ATI MS48" Vendor: "ATI Technologies Inc." Device: "MS48" SubVendor: "ATI Radeon® Xpress 1150" SubDevice: Revision: "01.00" Memory Size: 16 MB Memory Range: 0xc8000000-0xc8ffffff (rw) <snip> Mode 0x0312: 640x480 (+1920), 24 bits <snip> the comments in the menu.lst file say on the 16MB line "0x312=786" So I tried vga=786 And rebooted... Just before the boot messages list ":: Bringing up loopback interface" the screen still clears {expletive-deleted!} And then the fontsize still makes me squint. {many expletives-deleted!} Problem #1 How can I stop the reduction in the console font size??? Evidently the framebuffer setting isn't doing it... Problem #2 How can I stop the boot process from clearing the screen on tty1??? I really dislike ANY of the boot messages to disappear. I "LIKE" being able to use gpm to copy/paste them into a console editor... I didn't like it when it cleared the last few lines just prior to giving me a login prompt. But at least that could be compensated for by the kludge of including a multi-line echo statement in /etc/rc.local. But now that it lops the majority of the boot messages off the top it's beyond my ability to kludgon it into submission. ;-( Suggestions anyone? -- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>> I'm NOT clueless... But I just don't know.
On Sat, 10 Apr 2010 18:00:53 +0200, Joe(theWordy)Philbrook <jtwdyp@ttlc.net> wrote:
Sigh...
I just did a pacman -Syu. It updated lots of stuff. The only issues listed in my pacman.log were: While: updating keystore /etc/ssl/certs/java/cacerts... ignored import, signature not available: /etc/ssl/certs/COMODO_Certification_Authority.pem keytool error: java.security.NoSuchAlgorithmException: SHA384withECDSA Signature not available
And a warning about my manually managed separate primary boot partition not being mounted... Which will never be mounted during *_any_* Linux distro's upgrade process...
I compared /boot and /mnt/boot grub entries, verified that the vmlinuz and kernel.img filenames hadn't changed, Then copied the vmlinuz, and both kernal.img files from /boot, to /mnt/boot And rebooted...
As far as I can see (so far) the only real issue I have with my upgraded Arch system is that the size of my console fonts has drastically been reduced...
Once the gui started, all the X font sizes were just fine. But my eyes hurt just trying to read the console well enough to login to run startx...
The next thing I did was to edit MY grub's kernel line to include: vga=normal, and rebooted. But partway through the boot messages the screen still clears and the font size becomes painfully small.
Next, Even though I've never had to bother with framebuffer before (I prefer the normal sized console font, and I don't like pretty pictures on my screen until AFTER I run startx...) I read the "FRAMEBUFFER RESOLUTION SETTINGS" comments in the /boot/grub/menu.lst file. And that led me to the framebuffer section of the grub wiki file. Which in turn led to my installing hwinfo from aur on this amd_64 laptop.
02: None 00.0: 11001 VESA Framebuffer [Created at bios.459] Unique ID: rdCR.mrzO17IxmKC Hardware Class: framebuffer Model: "ATI MS48" Vendor: "ATI Technologies Inc." Device: "MS48" SubVendor: "ATI Radeon® Xpress 1150" SubDevice: Revision: "01.00" Memory Size: 16 MB Memory Range: 0xc8000000-0xc8ffffff (rw) <snip> Mode 0x0312: 640x480 (+1920), 24 bits <snip> the comments in the menu.lst file say on the 16MB line "0x312=786" So I tried vga=786 And rebooted... Just before the boot messages list ":: Bringing up loopback interface" the screen still clears {expletive-deleted!} And then the fontsize still makes me squint. {many expletives-deleted!}
Problem #1
How can I stop the reduction in the console font size???
Evidently the framebuffer setting isn't doing it...
Problem #2
How can I stop the boot process from clearing the screen on tty1???
I really dislike ANY of the boot messages to disappear. I "LIKE" being able to use gpm to copy/paste them into a console editor... I didn't like it when it cleared the last few lines just prior to giving me a login prompt. But at least that could be compensated for by the kludge of including a multi-line echo statement in /etc/rc.local. But now that it lops the majority of the boot messages off the top it's beyond my ability to kludgon it into submission. ;-(
Suggestions anyone?
For #1: For the resolution, you probably have some high resolution screen and KMS is now enabled by default. So check here: http://wiki.archlinux.org/index.php/KMS For #2: Just edit /et/inittab and comment out the rule with tty1 -- Jeroen Op 't Eynde jeroen@xprsyrslf.be http://xprsyrslf.be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? More: http://en.wikipedia.org/wiki/Posting_style#Bottom-posting
It would appear that on Apr 10, Jeroen Op 't Eynde did say:
On Sat, 10 Apr 2010 18:00:53 +0200, Joe(theWordy)Philbrook <jtwdyp@ttlc.net> wrote:
Sigh...
Problem #1
How can I stop the reduction in the console font size???
Evidently the framebuffer setting isn't doing it...
Problem #2
How can I stop the boot process from clearing the screen on tty1???
For #1: For the resolution, you probably have some high resolution screen and KMS is now enabled by default. So check here: http://wiki.archlinux.org/index.php/KMS
That does appear to be the issue. For me the quick fix was to disable KMS from grub by adding "radeon.modeset=0" to the kernel options...
For #2: Just edit /et/inittab and comment out the rule with tty1
Yup, that works... I can deal with only having 5 ttys available. AND with having to explicitly choose one before I login. Thanks! -- | --- ___ | <0> <-> Joe (theWordy) Philbrook | ^ J(tWdy)P | ~\___/~ <<jtwdyp@ttlc.net>>
It would appear that on Apr 10, I, Joe(theWordy)Philbrook did utter:
It would appear that on Apr 10, Jeroen Op 't Eynde did say:
For #1: For the resolution, you probably have some high resolution screen and KMS is now enabled by default. So check here: http://wiki.archlinux.org/index.php/KMS
That does appear to be the issue. For me the quick fix was to disable KMS from grub by adding "radeon.modeset=0" to the kernel options...
Well, like I said, that's the quick fix. But: I've done some more reading in http://wiki.archlinux.org/index.php/KMS and related links. And it would seem that KMS is going to become more & more prevalent. It could well be that as the hardware that supports it also becomes more prevalent, support for the "slow","painful", process of passing control of the video card back and forth between the X server and the kernel will become a lower priority, gradually leading to an intolerable level of "flickering" etc... So I'm suspicious that sooner or later I'm going to have to embrace KMS. Accordingly I've done a bit of experimenting. ;-) I found that there was a mechanism in Arch to set a different console font in the rc.conf. It's supposedly only needed for "non-US" {fonts? I presume} But as little as I know about console fonts, I guessed from the filename that "sun12x22.psfu.gz" would just be a larger US font. And as far as I can tell, that is in fact what it is. However, if I let the kernel enable KMS, the sun12x22.psfu.gz font is only just barely tolerable. (It "looks" like than expletive-deleted 10pt font size that most educators seem to favor. I'd love to find something that "looks" more like the 12pt fonts I can read without eyestrain.) Are there other compatible large US fonts that I could perhaps download from someplace????
For #2: Just edit /et/inittab and comment out the rule with tty1
Yup, that works... I can deal with only having 5 ttys available. AND with having to explicitly choose one before I login.
Well it turns out that only works for the last step. Which my rc.local echo statement kludge can compensate for without giving up tty1 as a viable console. If I let KMS happen, everything that printed to the screen before the kernel enabled it is gone. And if I set a larger console font, it clears the screen again when it enters runlevel 3... <sigh> I guess that if/when I choose to use KMS with a large console font, I'm going to have to settle for dmesg... I could even put a call to dmesg in rc.local. But it wouldn't be the same as watching the screen to see if any [failed] indicators scroll by. So whether or not I disable KMS, I'm uncommenting that tty rule and reinstating my echo statement. That, will at least let me keep an eye on my rc.local initializations. {Even with KMS & larger fonts enabled...} -- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>> I'm NOT clueless... But I just don't know.
participants (2)
-
Jeroen Op 't Eynde
-
Joe(theWordy)Philbrook