The ioctl structures were updated in kernel 2.6.36, causing the builds to fail: psb_drv.c: 985: error: unknown field 'ioctl' specified in initializer
Created attachment 253847 [details, diff] Patch to fix compile on kernel 2.6.36
Created attachment 253849 [details, diff] Patch from bug 322293, also required
Created attachment 253851 [details] ebuild to support new patches
Hi, For what it's worth, I can report a successful compile with this ebuild. linux-2.6.26-gentoo-r1 Not sure if this is the correct place to report this, but I have a few more kernel requirements these modules needs: drm-psb.ko needs unknown symbol acpi_evaluate_object psb.ko needs unknown symbol i2c_bit_add_bus psb.ko needs unknown symbol acpi_evaluate_object I've got the above messages during compile with a customized kernel. Also agpart (If I remember correctly) needs to be selected during kernel config, otherwise the compile fails. I report this because I saw in the ebuild that there are allready other checks about kernel options which must be selected. Thanks for these patches Jim! :-)
(In reply to comment #0) > The ioctl structures were updated in kernel 2.6.36, causing the builds to fail: > > psb_drv.c: 985: error: unknown field 'ioctl' specified in initializer > Seems it also needs glproto!
(In reply to comment #0) > The ioctl structures were updated in kernel 2.6.36, causing the builds to fail: > > psb_drv.c: 985: error: unknown field 'ioctl' specified in initializer > I get it to compile with glproto (which provides the relevant .h) but I get in dmesg: psb: Unknown symbol i2c_bit_add_bus Presumably, this is because some relevant i2c module or CONFIG_ isn't built into my kernel. I'll go through the kernel options in i2c to figure out what it is but this too should be added into the ebuild. Also, if you have a suggestion--nothing obvious called out to me in make menuconfig.
Hi. Finally got it to compile and work (briefly). I did need CONFIG_I2C_ALGO_BIT in the kernel (should add this to the ebuild?). In any case, attached is the X.log output of the segfault I get about 5 minutes into an X session. XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" after 6763 requests (6763 known processed) with 0 events remaining. urxvt: X connection to ':0.0' broken, unable to recover, exiting.
Could you share a little more about your setup? Are you running a composite desktop? What Window Manager? etc.. (In reply to comment #7) > Hi. Finally got it to compile and work (briefly). I did need > CONFIG_I2C_ALGO_BIT in the kernel (should add this to the ebuild?). > > In any case, attached is the X.log output of the segfault I get about 5 > minutes into an X session. > > XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" > after 6763 requests (6763 known processed) with 0 events remaining. > urxvt: X connection to ':0.0' broken, unable to recover, exiting. >
Rob, Thanks for the list of missing symbols, this helps. I will post an updated ebuild, hopefully by the end of this weekend. If it helps anyone, I have tested with genkernel (along with my own kernel), which should "just work". (In reply to comment #4) > Hi, > > For what it's worth, I can report a successful compile with this ebuild. > linux-2.6.26-gentoo-r1 > > Not sure if this is the correct place to report this, but I have a few more > kernel requirements these modules needs: > > drm-psb.ko needs unknown symbol acpi_evaluate_object > psb.ko needs unknown symbol i2c_bit_add_bus > psb.ko needs unknown symbol acpi_evaluate_object > > I've got the above messages during compile with a customized kernel. > > Also agpart (If I remember correctly) needs to be selected during kernel > config, otherwise the compile fails. > > I report this because I saw in the ebuild that there are allready other checks > about kernel options which must be selected. > > Thanks for these patches Jim! :-) >
(In reply to comment #8) > Could you share a little more about your setup? Are you running a composite > desktop? What Window Manager? etc.. So, it turns out I need to have Options "AccelMethod" "EXA" in xorg.conf to avoid this problem. My system is x86 stable, i.e., xorg-server 1.7.7-r1. I have a custom 2.6.36.1 kernel. My xorg.conf is vanilla other than the above Options. Now, so far things are ok: I get psb to load and make my console nice and pretty (if a bit slow) and X runs (if a bit slow; in fact, really slow). However, no segfaults or crashes except: 1. If I run xrandr -o right I get a blank screen. (I can post the relevant X.log if you'd like) 2. If I run mplayer I get a segfault!
Jim, Thanks for all your hard work on this. I bought my T91 last week and since then it has been a whirlwind of disappointment in discovering just how bad these gma500/poulsbo drivers are! It seems that one of the big problems is that they only work in certain pristine environments, i.e., with a certain X version and a certain kernel. What might be useful is that you post as well your kernel .config and version and your xorg.conf and version when you post the updated ebuild. At the moment, I got it to work in 2.6.36.1 and 1.7.7. It is slightly less responsive than the uvesafb + 915resolution (+gma500 patch) + fbdev route that also works. Do you feel that way too, or is this something wrong on my end? I would also like to know if xrandr -o right causes a segfault for you or not. (As to my mplayer problem, there appears to be an mplayer workaround I haven't yet looked into.) (In reply to comment #9) > Rob, > > Thanks for the list of missing symbols, this helps. I will post an updated > ebuild, hopefully by the end of this weekend. If it helps anyone, I have > tested with genkernel (along with my own kernel), which should "just work". > > (In reply to comment #4) > > Hi, > > > > For what it's worth, I can report a successful compile with this ebuild. > > linux-2.6.26-gentoo-r1 > > > > Not sure if this is the correct place to report this, but I have a few more > > kernel requirements these modules needs: > > > > drm-psb.ko needs unknown symbol acpi_evaluate_object > > psb.ko needs unknown symbol i2c_bit_add_bus > > psb.ko needs unknown symbol acpi_evaluate_object > > > > I've got the above messages during compile with a customized kernel. > > > > Also agpart (If I remember correctly) needs to be selected during kernel > > config, otherwise the compile fails. > > > > I report this because I saw in the ebuild that there are allready other checks > > about kernel options which must be selected. > > > > Thanks for these patches Jim! :-) > > >
(In reply to comment #11) Hi. Here's is what Xorg log outputs when I run xrandr -o left (I then get a totally black screen and have to reboot via ssh): (II) PSB(0): Debug: psbLVDSDetect 1 (II) PSB(0): Debug: psbGetLidStatus lidState= 0 (II) PSB(0): Debug: psbLVDSGetModes (II) PSB(0): EDID vendor "CMO", prod id 777 (II) PSB(0): Printing DDC gathered Modelines: (II) PSB(0): Modeline "1024x600"x0.0 45.00 1024 1077 1112 1200 600 603 609 625 -hsync -vsync (37.5 kHz) (II) PSB(0): Debug: psbLVDSSetProperty (II) PSB(0): EDID vendor "CMO", prod id 777 (II) PSB(0): Debug: psbLVDSModeValid (II) PSB(0): Debug: xxi830_sdvo_detect 1 (II) PSB(0): Debug: SDVO: W: 0E (i830_SDVO_CMD_GET_ACTIVE_HOT_PLUG) (II) PSB(0): SDVO: R: 00 00 (Not supported) (II) PSB(0): Debug: SDVO: W: 0D 01 00 (i830_SDVO_CMD_SET_ACTIVE_HOT_PLUG) (II) PSB(0): Debug: SDVO: W: 0E (i830_SDVO_CMD_GET_ACTIVE_HOT_PLUG) (II) PSB(0): Debug: xxi830_sdvo_dpms 0, active_outputs=0 (II) PSB(0): Debug: SDVO: W: 03 (i830_SDVO_CMD_GET_TRAINED_INPUTS) (II) PSB(0): SDVO: R: 00 (Success) (EE) PSB(0): First SDVO output reported failure to sync or input is not trainded!!! (II) PSB(0): Debug: SDVO: W: 05 00 00 (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) (II) PSB(0): SDVO: R: (Success) (II) PSB(0): Debug: SDVO: W: 02 (i830_SDVO_CMD_GET_DEVICE_CAPS) (II) PSB(0): SDVO: R: 02 42 02 01 01 3D 3E 00 (Success) (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Success) (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Success) (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Success) (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Success) (II) PSB(0): Debug: SDVO: W: 0B (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Pending) (II) PSB(0): SDVO: R: 00 00 (Success) (II) PSB(0): Debug: xxi830_sdvo_dpms 3, active_outputs=0 (II) PSB(0): Debug: SDVO: W: 05 00 00 (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) (II) PSB(0): SDVO: R: (Success) (II) PSB(0): Debug: psbLVDSDPMS (II) Debug: PanelPower Status = 0xc0000008 (II) Debug: Pipe B PLL 0xd8047200 (II) Debug: Pipe B Enabled 0x80000000 (II) PSB(0): Debug: BLCType=2 Backlightg level = 0 (II) PSB(0): Debug: xxi830_sdvo_dpms 3, active_outputs=0 (II) PSB(0): Debug: SDVO: W: 05 00 00 (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) (II) PSB(0): SDVO: R: (Success) (II) PSB(0): Debug: xxi830_psbCrtcDpms pipe 0 (II) PSB(0): Debug: Crtc DPMS Off Backtrace: 0: /usr/bin/X (xorg_backtrace+0x37) [0x80e7c07] Segmentation fault at address 0x20 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at "/var/log/Xorg.0.log" for additional information. (II) UnloadModule: "mouse" (II) UnloadModule: "kbd" (II) AIGLX: Suspending AIGLX clients for VT switch (II) PSB(0): Debug: psbLeaveVT (II) PSB(0): Debug: i830_psbCrtcSaveCursors (II) PSB(0): Debug: i830_psbCrtcHWCursorSave (II) PSB(0): Debug: i830_psbCrtcHWCursorSave (II) Debug: psbScanoutDestroy (II) PSB(0): Debug: PsbDRIUpdateScanouts (II) Debug: psbRestoreHWState (II) PSB(0): Debug: i830_psbOutputDPMS (II) PSB(0): Debug: psbLVDSDPMS (II) Debug: PanelPower Status = 0x48000001 (II) Debug: Pipe B PLL 0xd8047200 (II) Debug: Pipe B Enabled 0x80000000 (II) PSB(0): Debug: BLCType=2 Backlightg level = 0 (II) PSB(0): Debug: xxi830_sdvo_dpms 3, active_outputs=0 (II) PSB(0): Debug: SDVO: W: 05 00 00 (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) (II) PSB(0): SDVO: R: (Success) (II) PSB(0): Debug: xxi830_psbCrtcDpms pipe 0 (II) PSB(0): Debug: Crtc DPMS Off > Jim, > Thanks for all your hard work on this. I bought my T91 last week and since > then it has been a whirlwind of disappointment in discovering just how bad > these gma500/poulsbo drivers are! It > seems that one of the big problems is that they only work in certain pristine > environments, i.e., > with a certain X version and a certain kernel. What might be useful is that > you post as well your > kernel .config and version and your xorg.conf and version when you post the > updated ebuild. > > At the moment, I got it to work in 2.6.36.1 and 1.7.7. It is slightly less > responsive than the uvesafb + 915resolution (+gma500 patch) + fbdev route that > also works. Do you feel that way too, or is this something wrong on my end? I > would also like to know if xrandr -o right causes a segfault for you or not. > (As to my mplayer problem, there appears to be an mplayer workaround I haven't > yet looked into.) > > (In reply to comment #9) > > Rob, > > > > Thanks for the list of missing symbols, this helps. I will post an updated > > ebuild, hopefully by the end of this weekend. If it helps anyone, I have > > tested with genkernel (along with my own kernel), which should "just work". > > > > (In reply to comment #4) > > > Hi, > > > > > > For what it's worth, I can report a successful compile with this ebuild. > > > linux-2.6.26-gentoo-r1 > > > > > > Not sure if this is the correct place to report this, but I have a few more > > > kernel requirements these modules needs: > > > > > > drm-psb.ko needs unknown symbol acpi_evaluate_object > > > psb.ko needs unknown symbol i2c_bit_add_bus > > > psb.ko needs unknown symbol acpi_evaluate_object > > > > > > I've got the above messages during compile with a customized kernel. > > > > > > Also agpart (If I remember correctly) needs to be selected during kernel > > > config, otherwise the compile fails. > > > > > > I report this because I saw in the ebuild that there are allready other checks > > > about kernel options which must be selected. > > > > > > Thanks for these patches Jim! :-) > > > > > >
Created attachment 256051 [details] updated ebuild
Created attachment 256053 [details, diff] patch for randr -o right etc
(In reply to comment #12) FIXED the randr problem. https://bugs.launchpad.net/gma500/+bug/586304 I uploaded an updated ebuild and the patch. > (In reply to comment #11) > > Hi. Here's is what Xorg log outputs when I run xrandr -o left (I then get a > totally black screen and have to reboot via ssh): > > (II) PSB(0): Debug: psbLVDSDetect 1 > (II) PSB(0): Debug: psbGetLidStatus lidState= 0 > (II) PSB(0): Debug: psbLVDSGetModes > (II) PSB(0): EDID vendor "CMO", prod id 777 > (II) PSB(0): Printing DDC gathered Modelines: > (II) PSB(0): Modeline "1024x600"x0.0 45.00 1024 1077 1112 1200 600 603 609 > 625 -hsync -vsync (37.5 kHz) > (II) PSB(0): Debug: psbLVDSSetProperty > (II) PSB(0): EDID vendor "CMO", prod id 777 > (II) PSB(0): Debug: psbLVDSModeValid > (II) PSB(0): Debug: xxi830_sdvo_detect 1 > (II) PSB(0): Debug: SDVO: W: 0E > (i830_SDVO_CMD_GET_ACTIVE_HOT_PLUG) > (II) PSB(0): SDVO: R: 00 00 (Not supported) > (II) PSB(0): Debug: SDVO: W: 0D 01 00 > (i830_SDVO_CMD_SET_ACTIVE_HOT_PLUG) > (II) PSB(0): Debug: SDVO: W: 0E > (i830_SDVO_CMD_GET_ACTIVE_HOT_PLUG) > (II) PSB(0): Debug: xxi830_sdvo_dpms 0, active_outputs=0 > (II) PSB(0): Debug: SDVO: W: 03 > (i830_SDVO_CMD_GET_TRAINED_INPUTS) > (II) PSB(0): SDVO: R: 00 (Success) > (EE) PSB(0): First SDVO output reported failure to sync or input is not > trainded!!! > (II) PSB(0): Debug: SDVO: W: 05 00 00 > (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) > (II) PSB(0): SDVO: R: (Success) > (II) PSB(0): Debug: SDVO: W: 02 > (i830_SDVO_CMD_GET_DEVICE_CAPS) > (II) PSB(0): SDVO: R: 02 42 02 01 01 3D 3E 00 (Success) > (II) PSB(0): Debug: SDVO: W: 0B > (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Success) > (II) PSB(0): Debug: SDVO: W: 0B > (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Success) > (II) PSB(0): Debug: SDVO: W: 0B > (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Success) > (II) PSB(0): Debug: SDVO: W: 0B > (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Success) > (II) PSB(0): Debug: SDVO: W: 0B > (i830_SDVO_CMD_GET_ATTACHED_DISPLAYS) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Pending) > (II) PSB(0): SDVO: R: 00 00 (Success) > (II) PSB(0): Debug: xxi830_sdvo_dpms 3, active_outputs=0 > (II) PSB(0): Debug: SDVO: W: 05 00 00 > (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) > (II) PSB(0): SDVO: R: (Success) > (II) PSB(0): Debug: psbLVDSDPMS > (II) Debug: PanelPower Status = 0xc0000008 > (II) Debug: Pipe B PLL 0xd8047200 > (II) Debug: Pipe B Enabled 0x80000000 > (II) PSB(0): Debug: BLCType=2 Backlightg level = 0 > (II) PSB(0): Debug: xxi830_sdvo_dpms 3, active_outputs=0 > (II) PSB(0): Debug: SDVO: W: 05 00 00 > (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) > (II) PSB(0): SDVO: R: (Success) > (II) PSB(0): Debug: xxi830_psbCrtcDpms pipe 0 > (II) PSB(0): Debug: Crtc DPMS Off > > Backtrace: > 0: /usr/bin/X (xorg_backtrace+0x37) [0x80e7c07] > Segmentation fault at address 0x20 > > Fatal server error: > Caught signal 11 (Segmentation fault). Server aborting > > > Please consult the The X.Org Foundation support > at http://wiki.x.org > for help. > Please also check the log file at "/var/log/Xorg.0.log" for additional > information. > > (II) UnloadModule: "mouse" > (II) UnloadModule: "kbd" > (II) AIGLX: Suspending AIGLX clients for VT switch > (II) PSB(0): Debug: psbLeaveVT > (II) PSB(0): Debug: i830_psbCrtcSaveCursors > (II) PSB(0): Debug: i830_psbCrtcHWCursorSave > (II) PSB(0): Debug: i830_psbCrtcHWCursorSave > (II) Debug: psbScanoutDestroy > (II) PSB(0): Debug: PsbDRIUpdateScanouts > (II) Debug: psbRestoreHWState > (II) PSB(0): Debug: i830_psbOutputDPMS > (II) PSB(0): Debug: psbLVDSDPMS > (II) Debug: PanelPower Status = 0x48000001 > (II) Debug: Pipe B PLL 0xd8047200 > (II) Debug: Pipe B Enabled 0x80000000 > (II) PSB(0): Debug: BLCType=2 Backlightg level = 0 > (II) PSB(0): Debug: xxi830_sdvo_dpms 3, active_outputs=0 > (II) PSB(0): Debug: SDVO: W: 05 00 00 > (i830_SDVO_CMD_SET_ACTIVE_OUTPUTS) > (II) PSB(0): SDVO: R: (Success) > (II) PSB(0): Debug: xxi830_psbCrtcDpms pipe 0 > (II) PSB(0): Debug: Crtc DPMS Off > > > > Jim, > > Thanks for all your hard work on this. I bought my T91 last week and since > > then it has been a whirlwind of disappointment in discovering just how bad > > these gma500/poulsbo drivers are! It > > seems that one of the big problems is that they only work in certain pristine > > environments, i.e., > > with a certain X version and a certain kernel. What might be useful is that > > you post as well your > > kernel .config and version and your xorg.conf and version when you post the > > updated ebuild. > > > > At the moment, I got it to work in 2.6.36.1 and 1.7.7. It is slightly less > > responsive than the uvesafb + 915resolution (+gma500 patch) + fbdev route that > > also works. Do you feel that way too, or is this something wrong on my end? I > > would also like to know if xrandr -o right causes a segfault for you or not. > > (As to my mplayer problem, there appears to be an mplayer workaround I haven't > > yet looked into.) > > > > (In reply to comment #9) > > > Rob, > > > > > > Thanks for the list of missing symbols, this helps. I will post an updated > > > ebuild, hopefully by the end of this weekend. If it helps anyone, I have > > > tested with genkernel (along with my own kernel), which should "just work". > > > > > > (In reply to comment #4) > > > > Hi, > > > > > > > > For what it's worth, I can report a successful compile with this ebuild. > > > > linux-2.6.26-gentoo-r1 > > > > > > > > Not sure if this is the correct place to report this, but I have a few more > > > > kernel requirements these modules needs: > > > > > > > > drm-psb.ko needs unknown symbol acpi_evaluate_object > > > > psb.ko needs unknown symbol i2c_bit_add_bus > > > > psb.ko needs unknown symbol acpi_evaluate_object > > > > > > > > I've got the above messages during compile with a customized kernel. > > > > > > > > Also agpart (If I remember correctly) needs to be selected during kernel > > > > config, otherwise the compile fails. > > > > > > > > I report this because I saw in the ebuild that there are allready other checks > > > > about kernel options which must be selected. > > > > > > > > Thanks for these patches Jim! :-) > > > > > > > > > >
*** Bug 351382 has been marked as a duplicate of this bug. ***
As I am using gentoo-sources-2.6.37 I opened a new bug 353514 as the psb-kmod does not compile there. I downgraded to gentoo-sources-2.6.36-r15 and get the same errors. What could be wrong here? Do I have to use vanilla-sources?
(In reply to comment #17) > As I am using gentoo-sources-2.6.37 I opened a new bug 353514 as the psb-kmod > does not compile there. I downgraded to gentoo-sources-2.6.36-r15 and get the > same errors. What could be wrong here? Do I have to use vanilla-sources? > It was 2.6.35-r7, of course. I am now downgrading to 2.6.35, and hope that the other hardware in my laptop still wok with that.
Almost two month later. Is there any chance, that psb-kmod will compile with a current kernel? Now we have gentoo-sources-2.6.38-r1.
(In reply to comment #19) > Almost two month later. Is there any chance, that psb-kmod will compile with a > current kernel? Now we have gentoo-sources-2.6.38-r1. I have submitted an updated ebuild and a patch in Bug 353514 - it compiles against 2.6.37. But I do not have a GMA500 chipset to test it. However, Peter John Hartman wrote in Bug 274184 comment 53, that there is a new advance on the Poulsbo at launchpad.net/emgd. It is said to be a much better approach than psb-kmod.
People should move to CONFIG_STUB_POULSBO: http://forums.gentoo.org/viewtopic-t-911332-start-0.html
dropped
