#114219 - cartz - Fri Jan 05, 2007 1:15 pm
Hi everyone,
I've been getting right into the homebrew DS scene lately but can't get any of the Wifi programs to connect for some reason. Commercial games work fine, Opera browser also fine.
My wireless router is using WEP , the code is key is only 5 digits long. I don't suppose that anything to do with anything does it? I've tried entering it in ASCII and the HEX equivilant, though the DS didn't accept the HEX
I've tried manual settings, using the Nintendo WFC settings but haven't had any success ... yet. I'm really looking forward to trying two particular pieces of homebrew software: DSMidiWifi and DS2Key. Any help would be greatly appreciated.
- cartz -
P.S. This is my first post - If it's in the wrong section please don't scream at me! (^-^)
#114244 - Quirky - Fri Jan 05, 2007 8:02 pm
Have you had any luck with the wardriving DSWifi demo application? That allows you to connect using the built in Nintendo WFC settings or by hand editing the settings. You can scan for APs too, to check if homebrew sees your router. You can download it from sgstair's site http://akkit.org/dswifi/
#114275 - cartz - Sat Jan 06, 2007 4:26 am
Thank you for the reply! (^-^)
I used the wardriving application that comes with DS2Key. It sees my router. says that WEP is on, I get 70% signal strength. When I try connecting using the Nintendo WFC settings, it doesn't connect, no matter which way I try I always get "ASSOCSTATUS_SEARCHING" ... forever it seems. Hmm... tricky
I will download the version of wardriving demo you told me about and see if it can solve anything. Thanks so much for your help.
#114608 - cartz - Tue Jan 09, 2007 2:04 pm
I can see my router and whole bunch of others with the Wardriving program, but still I can't connect to anything. Really not sure how to solve this. Even with WEP turned off, it still won't connect! I know this a tricky one, but is there anything I could be doing wrong. I've triple quad checked that all the settings are right, WEP, SSID, IP, Gateway etc.. , I really don't know what it is. If anyone has any idea what could be stopping my unit connect it would be great if you let me know. Thanks so much.
#114699 - HyperHacker - Wed Jan 10, 2007 5:59 am
Your settings are NWFC connection #1? Most apps won't even look at #2 or #3.
_________________
I'm a PSP hacker now, but I still <3 DS.
#114822 - GrizzlyAdams - Wed Jan 10, 2007 10:56 pm
You likely have the new wifi chipset in your dslite like I do. It currently does not work. You can verify this by dumping the first 512bytes of your firmware and checking it against the dswifi documentation. The baseband and rf chip setup tables are different on the newest dslites.
Nintendo's wifi stuff works cause they propperly handle all the information there. Homebrew doesn't work cause sgstair didn't do something, and noone is quite sure yet what that is.
#114830 - Optihut - Thu Jan 11, 2007 12:07 am
| GrizzlyAdams wrote: |
You likely have the new wifi chipset in your dslite like I do. It currently does not work. You can verify this by dumping the first 512bytes of your firmware and checking it against the dswifi documentation. The baseband and rf chip setup tables are different on the newest dslites.
Nintendo's wifi stuff works cause they propperly handle all the information there. Homebrew doesn't work cause sgstair didn't do something, and noone is quite sure yet what that is. |
Argh!
I tried to use homebrew stuff like beup during the Christmas break (I don't have a WLAN here, but my parents do, so it seemed a good opportunity), but it didn't work for me either. Mariokart and Metroid were running fine, though. I guess that explains it, thanks for the info!
#114884 - GrizzlyAdams - Thu Jan 11, 2007 8:42 am
Ok, check out the newest CVS of dswifi. work has been done to fix the bug. SetChannel wasn't working on the new dslite hardware.
I've confirmed it to work now with the patch. I also applied the patch to linux and had success.
#114999 - tyraen - Fri Jan 12, 2007 2:58 am
Good thing I just read this because I was going to make a stupid post. :)
So my wife and I both have a DS now, her's is white, mine's black. I've been having a lot of trouble with wifi on mine (trouble connecting, then trouble keeping a connection or actually using it) and so I tried the wifi_lib_test on her's. It seemed to be much quicker in picked up the AP, and even picked up a number of them I didn't know existed around my neighbourhood. :)
But I can't really check the firmware can I, since I flashed it... is there any way to tell if it's a new chipset or if it's a crap chipset?
#115017 - GrizzlyAdams - Fri Jan 12, 2007 6:23 am
Even if you used flashme it should have retained the wifi settings area. Only thing I know that has caused problems is unflashme.
#115034 - tyraen - Fri Jan 12, 2007 11:36 am
Somebody mentioned that you can dump the first bit of your firmware to check what version it is, that's what I meant.
#118081 - devitek - Fri Feb 09, 2007 10:43 pm
| GrizzlyAdams wrote: |
Ok, check out the newest CVS of dswifi. work has been done to fix the bug. SetChannel wasn't working on the new dslite hardware.
I've confirmed it to work now with the patch. I also applied the patch to linux and had success. |
When you say "patch", what are you referring to? I need to patch DSLinux to work with the newer hardware, but I have no idea how to go about it.
#118996 - IBNobody - Mon Feb 19, 2007 12:24 am
Has there been any more updates to the DS Lite Wifi problem?
I'm currently running a DS Lite that is only a few months old, and I can't get anything that uses the wifi lib to work. It won't even pull up data stored in the first WFC slot.
I've tried the latest wifi lib test (0.3a built on 01-10-2007), and I get nothing there, either.