.:.:. * A Few Simple Questions * .:.:.
Hi all, I seem to be having some trouble with particularly these two problems...
1.) Trying to install my TRENDnet TEW-221PC (TRENDnet and ADMtek seem to have drivers for only RH 7 and 8 , I don't even think my PCMCIA package is working or how to start/restart it) 2.) How to boot to commandline - FOUND OUT HOW, THANKS! This is all on a Dell Inspiron 2650 Laptop with RedHat 9/GNOME |
Hi,
About your second question: In the file /etc/inittab change the line id:5:initdefault: to id:3:initdefault: This is called changing the runlevel. You can do it after booting as well with the telinit command. For more info see http://stalin.iodynamics.com/education/runlevel.html http://www.tuxfiles.org/linuxhelp/xbootup.html http://jamesthornton.com/redhat/linu...down-sysv.html Arvind |
Quote:
|
nobody's worked with a TEW-221PC?
|
http://www.trendnet.com/asp/download...=184&B1=Search
http://www.driverforum.com/network4/1789.html I found both of those by searching www.google.com with the search "TRENDnet TEW-221PC linux" Hope they help. (the Trendnet link has the manufacturers driver, the driverforum has instructions - I'd read over the driverforum to see if it helps). |
Is CARDBUS a package? If it is I can't find it anywhere, or is CARDBUS referring to the PCMCIA slot?
Also, last time I tried the "make" command on the untard dir, I ended up with a giant list of "Warning: error"s instead of some files |
Also, no matter how hard I try I cannot find drivers for RH9, or any other distribution for that matter, only RedHat 7.x and 8.0
|
RH 8 drivers should work with 9 (9 is just 8 with bugfixes [duck]).
What were the warning errors? It may be that you are missing some programs needed by the installer. |
do you have AIM? It would be alot easier if I could do a p2p conversation
|
But then you would rob the rest of the board members of the solution and the steps to that solution. :D
Talk me through what you have done so far and what errors have come up. |
alright I un-gzip'd the tar, and un-tar'd for a new directory...now I'm stuck on what to do from there
|
It is worth while reading the readme in the new directory just to make sure it doesn't need you to install in a different way from the instructions below.
In fact, if it's not too long, could you copy, paste and post the relevant bits from the readme. cd into the directory (in a terminal type 'cd /path/to/the/directory' minus the ' ' marks) then type in './configure' when it has finished, type in 'make' when that has finished type in 'su' type in the password for root type in 'make install' |
Code:
I. Installation Guide Code:
Makefile: line 1: CC: command not found |
Quote:
Since you have the source code, you will need to the 'manual' install. First, did you install the kernel-source when you installed RH? If not, you can add them through the install manager (it's been a while since I used RH9), I think it's the RPM manager you need. There is an option in there to install the kernel source, when it prompts you put in the relevant cd. That is, of course, if you didn't already install it. Then Quote:
Then Quote:
Note: I'm not sure where you are, but it's now 2254hrs and I have work in the morning (up at 0630hrs boo hoo) but I will be back on tomorrow night. Let me know how you get on. |
I have the same issues....
I can get the driver loaded (using the 3com provided one) for my 3Com RS...somin PC-Card. The light for the card comes on - but no link light. I can't see the ESSID set in iwconfig unless the card is in ad-hoc mode. I have an IP set, Key set and essid set (in ad-hoc) and can't see my AP. I put my AP essid broadcast on, removed mac address filtering and wep and the card still can't connect and get a "link" light up. What do I need to do? I am using Fedora Core 1 with the latest kernel and the drivers compiled from source from the 3Com web page. Cheers. |
3COM/3crshpw796 in Suse
I am having similar problems to ones posted earlier about
configuring wireless network cards and in particular setting wireless configurations using iwconfig I have 3COM 3CRSHPW796 card under Suse 9.0. By fiddling around repeatedly with iwconfig, I can set the ESSID but it appears I have to know what the essid is in advance... If I set ESSID to any then nothing is found nor does iwlist find anything. If I give it the ESSID that I can read in Windows it seems to find the signal (great signal strength shown, and if I switch off the access point, it disappears). Once I managed to get the Link light to come on. But I couldn't then set the ESSID. By the time I had set the ESSID the Link light disappeared. I went through my shell history and tried to replicate the process but without any luck... |
I have also used these drivers....
http://www.espina.info/papers/officeconnect/ And this time (after removing the 3com ones) I can sometimes get a link light. But as per the above URL I have left ESSID broadcast on, on the router. I never see anything when I do a iwlist. The driver does not support iwspy. Once I did get a link light, and a listing for an AP in iwlist - but after checking some other issues later on (when I had no link light or iwlist result) I found that the card is only finding itself. Point is, when I did have a link light and a iwlist result, I forget if the AP listed was in fact ME! :-\ Anyway, I could never ping. I have had it up to my neck with this driver.....this is one of the main issues with me for Linux. Friggin hardware support - talk about a waste of time. Anyway, being a long time Linux backend dude, I wanted to make the transition to the desktop - now that the palm link stuff is better - but I want WIFI!! :-) I have also tried searching for general info on how to setup wifi networking as it seems to be a minefield compared to standard Ethernet, iwtools package, this "something"-ng package, etc. I downloaded and install APRadar and it looks cool - but is hampered by the fact that both the 3com driver and the above driver from the Spanish dude don't support scanning. Also because the 8211.o or 3com.o driver don't appear in the list of hardware in the netcfg tool (even though /etc/pcmcia/config is updated) it is hard to use any of the GUI tools or ncurses tools to set this little bugger. So I am resorting to only iwconfig and command line editing of the cfg files otherwise you get these weird Frankenstein config files. Also, both drivers, =NEVER= unload the driver module when the card is ejected. Anyone know a good plan of attack for these drivers and this card? I assumed 3Com would have good support. Ha! Peach. |
I think we're in the same boat peach, and tried the same things.
I can sometimes get the card into state where it does see the AP (which I can verify by physically swiitching off the AP and seeing that the signal level drops) and I can ping the card but that'ts it. Anyway enough --- time to throw away this 3COM card and get another. |
Alas, I can't throw it away. Here in China wifi is non existant so the prices are HUGE!
I paid a fortune for this one (Tried to get another one when I was in Australia for work 2 months ago, where cards cost the same as the US re: cheap - but Dell stuffed up the delivery, sent me a Mini PCI card!!!!!) So I can't throw it away that easy as I ain't going to be able to re-sell it and I am not going to plonk another USD$80 down for a PC-CARD Wifi adapter.... :( And USD$80 we are talking .b forget about .g. Peach. |
All times are GMT -5. The time now is 10:10 PM. |