I remember having similar problem with that Intel536ep module.
Be sure to have the gcc-3.2 compiler installed as the 536EP corecode is compiled with this version : from the "readme.txt" in the 536EP tarball :
"2. Release Notes
This release supports 2.4.x kernels.
This release is not compatible with kernels prior to 2.4.
The 536EP corecode binary was compiled with gcc version 3.2"
this is what I have installed on my testing/sid with 2.4.22 kernel :
hi gcc 3.3.1-2 The GNU C compiler. hi gcc-3.2 3.2.3-8 The GNU C compiler hi gcc-3.2-base 3.2.3-8 The GNU Compiler Collection (base package) hi gcc-3.3 3.3.2-0pre5 The GNU C compiler hi gcc-3.3-base 3.3.2-0pre5 The GNU Compiler Collection (base package)
I have also the complete source of the kernel installed. Also remember to recompile the module after each kernel compile.
OK - I'll give it a go (tho' last time I ventured into testing I wound up having to re-install my system from scratch - a bunch of stuff was upgraded that I didn't want upgraded, masses of dependancies were broken etc.)
I do have gcc-3.0 installed - wonder if that would work?
So - how do I set 3.0 (or 3.2) as the default (it's currently 2.95)?
Thanks.
-- All the best
Steve.
---
Athlon XP 2400, Nvidia GeForce 4 AGP, ASRock SiS MB/Souncard, ESP 830 Running Debian Woody 3.0r2, 2.4.24 kernel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
