Hi
I am looking for the Asus Eeepc Poulsbo (psb) driver in Kernel
2.6.32-rc7. When is this driver expected to make it into the kernel?
At the moment I am getting following error:
CC [M] /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.o
CC [M] /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_bo.o
/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:
In function 'drm_ttm_ipi_handler':
/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:35:
error: implicit declaration of function 'flush_agp_cache'
/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:
In function 'drm_set_caching':
/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:116:
error: implicit declaration of function 'map_page_into_agp'
/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:118:
error: implicit declaration of function 'unmap_page_from_agp'
make[2]: *** [/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.o]
Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [_module_/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1]
Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.32-rc7'
make: *** [modules] Error 2
* ERROR: x11-drivers/psb-kmod-4.41.1_p10 failed:
* (no error message)
*
* Call stack:
* ebuild.sh, line 49: Called src_compile
* environment, line 3471: Called die
* The specific snippet of code:
* LINUXDIR=/usr/src/linux emake DRM_MODULES=psb || die
*
When trying to use the driver from:
http://www.happyassassin.net/2009/09/26/gma-500-poulsbo-driver-for-fedora-11-soon-to-be-in-rpm-fusion/comment-page-1/#comment-1005
I would prefer to install the driver directly from the kernel.
Thank you for your Feedback.
Let me know if you need my .config.
Best
Zeno
Op 19-11-09 09:52, Zeno Davatz schreef:
> Hi
>
> I am looking for the Asus Eeepc Poulsbo (psb) driver in Kernel
> 2.6.32-rc7. When is this driver expected to make it into the kernel?
>
> At the moment I am getting following error:
>
> CC [M] /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.o
> CC [M] /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_bo.o
> /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:
> In function 'drm_ttm_ipi_handler':
> /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:35:
> error: implicit declaration of function 'flush_agp_cache'
> /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:
> In function 'drm_set_caching':
> /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:116:
> error: implicit declaration of function 'map_page_into_agp'
> /var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.c:118:
> error: implicit declaration of function 'unmap_page_from_agp'
> make[2]: *** [/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1/drm_ttm.o]
> Error 1
> make[2]: *** Waiting for unfinished jobs....
> make[1]: *** [_module_/var/tmp/portage/x11-drivers/psb-kmod-4.41.1_p10/work/psb-kernel-source-4.41.1]
> Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.32-rc7'
> make: *** [modules] Error 2
Hi,
I'd also be interested by a patch to get the psb kernel module to
compile with 2.6.32. If anyone has this already available, please post it!
Or maybe someone knows what should be done to fix this type of errors?
Thanks,
Eric
Op 19-11-09 15:28, ?ric Piel schreef:
> Op 19-11-09 09:52, Zeno Davatz schreef:
>> Hi
>>
>> I am looking for the Asus Eeepc Poulsbo (psb) driver in Kernel
>> 2.6.32-rc7. When is this driver expected to make it into the kernel?
:
> Hi,
> I'd also be interested by a patch to get the psb kernel module to
> compile with 2.6.32. If anyone has this already available, please post it!
> Or maybe someone knows what should be done to fix this type of errors?
Hello,
I've just noticed that Zac Medico has written the fixes (as sed scripts)
for the psb driver in gentoo. Below is the patch version of his fixes.
It works for me :-)
Thanks Zac!
See you,
Eric
8<--------------------------------------------------
psb: Fix compilation with kernel 2.6.32
This patch made from the Gentoo ebuild written by Zac Medico <[email protected]>,
to fix compilation of the psb module with kernel 2.6.32
It should be safe to be used with older version of the kernel. It fixes two changes:
* In commit 6a12235c7d2d75c7d94b9afcaaecd422ff845ce0 phys_to_gart was removed
since it is a 1:1 mapping on all platforms.
* The acpi PREFIX constant is gone.
---
diff -urP psb-4.41.1-4mdv2010.0.orig/drm_agpsupport.c psb-4.41.1-4mdv2010.0.fix2632/drm_agpsupport.c
--- psb-4.41.1-4mdv2010.0.orig/drm_agpsupport.c 2009-10-08 12:09:11.000000000 +0200
+++ psb-4.41.1-4mdv2010.0.fix2632/drm_agpsupport.c 2009-12-05 02:46:28.000421027 +0100
@@ -524,7 +524,7 @@
DRM_DEBUG("Current page count is %ld\n", (long) mem->page_count);
mem->page_count = 0;
for (cur_page = pages; cur_page < last_page; ++cur_page)
- mem->pages[mem->page_count++] = phys_to_gart(page_to_phys(*cur_page));
+ mem->pages[mem->page_count++] = page_to_phys(*cur_page);
agp_be->mem = mem;
return 0;
}
diff -urP psb-4.41.1-4mdv2010.0.orig/drm_edid.c psb-4.41.1-4mdv2010.0.fix2632/drm_edid.c
--- psb-4.41.1-4mdv2010.0.orig/drm_edid.c 2009-10-08 12:09:11.000000000 +0200
+++ psb-4.41.1-4mdv2010.0.fix2632/drm_edid.c 2009-12-05 02:46:38.155168734 +0100
@@ -39,7 +39,7 @@
if (obj && obj->type == ACPI_TYPE_BUFFER)
memcpy(edid, obj->buffer.pointer, obj->buffer.length);
else {
- printk(KERN_ERR PREFIX "Invalid _DDC data\n");
+ printk(KERN_ERR "ACPI: " "Invalid _DDC data\n");
status = -EFAULT;
kfree(obj);
}
On Sat, Dec 5, 2009 at 1:35 PM, ?ric Piel <[email protected]> wrote:
> Op 19-11-09 15:28, ?ric Piel schreef:
>> Op 19-11-09 09:52, Zeno Davatz schreef:
>>> Hi
>>>
>>> I am looking for the Asus Eeepc Poulsbo (psb) driver in Kernel
>>> 2.6.32-rc7. When is this driver expected to make it into the kernel?
> :
>> Hi,
>> I'd also be interested by a patch to get the psb kernel module to
>> compile with 2.6.32. If anyone has this already available, please post it!
>> Or maybe someone knows what should be done to fix this type of errors?
> Hello,
>
> I've just noticed that Zac Medico has written the fixes (as sed scripts)
> for the psb driver in gentoo. Below is the patch version of his fixes.
> It works for me :-)
Ok, it does compile but when I insert the module I get:
psb: Unknown symbol i2c_bit_add_bus
I got the exact same error with 2.6.29
Best
Zeno
On Sat, Dec 5, 2009 at 1:35 PM, ?ric Piel <[email protected]> wrote:
> Op 19-11-09 15:28, ?ric Piel schreef:
>> Op 19-11-09 09:52, Zeno Davatz schreef:
>>> Hi
>>>
>>> I am looking for the Asus Eeepc Poulsbo (psb) driver in Kernel
>>> 2.6.32-rc7. When is this driver expected to make it into the kernel?
> :
>> Hi,
>> I'd also be interested by a patch to get the psb kernel module to
>> compile with 2.6.32. If anyone has this already available, please post it!
>> Or maybe someone knows what should be done to fix this type of errors?
> Hello,
>
> I've just noticed that Zac Medico has written the fixes (as sed scripts)
> for the psb driver in gentoo. Below is the patch version of his fixes.
> It works for me :-)
compiles fine. But I still get:
psb: Unknown symbol i2c_bit_add_bus
when inserting the module.
And this is my Xorg.0.log- see attachment.
Best
Zeno
Zeno Davatz wrote:
> Ok, it does compile but when I insert the module I get:
>
> psb: Unknown symbol i2c_bit_add_bus
This might solve it:
modprobe i2c_algo_bit
That module comes from CONFIG_I2C_ALGOBIT=m in your kernel config.
--
Thanks,
Zac
On Sun, Dec 6, 2009 at 5:24 PM, Zac Medico <[email protected]> wrote:
> Zeno Davatz wrote:
>> Ok, it does compile but when I insert the module I get:
>>
>> psb: Unknown symbol i2c_bit_add_bus
>
> This might solve it:
>
> ?modprobe i2c_algo_bit
>
> That module comes from CONFIG_I2C_ALGOBIT=m in your kernel config.
Yes, thanks. That helped another step. I am getting the correct screen
resolution after enabling that in the kernel as well. The boot [ok]
messages of Gentoo are in a higher resolution now though. That is a
good start.
But after my X starts I get a black screen with a
-
in the top left corner. They keyboard also does not work. May be an
X.org config problem.
Also this is in my /var/log/messages
[ 6.348077] [drm:psb_do_init] *ERROR* Debug is 0x00000000
Best
Zeno
Op 06-12-09 17:35, Zeno Davatz schreef:
:
> Yes, thanks. That helped another step. I am getting the correct screen
> resolution after enabling that in the kernel as well. The boot [ok]
> messages of Gentoo are in a higher resolution now though. That is a
> good start.
>
> But after my X starts I get a black screen with a
>
> -
>
> in the top left corner. They keyboard also does not work. May be an
> X.org config problem.
>
I've got similar behaviour here if psb is loaded before the X server
starts (aka there is a framebuffer). If the console is just ascii (no
vga=... argument on the kernel boot line, and no "modprobe psb"), then X
starts fine.
Eric
On Mon, Dec 7, 2009 at 12:05 AM, ?ric Piel <[email protected]> wrote:
> Op 06-12-09 17:35, Zeno Davatz schreef:
> :
>>
>> Yes, thanks. That helped another step. I am getting the correct screen
>> resolution after enabling that in the kernel as well. The boot [ok]
>> messages of Gentoo are in a higher resolution now though. That is a
>> good start.
>>
>> But after my X starts I get a black screen with a
>>
>> -
>>
>> in the top left corner. They keyboard also does not work. May be an
>> X.org config problem.
>>
> I've got similar behaviour here if psb is loaded before the X server starts
> (aka there is a framebuffer). If the console is just ascii (no vga=...
> argument on the kernel boot line, and no "modprobe psb"), then X starts
> fine.
When I do X -configure I also get:
X: symbol lookup error: /usr/lib/xorg/modules/drivers/psb_drv.so:
undefined symbol: LoaderRefSymLists
Let me know if you need any other info.
I will now try Eric's version from above.
Best
Zeno
On Mon, Dec 7, 2009 at 12:05 AM, ?ric Piel <[email protected]> wrote:
> Op 06-12-09 17:35, Zeno Davatz schreef:
> :
>>
>> Yes, thanks. That helped another step. I am getting the correct screen
>> resolution after enabling that in the kernel as well. The boot [ok]
>> messages of Gentoo are in a higher resolution now though. That is a
>> good start.
>>
>> But after my X starts I get a black screen with a
>>
>> -
>>
>> in the top left corner. They keyboard also does not work. May be an
>> X.org config problem.
>>
> I've got similar behaviour here if psb is loaded before the X server starts
> (aka there is a framebuffer). If the console is just ascii (no vga=...
> argument on the kernel boot line, and no "modprobe psb"), then X starts
> fine.
What are the exact options that you are using for "no vga"?
My terminal seems to automatically load "psb". I have no modprobe
loading "psb" explicitly.
Best
Zeno
Op 07-12-09 10:43, Zeno Davatz schreef:
> On Mon, Dec 7, 2009 at 12:05 AM, ?ric Piel <[email protected]> wrote:
>> Op 06-12-09 17:35, Zeno Davatz schreef:
>> :
>>> Yes, thanks. That helped another step. I am getting the correct screen
>>> resolution after enabling that in the kernel as well. The boot [ok]
>>> messages of Gentoo are in a higher resolution now though. That is a
>>> good start.
>>>
>>> But after my X starts I get a black screen with a
>>>
>>> -
>>>
>>> in the top left corner. They keyboard also does not work. May be an
>>> X.org config problem.
>>>
>> I've got similar behaviour here if psb is loaded before the X server starts
>> (aka there is a framebuffer). If the console is just ascii (no vga=...
>> argument on the kernel boot line, and no "modprobe psb"), then X starts
>> fine.
>
> What are the exact options that you are using for "no vga"?
>
> My terminal seems to automatically load "psb". I have no modprobe
> loading "psb" explicitly.
>
Well, I don't know exactly how it works, probably it's part of the
initrd. Here, on Mandriva, if I remove the "vga" argument, it
automatically stays in ascii mode.
You could use lsinitrd to check your initrd.
Eric
On Mon, Dec 7, 2009 at 10:51 AM, ?ric Piel <[email protected]> wrote:
> Op 07-12-09 10:43, Zeno Davatz schreef:
>> On Mon, Dec 7, 2009 at 12:05 AM, ?ric Piel <[email protected]> wrote:
>>> Op 06-12-09 17:35, Zeno Davatz schreef:
>>> :
>>>> Yes, thanks. That helped another step. I am getting the correct screen
>>>> resolution after enabling that in the kernel as well. The boot [ok]
>>>> messages of Gentoo are in a higher resolution now though. That is a
>>>> good start.
>>>>
>>>> But after my X starts I get a black screen with a
>>>>
>>>> -
>>>>
>>>> in the top left corner. They keyboard also does not work. May be an
>>>> X.org config problem.
>>>>
>>> I've got similar behaviour here if psb is loaded before the X server starts
>>> (aka there is a framebuffer). If the console is just ascii (no vga=...
>>> argument on the kernel boot line, and no "modprobe psb"), then X starts
>>> fine.
>>
>> What are the exact options that you are using for "no vga"?
>>
>> My terminal seems to automatically load "psb". I have no modprobe
>> loading "psb" explicitly.
>>
> Well, I don't know exactly how it works, probably it's part of the
> initrd. Here, on Mandriva, if I remove the "vga" argument, it
> automatically stays in ascii mode.
Not the same on Gentoo. I think I have to find the kernel boot-option
that I can pass to lilo.
Also: When I force remove the modules psb and drm_psb with "rmmod -f"
and then start X I get the same error:
X: symbol lookup error: /usr/lib/xorg/modules/drivers/psb_drv.so:
undefined symbol: LoaderRefSymLists
X just does not yet like psb.
;)
Best
Zeno
On Thu, 2009-11-19 at 09:52 +0100, Zeno Davatz wrote:
> When is this driver expected to make it into the kernel?
When they open-source the driver.
Op 07-12-09 11:02, Zeno Davatz schreef:
:
> Not the same on Gentoo. I think I have to find the kernel boot-option
> that I can pass to lilo.
>
> Also: When I force remove the modules psb and drm_psb with "rmmod -f"
> and then start X I get the same error:
>
> X: symbol lookup error: /usr/lib/xorg/modules/drivers/psb_drv.so:
> undefined symbol: LoaderRefSymLists
>
> X just does not yet like psb.
You are also aware that it does not work on Xserver 1.7, right? 1.6 is
the the maximum.
See you
Eric
On Mon, Dec 7, 2009 at 11:09 AM, ?ric Piel <[email protected]> wrote:
> Op 07-12-09 11:02, Zeno Davatz schreef:
> :
>> Not the same on Gentoo. I think I have to find the kernel boot-option
>> that I can pass to lilo.
>>
>> Also: When I force remove the modules psb and drm_psb with "rmmod -f"
>> and then start X I get the same error:
>>
>> X: symbol lookup error: /usr/lib/xorg/modules/drivers/psb_drv.so:
>> undefined symbol: LoaderRefSymLists
>>
>> X just does not yet like psb.
> You are also aware that it does not work on Xserver 1.7, right? 1.6 is
> the the maximum.
Thanks. I thought it should work with 1.7 as well. Will try that then.
Best
Zeno