Ireng

Ok, thanks and looking forward to testing your next release! I am going to try the realtek driver for my ALFA USB adapter with this image! regards, hitam4450

Igor, when you are going to release the DEBIAN (Jessie) image? regards, hitam4450

Ok, I got it!

Hi, Could you please help me to change the content of resolv.conf to my gateway/nameserver. Manually editing does not work resp. will be always overwritten! Many thanks! regards, hitam4450

UBUNTU Image: flawless boot including WORKING Display! Many, many thanks for your help! regards, hitam4450

Sorry, no change ! The first boot messages (uboot) showed up and Starting kernel ------> No display! regards, hitam4450

As I mentioned, I tried to boot the image in 2 different cubies, however with the same set of cables and power supply! Just to make sure it is no hardware problem of one system! regards, hitam4450

Hi Igor, thanks for your reply and help! All what is different is the image! ALL connectors, (HDMI--> VGA, HDMI -->DVI; Ethernet, USB Keyboard, Power) are and remained still the same! Prior image e.g.Linux cubie3 3.4.105-cubieboard #8 SMP PREEMPT Fri Jan 23 06:11:42 EST 2015 armv7l GNU/Linux works flawless! regards, hiatm4450

Ok Igor, and many thanks for your help! I'll let you asap I tried your suggestion. regads, hitam4450

What about a DEBIAN image?? This one is the UBUNTU image! problem was with http://mirror.igorpecovnik.com/Cubietruck_Debian_4.1_jessie_3.4.108.zip Regards, hitam4450

Hi Igor, thanks for your suggestion. Ok, I will try it! I tried the last version from your webseite (4.1). Please wait for a while for my feedback! reagds, hitam4450

I noticed, that there had been changes of the display driver in the latest kernel version (gihub). regards, hitam4450

I tried both of my other 2 cubies with the latest image -- result is always the same - NO Display!

