| Author |
Message |
wiarus_old
|
|
Post subject: X not starting in VB
 Posted: 13.02.2011, 17:53
|
|
Joined: 2010-09-14
Posts: 20
Location: Poland
Status: Offline
|
|
I tried to boot all 3 newest isos in VirtualBox and system exits when starting kdm.
So I started with init 4 option - ok, but again exits after run init 5.
VirtualBox version 3.2.10 r66523. |
_________________
Welcome on http://m-artcollection.eu - my ART site 
|
| |
|
|
|
 |
|
drb
|
|
|
Post subject:
Posted: 15.02.2011, 13:27
|
|
Joined: 2010-09-11
Posts: 96
Status: Offline
|
|
| I had the same issue here and xmodule=vesa worked |
|
|
| |
|
|
|
|
|
drobole
|
|
|
Post subject:
Posted: 15.03.2011, 19:06
|
|
Joined: 2011-03-15
Posts: 1
Status: Offline
|
|
I'm having a problem that might be related.
Starting the live CD (2011-01) on my laptop with a onboard intel i915 card, it fails to start X.
Basically, X says that it can't allocate the framebuffer, and that module fbcon was not found.
Earlier versions of aptosid didn't have this problem as I have aptosid installed on it already.
Maybe its a kernel thing...
I haven't tried xmodule=vesa yet but I'll try that when I get a chance.
If this is a new issue I'll be happy to post output from logfiles. |
|
|
| |
|
|
|
|
|
devil
|
|
|
Post subject:
Posted: 15.03.2011, 19:51
|
|
Joined: 2010-08-26
Posts: 491
Location: Berlin
Status: Offline
|
|
drobole: please do not highjack this thread. thxx.
if needed, start your own.
greetz
devil |
|
|
| |
|
|
|
|
|
|
|
|
