6 6
chwe

RockPi 4b 'board bring up'

Recommended Posts

Just building a fresh image right now.

 

BTW, this is my compile line.

git pull && ./compile.sh docker KERNEL_ONLY=no KERNEL_CONFIGURE=no BUILD_DESKTOP=no BRANCH=dev RELEASE=bionic BOARD=rockpi-4b
[ o.k. ] Done building [ /root/armbian/output/images/Armbian_5.77_Rockpi-4b_Ubuntu_bionic_dev_4.20.13.img ]

Will test in the evening. and report back.

Share this post


Link to post
Share on other sites
9 hours ago, Vonor said:

Will test in the evening. and report back.

Test done. fresh build (Armbian_5.77_Rockpi-4b_Ubuntu_bionic_dev_4.20.13.img)

Nothing was changed after building the image, except for coping the files as suggested.

 

I was watching syslog (tail -f) while I waited for it to happen. But couldn't see anything unusual when it started.

Perhaps it has to do with the Fritzbox I am connecting to (5GHz) ? I'll try using an older android phone as AP to see if that makes a change.

 

If you guys have suggestions on how to debug it further to provide additional valuable info, please let me know.

 

Spoiler

$ ssh user@172.16.0.2 "uptime && dmesg | grep -Ei 'sdio|brcmf' && sleep 22m && uptime && dmesg | grep -Ei 'sdio|brcmf'"
user@172.16.0.2's password: 
 21:00:13 up 0 min,  1 user,  load average: 0.52, 0.15, 0.05
[    2.311916] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    7.086903] brcmfmac: F1 signature read @0x18000000=0x15294345
[    7.091415] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    7.341825] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    7.355716] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84
 21:22:27 up 22 min,  1 user,  load average: 0.02, 0.02, 0.00
[    2.311916] mmc0: new ultra high speed SDR104 SDIO card at address 0001
[    7.086903] brcmfmac: F1 signature read @0x18000000=0x15294345
[    7.091415] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    7.341825] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[    7.355716] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84
[ 1075.630493] brcmfmac: brcmf_sdio_hostmail: mailbox indicates firmware halted
[ 1078.735681] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1078.741666] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1081.295715] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1081.300309] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1081.300321] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1083.855599] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1083.860790] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1086.415639] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1086.419623] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1086.419634] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1088.975518] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1088.979551] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1091.535503] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1091.539535] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1091.539547] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1094.095437] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1094.099483] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1096.655474] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1096.659585] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1096.659595] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1099.215359] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1099.220587] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1101.775393] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1101.779765] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1101.779776] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1104.335276] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1104.339595] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1106.895311] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1106.900325] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1106.900336] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1109.455198] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1109.461725] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1112.015126] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1112.019440] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1112.019457] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1114.575144] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1114.578566] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1117.134969] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1117.138393] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1117.138405] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1119.695048] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1119.698454] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1122.254900] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1122.258441] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1122.258457] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1124.815010] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1124.818583] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1127.374806] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1127.378360] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1127.378375] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1129.934888] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1129.938422] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1132.494725] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1132.498278] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1132.498294] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1135.054808] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1135.058340] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1137.614648] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1137.618203] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1137.618218] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1140.174726] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1140.178260] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1142.734559] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1142.738114] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1142.738130] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1145.294688] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1145.299136] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1147.854509] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1147.857947] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1147.857959] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1150.414564] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1150.417970] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1152.974398] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1152.977820] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1152.977831] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1155.534481] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1155.538016] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1158.094311] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1158.097868] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1158.097884] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1160.654416] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1160.657989] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1163.214236] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1163.217791] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1163.217807] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1165.774318] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1165.777853] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1168.334158] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1168.337696] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1168.337712] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1170.894294] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1170.897867] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1173.454075] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1173.457633] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1173.457649] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1176.014157] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1176.017691] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1178.573994] brcmfmac: brcmf_sdio_bus_rxctl: resumed on timeout
[ 1178.577548] brcmfmac: brcmf_sdio_checkdied: firmware trap in dongle
[ 1178.577564] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1181.134087] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1183.693934] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1183.693947] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1186.254007] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1188.813864] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1188.813875] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1191.373928] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1193.933787] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1193.933797] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1196.493844] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1199.053654] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1199.053667] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1201.613767] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1204.173596] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1204.173608] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1206.733698] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1209.293520] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1209.293533] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1211.853648] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1214.413440] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1214.413452] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1216.973521] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1219.533356] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1219.533368] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1222.093438] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1224.653274] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1224.653287] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1227.213357] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1229.773207] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1229.773220] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1232.333279] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1234.893141] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1234.893154] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1237.453196] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1240.012973] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1240.012985] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1242.573117] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1245.132949] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1245.132958] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1247.693034] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1250.252866] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1250.252878] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1252.813012] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1255.372789] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1255.372802] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1257.932920] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1260.492708] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1260.492721] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1263.052796] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1265.612628] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1265.612641] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1268.172710] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1270.732675] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1270.732688] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1273.292630] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1275.852501] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1275.852514] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1278.412549] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1280.972422] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1280.972434] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1283.532471] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1286.092303] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1286.092315] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1288.652390] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1291.212223] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1291.212236] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1293.772307] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1296.332131] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1296.332141] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1298.892283] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1301.452058] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1301.452069] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1304.012197] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1306.571977] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1306.571990] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1309.132066] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1311.691897] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1311.691909] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1314.251983] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1316.811842] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1316.811854] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1319.371911] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1321.931744] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1321.931756] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1324.491818] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1327.051653] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1327.051665] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1329.611734] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1332.171573] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1332.171585] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1334.731657] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1337.291491] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1337.291503] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1339.851618] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1342.411407] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1342.411420] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1344.971545] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1347.531302] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1347.531313] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1350.091415] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1352.651382] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110
[ 1352.651395] brcmfmac: brcmf_cfg80211_get_station: GET STA INFO failed, -110
[ 1355.211335] brcmfmac: brcmf_proto_bcdc_query_dcmd: brcmf_proto_bcdc_msg failed w/status -110

 

 

