You are not logged in.
kest wrote:Hi all. somebody can make a PKGBUILD for IEGD?
http://www.ihku.biz/joggler/iegd/ these may help.
got no luck with this one.
Last edited by canolucas (2010-08-07 03:07:15)
Offline
I'm doing a little Wiki editing, so I wanted to be sure I understand how the situation has "advanced" in the past few months and get some thoughts on how I plan to update the article.
Since the PSB driver has been updated (I have it working with kernel 2.6.34-ARCH and Xorg server 1.8.1.902), it no longer requires downgrading and forcing Pacman to ignore the kernel and Xorg updates. Thanks to this, the instructions for installing the Xorg 1.6.3.901 server and the FBDEV driver aren't strictly necessary for it.
The IEGD driver, from what I understand, still requires the older kernel, libdrm, and Xorg, and those who use would want the FBDEV driver for that available as well as a fallback. Also, it is not designed for netbooks.
Apparantly there is an "EMGD" or something driver in which Intel split out the US15W support from IEGD because it was so different from their own devices. It was SUPPOSED to be out by the end of July, not sure if it is yet. Don't really care anyway, since it's designed for EMBEDDED devices and not netbooks. I assume it also uses an older kernel, libdrm, and Xorg as well.
Also, I've read rumors of an "IVI" driver designed for in-vehicle systems, but I don't know anything about it. Both it and the EMGD driver would require research that I don't have a chance to do right now, due to other projects.
Would it be alright if I restructure the "Poulsbo" wiki entry to emphasize which do and do not require downgrading? As is, the current structure is
1 Drivers and their capabilities and limitations
2 Installing the IEGD driver
2.1 Installing Xorg server 1.6
2.2 Troubleshooting Xorg 1.6
2.2.1 Driver cannot be found
2.3 Installing IEGD-enabled kernel
2.4 Installing IEGD binary drivers
2.5 Installing mplayer-vaapi
3 Installing the Poulsbo driver
4 Installing the FBDEV Xorg framebuffer driver, Xorg-server>=1.7
5 Installing the FBDEV Xorg framebuffer driver, Xorg-server=1.6.3.901
My plan was to reorganize things to
1. Drivers, Their Capabilities and Limitations
1.1 PSB Driver
1.2 IEGD Driver
1.3 EMGD Driver
1.4 IVI Driver2. Do I Need To Downgrade?
3. Xorg-server 1.7 or higher (current Arch)
3.1 PSB/GMA500 Driver
3.1.1 Installing the Driver
3.1.2 Configure Xorg.conf3.2 Framebuffer FBDEV Driver
3.2.1 Installing the FBDEV Driver
3.2.2 Configure Xorg.conf
3.2.3 Configure Framebuffer (required)
3.2.3.1 Install v86d, 915resolution-static
3.2.3.2 Configure v86d
3.2.3.3 Configure 915resolution-static
3.2.3.4 Update Initrd4. Xorg-server 1.6.3.901
4.1 Are You Sure This Is What You Need? // Explain that if FBDEV is all that's needed, new Xorg is sufficient and less work
4.2 Install/Downgrade to Xorg 1.6.3.901
4.3 Framebuffer FBDEV Driver
4.3.1 Download and Install FBDEV driver // Explain how to find older, compatible FBDEV driver package
4.3.2 Configuration // Direct reader to 3.2.2 through 3.2.3.44.4 Intel Embedded Graphics Driver (IEGD)
. . . .
And so on, through IEGD, Mplayer, et cetra. The goal is to make the Wiki article more of an easy-to-read how-to, with the technical explanations isolated to one section. The reader would encounter the easier, less-work-involved method, which would probably be what they're looking for anyway, first.
Also: if you want to quote this post, please only quote the particular portion you're referring to, otherwise this long thread will become even longer and harder to extract information from.
If nobody has any strong objections, I'll probably rearrange things in about a week, and further ideas/changes can be discussed in the Wiki page's Talk section instead of here.
Last edited by mulenmar (2010-08-16 15:23:29)
Offline
Hi mulenmar,
That is awesome that you are working to update wiki.
I want to throw out some info on the EMGD driver. I have been following Meego very closely cause that is where Intel was supposed to distribute this driver. This weekend, I was able to take some rpm's from Meego's IVI release which included a beta release of that driver and install it on the latest arch (which includes kernel 2.6.34-ARCH and Xorg server 1.8.1.902). I have to admit that I am very impressed. It was very stable and provides excellent 2D and 3D graphics. The down side: I still can't suspend, but that may be due to not having the right suspend foo. Also I have not been able to get libva (or libva-sds or compat-libva) installed correctly, thus no HD video.
The point is that I believe if Intel were to ever release this driver, it would be a major advancement for our cause. Also, just to be clear, I was planning on publishing PKGBUILDs for us, but yesterday, Meego removed the rpm's from their repo!!!! Bastards!!! This driver we never supposed to be distributed I guess.
There are 10 kinds of people in this world.
Those who can read binary, and those who can't.
Offline
Personally, I'm quite satisfied with the "PSB" driver -- sure, I've had no luck getting Mplayer and libva to work together yet, and in Arch I have issues with anything OpenGL (probably something to do with the libdrm-psb files), but at least I get 2d responsiveness similar to with the FBDEV driver AND brightness control. In Ubuntu Lucid, I even get more-or-less perfect suspend-and-resume with it.
That's all I really need though, as with optimized builds of the codecs and MPlayer, "-ao sdl -vo sdl -framedrop -lavdopts fast:skiploopfilter=all" options on MPlayer's command line, and the CPU at full power I can watch 720p without issue. With the files I've downloaded, tests, and deleted anyway.
[rant]
This chipset is the "ET: The Extra-Terrestrial" of Intel chipsets, though. Product of rushed schedule, constantly falling into issues. Pain in the rear and pointless for the amount of effort you put into making it work.
[/rant]
Just a question of clarification: you said you got the EMGD driver from the Meego IVI distro -- I thought the IVI driver was a fourth, separate thing? And that the EMGD driver was split from the IEGD driver because the driver was so different from the rest, which was all Intel code?
Offline
I put together a simple shell script to set the backlight brightness with far less typing. It's designed for use with the PSB driver, and works from within a xterm or from the console.
The script is located here in the "Post your handy self made command line utilities" thread.
Offline
Wiki updated. We still need someone to write the section about getting mplayer-vaapi working, and then I'll feel comfortable with removing the "{Stub}" tag.
Anyone is welcome to wiki of course, but I'll probably have figured out mplayer-vaapi within a few days. In the meantime, I'm trying to sort out why nothing Mesa-related works with the PSB driver.
EDIT: Added a subsection detailing how to set backlight brightness.
Last edited by mulenmar (2010-08-24 21:45:00)
Offline
I went ahead and did some wiki changes
Offline
nevermind...
Last edited by maevius (2010-09-08 08:33:31)
Offline
I went ahead and did some wiki changes
Thanks for the help, maevius! Any and all help is appreciated.
As for my contributions, I fear that they are mostly at an end. My netbook refuses to boot now, almost as if there was no memory in it. There is, but I don't have the $$$ to spend on a new memory stick that might not even solve the problem and that I can't use in any other machines. And I am *not* getting another machine with an Intel System Controller Hub -- the next new laptop I buy will probably be a Leemote Yeelong, and that won't be until my current (circa 2001) laptops are completely nonfunctional. I'm *sick* of hardware that suffers from not at least having open datasheets available. Call me a min-RMS, but I like my hardware to actually be supported and supportable! *sigh*
I can, however contribute these tidbits from the last bit of testing I did on it:
Although the PSB driver in the AUR works with Xserver 1.8, you can not get Xv video acceleration. That's dealt with by the blobs (Xpsb.so at least), which don't work with anything newer than Xserver 1.6. I worked for hours on this with Xserver 1.8, perusing Xorg.0.log for the PSB-related messages and even trying some symlinks in an effort to get VA-API working. Xv works perfectly with Xserver 1.6, and I was able to play a 720p copy of "Big Buck Bunny" without any stuttering, noticeable artifacts, or audio/video desync. I was even able to speed up playback to 125% without stuttering, if I recall correctly.
I still wasn't able to get VA-API working, even with an MPlayer supporting it. This wasn't because of something wrong with MPlayer at all, it was partly because the PSB DRI (or is it GLX?) blob was in the wrong location (check vainfo, it'll complain and then you can use locate to find it) and, from what I was able to determine, dependent on a near-ancient version of Mesa that isn't even available on Mesa's servers anymore. You can find it on Sourceforge of course, but that all requires a lot of hand-editing the PKGBUILD
Offline
what need for acpi(cpu freq, fan)? Brightness "0" too bright... how to reduce?
Offline
I'm following the updated Wiki to install Arch on my Dell Mini 10 using the PSB/GMA500 Driver but don't get past the first item!
My system is up to date as of today with XFCE installed, I get a desktop working at 1024x768 by default. My monitor supports 13xx res. I had it working under Ubuntu as a test, but I use Arch on all my other machines so like to keep it the same as well.
[media@mini ~]$ yaourt psb-firmware
1 aur/psb-firmware 0.30-1 (9)
Binary firmware for the Poulsbo (psb) 3D X11 driver
==> Enter n° (separated by blanks, or a range) of packages to be installed
==> ----------------------------------------------------------------------
==> 1
==> Downloading psb-firmware PKGBUILD from AUR...
bsdtar: Removing leading '/' from member names
x PKGBUILD
First Submitted: Sat, 14 Nov 2009 14:35:42 +0000
psb-firmware 0.30-1 : Binary firmware for the Poulsbo (psb) 3D X11 driver
( Unsupported package: Potentially dangerous ! )
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==> ------------------------------------
==> n
Unable to read PKGBUILD for psb-firmware
==> WARNING: Following packages have not been installed:
psb-firmware
[media@mini ~]$
Offline
what need for acpi(cpu freq, fan)? Brightness "0" too bright... how to reduce?
There are quite a few packages that do the job. I haven't tested them but look here. As for the brightness, it is written in the wiki. I made some changes so as to be more clear.
I'm following the updated Wiki to install Arch on my Dell Mini 10 using the PSB/GMA500 Driver but don't get past the first item!
My system is up to date as of today with XFCE installed, I get a desktop working at 1024x768 by default. My monitor supports 13xx res. I had it working under Ubuntu as a test, but I use Arch on all my other machines so like to keep it the same as well.
Try to build it locally. I can't see where the error occurs...
Offline
Try to build it locally. I can't see where the error occurs...
Thanks for the tip, I'd always used yaourt for AUR. Didn't realise how easy it was
EDIT:
Thanks to all who contributed to getting the PSB/GMA500 Driver method in the Wiki/AUR. Glad to finally get rid of Windows on my netbook.
Last edited by dave00 (2010-09-15 10:01:25)
Offline
You don`t understood me... Bright "0" under Linux with loaded psb module brighter what "0" in Windows or Linux without use psb driver.
Offline
I'm getting a lag with window movement, although psb is loaded.
lsmod | grep psb
psb 136635 2
drm_psb 141959 3 psb
agpgart 23520 1 drm_psb
i2c_algo_bit 4407 1 psb
i2c_core 15599 4 videodev,psb,drm_psb,i2c_algo_bit
My xorg.conf is
Section "Device"
Option "ShadowFB" "true"
Option "MigrationHeuristic" "greedy"
Identifier "Card0"
Driver "psb"
VendorName "Intel Corporation"
BoardName "System Controller Hub (SCH Poulsbo) Graphics Controller"
BusID "PCI:0:2:0"
EndSection
lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller (rev 07)
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap,
GLX_INTEL_swap_event
GLX version: 1.2
GLX extensions:
GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,
GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
GLX_SGIX_visual_select_group
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) GMA500 20081116 - 5.0.1.0046 x86/MMX/SSE2
OpenGL version string: 2.0 Mesa 7.4
OpenGL shading language version string: 1.10
OpenGL extensions:
GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program,
GL_ARB_fragment_shader, GL_ARB_multisample, GL_ARB_multitexture,
GL_ARB_occlusion_query, GL_ARB_pixel_buffer_object,
GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shader_objects,
GL_ARB_shading_language_100, GL_ARB_shadow, GL_ARB_texture_border_clamp,
GL_ARB_texture_compression, GL_ARB_texture_cube_map,
GL_ARB_texture_env_add, GL_ARB_texture_env_combine,
GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3,
GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two,
GL_ARB_texture_rectangle, GL_ARB_transpose_matrix,
GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader,
GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color,
GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate,
GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint,
GL_EXT_cull_vertex, GL_EXT_compiled_vertex_array, GL_EXT_copy_texture,
GL_EXT_draw_range_elements, GL_EXT_framebuffer_object, GL_EXT_fog_coord,
GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels,
GL_EXT_pixel_buffer_object, GL_EXT_point_parameters,
GL_EXT_polygon_offset, GL_EXT_rescale_normal, GL_EXT_secondary_color,
GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_wrap,
GL_EXT_subtexture, GL_EXT_texture, GL_EXT_texture3D,
GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add,
GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3,
GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod_bias,
GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array,
GL_APPLE_client_storage, GL_APPLE_packed_pixels,
GL_ATI_blend_equation_separate, GL_ATI_separate_stencil,
dmseg
[drm] intel_lvds_prepare
[drm] intel_lvds_set_power: 0
[drm] intel_lvds_set_backlight: the level is 0
[drm] LVDSGetPWMMaxBacklight: the max_pwm_blc is 31250.
[drm] LVDS: set mode 1366x768 a
[drm] intel_lvds_commit
[drm] intel_lvds_set_power: 1
[drm] intel_lvds_set_backlight: the level is 100
[drm] LVDSGetPWMMaxBacklight: the max_pwm_blc is 31250.
[drm] intel_lvds_dpms: the mode is 0
[drm] intel_lvds_set_power: 1
[drm] intel_lvds_set_backlight: the level is 100
[drm] LVDSGetPWMMaxBacklight: the max_pwm_blc is 31250.
Last edited by maevius (2010-09-16 11:54:04)
Offline
I noticed that psb-kmod is still flagged as out-of-date in the AUR, probably because it cannot be compiled with the current kernel.
The make process fails with:
/tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/psb_msvdx.c: In function 'psb_msvdx_mtx_interrupt':
/tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/psb_msvdx.c:593:4: warning: ISO C90 forbids mixed declarations and code
CC [M] /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/psb_msvdxinit.o
CC [M] /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/psb_detear.o
LD [M] /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/drm-psb.o
LD [M] /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/psb.o
Building modules, stage 2.
MODPOST 2 modules
/bin/sh: line 1: 4811 Segmentation fault scripts/mod/modpost -i /usr/src/linux-2.6.35-ARCH/Module.symvers -I /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/Module.symvers -o /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/Module.symvers -S -w -s vmlinux /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/drm-psb.o /tmp/yaourt-tmp-jon/aur-psb-kmod/src/psb-kernel-source-4.41.1/psb.o
make[2]: *** [__modpost] Error 139
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.35-ARCH'
make: *** [modules] Error 2
Anyone know what is causing this, and have enough source-hacking skills to fix it? =P
Offline
@Jonhoo
I have kernel .35-4 and it builds fine. Try to download it and build it locally or be the first one to try the repo I've made
I updated the wiki and added a custom repo hosted on dropbox (what a cool service!). Feel free to try it. I'm considering making also one for xorg-1.6.
Install from Custom Repository
Add to your /etc/pacman.conf the following custom repository[poulsbo] Server = http://dl.dropbox.com/u/6228981/poulsbo/i686/psb/
remove libdrm and install the driver
# pacman -Syy # pacman -Rd libdrm # pacman -S xorg-x11-drv-psb
Restart X
Last edited by maevius (2010-09-24 12:35:23)
Offline
It seems that PSB does not work with xserver 1.9
Offline
seeking is right. There is neither no mention on wiki how to install Xorg 1.8 nor when support for Xorg 1.9 will be ready.
Offline
seeking is right. There is neither no mention on wiki how to install Xorg 1.8 nor when support for Xorg 1.9 will be ready.
Xorg 1.8 has been in the repos for quite some time, what do you mean by "there is no mention on wiki how to install it"?
xorg 1.9 though doesn't work with the driver unfortunately. I've modified the wiki yesterday. As for support it's really hard to tell as the psb driver is stuck to where it was since summer...
Last edited by maevius (2010-10-17 19:29:23)
Offline
Right now there isn't. I don't have any idea how to downgrade from 1.9.
By the way, if Fedora 13 or 14 uses Xorg 1.9, then Adam Williamson from http://happyassassin.net really should know, hot to make it work.
Offline
Well if you haven't cleaned up your cache, the packages are still in /var/cache/pacman/pkg/.
The ones you'll need to downgrade are
xorg-server xf86-input-evdev xf86-input-keyboard xf86-input-mouse xf86-input-synaptics xf86-video-fbdev xf86-video-vesa
and maybe
libgl mesa
I'm not sure. Just browse in that directory and install packages with
pacman -U package
Offline
I've installed Arch yesterday, when had given up trying with Ubuntu 10.10, Fedora 14 alpha and Mandriva. (=
So for me the only hope is that if somebody makes a repo with Xorg 1.8, if making the driver work with 1.9 is impossible within few days/weeks.
-----
Fedora 14 (rawhide) uses Xorg-server 1.9 and Adam Williamson from the site mentioned above pushed psb-driver to RPM Fusion. May be some programming person is able to make it work with Arch...
Last edited by sindikat (2010-10-17 23:41:20)
Offline
I'll try and find the xorg 1.8 packages within the day.
Offline
I've installed Arch yesterday, when had given up trying with Ubuntu 10.10, Fedora 14 alpha and Mandriva. (=
So for me the only hope is that if somebody makes a repo with Xorg 1.8, if making the driver work with 1.9 is impossible within few days/weeks.
I made a repo in dropbox for xorg 1.8. Add
[xorg-1.8]
Server = http://dl.dropbox.com/u/6228981/poulsbo/i686/xorg-1.8
to pacman.conf and downgrade to xorg 1.8.
Offline