The CONFIG_PM is on by default, my patch and updated ebuild turns this off and it compiles nicly on 2.6.11. Reproducible: Always Steps to Reproduce: 1. emerge intel-536ep on kernel >=2.6.9 Actual Results: the module had errors... Expected Results: compile fine
Created attachment 53416 [details] Updated ebuild
Created attachment 53417 [details, diff] Patch-file!
Okey here it is, the final frontier... This patch and ebuild solves the PM-probs!
Reopened for assignment
Reassigned bug to net-dialup@gentoo.org.
What errors? On my 2.6.10 it builds without errors. It has some warnings though, but are not related to CONFIG_PM.
/root/intel-536EP-2.56.76.0/coredrv/coredrv.c:295: error: `PM_SAVE_STATE' undeclared (first use in this function) and when I comment PM_SAVE_STATE-case out it yells about this: *** Warning: "pm_access" [/root/intel-536EP-2.56.76.0/coredrv/Intel536.ko] undefined! So by not using PM this problem is solved.
please comment the PM_SAVE_STATE case. also, you should comment the pm_access call.
Well, I will not... It's THE ugliest way to solve this problem. It's way more correct to #undef CONFIG_PM to avoid future compability issues with the power management in linux.
the ugliest way will be to remove support for power management. judging after changes suffered by power management I could say that: a) pm_access does not exist in 2.6.11. However, in previous versions it was an empty function anyway. b) PM_SAVE_STATE define has vanished, but this module did nothing but logging a message saying it doesn't support this. either you test what I tell you to or I will mark this as CANTFIX, since you refuse to do it and I don't have the hardware. btw, you should post patches as minimal as possible and with correct mime type.
Oki... I'll try... Btw I had a great problem making the patch (i.e. diff -Naur'). Thanks for investigating this futher.
Created attachment 53526 [details, diff] New patch, patching the PM_SAVE_STATEMENT & pm_access-function
Changed from 2.6.9->2.6.11
fixed in the same version, since compilation failed on affected systems. if I've screwed up something, please reopen this bug. thanks for your support.
I verified it with 'emerge portage', worked out of the box.
Closed it
'emerge intel-536ep' of course