Posts by mglae

Quote from ajiratech

Where can I see logs for the attempt to run autostart.sh ?

For the record:

journalctl -u kodi-autostart

IMO the FritzBox only supports SMB1 protocol. Try adding ,vers=1.0 to your Options= line.

Yes, set it on every suspend:

Quote from mglae

A sleep/resume script (see /storage/.config/sleep.d/99-sample.power.x) is a good place to set the resume time.

Quote from sk4hrr

Disabling the A6 GPU does not change anything: 1537209101.jpg

But, your tips works, but with this command:

Code

mount -t vfat -o rw,remount /dev/sda1 /flash

Thanks, fixed my post.

Quote

Should I do that every time I update?

No, an update does not change syslinux.cfg.

Without kernel radeon driver ~/.config/udev.rules.d/97-xorg.rules is not needed any more, delete it.

Now amdgpu driver is loaded and your monitor is detected. But the radeon driver is loaded too and xorg does crash.

Two Ideas:

- Disable the onboard graphics of the A6-6400K in BIOS configuration if possible.

- Disable the radeon kernel driver:

mount -o remount,rw /flash
nano /flash/syslinux.cfg

Add initcall_blacklist=radeon_init to the APPEND line, save and reboot.

You can use setwakeup.sh to set a resume time.

setwakeup.sh $(date +%s -d 23:59)

i.e. set a wake time of today 23:59. Other times need some more today/tomorrow time calculations.

A sleep/resume script (see /storage/.config/sleep.d/99-sample.power.x) is a good place to set the resume time.

The kernel of 8.2.5 is to old for RX550 support.

On 8.90.004 the kernel activates the radeon driver for HD 8470D and the amdgpu driver for the RX550. The system detects the radeon driver first and configures xorg for it.

Try:

sed '/DRIVER=="radeon"/d' </lib/udev/rules.d/97-xorg.rules >~/.config/udev.rules.d/97-xorg.rules

to remove radeon detection and reboot.

Maybe the system is confuse by having both the RX 550 and the Radeon HD 8470D of the A6-6400K CPU.

To get more information you can remove the RX 550 card. Configure network and sshd in the recent Milhouse build and test the ssh access over network.

Insert the RX 550 again. After boot network access should be still possible. Please post the results of:

dmesg|paste
journalctl|paste
paste /var/log/Xorg.0.log

tv_grab_file cannot parse your settings file.

1. For completeness: which platform, LE and Tvheadend addon version do you use?
2. There is an updated tv_grab_file in LE master, you can download and try https://github.com/libreelec/libreelec.tv/raw/master/packages/addons/service/tvheadend42/source/bin/tv_grab_file . In worst case it does not work either.

Quote from polo_joe

As you can see webgrab+ creates guide.xml, but tvh epg grab /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_file gives no output. Even if I start /storage/.kodi/addons/service.tvheadend42/bin/tv_grab_file with ssh I get no output.

If tv_grab is a shell script you can use

sh -x /storage/.kodi/addons/service.tvheadend42/bin/tv_grab

to see what is going wrong.

Is there anything visible in the log?

journalctl -u kodi-autostart

Quote from osen

Sorry, I'm a bit of a linux noob. What does this accomplish exactly? What should I change in the line? Just remove the r in -nr?

Yes, only remove the 'r'. Be careful, you loose networking if there is anything wrong with this file.

Quote from osen

Does this mean it sets Google DNS as default? Because I don't want that.

Google DNS is the default until any other name server is defined manually or via DHCP.

connmand is started with the option -r disabling the DNS proxy.

Copy the /usr/lib/systemd/system/connman.service file to /storage/.config/system.d/, change the ExecStart=... line and reboot.

Otter

The GPU of the A10-7860K may have some influence.

Please post the URLs of dmesg|paste and paste </var/log/Xorg.0.log

Regarding AMD: Kodi 17 only supports VDPAU acceleration for the AMD platform.

For using VAAPI (playing i.e. 4k HEVC 10bit videos) Kodi 18 is needed,

Does this still work?

Which platform? At least on Generic CONFIG_EFI_STUB is already enabled.

Quote from chorca

I'm really curious about this: How did you come up with this modeline?

Was a result of a web search and is in reality a 59,94Hz mode.

Quote from chorca

Every calculator i've tried says somewhere between 700 and 1000Mhz for the pixel clock, is there something wrong with using these to calculate digital resolutions?

Maybe these calculators still respects CRTs while today’s digital flat panel displays do accept short horizontal and vertical blanking times.