Bug with splash screen on some GPU/Computers
Projekt: | Trisquel |
Version: | 6.0 |
Komponente: | Packages |
Kategorie: | Fehlerbericht |
Priorität: | normal |
Zugewiesen: | upstream |
Status: | active |
Gehe zu:
Hello everyone,
I've noticed that on 2 of my 3 computers where Trisquel is installed I have the same problem. The splash screen doesn't appear normally. Either it is divided in multiple parts or doesn't appear (in this case I only see 3 weird lines).
Here is what I see in most cases :
So I started to see where this could come from (since it happens on my two computers with Nvidia but not on the one with Intel). I started to update the kernel (installing the jxself 3.7's one) and it doesn't have this bug. But this isn't a definitive solution.
I've installed Aptosid just to test and saw that the stock kernel from Trisquel using aptosid grub would load normally.So I started to search on grub and I've found this line:
menuentry 'Trisquel GNU/Linux, with Linux-Libre 3.2.0-31-generic' --class trisquel --class gnu-linux --class gnu --class os { recordfail gfxmode $linux_gfx_mode insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos3)' search --no-floppy --fs-uuid --set=root 01fd22de-b9bd-4948-8948-8969e4f96ef3 linux /boot/vmlinuz-3.2.0-31-generic root=UUID=01fd22de-b9bd-4948-8948-8969e4f96ef3 ro quiet splash $vt_handoff initrd /boot/initrd.img-3.2.0-31-generic }This is the original line from Trisquel's Grubd. The aptosid's grub is almost similar except for :
recordfail gfxmode $linux_gfx_mode insmod gzioThat aren't there. recordfail and insmod gzio couldn't be since they have nothing to do (directly or indirectly) with the splash screen. So I tried just to comment the second line before restarting.
And this was the result:
So it seems to be a very simple bug that could be solve. But how ? And what file should be changed in /etc/grub.d/ to reflect this changes on every update of the stock kernel ?
Best Regards, Luis.
Anhang | Größe |
---|---|
IMG_20121214_021134.jpg | 348.17 KB |
IMG_20121214_021548.jpg | 602.66 KB |
- Anmelden oder Registrieren um Kommentare zu schreiben
This is is fixed by the following upstream bug
http://ubuntu.5.n6.nabble.com/PATCH-QUANTAL-fix-booting-with-plymouth-nouveau-td4994027.html
As you can see it is fixed in Quantal, which is currently expected to be the basis for Trisquel 6.5.
@SirGrant -please mark this as status Upstream.
I know because it was fixed on Kernel 3.5. But how about the 5.5 and 6.0 users ? They will have to boot their computer everyday with this bug. Why not just blacklist those with Nouveau just for this option and disable it only for them ? This will not affect the rest of the experience with Trisquel and will solute (what I call) a problem with Trisquel 5.5 and 6.0.
Because the general rule is to fix the bug where it occurs, not change code elsewhere in a distribution to bypass the problem unless it is a show stopper. The bug is in nouveau.
Following on from above, Trisquel is resource constrained. If Ubuntu doesn't have the resources to backport the proper fix to oneiric and precise then Trisquel certainly doesn't.
Further, the recommendation on the forum to drop the splash parameter in /etc/default/grub as below seems 'good enough' for most people.
Change
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to read
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
and then run
sudo update-grub
Having a 'good enough' simple bypass would seem to reduce alternative bypasses involving coding to the status of a SMOP. https://en.wikipedia.org/wiki/SMOP