| 02:36 | _unreal_ | cant beleive it I got my cubox 1st gen working finally |
| 02:36 | _unreal_ | and goodgod this thing needs an ESATA |
| 02:37 | _unreal_ | thinking ssd esata |
| 09:51 | DHowett | _unreal_: i still love the gen1 cubox; there's something about the whole "not having gimped gigE" thing that i like |
| 20:14 | KBme | jnettlet, no dice. even with backports. |
| 20:16 | jnettlet | KBme, do you have any logs for me to take a look at? |
| 20:20 | KBme | jnettlet, sure |
| 20:22 | KBme | http://sprunge.us/FhXY |
| 20:23 | KBme | also, every once in a while (not at every connection try it seems) I get <"date" wt wpa_supplicant[1942]: nl80211: send_and_recv->nl_recvmsgs failed: -33> |
| 20:25 | jnettlet | KBme, that looks like you don't have the proper regulatory domain setup as the AP |
| 20:26 | KBme | weird thing is I do |
| 20:26 | KBme | I set it in wpa_supplicant and I have set it in the AP too |
| 20:27 | KBme | http://sprunge.us/HeFG |
| 20:27 | KBme | uh |
| 20:27 | KBme | ok |
| 20:27 | KBme | jnettlet, i'll check the backports config if it uses builting regdom or not |
| 20:28 | KBme | i'll ping you if I have more questions? |
| 20:28 | jnettlet | It also looks like it is trying to do channel bonding perhaps? I see it trying channel 5 and then 2 |
| 20:28 | jnettlet | KBme, sure keep me updataed |
| 21:15 | KBme | jnettlet, http://sprunge.us/IEfG |
| 21:15 | KBme | i'll check channel bonding |
| 21:15 | KBme | now it has correct reg |
| 21:16 | KBme | iw reg get |
| 21:16 | KBme | country FR: DFS-ETSI |
| 21:18 | jnettlet | yes that looks fine, but I see. WPA: 4-Way Handshake failed - pre-shared key may be incorrect |
| 21:19 | KBme | yep |
| 21:19 | KBme | the key is correct. |
| 21:19 | KBme | I have two interfaces on the same machine, both using the same wpa configuration |
| 21:20 | KBme | (wpa configuration = wpa_supplicant configuration) |
| 21:20 | KBme | jnettlet, |
| 21:26 | jnettlet | KBme, are your clients trying to authenticate with wpa2? That would require a passphrase of 8 characters. |
| 21:27 | KBme | I have a passphrase of 9 characters |
| 21:27 | jnettlet | the one in the wpa_supplicant.conf you sent me was only 7 |
| 21:28 | KBme | I changed it ... |
| 21:28 | KBme | that's the only thing I changed, though |
| 21:29 | KBme | also, do you know why, when I do panic=10 in the kernel boot command line and the kernel oopses the bootloader seems to not load the kernel. it hangs at loading the kernel. |
| 21:30 | jnettlet | does it read the kernel and start executing it and then hang, or hangs in u-boot trying to access the SDHC card? |
| 21:30 | KBme | not really sure. |
| 21:30 | KBme | I'm pretty sure u-boot fails |
| 21:31 | KBme | if I push reset it boots fine |
| 21:35 | jnettlet | can you log the entire console sequence and send it to me please? |
| 21:36 | KBme | jnettlet, do you mean dmesg? |
| 21:36 | KBme | also the kernel output at initialization? |
| 21:36 | jnettlet | KBme, no log the output of the serial console if you have one connected |
| 21:36 | KBme | same |
| 21:37 | KBme | jnettlet, it's the same as dmesg |
| 21:37 | jnettlet | no, because the serial console will give me the output of u-boot |
| 21:37 | KBme | yep |
| 21:37 | KBme | right on |
| 21:37 | jnettlet | and will show me the shutdown panics etc |
| 21:37 | jnettlet | thanks |
| 21:37 | KBme | jnettlet, i'll send it by mail if that's ok |
| 21:38 | jnettlet | yes preferable |
| 21:42 | KBme | jnettlet, done |
| 21:42 | jnettlet | thanks |
| 21:46 | KBme | jnettlet, also when rebooting from panic it hangs at Starting kernel ... |
| 21:47 | jnettlet | KBme, okay so the kernel has loaded but it is hanging on initialization. |
| 21:48 | jnettlet | You are compiling your own kernel right? I would need you to enable kernel low level debugging and early printk in the kernel config |
| 21:48 | jnettlet | and then add debug earlyprintk to your kernel commandline |
| 21:49 | KBme | jnettlet, so I get the sema exact issue with backports as without. should I keep backports? |
| 21:50 | jnettlet | KBme, I wouldn't |
| 21:50 | KBme | yep |
| 21:50 | jnettlet | this may be a wpasupplicant bug |
| 21:51 | KBme | I thought of that, but why with one interface and not the other? |
| 21:51 | KBme | I also tried using wext driver for the interface. no luck |
| 21:52 | jnettlet | okay. I am finishing something up tonight. Tomorrow I will take some time and test with the board you sent me. |
| 21:53 | KBme | I'll try what you said but it'll take a while to reconfigure and rebuild the kernel &c |
| 21:53 | KBme | jnettlet, you have a board with built-in wifi? |
| 21:53 | jnettlet | sure. whenever you have some output, or any questions ping me |
| 21:53 | KBme | so you have two wifi interfaces? |
| 21:54 | KBme | I think our wpa_supplicant is latest upstream |
| 21:54 | jnettlet | I have plenty of SOMs with wifi. Or I can add a USB device for testing |
| 21:54 | KBme | yeap. ok. |
| 21:54 | jnettlet | does the ath9k interface work in AP mode if it is by itself? |
| 21:54 | KBme | but just so I know. |
| 21:54 | jnettlet | okay |
| 21:54 | KBme | because we have one wifi som left over and I wonder whether it's for the machine you have or not |
| 21:55 | KBme | I don't know about AP mode |
| 21:55 | jnettlet | don't worry about that. I have a stack of soms |
| 21:55 | jnettlet | oh you are using both in client mode? |
| 21:55 | KBme | yep. for now. |
| 21:55 | KBme | then we will be using the peer to peer mode I think |
| 21:55 | jnettlet | okay easy enough to test for that |
| 21:55 | KBme | ad-hoc |
| 21:56 | jnettlet | okay, we do support wifi-direct as well |
| 21:56 | KBme | yeah, not sure what is used. it's going to be a B.A.T.M.A.N. mesh |
| 21:56 | jnettlet | sure |