[Bug 436535] Re: Live CD changes hardware clock
This bug was not present in Ubuntu 8.10 or 9.04. In the Ubuntu 8.10 LiveCD there are no K*hwclock* links in the /etc/rc?.d/ directories, which is correct, so /etc/init.d/hwclock.sh doesn't get called with stop, and the hardware clock is not changed. When Ubuntu 8.10 is installed, K25hwclock.sh, a link to /etc/init.d/hwclock.sh is placed in /etc/rc0.d/ and /etc/rc6.d/ so that /etc/init.d/hwclock.sh gets executed with stop, and the hardware clock is updated, when the PC is halted or rebooted. This is OK since there is, of course, no promise of not changing the computer. That difference between the installed flavor and the LiveCD flavor is a result of this correct 2005 change to casper-0.10: From debian/changelog in casper-1.228: casper (0.10) hoary; urgency=low * Remove rc?.d/K??hwclock.sh links, to avoid changing the system clock during reboot or shutdown -- Matt Zimmerman m...@debian.org Thu, 13 Jan 2005 18:13:31 -0800 From scripts/casper-bottom/25configure_init in casper-1.228: # Avoid clobbering the user's clock rm -f /root/etc/rc?.d/K??hwclock.sh As can be seen from the above, this code still exists in casper-1.228. The problem is that this code affects the System V initialization scripts, which have been replaced by upstart. What casper now needs is equivalent code that works for upstart. When halting or rebooting, upstart runs the script in /etc/init/hwclock- save.conf. So the simplest fix would seem to be to have casper remove that file. It looks like no other script currently depends upon the hwclock-save job, so this should be safe to do. If I boot up my 9.10 LiveCD and remove /etc/init/hwclock-save.conf before halting or rebooting, life is good: the hardware clock is left unchanged. With a new LiveCD being released next month, it would be great if this could be fixed soon. The Try Ubuntu without any changes to your computer promise gives potential Ubuntu users a great sense of freedom to try it. Try it out? No changes? OK, sure, what have I got to loose? That's how I got hooked on Ubuntu. But when those potential users find that their clocks have been clobbered, and the promise broken, they naturally wonder what other changes have been made to their computers. They can easily reset their clocks, but their trust in Ubuntu will not be restored so easily. Few, if any, of those potential users will take the time to find their way to Launchpad and file a bug report. They won't be counted in the Launchpad This bug affects N people tally. Many will simply toss the CD. I did not toss mine, but I had already developed a liking for Ubuntu from previous releases. I did, however, put my 9.10 CD on the shelf, went back to 8.10, and went looking for another disto. Yesterday was the six-month birthday for this bug report. Is it time to raise the Importance from Undecided? It would be a good birthday present. -- Live CD changes hardware clock https://bugs.launchpad.net/bugs/436535 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 385964] Re: VGA console supports multiple fonts but not multiple unimaps.
Hi Jeremy, It is good to see some action on this bug. You didn't mention what your results were when you tried to reproduce the problem (using the steps given in my original report). What were your results in 8.10 and in the latest development release. Norm -- VGA console supports multiple fonts but not multiple unimaps. https://bugs.launchpad.net/bugs/385964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 410335] Re: keyboard setting does not survive reboot
Rolf, If you are currently still having this problem, could you report the results of: ls -l /initrd.img uname -r If the versions don't match, you may be having the same problem that I am. (See LP:439776.) -- keyboard setting does not survive reboot https://bugs.launchpad.net/bugs/410335 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 439776] [NEW] Executing dpkg-reconfigure console-setup does not always update the correct initrd.img file
Public bug reported: Binary package hint: console-setup Ubuntu 8.10 console-setup, Version: 1.25ubuntu4 If you have multiple kernels installed, executing dpkg-reconfigure console-setup will update the /boot/initrd.img-* file that is linked to by /initrd.img. That link normally points to the /boot/initrd.img-* file used with the kernel which was most recently installed. So, if you happen to be using another kernel, the wrong file is updated. If that happens, the changes will be made to the console, as expected, but the next time the user reboots with that kernel, the console will revert to its previous state. Adding to the confusion is the fact that executing dpkg-reconfigure console-setup again will provide default answers matching those supplied before, and accepting those defaults will again make changes to the console, as expected. But the console will again revert to its previous state on the next reboot to that kernel. To reproduce: 1. If you have only one kernel installed, install another kernel package (not just a different version of your current package). 2. Note that the soft link at /initrd.img points to the the /boot/initrd.img-* file corresponding to the most recently installed kernel. 3. If you are using the most recently installed kernel, reboot and select another from the grub menu. 4. Run sudo dpkg-reconfigure console-setup and change the font and/or the font size. 5. Note that the font changes as expected. 6. Reboot and select the same kernel you just used. Actual results: the font has reverted to its old state. Expected results: the font is as configured in step 4. The seems to be in /var/lib/dpkg/info/console-setup.postinst. Near the bottom of that script is this line: update-initramfs -u When given the -u option, update-initramfs always prefers the file linked to by /initrd.img, if it exists. Perhaps that one line could be replaced by the following three lines (which were borrowed from update-initramfs itself, and modified appropriately): if [ -f /boot/initrd.img-`uname -r` ]; then update-initramfs -u -k `uname -r` fi This works for me, although I've not done any extensive testing. (This bug may be a duplicate of LP:345145 and/or LP:410335, but it is not clear if those bugs have the same root cause as this one.) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- Executing dpkg-reconfigure console-setup does not always update the correct initrd.img file https://bugs.launchpad.net/bugs/439776 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392959] Re: Ubuntu boot screen causes virtual terminal display problems.
Thanks for the results from the script. Agreed, usplash needs to be fixed to properly resolve this bug. It was helpful for me to know if the script left things in a working state or not, which is why I asked if it temporarily fixed the problem. Looking at the results, I see that nine of the sixteen palette registers point to the wrong color registers (mostly the ones for the brighter colors). This is not surprising since usplash doesn't restore the palette registers, which is the cause of bug 395374. Normally this would not cause the behavior that you see because the color registers that are incorrectly pointed to usually contain the same color values as the ones that are supposed to be pointed to. In your case, though, the values are different. (Possibly some color values were changed by your X Window driver, which would explain why you don't have the problem when the GDM daemon is not started.) If the unrestored palette registers are the only problem, then when bug 395374 gets fixed this bug will also be fixed. It is also possible that one or more extended registers of the Radeon may need to be restored by usplash. If that is the case, additional work will need to be done to fix this bug. Since it looks like this bug won't go away until bug 395374 is fixed, probably the best thing we can do now is wait for that bug to be fixed and see if that takes care of this bug too. If it doesn't, we (and/or others) can look into this further. -- Ubuntu boot screen causes virtual terminal display problems. https://bugs.launchpad.net/bugs/392959 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392959] Re: Ubuntu boot screen causes virtual terminal display problems.
Thanks for the detailed response, and taking the time to make the tests. It does make things more clear. Thanks also for the added info that the reset command will fix the problem after loading the Uni1 font. I do wish I had a Mobility Radeon X300 here to test with; it would make things a lot easier. I have been hunting through the source code but have not yet found what would cause the exact behavior you describe. Usplash modifies a number of VGA registers and neglects to restore them. That has caused other bugs, and may be causing this one. But I need to see what registers are wrong before I know for sure. If you have not run out of patience, could you try something else? I have attached a small shell script that will run the various commands, grab the state of the VGA registers before and after each command, and wrap the results into a tar file. This will help determine what is messed up (the color registers, the palette registers, the Color Plane Enable registers, or something else). To run this test, download the attached file, chmod to make it executable, then reboot as usual and run the script: sudo ./grab_vbe_states The screen will clear (because of the reset command) and you may see a couple of lines of data (Allocated buffer. . .) which you may ignore. It will create five files. Please send me only the tar file, vbestates.tar. Also, does running the script fix the problem (temporarily)? Thanks again for your time and patience. ** Attachment added: grab_vbe_states http://launchpadlibrarian.net/30314102/grab_vbe_states -- Ubuntu boot screen causes virtual terminal display problems. https://bugs.launchpad.net/bugs/392959 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392959] Re: Ubuntu boot screen causes virtual terminal display problems.
Peter, yes this is a weird one. When you say that text suddenly has the right colors after executing the first command, I am assuming that you are refering to text already on the screen. The unusual characters after the first command are normal, since this changes from a 256-character font to a 512-character font, but the fact that those characters are bright is not normal. They should be at medium intensity after loading a Uni1 font. I've seen a bug that causes the characters to fail to change intensity when switching from a 256-character font to a 512-character font, or vice versa (LP:392795). But I've never before seen a case where they actually switch to the wrong intensity. Since all is well on your other PC, I decided to experiment with using Radeon hardware. Unfortunately I don't have access to a Mobility Radeon X300, like you have. I borrowed an X1600, which did not behave as yours did. Using it gave me another problem: With it I could never disable the bright text! (See https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/392795/comments/4) Do I understand your original description correctly? You don't experience a problem when GDM isn't started, even if you boot with usplash, and you don't experience a problem if you don't boot with usplash, even if GDM is started? In other words, you must boot with both for this problem to appear? Sorry not to have anything more helpful for you. -- Ubuntu boot screen causes virtual terminal display problems. https://bugs.launchpad.net/bugs/392959 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139453] Re: colors are left on the screen after blanking with usplash enabled
While the initial description is a little different, I believe that this bug has the same root cause as LP:395374. I submitted a couple of patches for that bug, which should also fix this one. -- colors are left on the screen after blanking with usplash enabled https://bugs.launchpad.net/bugs/139453 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
I believe that the above patches will also fix the symptoms described in LP:139453. -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392795] Re: Some characters always display highlighted on VGA console.
Be aware, when testing this, that other problems can also cause this symptom. If you are using a Radeon X1600 video card, these patches may not work for you. When using this card (at least the one that I borrowed) the Color Plane Enable register is apparently ignored. Not only does changing the register from 0xF to 0x7 fail to mask bright colors, changing it to zero, in an attempt to disable all color planes, still allows all sixteen colors to be displayed. This is true whether or not usplash is run. Thinking that there might be a control bit in some extended register that causes the Color Plane Enable register to be bypassed, and that some other boot-time software was modifying it and not restoring it, I looked through the somewhat limited documentation available for this card, searching for such a bit. But I came up empty handed. By then I was beginning to think that this might simply be a VGA compatibility issue. (VGA Compatible is a term sometimes used loosely by manufacturers.) So I wrote a snippet of code to a boot floppy, to be executed immediately at boot-time. This code wrote 0x7 to the Color Plane Enable register and succeeded in masking the bright colors on all the machines I booted with it, except for the one with the Radeon X1600. So it looks like there may be a hardware problem with the X1600. I can't really say for sure. I suppose it is possible that the PC's BIOS is messing with the registers on the Radeon before passing control to the boot floppy, but it seems unlikely. Or the X1600 I used could be defective. I would be interested to hear from any other X1600 or other Radeon users who are experiencing similar problems, or not. A quick test to run is this: setfont Lat15-Fixed16 ; setfont Uni1-Fixed16 ; showconsolefont This should show all 512 glyphs of the Uni1-Fixed16 font, all of the same color and intensity. (This works even if you booted with usplash.) If this is what you see, your video card is working properly (or at least its Color Plane Enable logic is). If the glyphs on the right are a different color or intensity than those on the left, you may possibly have the same problem I found when using the Radeon X1600. I could supply the test boot floppy image if the above test fails for anyone, and further testing is desired. -- Some characters always display highlighted on VGA console. https://bugs.launchpad.net/bugs/392795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
Steve, I'm using an Intel Mobile 945 graphics controller. I'm wondering if you are using an ATI controller. On my system I do not see this problem if I don't boot with usplash; I do see it when I do boot with usplash (version 0.5.25); I do not see it if I apply either of the above patches and boot with usplash. I have seen console color problems with an ATI Radeon X1600/X1650 series controller that were unrelated to usplash (although not this particular problem). And I have seen other console-related bugs reported in Launchpad which apply to systems with ATI controllers, but not all controllers. If you are using an ATI controller, you may have found another bug related, perhaps, to the ATI controller not getting initialized properly. -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392795] Re: Some characters always display highlighted on VGA console.
Another bug resulting from the fact that usplash doesn't restore the VGA registers is LP:395374. Either of the two patches that I attached to that bug report should fix both that bug and this one. The first patch above will also fix both bugs, but the second, Patch to make usplash restore Color Plane Enable Register, will only fix this bug, so one of the other patches is preferred. All patches have worked fine for me, but whichever patch, if any, is used, I hope that someone who knows the code better than I do will look it over to see if any handshaking is necessary to prevent usplash and the kernel from trying to write to the VGA registers at the same time. (By the way, the garbage mentioned in step 7 above, that is displayed by showconsolefont with some recent kernels, should be eliminated by kernel 2.6.30. See http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=528357 for details.) ** Bug watch added: Debian Bug tracker #528357 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528357 -- Some characters always display highlighted on VGA console. https://bugs.launchpad.net/bugs/392795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 355057] Re: Non-ASCII characters get corrupted in framebuffer console
Uwe Geuder wrote on 2009-04-20: . . . the characters previously corrupted appear in a different color now. While all characters, which worked before are displayed in some kind of grey, the new characters are displayed in white. Any explanation for this? . . . Yes, that is LP:392795. -- Non-ASCII characters get corrupted in framebuffer console https://bugs.launchpad.net/bugs/355057 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303561] Re: Polish diacritics not working in Alt-Ctrl-Fx console
nital wrote on 2008-11-29: 1. After applying this fix, every Polish diacritic on the screen is displayed in bold (it's white, while the non-Polish letters are grey), which looks quite strange; That sounds like LP:392795. -- Polish diacritics not working in Alt-Ctrl-Fx console https://bugs.launchpad.net/bugs/303561 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
** Attachment added: Text file to modify all console text colors http://launchpadlibrarian.net/28675872/set_red_text_colors.txt -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
** Attachment added: Patch to make usplash restore Attribute Controller Registers http://launchpadlibrarian.net/28675924/restore_attr_ctrl_regs.patch -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
** Attachment added: Patch to make usplash restore all VGA registers http://launchpadlibrarian.net/28675915/restore_all_regs.patch -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] [NEW] some console colors cannot be modified
Public bug reported: Binary package hint: usplash Ubuntu 8.10 Linux 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 linux-image-2.6.27-14-generic, Version: 2.6.27-14.33 usplash, Version 0.5.25 Bug also appears with 8.10 live CD (with 2.6.27-7 kernel). After booting with usplash (splash) and no frame buffer (nofb), some console text colors cannot be modified, nor do they blank when the screen blanks. If you've noticed that when the console blanks after the blank timeout (the default is usually ten minutes) some text remains visible, you have this bug. To reproduce: 1. Download the three attached text files. 2. If necessary, reboot using the nofb and splash options. 3. Wait for system to fully boot up, then switch to a text console and log-in. 4. Load a 256-character font so that all sixteen colors can be used: setfont Lat15-Fixed16 5. cat display_text_colors.txt 6. The text colors should now be seen (15 digits on a black background). 7. cat set_red_text_colors.txt 8. All text should now be pure red. If some aren't, you have this bug. 9. cat restore_text_colors.txt 10. Text should now be back to its default colors. While all colors remain on the screen, you may also set the blank timeout: setterm -blank 1 Then wait a minute to see if all colors go blank. (If APM is available, this may or may not be a useful test. If your backlight also goes out you won't see anything anyway.) This bug is caused by the fact that usplash does not restore the VGA Palette Registers. In fact, usplash doesn't restore any VGA registers, which also caused bug 392795. See LP:392795 for details. Years ago it did restore the registers, but that code was removed. As I did for the other bug, I am including a couple of patches for consideration. Either one should fix the problem. One patch, restore_all_regs.patch, simply restores the code that restores all of the VGA registers. The other patch, restore_attr_ctrl_reg.patch, restores only the Attribute Controller Registers -- the registers that relate to this bug and to bug 392795. I think the first patch is probably the better patch, and could make usplash a little more robust by possibly preventing other bugs from cropping up in the future due to registers that were not restored. (We've already found a couple; there could be more.) On the other hand, there is something to be said for making the smallest change necessary to fix a bug, and thus reduce the chances of creating others, which is why I've included the second patch. Note that either of these patches should also fix bug 392795. So if either of these is used, there is no need to install another patch to fix that bug. Does anyone see any potential for usplash and the kernel trying to access the VGA registers at the same time? Do we need to add any handshaking to prevent conflicts? I've not seen any problems of that sort, but it would be good if someone who knows this code better than I looked it over for that sort of thing. When testing the patch, don't forget to update the appropriate initrd.img... file (as I have forgotten more times than I'd like to admit!). ** Affects: usplash (Ubuntu) Importance: Undecided Status: New -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
** Attachment added: Text file to display console text colors http://launchpadlibrarian.net/28675866/display_text_colors.txt -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395374] Re: some console colors cannot be modified
** Attachment added: Text file to restore console text colors http://launchpadlibrarian.net/28675881/restore_text_colors.txt -- some console colors cannot be modified https://bugs.launchpad.net/bugs/395374 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392959] Re: Ubuntu boot screen causes virtual terminal display problems.
Peter, what font are you using? Does it make a difference if you run setfont Lat15-Fixed16 The contents of your /etc/default/console-setup file could be helpful. -- Ubuntu boot screen causes virtual terminal display problems. https://bugs.launchpad.net/bugs/392959 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392959] Re: Ubuntu boot screen causes virtual terminal display problems.
Peter, thanks for the quick reply and attachment. This may be related to another bug I've seen, but perhaps not. If it is, loading a 512-character font, then immediately loading a 256-character font may help. This may sound odd, but humor me. If this doesn't help I have no other ideas at the moment. I'll try to look into it further when I get the chance. Please let me know if executing the following two commands helps: setfont Uni1-VGA16 setfont Lat15-VGA16 -- Ubuntu boot screen causes virtual terminal display problems. https://bugs.launchpad.net/bugs/392959 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392795] Re: Some characters always display highlighted on VGA console.
** Description changed: Binary package hint: usplash Ubuntu 8.10 Linux 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 linux-image-2.6.27-14-generic, Version: 2.6.27-14.33 usplash, Version 0.5.25 After booting a recent kernel with usplash (splash) and no frame buffer (nofb), when using 512-character console fonts (like Uni1-Fixed16), glyphs in the second half of the font are always displayed highlighted (that is, bright white, not dull white). This can best be seen by switching to the console immediately after booting and running showconsolefont. (If you have not patched the kernel to fix the font corruption issue with the 512-character fonts, you may need to first run setfont Uni1-Fixed16 to see all of the characters.) Some background: Normally, in text mode, the VGA hardware can only display 256 unique characters, since only 8 bits are available for each character in text memory. In order to display 512 unique characters, a bit must be stolen from the attribute memory, which normally is used for the character's foreground and background colors. The bit that is stolen is normally used to define the brightness of the character's foreground color. In fact, thanks to this bug, we see that it still can affect the character's brightness even after it has been stolen. In order to get all 512 characters to be displayed at the same intensity, the kernel clears a bit in the VGA's Color Plane Enable Register to disable the corresponding bit plane. Now when a binary (bright white) is passed to the color palette, only 0111 (dull white) gets through. At boot time, console-setup is run very early, even before usplash. If the font loaded by console-setup is a 512-character font, the kernel clears the necessary bit, as discussed above. Then usplash runs, switches to a graphics mode, does its thing, then exits. When it exits it puts the console back into text mode and restores the font to the VGA memory, but it never restores the VGA registers. Most of the VGA registers are set up fine, just by switching to text mode, but not the one we are interested in here. Oddly enough, usplash does save the VGA registers -- it just never restores them. It did up until a few years ago, but that was changed. I am including a couple of patches for consideration. Either one should fix the problem. One patch, restore_all_regs.patch, simply restores the code that restores all of the VGA registers. The other patch, restore_cpe_reg.patch, restores only the Color Plane Enable Register -- the one register that relates to this bug. I think the first patch is probably the better patch, and could make usplash a little more robust by possibly preventing other bugs from cropping up in the future due to registers that were not restored. On the other hand, there is something to be said for making the smallest change necessary to fix a bug, and thus reduce the chances of creating others, which is why I've included the second patch. This problem is mentioned by Uwe Geuder in a comment to LP:355057: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057/comments/12 Reports for other bugs that also happen to mention a similar problem which may or may not be related to this bug: https://bugs.launchpad.net/bugs/303561 https://bugs.launchpad.net/bugs/159053 Note that this problem does not occur when booting the 8.10 Live CD. This is only because there was a problem with an initramfs script which prevented the font from being loaded before usplash was run. That problem was fixed last November. So you need a kernel newer than that to test this. To reproduce: 1. grep CODESET /etc/default/console-setup 2. If CODESET is not a 512-character codeset (like Uni1, Uni2, or Uni3), run sudo dpkg-reconfigure console-setup to change it. 3. Ensure that the /boot/initrd... file that you boot with was the one that was updated by dpkg-reconfigure (it isn't always) 4. Boot using the nofb and splash options. (You have a recent kernel, right?) 5. Wait for system to fully boot up, then switch to a text console and log-in. 6. showconsolefont 7. Ignore the garbage between the columns of characters -- that's another bug. 8. If the 256 characters on the right are missing or trashed, run setfont Uni1-Fixed16 - 9. If the 256 characters on the right are brighter than the 256 on the right, + 9. If the 256 characters on the right are brighter than the 256 on the left, you have this bug. -- Some characters always display highlighted on VGA console. https://bugs.launchpad.net/bugs/392795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392795] Re: Some characters always display highlighted on VGA console.
** Attachment added: Patch to make usplash restore Color Plane Enable Register http://launchpadlibrarian.net/28451755/restore_cpe_reg.patch -- Some characters always display highlighted on VGA console. https://bugs.launchpad.net/bugs/392795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392795] Re: Some characters always display highlighted on VGA console.
** Attachment added: Patch to make usplash restore all VGA registers http://launchpadlibrarian.net/28451713/restore_all_regs.patch -- Some characters always display highlighted on VGA console. https://bugs.launchpad.net/bugs/392795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392795] [NEW] Some characters always display highlighted on VGA console.
Public bug reported: Binary package hint: usplash Ubuntu 8.10 Linux 2.6.27-14-generic #1 SMP Wed Apr 15 18:59:16 UTC 2009 linux-image-2.6.27-14-generic, Version: 2.6.27-14.33 usplash, Version 0.5.25 After booting a recent kernel with usplash (splash) and no frame buffer (nofb), when using 512-character console fonts (like Uni1-Fixed16), glyphs in the second half of the font are always displayed highlighted (that is, bright white, not dull white). This can best be seen by switching to the console immediately after booting and running showconsolefont. (If you have not patched the kernel to fix the font corruption issue with the 512-character fonts, you may need to first run setfont Uni1-Fixed16 to see all of the characters.) Some background: Normally, in text mode, the VGA hardware can only display 256 unique characters, since only 8 bits are available for each character in text memory. In order to display 512 unique characters, a bit must be stolen from the attribute memory, which normally is used for the character's foreground and background colors. The bit that is stolen is normally used to define the brightness of the character's foreground color. In fact, thanks to this bug, we see that it still can affect the character's brightness even after it has been stolen. In order to get all 512 characters to be displayed at the same intensity, the kernel clears a bit in the VGA's Color Plane Enable Register to disable the corresponding bit plane. Now when a binary (bright white) is passed to the color palette, only 0111 (dull white) gets through. At boot time, console-setup is run very early, even before usplash. If the font loaded by console-setup is a 512-character font, the kernel clears the necessary bit, as discussed above. Then usplash runs, switches to a graphics mode, does its thing, then exits. When it exits it puts the console back into text mode and restores the font to the VGA memory, but it never restores the VGA registers. Most of the VGA registers are set up fine, just by switching to text mode, but not the one we are interested in here. Oddly enough, usplash does save the VGA registers -- it just never restores them. It did up until a few years ago, but that was changed. I am including a couple of patches for consideration. Either one should fix the problem. One patch, restore_all_regs.patch, simply restores the code that restores all of the VGA registers. The other patch, restore_cpe_reg.patch, restores only the Color Plane Enable Register -- the one register that relates to this bug. I think the first patch is probably the better patch, and could make usplash a little more robust by possibly preventing other bugs from cropping up in the future due to registers that were not restored. On the other hand, there is something to be said for making the smallest change necessary to fix a bug, and thus reduce the chances of creating others, which is why I've included the second patch. This problem is mentioned by Uwe Geuder in a comment to LP:355057: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/355057/comments/12 Reports for other bugs that also happen to mention a similar problem which may or may not be related to this bug: https://bugs.launchpad.net/bugs/303561 https://bugs.launchpad.net/bugs/159053 Note that this problem does not occur when booting the 8.10 Live CD. This is only because there was a problem with an initramfs script which prevented the font from being loaded before usplash was run. That problem was fixed last November. So you need a kernel newer than that to test this. To reproduce: 1. grep CODESET /etc/default/console-setup 2. If CODESET is not a 512-character codeset (like Uni1, Uni2, or Uni3), run sudo dpkg-reconfigure console-setup to change it. 3. Ensure that the /boot/initrd... file that you boot with was the one that was updated by dpkg-reconfigure (it isn't always) 4. Boot using the nofb and splash options. (You have a recent kernel, right?) 5. Wait for system to fully boot up, then switch to a text console and log-in. 6. showconsolefont 7. Ignore the garbage between the columns of characters -- that's another bug. 8. If the 256 characters on the right are missing or trashed, run setfont Uni1-Fixed16 9. If the 256 characters on the right are brighter than the 256 on the right, you have this bug. ** Affects: usplash (Ubuntu) Importance: Undecided Status: New -- Some characters always display highlighted on VGA console. https://bugs.launchpad.net/bugs/392795 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 345145] Re: Console Font not loaded when usplash in on
Camper365, I have been trying to determine what could cause the behavior that you describe. There was a problem with 8.10, if installed, that was almost the reverse of yours: the Fixed font would not be loaded at boot if usplash was on. In fact, no font would be loaded, and the font from the character ROM in the graphics card would remain in use. Not surprisingly, if your graphics card was (like most) a descendent of VGA, this font looked very similar to the VGA fonts supplied with Ubuntu. (When running 8.10 as a live CD, the Fixed font did get loaded, but if you went first to /dev/tty1, instead of 2, 3, 4, 5, or 6, you might never see it.) I believe that this problem was fixed by version 1.25ubuntu4 of the console-setup package. The fact that your system is loading a font at boot time seems to indicate that you have the corrected version, but you should probably double-check. I am wondering if you have more than one kernel installed on your system. With the corrected version (1.25ubuntu4) of console-setup, the font is properly loaded at boot time using the initrd file. When you run the command sudo dpkg-reconfigure console-setup, the initrd file is updated. But it is possible that the file being updated is not the one you are booting with. If the softlink at /initrd.img doesn't point to the initrd file that you are booting with, this could cause the behavior that you are experiencing. It would be helpful if you would could post the result of: grep -6 initrd /boot/grub/menu.lst Which of the titles in that result are you booting with? And what is the result of: ls -l /initrd.img Thanks. -- Console Font not loaded when usplash in on https://bugs.launchpad.net/bugs/345145 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385964] [NEW] VGA console supports multiple fonts but not multiple unimaps.
Public bug reported: Binary package hint: linux-image-2.6.27-7-generic In Ubuntu 8.10, when using the VGA console driver (no framebuffer). If you load a new font into one virtual console that has a unimap that differs from the unimap used by the font in another virtual console, some characters subsequently entered in the other virtual console will not be mapped correctly to the font. To reproduce this problem: 1. If your console is currently using the framebuffer driver, not VGA, boot 8,10 live CD, using nofb option if necessary. 2. Go to any virtual console. 3. If necessary, issue unicode_start to ensure you are in UTF-8 mode. 4. setfont Uni1-Fixed16 5. echo -e \xc2\xb0 6. Observe that the degree symbol is displayed. This is good. 7. Go to another virtual console. 8. setfont Uni2-Fixed16 9. Return to previous virtual console. 10. echo -e \xc2\xb0 11. Observe that the symbol displayed in now incorrect. It appears that around the time of Ubuntu 8.04, some code was added (as an UBUNTU SAUCE enhancement) to complete_change_console() in drivers/char/vt_ioctl.c. This code saves the current font when switching away from a virtual console, and restores it when switching back. So far, so good. Traditionally the VGA console driver supported one font for all virtual consoles. (I believe this is still the case with a stock kernel.) Since all consoles shared a single font, they also shared a single unimap. However, the code in drivers\char\vt.c supports multiple unimaps so that another driver (e.g., the framebuffer console driver) can use them. In vt.c, visual_init() initializes vc-vc_uni_pagedir_loc to point at vc-vc_uni_pagdir, so that each console can have its own unimap. After doing that it calls vc-vc_sw-con_init(). When using the VGA console driver, that call goes to vgacon_init() in drivers/video/console/vgacon.c. That function changes .vc_uni_pagdir_loc in the vc_data structure to point at vga_unimap_pagedir, the single unimap shared by all VGA virtual consoles. So we have multiple fonts sharing a single unimap. I've only tested this with Intrepid, but it looks like the font save/restore code was added to 8.04 and 9.04 as well. Norm Pierce ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- VGA console supports multiple fonts but not multiple unimaps. https://bugs.launchpad.net/bugs/385964 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
