Jump to content

A64 and the 3.10 kernel

laughsalot

By laughsalot
in Allwinner sunxi

 Share

Recommended Posts

laughsalot

laughsalot

Posted
Posted

It seems like all the OS available for the A64 (for me specifically the orangepi winplus) are using the 3.10 kernel that has reached the EOL.  I have been advised against using this kernel but I don't see any other options.  I did find and armbian for the winplus that used 4.11 but it crumbled after upgrade every time.  Does anyone have any advice for me?

Thanks

t-bob

t-bob

Posted
Posted

you'll need to stick with 3.10 for the moment. 4.xx has several issues which will be fixed but not yet.

 

not much you can do

guidol

guidol

Posted
Posted
2 hours ago, Hannes Worst said:

As an experiment i tried running Arch Linux on my NanoPi a64 with 4.15.0-rc5. It's a pine64 image . To my total surprise it works. But it's no Armbian though...

Any idea why a Arch pine64 image does start on the NanoPi A64 and why the armbian pine64 image doesnt/shouldnt start?
I also got a NanoPi A64 at home, but using it with  NanoPi A64 Ubuntu Xenial Xerus 16.04 LXDE OS Image 
Kernel version 3.10.105 with Blue Led (heartbeat) 
https://github.com/avafinger/nanopi-a64-firmware

 

BTW: does the Xfce4 Desktop start on the NanoPi A64?

Hannes Worst

Hannes Worst

Posted
Posted

Actually, I have no idea why armbian won't boot on the nanopi A64. I can see some u-boot-activity but after that the board goes to a halt. It has to be a kernel issue in my perspective but I have no serial cable so I can't check anything. Sorry that I can't be of more help in this.

The arch-linux image boots fine, gives a fully functional xfce-desktop, automatically in the proper resolution (for me currently 1440x900). I had only to attach a wifi dongle for internet. Sound works flawless to.

1
guidol

guidol

Posted
Posted
7 minutes ago, Hannes Worst said:

It has to be a kernel issue in my perspective but I have no serial cable so I can't check anything.  

The arch-linux image boots fine, gives a fully functional xfce-desktop, automatically in the proper resolution (for me currently 1440x900).

I had only to attach a wifi dongle for internet. Sound works flawless to.

I do have a serial cable. If i do find the time this evening I'll check the output AND I'll test the arch-linux :)

1
guidol

guidol

Posted
Posted

I hadnt to install the serial cable :) (but see complete u-boot messages above at the second spoiler)
I did download and flash to uSD: Armbian_5.43.180417_Pine64_Debian_stretch_next_4.14.34-7z

After some short U-Boot Messages at the HDMI screen I did get a flashing cursor for about 10 seconds and then I did see the logon screen from armbian:

Debian GNU/Linux 9 pine64 tty1

pine64 login:

 ARMBIAN 5.43.180417 nightly Debian GNU/Linux 9 (stretch) 4.14.34-sunxi64

Linux nanopi-a64 4.14.34-sunxi64 #9 SMP Tue Apr 17 13:49:33 CEST 2018 aarch64 GNU/Linux

 

there is a error message for eth0 in u-boot for the follwing device: dwmac-sun8i 1c30000.ethernet eth0

 

erros in dmesg:
 

Spoiler 

[    1.599098] sunxi-de2-clks 1000000.clock: Error couldn't map SRAM to device
[    1.695733] cpufreq-dt: probe of cpufreq-dt failed with error -2
[    4.857727] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro


[    1.594259] sun4i-usb-phy 1c19400.phy: failed to get clock usb0_phy
[    1.695722] cpu cpu0: failed to get clock: -2
[    1.695733] cpufreq-dt: probe of cpufreq-dt failed with error -2
[    6.377743] thermal thermal_zone0: failed to read out thermal zone (-110)
[    7.393251] thermal thermal_zone0: failed to read out thermal zone (-110)
[    8.417247] thermal thermal_zone0: failed to read out thermal zone (-110)

 

 

and aplay didnt found any soundcard
aplay: device_list:270: no soundcards found...

 

For getting a network interface I used a USB-Ethernet-device

 

armbian doesnt seem to know the RTL8211E-Ethernet device

neither with firmware-realtek nor with armbian-firmware-full

 

armbianmonitor -u
System diagnosis information will now be uploaded to http://ix.io/187P

 

but for you and maybe others I connected the serial port for the u-boot messages:
 

Spoiler 