Share this post


Link to post
Share on other sites
57 minutes ago, Vonor said:

Perhaps it has to do with the Fritzbox I am connecting to (5GHz) ? I'll try using an older android phone as AP to see if that makes a change.

So, makes no difference whether I'm connected to a 5GHz AP or to a 2.4GHz AP.

Share this post


Link to post
Share on other sites
1 hour ago, Vonor said:

Perhaps it has to do with the Fritzbox I am connecting to (5GHz) ?

In the FritzBox you can set two different SSIDs for 2.4GHz and 5GHz. I've done this before to force a smartphone to connect to 5GHz.

 

FritzBox SSID-2GHz4 - SSID-5GHz.png

Share this post


Link to post
Share on other sites
7 hours ago, atula said:

M.2 NV SSD not work with 4.20.13.img

4.4.154 works

Lol, I probably should have tried that one myself. :( I returned a Corsair Force MP510 240 GB NVMe PCIe M.2 SSD this morning that was delivered on Saturday and a Samsung MZ-V7S250BW SSD 970 EVO Plus 250 GB M.2 NVMe SSD that was delivered today didn't work either. I use Debian_stretch_dev_4.20.0 because otherwise it works better than the Radxa images.

Share this post


Link to post
Share on other sites
33 minutes ago, mitag said:

Lol, I probably should have tried that one myself. :(

it's wip... things don't work should be the default expectation...

 

4.4 will have some drawbacks with the rockPI, as far as I know (tested some time ago) the DT needs some fixing cause we lent it out from their kernelfork which seems to be 'slightly' different to the one armbian uses.

Share this post


Link to post
Share on other sites

Something else I noticed when I shut down the system with "sudo shutdown -h now" and forget to unplug the USB C connector, then the system heats up completely. It just happened to me, so I disconnected the plug for 5 seconds and plugged it in again, so that the greeting shows the CPU temperature, 60°C! But I haven't done a test with another kernel version than Debian_stretch_dev_4.20.0 yet, I'm going to sleep now.

Share this post


Link to post
Share on other sites
2 hours ago, mitag said:

then the system heats up completely.

ugh, some power sequence is not correct, or a supply marked "always on" that shouldn't be perhaps.

Share this post


Link to post
Share on other sites

I found two more issues on this board.

 

1: USB Storage. Using the below shown adapter cable to connect a crucial bx500 ssd to the RockPi. Initial connection takes a while. As in dmesg showing that the dis is connected instantly, but showing the partition only after round about half a minute.

 

However, the real problem is, that issuing a reboot causes the neither the disk, nor the adapter cable to be seen. Physically detaching and re-attaching it brings it back. Unplugging the RockPi from the power source also works.

 

// EDIT: This is on the usb3 Ports.

// EDIT2: On the USB2 Ports the disk is available even after reboot.

 

NOTE: On the nanopi m4 the same adapter cable and ssd work without a flaw.

 

dmesg

Spoiler

[Tue Mar 12 21:19:27 2019] usb 8-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[Tue Mar 12 21:19:27 2019] usb 8-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=32.02
[Tue Mar 12 21:19:27 2019] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Tue Mar 12 21:19:27 2019] usb 8-1: Product: JMS579
[Tue Mar 12 21:19:27 2019] usb 8-1: Manufacturer: JMicron
[Tue Mar 12 21:19:27 2019] usb 8-1: SerialNumber: 183351523155
[Tue Mar 12 21:19:27 2019] scsi host0: uas
[Tue Mar 12 21:19:27 2019] scsi 0:0:0:0: Direct-Access     CT120BX5 00SSD1           3202 PQ: 0 ANSI: 6
[Tue Mar 12 21:19:27 2019] usbcore: registered new interface driver uas
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: tag#0 CDB: opcode=0x12 12 01 00 00 40 00
[Tue Mar 12 21:19:58 2019] scsi host0: uas_eh_device_reset_handler start
[Tue Mar 12 21:19:58 2019] usb 8-1: reset SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[Tue Mar 12 21:19:58 2019] scsi host0: uas_eh_device_reset_handler success
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] 4096-byte physical blocks
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] Write Protect is off
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] Disabling FUA
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Tue Mar 12 21:19:58 2019]  sda: sda1
[Tue Mar 12 21:19:58 2019] sd 0:0:0:0: [sda] Attached SCSI disk

 

 

