Jump to content

Firefly Station M3 (rk3588s)

balbes150

By balbes150
in Rockchip

 Share

Recommended Posts

kjhdfgkio

kjhdfgkio

Posted
Posted (edited)

This is fantastic! It's the first Armbian I was able to get to boot on the ROC-RK3588S-PC board, which seems to be nearly identical to the board inside the M3.

 

The only issue I have is that it doesn't seem to recognize the NVMe drive, or perhaps I'm just doing something wrong. Any tips for troubleshooting the NVMe?

 

I'm using this image from the "20230330-legacy" folder: 

Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img

 

armbianmonitor logs at: https://paste.armbian.com/uyiwocajac

 

I also tried this image from the "20230330-current" folder:
  

Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz

 

Which booted fine, but seems to have no fancontrol, and also no NVMe. Logs for Lunar are at https://paste.armbian.com/catoxosije

 

The NVMe drive I'm using is the SABRENT 2TB Rocket NVMe PCIe M.2 2242 (SB-1342-2TB):
https://www.amazon.com/dp/B07XVRTG1H

Edited by kjhdfgkio
new details
0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted (edited)

It was a me issue... updating /boot/extlinux/extlinux.conf to point to "rk3588s-roc-pc-nvme.dtb" instead of "rk3588s-roc-pc.dtb" got the NVMe going.

 

For the Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz image, the blue post-boot LED never comes on and the fan is always full speed. I saw the prior note about replacing the "/usr/bin/firefly-fan-control" file, but it looks like the image is completely missing the firefly-fan-control file to start with. Running firefly-fan-control is verbose mode gets: 

set_PWM: 59000
 pwm: 50
pwm: 50
no such file /tmp/fan_temperature
no such file /tmp/fan_temperature
no such file /tmp/fan_temperature
set_PWM: 59000
 pwm: 50
SetValue: 53000.000000
ActualValue: 50000.000000
PID->Ek: 3000.000000
PID->LocSum: 3000.000000
PIDLoc: -4584.000000
pwm:50.000198 
count is 0
fan_switch is 1
PID_fan_func exit
set_PWM: 59000
 pwm: 50
SetValue: 53000.000000
ActualValue: 50000.000000
PID->Ek: 3000.000000
PID->LocSum: 3000.000000
PIDLoc: -7584.000000
pwm:50.000198

 

So, it seems the -current build is missing some stuff for fan control.

 

The other issue I have is that now that I've installed armbian on the eMMC, I can't seem to get this ROC-RK3588-PC to boot from the SDCard again. During boot I only get the Armbian logo image, and no amount of hitting space-bar gets me into to the uboot cli.

Edited by kjhdfgkio
doh!
0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
11 часов назад, kjhdfgkio сказал:

installed armbian on the eMMC

Write in detail how the installation was performed.

 

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

I can't seem to get this ROC-RK3588-PC to boot from the SDCard again

Check the launch from USB (burn the image to a USB flash drive instead of an SD card), connect to the device and turn on the power.  When starting Armbian, disabling the screensaver works with the ESC button

 

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

no amount of hitting space-bar gets me into to the uboot cli.

management from u-boot only works with android versions installed in eMMC , this is not a u-boot function, it is an additional intermediate add-on

0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted
Quote

