Intel Poulsbo graphics with Puppy Lucid
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Intel Poulsbo graphics with Puppy Lucid
The Intel "Poulsbo" GMA500/600/3600/3650 graphics devices are not a true Intel product, but actually "PowerVR" by Imagination Technologies, and are problematic in Linux. They're found in certain Atom-based netbooks - "Silverthorne" Z5xx, "Lincroft" Z6xx, and "Cedarview" N2600/N2800/D2500/D2550/D2600/D2700 models.
Recent official versions of Puppy Linux (at June 2015) - Slacko 5.5/5.6/5.7/6beta and Tahrpup 6.x should all support Poulsbo graphics quite well, via the modesetting Xorg driver, which works in combination with the gma500_gfx kernel module. It should be noted that this is a non-accelerated graphics driver, but it's as good as you can get, and graphics performance is reported as quite good. The shortcoming is no support for 3D games, etc.
But for Puppy Lucid the modesetting driver cannot be used due to Lucid's older kernel. Fortunately there's an alternative graphics driver for Lucid which I now attach - the fbdev driver, which works in combination with the uvesafb kernel module.
Recent official versions of Puppy Linux (at June 2015) - Slacko 5.5/5.6/5.7/6beta and Tahrpup 6.x should all support Poulsbo graphics quite well, via the modesetting Xorg driver, which works in combination with the gma500_gfx kernel module. It should be noted that this is a non-accelerated graphics driver, but it's as good as you can get, and graphics performance is reported as quite good. The shortcoming is no support for 3D games, etc.
But for Puppy Lucid the modesetting driver cannot be used due to Lucid's older kernel. Fortunately there's an alternative graphics driver for Lucid which I now attach - the fbdev driver, which works in combination with the uvesafb kernel module.
- Attachments
-
- uvesafb-k2.6.33.2.pet
- ONLY compatible with Puppy 5.1/5.2
- (59.34 KiB) Downloaded 1455 times
-
- xorg-fbdev-Puppy5.pet
- (8.52 KiB) Downloaded 1456 times
Last edited by tempestuous on Fri 05 Jun 2015, 07:35, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
INSTRUCTIONS
Boot to your Lucid installation. Lucid will have already autoconfigured the generic "vesa" graphics driver - possibly with the wrong resolution and even flashing or glitches.
Download the fbdev and uvesafb dotpets from the previous post, and install both.
Do some research to find out the best (native) resolution of your monitor. If you don't know this information, you can diagnose with this command -
A resolution typical for Atom netbooks is 1366x768, which is considered a non-standard resolution, and I will use these values in the following example.
First you need to run the "915resolution" command which will permit the Poulsbo bios to report 1366x768 as a valid resolution to Xorg -
("38" is an Intel bios mode number)
And to make this fix permanent, the same command needs to be written to the relevant Puppy configuration file, as such -
Next you need to totally disable the vesa Xorg driver, otherwise the Xorg launch script will reinstate it, and disallow you from using the fbdev driver.
Use ROX to navigate to /usr/lib/xorg/modules/drivers and there you will see "vesa_drv.so"
You can delete it, but it would be a better idea just to shift it out of /usr/lib/xorg
So open a second ROX window, and move vesa_drv.so to somewhere convenient, like /root
Now you're ready to exit X with Ctrl<Alt>Backspace
which will drop you back to a command prompt. Prior to Xorg configuration you must first load the "uvesafb" kernel module, specifying the correct resolution, with this command -
Notice the "@60" at the end of the command - this is to set the refresh rate to 60Hz. It's a fairly safe value. Later you can try 65 or 70 if you think your screen flickers.
Now run the configuration wizard, with -
Select "Probe" and after a few seconds you should be presented with a list of resolutions to choose from. There's a fair chance that your correct resolution is not listed - don't worry, the resolution set by the kernel module actually overrides anything set by the Xorg configuration, so you can safely choose any value. The wizard will ask you if you want to TEST your configuration, which you should accept. Once the wizard finishes, you will be back at the command prompt. Now go ahead and re-launch X with this command -
and hopefully you should now see your desktop - at the correct resolution - thanks to a better graphics driver!
There's just one more step to make these settings permanent - open /etc/rc.d/rc.local in Geany, and add this line -
Save.
Reboot to check that the new driver settings hold. There's a small chance that X may fail to launch at bootup, and drop you at the command prompt - if this happens, you should just need to run the "xwin" command. This is a minor annoyance, but will hopefully not affect many users.
Boot to your Lucid installation. Lucid will have already autoconfigured the generic "vesa" graphics driver - possibly with the wrong resolution and even flashing or glitches.
Download the fbdev and uvesafb dotpets from the previous post, and install both.
Do some research to find out the best (native) resolution of your monitor. If you don't know this information, you can diagnose with this command -
Code: Select all
ddcprobe
First you need to run the "915resolution" command which will permit the Poulsbo bios to report 1366x768 as a valid resolution to Xorg -
Code: Select all
915resolution 38 1366 768
And to make this fix permanent, the same command needs to be written to the relevant Puppy configuration file, as such -
Code: Select all
echo "915resolution 38 1366 768" > /etc/resolutionfix
Use ROX to navigate to /usr/lib/xorg/modules/drivers and there you will see "vesa_drv.so"
You can delete it, but it would be a better idea just to shift it out of /usr/lib/xorg
So open a second ROX window, and move vesa_drv.so to somewhere convenient, like /root
Now you're ready to exit X with Ctrl<Alt>Backspace
which will drop you back to a command prompt. Prior to Xorg configuration you must first load the "uvesafb" kernel module, specifying the correct resolution, with this command -
Code: Select all
modprobe uvesafb mode_option=1366x768@60
Now run the configuration wizard, with -
Code: Select all
xorgwizard
Code: Select all
xwin
There's just one more step to make these settings permanent - open /etc/rc.d/rc.local in Geany, and add this line -
Code: Select all
modprobe uvesafb mode_option=1366x768@60
Reboot to check that the new driver settings hold. There's a small chance that X may fail to launch at bootup, and drop you at the command prompt - if this happens, you should just need to run the "xwin" command. This is a minor annoyance, but will hopefully not affect many users.
Last edited by tempestuous on Fri 05 Jun 2015, 07:43, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
If you have an ASUS Eee netbook with Poulsbo graphics, you are likely to want to use Puppeee, and as I understand it Puppeee already contains the necessary fbdev Xorg driver and uvesafb kernel module ...
but if you have a netbook other than Eee, you're more likely to want to use Fluppy. I just discovered that Fluppy 013 includes the fbdev Xorg driver, but it doesn't include the uvesafb kernel module, so I now attach it as a separate dotpet.
Once this dotpet is installed, setup instructions are the same as above.
but if you have a netbook other than Eee, you're more likely to want to use Fluppy. I just discovered that Fluppy 013 includes the fbdev Xorg driver, but it doesn't include the uvesafb kernel module, so I now attach it as a separate dotpet.
Once this dotpet is installed, setup instructions are the same as above.
- Attachments
-
- uvesafb-k2.6.35.7.pet
- compatible ONLY with Fluppy 013
- (28.78 KiB) Downloaded 1031 times
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I don't know for sure. I've only tested this Xorg driver with my onboard SiS graphics card where it works fine, but I have no direct experience with Poulsbo graphics devices.
First let's just check that you have installed the dotpets from the first post, which are compatible with Puppy 5.1/5.2?
I would guess that when you load the uvesafb module, you may be specifying parameters too high for the graphics device to handle. So if you are using the same values I provided in my example above -
then maybe the refresh rate needs to be reduced? Exit X and try this -
or even this
First let's just check that you have installed the dotpets from the first post, which are compatible with Puppy 5.1/5.2?
I would guess that when you load the uvesafb module, you may be specifying parameters too high for the graphics device to handle. So if you are using the same values I provided in my example above -
Code: Select all
modprobe uvesafb mode_option=1366x768@70
Code: Select all
modprobe uvesafb mode_option=1366x768@65
Code: Select all
modprobe uvesafb mode_option=1366x768@60
Would this have any positive impact on a Samsung NB30 with a GMA3150?
The Netbook is working OK but seems dim in bright light ... and I am always curious about incremental improvements ... especially while we pray for Jemimah to be reassigned to quiet desk-duty!
I am also trying to update Claws-mail ... preferably without breaking it!
The Netbook is working OK but seems dim in bright light ... and I am always curious about incremental improvements ... especially while we pray for Jemimah to be reassigned to quiet desk-duty!
I am also trying to update Claws-mail ... preferably without breaking it!
[b]Thanks! David[/b]
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
[i]Home page: [/i][url]http://nevils-station.com[/url]
[i]Don't google[/i] [b]Search![/b] [url]http://duckduckgo.com[/url]
TahrPup64 & Lighthouse64-b602 & JL64-603
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
I don't know. Go ahead and try it.edoc wrote:Would this have any positive impact on a Samsung NB30 with a GMA3150?
But follow the instructions I provided in the second post carefully, and in particular, make sure you shift the generic vesa Xorg driver, rather than deleting it. Because you may want to revert to the vesa driver if you're not happy with the fbdev driver.
And to be clear: the fbdev driver that I have provided here, like the generic vesa driver (which Puppy currently falls back to with Poulsbo devices) is non-accelerated.
So your video performance under Linux will never be as good as it could be if a fully-accelerated Xorg driver could be made to work properly.
What do I mean by poor video performance?
- less than snappy page scrolling of word processor documents with complex fonts etc.
- stuttery video file playback, especially with higher resolution video files.
I am going to drop in my two cents worth of advice here and suggest you do a backup of your pupsave file before you start anything like this.
That way, in a worst case crash, you have a backup that you can copy to your frugal install directory to recover.
Pupsave backups have saved my bacon a number of times!
That way, in a worst case crash, you have a backup that you can copy to your frugal install directory to recover.
Pupsave backups have saved my bacon a number of times!
Im trying to install lucy 5.2.8 on a asus eee 1101ha, but I´m stuck on
"We need to configure Xorg to use the newly installed fbdev driver: open /etc/X11/xorg.conf in Geany, and change this line -
Code:
Driver "vesa" #card0driver
to this -
Code:
Driver "fbdev" #card0driver "
cant even find the word driver in that file, I guess I ´m going wrong somewhere before that but cant figure out where.
"We need to configure Xorg to use the newly installed fbdev driver: open /etc/X11/xorg.conf in Geany, and change this line -
Code:
Driver "vesa" #card0driver
to this -
Code:
Driver "fbdev" #card0driver "
cant even find the word driver in that file, I guess I ´m going wrong somewhere before that but cant figure out where.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia