I've been sober for a couple of days now, but I've got no joy from that card.
That closed binary object probably was compiled for 2.4.18, but obliging it did not help. I swapped out my kernel and source to 2.4.18 and the insmod was a little easier. I had to change kernel_thread from int to long in my asm headers to match the kernel source, yuck. It complained that 2.4.18-X was not 2.4.18 and about tainting when forced, but loaded quicker. Still, it would not see the darn thing and the module is listed as unused despite network restarts and some use of iwconfig, another closed binary. I'm tempted to set up a red hat box. If that does not work, and no one has any other ideas, that dinky card is going back where it came from or sold to anyone who wants it. Hell, I should have sent it back when I opened the box and saw it had no antenna. On 2003.07.31 11:12 John Hebert wrote: > Friends don't let friends compile kernels drunk. ;) > > Maybe this is a dumb question, but is it the problem caused because the > closed binary ADM_Prv.o was compiled for 2.4.18? And what are you doing > running a closed binary anyway? Aren't you the token RMS apologist on this > list? Oh, wait. That's me. :) > > Why not just upgrade your kernel to 2.4.18? That should make your problem go > away. If you need help doing that, just ask. It is as simple as getting the > sources for 2.4.18 and doing the make menuconfig song and dance. > > John Hebert >