Write in detail how the installation was performed.

  1. ROC-RK3588-PC running Firefly provided "ROC-RK3588S-PC_Ubuntu20.04-Gnome-r240_v1.0.6f_230404" image (which had been written over USB using RKDevTool 2.96 from a Windows 11 machine)
  2. Used Raspberry Pi Imager to write the provided image to an SDHC card on a Windows 11 machine
  3. Inserted SDHC card into the SBC's card slot
  4. Powered on the SBC
  5. It booted to Armbian
  6. Ran "lsblk", noticed there was no NVMe
  7. Edited "/boot/extlinux/extlinux.conf" to set the fdt file to "/boot/dtb/rockchip/rk3588s-roc-pc-nvme.dtb" (just added "-nvme" before ".dtb")
  8. Ran "reboot"
  9. Booted from Armbian again
  10. Ran "lsblk", was happy to see the "nvme0n1" drive - but noticed no partitions
  11. Ran "fdisk /dev/nvme0n1" - typed "n" for a new partition, took defaults, typed "w" to write and quit
  12. Typed 'armbian-install'
  13. Selected "Boot from eMMC - system on SATA, USB or NCMe" - answered "Y" to both prompts warning it would overwrite "mmcblk0p1" and "nvme0n1p1"
  14. Rebooted at the end
  15. Ran "mount" and was happy to see "/dev/nvme0n1p1 on /" and "/dev/mmcblk0p1 on /boot"
  16. Removed the SDHC card, tried power cycling a few more times, all seemed good
Quote

Check the launch from USB (burn the image to a USB flash drive instead of an SD card), connect to the device and turn on the power. 

The "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image on a USB flash drive seems to boot, as it gets to a point where the fan slows down and the post-boot blue LED just above the SD slot lights up, but there is no network or HDMI, so I can't do anything with it.

 

The "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image on a USB flash drive booted, and took me to the initial "Create root password" prompt. HDMI and networking worked great.

 

Thanks for the pointer here. USB flash drives are substantially faster than the SDHC cards, so this is a much better way to go.

 

 

Quote

When starting Armbian, disabling the screensaver works with the ESC button

Works great, thank you!

 

Quote

management from u-boot only works with android versions installed in eMMC , this is not a u-boot function, it is an additional intermediate add-on

Got it, thanks!

0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted

On the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image, I'm seeing a Kernel panic that seems somewhat random while reading/writing to the NVMe. Here are two examples of it (OCR'd from a photo of the panic ... pretty sure I double checked every character in it).

  

station-m3 login: [ 659.401029] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 659.401730] CPU: 5 PID: 1 Comm: systemd Tainted: G    W    6.2.0-rc1-station-m3 #23.02.3
[ 659.402523] Hardware name: Firefly ROC-RK3588S-PC NVMe (DT)
[ 659.403017] Call trace:
[ 659.403236] dump_backtrace+0xdc/0x130
[ 659.403577] show_stack+0x18/0x30
[ 659.403874] dump_stack_lvl+0x64/0x80
[ 659.404204] dump_stack+0x18/0x34
[ 659.404502] panic+0x180/0x330
[ 659.404776] make_task_dead+0x0/0x16c
[ 659.405104] do_group_exit+0x34/0x90
[ 659.405423] get_signal+0x830/0x894
[ 659.405734] do_notify_resume+0x2d0/0x1310
[ 659.406101] el0_svc+0xa4/0xb4
[ 659.406375] el0t_64_sync_handler+0xf4/0x120
[ 659.406754] elot_64_sync+0x1a0/0x1a4
[ 659.407081] SMP: stopping secondary CPUs
[ 659.407496] Kernel Offset: disabled
[ 659.407806] CPU features: 0x60000,000e0148,cc00720b
[ 659.408239] Memory Limit: none
[ 659.414666]---[ end Kernel panic- not syncing: Attempted to kill init! exitcode=0x0000000b ]---

 

 

  

