Jump to content

Armbian image and build support for RISC-V.


balbes150

Recommended Posts

Donate your old hardware to community. Start a giveaway Raffle!

I have the one (Armbian_22.08.0-trunk_Nezha_jammy_current_6.1.0_xfce_desktop.img) from December (the other ones don't start for me) and it has the vector extension:

 _   _          _
| \ | | ___ ___| |__   __ _
|  \| |/ _ \_  / '_ \ / _` |
| |\  |  __// /| | | | (_| |
|_| \_|\___/___|_| |_|\__,_|

Welcome to Armbian 22.08.0-trunk Jammy with Linux 6.1.0-rc3-d1

System load:   168%             Up time:       2 min
Memory usage:  10% of 978M      IP:            192.168.1.199
CPU temp:      38°C             Usage of /:    9% of 58G

Last login: Mon Jan 30 19:38:20 2023 from 192.168.1.144

root@mq-pro-jenkins-agent-2:~#
root@mq-pro-jenkins-agent-2:~# cat /proc/cpuinfo
processor       : 0
hart            : 0
isa             : rv64imafdc
mmu             : sv39
uarch           : thead,c906
mvendorid       : 0x5b7
marchid         : 0x0
mimpid          : 0x0

 

Link to comment
Share on other sites

@gounthar, notice the "v"  character missing in your output, so it means that that particular image does not detect vector extension.

isa : rv64imafdc

For MangoPI MQ(PRO) - The thing is that there were several builds that successfully detected RVV extemsion ( RVV v0.7 ) present on c906 CPU, and there were builds that do not.  I`m wandering what has changed in those images, that prevents "v" appearing in "isa" line of /proc/cpuinfo? And how to enable it again?

Link to comment
Share on other sites

1 час назад, msomeone сказал:

For MangoPI MQ(PRO) - The thing is that there were several builds that successfully detected RVV extemsion ( RVV v0.7 ) present on c906 CPU, and there were builds that do not.  I`m wandering what has changed in those images, that prevents "v" appearing in "isa" line of /proc/cpuinfo? And how to enable it again?

Specify the exact name of the image where there is support.

Link to comment
Share on other sites

> New ver 20220622 for D1 (Nezha Lichee RV Mango MQ pro etc) and StarFive V1 (u740)

This one, i've tested CLI only image - Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz ( https://disk.yandex.ru/d/da8qJ8wyE1hhcQ/Nezha_D1/ArmbianTV/20220622/Armbian_22.08.0-trunk_Nezha_jammy_current_5.19.0.img.xz?pane=file-info )

Is there a way to determine which image that was from burned SD card content or booted Mango? (as i`m not sure that this is the only image that had RVV support). But i`m pretty sure it was june-july image, corresponding to your initial bring-up efforts for Mango PI.

Thanks!

 

P.S. I will check new images again with another sdcard to provide thorough report on which images boot and have "v" in "isa" and which do not

 

Image that has RVV outputs following when queried:

 

> msomeone@nezha:~$ uname -a
> Linux nezha 6.1.0-rc3-d1 #trunk Fri Jan 13 08:21:24 UTC 2023 riscv64 GNU/Linux
> msomeone@nezha:~$ cat /proc/cpuinfo
> processor       : 0
> hart                 : 0
> isa                   : rv64imafdcv
> mmu              : sv39
> uarch             : thead,c906
> mvendorid    : 0x5b7
> marchid         : 0x0
> mimpid          : 0x0

 

Edited by msomeone
Link to comment
Share on other sites

Sorry for the delays, after kaspersky policy update, had troubles flashing on my computer. Finally resolved, and i tried latest image  - 20230116-current-Armbian_22.08.0-trunk_Nezha_sid_current_6.1.0.img

(jammy image - 20230116-current-Armbian_22.08.0-trunk_Nezha_jammy_current_6.1.0.img     does not detect RVV extension ("CPU:   rv64imafdc") and does not boot also with same log)

 

Now it does not boot:

 

Цитата

Unknown command 'U-Boot' - try 'help'
=> WDT:   Started watchdog@6011000 with servicing (16s timeout)
Unknown command 'WDT:' - try 'help'
=> MMC:nvironment from nowhere... OK
Unknown command 'MMC:nvironment' - try 'help'
=> In:    serial2500000
Unknown command 'In:' - try 'help'
=> Out:   serrning: ethernet@4500000 (eth0) usiernet@4500000
Unknown command 'Out:' - try 'help'
=> Hit anyitions #0, OK
Unknown command 'Hit' - try 'help'
=> mmc0 is current device
Unknown command 'mmc0' - try 'help'
=> Scanning mmc 0:1...
Unknown command 'Scanning' - try 'help'
=> 2able to read file ubos
Unknown command '2able' - try 'help'
=> BootOrder not definedstarting USB...
Unknown command 'BootOrder' - try 'help'
=> Bus SB OHCI 1.0
Unknown command 'Bus' - try 'help'
=> Bus usb@4200CI 1.0
Unknown command 'Bus' - try 'help'
=> scanning bus usb@4101000 for dsb@4101400 for d bus usb@4200000 foing bus usb@4200400 for devices... ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
Unknown command 'scanning' - try 'help'
=> not rovide a handshake (OUT) (5)
Unknown command 'not' - try 'help'
=> ERROR: USB-error: DEVICENOTRESPOr did
Unknown command 'ERROR:' - try 'help'
=> not provide a handshake (OUerror=-1)
Unknown command 'not' - try 'help'
=> 1 USB Device(s) found
Unknown command '1' - try 'help'
=>       age Device(s) found
Unknown command 'age' - try 'help'
=>
Unknown command 'age' - try 'help'
=> Device 0: unknowissing environment varux.cfg/01-6e-22-20-bb-1b-1n_eth_start: Timeout
Unknown command 'Device' - try 'help'
=> Retrieving file: pxelinux.cfg/0000000
Unknown command 'Retrieving' - try 'help'
=> sun8i_emac_eth_start: Timeo8i_emac_eth_start: Timeout
Unknown command 'sun8i_emac_eth_start:' - try 'help'
=> Retrieving Timeout
Unknown command 'Retrieving' - try 'help'
=> Retrieving file: pxelinux.cfg/0000
Unknown command 'Retrieving' - try 'help'
=> sun8i_emac__emac_eth_start: Tic_eth_start: Timeout
Unknown command 'sun8i_emac__emac_eth_start:' - try 'help'
=> Retrieving fil
Unknown command 'Retrieving' - try 'help'
=> Retrieving file: pxelinux.cfg/default-riscv-sunxi-g/default-riscv file: pxelinux.cfg/default-riscv
Unknown command 'Retrieving' - try 'help'
=> sun8i_emac_eth_start: Timeout
Unknown command 'sun8i_emac_eth_start:' - try 'help'
=> Retrieving file: pxelinux.cfg/defaut found
Unknown command 'Retrieving' - try 'help'
=> sun8i_emac_eth_start:
[93]HELLO! BOOT0 is starting!
[96]BOOT0 commit : 882671f
[98]set pll start
[100]periph0 has been enabled
[103]set pll end
[105]board init ok
[107]DRAM only have internal ZQ!!
[110]get_pmu_exist() = -1
[112]ddr_efuse_type: 0x0
[115][AUTO DEBUG] two rank and full DQ!
[119]ddr_efuse_type: 0x0
[122][AUTO DEBUG] rank 0 row = 15
[125][AUTO DEBUG] rank 0 bank = 8
[128][AUTO DEBUG] rank 0 page size = 2 KB
[132][AUTO DEBUG] rank 1 row = 15
[135][AUTO DEBUG] rank 1 bank = 8
[138][AUTO DEBUG] rank 1 page size = 2 KB
[142]rank1 config same as rank0
[145]DRAM BOOT DRIVE INFO: V0.24
[148]DRAM CLK = 792 MHz
[150]DRAM Type = 3 (2:DDR2,3:DDR3)
[153]DRAMC ZQ value: 0x7b7bfb
[156]DRAM ODT value: 0x42.
[158]ddr_efuse_type: 0x0
[161]DRAM SIZE =1024 M
[165]DRAM simple test OK.
[167]dram size =1024
[169]card no is 0
[171]sdcard 0 line count 4
[173][mmc]: mmc driver ver 2021-04-2 16:45
[183][mmc]: Wrong media type 0x0
[186][mmc]: ***Try SD card 0***
[194][mmc]: HSSDR52/SDR25 4 bit
[197][mmc]: 50000000 Hz
[199][mmc]: 29580 MB
[201][mmc]: ***SD/MMC 0 init OK!!!***
[248]Loading boot-pkg Succeed(index=1).
[251]Entry_name        = opensbi
[255]Entry_name        = dtb
[257]Entry_name        = u-boot
[261]Adding DRAM info to DTB.
[266]Jump to second Boot.

OpenSBI v1.0-95-gade588d
   ____                    _____ ____ _____
  / __ \                  / ____|  _ \_   _|
 | |  | |_ __   ___ _ __ | (___ | |_) || |
 | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |
 | |__| | |_) |  __/ | | |____) | |_) || |_
  \____/| .__/ \___|_| |_|_____/|____/_____|
        | |
        |_|

Platform Name             : Allwinner D1 Nezha
Platform Features         : medeleg
Platform HART Count       : 1
Platform IPI Device       : ---
Platform Timer Device     : --- @ 0Hz
Platform Console Device   : uart8250
Platform HSM Device       : sun20i-d1-ppu
Platform Reboot Device    : sunxi-wdt-reset
Platform Shutdown Device  : ---
Firmware Base             : 0x40000000
Firmware Size             : 240 KB
Runtime SBI Version       : 0.3

Domain0 Name              : root
Domain0 Boot HART         : 0
Domain0 HARTs             : 0*
Domain0 Region00          : 0x0000000040000000-0x000000004003ffff ()
Domain0 Region01          : 0x0000000000000000-0xffffffffffffffff (R,W,X)
Domain0 Next Address      : 0x000000004a000000
Domain0 Next Arg1         : 0x0000000044000000
Domain0 Next Mode         : S-mode
Domain0 SysReset          : yes

Boot HART ID              : 0
Boot HART Domain          : root
Boot HART Priv Version    : v1.11
Boot HART Base ISA        : rv64imafdcvx
Boot HART ISA Extensions  : time
Boot HART PMP Count       : 8
Boot HART PMP Granularity : 2048
Boot HART PMP Address Bits: 38
Boot HART MHPM Count      : 0
Boot HART MIDELEG         : 0x0000000000000222
Boot HART MEDELEG         : 0x000000000000b109


