SmashGuy

Members
  • Content Count

    9
  • Joined

  • Last visited

About SmashGuy

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ok, new problem. Tried to get the linux headers: apt-get install linux-headers-generic It then installed linux-headers-4.4.0-93. Turns out that 4.4.73 is already installed in the Armbian distribution, but it is missing the header files found in /usr/src/linux-headers-4.4.73-mvebu64/arch/arm/include/asm/. A few of these files are used by the arm85 versions, so it prevents building the wireless driver from source. Any know how I can fix this? If we can find the 4.4.73 arm files somewhere, I can copy them into the file system. Hacky, but it will work. Fix: apt-get install linux-header-generic -> installs 4.4.0-93 header files Fortunately, these seem to work. You have to recursively copy all of the files in linux-headers-4.4.0-93/arch/arm/include/asm/* to the same location in linux-headers-4.4.73/arch/arm/include/asm. Next, there is a bug in /arm64/include/asm/opcodes.h that points to the wrong directory. Add an additional "../" to the include directory in that file. Now you can build a stable wifi driver for the Edimax 7811Un dongle (ie: https://github.com/pvaret/rtl8192cu-fixes). This fix is probably needed for a lot of other things as well though.
  2. Sure, I'll take a crack at it once I fixed some new stability issues I found. The Edimax card is going down pretty regularly and taking dns with it...
  3. This is a pretty good start! A little cryptic for the uninitiated though. I have a lot of additional tips and settings I could add. I now have a working router with dnsmasq which supports both wireless and ethernet wan connections. I'm able to connect lan0/1 by cable but I have not succeeded in getting a second wireless card to work due to the error -110 issue noted above (very strange that USB 2.0 is fine but USB 3.0 is not, I would have expected the opposite). Right now it seems to be really stable, though I still experience seemingly random issues when I dis/reconnect cables. That's rare though so a very good start.
  4. It would get a lot more contributions if there was a step-by-step guide to setting up Armbian on the EspressoBin and getting more than just a minimally viable install going. For instance, not being able to upgrade right now due to the different Armada driver is a big deal. Everyone seems to have problems getting the LAN and WAN ports working independently (having both wan and eth0 interfaces is unique to this board, as far as I know). CPUFreq needs to be faster out of the box... defaulting to 200Mhz is crazy. I haven't experienced any overheating at all running at 1000Mhz. The bootup timeout on the eth0 interface defaults to 5 minutes as well. These are just the problems I encountered so far. Not insurmountable by any means, but I bet there are a ton of people who tried to boot up their EspressoBin and just set it aside because of things like this.
  5. I'm using /etc/network/interfaces right now. Got wifi and wan working, but I'm not having any luck getting a connection through lan0 or lan1 to my local PC. This is the output of /var/log/syslog when I plug in the cable: Sep 6 13:44:44 espressobin kernel: [ 830.336999] dsa dsa@0 lan1: Link is Up - 100Mbps/Full - flow control r Sep 6 13:44:44 espressobin kernel: [ 830.341862] br0: port 2(lan1) entered blocking state Sep 6 13:44:44 espressobin kernel: [ 830.341879] br0: port 2(lan1) entered forwarding state Sep 6 13:44:44 espressobin NetworkManager[1494]: <info> [1504705484.0595] device (lan1): link connected Sep 6 13:44:44 espressobin NetworkManager[1494]: <info> [1504705484.0598] device (br0): link connected Sep 6 13:44:45 espressobin ntpd[2680]: Listen normally on 4 br0 192.168.101.1:123 And here's my /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet manual #hwaddress ether f0:ad:4e:03:6a:9f auto wan iface wan inet dhcp pre-up /sbin/ifconfig wan up auto wlan0 iface wlan0 inet dhcp wpa-ssid "xxxx" wpa-psk "xxxx" auto lan0 iface lan0 inet manual pre-up /sbin/ifconfig lan0 up auto lan1 iface lan1 inet manual pre-up /sbin/ifconfig lan1 up auto br0 iface br0 inet static bridge_ports lan0 lan1 bridge_waitport 0 address 192.168.101.1 network 192.168.101.0 netmask 255.255.255.0 dns-nameservers 192.168.101.1 And finally ifconfig br0: br0 Link encap:Ethernet HWaddr f0:ad:4e:03:64:7f inet addr:192.168.101.1 Bcast:192.168.101.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:316 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:61758 (61.7 KB) TX bytes:2646 (2.6 KB) Seems the devices are seeing each other but nothing else happens after that. Anyone have any ideas? Edit: Looks like DHCP queries are coming in but dnsmasq is not receiving (or not responding) to them. Edit: Resolved! The /etc/network/interfaces file above works fine and I can now connect via lan1. The problem was a configuration setting in dnsmasq that was not allowing it to respond to that interface.
  6. Ok, I don't recommend that anyone upgrades as it appears that none of the beta drivers are included when upgrading, so you lose core functionality (such as cpufreq support). I'm wiping and reverting back to the original version. The upgrade didn't fix the Edimax problem anyway.
  7. Ok, I've run into one more problem that maybe someone here can comment on. And my apologies in advance because I'm not really a hardware guy so linux kernels are beyond my current skillset. In an effort to get the USB 3.0 port to recognize the Edimax wifi card, I performed an upgrade (apt-get upgrade). Worked fine, supposedly. However, now I cannot boot because the SD card is not recognized. It gets to the end of the boot process and gives me this: Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! [ 43.350941] usbcore: registered new interface driver usbhid [ 43.356740] usbhid: USB HID core driver A quick check on /dev shows that there are no files starting with either mmc* or sd*. Any clues on how to get the SD card recognized again? And are upgrades hopeless at this point? Edit: Just checked /proc/devices and mms is showing up: 133 sd 134 sd 135 sd 179 mmc 252 nvme 253 virtblk 254 mdp Fix: I solved it and the upgrade worked! The problem is that the Armbian /boot directory contains the directory dtb-4.4.84-mvebu64/*. My environment variables were pointing to an earlier version (dtb-4.4.73) so the drivers weren't being loaded. To fix this, I aborted autoboot and while in uboot, changed the fdt_name environment variable to point to the correct version. It booted up just fine.
  8. I ran into the same problem while waiting for eth0 with no network cable plugged in. The workaround is to edit /etc/systemd/system/network-online.target.wants/networking.service. Change the timeout in the final line to something shorter, like "5sec". __ Regarding the heat test, I shot a laser thermometer at the SOC and get a reading of around 58C. Has been idling at 1000Mhz all day. I'm running into a different problem. I have an Edimax 7811Un wifi adapter plugged into the USB 2.0 port and it works fine. If I plug an identical unit into the USB 3.0 port, I run into a insufficient power error (error -110). The first device is recognized with lsusb, the second isn't. Any ideas? [ 5.697291] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 5.787901] usb 2-1: new high-speed USB device number 2 using xhci-hcd [ 10.900013] usb 2-1: device descriptor read/64, error -110 [ 26.120022] usb 2-1: device descriptor read/64, error -110 [ 26.339981] usb 2-1: new high-speed USB device number 3 using xhci-hcd [ 31.456008] usb 2-1: device descriptor read/64, error -110 [ 46.676011] usb 2-1: device descriptor read/64, error -110 [ 46.895982] usb 2-1: new high-speed USB device number 4 using xhci-hcd [ 51.904033] xhci-hcd d0058000.usb3: Timeout while waiting for setup device command [ 57.120025] xhci-hcd d0058000.usb3: Timeout while waiting for setup device command [ 57.331950] usb 2-1: device not accepting address 4, error -62 [ 57.503982] usb 2-1: new high-speed USB device number 5 using xhci-hcd [ 62.512038] xhci-hcd d0058000.usb3: Timeout while waiting for setup device command [ 67.727928] xhci-hcd d0058000.usb3: Timeout while waiting for setup device command [ 67.935954] usb 2-1: device not accepting address 5, error -62 [ 67.942290] usb usb2-port1: unable to enumerate USB device [ 72.523525] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1 [ 72.586801] usbcore: registered new interface driver rtl8192cu [ 105.334452] usb 2-1: new high-speed USB device number 6 using xhci-hcd [ 110.446365] usb 2-1: device descriptor read/64, error -110 [ 110.666355] usb 2-1: device descriptor read/64, error -71 [ 110.886321] usb 2-1: new high-speed USB device number 7 using xhci-hcd [ 110.998338] usb 2-1: device descriptor read/64, error -71 [ 116.218213] usb 2-1: device descriptor read/64, error -110 [ 116.438191] usb 2-1: new high-speed USB device number 8 using xhci-hcd [ 116.438321] usb 2-1: Device not responding to setup address. [ 116.642321] usb 2-1: Device not responding to setup address. [ 116.846188] usb 2-1: device not accepting address 8, error -71 [ 117.018181] usb 2-1: new high-speed USB device number 9 using xhci-hcd [ 122.030090] xhci-hcd d0058000.usb3: Timeout while waiting for setup device command [ 127.245971] xhci-hcd d0058000.usb3: Timeout while waiting for setup device command [ 127.449951] usb 2-1: device not accepting address 9, error -62 [ 127.455901] usb usb2-port1: unable to enumerate USB device