xorg-prop-drivers-testers team mailing list archive

[Tim Cuthbertson <ratcheer@xxxxxxxxx>]

On Fri, Feb 12, 2010 at 12:45 PM, Erik Andersen
<erik.b.andersen@xxxxxxxxx> wrote:
>
>
> On Fri, Feb 12, 2010 at 07:26, Keivn McKinney <klmckinney1@xxxxxxxxx> wrote:
>>
>> I am having a hard time installing it on my Toshiba that has an ATI x1200
>> graphics card. Has anyone found a solution???
>> Thanks,
>> Kevin
>> On Thu, Feb 11, 2010 at 9:52 PM, Chase Douglas
>> <chase.douglas@xxxxxxxxxxxxx> wrote:
>>>
>>> Tim Cuthbertson wrote:
>>>>
>>>> On Thu, Feb 11, 2010 at 3:10 PM, Chase Douglas
>>>> <chase.douglas@xxxxxxxxxxxxx> wrote:
>>>>>
>>>>> ratcheer@xxxxxxxxx wrote:
>>>>>>
>>>>>> Ok, I give up. I cannot get a working installation of Lucid on this
>>>>>> machine. BTW, it was not the installation of the nVidia driver that
>>>>>> messed
>>>>>> it up. I deleted the Lucid partitions and reinstalled Lucid alternate
>>>>>> CD.
>>>>>> Then, when it attempted to reinstall the nVidia driver, I declined. I
>>>>>> attempted to reboot Lucid and it will not boot.
>>>>>>
>>>>>> It is strange that it boots successfully at the end of Lucid
>>>>>> installation,
>>>>>> but then, even with no changes, it will never boot again.
>>>>>>
>>>>>> It appears that I cannot participate in this testing effort.
>>>>>
>>>>> There's a known issue with plymouth that caused boot failures for
>>>>> people. It
>>>>> is partially fixed as of some point yesterday with a new plymouth
>>>>> package.
>>>>> You should try with the new package and/or by removing the plymouth
>>>>> package
>>>>> to see if it helps you.
>>>>>
>>>>> Thanks,
>>>>> Chase
>>>>>
>>>>
>>>> I installed the new kernel 2.6.32.13 dated 2010-02-11 and it still
>>>> will not boot. Then,
>>>> I removed the plymouth package and it still will not boot.
>>>
>>> That's too bad. Please consider opening a bug against the linux package
>>> so we can track the issue and try to get it resolved for you. We obviously
>>> don't want to ship Lucid with defects that cause it to not boot on some
>>> hardware.
>>>
>>> Thanks,
>>> Chase
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~xorg-prop-drivers-testers
>>> Post to     : xorg-prop-drivers-testers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~xorg-prop-drivers-testers
>>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~xorg-prop-drivers-testers
>> Post to     : xorg-prop-drivers-testers@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~xorg-prop-drivers-testers
>> More help   : https://help.launchpad.net/ListHelp
>>
> I may have just not been paying attention, but I never really got what
> wasn't working on the second boot up. I had trouble with X coming up but
> either having a jumble of the colors it should be showing, or not responding
> to mouse clicks, on both the live cd and the installation. I got around this
> by doing Ctrl Alt SysRq r and then Ctrl Alt SysRq k.
> Sorry if this isn't the same problem.
> Also, when I'm posting to an email list, do I just send it too the list, or
> do I cc the person I'm replying to also?
> Erik B. Andersen
> _______________________________________________
> Mailing list: https://launchpad.net/~xorg-prop-drivers-testers
> Post to     : xorg-prop-drivers-testers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~xorg-prop-drivers-testers
> More help   : https://help.launchpad.net/ListHelp
>
>

On a last hunch to try to get Lucid to work, I wondered whether my
Karmic installation was for some reason keeping Lucid from booting.
Maybe the partitioning or something. So, today, I bit the big one and
backed up my /home to a DVD, then started Lucid install and completely
repartitioned the disk and gave the whole thing to Lucid. I would like
to be able to report that it worked, but it didn't.

So, now I am doing a clean install of Karmic. Lord knows how I will
get everything back and configured, again. But, I will probably get
rid of a lot of old garbage, too.

Tim