Wireless receptor
-
- KVRian
- 524 posts since 25 Aug, 2005
Don't know why not, if the USB receiver on the Receptor is fully compliant, but that is NOT a "yes", I do not know. Ask Linksys how they handle Linux (their tech support has been good to me when I've called - a bit digmatic and scripted, but the ts guys were knowledgable) - if it needs drivers, you're SOL, if it's transparent to the system, you're prbably good to go...
-
- KVRist
- 96 posts since 2 May, 2004 from USA
lets see here...
get usb wireless thingy thats already in the 2.4 source tree.
download "muse's 2.4 kernel source's" tree and "GCC".
copy the .config from the sources as A backup.
"cat /proc/pci" (to get your hardware type)
"dmesg and lspci" (more info pertaning to your wiFi card-thingy).
build your kernel, make your modules, write a new entry in grub for your new kernel (leave the backup).
add your module in the required runlevel, write the needed attibutes into the eth0.
# out your realtec eth0 so the wifi is now default.
---------------------------------------
its all about runlevels, modules and configs.
Beken One
get usb wireless thingy thats already in the 2.4 source tree.
download "muse's 2.4 kernel source's" tree and "GCC".
copy the .config from the sources as A backup.
"cat /proc/pci" (to get your hardware type)
"dmesg and lspci" (more info pertaning to your wiFi card-thingy).
build your kernel, make your modules, write a new entry in grub for your new kernel (leave the backup).
add your module in the required runlevel, write the needed attibutes into the eth0.
# out your realtec eth0 so the wifi is now default.
---------------------------------------
its all about runlevels, modules and configs.
Beken One
myspace.com/bekenone
-
- KVRist
- 96 posts since 2 May, 2004 from USA
---------------WARNING THIS IS FOR EXPERIANCED LINUX HACKERS--------
---------IF YOU DONT UNDERSTAND ANY OF THIS PLEASE SKIP THIS POST-------
----------------------YOU HAVE BEEN WARNED!!!--------------
first you need to know your WIFI hardware.
NO this wont involve clicking a mouse and buttons to push.
research the following: "lspci", "dmesg", "tail -c /var/log/lastlog" and "cat /proc/pci"
then
1. go to Receptors ftp site and download the 2.4 sources and the GCC rpm's that were used for a stock receptor.
2. untar this baby in a folder that you created in the "/root" directory.
3. all we care about is the ".config" file in /usr/src/linux.
4. you have 2 choice's....using the sources from muse (2.4) or a vanilla or patched sources from kernal.org.....or any kernal tree you trust and love (I use 2.6-gentoo-sources).
5. regardless which you use, untar it inside "/usr/src" then make a symbolic link (soft)to the name of your folder to "linux".
6. ok...if your using A 2.4 tree you can reuse the .config file and copy it inside "/usr/src/linux" then "make oldconfig" then "make menuconfig", if not you have to "make menuconfig" and input the info from the .config from skratch (have fun and beware).
7. make bzImage && make modules make modules_install (2.4.x), make bzImage && make modules (2.6.x).
8. edit your boot loader and updade it, better yet make a new entry for that new kernel (man lilo, man grub).
9. restart and "modprobe the_name_of_your_wifi_module".
10. read up on anyone that have used that card on linux , particularly REDHAT based so you could edit the "init files for it (many are different).
-----------------------------------------
this is a starting point and NOT a how to.
---------IF YOU DONT UNDERSTAND ANY OF THIS PLEASE SKIP THIS POST-------
----------------------YOU HAVE BEEN WARNED!!!--------------
first you need to know your WIFI hardware.
NO this wont involve clicking a mouse and buttons to push.
research the following: "lspci", "dmesg", "tail -c /var/log/lastlog" and "cat /proc/pci"
then
1. go to Receptors ftp site and download the 2.4 sources and the GCC rpm's that were used for a stock receptor.
2. untar this baby in a folder that you created in the "/root" directory.
3. all we care about is the ".config" file in /usr/src/linux.
4. you have 2 choice's....using the sources from muse (2.4) or a vanilla or patched sources from kernal.org.....or any kernal tree you trust and love (I use 2.6-gentoo-sources).
5. regardless which you use, untar it inside "/usr/src" then make a symbolic link (soft)to the name of your folder to "linux".
6. ok...if your using A 2.4 tree you can reuse the .config file and copy it inside "/usr/src/linux" then "make oldconfig" then "make menuconfig", if not you have to "make menuconfig" and input the info from the .config from skratch (have fun and beware).
7. make bzImage && make modules make modules_install (2.4.x), make bzImage && make modules (2.6.x).
8. edit your boot loader and updade it, better yet make a new entry for that new kernel (man lilo, man grub).
9. restart and "modprobe the_name_of_your_wifi_module".
10. read up on anyone that have used that card on linux , particularly REDHAT based so you could edit the "init files for it (many are different).
-----------------------------------------
this is a starting point and NOT a how to.
myspace.com/bekenone
-
- KVRist
- 69 posts since 9 Jan, 2006
Not to rain on your parade, but there are no rpms for the kernel sources Muse used for the Receptor at Muse's FTP. If there are, where are they? I could be blind, but I'm not sure... please point me in the right ftp://ftp.museresearch.com/rpms/redhat8/<direction>. gcc I can find, but then all I get is a chicken and egg situation. Can't compile the gcc without gcc.bekenone wrote:1. go to Receptors ftp site and download the 2.4 sources and the GCC rpm's that were used for a stock receptor.
Are you meaning that you actually are running your Receptor on a 2.6 kernel? Please do tell how you managed to do that. What soundcard drivers etc. did you use? Does it run faster?bekenone wrote:4. you have 2 choice's....using the sources from muse (2.4) or a vanilla or patched sources from kernal.org.....or any kernal tree you trust and love (I use 2.6-gentoo-sources).
Maybe I should mention that I haven't personally tried compiling a 2.6 kernel for the Receptor myself mainly because I don't have the required developement packages installed on the Receptor (and neither do I have another dedicated developement computer running a similar RedHat installation that could compile stuff for the Receptor). Also, I can't find binary packages for gcc etc. anywhere. Maybe I'm an google idiot or just plain lazy, but it would be nice to be able to compile your own stuff on the Receptor. (I'm not at all used to RPM dependencies etc. In fact, I have a source based upbringing having used Crux GNU/Linux for a long time).
Cheers,
--
Olle Gustafsson
-
- KVRist
- 96 posts since 2 May, 2004 from USA
PLEASE!! before you do any of this use a copyed version of your hardrive...
GCC:
ftp://ftp.museresearch.com/rpms/redhat8 ... -7.src.rpm
GLIBC:
ftp://ftp.museresearch.com/rpms/other/g ... 8.i386.rpm
GLIBC-DEV
ftp://ftp.museresearch.com/rpms/other/g ... 8.i386.rpm
well...Im used to source building as well on Slackware and FreeBSD for but now Im a Gentoo zealot.
I logged in as root then "PROC-ed" that crap out of my stock system and saved them to text files and looked up the info on the net and in the kernal sources websites (too many to mention).
then played withg differnet nic and video cards at first just to see if its runs like a "NORMAL" motherboard, It did so I'm just testing the waters (so to speak).
Im using 2.6.18-gentoo-sources on a practice harddrive because its already patched with the low latency stuff.
the stock ALSA driver (sound) is one "IC Ensemble Inc. rev 1" and A "VIA VT8233 AC97"
it runs about the same, nothing special.
what I want to do is use a better video card and enable DRI so the rendering wont be so damm wierd.
P.S. I hate "VI" with a passion so I use NANO instead...those that want it here it is:
http://www.nano-editor.org/dist/v1.2/RP ... 1.i386.rpm
GCC:
ftp://ftp.museresearch.com/rpms/redhat8 ... -7.src.rpm
GLIBC:
ftp://ftp.museresearch.com/rpms/other/g ... 8.i386.rpm
GLIBC-DEV
ftp://ftp.museresearch.com/rpms/other/g ... 8.i386.rpm
well...Im used to source building as well on Slackware and FreeBSD for but now Im a Gentoo zealot.
I logged in as root then "PROC-ed" that crap out of my stock system and saved them to text files and looked up the info on the net and in the kernal sources websites (too many to mention).
then played withg differnet nic and video cards at first just to see if its runs like a "NORMAL" motherboard, It did so I'm just testing the waters (so to speak).
Im using 2.6.18-gentoo-sources on a practice harddrive because its already patched with the low latency stuff.
the stock ALSA driver (sound) is one "IC Ensemble Inc. rev 1" and A "VIA VT8233 AC97"
it runs about the same, nothing special.
what I want to do is use a better video card and enable DRI so the rendering wont be so damm wierd.
P.S. I hate "VI" with a passion so I use NANO instead...those that want it here it is:
http://www.nano-editor.org/dist/v1.2/RP ... 1.i386.rpm
myspace.com/bekenone
