"Steven C. Darnold" wrote: > Robert Steinmetz wrote: > > > > I was able to ultimately get an older version of PCMCIA-CS > > to compile, but more recent versions still fail. I was able > > to get an orinoco based wireless card to work but with > > limited functionality (no encryption). More current versions > > of PCMCIA-CS don't compile. > > It is possible that the source code uses a glibc2 capability > that is not available in libc5. This is not uncommon. > It is much easier to use current versions of software when > you have the current libraries. On several occasions I have > investigated updating the BasicLinux libraries, but the size > increase is so alarming that it scares me off. >
I think that is a good possibility. I have already installed the glib packages from Slackware 3.5. I agree I don't want to go around adding a bunch of extra stuff. I probably have enough hard disk space on the machine I'm using to install a more current release together with some packages, but I'm concerned about performance. I am now attempting to update the wireless extensions in the kernel to v6 see if that's where the problem is. I need to get to v10 to be able to compile current drivers anyway. I built a new kernel yesterday with updated extensions (v6) from Slackware 4.0 but haven't tested it yet. The PCMCIA-CS maintainer says that package is no longer tested against 2.0.x kernels much, although he thinks 2.0.39 should work but no Slackware version seems to have been based upon that kernel ( 4.0 is 2.0.37, 7.0 is 2.2.?). I was able to get 3.1.15 version to compile on BasicLinux but I need to get to about 3.1.29 to get the drivers I need. Have you considered a special version of BasicLinux for old notebooks? You could strip out most support for network cards, enable PCMCIA ( I know its already enabled ) and wireless extensions, since very few old notebooks don't have built in networking and use PCMCIA-CS for networking. The kernel I built doing that is a little smaller than the stock BasicLinux kernel, although I may have cut out some other stuff as well. -- Rob Steinmetz To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with unsubscribe SURVPC in the body of the message. Also, trim this footer from any quoted replies. More info can be found at; http://www.softcon.com/archives/SURVPC.html