HDMI is plugged in firmly! (in both cases!? Regards, hitam4450

Hi Igor, I grabbed your 4.1 image, flashed it onto the microsd Card and boot the cubietruck. However, I received the message from my display: Out of specification: 67.5kHz / 60 Hz. The first boot is ok, but after starting the kernel the screen turns black and above mentioned message apears. This happens on the analouge (VGA) input and on the digital input (DVI) as well. How to fix the problem?? I never had any display problems with all your images. never! This is the first time. I might to use your 4.0 image to return into operation again. regards, hitam4450

Hi Igor, thank you for your comment! Allwinner A80 based devices are getting even mor epopular. Cubitech is going to release the Cubietruck+ (aka cubieboard 5, see http://cubietech.com)in the future. That is why I think the MK 80 Le might be a device which can be or should be supported and included into the group of hardware devices. regards, hitam4450

HI, what do you (Igor) think about supporting e.g. the following devices from Rikomagic with your nicely developped DEBIAN image: http://www.rikomagic.com/en/product/showpro_id_59_pid_19.html CPU: RK3288 Quad Core http://www.rikomagic.com/en/product/showpro_id_70_pid_22.html CPU: Allwinner A80 Octa Core Regards, Ireng

Output fro iw list: cubie5:~# iw list Wiphy phy1 Band 1: Capabilities: 0x1862 HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT TX/RX MCS rate indexes supported: 0-15, 32 Frequencies: * 2412 MHz [1] (20.0 dBm) * 2417 MHz [2] (20.0 dBm) * 2422 MHz [3] (20.0 dBm) * 2427 MHz [4] (20.0 dBm) * 2432 MHz [5] (20.0 dBm) * 2437 MHz [6] (20.0 dBm) * 2442 MHz [7] (20.0 dBm) * 2447 MHz [8] (20.0 dBm) * 2452 MHz [9] (20.0 dBm) * 2457 MHz [10] (20.0 dBm) * 2462 MHz [11] (20.0 dBm) * 2467 MHz [12] (20.0 dBm) (no IR) * 2472 MHz [13] (20.0 dBm) (no IR) * 2484 MHz [14] (20.0 dBm) (no IR) Bitrates (non-HT): * 1.0 Mbps * 2.0 Mbps * 5.5 Mbps * 11.0 Mbps * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps Band 2: Capabilities: 0x1862 HT20/HT40 Static SM Power Save RX HT20 SGI RX HT40 SGI No RX STBC Max AMSDU length: 7935 bytes DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 16 usec (0x07) HT TX/RX MCS rate indexes supported: 0-15, 32 Frequencies: * 5170 MHz [34] (disabled) * 5180 MHz [36] (20.0 dBm) (no IR) * 5190 MHz [38] (20.0 dBm) (no IR) * 5200 MHz [40] (20.0 dBm) (no IR) * 5210 MHz [42] (20.0 dBm) (no IR) * 5220 MHz [44] (20.0 dBm) (no IR) * 5230 MHz [46] (20.0 dBm) (no IR) * 5240 MHz [48] (20.0 dBm) (no IR) * 5260 MHz [52] (disabled) * 5280 MHz [56] (disabled) * 5300 MHz [60] (disabled) * 5320 MHz [64] (disabled) * 5500 MHz [100] (disabled) * 5520 MHz [104] (disabled) * 5540 MHz [108] (disabled) * 5560 MHz [112] (disabled) * 5580 MHz [116] (disabled) * 5600 MHz [120] (disabled) * 5620 MHz [124] (disabled) * 5640 MHz [128] (disabled) * 5660 MHz [132] (disabled) * 5680 MHz [136] (disabled) * 5700 MHz [140] (disabled) * 5745 MHz [149] (20.0 dBm) (no IR) * 5765 MHz [153] (20.0 dBm) (no IR) * 5785 MHz [157] (20.0 dBm) (no IR) * 5805 MHz [161] (20.0 dBm) (no IR) * 5825 MHz [165] (20.0 dBm) (no IR) * 5920 MHz [184] (disabled) * 5940 MHz [188] (disabled) * 5960 MHz [192] (disabled) * 5980 MHz [196] (disabled) * 6000 MHz [200] (disabled) * 6020 MHz [204] (disabled) * 6040 MHz [208] (disabled) * 6060 MHz [212] (disabled) * 6080 MHz [216] (disabled) Bitrates (non-HT): * 6.0 Mbps * 9.0 Mbps * 12.0 Mbps * 18.0 Mbps * 24.0 Mbps * 36.0 Mbps * 48.0 Mbps * 54.0 Mbps max # scan SSIDs: 9 max scan IEs length: 2304 bytes Retry short limit: 7 Retry long limit: 4 Coverage class: 0 (up to 0m) Supported Ciphers: * WEP40 (00-0f-ac:1) * WEP104 (00-0f-ac:5) * TKIP (00-0f-ac:2) * CCMP (00-0f-ac:4) Available Antennas: TX 0 RX 0 Supported interface modes: * IBSS * managed * AP * monitor * P2P-client * P2P-GO software interface modes (can always be added): * monitor interface combinations are not supported Supported commands: * new_interface * set_interface * new_key * start_ap * new_station * set_bss * join_ibss * set_pmksa * del_pmksa * flush_pmksa * remain_on_channel * frame * set_channel * connect * disconnect Supported TX frame types: * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0 Supported RX frame types: * IBSS: 0xd0 * managed: 0x40 0xd0 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0 * P2P-client: 0x40 0xd0 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0

Hi Igor! Thanks for your support. The current configuration and driver shows a 5 GHz WLAN available. The only problem is, that I can not connect from my mobile phone or tab to the AP. It always refused the connection. Perhaps a misconfiguration of the network?? The mobile devices are ac capable devices. Regards, Ireng PS. The reason why I want to use 5 GHZ network is because the 2,4 GHZ is over crowded in my location. Nobody is using 5 GHZ.

Hi Igor" Did you have a chance to look at my last postings? Regards, Ireng

Now the Infor in the router changed (without my interaction) But still no access to the net! regards, Ireng

Hi Igor! Thanks for your answer: Enclosed you'll find my network configuration from /etc/network/interfaces: #Loopback device auto lo iface lo inet loopback #LAN Device eth0 auto eth0 iface eth0 inet static address 192.168.175.25 netmask 255.255.255.0 broadcast 192.168.175.255 network 192.168.175.0/24 gateway 192.168.175.1 nameserver 192.168.175.1 #WLAN Device 1 (USB Adapter ALFA AWUS036AC) auto wlx00c0ca8184e0 allow-hotplug wlx00c0ca8184e0 iface wlx00c0ca8184e0 inet manual address 0.0.0.0 ##Bridge br0 fuer Interfaces ETH0 und wlx00c0ca8184e0 auto br0 iface br0 inet static address 192.168.175.191 netmask 255.255.255.0 network 192.168.175.0/24 broadcast 192.168.175.255 gateway 192.168.175.1 nameserver 192.168.175.1 bridge_ports eth0 wlx00c0ca8184e0 bridge_fd 0 bridge_stp n At this time I even can not access the net! Enclosed you'll find a screenshot from my router! strange, that br0 and cubie5 share the same IP address! ifconfig: br0 Link encap:Ethernet HWaddr 00:c0:ca:81:84:e0 inet addr:192.168.175.191 Bcast:192.168.175.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:caff:fe81:84e0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1968 errors:0 dropped:0 overruns:0 frame:0 TX packets:1428 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:155003 (151.3 KiB) TX bytes:244568 (238.8 KiB) eth0 Link encap:Ethernet HWaddr 02:05:06:c0:f8:68 inet addr:192.168.175.25 Bcast:192.168.175.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2391 errors:0 dropped:0 overruns:0 frame:0 TX packets:1577 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:273843 (267.4 KiB) TX bytes:270930 (264.5 KiB) Interrupt:117 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:105 errors:0 dropped:0 overruns:0 frame:0 TX packets:105 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10200 (9.9 KiB) TX bytes:10200 (9.9 KiB) wlx00c0ca8184e0 Link encap:Ethernet HWaddr 00:c0:ca:81:84:e0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:44 errors:0 dropped:34 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 TX bytes:6320 (6.1 KiB) regards, Ireng Cubie5 is the system in trouble! :-)

Thanks, Igor for your advice. Checking the MAkefile I found 2 otions for the ARM Architecture: CONFIG_PLATFORM_ARM_SUNxI = n CONFIG_PLATFORM_ARM_SUN6I = n Which one is the right one for the cubietruck to set?? Thanks in advance for your advice! regards, Ireng

Hi Igor, at the moment the WLAN AP is working in 802.11.a mode(5 GHZ) including the current installed driver (rtl8812au-linux). However I still can not connect with my TAB S or Glaxay mobile phone. /usr/sbin/hostapd-rt /etc/hostapd.conf-rt starts the WALN-AP. Please have a look at the enclosed hostapd.conf-rt, maybe I made some mistakes or overlooked an option: ctrl_interface=/var/run/hostapd ctrl_interface_group=0 interface=wlx00c0ca8184e0 bssid=00:c0:ca:81:84:e0 ssid=Office5 channel=44 noscan=1 wpa=2 wpa_passphrase=XXXXXXXXXXXXXXX bridge=br0 wmm_enabled=1 #driver=rtl8821au #driver=rtl8821au #driver=8812au #driver=rtl8812au #driver=RTL871X #driver=nl80211 beacon_int=100 hw_mode=a #ieee80211d=1 ieee80211n=1 #ieee80211ac=1 country_code=DE wme_enabled=1 ht_capab=[sHORT-GI-40][sHORT-GI-40][HT40+] #ht_capab=[HT40+] wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP wpa_group_rekey=86400 ### hostapd event logger configuration logger_syslog=127 logger_syslog_level=2 logger_stdout=127 logger_stdout_level=2 the strange looking WLAN devices name was derived from the driver rinstallation. ifconfig results into the following output: br0 Link encap:Ethernet HWaddr 00:c0:ca:81:84:e0 inet addr:192.168.XXX.YYY Bcast:192.168.175.255 Mask:255.255.255.0 inet6 addr: fe80::2c0:caff:fe81:84e0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5558 errors:0 dropped:0 overruns:0 frame:0 TX packets:715 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:617108 (602.6 KiB) TX bytes:81552 (79.6 KiB) eth0 Link encap:Ethernet HWaddr 02:05:06:c0:f8:68 inet addr:192.168.XXX.ZZ Bcast:192.168.175.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10877 errors:0 dropped:0 overruns:0 frame:0 TX packets:1734 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1725206 (1.6 MiB) TX bytes:134456 (131.3 KiB) Interrupt:117 Base address:0xc000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:528 errors:0 dropped:0 overruns:0 frame:0 TX packets:528 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:52632 (51.3 KiB) TX bytes:52632 (51.3 KiB) wlx00c0ca8184e0 Link encap:Ethernet HWaddr 00:c0:ca:81:84:e0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:36 errors:0 dropped:0 overruns:0 frame:0 TX packets:879 errors:0 dropped:1250 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:840 (840.0 TX bytes:104805 (102.3 KiB) Thanks for your help and support! regards, Ireng

Hi Igor, thank you for your reply and support! Since I opened this subject already twice on cubieforums.com, I thin we should discuss the issue here and in the other two threads should refere to her! I tried the ALFA driver, and it is a complete mess. Currently I try get the adapter to work with the rtl8812au-linux driver. However, I'll give your reference https://github.com/gnab/rtl8812au a trial as well and will report back here later. Thanks for your help, support and references. I'll keep this thread updated! regards, Ireng