INFO:    PSCI Affinity Map:
INFO:      AffInst: Level 0, MPID 0x0, State ON
INFO:      AffInst: Level 0, MPID 0x1, State ON
INFO:      AffInst: Level 0, MPID 0x2, State ON
INFO:      AffInst: Level 0, MPID 0x3, State ON

U-Boot SPL 2017.11-armbian (Apr 17 2018 - 14:46:51)
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL3-1: Running on A64/H64 (1689) in SRAM A2 (@0x44000)
NOTICE:  Configuring SPC Controller
NOTICE:  BL3-1: v1.0(debug):c9f55c0
NOTICE:  BL3-1: Built : 14:46:45, Apr 17 2018
NOTICE:  DT: sun50i-a64-pine64-plus
INFO:    Configuring AXP PMIC
INFO:    PMIC: DRAM voltage: 1.36V
INFO:    PMIC: setup successful
NOTICE:  SCPI: dummy stub handler, implementation level: 000000
INFO:    BL3-1: Initializing runtime services
INFO:    BL3-1: Preparing for EL3 exit to normal world
INFO:    BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9


U-Boot 2017.11-armbian (Apr 17 2018 - 14:46:51 +0200) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: Pine64+
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   vidconsole
Err:   vidconsole
Net:   phy interface7
Could not get PHY for ethernet@01c30000: addr 1
No ethernet found.
starting USB...
USB0:   PA: set_value: error: gpio PA0 not reserved
USB EHCI 1.00
USB1:   USB OHCI 1.0
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3100 bytes read in 206 ms (14.6 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
153 bytes read in 166 ms (0 Bytes/s)
31571 bytes read in 302 ms (101.6 KiB/s)
3795 bytes read in 309 ms (11.7 KiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 44000000
4930190 bytes read in 526 ms (8.9 MiB/s)
13080584 bytes read in 920 ms (13.6 MiB/s)
## Loading init Ramdisk from Legacy Image at 4fe00000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    4930126 Bytes = 4.7 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 49b4c000, end 49fffa4e ... OK
   reserving fdt memory region: addr=4fa00000 size=6e000
   Loading Device Tree to 0000000049adb000, end 0000000049b4bfff ... OK

Starting kernel ...

Loading, please wait...
starting version 232

 


 

1GB memory is recognized :)

Couldnt change keyboard to german via dpkg-reconfigure keyboard-configuration or armbian-config.

OK I could change, but allways did get US-keyboard :(

 

guidol

guidol

Posted
Posted
20 minutes ago, Hannes Worst said:

That's great! You did manage to get further than I did last time. It's time I try again. :) Thank you!

Yes :) but also the WiFi RTL8189ETV isnt recognized (and no loadable module) :(

 

The CPU is running VERY COOL ;)
armbianmonitor -m
Stop monitoring using [ctrl]-[c]
Time      CPU n/a    load %cpu %sys %usr %nice %io %irq   CPU

22:11:48:   ---      0.00   0%   0%   0%   0%   0%   0% -6171°C
22:11:53:   ---      0.00   0%   0%   0%   0%   0%   0% -6534°C

guidol

guidol

Posted
Posted

for testing I did try the Banana Pi M64 (work in progress) Image

( https://dl.armbian.com/bananapim64/Debian_stretch_next_nightly.7z )

on the NanoPi A64, because the BPi M64 also should have the RTL8211E Ethernet-Chip.

But RTL8211E isnt recognized and a USB-Ethernet doesnt work after configuration.

Only a USB-WiFi Dongle did work to connect to the net.

 

So the BPi M64 image isnt as much useable as the one for the Pine64 on the NanoPi A64

guidol

guidol

Posted
Posted

next try :)
today I did try the -at this time- actual image for the Banana Pi M64 on the NanoPi A64:
Armbian_5.59_Bananapim64_Debian_stretch_next_4.14.65

 

OK - I knew the image isnt made for the NanoPi A64 - but as information to @Igor I got sometimes the same boot error as I did seen the last week with another systems here in the forum (which had boot problems after the update). I will attach the image here in this message.

With an active hub from D-Link the system doenst came up wit the Keyboard-Dongle/USB-Ethernet and USB-Soundcard.
After I removed the USB-Soundcard from the active Hub the NanoPi A64 did boot.

 

After initial getting the boot error the system booted with a blinking cursor to the login prompt.

Like the 5.41 image before onboard-eth0 / leds nor the onboard-soundcard isnt recognized.

 

