Have anyone noticed that some rare types of videos are playing in only Red Colour Tone?
Status of NanoPC-T4 (RK3399)
-
Aciel -
January 3, 2019 at 3:58 PM -
Thread is Unresolved
-
-
When you use Recalbox dtb on NanoPC-T4, is your ethernet working with the latest dtb from 3 June?
I'm having caching issue on WiFi, so I thought I'll switch to ethernet. I plugged in my cable and disabled WiFi, but I got no Internet access and Kodi had no ethernet settings under LibreELEC Settings.
I dropped in ssh and ran "ifconfig". There were only two interfaces wlan0 & lo, no eth0.
-
When you use Recalbox dtb on NanoPC-T4, is your ethernet working with the latest dtb from 3 June?
I'm having caching issue on WiFi, so I thought I'll switch to ethernet. I plugged in my cable and disabled WiFi, but I got no Internet access and Kodi had no ethernet settings under LibreELEC Settings.
I dropped in ssh and ran "ifconfig". There were only two interfaces wlan0 & lo, no eth0.
I can't reproduce the problem because I don't have a LAN on my NanoPC-T4 at the moment,
but I will reproduce it in the next days and let you know.
-
Hi Aciel,
I can't recreate your problem.
I use the following configuration:
Code############################################## # LibreELEC # # https://libreelec.tv # ############################################## LibreELEC (community): devel-20190606140016-a41fdf1 (RK3399.aarch64)
I have this LE Image from @balbes150:
With the extracted DTB from this Recalbox Version.
All interfaces (also eth0) will be displayed:
Code
Display Morehades:~ # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP8000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether XX:XX:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP8000> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether YY:YY:YY:YY:YY:YY brd ff:ff:ff:ff:ff:ff inet 10.aa.bb.11/24 brd 10.aa.bb.255 scope global wlan0 valid_lft forever preferred_lft forever hades:~ # ifconfig eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:680 (680.0 B) Interrupt:24 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:4170 errors:0 dropped:0 overruns:0 frame:0 TX packets:4170 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:228606 (223.2 KiB) TX bytes:228606 (223.2 KiB) wlan0 Link encap:Ethernet HWaddr YY:YY:YY:YY:YY:YY inet addr:10.aa.bb.11 Bcast:10.aa.bb.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11686 errors:0 dropped:2323 overruns:0 frame:0 TX packets:4835 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11119802 (10.6 MiB) TX bytes:462892 (452.0 KiB) hades:~ #
I'm sorry I can't help you with that.
Greetings and good luck.
-
Hello back @JerryPenguin
Thank you for checking it on your device.
I have 1 thing in mind which might have caused no ethernet device, which is when I do Kodi build updates from within Kodi by downloading and place the .gz file in the update folder could have altered the Recalbox's dtb. I'll replace the dtb again and give it a test.
Otherwise the ethernet is working if I boot into Android from eMMC.
-
Hi Aciel,
yes, you're right, the image files *.gz also contain DTBs and are exchanged.
After that I always had the problem that I didn't have the EEMC entries (from balbes150) in the LE settings anymore and neither Bluethooth nor WLan works.
Since balbes150 no longer created AARCH64 images, I also decided not to update. So I'm waiting for the change to the 5 kernel, where our NanoPC-T4 is directly supported.
Since my configuration (except for the not always occurring problem with the aborts when watching TV in SD and HD) my LE installation runs stable.
I only use LE to watch TV and movies over the EMBY plugin, because I have my own EMBY server with TVHeadend running on a QNAP for years.
That runs sufficiently stable in this combination for me.
I was already thinking about getting an ODROID N2, but I want to wait until I connect a new 4K TV to the LE (old TV causes its problems there) and hope that there will be stable images for the ODROIS N2 until then.
Greetings
-
Hello once again @JerryPenguin
Yes, indeed it was the *.gz updating which caused alterations to dtb. Now I have to replace dtb every time I do the LE Update.
Ethernet is now working smoothly.
-
Hello once again @JerryPenguin
Yes, indeed it was the *.gz updating which caused alterations to dtb. Now I have to replace dtb every time I do the LE Update.
Ethernet is now working smoothly.
I am curious ...
Which LE image do you currently use on your NanoPC-T4?
-
I am curious ...
Which LE image do you currently use on your NanoPC-T4?
Rock960 image from Index of /, because I watch a lot of 10bit x2664/HEVC (mostly Anime) haha.
-
Rock960 image from Index of /, because I watch a lot of 10bit x2664/HEVC (mostly Anime) haha.
Thanks for your information
Do Wifi and Bluetooth work under the Rock960 images?
How do you get the image on the internal EMMC memory?
-
Thanks for your information
Do Wifi and Bluetooth work under the Rock960 images?
How do you get the image on the internal EMMC memory?
Yes, WiFi & Bluetooth both work flawlessly, using the above dtb.
About eMMC, there is no support for it in Official images by LE. Internal Storage is not recognisable at all.
Images by bybalbes150 do have eMMC support and you can install to it through LE Settings Menu.
-
Yes, WiFi & Bluetooth both work flawlessly, using the above dtb.
About eMMC, there is no support for it in Official images by LE. Internal Storage is not recognisable at all.
Images by bybalbes150 do have eMMC support and you can install to it through LE Settings Menu.
Thanks for the info...
Because of the missing EMMC support I stay balbes150 Imgages ... even if no suitable AArch64 images are created at the moment.
In combination with the DTB of RecalBox everything works fine, even if with an older image.
Greetings
-
Hi!!!
I'm trying to add 6 SATA HDD's to the NANOPC-T4.
Does anyone know how to add SATA support to the kernel? and lvm? balbes150 ?
I've bought https://www.amazon.es/dp/b07rmhh43w/?coliid=i167rpmxeer96f&colid=3uw4ac29w4bys&psc=1
And works fine with armbian and ubuntu distros....
-
Any news on the 4K resolution issues?
-
- Official Post
1. You can specify the name of the DTB file are you using from the image Recalbox ?
2. You can perform a simple test of image is running Armbian
https://yadi.sk/d/tpeis4lvlmgtvq
(I'm interested in two things, will it work booting u-boot on a T4 and what DTB from the image Armbian will have better hardware support T4) ?
-
Hello balbes150,
I use your current image from https://yadi.sk/d/qgyvmkow5oqcha/2019090 with the DTB file for the NanoPC-T4 from Releases · recalbox/recalbox-os · GitHub Version 4.1.0.
It works fine for me, but I don't watch 4k movies and therefore can't rate 4K support.
Bluetooth, WiFi and EMMC (including your installation and backup/restore scripts) works fine.
Greetings
-
1. You can specify the name of the DTB file are you using from the image Recalbox ?
2. You can perform a simple test of image is running Armbian
https://yadi.sk/d/tpeis4lvlmgtvq
(I'm interested in two things, will it work booting u-boot on a T4 and what DTB from the image Armbian will have better hardware support T4) ?
Hello balbes150,
I just tested your Buster image from https://yadi.sk/d/qgyvmkow5oqcha/2019090 with the DTB file for the NanoPC-T4 from Releases · recalbox/recalbox-os · GitHub Version 4.1.0.
My NanoPC-T4 boots into a text console.
Without a valid login I can't get any further here.
Greetings
-
- Official Post
Hi
What is exactly the file you are using (copying) from the image Recalbox ? I need the full name of the DTB file used. If running Armbian happens, you can try to perform the initial configuration. If you took a desktop image, you need to log in to the console as "root" with the password 1234, change the password, create a new user, set the password and see if the graphical desktop shell will start.
-