[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: asus eee pc 1101HA: memtest error

Colin Brace wrote:

Mike Wohlgemuth wrote:
I can't really help with your memory issue, but unless you plan on coding your own X driver, you will probably want to stick to F11 since it has a functioning Poulbos driver available from RPM Fusion:


It's been working great for me on an Acer A0751h-1401. I'm cannot tell you how frustrated with Intel I am over the GMA-500.


The Poulbos driver has also been an amazing source of frustration for me;
moreover, you've gotten further than I have. Since acquiring this netbook
around two months ago, I have been scouring the net looking for a solution
all in vain. I've posted it about in the comment section of Adam
Williamson's blog:

As well as here:


and here:


and here:


without success. The worst is that an Amazon customer did get F11 working on
this very model:


As I detailed in exhaustive detail in all of the above posts, in any of the
distros that support Poulbos -- Ubuntu 9.04, F11, Mandriva 2010 -- the
screen grays out at the point X is loaded. Nothing in the xorg or system
logs give any indication of what is going wrong. The thing boots but nothing
is displayed.

At the moment, I am running this Eee with VESA 800x600, which is obviously
deeply unsatisfactory. I love the size/performance of this laptop, but
basically, from a Linux perspective, it appears to be a lemon; I would have
sold it already on eBay except that I deleted Windows the partition, and I
have no idea how to reinstall it.

Put it back in from you backup.  :-(
Okay, you didn't make one, let's get your system working.

In similar situations I have had luck with these techniques. If you feel like trying a few I expect one or more will help.
- add "vga=ask" or some known good resolution. Need not be your desired
  resolution, just what works.
- be sure you take xorg.conf out and let it build one
- use the "video=" boot option to get various options
- use the option to set the X driver ("xdriver=" from memory)
- use another framebuffer
Can't guess which might help, sorry.

Bill Davidsen <davidsen tmr com>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]