lsusb -vvv

Spoiler

$ lsusb -vvv

Bus 008 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. 
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         9
  idVendor           0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
  idProduct          0x0578 
  bcdDevice           32.02
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          121
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              224mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     98 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
        Command pipe (0x01)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
        MaxStreams             32
        Status pipe (0x02)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15
        MaxStreams             32
        Data-in pipe (0x03)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               7
        MaxStreams             32
        Data-out pipe (0x04)

 

 

2: shutdown -h now

The OS goes down, but the system does not power off. The green LED stays on, the Ethernet LED shows activity and hdmi display looks like i smashed a hammer into the monitor.

Unfortunately I don't have a serial console adapter so I can't debug this issue.

 

// EDIT: I notice the same heat raise @mitag has mentioned. even though I have a PI-Fan connected to the 5V GPIO Pins and attached to the heat sink, which usually keeps the RockPi very cool

Share this post


Link to post
Share on other sites
2 hours ago, Vonor said:

NOTE: On the nanopi m4 the same adapter cable and ssd work without a flaw.

 

2 hours ago, Vonor said:

Unfortunately I don't have a serial console adapter so I can't debug this issue. 

 

there you go:

 

it's called 'The silly approach' :lol:

Share this post


Link to post
Share on other sites

In my eyes an access to the serial console is absolutely necessary, if you don't want it, you should get other toys. SBC are often offered with a recommended USB-UART adapter, for a small extra charge, as an option and I have used this possibility already several times.