station-m3 login: [ 1298.038509] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 1298.039211] CPU: 7 PID: 1 Comm: systemd Tainted: G    W     6.2.0-rc1-station-m3 #23.02.3
[ 1298.040004] Hardware name: Firefly ROC-RK3588S-PC NVMe (DT)
[ 1298.040498] Call trace:
[ 1298.040718] dump_backtrace+0xdc/0x130
[ 1298.041060] show_stack+0x18/0x30
[ 1298.041358] dump_stack_lvl+0x64/0x80
[ 1298.041688] dump_stack+0x18/0x34
[ 1298.041986] panic+0x180/0x330
[ 1298.042260] make_task_dead+0x0/0x16c
[ 1298.042587] do_group_exit+0x34/0x90
[ 1298.042906] get_signal+0x830/0x894
[ 1298.043217] do_notify_resume+0x2d0/0x1310
[ 1298.043583] el0_undef+0xf0/0xf4
[ 1298.043871] el0t_64_sync_handler+0xa0/0x120
[ 1298.044251] el0t_64_sync+0x1a0/0x1a4
[ 1298.044578] SMP: stopping secondary CPUs
[ 1298.044930] Kernel Offset: disabled
[ 1298.045239) CPU features: 0x60000,000e0148, cc00720b
[ 1298.045671] Memory Limit: none
[ 1298.052109] ---[ end Kernel panic- not syncing: Attempted to kill init! exitcode=0x0000000b ]---

 

 

I had another one that was a paging issue during a find_inode_fast call, but it seems to have been fixed by changing mergerfs to have "cache.files=off" rather than "cache.files=full" or "partial", so I'm assuming mergerfs just isn't fully 6.2.0 compatible yet.

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
9 часов назад, kjhdfgkio сказал:

Used Raspberry Pi Imager to write the provided image to an SDHC card on a Windows 11 machine

the exact name of the image (or a link to it)

 

9 часов назад, kjhdfgkio сказал:

ROC-RK3588-PC running Firefly provided "ROC-RK3588S-PC_Ubuntu20.04-Gnome-r240_v1.0.6f_230404" image (which had been written over USB using RKDevTool 2.96 from a Windows 11 machine)

What was in eMMC before and what steps did you do earlier on M3 (installing different versions of Android\StationOS, including multiloading or other experiments with the previous system).

 

9 часов назад, kjhdfgkio сказал:

is no network or HDMI

Which monitor is connected and how ?

 

9 часов назад, kjhdfgkio сказал:

On the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image, I'm seeing a Kernel panic that seems somewhat random while reading/writing to the NVMe. Here are two examples of it (OCR'd from a photo of the panic ... pretty sure I double checked every character in it).

This is a core for development, it has many flaws and bugs. 

0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted
On 4/10/2023 at 2:36 AM, balbes150 said:

the exact name of the image (or a link to it)

"Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz"

 

On 4/10/2023 at 2:36 AM, balbes150 said:

What was in eMMC before and what steps did you do earlier on M3 (installing different versions of Android\StationOS, including multiloading or other experiments with the previous system).

Whatever Android came on the eMMC for the device that Firefly shipped to me last week. I didn't actually look at the Android build, I just immediately used RKDevTool to flash "ROC-RK3588S-PC_Ubuntu20.04-Gnome-r240_v1.0.6f_230404" to it.

 

On 4/10/2023 at 2:36 AM, balbes150 said:

Which monitor is connected and how ?

I've tried both a Dell U4021QW and a Phillips 272P7VUBNB/27. Both are just a direct HDMI cable from the RK's HDMI output port to the HDMI1 port on the monitor. I also tried a few different HDMI cables, some active, some passive. Again, works fine on USB boot from the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image, but not the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image.

 

On 4/10/2023 at 2:36 AM, balbes150 said:

This is a core for development, it has many flaws and bugs. 

Understood. Any pointers to ways I can collect more information or kernel dumps to help the team troubleshoot these issues?

 

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
16 часов назад, kjhdfgkio сказал:

but not the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image.

try to burn images 5.10 from the directory 20230302 to the SD card and check their launch, and then burn the same image to USB and check its operation.

0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted
7 hours ago, balbes150 said:

