alexPixel Posted March 16, 2018 Posted March 16, 2018 I have a orange pi lite2. I hoped that usb3 is working with the latest images (and least wifi does). The strange thing is when I connect a usb3 device it doesn't show up with super speed. root@OrangePi:/mnt# lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=sunxi-ohci/1p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=sunxi-ohci/1p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=sunxi-ehci/1p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=sunxi-ehci/1p, 480M Dev 2 is a M.2 device in a usb3 case. You see that nothing is connected to Bus 06, but I definitely connected it to the usb 3 port! Can somebody else connect a usb3 device and see with "lsusb -t" at what speed the device is connected. thanks
tkaiser Posted March 16, 2018 Author Posted March 16, 2018 1 hour ago, alexPixel said: I definitely connected it to the usb 3 port! Look into the USB3-A receptacle please. The huge contacts are for Hi-Speed (480 Mbps), the few tiny ones are for SuperSpeed (5 Gbps). Makes absolutelty no sense at all (you want the connection using the way higher link rate to use reliable contacts) but that's how USB3-A has been designed. Maybe you're just running into the usual USB3-A connector crappiness issue and re-inserting the cable with some force already fixes it? BTW: providing dmesg output (or armbianmonitor -u) would be useful.
alexPixel Posted March 16, 2018 Posted March 16, 2018 thanks for the hints @tkaiser I tried to reinserting the cable a few times, but nothing changed. I also tried another cable. I also looked at the connections on cable and ports, they seem to look fine. When I connect the device to my linux machine it works as expected. Here is the dmesg output of the orange pi lite2 with kernel Linux 3.10.65, with the image from orangepi Ubuntu Server from 2018-03-12 [12307.950096] usb 5-1: new high-speed USB device number 4 using xhci-hcd [12308.001036] usb 5-1: New USB device found, idVendor=125f, idProduct=a37a [12308.001063] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [12308.001081] usb 5-1: Product: USB [12308.001098] usb 5-1: Manufacturer: JMicron [12308.001115] usb 5-1: SerialNumber: DD564198838738739F [12308.030823] usb-storage 5-1:1.0: USB Mass Storage device detected [12308.031067] scsi2 : usb-storage 5-1:1.0 [12309.030858] scsi 2:0:0:0: Direct-Access INTEL SS DSCKKW512G8 3203 PQ: 0 ANSI: 6 [12309.032869] sd 2:0:0:0: [sda] 1000215216 512-byte logical blocks: (512 GB/476 GiB) [12309.033347] sd 2:0:0:0: [sda] Write Protect is off [12309.033372] sd 2:0:0:0: [sda] Mode Sense: 47 00 00 08 [12309.033823] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [12309.042505] sda: sda1 sda2 [12309.045850] sd 2:0:0:0: [sda] Attached SCSI disk on my linux machine it looks correct with kernel Linux 4.4.0-116-generic lsusb -t /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M |__ Port 1: Dev 3, If 0, Class=Mass Storage, Driver=uas, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M [906487.979366] usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd [906487.996183] usb 4-1: New USB device found, idVendor=125f, idProduct=a37a [906487.996192] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [906487.996197] usb 4-1: Product: USB [906487.996202] usb 4-1: Manufacturer: JMicron [906487.996207] usb 4-1: SerialNumber: DD564198838738739F [906487.998450] scsi host7: uas [906487.999145] scsi 7:0:0:0: Direct-Access INTEL SS DSCKKW512G8 3203 PQ: 0 ANSI: 6 [906488.000287] sd 7:0:0:0: Attached scsi generic sg3 type 0 [906488.000428] sd 7:0:0:0: [sdd] 1000215216 512-byte logical blocks: (512 GB/477 GiB) [906488.000439] sd 7:0:0:0: [sdd] 4096-byte physical blocks [906488.001004] sd 7:0:0:0: [sdd] Write Protect is off [906488.001013] sd 7:0:0:0: [sdd] Mode Sense: 53 00 00 08 [906488.001319] sd 7:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [906488.005007] sdd: sdd1 sdd2 [906488.006719] sd 7:0:0:0: [sdd] Attached SCSI disk Does somebody else has the same problem with the lite 2 or does usb 3 work?. Not sure if its a driver/software problem or hardware. I will try the android image next.
joaofl Posted March 27, 2018 Posted March 27, 2018 Video drivers were added to the H6 GPU at Allinner's git repository: https://github.com/Allwinner-Homlet/H6-CedarC Is there any progress with Armbian for the H6 boards?
Xalius Posted March 28, 2018 Posted March 28, 2018 14 hours ago, joaofl said: Video drivers were added to the H6 GPU at Allinner's git repository: https://github.com/Allwinner-Homlet/H6-CedarC Is there any progress with Armbian for the H6 boards? Those are not really video drivers, it's more or less just the glue layer between Cedarx (AW's proprietary video libraries) and the kernel drivers for Android BSP (Linux 3.10.x).... so it's more or less just a reference to look up some things that are not in the documentation (which might be released soon...) 1
Igor Posted March 28, 2018 Posted March 28, 2018 15 hours ago, joaofl said: Is there any progress with Armbian for the H6 boards? When we have at least mainline u-boot support ... it's not near to copy/paste operation. Modern kernel support is in a very infant state. https://groups.google.com/forum/#!topic/linux-sunxi/6StQyINyin8 1
Anodev Posted March 29, 2018 Posted March 29, 2018 I was able to get ROOT rights to Android from Xunlong image(OrangePi OnePlus), and install GAPPS! 1. Remove the boot.img from this firmware 2. Install the Magisk Manager and patch boot.img 3. Turn on USB0 mode in the developer settings 4. Run adb and reboot into the bootloader 5. Flash patched_boot.img via fastboot Then install GAPPS manually patched_boot.img boot_xunlong.img 2
kripo Posted March 31, 2018 Posted March 31, 2018 On 28.3.2018 at 12:46 PM, Igor said: When we have at least mainline u-boot support ... it's not near to copy/paste operation. Modern kernel support is in a very infant state. https://groups.google.com/forum/#!topic/linux-sunxi/6StQyINyin8 I just want to thank you for your effort to bring armbian to the new H6 boards. cant wait...
danielc_123 Posted April 9, 2018 Posted April 9, 2018 On 29/3/2018 at 4:07 AM, Anodev said: ..... Then install GAPPS manually ..... Hello Anodev, Could you please expand more information about how did you reached to install GAPPS manually? I followed your instructions: I sucessfully installed MagiskManager, patched and re-flash boot_patched.img. Then I tried to install Gapps (7.0, Micro, ARM32) from opengapps.org by using recovery mode but it didn't. Should I install 64bit Gapps? or Dynamic Gapps? or any MagiskManager module before installing Gapps? Thank you in advance for any help. Daniel
constantius Posted April 10, 2018 Posted April 10, 2018 (edited) Is there a topic about H6 orangepi boards? I meana Orangepi lite 2 and Orangepi One Plus? Both with H6 Allwinner CPU? Can we expect armbian for such devices????? Edited April 10, 2018 by constantius merged here
Igor Posted April 24, 2018 Posted April 24, 2018 First Pine H64/H6 mainline testing images based on @Icenowy patchset https://dl.armbian.com/pineh64/ Boot log: http://ix.io/18DU 8
tkaiser Posted April 25, 2018 Author Posted April 25, 2018 18 hours ago, Igor said: Boot log: http://ix.io/18DU USB3/XHCI is not active according to the boot log. Seems PHY_SUN50I_USB3 is not set?
Igor Posted April 25, 2018 Posted April 25, 2018 1 hour ago, tkaiser said: USB3/XHCI is not active according to the boot log. Seems PHY_SUN50I_USB3 is not set? True, I notice that USB3 port was not working. I was happy that it booted in the first place. I already merged into our main sunxi DEV branch (attached back to upstream master) and will try to remake this with a working USB3. 3
pfeerick Posted April 28, 2018 Posted April 28, 2018 (edited) Oh my, nice work! Actually booting into linux and not promptly bursting in flames... That in itself is an noteworthy milestone! Not sure of performance, but the processor is running very cool on 'idle' . barely warm to touch. No frequency or thermals yet, so it'll be interesting to see what is really going on. I don't think it was able to shut down properly on a 'sudo poweroff'... need the plug in a console cable to see what happened there. Addendum: Got the serial console working on the EXP header @ 115200 baud. It does 'power off' / "Starting Power-Off... [ 2557.657434] reboot: Power down", but continues to draw a health 0.8W or 170mA (basically the same as when it's idling, and leaves the green LED near the headphones jack lit. A forcible power off by pressing and holding the power button for ~8 seconds results in a drop to 0.18W or 32ma. Serial logs for Debian (first boot) and Ubuntu (rebooted). It looks like I booted the same build as Igor... Bionic... as I'm more partial to Ubuntu than Debian. My armbianmonitor dump is here, vanilla pineH64, nothing plugged in except for power and GbE via a switch : http://ix.io/18UC Edit re Debian: For the sake of completeness, I also booted the Debian build, and it's armbianmonitor log is http://ix.io/18V7 I can also report zero activity from the USB3 port. It is being powered, but there is no response/kernel messages when a device is plugged in, USB3, 2 or otherwise. On the other hand, this was the output from plugging something into the USB2 ports... Seems to be working fine (can see and mount drives) just the dwc3 error. == Lower USB Port == [Apr28 04:48] usb 3-1: new high-speed USB device number 2 using ehci-platform [ +0.160142] usb-storage 3-1:1.0: USB Mass Storage device detected [ +0.012355] scsi host0: usb-storage 3-1:1.0 [ +0.005677] dwc3 5200000.dwc3: failed to initialize core [ +1.007158] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ +0.004774] dwc3 5200000.dwc3: failed to initialize core [ +0.367311] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ +0.000978] sd 0:0:0:0: [sda] Write Protect is off [ +0.000008] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ +0.001013] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ +0.012624] sda: sda1 [ +0.003756] sd 0:0:0:0: [sda] Attached SCSI removable disk == Disconnect and Upper USB Port == [Apr28 04:49] usb 3-1: USB disconnect, device number 2 [ +2.625559] usb 1-1: new high-speed USB device number 2 using ehci-platform [ +0.160284] usb-storage 1-1:1.0: USB Mass Storage device detected [ +0.005631] scsi host0: usb-storage 1-1:1.0 [ +0.003775] dwc3 5200000.dwc3: failed to initialize core [ +1.027671] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ +0.002970] dwc3 5200000.dwc3: failed to initialize core [ +0.367868] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ +0.001101] sd 0:0:0:0: [sda] Write Protect is off [ +0.000008] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ +0.000993] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ +0.010520] sda: sda1 [ +0.003916] sd 0:0:0:0: [sda] Attached SCSI removable disk Edit re Debian: The Debian image from the didn't have the dwc3 errors when plugging into the USB2 ports... [Apr28 08:28] usb 3-1: new high-speed USB device number 2 using ehci-platform [ +0.159409] usb 3-1: New USB device found, idVendor=05e3, idProduct=0749, bcdDevice=15.32 [ +0.000009] usb 3-1: New USB device strings: Mfr=3, Product=4, SerialNumber=2 [ +0.000005] usb 3-1: Product: USB3.0 Card Reader [ +0.000005] usb 3-1: Manufacturer: Generic [ +0.000005] usb 3-1: SerialNumber: 000000001532 [ +0.000938] usb-storage 3-1:1.0: USB Mass Storage device detected [ +0.000994] scsi host0: usb-storage 3-1:1.0 [ +0.175901] usbcore: registered new interface driver uas [ +0.844075] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 1532 PQ: 0 ANSI: 6 [ +0.000708] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ +0.370255] sd 0:0:0:0: [sda] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) [ +0.000981] sd 0:0:0:0: [sda] Write Protect is off [ +0.000007] sd 0:0:0:0: [sda] Mode Sense: 21 00 00 00 [ +0.000994] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ +0.008896] sda: sda1 [ +0.004247] sd 0:0:0:0: [sda] Attached SCSI removable disk Just tried the "Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter" (from the pine64 store) for the first time, and it seems to have been just a plug an play affair even in this early stage... quick run of nmtui and it was up and running. == Plugging in USB Wifo, bottom USB2 port == [Apr28 05:01] usb 3-1: new high-speed USB device number 5 using ehci-platform [ +0.161519] dwc3 5200000.dwc3: failed to initialize core [ +0.256283] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ +0.007980] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ +0.002099] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ +0.000014] cfg80211: failed to load regulatory.db [ +1.350222] usb 3-1: USB disconnect, device number 5 [ +0.000496] usbcore: registered new interface driver 8812au [ +0.421349] usb 3-1: new high-speed USB device number 6 using ehci-platform [ +0.463789] dwc3 5200000.dwc3: failed to initialize core [ +0.117435] 8812au 3-1:1.0 wlx08107aff527a: renamed from wlan0 [ +0.089667] IPv6: ADDRCONF(NETDEV_UP): wlx08107aff527a: link is not ready [ +0.576959] IPv6: ADDRCONF(NETDEV_UP): wlx08107aff527a: link is not ready [ +0.000041] IPv6: ADDRCONF(NETDEV_CHANGE): wlx08107aff527a: link becomes ready [ +0.142635] IPv6: ADDRCONF(NETDEV_UP): wlx08107aff527a: link is not ready [Apr28 05:02] IPv6: ADDRCONF(NETDEV_CHANGE): wlx08107aff527a: link becomes ready == ip addr == 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 86:99:5f:3e:0e:2d brd ff:ff:ff:ff:ff:ff inet 192.168.0.122/24 brd 192.168.0.255 scope global dynamic noprefixroute eth0 valid_lft 84343sec preferred_lft 84343sec inet6 fe80::8eb6:99f:513a:2d7/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlx08107aff527a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 08:10:7a:ff:52:7a brd ff:ff:ff:ff:ff:ff inet 192.168.0.123/24 brd 192.168.0.255 scope global dynamic noprefixroute wlx08107aff527a valid_lft 85820sec preferred_lft 85820sec inet6 fe80::ff65:b46c:ed97:2d32/64 scope link noprefixroute valid_lft forever preferred_lft forever == lsusb == Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 006: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Edited April 28, 2018 by pfeerick added wifi info, debian, power notes, serial logs
kissste Posted May 4, 2018 Posted May 4, 2018 PineH64 - Booting from SD Card works well. But, trying to boot from EMMC and getting this: U-Boot SPL 2018.03-rc1-armbian (Apr 24 2018 - 21:55:29 +0200) DRAM: 4096 MiB, 3072 MiB usable Trying to boot from MMC2 mmc_load_image_raw_sector: mmc block read error SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### So, U-Boot loads something but then SPL is having trouble. Here is a boot from SD Card, which is fine: U-Boot SPL 2018.03-rc1-armbian (Apr 29 2018 - 22:12:29 +0200) DRAM: 4096 MiB, 3072 MiB usable Trying to boot from MMC1 INFO: PSCI: Powering off cluster 0 core 1 INFO: PSCI: Disabling power to cluster 0 core 1 INFO: PSCI: Powering off cluster 0 core 2 INFO: PSCI: Disabling power to cluster 0 core 2 INFO: PSCI: Powering off cluster 0 core 3 INFO: PSCI: Disabling power to cluster 0 core 3 NOTICE: BL31: v1.4(debug):c591d63 NOTICE: BL31: Built : 20:35:18, Apr 26 2018 INFO: ARM GICv2 driver initialized INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: errata workaround for 835769 was applied INFO: BL31: cortex_a53: errata workaround for 843419 was applied INFO: BL31: cortex_a53: errata workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2018.03-rc1-armbian (Apr 29 2018 - 22:12:29 +0200) Allwinner Technology CPU: Allwinner H6 (SUN50I) Model: Pine H64 DRAM: 3 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from FAT... Unable to use mmc 1:1... Failed (-5) In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... No controllers found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3100 bytes read in 207 ms (13.7 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 166 ms (0 Bytes/s) 11031 bytes read in 359 ms (29.3 KiB/s) ** File not found /boot/dtb/allwinner/overlay/sun50i-h6-fixup.scr ** 9230674 bytes read in 1224 ms (7.2 MiB/s) 15811072 bytes read in 1876 ms (8 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9230610 Bytes = 8.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49732000, end 49fff912 ... OK reserving fdt memory region: addr=4fa00000 size=69000 Loading Device Tree to 00000000496c6000, end 0000000049731fff ... OK Starting kernel ... Loading, please wait... starting version 237 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.31.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: recovering journal /dev/mmcblk0p1: clean, 34409/1711248 files, 337575/7562636 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. once running, EMMC is visible, partition table looks good to me. mmcblk1 is EMMC and mmcblk0 is SD Card steve@pineh64:~$ sudo fdisk /dev/mmcblk1 Command (m for help): p Disk /dev/mmcblk1: 14.5 GiB, 15518924800 bytes, 30310400 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xea8d319c Device Boot Start End Sectors Size Id Type /dev/mmcblk1p1 8192 2138111 2129920 1G 83 Linux Command (m for help): q steve@pineh64:~$ sudo fdisk /dev/mmcblk0 Command (m for help): p Disk /dev/mmcblk0: 29.1 GiB, 31293702144 bytes, 61120512 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xea8d319c Device Boot Start End Sectors Size Id Type /dev/mmcblk0p1 8192 60509279 60501088 28.9G 83 Linux
Igor Posted May 4, 2018 Posted May 4, 2018 On 28. 4. 2018 at 6:58 AM, pfeerick said: Actually booting into linux and not promptly bursting in flames... Development versions without active DVFS are usually clocked lower so performance wise we are not there yet. Reboot/power off troubles ... noticed. On 28. 4. 2018 at 6:58 AM, pfeerick said: I can also report zero activity from the USB3 port. It is being powered, but there is no response/kernel messages when a device is plugged in, USB3, 2 or otherwise. Yes, ack-ed. I am waiting for another big chunk of free time to dive back in and try to fix this. I also hope that someone else will join and try to move it forward. 5 hours ago, kissste said: But, trying to boot from EMMC and getting this: Support is enabled in configuration but it looks like implementation on this board needs few adjustments ... Thanks for trying out. 2
Vincen Posted May 25, 2018 Posted May 25, 2018 Hi I own an Orange PI One Plus but found it's not supported by armbian. I tried to find the nearest model but it looks to be the only one with H6 processor in it. Any chances to get that board supported in near future ? Thanks Vincèn
guidol Posted May 25, 2018 Posted May 25, 2018 45 minutes ago, Vincen said: Any chances to get that board supported in near future ? chances - I think yes....but near future - I dont think so:
Vincen Posted May 25, 2018 Posted May 25, 2018 56 minutes ago, guidol said: chances - I think yes....but near future - I dont think so: Hum looks like I went too fast in buying that board as Raspberry replacement Sitting on my desk since january and guess will stay there for a while
jeyjey Posted May 26, 2018 Posted May 26, 2018 Hi, I am trying to install linux drivers in H6. I would like to have Armbian in that board (OrangePi One Plus). The GPU is better than Odroid XU4, but the ram is only 1Gb. However I am trying to experiment its graphic card. I want use that because It is very cost/power effectively good. Is there anyone that experienced drivers for SOCs GPUs? And Why Armbian is not released for H6? Thanks.
TonyMac32 Posted May 26, 2018 Posted May 26, 2018 Because Linux support is not mature for the H6? It's hard to release a distro for something that doesn't have proper kernel support. :-). @Vincen, The Asus Tinker Board, and MQMaker MiQi have experimental video decoder and GPU support. I'm not as familiar with the other boards to know what they can and can't do in that department. 1
chwe Posted May 26, 2018 Posted May 26, 2018 38 minutes ago, TonyMac32 said: @Vincen, The Asus Tinker Board, and MQMaker MiQi have experimental video decoder and GPU support. there you go.. (should be more or less correct, cause only @jmmc works on such features.. ) 5 hours ago, jeyjey said: I want use that because It is very cost/power effectively good. sure, a not powered board doesn't need much power... If you want mainline on it, the things you're interested in might come in one or two years (just my opinion)... To my knowledge, mainlining H6 is still a 'one-woman-show', so better hope that she doesn't looses interest in doing all the work. 1
Vincen Posted May 27, 2018 Posted May 27, 2018 13 hours ago, TonyMac32 said: Because Linux support is not mature for the H6? It's hard to release a distro for something that doesn't have proper kernel support. :-). @Vincen, The Asus Tinker Board, and MQMaker MiQi have experimental video decoder and GPU support. I'm not as familiar with the other boards to know what they can and can't do in that department. Thanks TonyMac32 I didn't realise it was even in Linux itself that support for these procs was so early
j0bb13 Posted June 7, 2018 Posted June 7, 2018 H6 stuff is "Suitable for testing (WIP)": https://www.armbian.com/download/?tx_soc=h6
Vincen Posted June 7, 2018 Posted June 7, 2018 52 minutes ago, j0bb13 said: H6 stuff is "Suitable for testing (WIP)": https://www.armbian.com/download/?tx_soc=h6 Yep thanks just discovered that great news yesterday while showimg website to a friend
Rauli Kumpulainen Posted June 11, 2018 Posted June 11, 2018 Thank you for making available the WIP images for the Allwinner H6 boards. I booted up both the Orange Pi One Plus and Lite2 ok and my mt6701u usb wifi was plug and play however I noticed it was slower than the kernel 3.10 ubuntu image from Orange Pi's official Beta offerings. I use these boards as servers for crypto hashing but noticed the has rate was half on the Armbian WIP image. Is this because cpu frequency was below the 1.8ghz by any chance? I could not get any info or alter the cpu frequency at all. Nothing in /proc to read or echo values to. I foolishly tried using the OrangePiH6.dtb on the WIP image hoping to get cpufreq control and results in boot fail. Regards, Rauli
zador.blood.stained Posted June 11, 2018 Posted June 11, 2018 13 minutes ago, Rauli Kumpulainen said: Is this because cpu frequency was below the 1.8ghz by any chance? I could not get any info or alter the cpu frequency at all. Nothing in /proc to read or echo values to. You can always check this to see what kernel features are available. "NO" in the "CPUFreq" row answers why there is no CPU frequency available and "NO" in the "Thermal" row tells why we won't try to up the frequency from the default 890MHz value.
valant Posted June 17, 2018 Posted June 17, 2018 By the way, a while ago i had been faced with the fact, that uboot on Allwinner's 64 bit capable CPUs runs in the aarch32 state (because brom starts in aarch32) and only bootm and booti commands do a warm reset for the a64 linux kernel, basically a quirk. How it is with H6? I mean it's a newer allwinner SoC with a lot of changes, maybe their brom finally taught itself to work in aarch64? And yet. I am not into uboot that much, but I need to know this and you know uboot "documentation" is a joke. How the linux command line (bootargs content) is passed to linux for the case of using DT? I did a check with cb2 (their images), bpi m2u (their images) and pine64+ (armbian). 1) uses ATAGs with bootm (at least if the latter used without arguments), 2) uses DT that obviuosly is embedded into uboot itself, 3) passes all zeros into x0, x1, x2, x3 if the command (bootm) is used without arguments. apparently it would pass DT in x0 should it have it passed to it before by the user. But I see, armbian sets up bootargs variable, so the question is how DT variants of uboot pass the command line to linux? some DT node added on the fly? Thanks.
jernej Posted June 17, 2018 Posted June 17, 2018 1 hour ago, valant said: How it is with H6? I mean it's a newer allwinner SoC with a lot of changes, maybe their brom finally taught itself to work in aarch64? Same as with other Cortex-A53 AW SoCs, it starts in aarch32 mode. I doubt they changed BROM functionality much. If you are using mainline U-Boot, that shouldn't bother you, since SPL switches to aarch64. 1
valant Posted June 17, 2018 Posted June 17, 2018 22 minutes ago, jernej said: Same as with other Cortex-A53 AW SoCs, it starts in aarch32 mode. I doubt they changed BROM functionality much. If you are using mainline U-Boot, that shouldn't bother you, since SPL switches to aarch64. Thanks. How about command line hand off? Do you know how it's passed in case of using DT (thus no ATAGs)?
Recommended Posts