The kernel module 3w-xxxx don`t see my 3ware 7500 card on 2.6.16.20 kernel with applied grsecurity-2.1.9-2.6.16.19-200606041421.patch
Is it a known issue?
Dr_Napalm wrote:I have a Asus P4G8X (i865) with a 3Ware/AMCC 7xxx running right now without any problems detecting the card.
Whats your hardware exactly? Maybe wrong .config?
i think it's not your hw but a bug in PaX that i ran across as well when i disabled NOEXEC, i'm still debugging it. in the meantime enabling NOEXEC options should get your machine to work.flagman wrote:Now my mashine runs on 2.6.14.3 + grsec 2.1.8 patch without problems, .config for 2.6.16.20 is identical with current kernel that works.
PaX Team wrote:i think it's not your hw but a bug in PaX that i ran across as well when i disabled NOEXEC, i'm still debugging it. in the meantime enabling NOEXEC options should get your machine to work.flagman wrote:Now my mashine runs on 2.6.14.3 + grsec 2.1.8 patch without problems, .config for 2.6.16.20 is identical with current kernel that works.
i fixed this in the meantime at least.PaX Team wrote:i think it's not your hw but a bug in PaX that i ran across as well when i disabled NOEXEC, i'm still debugging it. in the meantime enabling NOEXEC options should get your machine to work.
what errors are you getting? any PaX logs maybe?flagman wrote:I can`t enable NOEXEC because my apache with PHP won`t work with it.
PaX Team wrote:what errors are you getting? any PaX logs maybe?flagman wrote:I can`t enable NOEXEC because my apache with PHP won`t work with it.
This will also break programs that rely on the old behaviour and
expect that dynamically allocated memory via the malloc() family
of functions is executable (which it is not). Notable examples
are the XFree86 4.x server, the java runtime and wine.