Try a usb stick. Burn the image to usb and try again. If it doesn't work in first usb port try the other. I have the same problem, seems it doesn't work from SD on some boxes.
Posts by roel
-
-
I tested streaming on H5 version and it worked fine at that time, but it used HLS protocol. It could be protocol related. Note that Tritium boards only have 100 Mbps ethernet via internal PHY - I already had compatibility issues with that.
I will investigate further with other streaming sites and from my server. Probably it's only related to the mpeg-dash streams.
SMB1 is not supported anymore and afaik you must use username/password with SMB2/3
I know, it's because on my khadas vim1 and firefly M1 I have to login also with username and pasword and there it works. On the tritium not I get the response "check your credentials" while I'm sure username and password are correct. But as I said, maybe I didn't try enough. SSH works though.
-
Regarding Tritium H3,
I tried a few things yesterday, installs fine, my needed add-ons work, although the streaming buffers a lot. I don't know if it's related to the Tritium H3 or the mpeg-dash stream. We always had problems with these streams, but no freezing or repeatedly buffering. When I switched back to my khadas vim1 running leia everything was OK'isch using the same add-on.
Couldn't log in with samba, but maybe i didn't try enough. Before shutting down the device I checked the LE settings and there seems to be a choice now to login with or without pasword. but I didn't try it anymore. I know it nevers gone happen but a nfs server is way more trouble free.
-
I will see if i can try this evening on my station M1.
-
Anyone can test the Netflix addon on these images?
repository.castagnait-1.0.0.zip
It's already on 1.0.1 maybe that's the problem -> GitHub - CastagnaIT/repository.castagnait: CastagnaIT Kodi addons repository
Or just install 1.14.1 directly -> Releases · CastagnaIT/plugin.video.netflix · GitHub
-
Display More
@all
There are few boards that we are not able to test, so I would like to get status of following boards (playback including deinterlacing, network, USB, suspend/resume, ...):
Libre Computer ALL-H3-CC (H3 version)
Nano Pi M1 (H3)
Orange Pi 2
Orange Pi PC
Orange Pi PC 2
Orange Pi Plus
Pine64 LTS
Additionally, can someone confirm that WIFI and Bluetooth don't work on PineH64 model B (my board may be broken in this regard).
I can test tritium H3.
Wifi on my pineH64 doesn't seem to work also.
-
I didn't look into the reason why it almost always fail on AW boards.
It's not AW only, Amlogic has also the network timeout issue.
-
In any case shutting down as well as restarting kodi is very slow
The very slow shutting down feature is also available on the rockchip and amlogic devices not exclusively for H3
-
About KVIM1
I tested the latest nightlies on my KVIM1. I just dd the KVIM-image to emmc, I only read later it should be done with the emmctool, but it boots fine. Now when I test some local streaming services (VRT-NU and VTM GO) the screen is shaking a lot, including the control panels and the video hangs.
Local video's start but without screen. When I stop them the system freezes.
Here is thelog: http://ix.io/2NDN but it seems it stopped logging at some point.
Another problem, but already known probably, is that it takes ages to shut down the system (I have this also on my RK3328).
-
The name of the images contains rk3328-roc-pcStupid of me, I should have seen that
-
For M1, I release special images LE (arm and aarch64)
Yes, I read that in the forum of firefly, but You didn't put the link to the LE images, only to the Armbian image. So can you provide the link to the LE images?
-
it's a Station M1. I test it, it works OK, I had to use the dtb from the firefly ROC-RK3328-PC as the Station M1 is in fact a ROC-RK3328-PC with a shell.
I will test this evening a 32-bit image as widevine is not available for 64-bit. I will see how it works out.
-
Sorry, I made a typo, the M1 is indeed a RK3328. Nevermind, I will take a rk3328 image, burn it to SD and then burn the M1 u-boot to the sd-card. I will see what it does.
-
I read your explanation about the Station M1 on the firefly forum. There you speak about linux mainline builds for the M1. So if I understand correctly, I just have to use one of your rk3228 testbuilds and burn the u-boot from the firefly forum to the sd-card?
-
As I understand, DT-overlays should be used to add are change properties in the device tree. So, if I understand this correctly, it shiould activate properties from add-on boards, for example a DAC or Wifi board as available for pine64. So in this case, it should be good to add support for the wifi board and also the audio pot board on the pine64 boards .
-
I have time
I'm glad some people still have the motivation to put some new life in older hardware.
-
If I could help I would, but I don't understand a thing about making device trees. I once started reading the documentation, but I have zero background, so it's all chinese to me.
If I find another wetek core, I will contact you regarding Martin's adress.
-
Just test it on my M8S. Boots fine with the mxIII-plus dtb, but not with the M8S dtb.
Could test further as it seems I got a overload on the usb ports and now the usb doesn't work anymore. I hope there is some kind of overcurrent protection on this box, so when it's cooled down, it works again.
Regarding the wetek core. It seems there is no dtb for the wetek core in mainline.
Edit: My usb-ports don't work anymore...
