lubuntu-qa team mailing list archive
-
lubuntu-qa team
-
Mailing list archive
-
Message #02497
Re: Saucy Alpha Alternate PPC
On May 14, 2013, at 2:50 PM, Str8bs wrote:
Thanks Keith.
Post live install:
could you sudo nano /etc/yaboot.conf and remove the appends which have
those commands to see if you can replicate what Lars saw post
alternate install? Don't forget to sudo ybin -v after editing.
If you want to try capturing some logs, I would remove quiet splash as
well and put "drm.debug=0x4 plymouth:debug" there instead.
After doing the above, several screens of text scrolled past during
the boot process. I end up with a multi-color display at what appears
to be a very low resolution and low color depth setting.
However, I could just make out the outline of a rectangle in the
middle of the screen, which turned out to be the login window. When I
type my password (blindly), the boot process continues and ends up at
the desktop with the correct resolution, but still the wrong color
depth.
Still, at this point I'm able to launch applications and windows
normally. The color depth is low, but the resolution is correct and
everything works correctly--Firefox, FXTerminal, etc.
Also, where will I find these logs you mentioned. I don't know where
to look for them. Please excuse my ignorance, Linux is new to me.
To clarify: some appends used to boot the live installer will get
added to yaboot automatically which can confuse or imply differences
between the live and alternate installers.
That line in yaboot does literally "append" its contents just as if
you had typed them manually after Linux at the boot: prompt.
No need to reinstall, but could you(or anyone with r200 radeon) try
booting the live iso with "live radeon.modeset=1 video=offb:off
video=radeonfb:off radeon.agpmode=-1" (that is negative 1 on the very
When I tried the above boot parameters with the live iso, I ended up
at a black screen, loaded with lines of text. I don't know how to
capture this text, so I can't tell you what it said.
end)
My goal here is to hopefully identify the actual culprit to the point
a dev can either correct or add a quirk so only "live" would be
required to boot.
Str8
Follow ups
References