U-Boot 2022.07-rc3-35470-gafc07cec42-dirty (Jun 26 2022 - 13:03:06 +0300)

CPU:   rv64imafdc
Model: Allwinner D1 Nezha
DRAM:  1 GiB
sunxi_set_gate: (CLK#24) unhandled
Core:  66 devices, 24 uclasses, devicetree: board
WDT:   Started watchdog@6011000 with servicing (16s timeout)
MMC:   mmc@4020000: 0, mmc@4021000: 1
Loading Environment from nowhere... OK
In:    serial@2500000
Out:   serial@2500000
Err:   serial@2500000
Net:
Warning: ethernet@4500000 (eth0) using random MAC address - f2:b1:de:48:d9:18
eth0: ethernet@4500000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
26980 bytes read in 7 ms (3.7 MiB/s)
** Unable to read file ubootefi.var **
Failed to load EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
starting USB...
Bus usb@4101000: USB EHCI 1.00
Bus usb@4101400: USB OHCI 1.0
Bus usb@4200000: USB EHCI 1.00
Bus usb@4200400: USB OHCI 1.0
scanning bus usb@4101000 for devices... 1 USB Device(s) found
scanning bus usb@4101400 for devices... 1 USB Device(s) found
scanning bus usb@4200000 for devices... 1 USB Device(s) found
scanning bus usb@4200400 for devices... ERROR:  USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
ERROR: USB-error: DEVICENOTRESPONDING: Device did not respond to token (IN) or did
not provide a handshake (OUT) (5)
unable to get device descriptor (error=-1)
1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
sun8i_emac_eth_start: Timeout
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-f2-b1-de-48-d9-18
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/00000000
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/0000000
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/000000
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/00000
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/0000
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/000
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/00
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/0
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default-riscv-sunxi-sunxi
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default-riscv-sunxi
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default-riscv
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default
sun8i_emac_eth_start: Timeout
Config file not found
sun8i_emac_eth_start: Timeout
sun8i_emac_eth_start: Timeout
=>
 


 

Update: 
230113 - Armbian_22.08.0-trunk_Nezha-stu_sid_current_6.1.0.img - boots successfully with RVV support detected.

Edited by msomeone
Link to comment
Share on other sites

Good day! I apologize for the indiscreet request. Has it happened in your practice that you could not connect a single-board computer to the Internet in standard ways (lack of wi-fi and LAN) and had to connect over usb or via uart? I'm not asking for sequential instruction. On hand there is a lichee rv for 512mb ram, sd 32gb, usb <> ttl via ch340 (not an ordinary converter, but a chip on wemos d1 mini, the esp chip is closed rst to gnd, thereby converting from usb to ttl via the rx \ tx line). lichee (dock) without wi-fi. There is another esp32 and 2 pcs esp8266, the plans were to make them friends and use them as a standard wi-fi adapter. I am using armbian from this branch (20220627). I ask for advice - what tool can - update apt (list of packages, repositories, packages) using another computer? Many methods are attractive, but everything rests on manual updating, because the branching and depth of dependencies (the number of package dependencies grows with each iteration, which makes manual updating difficult). If I am not mistaken with the topic and you have a more "elegant" solution to this problem, I will be grateful for the hint and advice. From myself I promise to leave the results of my "works" on this forum. Thank you for your attention. I'm sorry for my English, I'm using a translator.

Edited by Ан Со
Link to comment
Share on other sites

Thanks for the advice! I solved it a bit trivial and funny. I downloaded the repository to an external hdd (about 120 GB), updated it and started trying different ways. Almost immediately it turned out to do the necessary, through rndis. (there were several interesting moments, but this is not for this topic, I will make a separate topic) How to accumulate a critical mass of changes, I will create a separate topic, there will be only lichee-rv and armbian.

Link to comment
Share on other sites

Hi @balbes150, I have installed your version from 20221201 (CLI), now I want to compile some custom modules (e.g. Realtek 8821cu) - so the question is: where to get the linux headers? Nor armbian-config nor apt doesn't offer anything relevant...

Link to comment
Share on other sites

ver 20230616-edge kernel 6.4-rc6 (HDMI not work)

work - SD card, USB, wifi. management is possible via UART or USB-LAN

 

root@192.168.1.19's password: 
 _   _          _           
| \ | | ___ ___| |__   __ _ 
|  \| |/ _ \_  / '_ \ / _` |
| |\  |  __// /| | | | (_| |
|_| \_|\___/___|_| |_|\__,_|
                            
Welcome to Armbian 22.08.0-trunk Jammy with Linux 6.4.0-rc6-d1

System load:   129%           	Up time:       2 min	
Memory usage:  19% of 478M   	IP:	       192.168.1.19
Usage of /:    5% of 29G    	
RX today:      23.6 KiB  	

[ 5 security updates available, 8 updates total: apt upgrade ]
Last check: 2023-06-16 09:56

[ General system configuration (beta): armbian-config ]

Last login: Fri Jun 16 09:55:59 2023

root@nezha:~# neofetch 
            .-/+oossssoo+/-.               root@nezha 
        `:+ssssssssssssssssss+:`           ---------- 
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 22.04.2 LTS riscv64 
    .ossssssssssssssssssdMMMNysssso.       Host: Allwinner D1 Nezha 
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 6.4.0-rc6-d1 
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 6 mins 
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 529 (dpkg) 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.1.16 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Terminal: /dev/pts/0 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   CPU: (1) 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   Memory: 97MiB / 478MiB 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+
.ssssssssdMMMNhsssssssssshNMMMdssssssss.                           
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/                            
  +sssssssssdmydMMMMMMMMddddyssssssss+
   /ssssssssssshdmNNNNmyNMMMMhssssss/
    .ossssssssssssssssssdMMMNysssso.
      -+sssssssssssssssssyyyssss+-
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.


root@nezha:~# cat /proc/cpuinfo 
processor	: 0
hart		: 0
isa		: rv64imafdc
mmu		: sv39
uarch		: thead,c906
mvendorid	: 0x5b7
marchid		: 0x0
mimpid		: 0x0

 

Link to comment
Share on other sites

My system (fully updated and rebooted) shows:

 

sander@nezha:~$ uname -a
Linux nezha 6.1.0-rc3-d1 #trunk Thu Dec  1 14:53:18 MSK 2022 riscv64 riscv64 riscv64 GNU/Linux

 

Can I upgrade (easily?) to 6.4.0-rc6-d1 ? If so, how?

Link to comment
Share on other sites

11 часов назад, Superkoning сказал:

Can I upgrade (easily?) to 6.4.0-rc6-d1 ? If so, how?

there is no easy way, if you need a new kernel, use the appropriate image with a new kernel.

Link to comment
Share on other sites

@balbes150 Debian(sid) version of 20230615-current and 20230616-edge not work:

 

Retrieving file: pxelinux.cfg/default-riscv-sunxi-sunxi
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default-riscv-sunxi
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default-riscv
sun8i_emac_eth_start: Timeout
Retrieving file: pxelinux.cfg/default
sun8i_emac_eth_start: Timeout
Config file not found
sun8i_emac_eth_start: Timeout
sun8i_emac_eth_start: Timeout

 

Link to comment
Share on other sites

2 часа назад, Evgeny Nikulin сказал:

Debian(sid) version of 20230615-current and 20230616-edge not work:

they work, only requires a number of manual operations to prepare for launch. If you don't know what needs to be done, wait for the images to come out with automatic startup. I have published these versions at the request of those who know what needs to be done.

 

2 часа назад, Evgeny Nikulin сказал:

how do you turn on wifi for Armbian_22.08.0-trunk_Nezha_jammy_edge_6.4.0.img.xz? After load wifi not found as device

With so many details - wait for a psychic who will guess what is going on with you (what equipment you have, all your steps, etc.).

Link to comment
Share on other sites

1 час назад, balbes150 сказал:

With so many details - wait for a psychic who will guess what is going on with you (what equipment you have, all your steps, etc.).

My env:
- standard MangoPi D1 v1.4
- Armbian_22.08.0-trunk_Nezha_jammy_edge_6.4.0.img.xz
- update all packages to last version (apt update & apt upgrade)

After start:
 

ip a
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
3: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 43:43:43:43:43:43 brd ff:ff:ff:ff:ff:ff


*mac not real

Try to load module:
 

sudo modprobe -v 8723ds
insmod /lib/modules/6.4.0-rc6-d1/kernel/net/wireless/cfg80211.ko.xz
insmod /lib/modules/6.4.0-rc6-d1/kernel/drivers/net/wireless/rtl8723ds/8723ds.ko.xz


But no new interfaces :(


 

ip a
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
3: usb0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 43:43:43:43:43:43 brd ff:ff:ff:ff:ff:ff


armbian-config also does not show the ability to configure wifi

Link to comment
Share on other sites

1 hour ago, Evgeny Nikulin said:

My env:
- standard MangoPi D1 v1.4
- Armbian_22.08.0-trunk_Nezha_jammy_edge_6.4.0.img.xz
- update all packages to last version (apt update & apt upgrade)

 

On my Sipeed D1 board it was working fine.... Looks like there's a specific chip issue?

 

C14382:~ vkozlov$ ssh vkozlov@192.168.0.98
The authenticity of host '192.168.0.98 (192.168.0.98)' can't be established.
ED25519 key fingerprint is SHA256:9O1jGMEfv5tennGmm9+tkRItWGxm6iz7XyeC3HcEUME.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '192.168.0.98' (ED25519) to the list of known hosts.
vkozlov@192.168.0.98's password:
 _   _          _
| \ | | ___ ___| |__   __ _
|  \| |/ _ \_  / '_ \ / _` |
| |\  |  __// /| | | | (_| |
|_| \_|\___/___|_| |_|\__,_|

Welcome to Armbian 22.08.0-trunk Jammy with Linux 6.4.0-rc6-d1

System load:   89%           	Up time:       2 min
Memory usage:  18% of 478M   	IP:	       192.168.0.98
Usage of /:    5% of 30G
RX today:      Error: No interface matching "--oneline" found in database.

[ 6 security updates available, 8 updates total: apt upgrade ]
Last check: 2023-06-16 13:40

[ General system configuration (beta): armbian-config ]

To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

vkozlov@nezha:~$ sudo apt update
[sudo] password for vkozlov:
Hit:1 http://ports.ubuntu.com jammy InRelease
Hit:2 http://deb.volian.org/volian scar InRelease
Get:3 http://ports.ubuntu.com jammy-security InRelease [110 kB]
Get:4 http://ports.ubuntu.com jammy-updates InRelease [119 kB]
Get:5 http://ports.ubuntu.com jammy-backports InRelease [108 kB]
Get:6 http://ports.ubuntu.com jammy-security/main riscv64 Packages [392 kB]
Get:7 http://ports.ubuntu.com jammy-security/universe riscv64 Packages [611 kB]
Get:8 http://ports.ubuntu.com jammy-updates/main riscv64 Packages [668 kB]
Get:9 http://ports.ubuntu.com jammy-updates/restricted riscv64 Packages [5,204 B]
Get:10 http://ports.ubuntu.com jammy-updates/multiverse riscv64 Packages [3,349 B]
Get:11 http://ports.ubuntu.com jammy-updates/universe riscv64 Packages [836 kB]
Get:12 http://ports.ubuntu.com jammy-backports/universe riscv64 Packages [15.0 kB]
Fetched 2,868 kB in 45s (63.4 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
14 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Skipping acquire of configured file 'main/binary-riscv64/Packages' as repository 'http://deb.volian.org/volian scar InRelease' doesn't support architecture 'riscv64'
vkozlov@nezha:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libmm-glib0
The following packages will be upgraded:
  bind9-dnsutils bind9-host bind9-libs dnsutils libcap2 libcap2-bin libglib2.0-0 libglib2.0-bin libglib2.0-data libudev1 linux-libc-dev qemu-utils udev
13 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 6,866 kB of archives.
After this operation, 31.7 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ports.ubuntu.com jammy-security/main riscv64 libcap2 riscv64 1:2.44-1ubuntu0.22.04.1 [16.5 kB]
Get:2 http://ports.ubuntu.com jammy-updates/main riscv64 udev riscv64 249.11-0ubuntu3.9 [1,496 kB]
Get:3 http://ports.ubuntu.com jammy-updates/main riscv64 libudev1 riscv64 249.11-0ubuntu3.9 [70.4 kB]
Get:4 http://ports.ubuntu.com jammy-security/main riscv64 libcap2-bin riscv64 1:2.44-1ubuntu0.22.04.1 [24.9 kB]
Get:5 http://ports.ubuntu.com jammy-security/main riscv64 libglib2.0-data all 2.72.4-0ubuntu2.2 [4,612 B]
Get:6 http://ports.ubuntu.com jammy-security/main riscv64 libglib2.0-bin riscv64 2.72.4-0ubuntu2.2 [74.0 kB]
Get:7 http://ports.ubuntu.com jammy-security/main riscv64 libglib2.0-0 riscv64 2.72.4-0ubuntu2.2 [1,312 kB]
Get:8 http://ports.ubuntu.com jammy-security/main riscv64 bind9-host riscv64 1:9.18.12-0ubuntu0.22.04.2 [51.7 kB]
Get:9 http://ports.ubuntu.com jammy-security/main riscv64 bind9-dnsutils riscv64 1:9.18.12-0ubuntu0.22.04.2 [153 kB]
Get:10 http://ports.ubuntu.com jammy-security/main riscv64 bind9-libs riscv64 1:9.18.12-0ubuntu0.22.04.2 [1,174 kB]
Get:11 http://ports.ubuntu.com jammy-security/universe riscv64 dnsutils all 1:9.18.12-0ubuntu0.22.04.2 [3,926 B]
Get:12 http://ports.ubuntu.com jammy-security/main riscv64 linux-libc-dev riscv64 5.15.0-76.83 [1,264 kB]
Get:13 http://ports.ubuntu.com jammy-security/main riscv64 qemu-utils riscv64 1:6.2+dfsg-2ubuntu6.11 [1,220 kB]
Fetched 6,866 kB in 1min 19s (86.8 kB/s)
(Reading database ... 39071 files and directories currently installed.)
Preparing to unpack .../libcap2_1%3a2.44-1ubuntu0.22.04.1_riscv64.deb ...
Unpacking libcap2:riscv64 (1:2.44-1ubuntu0.22.04.1) over (1:2.44-1build3) ...
Setting up libcap2:riscv64 (1:2.44-1ubuntu0.22.04.1) ...
(Reading database ... 39071 files and directories currently installed.)
Preparing to unpack .../udev_249.11-0ubuntu3.9_riscv64.deb ...
Unpacking udev (249.11-0ubuntu3.9) over (249.11-0ubuntu3) ...
Preparing to unpack .../libudev1_249.11-0ubuntu3.9_riscv64.deb ...
Unpacking libudev1:riscv64 (249.11-0ubuntu3.9) over (249.11-0ubuntu3) ...
Setting up libudev1:riscv64 (249.11-0ubuntu3.9) ...
(Reading database ... 39071 files and directories currently installed.)
Preparing to unpack .../0-libcap2-bin_1%3a2.44-1ubuntu0.22.04.1_riscv64.deb ...
Unpacking libcap2-bin (1:2.44-1ubuntu0.22.04.1) over (1:2.44-1build3) ...
Preparing to unpack .../1-libglib2.0-data_2.72.4-0ubuntu2.2_all.deb ...
Unpacking libglib2.0-data (2.72.4-0ubuntu2.2) over (2.72.4-0ubuntu2) ...
Preparing to unpack .../2-libglib2.0-bin_2.72.4-0ubuntu2.2_riscv64.deb ...
Unpacking libglib2.0-bin (2.72.4-0ubuntu2.2) over (2.72.4-0ubuntu2) ...
Preparing to unpack .../3-libglib2.0-0_2.72.4-0ubuntu2.2_riscv64.deb ...
Unpacking libglib2.0-0:riscv64 (2.72.4-0ubuntu2.2) over (2.72.4-0ubuntu2) ...
Preparing to unpack .../4-bind9-host_1%3a9.18.12-0ubuntu0.22.04.2_riscv64.deb ...
Unpacking bind9-host (1:9.18.12-0ubuntu0.22.04.2) over (1:9.18.12-0ubuntu0.22.04.1) ...
Preparing to unpack .../5-bind9-dnsutils_1%3a9.18.12-0ubuntu0.22.04.2_riscv64.deb ...
Unpacking bind9-dnsutils (1:9.18.12-0ubuntu0.22.04.2) over (1:9.18.12-0ubuntu0.22.04.1) ...
Preparing to unpack .../6-bind9-libs_1%3a9.18.12-0ubuntu0.22.04.2_riscv64.deb ...
Unpacking bind9-libs:riscv64 (1:9.18.12-0ubuntu0.22.04.2) over (1:9.18.12-0ubuntu0.22.04.1) ...
Preparing to unpack .../7-dnsutils_1%3a9.18.12-0ubuntu0.22.04.2_all.deb ...
Unpacking dnsutils (1:9.18.12-0ubuntu0.22.04.2) over (1:9.18.12-0ubuntu0.22.04.1) ...
Preparing to unpack .../8-linux-libc-dev_5.15.0-76.83_riscv64.deb ...
Unpacking linux-libc-dev:riscv64 (5.15.0-76.83) over (5.15.0-73.80) ...
Preparing to unpack .../9-qemu-utils_1%3a6.2+dfsg-2ubuntu6.11_riscv64.deb ...
Unpacking qemu-utils (1:6.2+dfsg-2ubuntu6.11) over (1:6.2+dfsg-2ubuntu6.10) ...
Setting up bind9-libs:riscv64 (1:9.18.12-0ubuntu0.22.04.2) ...
Setting up libglib2.0-0:riscv64 (2.72.4-0ubuntu2.2) ...
No schema files found: doing nothing.
Setting up linux-libc-dev:riscv64 (5.15.0-76.83) ...
Setting up libcap2-bin (1:2.44-1ubuntu0.22.04.1) ...
Setting up libglib2.0-data (2.72.4-0ubuntu2.2) ...
Setting up udev (249.11-0ubuntu3.9) ...
Setting up qemu-utils (1:6.2+dfsg-2ubuntu6.11) ...
Setting up bind9-host (1:9.18.12-0ubuntu0.22.04.2) ...
Setting up libglib2.0-bin (2.72.4-0ubuntu2.2) ...
Setting up bind9-dnsutils (1:9.18.12-0ubuntu0.22.04.2) ...
Setting up dnsutils (1:9.18.12-0ubuntu0.22.04.2) ...
Processing triggers for initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: Generating /boot/initrd.img-6.4.0-rc6-d1
update-initramfs: mv Initrd
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for man-db (2.10.2-1) ...
vkozlov@nezha:~$ sudo reboot
vkozlov@nezha:~$ Connection to 192.168.0.98 closed by remote host.
Connection to 192.168.0.98 closed.
C14382:~ vkozlov$ ssh vkozlov@192.168.0.98
^C
C14382:~ vkozlov$ ssh vkozlov@192.168.0.98
^C
C14382:~ vkozlov$ ping 192.168.0.98
PING 192.168.0.98 (192.168.0.98): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
Request timeout for icmp_seq 8
Request timeout for icmp_seq 9
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
Request timeout for icmp_seq 12
Request timeout for icmp_seq 13
Request timeout for icmp_seq 14
Request timeout for icmp_seq 15
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
Request timeout for icmp_seq 21
Request timeout for icmp_seq 22
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
Request timeout for icmp_seq 25
Request timeout for icmp_seq 26
Request timeout for icmp_seq 27
Request timeout for icmp_seq 28
Request timeout for icmp_seq 29
Request timeout for icmp_seq 30
64 bytes from 192.168.0.98: icmp_seq=31 ttl=64 time=131.477 ms
64 bytes from 192.168.0.98: icmp_seq=32 ttl=64 time=963.402 ms
64 bytes from 192.168.0.98: icmp_seq=33 ttl=64 time=656.280 ms
Request timeout for icmp_seq 34
64 bytes from 192.168.0.98: icmp_seq=35 ttl=64 time=398.326 ms
64 bytes from 192.168.0.98: icmp_seq=36 ttl=64 time=12.819 ms
Request timeout for icmp_seq 37
Request timeout for icmp_seq 38
^C
--- 192.168.0.98 ping statistics ---
40 packets transmitted, 5 packets received, 87.5% packet loss
round-trip min/avg/max/stddev = 12.819/432.461/963.402/346.367 ms
C14382:~ vkozlov$ ssh vkozlov@192.168.0.98
vkozlov@192.168.0.98's password:
 _   _          _
| \ | | ___ ___| |__   __ _
|  \| |/ _ \_  / '_ \ / _` |
| |\  |  __// /| | | | (_| |
|_| \_|\___/___|_| |_|\__,_|

Welcome to Armbian 22.08.0-trunk Jammy with Linux 6.4.0-rc6-d1

System load:   300%           	Up time:       1 min
Memory usage:  18% of 478M   	IP:	       192.168.0.98
Usage of /:    5% of 30G
RX today:      Error: No interface matching "--oneline" found in database.

[ General system configuration (beta): armbian-config ]

Last login: Fri Jun 30 17:56:12 2023 from 192.168.0.52
vkozlov@nezha:~$ uname -a
Linux nezha 6.4.0-rc6-d1 #trunk Fri Jun 16 09:23:49 MSK 2023 riscv64 riscv64 riscv64 GNU/Linux
vkozlov@nezha:~$ lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
vkozlov@nezha:~$ sudo lspci
[sudo] password for vkozlov:
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
vkozlov@nezha:~$ sudo lsusb
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
vkozlov@nezha:~$ sudo modprobe -v 8723ds
vkozlov@nezha:~$ ip a
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
3: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 8a:7d:bd:0a:5d:eb brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 2c:05:47:53:96:e9 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.98/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
       valid_lft 43089sec preferred_lft 43089sec
    inet6 fe80::5ac3:81c2:192c:a669/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
vkozlov@nezha:~$

 

Here's how it does look on my Sipeed D1 board ^^

 

Edited by vkozlov
Link to comment
Share on other sites

MangoPI

Just downloaded the image from the website, recorded it on the SD card and launched

 

root@nezha:~# uname -a
Linux nezha 6.4.0-rc6-d1 #trunk Fri Jun 16 09:23:49 MSK 2023 riscv64 riscv64 riscv64 GNU/Linux
root@nezha:~# ip a
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
3: usb0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 8a:7d:bd:0a:5d:eb brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 94:a4:08:cd:88:9c brd ff:ff:ff:ff:ff:ff
    inet 10.1.30.37/24 brd 10.1.30.255 scope global dynamic noprefixroute wlan0
       valid_lft 25047sec preferred_lft 25047sec
    inet6 fe80::f69c:a60f:64e3:e69e/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
root@nezha:~# 
 

Link to comment
Share on other sites

Version 20230630-current for Allwinner D1.

The package composition has changed significantly, now the system is close to other platforms in terms of package composition.

Fixed Debian startup.

 

Version 20230630-edge (6.4.0)  for Allwinner D1.

Link to comment
Share on other sites

Version 20230702-current with kernel 6.2 for StarFive 1 (jh7100).

When starting Debian with DE XFCE\IceWM, there is a bug, immediately at the first start the system switches to Lightdm, to start correctly, switch to the first console (Ctl+Alt+F1) and perform the initial configuration of the system, and reboot system.

With a number of limitations, you can even watch videos in windowed mode using the PAROLE player and a USB sound card.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines