Posts by twinpeaksr

Quote from mglae

Generic is using X11. Try xrandr instead.

Thanks, that worked, will see if I get a change during power cycle and try out the EDID fix.

I tried several changes in the Bios based on some other threads/forums, did not give positive results.

I think you found my issue, though not what was expected.

Modetest returns no devices. I suspect that is what is causing the issue, though it does not answer why HDMI works, it would answer why it does not maintain sync after power cycle.

trying to open device 'i915'...failed
trying to open device 'amdgpu'...failed
trying to open device 'radeon'...failed
trying to open device 'nouveau'...failed
trying to open device 'vmwgfx'...failed
trying to open device 'omapdrm'...failed
trying to open device 'exynos'...failed
trying to open device 'tilcdc'...failed
trying to open device 'msm'...failed
trying to open device 'sti'...failed
trying to open device 'tegra'...failed
trying to open device 'imx-drm'...failed
trying to open device 'rockchip'...failed
trying to open device 'atmel-hlcdc'...failed
trying to open device 'fsl-dcu-drm'...failed
trying to open device 'vc4'...failed
trying to open device 'virtio_gpu'...failed
trying to open device 'mediatek'...failed
trying to open device 'meson'...failed
trying to open device 'pl111'...failed
trying to open device 'stm'...failed
trying to open device 'sun4i-drm'...failed
trying to open device 'armada-drm'...failed
trying to open device 'komeda'...failed
trying to open device 'imx-dcss'...failed
trying to open device 'mxsfb-drm'...failed
no device found

Now to find out why the HDMI is not recognized

Anyone have any idea on this? Is this an HDCP issue as the HDMI link is reestablished when the Preamp is turned on? Any recommended means to test this?

Quote from Da Flex

Are you sure you've been stored your GUI setting correctly?

1. go to Settings -> LibreELEC -> Connections -> Wired -> Edit -> Connection -> Connect Automatically
2. switch this setting on
3. move to the right on your remote to focus on the "Save" button
4. press "OK" on your remote

This is exactly what I did, many, many times to make sure.

Always good to double check.

Thanks.

I found a way to fix it, but it does not answer why it cannot be fixed in the gui.

I found a settings file in connman:

Tyr:~/.cache/connman/ethernet_e45f0101f147_cable # cat settings
[ethernet_e45f0101f147_cable]
Name=Wired
AutoConnect=false
Modified=2021-02-02T09:40:36Z
IPv4.method=manual
IPv4.netmask_prefixlen=24
IPv4.local_address=192.168.0.71
IPv4.gateway=192.168.0.2
IPv6.method=off
IPv6.privacy=disabled
Nameservers=192.168.0.24;192.168.0.2;
Timeservers=0.pool.ntp.org;1.pool.ntp.org;2.pool.ntp.org;

it shows what I saw in the gui, AutoConnect=false. Changing that to AutoConnect=true and rebooting caused the network to connect with no issues and both the external DB and media is working as expected.

I did notice the permissions are restrictive on the file, but that should not cause this issue. Is there something specific to my system that caused this or is this an error in the code?

Tyr:~/.cache/connman/ethernet_e45f0101f147_cable # ls -ahl
total 3K
drwx------    2 root     root        1.0K Feb  2 09:40 .
drwxr-xr-x    3 root     root        1.0K Feb  2 09:32 ..
-rw-------    1 root     root         325 Feb  2 09:40 settings

Thanks!

I removed the advancedsettings file and used a local DB, however the problem remains.

I believe the connection the the DB error is caused by the wired connection being unable to start automatically.

Looking through the log this line stands out:

2021-02-02 09:30:02.887 T:1093  WARNING <general>: JSONRPC: Could not parse type "Setting.Details.SettingList"

Is is possible that this or another settings file that contains the "Connect automatically" setting is not writable and hence wired network remains manual connect only? Is there details on where that setting is located in the settings files?

thanks!

Log: http://ix.io/3uJD

No difference with Wi-Fi enabled or disabled. When connected manually works without issue. This is not a hardware defect.

Thanks!

No difference. This is a static IP so I would not expect a delay from the DHCP.

Also have several RPi3 that connect without issue using a 5sec delay.

The part that bothers me is the "Connect Automatically" option will not stay enabled pointing me at a setting somewhere that is not allowing that to remain enabled.

Thanks!

Yes, it is enabled, was set to 10sec, but moved to 30sec, same issue remains. I can tell that it is waiting, change from 10 to 30 added 20sec to boot.

I have had an issue that has been persistent for several years and I have been unable to understand the cause or find a solution.

Issue:

Whenever I turn on the Preamp/Amp/Projector, the pass-through audio is distorted. If I reboot the HTPC, the audio is restored and works flawlessly, unless I power on/off the rest of the system.

• distortion noticeable on default kodi navigation sound, audio freq shifts up and crackle distortion
• distortion present if trying to play media
• Reboot system after Preamp/Amp/Projector are power up and audio is corrected
• Logs: http://ix.io/3uA0

HTPC:

• Intel I3-7100
• Gigabyte GA-H270M-DS3H Motherboard
• 16GB DDR
• Silverstone ST455F Power Supply
• ADATA Premier 600 64GB SSD
• Clean install of LE10 RC5 Build currently loaded (Same issue with last 5 versions of LE9)
• All format for audio set to pass-through
• No audio plugins added beyond base install with LE image

System:

• HDMI from HTPC to Anthem AVM60
• 1000BaseT Ethernet from HTPC to Cisco SG200-18 Switch
• All Media on Server Connected to Cisco Switch (Proxmox Server, NFS Share)
• DB on Server Connected to Cisco Switch (MariaDB CT on Proxmox Server)

I believe there is something going on with the ALSA setup but despite several attempts over the years I have not been able to correct this. My hope was it would be corrected with Kodi 19 (LE10) but right now I am not seeing any change. Any guidance would be appreciated.

Thanks!

I have a stock RPi4 with latest RC1 (Also saw issue on Beta 5) and I cannot get Wired to connect automatically.

If I select the connection and "connect" it connects and works fine.

If I edit the connection, enable "Connect Automatically" and save, I go to check the setting and it is disabled again.

Am I missing something? This is a new RPi4 and has only had RC1 and Beta5 installed, both with same issue.

Thanks!

Had the same issue, found the solution:

Remove the following lines from the *.mount files.

Requires=network-online.service
After=network-online.service

I believe that the service is waiting until network-online.service loads, but since it is never used, it never loads the mount. This allowed my NFS shares to work correctly.