Posts by talkenig

Joining that thanks!

Just updated to 8.2.1, everything seems to work except of the smb configuration - but I saw this is a known issue with a fix.

Many thanks vpeter!

I agree it sounds like a router issue.

If I were you I would do the following:

1. Check the NAT settings on the router.
2. Factory reset the router and then reconfigure it.
3. Try a different router with the same modem.

Thanks for trying to help. Maybe one day there will be an LE version with a newer kernel working on the i4x4.

Conversely, is there a reliable resource where I can see a list of dvb-t adapters and their compatibility with kernel versions?

Well, I found this table.

Seems that only the PCTV Systems nanoStick T2 290e would work with this kernel.

Thanks again for the effort. I will keep looking for any distro that can run on my i4x4 with newer kernel.

I also tried the OE 8.0.4 for imx6. Interestingly, it boots fine (kernel 4.8). However, it recognizes only 2GB RAM, Samba seemed not to work and tvheadend is not supported... So this is not really a plausible option.

Hi Peter.

I plugged in the device, then I ssh'd and this is what I got:

LibreELEC (community/vpeter) Version: 8.0.2
LibreELEC:~ # dmesg | pastebinit
http://sprunge.us/bLLC
LibreELEC:~ # lsusb -v | pastebinit
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
http://sprunge.us/TcWd

The device is not recognized by the system - no devices showing on the tvheadend.

I wrote this post on the DVB-T support forum.

Not sure what it is, since people report this exact device to work on LE 8.0.2 out of the box.

It might be that the best option is to get another DVB-T2 stick.

Thanks for all the help.

OK. Tried it - got the blank screen issue again.

This time the the screen is blinking between shades of black + a no signal message every few seconds.

Interesting how every kernel version makes the blank screen a bit different.

I wonder what it is.

Will keep the 3.14 kernel version in the meanwhile.

Thanks for your time.

OK. Thanks. Will try it.

In the meanwhile I tried the latest Xbian image for imx6.

After the initial splash, I got a blank screen again and the Cubox led went off.

No luck there also...

OK. So here are the results:

• LibreELEC-imx6.arm-8.0.2-4.10-xbian.img.gz: Did not even boot to the LibreELEC splash. I got the following:

### Error in mount flash: mount_common: could not mount /dev/mmcblk0p1 ###
### Starting debugging shell... type exit to quit ###
sh: can't access tty; job control turned off

• LibreELEC-imx6.arm-8.0.2-4.8-xbian.img.gz : Got the black screen issue
• imx6-xbian-kernel-4.4/LibreELEC-imx6.arm-8.0.1.img.gz : Blank screen and "No signal" flashes every few seconds.

Overall, no luck...

I have the Cubox-i4x4 - hope this at least helps someone...

OK. I have a spare SD card and I am trying now. Will update on the results.

Thanks again.

Have the same problem. Your image with the older kernel resolved my problem. Thanks for that Peter.

However, I would like to run a newer kernel to support my DVB-T2 dongle (I think this is the problem).

Do you have an idea whether your Xbian images under Index of /imx6-xbian-kernel-4.10/ work on the i4x4?

Thanks,

Tom.

Hi all.

I am running Cubox-i4x4 with LE 8.0.2. The regular imx6 image does not run on my device (why?), so I am running vpeter's image: LibreELEC-imx6.arm-8.0.2-3.14-sr.img.gz .

I installed tvheadend 4.2 and the device is simply not recognized. I intentionally got the T230 and NOT T230c, since I read it should work out of the box.

I saw around the web some people having similar problems, and the suggested solution was to get 3 firmware files. My system already has those files in /lib/firmware and I tried to shadow them by placing (newer ?) versions in /storage/.config/firmware.

Nothing helps. My guess is that the reason for this is that my image uses kernel 3.14 instead of the 4.4 of the official version.

Any ideas anyone? Should I try Xbian perhaps?

Thanks,

Tom.