2012853004_USB-UARTBridge.thumb.png.2212a98f9b77e1ac14854e34764bdb7c.png
The photo probably doesn't show all USB-UART adapters I own, only those that were handy.

Share this post


Link to post
Share on other sites
10 minutes ago, TonyMac32 said:

I use a USB uart daily

Me too ! So much, that I recently purchased some more to avoid unplugging one from one board to test the other ... I've leave them attached on more than 10 boards ... :lol:

Share this post


Link to post
Share on other sites

Seems like with Armbian 5.77 and kernel 5.0 wifi runs kinda stable.

 

Did the filename for the nvram txt change? See dmesg output below where it failed to load the file with radxa or rockpi-4b in the name. Despite the errors about the backplane wifi seems to run stable this time.

 

Spoiler

$ uname -a
Linux rockpi 5.0.0-rockchip64 #5.77 SMP Sun Mar 17 16:26:24 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux


[Mon Mar 18 22:39:25 2019] rockchip-drm display-subsystem: fb0:  frame buffer device
[Mon Mar 18 22:39:25 2019] brcmfmac: F1 signature read @0x18000000=0x15294345
[Mon Mar 18 22:39:25 2019] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[Mon Mar 18 22:39:25 2019] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[Mon Mar 18 22:39:25 2019] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.radxa,rockpi-4b.txt failed with error -2
[Mon Mar 18 22:39:25 2019] Adding 1048572k swap on /dev/zram1.  Priority:5 extents:1 across:1048572k SSFS
[Mon Mar 18 22:39:25 2019] zram0: detected capacity change from 0 to 52428800
[Mon Mar 18 22:39:25 2019] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
[Mon Mar 18 22:39:25 2019] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9
[Mon Mar 18 22:39:25 2019] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/9 wl0: Jun 16 2017 12:38:26 version 7.45.96.2 (66c4e21@sh-git) (r) FWID 01-1813af84
[Mon Mar 18 22:39:31 2019] RTL8211E Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[Mon Mar 18 22:39:31 2019] rk_gmac-dwmac fe300000.ethernet eth0: No Safety Features support found
[Mon Mar 18 22:39:31 2019] rk_gmac-dwmac fe300000.ethernet eth0: PTP not supported by HW
[Mon Mar 18 22:39:35 2019] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[Mon Mar 18 22:39:35 2019] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[Mon Mar 18 23:04:12 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 00:05:06 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 00:17:42 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 02:28:57 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 04:04:30 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 05:43:12 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 05:43:12 2019] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 237
[Tue Mar 19 05:44:15 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 06:00:00 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 06:00:00 2019] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 234
[Tue Mar 19 06:46:12 2019] brcmfmac: brcmf_sdio_isr: failed backplane access
[Tue Mar 19 07:03:41 2019] dwmmc_rockchip fe310000.dwmmc: Successfully tuned phase to 234
[Tue Mar 19 07:03:50 2019] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

 

 

Share this post


Link to post
Share on other sites
1 hour ago, Vonor said:

Direct firmware load for brcm/brcmfmac43455-sdio.radxa,rockpi-4b.txt failed with error

This is new in 5.0.y and normal, but if file isn't found, it fall back to normal one ...

 

Share this post


Link to post
Share on other sites
On 3/12/2019 at 1:12 AM, mitag said:

Something else I noticed when I shut down the system with "sudo shutdown -h now" and forget to unplug the USB C connector, then the system heats up completely. It just happened to me, so I disconnected the plug for 5 seconds and plugged it in again, so that the greeting shows the CPU temperature, 60°C! But I haven't done a test with another kernel version than Debian_stretch_dev_4.20.0 yet, I'm going to sleep now. 

 

exact same problem on nanopi m4 "next" branch. Need test last armbian version.

Share this post


Link to post
Share on other sites

Maybe it's related but after i execute 

reboot 

command,  via ssh, local or omv - reboot 

 

EDIT: 

