Bug 521034 - LiveCD 32-Bits does not load KDE Desktop; remains in command prompt
Summary: LiveCD 32-Bits does not load KDE Desktop; remains in command prompt
Status: RESOLVED DUPLICATE of bug 517102
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: Live Medium (show other bugs)
Version: Milestone 3
Hardware: i686 openSUSE 10.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Stephan Kulow
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-10 12:47 UTC by Francis Lamonde
Modified: 2009-07-10 18:30 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francis Lamonde 2009-07-10 12:47:06 UTC
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.11) Gecko/2009060215 Firefox/3.0.11

LiveCD 32-bits M3 seems to boot up normally for a while, I cannot find any unexpected error, but at the point where it is supposed to load X and KDE Desktop, it defaults to command prompt log-in. Logging in under root or linux user and typing 'startx' says that I have no screen.

64-Bits LiveCD M3 is working fine.

I do not know how to troubleshoot this problem.

Reproducible: Always

Steps to Reproduce:
1. Insert LiveCD 32-Bits Milestone 3
2. Boot from GRUB using the default options
3.
Actual Results:  
Defaults back to command prompt log-in and starting X returns a 'no screen' error.

Expected Results:  
Boot sequence should go through, find the screen and load to KDE Desktop automatically.
Comment 1 Daniele Tombolini 2009-07-10 18:24:30 UTC
Nvidia ?!?
If yes: it's a dupe #517102
If not: http://en.opensuse.org/Bugs:X

Bye.
Comment 2 Francis Lamonde 2009-07-10 18:30:07 UTC
Related to the grafx card, not the screen, of course I didn't think about that.

So yes, nvidia (not the same card as 517102 but same manufacturer).

Let's make it a dupe.

tnx

*** This bug has been marked as a duplicate of bug 517102 ***