You are not logged in.

#426 2011-08-25 08:36:45

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

peterjohnhartman wrote:

Second, I'm running psb-gfx from 3.0.3 and xorg 1.10.  Things seem to be (finally) fine.  However, I can't resume from suspend, neither from console nor from X.  Anyone else experience this?  All I do is

echo -n mem > /sys/power/state

I get a black screen upon resume

Best,
Peter

What does this command do? I've been using s2disk for quite some time now and suspend from disk works fine. Suspend to ram causes segfault when resuming so it's a no go. But again, I'm still with psb driver, kernel 2.26.37, xorg 1.9. Maybe these problems are fixed in 3.0 I don't know. Have you tried also this?

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

I made a list below in order to help us better document the wiki page. Please take 2' and post your answer. If you think I'm missing sth please add it. Thanks smile

Kernel version: 
Xorg version: 
Video driver:  
Are there any extra packages needed for the driver to work?:
Are there any modules needed to load?
Is xorg.conf neeed? If yes please post it:
Is native resolution working?
2D acceleration status: 
3D acceleration status: 
Flash player status (fullscreen working?): 
Movie player status: 
Hardware acceleration status: 

Last edited by maevius (2011-08-25 08:50:37)

Offline

#427 2011-08-29 20:04:38

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

So, I finally updated to linux 3.0.3 with native psb support. Didn't expect it would work with one shot but it did! Backlight seems lower than it was before. Also the touchpad scrolling doesn't work. Is it just me?

kernel 3.0.3-1
xorg-server 1.10.3.901-1

Edit: to get back the sidebar scrolling, edit /etc/X11/xorg.conf.d/10-synaptics.conf and add lines:
Option "VertEdgeScroll" "true"

https://bugs.archlinux.org/task/23330

Last edited by maevius (2011-08-29 20:15:52)

Offline

#428 2011-09-05 07:42:19

Hailstorm
Member
Registered: 2009-08-26
Posts: 11

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

apefish wrote:

I can confirm Hailstorm's jitter issue, I also get jitter a few seconds after it goes into native resolution. The jitter is on and off, usually off, but annoying when on. It's like rows of pixels get shifted or blanked for one frame, making things blurry and jittery.

Also, the whole screen seems to be shifted left one or two pixels such that the first column of characters gets shaved. Has anyone else seen this? I hope this is easy to
fix with some shift parameter somewhere.

As for X, startx works, but I get a blank grey screen. if I try to switch back to vc1-6,
They are all blank grey screens except vc1, which looks like it has my window manager drawn
on it at 640*480 but then smeared out as if the driver still thinks it's in 1366*768. It is
NOT stretched or modified at all, it is smeared; the first row of pixels on the screen looks
like a concatenation of the first and second rows, and a few from the third from the 640*480.
It is like X couldn't figure anything out and drew in 640 (usual behavior), but then
the driver is reading the framebuffer at 1366. I hope you understand what I mean.
anyways, is there anything I can do to make X draw correctly and stay on it's own vc?
As is, startx is point of no return and I have to hard power off, because I can't get to a text login to kill X.
X -configure fails complaining about xgi, vmwgfx, and something about symbol lookup.
This is all on a Asus eee 1101HA if that helps. Everything default, have not installed anything special.

EDIT: I got x working by adding xorg.conf.d/10-monitor.conf with:

Section "Monitor"
    Identifier "Monitor0"
EndSection

Section "Device"
    Identifier "Device0"
    Driver "fbdev"
Endsection

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
        Modes "1366x768"
    EndSubSection
EndSection

Basically I explicitly told X it can draw at 1366.

So the only issue remaining is the 1 pixel shift and the jitter. The jitter I can live with, the shift is really bad.
I can even see the extra column of black pixels on the right. Should I file a bug report? (Where?)

Have you been able to solve this issue or at least report the issue anywhere?
I'm also curious who i could contact about this problem. It's probably limited to asus 1101HA (i have the same model) but for me it still persists with the latest kernel. (both the jittering and the pixels getting shifted)

Last edited by Hailstorm (2011-09-05 07:43:10)

Offline

#429 2011-09-05 08:05:55

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

I have also an 1101HA and haven't faced any of your problems guys. I have native 1366x768 and no jitter or pixelation with latest linux 3.0.4-1.
I forgot to mention that I have been using these steps (except for the last one of xorg.conf) since I was with the old psb driver. Maybe that should help you out.

Last edited by maevius (2011-09-05 08:14:35)

Offline

#430 2011-09-21 23:04:32

degeberg
Member
From: Denmark
Registered: 2011-02-27
Posts: 6

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Hailstorm wrote:

I'm not using any login manager. By login prompt i just meant the default shell prompt. It doesn't seem to be related to X at all, even if i log in quickly and start X the same thing happens. The screen stays sharp for a few seconds after the boot process, and then it gets fuzzy as i explained above. I have a fairly minimalistic system so the problem could not possibly be caused by any eye-candy like a dm or a splash.
Now i timed it. It seems that something goes wrong about 30 seconds after loading the module. I started timing when the screen flushed during bootup and it switched to the native resolution. It doesn't matter if i start X or anything else, it doesn't even make a difference if i don't even log in. It just gets fuzzy after these 30 seconds and won't stop jittering.
And as i said, once it starts jittering, a reboot won't fix it but only a complete power off. I have no idea what to make of this fact but for a more experienced driver developer /and for someone more familiar with the code/ it might be a hint.

