Hi Daniel,
If you don't mind, could you post this as a new thread? I don't want to make
this thread too long with unrelated issues. I will move this reply to your
new thread when it's done. But I can give a quick thought about those issues:
- The first issue could be that your CD is
Let me make sure I understand you correctly.
Did you experience graphical corruption like in this image with a previous (
Just to be sure, did you install 64-bit Trisquel 5 over 32-bit Trisquel 5 by
formatting the hard drive? Or did you update it somehow? Or did you install 5
64 over an older 32-bit?
I don't think 32-bit vs 64-bit has anything to do with it, though. It
corrupts on both 32- and 64-bit for me.
I think I was wrong; probably it is a different problem. It happened long
time ago. Maybe I saw it in another machine.
I've tried a Trisquel 4.0 live session and now I think that I'm experiencing
the problem I had in the past. I'll describe the case with the hope of help,
not being
Hi malberts,
First, to answer your question: I've got an NVIDIA Geforce 8300 GS video
card installed (came with the machine). I didn't try your suggested
solution, because FRAMEBUFFER-y was already in
/etc/initramfs-tools/conf.d/splash
Although the corrupt screen used to be displayed
I tried to install Trisquel 5 and I didn't experience the error! I had such
experience with Trisquel 4.5, but I didn't reproduce it this time. The only
problem was that brightness was very low an I was not be able to adjust it
with the Fn key; it always indicated the maximum brightness in
I did some more testing using my Thinkpad. I measured the time from pressing
the laptop's power button until some image from Plymouth appears and also the
total time (including that) until I get the login screen. The times were
measured with a stopwatch so the timing might off by ~ +1/-1
Thanks very much for doing all of this investigation. Unfortunately, the
above solution didn't work.
Thanks for trying that, though.
What graphics card are you using? And did the above change have *any* effect
at all?
If you do CTRL+ALT+F6 when the corrupted image appears and then immediately
thereafter CTRL+ALT+F7 what do you see? I get a brief flash of black (as it
switches to the
I could not get it to work. I played around with /etc/default/grub and the
/etc/grub,d/ files but I had no luck (those are the files where other people
suggest changes should be made). It would either show the same mess or
nothing at all. I do not have sufficient knowledge of the
OK, so I actually found another 5400 hard drive to put into the Thinkpad. My
testing so far:
- 5400 vs 7200 hard drive makes no difference to Plymouth,
- Ubuntu 11.04 gives me a similarly corrupted Plymouth.
I found an interesting thing. When the corrupted image appears and I switch
to
With Ubuntu 11.10 so far:
- Plymouth is still corrupted (similar graphical distortion)
- Switching the console when the garbled image appears and switching back
causes Plymouth to display correctly for the very short remaining time.
I can confirm that comment 5 at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/723477 produces a minor
(hacky) solution.
I removed vt.handoff=7 as per that comment and Plymouth does not corrupt now
but there is quite a long time before the Plymouth even starts to show. And
just
Thanks for datailing your tests and researches!
Apologies for my multiple postings, but I've found this:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/713088
The photo in there is exactly what I get except with the Trisquel
green instead of the purple.
I'll probably only get back to this issue nearer to the weekend.
So in the
No solution to offer, but I have this problem with a freshly installed 32-bit
Trisquel 5.0 on an old Dell Vostro 400 desktop (64-bit machine).
Shutting down, however, it displays the glowing logo correctly.
Apologies for my multiple postings, but I've found this:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/713088
The photo in there is exactly what I get except with the Trisquel green
instead of the purple.
I'll probably only get back to this issue nearer to the weekend. So in the
18 matches
Mail list logo
