wicked wiki problems
in [Mandrake]
|
Prev: PVR
Next: Wallpaper moves up and down
From: the man with no idea on 29 Aug 2005 18:17 Well I've been trying for ever to get my Belkin F5D7050 usb wireless dongle to work to no avail. I happened across some instructions (the easiest I've seen) that went like this: 1) Download the newest RT2570 USB nightly CVS tarball from http://rt2x00.serialmonkey.com/wiki/index.php/Downloads 2) Open a console in the download directory. 3) Unpack the tarball with the following command: code:# tar -xzf rt2500-cvs-daily.tar.gz 4) Type: code:# cd ./rt2500-cvs-*/Module 5) Type: code:# make 6) To install the module, type: code:# sudo insmod rt2500.ko etc, etc. I got stuck at stage 3, I couldn't get the tarball to unpack but got an error message. So I unpacked it on my windows machine using ALZip (which is a great freeware utility) and copied the unpacked stuff into tmp. 4: managed to navigate to the right subdirectory /tmp/rt2750-cvs-20050813/Module (it took me a while before I realised that the capitalization is important). 5: typed make and got the following: make: *** /lib/modules/2.6.8.1-12mdk/build: No such file or directory. Stop. rt2570.ko failed to build! make: *** [module] Error 1 Now I do have a /lib/modules/2.6.8.1-12mdk directory but there is no build subdirectory. Should there be one? Could the problem be with the tarball (since the tar command just produced an error) - although it did unpack using ALZip in win XP? Any help appreciated.
From: Mike Todd on 30 Aug 2005 00:24 "the man with no idea" <no.spam(a)thanks> wrote in message news:yPLQe.1216$76.136(a)newsfe5-gui.ntli.net... > Well I've been trying for ever to get my Belkin F5D7050 usb wireless dongle > to work to no avail. I happened across some instructions (the easiest I've > seen) that went like this: > 1) Download the newest RT2570 USB nightly CVS tarball from > http://rt2x00.serialmonkey.com/wiki/index.php/Downloads > 2) Open a console in the download directory. > 3) Unpack the tarball with the following command: > code:# tar -xzf rt2500-cvs-daily.tar.gz Please note that "code:# " is the system prompt. What it means is that you have logged on as "super user" because of the "#" ending the prompt. > 4) Type: > code:# cd ./rt2500-cvs-*/Module > 5) Type: > code:# make > 6) To install the module, type: > code:# sudo insmod rt2500.ko > > etc, etc. > > I got stuck at stage 3, I couldn't get the tarball to unpack but got an > error message. So I unpacked it on my windows machine using ALZip (which is > a great freeware utility) and copied the unpacked stuff into tmp. A tarball contains not just files but also directory structures. Unarchiving the file on a Windows system just gives you the files and does not create the right "directories" on your Unix/Linux system. That is a precursor to failure of the process. > > 4: managed to navigate to the right subdirectory > /tmp/rt2750-cvs-20050813/Module (it took me a while before I realised that > the capitalization is important). > > 5: typed make and got the following: > make: *** /lib/modules/2.6.8.1-12mdk/build: > No such file or directory. Stop. > rt2570.ko failed to build! > make: *** [module] Error 1 > > Now I do have a /lib/modules/2.6.8.1-12mdk directory but there is no build > subdirectory. Should there be one? > > Could the problem be with the tarball (since the tar command just produced > an error) - although it did unpack using ALZip in win XP? Hopefully, you included the "code:# " in your command to process the tarball and using the correct command will "fix" the problems... > > Any help appreciated. > -- Mike Todd
From: BearItAll on 30 Aug 2005 12:11 On Mon, 29 Aug 2005 22:17:02 +0000, the man with no idea wrote: > Well I've been trying for ever to get my Belkin F5D7050 usb wireless dongle > to work to no avail. I happened across some instructions (the easiest I've > seen) that went like this: > 1) Download the newest RT2570 USB nightly CVS tarball from > http://rt2x00.serialmonkey.com/wiki/index.php/Downloads > 2) Open a console in the download directory. > 3) Unpack the tarball with the following command: > code:# tar -xzf rt2500-cvs-daily.tar.gz > 4) Type: > code:# cd ./rt2500-cvs-*/Module > 5) Type: > code:# make > 6) To install the module, type: > code:# sudo insmod rt2500.ko > > etc, etc. > > I got stuck at stage 3, I couldn't get the tarball to unpack but got an > error message. So I unpacked it on my windows machine using ALZip (which is > a great freeware utility) and copied the unpacked stuff into tmp. > > 4: managed to navigate to the right subdirectory > /tmp/rt2750-cvs-20050813/Module (it took me a while before I realised that > the capitalization is important). > > 5: typed make and got the following: > make: *** /lib/modules/2.6.8.1-12mdk/build: > No such file or directory. Stop. > rt2570.ko failed to build! > make: *** [module] Error 1 > > Now I do have a /lib/modules/2.6.8.1-12mdk directory but there is no build > subdirectory. Should there be one? > > Could the problem be with the tarball (since the tar command just produced > an error) - although it did unpack using ALZip in win XP? > > Any help appreciated. As mike said, on the assumption you typed exactly as you printed it here, you are likely to be typing the prompt as well as the command. But I also noticed a missing step. So this is you list again, with a couple of hints as well. 1) Download the newest RT2570 USB nightly CVS tarball from http://rt2x00.serialmonkey.com/wiki/index.php/Downloads Have a directory that is just for this sort of thing, i.e. downloads. mkdir downloads Then make sure your browser is pointing there when it offers the save directory. Do the same if you use 'wget'. It makes it easy for you to find them, also you may occasionally want useful downloads written to CD/DVD and this way you can grab the whole directory. 2) Open a console in the download directory. 3) Unpack the tarball with the > following command: code:# tar -xzf > rt2500-cvs-daily.tar.gz Change to your downloads directory. cd downloads tar -xzf rt2500-cvs-daily.tar.gz This unzips the file, then extracts contents to the file structure. This is important because the 'make' command will use all relative file commands. For example it might include one of it's sub directories .../includethis/somefile Which may or may not have been there when you extracted using your Windows program. You will see tar a lot, also 'gz' files. You can do the same extract in two stages like this, gunzip rt2500-cvs-daily.tar.gz If you then type ls You will see the 'gz' file has been replaced with. rt2500-cvs-daily.tar (it has been unzipped) Then the command tar -xf rt2500-cvs-daily.tar Extracts the files to a relative file structure. Which means it produces the original structure that was included in the tar file, but starting at the current directory. 4) Type: > code:# cd ./rt2500-cvs-*/Module cd rt2500-cvs-daily/Module > 5) Type: > code:# make There was a step missing in your instructions. su Which will prompt you for your root password. Make will not build successfully, in this case, if you run it as a standard user. make Then watch the screen, at the end of the make you are told whether it was built successfully. > 6) To install the module, type: > code:# sudo insmod rt2500.ko As you are still root you can just type, insmod rt2500.ko I think your instructions will then take you into 'enabling' and then the security aspect for general wifi connectivity, also there will be a process of 'discovering' your wireless router. But I suspect it will take you through doing all of that using GUI tools, so I wont try to guess the next part for you and you will find theirs easier to follow anyway.
From: the man with no idea on 30 Aug 2005 16:17 >> 1) Download the newest RT2570 USB nightly CVS tarball from >> http://rt2x00.serialmonkey.com/wiki/index.php/Downloads >> 2) Open a console in the download directory. >> 3) Unpack the tarball with the following command: >> code:# tar -xzf rt2500-cvs-daily.tar.gz > > Please note that "code:# " is the system prompt. What it means is that > you > have logged on as "super user" because of the "#" ending the prompt. well, I did try code:# etc and got a bash message that there was no command code and twigged that I probably shouldn't type it >> 4) Type: >> code:# cd ./rt2500-cvs-*/Module >> 5) Type: >> code:# make >> 6) To install the module, type: >> code:# sudo insmod rt2500.ko >> >> etc, etc. >> >> I got stuck at stage 3, I couldn't get the tarball to unpack but got an >> error message. So I unpacked it on my windows machine using ALZip (which > is >> a great freeware utility) and copied the unpacked stuff into tmp. > > A tarball contains not just files but also directory structures. > Unarchiving the file on a Windows system just gives you the files and does > not create the right "directories" on your Unix/Linux system. That is a > precursor to failure of the process. > >> Doing the unpacking on my windows machine did produce a folder with subfolders - so I assumed it was OK - guess not. >> 4: managed to navigate to the right subdirectory >> /tmp/rt2750-cvs-20050813/Module (it took me a while before I realised >> that >> the capitalization is important). >> >> 5: typed make and got the following: >> make: *** /lib/modules/2.6.8.1-12mdk/build: >> No such file or directory. Stop. >> rt2570.ko failed to build! >> make: *** [module] Error 1 >> >> Now I do have a /lib/modules/2.6.8.1-12mdk directory but there is no >> build >> subdirectory. Should there be one? >> >> Could the problem be with the tarball (since the tar command just >> produced >> an error) - although it did unpack using ALZip in win XP? > > Hopefully, you included the "code:# " in your command to process the > tarball > and using the correct command will "fix" the problems... > >> Now this is where you've really lost me - above "code:#" was a prompt - now are you saying that I should type it? If it wasn't recognised before, why would it be now????? >> Any help appreciated. >> > > -- > > Mike Todd > >
From: the man with no idea on 30 Aug 2005 16:17
"BearItAll" <bearitall(a)rassler.co.uk> wrote in message news:pan.2005.08.30.16.11.47.140307(a)rassler.co.uk... > On Mon, 29 Aug 2005 22:17:02 +0000, the man with no idea wrote: > >> Well I've been trying for ever to get my Belkin F5D7050 usb wireless >> dongle >> to work to no avail. I happened across some instructions (the easiest >> I've >> seen) that went like this: >> 1) Download the newest RT2570 USB nightly CVS tarball from >> http://rt2x00.serialmonkey.com/wiki/index.php/Downloads >> 2) Open a console in the download directory. >> 3) Unpack the tarball with the following command: >> code:# tar -xzf rt2500-cvs-daily.tar.gz >> 4) Type: >> code:# cd ./rt2500-cvs-*/Module >> 5) Type: >> code:# make >> 6) To install the module, type: >> code:# sudo insmod rt2500.ko >> >> etc, etc. >> >> I got stuck at stage 3, I couldn't get the tarball to unpack but got an >> error message. So I unpacked it on my windows machine using ALZip (which >> is >> a great freeware utility) and copied the unpacked stuff into tmp. >> >> 4: managed to navigate to the right subdirectory >> /tmp/rt2750-cvs-20050813/Module (it took me a while before I realised >> that >> the capitalization is important). >> >> 5: typed make and got the following: >> make: *** /lib/modules/2.6.8.1-12mdk/build: >> No such file or directory. Stop. >> rt2570.ko failed to build! >> make: *** [module] Error 1 >> >> Now I do have a /lib/modules/2.6.8.1-12mdk directory but there is no >> build >> subdirectory. Should there be one? >> >> Could the problem be with the tarball (since the tar command just >> produced >> an error) - although it did unpack using ALZip in win XP? >> >> Any help appreciated. > > As mike said, on the assumption you typed exactly as you printed it here, > you are likely to be typing the prompt as well as the command. nope But I also noticed a missing step. So this is you list again, with a couple of > hints as well. > > 1) Download the newest RT2570 USB nightly CVS tarball from > http://rt2x00.serialmonkey.com/wiki/index.php/Downloads > > Have a directory that is just for this sort of thing, i.e. downloads. > > mkdir downloads > > Then make sure your browser is pointing there when it offers the save > directory. Note - not using the internet on the linux machine - due to position I need to get the wireless adapter working before I can use the web. Do the same if you use 'wget'. It makes it easy for you to find > them, also you may occasionally want useful downloads written to CD/DVD > and this way you can grab the whole directory. > > 2) Open a console in the download directory. > > 3) Unpack the tarball with the >> following command: code:# tar -xzf >> rt2500-cvs-daily.tar.gz > > Change to your downloads directory. > > cd downloads > tar -xzf rt2500-cvs-daily.tar.gz > > This unzips the file, then extracts contents to the file structure. This > is important because the 'make' command will use all relative file > commands. For example it might include one of it's sub directories > > ../includethis/somefile > > Which may or may not have been there when you extracted using your Windows > program. Got it > > You will see tar a lot, also 'gz' files. You can do the same extract in > two stages like this, > > gunzip rt2500-cvs-daily.tar.gz > > If you then type > > ls > > You will see the 'gz' file has been replaced with. > > rt2500-cvs-daily.tar > (it has been unzipped) > > Then the command > > tar -xf rt2500-cvs-daily.tar > > Extracts the files to a relative file structure. Which means it produces > the original structure that was included in the tar file, but starting at > the current directory. > Now I'm lost again. What are the switches xf (tar the tar) and xzf (tar the gz)? Also, it sounds as if the original tar is extracting the files all over the linux system (from above) but gunzip followed by tar unpacks it to the download directory? And finally, why do it in 2 commands when one will do? Can tar operate on gz files? Note that the daily download is rt2570-cvs-daily.tar.gz and the beta is rt2570-1.1.0-b1.tar.tar Now I just don't get this double archive format - if a tarball is an archive why is it then gzipped or retarred? Obviously I'm missing something important - from between the ears I suspect. > 4) Type: >> code:# cd ./rt2500-cvs-*/Module > > cd rt2500-cvs-daily/Module > > >> 5) Type: >> code:# make > > There was a step missing in your instructions. > > su > I actually did su right at the start - is that a problem??? I always start in KDE logging in as me since root isn't an option. > Which will prompt you for your root password. Make will not build > successfully, in this case, if you run it as a standard user. > > make > > Then watch the screen, at the end of the make you are told whether it was > built successfully. > >> 6) To install the module, type: >> code:# sudo insmod rt2500.ko > > As you are still root you can just type, > > insmod rt2500.ko > > > I think your instructions will then take you into 'enabling' and then the > security aspect for general wifi connectivity, also there will be a > process of 'discovering' your wireless router. But I suspect it will take > you through doing all of that using GUI tools, so I wont try to guess the > next part for you and you will find theirs easier to follow anyway. If I get that far I'll be amazed. BTW, can you recommend a good guide for mandrake /linux novices - "linux for morons" perhaps? |