I have the exact same problem. Has anyone been able to fix it?

Offline

#431 2011-09-22 06:38:33

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Have you guys followed the steps I mentioned in my previous post? I think 915resolution-static is the package that you should use.

Offline

#432 2011-09-22 06:41:49

degeberg
Member
From: Denmark
Registered: 2011-02-27
Posts: 6

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

maevius wrote:

Have you guys followed the steps I mentioned in my previous post? I think 915resolution-static is the package that you should use.

Yes. It makes no difference with or without that package, unfortunately.

Offline

#433 2011-09-22 08:13:54

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

You sure made all the changes for the right resolution? Check the uvesafb wiki page. I have followed all the steps mentioned in there.

1) pacman -S v86d

2) build from aur 915resolution-static

3) Edit /etc/modprobe.d/uvesafb.conf
options uvesafb mode_option=1366x768-32 scroll=ywrap


4) Edit /lib/initcpio/hooks/915resolution

run_hook ()
{
   msg -n ":: Patching the VBIOS..."
   /usr/sbin/915resolution 5c 1280 800
   msg "done."
}

5) Edit /etc/mkinicpio.conf
HOOKS="base udev 915resolution v86d autodetect pata scsi sata filesystems"

6) sudo mkinitcpio -p linux

7) Remove from grub vga=xxx if any.

Offline

#434 2011-09-22 11:04:16

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 3,769

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Try using kms instead of uvesafb? It works on most devices now, just include the psb_gfx module in the initcpio.


Evil #archlinux@freenode channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

#435 2011-09-22 13:24:44

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Mr.Elendig wrote:

Try using kms instead of uvesafb? It works on most devices now, just include the psb_gfx module in the initcpio.

Does suspend/hibernate work with this? Currently with uvesafb doesn't work..

Offline

#436 2011-09-22 14:13:50

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 3,769

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

In teory it should.


Evil #archlinux@freenode channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

#437 2011-09-25 13:25:47

degeberg
Member
From: Denmark
Registered: 2011-02-27
Posts: 6

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

I got it working by removing psb_gfx from MODULES in /etc/mkinitcpio.conf.

Suspend doesn't work though, or rather, waking up from suspend doesn't work.

Offline

#438 2011-09-26 00:59:23

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,932

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

I'm running psb_gfx without uvesafb and the performance is more or less what I remember uvesafb being like. So what's the relationship between psb_gfx and uvesafb? There's an error coming up with 915resolution-static and v86d during mkinitcpio, so I'm not willing to try it.

The error is the same as Freso's post at 915resolution-static AUR page:

WARNING: errors were encountered during the build. The image may not be complete.

Last edited by skottish (2011-09-26 01:00:21)

Offline

#439 2011-09-26 03:07:39

degeberg
Member
From: Denmark
Registered: 2011-02-27
Posts: 6

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Yeah I get that warning when running mkinitcpio as well. It boots fine though.

Offline

#440 2011-09-30 01:49:59

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,932

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Bump.

I'm still curious why the psb-gfx-bzr install file and posters in this thread have recommended to use the psb-gfx module with uvesafb. Was this pre-kms advice that hasn't gone away or am I missing the point?

Offline

#441 2011-10-06 20:03:54

cesc
Member
From: Vienna, Austria
Registered: 2011-04-30
Posts: 6
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

