Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#30290 - Mkinitcpio fails to take uvesafb.conf into consideration.
Attached to Project:
Arch Linux
Opened by Mikolaj Romel (wassup) - Thursday, 14 June 2012, 11:37 GMT
Last edited by Dave Reisner (falconindy) - Friday, 15 June 2012, 00:06 GMT
Opened by Mikolaj Romel (wassup) - Thursday, 14 June 2012, 11:37 GMT
Last edited by Dave Reisner (falconindy) - Friday, 15 June 2012, 00:06 GMT
|
DetailsDescription:
I've got an fbsplash-patched kernel to use it with a background image. In order to do that, I need to load uvesafb driver with a couple of options. Normally this should be set in /etc/modprobe.d/uvesafb.conf. This file contains the following line: options uvesafb mode_option=1366x768-32 scroll=ywrap Nevertheless, on boot, the system tries to load 1024x768 resolution. Such a resolution is set in /usr/lib/modprobe.d/uvesafb.conf - a file that changes on every upgrade of the package. When the resolution is changed in the abovementioned file to match what is in /etc/modprobe.d/uvesafb.conf and mkinitcpio -p kernel command is issued, everything starts working as expected. Thus, I believe that mkinitcpio does not take the file found in /etc into consideration. Unfortunatelly, I have no internet at the moment, so I will not be able to debug it further or answer the questions quickly - sorry for the inconvenience. |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 15 June 2012, 00:06 GMT
Reason for closing: Won't fix
Additional comments about closing: If you want specific module config on the image, add it in /etc/mkinitcpio.conf
Friday, 15 June 2012, 00:06 GMT
Reason for closing: Won't fix
Additional comments about closing: If you want specific module config on the image, add it in /etc/mkinitcpio.conf
Comment by Dave Reisner (falconindy) -
Thursday, 14 June 2012, 12:24 GMT
How is mkinitcpio supposed to access this file when it's on root device, which isn't even mounted yet? You need to add /etc/modprobe.d/uvesafb.conf to the image if you want to override options from the shipped config.