Jump to content

Recommended Posts

Posted

Good news. Full-fledged working images (20210827) of ArmbianTV for P2 and M2  are ready. All the equipment works in them and you can start and configure the system via an HDMI monitor and a keyboard/mouse.  :)

 

M2

 

https://disk.yandex.ru/d/OBDO8BU2y1M6ug

 

https://users.armbian.com/balbes150/rk3566/

 

 

P2

 

https://disk.yandex.ru/d/neKXsYolKXgLzg

 

https://users.armbian.com/balbes150/rk3568/

Posted

¡Great job, balbes150! Thank you, all

System goes fine, and I am writing this from the Station P2.

Some details, I'm searching solutions for, but prefer to tell:

a) on boot, HDMI goes well, but colors are mixed. If I unplug & replug hdmi, this situation disapears, don't know why yet.

b) tried to pass system boot to emmc, twice, appears a /nand-sata-install.jusNh3 empty. Besides lsblk shows mmcblk0boot0 & mmcblk0boot1,

can't mount it:  mount: /mnt/mmcblk0boot1: wrong fs type, bad option, bad superblock on /dev/mmcblk0boot1, missing codepage or helper program, or other error.

If I find anything, I'll write back that.

Best regards, well done!

Francisco

Posted
20 часов назад, FJOtero сказал:

¡Great job, balbes150! Thank you, all

System goes fine, and I am writing this from the Station P2.

Some details, I'm searching solutions for, but prefer to tell:

a) on boot, HDMI goes well, but colors are mixed. If I unplug & replug hdmi, this situation disapears, don't know why yet.

b) tried to pass system boot to emmc, twice, appears a /nand-sata-install.jusNh3 empty. Besides lsblk shows mmcblk0boot0 & mmcblk0boot1,

can't mount it:  mount: /mnt/mmcblk0boot1: wrong fs type, bad option, bad superblock on /dev/mmcblk0boot1, missing codepage or helper program, or other error.

If I find anything, I'll write back that.

Best regards, well done!

The current version does not support installation in eMMC. Do not try to do this.

Posted

Thanks for telling so clear. I tried before your warning. Lost access to config pressing reset before power-up. So my mistake perhaps will be useful to prevent this for others. Thanks a lot, balbes150!!

Posted
On 8/27/2021 at 5:43 AM, balbes150 said:

Good news. Full-fledged working images (20210827) of ArmbianTV for P2 and M2  are ready. All the equipment works in them and you can start and configure the system via an HDMI monitor and a keyboard/mouse.  :)

 

M2

 

https://disk.yandex.ru/d/OBDO8BU2y1M6ug

 

https://users.armbian.com/balbes150/rk3566/

 

 

P2

 

https://disk.yandex.ru/d/neKXsYolKXgLzg

 

https://users.armbian.com/balbes150/rk3568/

Thank you so much for this.  I now have my Station P2 up and running Armbian.  I for one appreciate all the work you do with these new SBCs and variants of Linux/Armbian.

 

Thanks again!

 

Rick

Posted

@balbes150, Do your images support an m.2 SSD?  I can't seem to get Linux to recognize mine.  Using lsblk it does not show up. :(

 

Rick

Posted
09.09.2021 в 16:00, redjr сказал:

Do your images support an m.2 SSD?  I can't seem to get Linux to recognize mine.  Using lsblk it does not show up.

 

I connected the NVMe module to P2 , the system sees it and can work with it. Which image and which DTB are you using ? Here is the output of "fdisk -l", which clearly shows the presence of NVMe in the system.

 

Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: NE-128                                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

 

Armbian 21.11.0-trunk Hirsute ttyFIQ0 

station-m2 login: root
Password: 
 ____  _        _   _               __  __ ____  
/ ___|| |_ __ _| |_(_) ___  _ __   |  \/  |___ \ 
\___ \| __/ _` | __| |/ _ \| '_ \  | |\/| | __) |
 ___) | || (_| | |_| | (_) | | | | | |  | |/ __/ 
|____/ \__\__,_|\__|_|\___/|_| |_| |_|  |_|_____|
                                                 
Welcome to Armbian 21.11.0-trunk Hirsute with Linux 4.19.193

No end-user support: built from trunk

System load:   62%              Up time:       0 min
Memory usage:  6% of 3.68G      IP:            192.168.1.39
CPU temp:      30�°C            Usage of /:    32% of 15G    

[ 2 security updates available, 7 updates total: apt upgrade ]
Last check: 2021-09-08 14:13

Last login: Wed Sep  8 14:13:42 UTC 2021 on ttyFIQ0
root@station-m2:~# fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 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/mtdblock0: 32 MiB, 33554432 bytes, 65536 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/mmcblk0: 29.12 GiB, 31268536320 bytes, 61071360 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: 1E020000-0000-406A-8000-113E00001CED

Device            Start      End  Sectors  Size Type
/dev/mmcblk0p1    16384    24575     8192    4M unknown
/dev/mmcblk0p2    24576    32767     8192    4M unknown
/dev/mmcblk0p3    32768    40959     8192    4M unknown
/dev/mmcblk0p4    40960    49151     8192    4M unknown
/dev/mmcblk0p5    49152    51199     2048    1M unknown
/dev/mmcblk0p6    51200   116735    65536   32M unknown
/dev/mmcblk0p7   116736   124927     8192    4M unknown
/dev/mmcblk0p8   124928   321535   196608   96M unknown
/dev/mmcblk0p9   321536  1107967   786432  384M unknown
/dev/mmcblk0p10 1107968  1894399   786432  384M unknown
/dev/mmcblk0p11 1894400  1927167    32768   16M unknown
/dev/mmcblk0p12 1927168  8300543  6373376    3G unknown
/dev/mmcblk0p13 8300544  9349119  1048576  512M unknown
/dev/mmcblk0p14 9349120 61071326 51722207 24.7G unknown


Disk /dev/mmcblk1: 14.87 GiB, 15962472448 bytes, 31176704 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: BE4EF038-2CF8-46BD-8D6E-05E4769B6502

Device         Start      End  Sectors  Size Type
/dev/mmcblk1p1 32768    65535    32768   16M Linux filesystem
/dev/mmcblk1p2 65536 30834687 30769152 14.7G EFI System


Disk /dev/nvme0n1: 119.24 GiB, 128035676160 bytes, 250069680 sectors
Disk model: NE-128                                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
root@station-m2:~#

 

Posted

New version of images 20210915-edge with 5.15.0-rc1 kernel.
Please note, this version does not have an HDMI output, control is performed via SSH or UART. The wired network works, both LAN1 and LAN2 interfaces work on P2, M2 - LAN1.

Please note that this is the primary test version and unpredictable behaviors are possible.

Posted

@balbes150 At first I'd like to thank you for your great work to make armbian work on many Android boxes.

 

I have an X96 X6 Android box which based on RK3566. I've tried to use your latest M2 rk3566 image but there it could not be boot successfully. 

Posted
4 часа назад, chinhhut сказал:

I have an X96 X6 Android box which based on RK3566.

Only Station M2 P2 is discussed in this topic. If you want to have Armbian on rk35xx, use proven hardware. With your TV box, you need to contact the manufacturer or seller from whom you bought it.

Posted
19 minutes ago, balbes150 said:

Only Station M2 P2 is discussed in this topic. If you want to have Armbian on rk35xx, use proven hardware. With your TV box, you need to contact the manufacturer or seller from whom you bought it.

I got it. There is no option to delete my previous post so I just removed the unrelated content to Station M2 P2.

 

Thank you.

Posted

Update version 20211124 with legacy kernel.

 

 

p.s. Now I am testing a new image with a 5.16.rc2 kernel, in which HDMI and USB work. After all checks are completed, new versions of images with a new kernel will be available.  :)

Posted

Do the Armbian_21.11.0-trunk_Station-p2_bullseye_edge_5.16.0_xfce_desktop  boot with working hdmi? Do they boot from tf card or do they need to be flashed to the device?  Are the 5.16.0 images the same as the 5.16-rc2 images ? 

 

Thanks for all your hard work. 

 

For me the 5.16.0 images did not boot via hdmi but I do not have the cable to check via serial port at the moment and do not know how to properly get logs. I was trying to boot via tf card flashed via balena etcher. I have a station p2 8gb model.  

Posted
3 часа назад, LocationUnknown сказал:

For me the 5.16.0 images did not boot via hdmi but I do not have the cable to check via serial port at the moment and do not know how to properly get logs. I was trying to boot via tf card flashed via balena etcher. I have a station p2 8gb model. 

 

Everything works from an SD card. But to run, you must have the bootloader updated in eMMC. The order of how to do this is described at this link (mesenge  2021-9-20 19:05:26)

 

https://bbs.stationpc.com/forum.php?mod=viewthread&tid=209&extra=page%3D1%26filter%3Dauthor%26orderby%3Dlastpost

 

To check that you have updated the bootloader correctly, check the launch of the legacy kernel version (4.19) from the beginning.

If you have previously used your SD card for other images, perform a complete cleaning of the SD card with the DD command to remove all dirt from the previous systems.

Posted

Using the 5.16 build I was finally able to a working uart log reader. Here are my logs from the UART port. I could not get the port from the serial/rj45 to get readable logs.  Through the uart terminal using minicom I was able to login and go through the user/root setup like normal and the system does boot. It just seems to me there is still a issue with the hdmi. Thank you for your efforts and I hope this helps. I am using the station p2  by the way. The link is a pastbin of the full bootup until the login and the quoted error is the the only error in the log I could see. I am booting from the tf card if that matters. I have already updated the uboot too. 

 

https://zerobin.net/?8b0d1e0e3de2e359#CrJefubSkdktCEG5pxf1lYOGwdfkqPuQjOD8GT781tE=

 

 

5.068486] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068500] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068511] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068521] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068531] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068542] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068552] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068562] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068573] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0
[    5.068583] rockchip-drm display-subsystem: [drm] *ERROR* POST_BUF_EMPTY irq err at vp0

 

Posted
15 часов назад, LocationUnknown сказал:

Using the 5.16 build I was finally able to a working uart log reader. Here are my logs from the UART port. I could not get the port from the serial/rj45 to get readable logs.  Through the uart terminal using minicom I was able to login and go through the user/root setup like normal and the system does boot. It just seems to me there is still a issue with the hdmi. Thank you for your efforts and I hope this helps. I am using the station p2  by the way. The link is a pastbin of the full bootup until the login and the quoted error is the the only error in the log I could see. I am booting from the tf card if that matters. I have already updated the uboot too. 

 

VOP update mode to: 3840x2160p0, type: HDMI0 for VP0

 

Judging by the log, you have 4k TV. This permission is not supported. so far, only the 1920 x 1080 option is working. Please note, I have already written that HDMI support is a very early version that cannot fully work. Also in the log, I see that you do not have a wired LAN connection, there is no IP address for networks. Without this, you will not be able to use an SSH connection. Are you sure you have a P2 model? Show a photo of how the wire is connected to the LAN network card on your device.

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

Important Information

Terms of Use - Privacy Policy - Guidelines