Bugzilla – Bug 6186
Jive r923 won't accept passphrase
Last modified: 2007-11-19 01:57:07 UTC
Starting with 932, I cannot get jive to accept my passphrase. I just reset Jive, after taking download of r923. After entering the last character of my WPA passphrase, I click the center button twice as usual. The center button beeps, but jive does not advance to the next screen.
Mike, I can't recreate this here. Are you sure you have entered your wpa passphrase correctly, you can go on if you have not entered enough characters. If not I really need the debug from /var/log/messages, so can you: 1. Try to connect with WPA 2. Disable WPA on your access point 3. Connect with no encryption 4. Copy /var/log/messages from Jive over SSH (let me know if you need instructions for this) (You can always put the battery in while pressing the volume up button to revert to the previous installed version.)
The unit does not attempt to proceed to the next step after entering the last character. It just "bounces" instead of moving to the next step. This is the first time I've experienced this (and I've had to re-enter my gawd-awful long passphrase dozens of times). I'll get you some logs... Stay tuned. Mike
ah, ok. so it bounces, how long is your passphrase? maybe you could email it to me at richard at slimdevices dot com.
Actually, it beeps. Sorry. I disabled security, and try to connect w/no security. Same thing - beeps but won't go to the next step. Also, it is not detecting my SSID, despite it being being broadcast and MAC address control disabled. I'm resetting now.
Pulled battery, held Vol Up, replaced battery. It does not see the network, and will not proceed past the Wireless Encryption stage. No beeps now (the wheel clicks so sound is working). Should I factory reset ?
Hmm. I'd love some debug, but not sure how you can get it! Please try a factory reset, does that help? Does it see any networks (assuming you can normally see more than one)?
After a + Key - battery insert reset, the unit now connects to the network and all looks good. I think the unit became very confused
reducing severity as issue has passed. Is it considered a one-time glitch; should this be closed?
I'm ok with closing.
Closing the bug now, please reopen if you have the problem again.