try to burn images 5.10 from the directory 20230302 to the SD card and check their launch, and then burn the same image to USB and check its operation.

  • "Armbian_23.02.0-trunk_Station-m3_jammy_legacy_5.10.110.img.xz" from the 20230302 folder on a USB flash drive has a "not syncing" kernel panic during boot. The normal shift+pageup doesn't seem to work for scrolling back up to get stack info.
  • "Armbian_23.02.0-trunk_Station-m3_jammy_legacy_5.10.110.img.xz" from the 20230302 folder on an SD card has the same "not syncing" kernel panic during boot.

 

I tried the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image again from USB and got video this time (no changes, just worked this time?). It also landed at a "not syncing" kernel panic. When the stock bootloader was on the device I was able to boot the "Armbian_23.02.3_Station-m3_jammy_legacy_5.10.110.img.xz" image from SD and flash the device (eMMC bootloader/eMMC system), but after flashing the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image (eMMC bootloader, SSD system) the jammy images seem to panic during boot.

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
16 часов назад, kjhdfgkio сказал:

but after flashing the "Armbian_23.02.3_Station-m3_lunar_current_6.2.0.img.xz" image (eMMC bootloader, SSD system) the jammy images seem to panic during boot.

do not install versions with kernel 6.2 on eMMC, these are test versions with possible bugs and errors.

0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted (edited)

 

On 4/13/2023 at 1:45 AM, balbes150 said:

do not install versions with kernel 6.2 on eMMC, these are test versions with possible bugs and errors.

I moved the eMMC install back to the legacy kernel.

 

Any tips for collecting kernel panic dumps or auto-rebooting after a kernel panic? I set "kernel.panic=5" in /etc/sysctl.conf, but it seems to only reboot for about 1 in 5 kernel panics. For the other ones, everything has scrolled so far up that I can't get the details and the normal up arrows, or ctl+page up, keyboard sequences aren't scrolling. All the methods I know for getting kernel panic dumps require building the kernel on my own...

I also tried installing the system watchdog service (apt install watchdog), but the /dev/watchdog device that exists in the Firefly linux image seems to be missing in this Armbian image. There are more details at https://wiki.t-firefly.com/en/ROC-RK3588S-PC/usage_watchdog.html

 

Edited by kjhdfgkio
watchdog
0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
15 часов назад, kjhdfgkio сказал:

Any tips for collecting kernel panic dumps or auto-rebooting after a kernel panic?

What kind of core panic are you writing about ? I don't see any messages about legacy kernel panic.

0
Link to comment
Share on other sites
kjhdfgkio

kjhdfgkio

Posted
Posted
On 5/2/2023 at 2:53 AM, balbes150 said:

What kind of core panic are you writing about ? I don't see any messages about legacy kernel panic.

I'm not sure since I can't scroll up and I haven't been able to catch it as it is happening with a camera as I haven't found a specific trigger, but I've attached a picture of the not-very-useful end of it.

I'm running the Plex server inside a docker container and it seems to be associated with Plex rescanning the media collection on a 2 hour timer, but I can't trigger it on manual rescans. There are no Plex clients trying to get media from this as I've just set it up on my desk to test the board out to see if it can replace my current Plex server.

end.jpg

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
20 часов назад, kjhdfgkio сказал:

I'm not sure since I can't scroll up and I haven't been able to catch it as it is happening with a camera as I haven't found a specific trigger, but I've attached a picture of the not-very-useful end of it.

where is the system installed ? If on USB\SD, you can connect the media to the PC and open the log file and see the full output (/var/log) and find the reason that causes the kernel to panic. If the system is on SATA\NVMe - start the system from SD\USB media, mount SATA\NVMe and see the same logs.

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

Ver 20230609-edge (use u-boot) kernel 6.4-rc5 (no HDMI)

20230609-EDK2-EFI-edge kernel 6.4-rc5 - HDMI work only EDK2 (grub), HDMI in system not work

 

  

root@192.168.1.20's password: 
 ____  _        _   _               __  __ _____ 