I followed the steps indicated above by maevius and updated my xorg.conf as depicted by Hailstorm. Still, I only have a resolution of 1024x768 available sad(

Offline

#442 2011-10-06 20:29:42

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 3,769

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

skottish wrote:

Bump.

I'm still curious why the psb-gfx-bzr install file and posters in this thread have recommended to use the psb-gfx module with uvesafb. Was this pre-kms advice that hasn't gone away or am I missing the point?

Probably old info/habit, because  I can't see any reason to not use kms with the driver.


Evil #archlinux@freenode channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

#443 2011-10-07 02:20:21

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,932

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Mr.Elendig wrote:
skottish wrote:

Bump.

I'm still curious why the psb-gfx-bzr install file and posters in this thread have recommended to use the psb-gfx module with uvesafb. Was this pre-kms advice that hasn't gone away or am I missing the point?

Probably old info/habit, because  I can't see any reason to not use kms with the driver.

Thanks. As my recent experience progressed your post on setup was the only thing that was making sense to me. In your opinion, has there been in substantial progress made in performance from uvesafb and this driver?

Offline

#444 2011-10-07 15:26:55

Mr.Elendig
#archlinux@freenode channel op
From: The intertubes
Registered: 2004-11-07
Posts: 3,769

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

In my case the new psb_gfx driver with kms is the first time the laptop have worked at all with anything else than vesa, and even as slow as it is, it is about 600 times better than vesa tongue Also, it seems the the performance with 3.1 will be even better. What I miss the most though is a propper xorg driver for it too though, instead of having to use fbdev.


Evil #archlinux@freenode channel op and general support dude.
. files on github, Screenshots, Random pics and the rest

Offline

#445 2011-10-08 02:18:16

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,932

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Well, this is definitely an improvement in that it's far easier to set up than uvesafb. And, it's not really bad. I'd just like to see improved scrolling and better color saturation. If the color situation was fixed and nothing else changed, I'd be pretty content.

Offline

#446 2011-10-09 07:09:15

cesc
Member
From: Vienna, Austria
Registered: 2011-04-30
Posts: 6
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Just to throw some info to the bunch:

I installed Ubuntu 11.04 with the EMGD (Intel Embedded Media and Graphics Driver). It is of course not the same as arch in my Toshiba R700 (other chipset), but I got a smooth Youtube video playback (up to 240p or 360p in full screen, up to 480 in "normal-window" view) and a reasonably responsive experience.

Offline

#447 2011-10-29 03:25:44

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,932

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Mr.Elendig wrote:

...snip...

Also, it seems the the performance with 3.1 will be even better.

...snip...

This happened. Scrolling is now pretty fluid with the 1.2Ghz Atom on the netbook that I have with the 3.1 kernel. Very nice.

Now, a little splash of color (read: a proper X driver) and things may finally be set right for the GMA500 chipset under Linux.

Offline

#448 2012-02-29 00:10:43

kingguru
Member
From: Copenhagen, Denmark
Registered: 2011-01-19
Posts: 16
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Hi there,

This thread might seem pretty dead, but I'm taking my chance and posting here anyway.

So, it seems like a lot of development is still going on with the kernel driver for the GMA500 since Alan Cox started working on it, but I'm wondering if that will mean that we will ever have acceptable performance under X with an open source driver.

I have tried to look into whether any development was going on with regards to an X driver and it seems like most people are still stuck with the old, closed sourced EMGD driver and I haven't found anything related to an open source driver being developed.

As far as I have understood, there has been quite a lot of changes to the X architecture with regards to what the responsibility of the X driver should be, where more has been moved to kernel space and that the kernel driver should provide an interface for X to talk to (DRI?)

Does that mean that we will eventually get acceptable performance from our GMA500 chipset in X with a generic driver as the kernel driver gets updated?

I know this question is not directly related to using GMA500 in Arch Linux, but I would rather ask here than getting flamed in LKML or whatever the x.org development equivalent is. :-)

If someone can point me somewhere where I can find more information, I would find that very useful as well.

Thanks.

Offline

#449 2012-08-07 21:34:49

maevius
Member
From: Greece
Registered: 2009-09-10
Posts: 134
Website

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

I edited the wiki page [0] so that it refers only to the in-kernel driver (gma500_gfx). In the troubleshooting area there is a hack for suspend to work. Native resolution is not a problem for me (Asus 1101HA), so you could visit ubuntu's wiki (See also section) to try with 915resolution. Hope that helps.

[0] https://wiki.archlinux.org/index.php/Poulsbo

Last edited by maevius (2012-08-07 21:35:37)

Offline

#450 2012-08-07 22:47:46

min
Member
Registered: 2011-05-14
Posts: 46

Re: Poulsbo aka Intel GMA500 drivers PKGBUILD

Personally I think that the old information is useful to learn about the options for poulsbo. Though it wouldn't be recommended for rolling release like archlinux, it would benefit some to use that old drivers using different distribiution, or even using arch but downgrade several components.

That aside, I can confirm in my machine (vaio p) that the suspend trick work. And the native resolution is supported out of the box. Regarding brightness control, I put this inside rc.local

chmod a+w /sys/class/backlight/psb-bl/brightness
# Make it less bright on start up
echo 20 > /sys/class/backlight/psb-bl/brightness

And Create similar script to mulenmar to increase or decrease brightness (named birightness-control.sh inside ~/bin/)

#/!bin/bash

brightness=`cat /sys/class/backlight/psb-bl/brightness`

increment=5

if [ "$1" == + ]; then
	if [ $brightness -lt 100 ]; then
		brightness=$[$brightness + $increment]
	fi
elif [ "$1" == - ]; then
	if [ $brightness -gt 0 ]; then
		brightness=$[$brightness - $increment]
	fi
else
	exit 0;
fi

echo $brightness > /sys/class/backlight/psb-bl/brightness

notify-send "brightness: $brightness"

And bind it using xbindkeys

"~/bin/brightness-control.sh -"
XF86MonBrightnessDown

"~/bin/brightness-control.sh +"
XF86MonBrightnessUp

That will enable me to control the birghtness using the hotkey without entering password. I am not sure whether it is safe to change the permision for the backlight though.

Thanks for updating the wiki, and maybe information about using modesetting instead of fbdev can be put in there as well. I heard that using modesetting will enable changing resolution (Might be useful with external monitor)

Offline

Board footer

Powered by FluxBB