SliTaz SliTaz Forum

You are not logged in.

#1 2014-10-01 18:55:28

Jon_J
Member
Registered: 2013-02-25
Posts: 38

@jp32 - GMA500 poulsbo graphics

[c]Dear jon_J
You have been successful running slitaz with 1366x768 on a dell netbook with
gma 500-chip. Can You just tell me how You did? I have a Acer Spire-One 751 with GMA-500.
The greatest pain is using (trying to use) the mousewheel for scrolling in
pdf- or txt-files. Thank You (or other) for help.
jp32[/c]
This was a long time ago, and your question is under a topic for a now defunct computer I no longer use, so I started a new topic.

Try these 2 links, the first one describes (last 2 posts) my experience installing the driver.

http://forum.slitaz.org/topic/gma500-aka-poulsbo-video-card-support/page/2

HowTo link to install driver:

http://doc.slitaz.org/en:guides:poulsbo

Offline

#2 2015-04-02 17:30:14

Jon_J
Member
Registered: 2013-02-25
Posts: 38

Re: @jp32 - GMA500 poulsbo graphics

jp32,

Here is what I have done recently. March 31, 2015

It got my GMA500 poulsbo chip working in recent Slitaz-rolling-core March 27, 2015

The linked page has a typo (March 17, 2015)

http://forum.slitaz.org/topic/does-anyone-have-an-xorgconf-example-file-for-slitaz-rolling-core

Look at last post by me.

======================================================

Following these instructions: http://doc.slitaz.org/en:guides:poulsbo

I have my Intel GMA500 poulsbo driver running in Slitaz-rolling-core Date March 27, 2015

When I first followed those instructions, where the author states:

======================================================

# nano /etc/rcS.conf

Look for the row called LOAD_MODULES and remove poulsbo from the list, also make sure that psb_gfx is present.

Then remove VESA and add the psb_gfx module (which is inside the linux-staging package)

======================================================

I was in text mode then and there was nothing inside /etc/rcS.conf (I was also running as root)

Today I booted Slitaz with vga=791 as shown above in my last post. The window manager loaded, and I followed the instructions above, again.

When I got to the part where you use nano to edit /etc/rcS.conf, this time the rcS.conf file was full of settings.

I finished following the instructions, rebooted into my other distro, removed "vga=791" from Grub2's grub.conf file, and rebooted a second time into Slitaz.

Yay! 1366x768 Hi Def graphics is working!! smile

Jon

BTW, I almost forgot. In those instructions the author says to download and install:

xorg-xf86-video-fbdev-0.4.2.tazpkg

That package has beed replaced by: xorg-xf86-video-fbdev-0.4.4.tazpkg

And the url in those instructions no longer exists. I found the 0.4.4 version in one of the repositories using a browser on my desktop box. Once I found it, I was able to install it.

======================================================

Offline

#3 2015-04-02 21:43:57

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: @jp32 - GMA500 poulsbo graphics

The GMA 500? I've done driver modding for the GMA 950 to X3100 on Windows (Chell Modded Video driver) and it's the first time I've heard of it. How does it rate rendering wise? I actually want to get into driver modding on Linux too.

Offline

#4 2015-04-03 02:42:13

Jon_J
Member
Registered: 2013-02-25
Posts: 38

Re: @jp32 - GMA500 poulsbo graphics

Trixar_za,

I'm not a coder, or programmer. just a regular user that loves Linux.

If you Google "Intel GMA500" and/or "poulsbo" you will find tons of info.

A lot of people have been successful making it load onto their system using Linux.

There are/was a lot of people that have/had problems getting decent video on their laptop with GMA500 poulsbo. This chip is on my Dell mini 1010 netbook (this chip came out in 2007 or 08)

You'll have your best luck using the term "poulsbo" in Google. It's an unusual name and doesn't have any common words or numbers.

Jon

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]