/ ___|| |_ __ _| |_(_) ___  _ __   |  \/  |___ / 
\___ \| __/ _` | __| |/ _ \| '_ \  | |\/| | |_ \ 
 ___) | || (_| | |_| | (_) | | | | | |  | |___) |
|____/ \__\__,_|\__|_|\___/|_| |_| |_|  |_|____/ 
                                                 
Welcome to Armbian 23.04 Lunar with bleeding edge Linux 6.4.0-rc5-media

No end-user support: built from trunk

System load:   36%           	Up time:       3 min	
Memory usage:  2% of 7.76G  	IP:	       192.168.1.20
CPU temp:      37°C           	Usage of /:    51% of 3.4G   	
RX today:      0 B  	

[ 30 security updates available, 35 updates total: apt upgrade ]
Last check: 2023-06-09 10:03

Last login: Fri Jun  9 13:03:38 2023
root@station-m3:~# neofetch 
                                 root@station-m3 
                                 --------------- 
      █ █ █ █ █ █ █ █ █ █ █      OS: Armbian (23.04) aarch64 
     ███████████████████████     Host: Firefly ROC-RK3588S-PC SATA 
   ▄▄██                   ██▄▄   Kernel: 6.4.0-rc5-media 
   ▄▄██    ███████████    ██▄▄   Uptime: 3 mins 
   ▄▄██   ██         ██   ██▄▄   Packages: 549 (dpkg) 
   ▄▄██   ██         ██   ██▄▄   Shell: bash 5.2.15 
   ▄▄██   ██         ██   ██▄▄   Terminal: /dev/pts/0 
   ▄▄██   █████████████   ██▄▄   CPU: (8) 
   ▄▄██   ██         ██   ██▄▄   Memory: 198MiB / 7943MiB 
   ▄▄██   ██         ██   ██▄▄
   ▄▄██   ██         ██   ██▄▄                           
   ▄▄██                   ██▄▄                           
     ███████████████████████
      █ █ █ █ █ █ █ █ █ █ █

root@station-m3:~# lspci
root@station-m3:~# fdisk -l
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram0: 3.88 GiB, 4164710400 bytes, 1016775 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/sda: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: GN128           
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: 0xfa4731db

Device     Boot     Start       End   Sectors  Size Id Type
/dev/sda1            2048 216059903 216057856  103G 83 Linux
/dev/sda2       216059904 250068991  34009088 16.2G 82 Linux swap / Solaris


Disk /dev/mmcblk1: 58.24 GiB, 62537072640 bytes, 122142720 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: gpt
Disk identifier: E17A25F6-9411-4879-B537-9B2E202E5AFF

Device         Start       End   Sectors  Size Type
/dev/mmcblk1p1 32768 120913919 120881152 57.6G Linux filesystem


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 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


Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 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


Disk /dev/sdb: 3.7 GiB, 3967811584 bytes, 7749632 sectors
Disk model: Silicon-Power4G 
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: gpt
Disk identifier: 0AEF938A-4585-154F-81FE-D01D61B5A6EC

Device     Start     End Sectors  Size Type
/dev/sdb1  32768 7340032 7307265  3.5G Linux filesystem


Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@station-m3:~#

 

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

Ver 20230911-EDK2-EFI kernel legacy\current\edge 

 

On the edge version, HDMI does not work in the kernel itself, but HDMI is supported at the level of the selection menu in GRUB, this allows you to have several different versions of the kernel\system (for example, add a self-assembled EDGE kernel with its own configuration) and choose on the monitor screen which kernel\system to run not using the UART console.

0
Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

I launched the system on Station M3 on a 4k monitor (desktop resolution 4096×2160), checked the full-screen playback of all formats via MPV that I use (including 4k), everything is played without brakes. The temperature is 35-50 degrees (the fan is running at minimum rpm). I use a simple USB sound card to output sound. 

Similarly, everything works smoothly and without brakes when using KODI and copes with all the found video decoding formats in SW mode without any problems (there is enough performance).  :)

0
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...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept