FS#29781 - [initscripts] consolefont is reset to default after loading udev

Attached to Project: Arch Linux
Opened by erdbeer (erdbeer) - Sunday, 06 May 2012, 12:45 GMT
Last edited by Tom Gundersen (tomegun) - Saturday, 09 June 2012, 17:07 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 16
Private No

Details

Description:
The consolefont is reset to default after udev is loaded. Before the bug existed, udev was loaded before setting the consolefont.

Additional info:
Bug was created with this change:
http://projects.archlinux.org/initscripts.git/commit/?id=222cefd41344f82a88dbf2b4a9480c966884d0e7


Steps to reproduce:
1. set consolefont to something non-default
2. boot and watch
This task depends upon

Closed by  Tom Gundersen (tomegun)
Saturday, 09 June 2012, 17:07 GMT
Reason for closing:  Fixed
Comment by fzap (fzap) - Sunday, 06 May 2012, 15:24 GMT
I can confirm this. I've changed consolefont to CONSOLEFONT="Lat2-Terminus16", but it will be resetted after boot process.
Comment by Tom Gundersen (tomegun) - Sunday, 06 May 2012, 19:02 GMT
Hm... probably this means that the font settings are lost when the graphics driver is loaded. That's not cool. I'd argue this should be fixed in the kernel. Thanks for reporting, I'll look into it.
Comment by Tilman Blumenbach (Tblue) - Monday, 14 May 2012, 12:09 GMT
I fixed this on my system by adding the i915 module to MODULES in /etc/mkinitcpio.conf (you might need to use another module, depending on your graphics card/chipset).
Comment by aksr (aksr) - Thursday, 17 May 2012, 05:17 GMT
@tomegun: Hello. Any progress on this?
Comment by Tom Gundersen (tomegun) - Thursday, 17 May 2012, 15:11 GMT
Fixed in git. Will be included in the next release.
Comment by aksr (aksr) - Thursday, 17 May 2012, 17:54 GMT
Thank you.
Comment by aksr (aksr) - Friday, 01 June 2012, 21:53 GMT
@tomegun: This bug isn't fixed with the latest initscripts 2012.05.1-3.
Comment by Tom Gundersen (tomegun) - Friday, 01 June 2012, 22:56 GMT
it will be fixed in the next proper release. i.e., 2012.06.1-1.

Loading...