Ah, no fun with games tonight. I got myself a cheap 802.11B wireless card from Trendnet, TEW-223PI. I bought it on the strength of a page they had saying they had drivers. Oh, they do, if you run Red Hat 7.3 or 8.0 and have one of their normal kernels. It seems as though the chipset maker ADMtec made a driver, sort of and that's what I got from the Trendnet site. It includes a half source distribution too, that has a private module that gets linked. This aproach also makes Belkin junk work and anyone with a wireless card that does not work might check out this clueful howto:
http://www.houseofcraig.net/belkin_howto.php The object file, ADM_Prv.o and all the ^Ms in the read me file make me a little nervous, but my problems are more basic than that. I'm not bright enough to figure out kernel compiling. I followed the directions, got kernel source, modified a c source file that had a problem but get an error when I try to load what pops out: refuse:/home/willhill/ADM8211# insmod 8211 Using /lib/modules/2.4.16-k6/kernel/drivers/net/wireless/8211.o /lib/modules/2.4.16-k6/kernel/drivers/net/wireless/8211.o: kernel-module version mismatch /lib/modules/2.4.16-k6/kernel/drivers/net/wireless/8211.o was compiled for kernel version 2.4.18 while this kernel is version 2.4.16-k6 Ugh, make me feel like an idiot. I specified march=k6, and my kernel source is 2.4.16. I've got no idea where it's getting 2.4.18. It does not show up in the card source, nor do I find it in the kernel source. Here's the card's Makefile: /**************************************snip************************************/ CC = gcc FLAG = -D__KERNEL__ -DMODULE -Wall -Wstrict-prototypes -O2 -I/usr/src/linux-2.4/include -fomit-frame-pointer -fno-strict-aliasing -Wno-trigraphs -fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 all: 8211.o 8211.o : adm8201.o ADM_Prv.o $(LD) -r $^ -o $@ adm8201.o: adm8201.c $(CC) $(FLAG) -c adm8201.c clean: rm -f 8211.o adm8201.o /**************************************end snip********************************/ insmod -f crams it in with justified warnings of tainting, but does not get it used and restarting the network does not seem to help either. The device does show up under /proc/pci and in lspci, but I'm starting to feel stumped. If this had worked, I'd be happy by now. Then I could be playing with FreeDOS. On 2003.07.30 19:45 John Hebert wrote: > Finally, something on topic. ;) > > FreeDOS is neat, though still a little rough around the edges. I installed > it to play Harpoon II but had some problems with it, since Harpoon II uses > its own memory manager. It even has its own bootloader that is apparently > configurable. > > What would be really cool is a tool that spits out bootable CDs from a drive > partition with FreeDOS and some installed game, or maybe a slew of em. Hmmm, > this is doable... > > --
