Summary: | madwifi-ng-0.9.2.1 compile fail with kernel 2.6.20 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Bainbridge (RETIRED) <chrb> |
Component: | New packages | Assignee: | Steev Klimaszewski (RETIRED) <steev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | daniel, dsd, ikelos, Sander.Sweers |
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 163825 | ||
Attachments: |
patch
An updated madwifi-ng-0.9.2.1-linux-2.6.20.patch |
Description
Chris Bainbridge (RETIRED)
2007-02-05 13:53:53 UTC
Created attachment 109247 [details, diff]
patch
taken from various upstream commits
I tried the attached patch, compiles ok, but runtime fails: ath_hal: module license 'Proprietary' taints kernel. ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) wlan: 0.8.4.2 (0.9.2.1) ath_rate_sample: 1.2 (0.9.2.1) ath_pci: 0.9.4.5 (0.9.2.1) ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 wifi%d: unable to attach hardware: '' (HAL status 4171240159) works for me maybe try current madwifi-ng svn trunk? Compilation works for me but after insmodding ath_pci i get a kernel Oops when insmodding i915 driver. This is probably related to new workqueue API: http://madwifi.org/changeset/1891 Your problem is not related to that changeset, as it is included in my patch. If you have problems, the next thing to try is to reproduce it on madwifi svn trunk. Following the thread here http://madwifi.org/ticket/1048 it looks as thought the binary call interface changed so the regparam option to gcc needs fixing as well. I'll try todays svn snapshot as well. Todays svn r2083 compiles and runs fine, so maybe it would be better to release a version bump than a backported patch. Created attachment 109671 [details, diff] An updated madwifi-ng-0.9.2.1-linux-2.6.20.patch I've also been having the "unable to attach hardware" problem. It appears this was fixed in r1890 (http://madwifi.org/changeset/1890). Attached is an updated madwifi-ng-0.9.2.1-linux-2.6.20.patch which features this extra fix, and seems to solve the problem... Ok, I just pushed this to the tree, please give it a couple of hours and then try re-emerging madwifi-ng. If you're still experiencing the "unable to attach hardware" problem, feel free to reopen the bug... 5:) |