I doesn't matter which way I try to reboot or shutdown, it just never goes back up. 

 

I also installed OMV maybe it's related?

 

The board never goes back up. Not even disconnecting from power source, and reconnecting.  only reflashing the img will boot the system back up. 

 

 Using the model 4A model with latest nightly.

 

In addition, 

Using the raxda armbian img it does not occur :(

 

 

 

EDIT 2: 

 

Freezing kernel using armbian-config after first install did the trick. <3 

 

Share this post


Link to post
Share on other sites

I'm also expiriencing @Vonor issue, I considering upgrading. do u think I can unfreeze my kernel and pray that i would boot ? :D

Share this post


Link to post
Share on other sites
On 4/16/2019 at 5:08 PM, mrsufgi said:

I'm also expiriencing @Vonor issue, I considering upgrading. do u think I can unfreeze my kernel and pray that i would boot ? :D

 

Don't, it doesn't work (tried it myself).

 

I also tried all available images (5.79 with 5.0.0 kernel), non of them works. :(

 

 

Share this post


Link to post
Share on other sites
On 4/25/2019 at 8:41 PM, mrsufgi said:

 

Don't, it doesn't work (tried it myself).

 

I also tried all available images (5.79 with 5.0.0 kernel), non of them works. :(

 

 

 

I also have a ROCK Pi 4 -- MODEL A 1GB. Armbian can't boot. No hdmi output.

Share this post


Link to post
Share on other sites

Hmmm, does anyone else have a 1 GB model?

Also can anyone provide any debug info that would aid in determining the cause?

Sent from my Pixel using Tapatalk

Share this post


Link to post
Share on other sites
27 minutes ago, TonyMac32 said:

Hmmm, does anyone else have a 1 GB model?

Also can anyone provide any debug info that would aid in determining the cause?

Sent from my Pixel using Tapatalk
 

 

Here it is:

Spoiler

DDR Version 1.13 20180801
In
Channel 0: LPDDR4,50MHz
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x0
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB
Channel 1: LPDDR4,50MHz
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x0
MR12=0x4D
MR14=0x4D
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB
256B stride
channel 0
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x0
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 1
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x0
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x0
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 1
CS = 0
MR0=0x19
MR4=0x3
MR5=0x6
MR8=0x0
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0xFF
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x10
ch 1 ddrconfig = 0x101, ddrsize = 0x10
pmugrf_os_reg[2] = 0x3241F241, stride = 0x5
OUT
U-Boot SPL board init

U-Boot SPL 2017.09-armbian (Feb 08 2019 - 12:13:00)
booted from SD
Trying to boot from MMC2
NOTICE:  BL31: v1.3(debug):65aa5ce
NOTICE:  BL31: Built : 10:47:37, Jun 19 2018
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1151): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9


U-Boot 2017.09-armbian (Feb 08 2019 - 12:13:00 +0100)

Model: RockPi-4B
DRAM:  1022 MiB
DCDC_REG1@vdd_center: ; enabling
DCDC_REG2@vdd_cpu_l: ; enabling
DCDC_REG3@vcc_ddr: ; enabling (ret: -38)
DCDC_REG4@vcc_1v8: set 1800000 uV; enabling
LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling
LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling
LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling
LDO_REG4@vcc_sd: set 3300000 uV; enabling
LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling
LDO_REG6@vcc_1v5: set 1500000 uV; enabling
LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling
LDO_REG8@vcc_3v0: set 3000000 uV; enabling
SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38)
SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38)
vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38)
dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38)
vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38)
vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38)
vcc-phy-regulator@vcc_phy: ; enabling (ret: -38)
vdd-log@vdd_log: ; enabling (ret: -38)
MMC:   sdhci@fe330000: 0, dwmmc@fe320000: 1
SF: unrecognized JEDEC id bytes: ff, ff, ff
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: RockPi-4B
Net:   eth0: ethernet@fe300000
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc_init: -95, time 19
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2958 bytes read in 23 ms (125 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
102 bytes read in 19 ms (4.9 KiB/s)
7450022 bytes read in 841 ms (8.4 MiB/s)
18667528 bytes read in 2057 ms (8.7 MiB/s)
93774 bytes read in 113 ms (809.6 KiB/s)
** File not found /boot/dtb/rockchip/overlay/rockchip-fixup.scr **
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    7449958 Bytes = 7.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   Loading Ramdisk to 3d7e8000, end 3df02d66 ... OK
   reserving fdt memory region: addr=1f00000 size=7d000
   Loading Device Tree to 000000003d768000, end 000000003d7e7fff ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.174-rockchip64 (root@armbian.com) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11) ) #6 SMP Sun Feb 10 10:43:16 CET 2019