First I did try like before a USB-Ethernet adapter - but I had to find out that only the lower USB-port is working

(in the first try I got a wireless USB-Keyboard at the lower USB-port and the USB-Network at the upper USB-port) - so the network wasnt found.

 

After I did try the keyboard in the upper port and seeing that it isnt recognized I did put a passive USB-Hub in the lower USB-port and now I can use the USB-Keyboard and the USB-Network-Dongle :)

 

The image 5.59 has been updated to 

root@nanopi-m64(192.168.6.64):~# dpkg -l|grep 5.60
ii  armbian-config                      5.60                           all          Armbian configuration utility
ii  armbian-firmware                    5.60                           all          Linux firmware
ii  armbian-tools-stretch               5.60                           arm64        Armbian tools, Cubie bt utils
ii  hostapd                             3:2.6-99~armbian5.60+1         arm64        IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator
ii  linux-dtb-next-sunxi64              5.60                           arm64        Linux DTB, version 4.14.70-sunxi64
ii  linux-image-next-sunxi64            5.60                           arm64        Linux kernel, version 4.14.70-sunxi64
ii  sunxi-tools                         1.4.2-2~armbian5.60+1          arm64        tools for working with Allwinner (sunxi) ARM processors

but Welcome-Message did show 5.59

 

ARMBIAN 5.59 testing Debian GNU/Linux 9 (stretch) 4.14.70-sunxi64

Linux nanopi-m64 4.14.70-sunxi64 #274 SMP Wed Sep 19 12:09:30 CEST 2018 aarch64 GNU/Linux

 

System diagnosis information has been uploaded to http://ix.io/1nAF 

NanoPi_A64_with_BPi_M64_image.jpg

tkaiser

tkaiser

Posted
Posted
15 minutes ago, guidol said:

Welcome-Message did show 5.59

That's due to package 'linux-stretch-root-next-bananapim64' remaining at 5.59.

 

I don't understand this since years. The mechanism is broken, confuses users and generates unnecessary support requests. Why not fixing it or at least always update this package too with version bumps?

Igor

Igor

Posted
Posted
3 minutes ago, tkaiser said:

Why not fixing it or at least always update this package too with version bumps?


With the latest update, it should be 5.60 ... but perhaps after reboot/logout/login?

 

Well, perhaps it's time to enforce some already proposed naming for a version of Armbian and use this numbering only for our internal process. 

 

Armbian 2018.10

Armbian 18.04

Armbian Some_Generic_Names

 

Let's make a separate topic or attach to existing for those changes.

guidol

guidol

Posted
Posted
2 hours ago, Igor said:


With the latest update, it should be 5.60 ... but perhaps after reboot/logout/login?

With the "latest update" - just a few seconds before..... I did get

arm64 armbian-config all 5.61

but the "root"-package is at 5.59:    linux-stretch-root-next-bananapim64 5.59

 

Maybe because of ARMBIAN 5.59 testing Debian GNU/Linux 9 (stretch) 4.14.70-sunxi64 ?

Igor

Igor

Posted
Posted
21 minutes ago, guidol said:

but the "root"-package is at 5.59:    linux-stretch-root-next-bananapim64 5.59


Probably because it is still .wip and packages are made only for .conf ... not 100% sure but possible. 

1
guidol

guidol

Posted
Posted
On 6/17/2018 at 12:10 AM, guidol said:

not for the NanoPi A64 with armbian - but somebody is working on a kernel 4.4.111 at
http://www.friendlyarm.com/Forum/viewtopic.php?f=53&amp;t=1543

Thanks to @lex I could test a version of this image:
Ubuntu 18.04.1 LTS (GNU/Linux 4.4.117-a64 aarch64)

Linux nanopi-a64 4.4.117-a64 #1 SMP PREEMPT Wed Sep 26 19:23:53 -03 2018 aarch64 aarch64 aarch64 GNU/Linux

where eth0, Wifi and HDMI-Sound does work :)

For his image I did create a NanoPi A64 Boot-Logo (visible because of Android kernel) - here as attachment :)

bootlogo.bmp

guidol

guidol

Posted
Posted
9 hours ago, rocka said:

Can I test this image? Is it available?
 

you have to ask @lex here in the forum or in the thread of the friendlyarm-forum,

because at this time it seems that this image isnt public

guidol

guidol

Posted
Posted
12 minutes ago, rocka said:

The link takes me to the login site.

me too - dont know if its the link or Mega.nz did change something :(

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept