Jump to content

Board Bring Up Station P1 rk3399, M1 rk3328

balbes150

By balbes150
in Rockchip

 Share

Recommended Posts

Recommended

Posted by balbes150,

Update to version 20210319. Using kernel 5.10.24. Added support for Firefly-rk3399 in station-p1 images (for proper operation, you need to configure DTB in extlinux.conf). With the correct DTB setup, the HDMI audio LAN WiFi BT works in kernel 5.10. In kernel 4.4 worck remote control and analog sound. 
Recommended by Werner
3

Reputation Points

Go to this post
Chris4arm

Chris4arm

Posted
Posted
7 hours ago, balbes150 said:

Version 20220311-legacy for Station M1, which adds support for BT.

To turn on BT, after the initial system startup and logging in to XFCE, turn on BT in the bluetooth manager and restart the system. After that, you can connect BT devices.

 

 

Thanks balbes150,

I'll wait the Bullseye server image...

Link to comment
Share on other sites
Chris4arm

Chris4arm

Posted
Posted
30 minutes ago, Chris4arm said:

 

Thanks, but I see only a desktop image, not a server one. I'll try it however...

 

So, with Armbian_22.05.0-trunk_Station-m1_bullseye_edge_5.16.12_xfce_desktop.img :

the rtk_hciattach command times out  :

  

root@station-m1:~# rtk_hciattach -n -s 115200 /dev/ttyS2 rtk_h5
noflow
Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H5
Realtek Bluetooth :Realtek hciattach version 4.1 

Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 4, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 5, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 6, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 7, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 8, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 9, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 10, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 11, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 12, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 13, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 14, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 15, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 16, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 17, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 18, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 19, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 20, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 21, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 22, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 23, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 24, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 25, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 26, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 27, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 28, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 29, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 30, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 31, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 32, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 33, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 34, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 35, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 36, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 37, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 38, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 39, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 40, len: 8

Realtek Bluetooth ERROR: H5 sync timed out

root@station-m1:~# 
root@station-m1:~# rfkill 
ID TYPE DEVICE      SOFT      HARD
 0 wlan phy0   unblocked unblocked
root@station-m1:~#

 

Something missing...

 

Chris

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
1 минуту назад, Chris4arm сказал:

So, with Armbian_22.05.0-trunk_Station-m1_bullseye_edge_5.16.12_xfce_desktop.img :

 

11.03.2022 в 11:23, balbes150 сказал:

Version 20220311-legacy for Station M1, which adds support for BT.

legacy = kernel 4.4

edge = kernel 5.16

support BT for m1 only legacy (4.4)

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
11 минут назад, Chris4arm сказал:

Ok but I don't see a legacy bullseye server (not desktop) image in your test repository https://disk.yandex.ru/d/yY2wu1u4p7j4CQ ...

 

The link you provided is intended for other purposes. See the general directory for M1 , subdirectory 20220311-legacy.

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

Link to comment
Share on other sites
Chris4arm

Chris4arm

Posted
Posted
45 minutes ago, balbes150 said:

The link you provided is intended for other purposes. See the general directory for M1 , subdirectory 20220311-legacy.

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

 

thanks for your fast answers.

So I tried Armbian_22.05.0-trunk_Station-m1_bullseye_legacy_4.4.213.img

Unfortunately the result is the same as for 5.16.12 : the rtk_hciattach command ends in "Realtek Bluetooth ERROR: H5 sync timed out" (from rc.local or later by hand).

Note there are many warnings while boot, here are the most severe : 

root@station-m1:~# journalctl -b -p err
-- Journal begins at Sat 2022-03-12 05:59:51 UTC, ends at Sun 2022-03-13 10:33:08 UTC. --
Mar 12 05:59:51 station-m1 kernel: Failed to find legacy iommu devices
Mar 12 05:59:51 station-m1 kernel: vcc_sd: regulator get failed, ret=-517
Mar 12 05:59:51 station-m1 kernel: rk-vcodec vpu_combo: failed on clk_get clk_cabac
Mar 12 05:59:51 station-m1 kernel: rk-vcodec vpu_combo: failed on clk_get clk_core
Mar 12 05:59:51 station-m1 kernel: rk-vcodec vpu_combo: could not find power_model node
Mar 12 05:59:51 station-m1 kernel: i2c i2c-4: of_i2c: modalias failure on /hdmi@ff3c0000/ports
Mar 12 05:59:51 station-m1 kernel: rk_gmac-dwmac ff540000.ethernet: cannot get clock clk_mac_speed
Mar 12 05:59:51 station-m1 kernel: .. rk pwm remotectl v1.1 init
Mar 12 05:59:51 station-m1 kernel: cpu cpu0: Failed to get pvtm
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: unable to get devfreq-event device : dfi
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'ov4689' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'ov7750' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'ov13850' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'sc031gs' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: rockchip ion idev is NULL
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: Failed to get pvtm
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: failed to get vop bandwidth to dmc rate
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: failed to get vop pn to msch rl
Mar 12 05:59:51 station-m1 kernel: devfreq dmc: Couldn't update frequency transition information.
Mar 12 05:59:51 station-m1 kernel: cgroup: cgroup2: unknown option "nsdelegate,memory_recursiveprot"
Mar 12 05:59:51 station-m1 kernel: cgroup: cgroup2: unknown option "nsdelegate"
Mar 12 05:59:52 station-m1 kernel: mali-utgard ff300000.gpu: Failed to get pvtm
Mar 12 05:59:52 station-m1 kernel: devfreq ff300000.gpu: Couldn't update frequency transition information.
Mar 12 05:59:53 station-m1 kernel: Error: Driver 'bcmdhd_wlan' is already registered, aborting...
Mar 12 05:59:53 station-m1 kernel: Error: Driver 'bcm4329_wlan' is already registered, aborting...
Mar 12 05:59:54 station-m1 kernel: Error: Driver 'rtl8723ds' is already registered, aborting...
Mar 12 05:59:54 station-m1 kernel: Error: Driver 'bcmdhd_wlan' is already registered, aborting...
Mar 12 05:59:54 station-m1 kernel: Error: Driver 'bcm4329_wlan' is already registered, aborting...
Mar 12 05:59:55 station-m1 kernel: Error: Driver 'rtl8723ds' is already registered, aborting...
Mar 12 05:59:59 station-m1 kernel: proc: unrecognized mount option "hidepid=invisible" or missing value
Mar 12 05:59:59 station-m1 smartd[1523]: In the system's table of devices NO devices found to scan
Mar 12 06:00:00 station-m1 kernel: proc: unrecognized mount option "hidepid=invisible" or missing value
Mar 13 10:03:26 station-m1 systemd[1]: Timed out waiting for device /dev/ttyFIQ0.
Mar 13 10:18:51 station-m1 kernel: proc: unrecognized mount option "hidepid=invisible" or missing value

 

 

A "armbianmonitor -u" is at http://ix.io/3S6E ...
 

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
4 минуты назад, Chris4arm сказал:

Unfortunately the result is the same as for 5.16.12 : the rtk_hciattach command ends in "Realtek Bluetooth ERROR: H5 sync timed out" (from rc.local or later by hand).

Do you read the instructions carefully ? rtk_hciattach autorun has already been added to these images, but you must turn on the bluetooth manager yourself (for those who need it) and restart the system so that BT will automatically start.

 

11.03.2022 в 11:23, balbes150 сказал:

To turn on BT, after the initial system startup and logging in to XFCE, turn on BT in the bluetooth manager and restart the system. After that, you can connect BT devices.

 

Link to comment
Share on other sites
Chris4arm

Chris4arm

Posted
Posted
3 hours ago, balbes150 said:

Do you read the instructions carefully ? rtk_hciattach autorun has already been added to these images, but you must turn on the bluetooth manager yourself (for those who need it) and restart the system so that BT will automatically start.

 

 

 

Sorry but rtk_hciattach autorun fails, even after reboot :

  

root@station-m1:~# journalctl -b|egrep rc.local
Mar 13 13:56:56 station-m1 systemd[1]: Starting /etc/rc.local Compatibility...
Mar 13 13:56:58 station-m1 rc.local[1548]: Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H5
Mar 13 13:56:58 station-m1 rc.local[1548]: Realtek Bluetooth :Realtek hciattach version 4.1
Mar 13 13:56:58 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8
Mar 13 13:56:58 station-m1 systemd[1]: Started /etc/rc.local Compatibility.
Mar 13 13:56:58 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8
Mar 13 13:56:58 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8
Mar 13 13:56:58 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 4, len: 8
Mar 13 13:56:59 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 5, len: 8
Mar 13 13:56:59 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 6, len: 8
Mar 13 13:56:59 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 7, len: 8
Mar 13 13:56:59 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 8, len: 8
Mar 13 13:57:00 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 9, len: 8
Mar 13 13:57:00 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 10, len: 8
Mar 13 13:57:00 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 11, len: 8
Mar 13 13:57:00 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 12, len: 8
Mar 13 13:57:01 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 13, len: 8
Mar 13 13:57:01 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 14, len: 8
Mar 13 13:57:01 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 15, len: 8
Mar 13 13:57:01 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 16, len: 8
Mar 13 13:57:02 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 17, len: 8
Mar 13 13:57:02 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 18, len: 8
Mar 13 13:57:02 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 19, len: 8
Mar 13 13:57:02 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 20, len: 8
Mar 13 13:57:03 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 21, len: 8
Mar 13 13:57:03 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 22, len: 8
Mar 13 13:57:03 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 23, len: 8
Mar 13 13:57:03 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 24, len: 8
Mar 13 13:57:04 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 25, len: 8
Mar 13 13:57:04 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 26, len: 8
Mar 13 13:57:04 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 27, len: 8
Mar 13 13:57:04 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 28, len: 8
Mar 13 13:57:05 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 29, len: 8
Mar 13 13:58:44 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 30, len: 8
Mar 13 13:58:44 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 31, len: 8
Mar 13 13:58:45 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 32, len: 8
Mar 13 13:58:45 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 33, len: 8
Mar 13 13:58:45 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 34, len: 8
Mar 13 13:58:45 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 35, len: 8
Mar 13 13:58:46 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 36, len: 8
Mar 13 13:58:46 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 37, len: 8
Mar 13 13:58:46 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 38, len: 8
Mar 13 13:58:46 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 39, len: 8
Mar 13 13:58:47 station-m1 rc.local[1548]: Realtek Bluetooth :3-wire sync pattern resend : 40, len: 8
Mar 13 13:58:47 station-m1 rc.local[1548]: Realtek Bluetooth ERROR: H5 sync timed out
Mar 13 13:58:47 station-m1 rc.local[1548]: noflow
root@station-m1:~# 
root@station-m1:~# hcitool dev
Devices:
root@station-m1:~#

 

so there is no hci bt device to manage :(

 

Chris

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
3 часа назад, Chris4arm сказал:

Sorry but rtk_hciattach autorun fails, even after reboot :

 

11.03.2022 в 11:23, balbes150 сказал:

To turn on BT, after the initial system startup and logging in to XFCE, turn on BT in the bluetooth manager and restart the system. After that, you can connect BT devices.

 

Link to comment
Share on other sites
Chris4arm

Chris4arm

Posted
Posted
1 hour ago, Chris4arm said:

 

Ok but there is no XFCE in Armbian_22.05.0-trunk_Station-m1_bullseye_legacy_4.4.213.img :wacko:

Is it possible to do that with command lines  ?

 

Thanks,

Chris

 

ok, I've found : rfkill unblock bluetooth :)

 

thanks

 

 

Link to comment
Share on other sites
mo123

mo123

Posted
Posted
On 3/16/2022 at 5:54 PM, Chris4arm said:

 

Hi,

 

any hope to have BT support in Bullseye  5.15  soon ?

 

Chris

I just got bluetooth working but on the Station P1 for Bullseye 5.15

It uses RTL8723DU bluetooth.

It uses serial0 while the Station M1 uses serial2 for bluetooth.

Only thing I can think of is that the serial2 is in use somewhere by Armbian and doesn't get released for bluetooth or there might be a small bug in the kernel driver for RTL8723DS bluetooth that work differently than RTL8723BS, RTL8723DU. It's very difficult to find the exact cause but there is hope.

Link to comment
Share on other sites
Chris4arm

Chris4arm

Posted
Posted
14 hours ago, mo123 said:

I just got bluetooth working but on the Station P1 for Bullseye 5.15

It uses RTL8723DU bluetooth.

It uses serial0 while the Station M1 uses serial2 for bluetooth.

Only thing I can think of is that the serial2 is in use somewhere by Armbian and doesn't get released for bluetooth or there might be a small bug in the kernel driver for RTL8723DS bluetooth that work differently than RTL8723BS, RTL8723DU. It's very difficult to find the exact cause but there is hope.

 

Hi mo123,

 

in Armbian_22.05.0-trunk_Station-m1_bullseye_edge_5.16.12_xfce_desktop.img,

ttyS2 is there : 

[    1.677546] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 20, base_baud = 1500000) is a 16550A


and not in use, but the rtk_hciattach falls in timeout because there is nothing to reply to it :


  

root@station-m1:/boot# rtk_hciattach  -s 115200 /dev/ttyS2 rtk_h5
noflow
Realtek Bluetooth init uart with init speed:115200, final_speed:115200, type:HCI UART H5
Realtek Bluetooth :Realtek hciattach version 4.1 

Realtek Bluetooth :3-wire sync pattern resend : 1, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 2, len: 8

Realtek Bluetooth :3-wire sync pattern resend : 3, len: 8
[...]

Realtek Bluetooth :3-wire sync pattern resend : 40, len: 8

Realtek Bluetooth ERROR: H5 sync timed out

 

the 8723ds module version is v5.1.1.5_20523.20161209_BTCOEX20161208-1212


what have you done to get BT up ?

 

Chris

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted

The test version for Station P1 of ArmbianTV 20220324 with a new version of u-boot-2022.

Allows you to select different systems when starting on the TV screen from the keyboard.

This will allow you to have several different systems on eMMC at once and choose which system to run.

 

Please note, this is a test version and there may be errors in it. I recommend checking its operation by launching it from an SD card.

 

@mo123 I tested BT with 5.16 core on P1, everything works.

Link to comment
Share on other sites
mo123

mo123

Posted
Posted
2 hours ago, balbes150 said:

The test version for Station P1 of ArmbianTV 20220324 with a new version of u-boot-2022.

Allows you to select different systems when starting on the TV screen from the keyboard.

This will allow you to have several different systems on eMMC at once and choose which system to run.

 

Please note, this is a test version and there may be errors in it. I recommend checking its operation by launching it from an SD card.

 

@mo123 I tested BT with 5.16 core on P1, everything works.

 

Yes, seems bt is working on P1.

It seems it uses a USB driver and not uart so works out of the box :)

 

For P1, can you check the wifi driver?

It seems it builds the 5.13.4 driver for 5.15/5.16 kernels but should change to the master branch which has a fix otherwise wifi authentication fails after you type a wifi password.

https://github.com/150balbes/build/blob/armbian-tv/lib/compilation-prepare.sh#L660-L661

I tried LE too(from your Yandex link) but it doesn't show a wifi connection on P1 even after adding this master RTL8723DU branch package, so must be something else, perhaps the kernel config file or something changed in LE?

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
2 часа назад, Chris4arm сказал:

Hi, what about M1 ?

The same as before - BT is only on the legacy kernel.

 

 

New version 20220331-edge with core 5.16.18.

Important. Now u-boot-2022 is used with the enabled function of displaying the system (kernel) selection menu immediately at the startup stage. This allows you to have multiple systems (cores) on the media and select them from the keyboard immediately when the system starts.

Link to comment
Share on other sites
Chris4arm

Chris4arm

Posted
Posted

Hi,

 

I see many boot errors on my M1with the image Armbian_22.05.0-trunk_Station-m1_bullseye_legacy_4.4.213.img.

Here are only those tagged errors :

  

root@station-m1:~# journalctl -b -p err
-- Journal begins at Sat 2022-03-12 05:59:51 UTC, ends at Sun 2022-03-13 10:33:08 UTC. --
Mar 12 05:59:51 station-m1 kernel: Failed to find legacy iommu devices
Mar 12 05:59:51 station-m1 kernel: vcc_sd: regulator get failed, ret=-517
Mar 12 05:59:51 station-m1 kernel: rk-vcodec vpu_combo: failed on clk_get clk_cabac
Mar 12 05:59:51 station-m1 kernel: rk-vcodec vpu_combo: failed on clk_get clk_core
Mar 12 05:59:51 station-m1 kernel: rk-vcodec vpu_combo: could not find power_model node
Mar 12 05:59:51 station-m1 kernel: i2c i2c-4: of_i2c: modalias failure on /hdmi@ff3c0000/ports
Mar 12 05:59:51 station-m1 kernel: rk_gmac-dwmac ff540000.ethernet: cannot get clock clk_mac_speed
Mar 12 05:59:51 station-m1 kernel: .. rk pwm remotectl v1.1 init
Mar 12 05:59:51 station-m1 kernel: cpu cpu0: Failed to get pvtm
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: unable to get devfreq-event device : dfi
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'ov4689' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'ov7750' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'ov13850' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: Error: Driver 'sc031gs' is already registered, aborting...
Mar 12 05:59:51 station-m1 kernel: rockchip ion idev is NULL
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: Failed to get pvtm
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: failed to get vop bandwidth to dmc rate
Mar 12 05:59:51 station-m1 kernel: rockchip-dmc dmc: failed to get vop pn to msch rl
Mar 12 05:59:51 station-m1 kernel: devfreq dmc: Couldn't update frequency transition information.
Mar 12 05:59:51 station-m1 kernel: cgroup: cgroup2: unknown option "nsdelegate,memory_recursiveprot"
Mar 12 05:59:51 station-m1 kernel: cgroup: cgroup2: unknown option "nsdelegate"
Mar 12 05:59:52 station-m1 kernel: mali-utgard ff300000.gpu: Failed to get pvtm
Mar 12 05:59:52 station-m1 kernel: devfreq ff300000.gpu: Couldn't update frequency transition information.
Mar 12 05:59:53 station-m1 kernel: Error: Driver 'bcmdhd_wlan' is already registered, aborting...
Mar 12 05:59:53 station-m1 kernel: Error: Driver 'bcm4329_wlan' is already registered, aborting...
Mar 12 05:59:54 station-m1 kernel: Error: Driver 'rtl8723ds' is already registered, aborting...
Mar 12 05:59:54 station-m1 kernel: Error: Driver 'bcmdhd_wlan' is already registered, aborting...
Mar 12 05:59:54 station-m1 kernel: Error: Driver 'bcm4329_wlan' is already registered, aborting...
Mar 12 05:59:55 station-m1 kernel: Error: Driver 'rtl8723ds' is already registered, aborting...
Mar 12 05:59:59 station-m1 kernel: proc: unrecognized mount option "hidepid=invisible" or missing value
Mar 12 05:59:59 station-m1 smartd[1523]: In the system's table of devices NO devices found to scan
Mar 12 06:00:00 station-m1 kernel: proc: unrecognized mount option "hidepid=invisible" or missing value
Mar 13 10:03:26 station-m1 systemd[1]: Timed out waiting for device /dev/ttyFIQ0.
Mar 13 10:18:51 station-m1 kernel: proc: unrecognized mount option "hidepid=invisible" or missing value

 

A "armbianmonitor -u" is at http://ix.io/3S6E

 

Is there a mismatch between this firmware and the M1 ?

 

Chris

 

Link to comment
Share on other sites
balbes150

balbes150

Posted
  • Author
Posted
01.05.2022 в 18:45, Chris4arm сказал:

image Armbian_22.05.0-trunk_Station-m1_bullseye_legacy_4.4.213.img.

Where is the image taken from (link) ?

 

01.05.2022 в 18:45, Chris4arm сказал: 
Journal begins at Sat 2022-03-12

Where did such an old log come from ?

Link to comment
Share on other sites
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