startx fails on EeePC 900HA with Intel GMA 950?

[SteelBytes]

worked fine in bt4-pre-final and bt3, but not bt4-final :-(

--------------------

X: warning; process set to priority -1 instead of requested priority 0

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux bt 2.6.30.9 #1 SMP Tue Dec 1 21:51:08 EST 2009 i686
Build Date: 09 March 2009 10:48:54AM
xorg-server 2:1.5.2-2ubuntu3.1 (buildd@rothera.buildd)
Before reporting problems, check X.Org Wiki - Home
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 13 18:56:45 2010
(==) Using config file: "/etc/X11/xorg.conf"
(EE) GARTInit: Unable to open /dev/agpgart (No such file or directory)
FATAL: Could not load /lib/modules/2.6.30.9/modules.dep: No such file or directory
(EE) [drm] drmOpen failed.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low?
(EE) intel(0): Couldn't allocate video memory

Fatal server error:
AddScreen/ScreenInit failed for driver 0

giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.

[DigiP]

Maybe boot a bt4-pre-final and compare the output of x-org in that version to the new one and see what has changed. Also, you might try to run the xorg conf and create a new file for your system instead of using the one shipped with this release:

X -configure

If the auto configuration above doesnt work try and edit what you want to change manually in the xorg.conf file and maybe compare to what you had in settings for the previous release that worked.

[InlandEmpire]

works perfectly on my 1000 and my 900.
Did you check MD5 of the iso? If thats good try reinstalling again.

[SteelBytes]

yes the MD5 is fine (first thing I checked)

further investigation ...

it works from cold boot, but not from restart! (by restart I mean using ctrl+alt+del to logout/exit backtrack and restart the pc)

on restart I get errors about not being able to set Hardware/System clock, and a few "FATAL: Could not load /lib/modules/2.6.30.9/modules.dep: No such file or directory"

[Valifake]

Check your /lib/modules/ if you have a 2.6.29 directory and not an 2.29.30 directory then you have persistent settings from another install conflicting with the BT4 install. resolve this conflict by moving or deleting the other files. You should then be able to start BT4.

The actual problem your having relates to not being able to load the agpgart module so you can't access the laptops ram to use as video memory.

[arkasjimis]

I have the same problem with my eee1000h and BT4-Final. The same I have with BT3 solved by edit the "menu.lst" with the right resolution of screen but not now. I try the "fix-splash" but neither that works. Can someone helps?

[john_doe]

The same here. Although mine is the 100HA model, the graphics card is the same. And X behaves exactly as SteelBytes explained.

[SteelBytes]

> Check your /lib/modules/ if you have a 2.6.29 directory and not an 2.29.30 directory

but it works sometimes so this suggestion doesn't make sense.

also, this is a clean formated usb stick (I am using live boot from usb) and the contents have been verified (the iso has valid md5, and I extracted the iso and compared it's contents to the usb - perfect byte for byte).

anyway, now it works everytime for me and I haven't changed anything! (not even re-extracting the iso to usb)

go figure.

[d3m0nEy3z]

Please try this :

~#fixvesa

it wil change the resolution to VESA MODEl

[rcs-al]

I solved it, i had the pre-release in my usb drive, and after booting the kernel from the final iso, it took the squashfs from the pre-release(extracted files), and it ended having the final kernel with the wrong modules. Solution: deleted completely the pre-release from my usb and extracted the files from the final one, everything works out of the box.

Btw, i have a 904ha