[    0.000000] Boot CPU: AArch64 Processor [410fd034]
[    0.000000] earlycon: Early serial console at MMIO32 0xff1a0000 (options '')
[    0.000000] bootconsole [uart0] enabled
 

 

Share this post


Link to post
Share on other sites
22 hours ago, Fan KunPeng said:

Here it is:

how long did you wait then?

 

unfortunately they're only 4b dev samples around right?

Share this post


Link to post
Share on other sites
9 hours ago, chwe said:

how long did you wait then?

 

unfortunately they're only 4b dev samples around right?

it just stop there. Sometimes it stop earlier.

 

I have tried to replace with radxa's dtb file but failed with kernel panic.

Share this post


Link to post
Share on other sites

Could anyone also enable kernel 5.1 for the RockPi4 dev on the Armbian build script please? 
I would love to test it out with Armbian. I'm very curious how it is.
I've just started building a dev 5.0 for the RockPi4 and saw there's now Disco. Also very curious about that. I love new things to test, and this time it doesn't cost me money :)

Share this post


Link to post
Share on other sites
19 hours ago, NicoD said:

Could anyone also enable kernel 5.1 for the RockPi4 dev on the Armbian build script please? 
I would love to test it out with Armbian. I'm very curious how it is.

Short answer: No (or: yes you can -- > see long answer)

 

Long answer:

what do you expect to change between 5.0 and 5.1? there's not much changed for RK3399 between those two except:

 

New hardware – FriendlyELEC NanoPC-T4 and NanoPi M4, Radxa RockPi 4

 

means this patch needs to be adjusted:

https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-dev/add-board-rockpi4b.patch

 

see which patches else break as well... probably a few others, e.g. every patch modifying the makefile of all the DTS. We don't switch kernels for one board.. we switch it for the whole boardfamily.. which means here rockchip64 with: RockPi, Renegade, Firefly, NanoPis 4 (at least on mainline they share their kernel), Rock64, RockPro64 and maybe a few I forgot..

20 hours ago, NicoD said:

and this time it doesn't cost me money :)

It doesn't cost money, but it costs time... ;)  But you can do it on your own :

  1. clone buildscript
  2. altering those lines to the 'real mainline source' (we use ayufans mainline branch which currently not switched to 5.1) go through his 60 commits on top of mainline to figure out which of those are still needed (and which need to be fixed).. then apply our ~20 patches for this kernel and fix all the regressions you'll get here..
  3. and if you really want to test something new, not only what has enhanced in the same 'drivers' you had in 5.0, you would need to adjust the config file as well to get the new stuff compiled (e.g. if you want to play around with the new scheduler --> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=81a930d3a64a00c5adb2aab28dd1c904045adf57 ).

 

Share this post


Link to post
Share on other sites
46 minutes ago, chwe said:

Short answer: No (or: yes you can -- > see long answer) 

Thank you for your very complete answer. I'm ignorant when it comes to these things.
I saw that "new hardware : RockPi4"
So I thought it was now supported more easily with kernel 5.1. Not as simple as I thought clearly.
I'm planning a video about the NanoPi M4 and RockPi4B in some weeks. So it would have been great. I should have known it wasn't that simple... since it never is :D
I'm learning every day. Thanks

Share this post


Link to post
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...
6 6