chiefwigms Posted October 9, 2015 Share Posted October 9, 2015 Using Armbian_4.4_Udoo_Debian_jessie_3.14.28 - Wicd doesn't detect any networks (/etc/network/interfaces has wlan0 commented out). If i setup /etc/network/interfaces and edit /etc/hostapd.conf and /etc/init.d/hostapd, I can get the udoo to authenticate to my wireless network, but I can't ping/resolve/browse anything but google.com Using CLI images - I can't get my network card to auth at all. Any idea what happened - a few months ago wifi was working perfectly. Also - is there anyway to modify the startup job to raise network interfaces to have a time limit? Occasionally boot will go indefinitely. Link to comment Share on other sites More sharing options...
Igor Posted October 9, 2015 Share Posted October 9, 2015 This kernel is new and this is the first build of this kernel so problems are possible. I need to check once again. Few general hints. Try not to use bonding at first and don't mess with interfaces settings if you are using WICD. What you get from: iwconfig It's also possible that you have wlan1 or wlan2 instead of wlan0. Link to comment Share on other sites More sharing options...
chiefwigms Posted October 20, 2015 Author Share Posted October 20, 2015 So i tried the updated desktop image and wifi works fine now! However when I rebuild the next kernel to add w1 in, no dice. Should I stick with the default kernel? Were there any patches needed to get wicd working? Link to comment Share on other sites More sharing options...
Igor Posted October 20, 2015 Share Posted October 20, 2015 No, I only change was in (proper) configuration.Regarding W1 ... check also if you have those settings in your DTB. https://github.com/patrykk/linux-udoo/commit/697c08d940f67b61690a66a7ec4cdc3ac7f42535 In another words - make sure you upgrade DTB package too. Link to comment Share on other sites More sharing options...
Recommended Posts