linksys wusb11 ver 2.6

[235u at comcast.net]

chris, thanks for the info.  you brought up some stuff i didn't realize.  (like not starting in root, ./configure, ect.)  yep, i was doing what the README said to do.  i tried it your way, still didn't work.  (do i need specific drivers for specific kernels?  oh god my little brain hurts again.  i think this is too big a bone for a little dog.)  errors everywhere!  i got pissed (i've been screwing with this thing for about a month on and off) and gave it to my roomate.  tomorrow i'm going to best buy or what ever to pick up a linksys WET11, ethernet connection man, no driver needed!  wish i would've done that from the beginning.  

one more question if you don't mind;  i remember when i installed redhat 9 there was some option i picked that sounded like a "roll back" feature similar to what M$ has.  it has saved my ass a few times with M$ XtraProfit.  i'ld love to do some time traveling to bring my box back to what it was prior to me screwing around with this lame ass driver.  i looked in the docs and couldn't find a damn thing on it though.  does anybody know what i'm talking about or am i just wacko?  thanks for any help.  -eric the chronic noob.
> On Wed, 1 Oct 2003 235u at comcast.net wrote:
> 
> > [root at playPen1 root]# cd /opt/atmelwlandriver
> > [root at playPen1 atmelwlandriver]# make config
> 
> ^-- this package didn't require you to start with a `./configure`, or
> `./configure --opts` command? I'm assuming you read the README and did as
> it instructed here, but I just want to check...
> 
> > [... several `make config` lines omitted ...]
> > Finished. Now run make clean, all, install
> > [root at playPen1 atmelwlandriver]# make all
> 
> ^-- hang on, you were asked to do a `make clean` before `make all`. Did
> you try doing that? Did it help? If you didn't, but you try adding that
> step, do the results change at all?
> 
> > [... several `make all` lines omitted ...]
> > make[3]: Entering directory `/opt/atmelwlandriver/src/usb'
> > gcc -D__KERNEL__ -O3 -fno-strict-aliasing -fomit-frame-pointer -pipe         -
> > I/include -I/opt/atmelwlandriver/src/includes -
> > I/opt/atmelwlandriver/src/includes/usb -Wall  -DRFMD -DUSBDBG   -c -o
> > callbacks.o callbacks.c

> > In file included from /usr/include/linux/fs.h:23,
> >                  from /usr/include/linux/capability.h:17,
> >                  from /usr/include/linux/binfmts.h:5,
> >                  from /usr/include/linux/sched.h:9,
> >                  from /opt/atmelwlandriver/src/includes/usb/vnetusba.h:24,
> >                  from callbacks.c:22:
> > /usr/include/linux/string.h:8:2: warning: #warning Using kernel header in
> > userland!
> 
> ...and from here on you start getting these userland errors, among others.
> It looks to me like little if annything managed to finish compiling
> cleanly.
> 
> > [... many, many `make all` lines, mostly error reports, omitted ...]
> > make[3]: *** [callbacks.o] Error 1
> > make[3]: Leaving directory `/opt/atmelwlandriver/src/usb'
> > make[2]: *** [rfmdD] Error 2
> > make[2]: Leaving directory `/opt/atmelwlandriver/src/usb'
> > make[1]: *** [all] Error 1
> > make[1]: Leaving directory `/opt/atmelwlandriver/src/usb'
> > make: *** [all] Error 1

> > [root at playPen1 atmelwlandriver]# make install
> 
> Hang on, this definitely shouldn't work. In the typical
> 
>     ./configure
>     make
>     make all
>     make install
> 
> quartet (or variations of it, such as here), generally each step has to
> finish cleanly before you can move on to the next one. In this case, your
> `make all` failed, which guarantees that `make install` won't work, and
> doing that last step after a failed compilation just might make a very big
> mess if it clobbers previously stable files.
> 
> As an aside, this is part of why it's considered best to do the first
> steps of a compilation as a non-priviliged user, and only use root for
> `make install` if & only if the other steps went well. If your system has
> sudo, that would mean
> 
>     $ ./configure
>     $ make
>     $ make all
>     $ sudo make install
> 
> and if you don't have sudo, then maybe this instead:
> 
>     $ ./configure
>     $ make
>     $ make all
>     $ su -
>     # make install
> 

> If you're building software with root authority, and bad things happen,
> the damage can be much worse than if you're building the software with a
> non-priviliged account.
> 
> 
> But anyway, the main omission I see is the apparent lack of a `make clean`
> step. Running that when asked to do so might resolve this problem -- or at
> least, it certainly can't hurt to go back & add it.
> 
> It's a little hard to comment on what other changes to try without that
> happening first. It could be the case that many things change after you do
> that (old errors may go away, new ones may come up), so it seems best to
> try that, then report back to the list if things go wrong again.
> 
> Good luck! :)
> 
> 
> -- 
> Chris Devers      cdevers at pobox.com
> 
> np: 'Little Palaces'
>      by Elvis Costello (The Costello Show)
>      from 'King Of America'
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss