Closed GoogleCodeExporter closed 8 years ago
rEFIt does not show this issue. since both are GPL, why don't you look around
in refits source code about EFI graphics?
Original comment by mikeloc...@gmail.com
on 11 Jun 2010 at 7:10
Perhaps you can try different themes, theme like refit or ubuntu should be
pretty fast.
Original comment by bean12...@gmail.com
on 11 Jun 2010 at 8:08
quite true. the radiance theme seems to be quite slow, I just noticed it on
another computer.
as a sidenote, I'm not sure if it's a burg bug or a linux one so I won't report
it here, but linux seems to regain the framebuffer very late. It stays stuck on
the last thing burg displayed for ~10 seconds, then I see plymouth for only 1
second, and then X. On my other, normal (BIOS) computer, it quickly goes to a
blinking _ then a much longer plymouth. This is a rather annyoing bug,
especially when resuming, as it stays tuck there for a while... I don't even
see plymouth telling me it's resuming, it's stuck on burg and after ~20-30
seconds it's in X, with no trace of plymouth (and sometimes it doesn't even go
to X, instead I think it's on a VT, as it seems as soon as X starts, VTs are
disabled and the screen turns off when I go to one, and when it resumes
sometimes it stays black and pressing Alt+F7 fixes it...)
Original comment by mikeloc...@gmail.com
on 23 Jun 2010 at 6:20
radiance use transparent layer, it needs to draw multiple layers when it needs
to update, while other themes only need to draw one layer. However, I'd try to
improve the update algorithm when I have more time.
BTW, plymouth doesn't work well with framebuffer, even for bios mode. In
previous version, I keep video mode and pass the framebuffer address to linux,
and users reports all sorts of problem. Later, I switch back to text mode
before booting linux and everything works fine. Of course, EFI don't have text
mode, therefore there is no easy fix for this.
Original comment by bean12...@gmail.com
on 24 Jun 2010 at 3:52
Original comment by bean12...@gmail.com
on 24 Jun 2010 at 3:52
Original issue reported on code.google.com by
mikeloc...@gmail.com
on 11 Jun 2010 at 7:09