Summary: | net-misc/zaptel-1.0.10-r1 - Error inserting zaphfc after upgrading gcc to 4.1.1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kent B. Hansen <kent> |
Component: | New packages | Assignee: | Rajiv Aaron Manglani (RETIRED) <rajiv> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | stkn |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log
emerge --info |
Description
Kent B. Hansen
2006-09-04 11:09:55 UTC
Created attachment 95986 [details]
Build log
Created attachment 95987 [details]
emerge --info
Sorry, this was not a gcc issue, but an 'unsupported' kernel version I guess. After downgrading to kernel 2.6.16.19 from 2.6.17.6 it compiles just fine... -Kent I'm reopening the bug. zaptel is compiling fine, but the resulting module can't be inserted: # modprobe zaphfc FATAL: Error inserting zaphfc (/lib/modules/2.6.16.19/misc/zaphfc.ko): Invalid argument In /var/log/messages the following is listed: "zaphfc: falsely claims to have parameter modes" # modinfo zaphfc filename: /lib/modules/2.6.16.19/misc/zaphfc.ko description: HFC-S PCI A Zaptel Driver author: Klaus-Peter Junghanns <kpj@junghanns.net> license: GPL vermagic: 2.6.16.19 CYRIXIII gcc-4.1 depends: parm: debug:i parm: modes:i Both the kernel and zaptel is compiled with the same gcc (4.1.1). Same kernel and module versions didn't have problems with gcc 3.4.6. Using the newest testing release zaptel-1.2.6 seems to be working. zaptel 1.0.x is no longer supported. |