You are not logged in.
Greetings.
I was setting up uvesafb and v86d in my installation by following the ArchWiki page here and ran into some problems.
Briefly, configurations made in /etc/modprobe.d/uvesafb do not come into effect until initramfs is regenerated (e.g. "mkinitcpio -p kernel26" or "mkinitcpio -g /boot/kernel26.img) and this has to be done every time /etc/modprobe.d/uvesafb is modified for those modifications to come into effect. This step is not explicitly mentioned and only implied in "Uvesafb and 915resolution\Finalize" subsection.
Can someone please confirm that this is indeed the case, e.g. regeneration required after each reconfiguration? I will clarify this in the wiki if it is confirmed.
Last edited by msh (2009-01-20 18:16:37)
Offline
i think it is neccesarry
also i need to stop reading marvel i read your country as latveria
dovie andi se tovya sagain
Offline
Thanks, INCSlayer!
More input would be welcome. I'd like to hear what others think of this.
also i need to stop reading marvel i read your country as latveria
Heh.
Offline
Or "New Latveria" if you like "Secret Wars".
Has anyone else noticed a messed up screen after updating from v86d 0.1.9-1 to v86d 0.1.9-2? I had to downgrade to get my framebuffer to work. Otherwise the screen was split down the middle, flashed all the time and had the letters too spread out... basically what happens to xorg when you make the refresh rates grossly wrong.
6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.
Offline