amirul Posted October 11, 2019 Posted October 11, 2019 N6 goes up to 1.70 .LITTLE and 2.02 big. with this rk3399-rock-pi-4-2.dtb rk3399-rock-pi-4-2.dts 2
balbes150 Posted October 12, 2019 Author Posted October 12, 2019 I installed the latest version of LE (kernel 4.4 and KODI-19) in eMMC on N6 (WiFi BT works) and can now easily run all test systems from USB media. 11 hours ago, NicoD said: I've tried with next bionic desktop and default bionic desktop. For a proper test run from USB, using an SD card, you need to have two different systems (Armbian and LE). For example, on an Armbian SD card, and on a LE USB drive. If you try to run two identical Armbian systems on both media (it doesn't matter that there will be different versions) it doesn't work correctly. Or you need to manually change the labels of BOOT and ROOTFS partitions on the SD card to others. Or use on SD card LE, and on USB you can record Armbian.
NicoD Posted October 12, 2019 Posted October 12, 2019 13 hours ago, balbes150 said: For a proper test run from USB, using an SD card, you need to have two different systems (Armbian and LE). Tried again with the RockPi4 with LE (kernel 4&5) and armbian next. Doesn't seem to boot from USB. with either Armbian or LE. LE kernel 5 also doesn't work on the RockPi4. Doesn't boot into Kodi. Kernel 4 seems to work fine. Again no Nanopi M4 .dtb there.
amirul Posted October 13, 2019 Posted October 13, 2019 amirul@rk3399:~$ uname -r 5.4.0-rc2-next-20191009-rk3399-tv amirul@rk3399:~$ lsmod |grep ^panfrost panfrost 53248 0 Is panfrost usable?
amirul Posted October 16, 2019 Posted October 16, 2019 Think I'll go back to default. Cannot get wifi to work in next
balbes150 Posted October 19, 2019 Author Posted October 19, 2019 Armbian (5.98_20191018) and Libreelec KODI-19 (kernel 4) 20191018 images update for rk3399 platform with USB startup support. Important change. When testing these images on Magicsee N6 Max (rk3399) and MVR (rk3328) I found an interesting nuance. If you install one of the versions of Armbian or Libreelec in eMMC of these models with support for launching from USB, you can write to a USB flash drive any version of the image for rk3399 or rk3328 and use it on both platforms (on TV boxes with rk3399 and rk3328 at the same time). I. e. the image from rk3399 can be run on rk3328 and Vice versa (you only need to correctly specify the desired DTB in the settings). p.s. On Magicsee N6 Max running from USB works on both USB 2.0 ports (on the left side of the TV box). 1
jeanrhum Posted October 19, 2019 Posted October 19, 2019 4 hours ago, balbes150 said: If you install one of the versions of Armbian or Libreelec in eMMC Just to be sure, we have to use install.sh script to do that?
balbes150 Posted October 19, 2019 Author Posted October 19, 2019 53 minutes ago, jeanrhum said: Just to be sure, we have to use install.sh script to do that? The system update is necessary for those cases when armbian or Libreelec is already used in eMMC. A new installation will update u-boot with USB startup support. For those who saved Android in eMMC and use the main system from SD card, installation in eMMC is not necessary, USB startup will work with SD card (with new images).
Wayne678 Posted October 22, 2019 Posted October 22, 2019 (edited) On 10/11/2019 at 6:03 AM, amirul said: Armbian_5.98_Rk3399-tv_Ubuntu_bionic_next_5.4.0-rc2-next-20191009_desktop runs from sdcard on the N6 - no wifi though I flashed the default img to sd card but it failed to boot up my N6 box with the dtb files you posted. it says that it cannot find ROOTFS. Can you put up a tutorial for howto? Thank for your help! I looked up armbianEnv.txt in which rootdev=UUID=e4f3cef1-6360-464a-a70d-21cfd96b763c rootfstype=BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic rootdev=LABEL=ROOTFS rootfstype=ext4 but in the BOOT (dos) there is no file named /boot/vmlinuz-5.0.0-32-generic. Edited October 22, 2019 by Wayne678
amirul Posted October 23, 2019 Posted October 23, 2019 6 hours ago, Wayne678 said: I flashed the default img to sd card but it failed to boot up my N6 box with the dtb files you posted. it says that it cannot find ROOTFS. Can you put up a tutorial for howto? Thank for your help! Did you edit /boot/extlinux/extlinux.conf to FDT /dtb/rockchip/rk3399-rock-pi-4-2.dtb
Wayne678 Posted October 23, 2019 Posted October 23, 2019 I used N6 dtb, rk3399-magicsee-n6-max.dtb, which works! Thanks so much! If you put up a tutorial, there will be more members to follow. Next question: where we can modify the rootfs info such as partition ext2, ext3, ext4 etc?
balbes150 Posted October 23, 2019 Author Posted October 23, 2019 6 hours ago, amirul said: FDT /dtb/rockchip/rk3399-rock-pi-4-2.dtb ???
balbes150 Posted October 23, 2019 Author Posted October 23, 2019 58 minutes ago, amirul said: my little mod It is advisable definitely to mention. Users often make a direct copy\paste and do not think where it originates (as part of the regular image of these files are not).
amirul Posted October 23, 2019 Posted October 23, 2019 8 hours ago, Wayne678 said: I used N6 dtb, rk3399-magicsee-n6-max.dtb, which works! Thanks so much! If you put up a tutorial, there will be more members to follow. It wouldn't be much of a tutorial. 1. Burn img to sd card 2. Edit /boot/extlinux/extlinux.conf to point to the correct dtb (rk3399-magicsee-n6-max.dtb for default, rk3399-rock-pi-4.dtb for next) 3. Boot
balbes150 Posted October 25, 2019 Author Posted October 25, 2019 New image 20191025 NEXT (kernel 5.4.0-rc4)
Wayne678 Posted October 26, 2019 Posted October 26, 2019 11 hours ago, balbes150 said: New image 20191025 NEXT (kernel 5.4.0-rc4) Thanks for your work!!! I would like to give feedback FYI. I pent few days to play with the images on N6: 1. WIFI is not shown; 2. Web browsers Firefox /Chromium do not connect to internet for "security" issue; 3. The system, even terminal, respond very very slow. It supposed to be very fast, faster than S912 which I tried your img. S912 img are very fast.
Lexx Posted November 5, 2019 Posted November 5, 2019 Hello! TV-BOX magiksee n6max with Armbian_5.98_Rk3399-tv_Ubuntu_disco_default_4.4.154_desktop_20191022.img. The problem is as follows. Usb type c port does not work. Moreover, when the android boots, the disks connected to it begin to be detected. Question. Can someone fix usb in armbian system or teach how to do it?
Lexx Posted November 8, 2019 Posted November 8, 2019 Found such lines after dmesg | grep usb 1.900520] phy phy-ff770000.syscon:usb2-phy@e450.0: Looking up phy-supply from device tree [ 1.900620] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e450.0 err -2 [ 1.900946] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up phy-supply from device tree [ 1.900958] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed [ 1.901187] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up vbus-supply from device tree [ 1.901197] phy phy-ff770000.syscon:usb2-phy@e450.1: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e450/otg-port failed [ 1.901210] phy phy-ff770000.syscon:usb2-phy@e450.1: Failed to get VBUS supply regulator [ 1.901974] phy phy-ff770000.syscon:usb2-phy@e460.2: Looking up phy-supply from device tree [ 1.902027] vcc5v0_host: could not add device link phy-ff770000.syscon:usb2-phy@e460.2 err -2 [ 1.902307] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up phy-supply from device tree [ 1.902317] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up phy-supply property in node /syscon@ff770000/usb2-phy@e460/otg-port failed [ 1.902534] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up vbus-supply from device tree [ 1.902545] phy phy-ff770000.syscon:usb2-phy@e460.3: Looking up vbus-supply property in node /syscon@ff770000/usb2-phy@e460/otg-port failed [ 1.902557] phy phy-ff770000.syscon:usb2-phy@e460.3: Failed to get VBUS supply regulator [ 1.904311] phy phy-ff7c0000.phy.6: Looking up phy-supply property in node /phy@ff7c0000/usb3-port failed [ 1.904776] phy phy-ff800000.phy.8: Looking up phy-supply property in node /phy@ff800000/usb3-port failed It is clear that the device is not configurable. No one will tell you how to defeat this?
Lexx Posted November 9, 2019 Posted November 9, 2019 rockchip-dwc3 usb0: fail to get drvdata hcd [ 4.446338] phy phy-ff770000.syscon:usb2-phy@e450.1: charger = USB_FLOATING_CHARGER [ 4.452244] rockchip-dwc3 usb1: fail to get drvdata hcd And what kind of driver he cannot get?
balbes150 Posted November 14, 2019 Author Posted November 14, 2019 New version: 5.99. Please note, this version NEXT is the primary preparation for the transition to the release of a single image for the platform Rockchip + Amlogic + Allwinner. The new image after writing to external media and after configuring the used dtb (and if necessary adding the desired u-boot option to run from the SD card on the RK) can be used simultaneously on AML (s9xxx) and RK (rk3399 and rk3328). If the TV boxes RK (rk3328 and rk3399) in eMMC installed a new version of u-boot with support for starting the system with USB, adding u-boot to SD card is not required, the system will automatically start on rk33xx with USB. The "default" version is only suitable for RK33xx (rk3399 and rk3328). Important. These images do not yet have new scripts to install the system in eMMC for AML and rk3328. Therefore, do not use these images to install in eMMC on AML models and on RK3328.
amirul Posted November 14, 2019 Posted November 14, 2019 2 hours ago, balbes150 said: New version: 5.99. Please note, this version NEXT is the primary preparation for the transition to the release of a single image for the platform Rockchip + Amlogic + Allwinner. The new image after writing to external media and after configuring the used dtb (and if necessary adding the desired u-boot option to run from the SD card on the RK) can be used simultaneously on AML (s9xxx) and RK (rk3399 and rk3328). If the TV boxes RK (rk3328 and rk3399) in eMMC installed a new version of u-boot with support for starting the system with USB, adding u-boot to SD card is not required, the system will automatically start on rk33xx with USB. The "default" version is only suitable for RK33xx (rk3399 and rk3328). Important. These images do not yet have new scripts to install the system in eMMC for AML and rk3328. Therefore, do not use these images to install in eMMC on AML models and on RK3328. 5.99 NEXT boots off USB on my S905 box, but as with all 5.4 kernels, no hdmi sound
balbes150 Posted November 15, 2019 Author Posted November 15, 2019 14 hours ago, amirul said: 5.99 NEXT boots off USB on my S905 box, but as with all 5.4 kernels, no hdmi sound Use the DEV version, it has an extended hardware list and additional patches.
amirul Posted November 16, 2019 Posted November 16, 2019 On 11/15/2019 at 7:05 AM, balbes150 said: Use the DEV version, it has an extended hardware list and additional patches. 20191114 DEV does not have hdmi sound either
balbes150 Posted November 16, 2019 Author Posted November 16, 2019 26 minutes ago, amirul said: DEV does not have hdmi sound either s9xxx - sound work rkxx - sound not work
amirul Posted November 16, 2019 Posted November 16, 2019 49 minutes ago, balbes150 said: s9xxx - sound work rkxx - sound not work for me s905 using gxbb_p201 - no sound
Lexx Posted November 18, 2019 Posted November 18, 2019 usb 3.1 type c does not work on magicsee -n6-max. Not a single version of armbian
balbes150 Posted November 23, 2019 Author Posted November 23, 2019 Update Armbian images 5.99_20191121 to rk3399. DEFAULT - kernel 4. Please note, in the future I plan to completely switch to using kernel 5 for all images. The kernel 4 version will no longer be released. 1
balbes150 Posted November 23, 2019 Author Posted November 23, 2019 On 11/5/2019 at 8:24 AM, Lexx said: Question. Can someone fix usb in armbian system or teach how to do it? Verify that the settings in the DTB and to build your working version. The forum discussed many times how to work with the DTC utility.
amirul Posted November 23, 2019 Posted November 23, 2019 1 hour ago, balbes150 said: Update Armbian images 5.99_20191121 to rk3399. DEFAULT - kernel 4. Please note, in the future I plan to completely switch to using kernel 5 for all images. The kernel 4 version will no longer be released. I'm sticking with kernel 4 for now. Everything works, even wifi (with a bit of a hack)
Recommended Posts