The flex error is the common item between your two posts... Maybe need to install flex-2.5.4a-293.i586.rpm from ftp://ftp.suse.com/pub/suse/i386/9.1/suse/i586/ ? Keith -----Original Message----- From: doc [mailto:kd4e@verizon.net] Sent: Friday, July 23, 2004 11:56 AM To: suse-linux-e@suse.com Subject: Re: [SLE] Help with ndiswrapper?
flex -t inf-parser.l > inf-parser.c /bin/sh: line 1: flex: command not found
burgeke@HQ.VerizonWireless.com wrote:
The flex error is the common item between your two posts... Maybe need to install flex-2.5.4a-293.i586.rpm from ftp://ftp.suse.com/pub/suse/i386/9.1/suse/i586/ ?
Keith
Thanks! I have just done so and then re-ran things. Here are the new results: linux:/usr/src/ndiswrapper # make install make -C driver install make[1]: Entering directory `/usr/src/ndiswrapper/driver' make -C /lib/modules/2.6.5-7.95-default/build SUBDIRS=/usr/src/ndiswrapper/driver modules make[2]: Entering directory `/usr/src/linux-2.6.5-7.95-obj/i386/default' make -C ../../../linux-2.6.5-7.95 O=../linux-2.6.5-7.95-obj/i386/default modules WARNING: Symbol version dump /usr/src/linux-2.6.5-7.95-obj/i386/default/Module.symvers is missin Building modules, stage 2. MODPOST make[2]: Leaving directory `/usr/src/linux-2.6.5-7.95-obj/i386/default' mkdir -p /lib/modules/2.6.5-7.95-default/misc install -m 0644 ndiswrapper.ko /lib/modules/2.6.5-7.95-default/misc depmod -a make[1]: Leaving directory `/usr/src/ndiswrapper/driver' make -C utils make[1]: Entering directory `/usr/src/ndiswrapper/utils' flex -t inf-parser.l > inf-parser.c cc -g -Wall -c -o inf-parser.o inf-parser.c gcc -o loadndisdriver loadndisdriver.o inf-parser.o rm inf-parser.c make[1]: Leaving directory `/usr/src/ndiswrapper/utils' linux:/usr/src/ndiswrapper # ndiswrapper -i /home/edoc/apps/buffalo/broadcom/bcmwl5.sys bash: ndiswrapper: command not found linux:/usr/src/ndiswrapper # cd utils linux:/usr/src/ndiswrapper/utils # ls . inf-parser.l loadndisdriver loadndisdriver.h Makefile .. inf-parser.o loadndisdriver.c loadndisdriver.o linux:/usr/src/ndiswrapper/utils # cd .. linux:/usr/src/ndiswrapper # cd driver linux:/usr/src/ndiswrapper/driver # ls . .loader.o.cmd ndis.o ndiswrapper.o winsyms.h .. Makefile .ndis.o.cmd .ndiswrapper.o.cmd winsyms.o casemap.h misc_funcs.c ndiswrapper.ko proc.c .winsyms.o.cmd coffpe.h misc_funcs.o .ndiswrapper.ko.cmd proc.o wrapper.c loader.c .misc_funcs.o.cmd ndiswrapper.mod.c .proc.o.cmd wrapper.h loader.h ndis.c ndiswrapper.mod.o .tmp_versions wrapper.o loader.o ndis.h .ndiswrapper.mod.o.cmd winsyms.c .wrapper.o.cmd linux:/usr/src/ndiswrapper/driver # ndiswrapper -i /home/edoc/apps/buffalo/broadcom/bcmwl5.sys bash: ndiswrapper: command not found linux:/usr/src/ndiswrapper/driver # -- Thanks! & 73, doc kd4e West Central Florida Drake, Heathkit, Kenwood, TenTec, Yaesu Radio Life: http://www.gospelcom.net/twr/ Linux-Incompatible hardware is defective! USA Pres. Election 2004: http://www.rnc.org/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* doc
linux:/usr/src/ndiswrapper/driver # ndiswrapper -i /home/edoc/apps/buffalo/broadcom/bcmwl5.sys bash: ndiswrapper: command not found linux:/usr/src/ndiswrapper/driver #
either ndiswrapper is *not* an executable or it is *not* in root's path. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Patrick Shanahan wrote:
* doc
[07-23-04 12:58]: linux:/usr/src/ndiswrapper/driver # ndiswrapper -i /home/edoc/apps/buffalo/broadcom/bcmwl5.sys bash: ndiswrapper: command not found linux:/usr/src/ndiswrapper/driver #
either ndiswrapper is *not* an executable or it is *not* in root's path.
How do I determine if it is an executable? How do I cause it to be in root's path? This, of course, leaves unanswered the question of why the make install did not cause ndiswrapper to be set up correctly -- a question for another day! ;-) -- Thanks! & 73, doc kd4e West Central Florida Drake, Heathkit, Kenwood, TenTec, Yaesu Radio Life: http://www.gospelcom.net/twr/ Linux-Incompatible hardware is defective! USA Pres. Election 2004: http://www.rnc.org/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* doc
Patrick Shanahan wrote:
either ndiswrapper is *not* an executable or it is *not* in root's path.
How do I determine if it is an executable?
How do I cause it to be in root's path?
This, of course, leaves unanswered the question of why the make install did not cause ndiswrapper to be set up correctly -- a question for another day! ;-)
First question answer. See if executable is set in the permissions. you@local:~> ls -l /<location>/ndiswrapper Second question answer. Add the path to <filename> to root's path. but I suspect that the answers make little sense to you. Just off-hand, I would suggest that you need to spend some time with the Admin and User manuals you received with your distro. Your questions are of a *very* basic level. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
Patrick Shanahan wrote:
* doc
[07-23-04 15:46]: Patrick Shanahan wrote:
either ndiswrapper is *not* an executable or it is *not* in root's path.
How do I determine if it is an executable?
How do I cause it to be in root's path?
This, of course, leaves unanswered the question of why the make install did not cause ndiswrapper to be set up correctly -- a question for another day! ;-)
First question answer. See if executable is set in the permissions. you@local:~> ls -l /<location>/ndiswrapper
Second question answer. Add the path to <filename> to root's path.
but I suspect that the answers make little sense to you. Just off-hand, I would suggest that you need to spend some time with the Admin and User manuals you received with your distro. Your questions are of a *very* basic level.
I have spent hundreds of dollars and hundreds of hours reading manuals and online how-to's, mans, etc. The problem is they all assume elements of knowledge and thus skip them -- even in instructions that claim to be "basic". I frankly no longer have the funds and time to try to figure out why "make install" is not properly coded to get the job done and to try and guess the correct workaround -- the coder should have written the necessary tests and code to handle the exceptions -- or to at least write error messages that are less cryptic and more helpful than M$. I should be able to type "help set permissions executable" and read simple instructions with complete examples within Suse instead of a string and list of variables designed for someone already well-versed in linux command parsing. I should be able to type "help add path to root's path" and read the same. Man -k output is generally a nightmare, e.g. one sends "man -k path" and gets essentially and useless useless dump or every command that includes the word "path". Some of the items on the list look like a Webster's dictionary definition that uses the word in its own definition -- not helpful -- or that references obscure terminology -- not newbie friendly. As Linux tries to move into general use the lack of truly basic instructions in a highly accessible and easily understood format will make or break the effort -- things have improved but still have along way to go. Meanwhile I just want make install to make install ndiswrapper, not to send me into days wasted trying to figure out what the incomplete make install code did wrong. Is that too much to ask? *Rant Off* Sorry, just frustrated because life is busy and I keep imagining that computers are supposed to make things more rather than less efficient! Linux is better than M$ Windows but still wastes far too much of my time. ;-\ -- Thanks! & 73, doc kd4e West Central Florida Drake, Heathkit, Kenwood, TenTec, Yaesu Radio Life: http://www.gospelcom.net/twr/ Linux-Incompatible hardware is defective! USA Pres. Election 2004: http://www.rnc.org/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
doc wrote:
<SNIP> As Linux tries to move into general use the lack of truly basic instructions in a highly accessible and easily understood format will make or break the effort -- things have improved but still have along way to go.
Meanwhile I just want make install to make install ndiswrapper, not to send me into days wasted trying to figure out what the incomplete make install code did wrong. Is that too much to ask?
*Rant Off* Sorry, just frustrated because life is busy and I keep imagining that computers are supposed to make things more rather than less efficient! Linux is better than M$ Windows but still wastes far too much of my time. ;-\
I wouldn't consider compiling low level network drivers general use of Linux or any other operating system. Very few Windows users would dare attempt what you are trying. That, however, is just my opinion and not helping you a bit. Soooo .... It still may have something to do with flex ... double check it is installed. Try "which flex" and see what you get. Run ldconfig I don't recall ... did you try the ndiswrapper RPM that is included in 9.1 (ver. 6.23) or will it not work with your driver? clear the current source directory and try again. make sure and run "modprobe -r ndiswrapper" before trying anything. uninstall the ndiswrapper RPM before doing the compile and install of the source version. Keep trying! Louis
On Friday 23 July 2004 04:56 pm, doc wrote:
I have spent hundreds of dollars and hundreds of hours reading manuals and online how-to's, mans, etc. The problem is they all assume elements of knowledge and thus skip them
Well then you probably will never succeed with linux OR windows. With your approach, you may be better off paying the $19 to Linuxant.com for their driver loader. Its a LOT easier than ndiswrapper, and no pesky manuals to read. -- _____________________________________ John Andersen
Patrick Shanahan wrote:
* doc
[07-23-04 12:58]: linux:/usr/src/ndiswrapper/driver # ndiswrapper -i /home/edoc/apps/buffalo/broadcom/bcmwl5.sys bash: ndiswrapper: command not found linux:/usr/src/ndiswrapper/driver #
either ndiswrapper is *not* an executable or it is *not* in root's path.
How do I determine if it is an executable?
How do I cause it to be in root's path?
This, of course, leaves unanswered the question of why the make install did not cause ndiswrapper to be set up correctly -- a question for another day! ;-)
-- Thanks! & 73, doc kd4e <SNIP> All I can tell you is that I compiled it from root, and upon installation the binary was not only in root's path but was executable. -- ...CH "The more they over-think the plumbing,
On Friday 23 July 2004 15:44, doc wrote: the easier it is to stop up the drain." Scotty
participants (6)
-
burgeke@HQ.VerizonWireless.com
-
C Hamel
-
doc
-
John Andersen
-
Louis Richards
-
Patrick Shanahan