Posts by heitbaum

Now a lsusb -v please

Sorry. But I can’t follow what has been shared.

Just juggling builds.

Can you please share the boot dmesg and lsusb -t without any usbs plugged in?

Is there any error?

Then plug in the USB devices one at a time to identify which one is causing the error.

Once we identify the faulty device then we can look in to the lsusb -v data

So looking at this - please run -

lsusb -t

It looks like the composite device has come online, where it did not during the boot process.

So when testing tomorrow. Try with no USB connected, that should isolate the error down.

I don’t think the “device connected” is coming online.

If Disconnecting all USB, does the error occur?

When connecting the haobo you get the 1-7 and 1-8 messages?

The device descriptor read/64, error -110 means a conn3ction establishment error, sometimes that a that USB port power supply was exceeded. Can you please disconnect all USB devices and reboot, and then add them back one by one to identify the failing device.

I can see the keyboard as 1-7.

Also please share the lsusb from the system.

2C:CF:67:2C:88:8D is the onboard (wlan0)

70:15:FB:10:B1:1B is the intel (wlan1)

Quote from emveepee

Service.nextpvr installs ffmpeg-tools and I tried to find ffmpegx and couldn't. I installed TVH too but couldn't find it in .Kodi. How do I find it?

I did try to use -f v4l and thought it was my lack of understanding causing the missing ioctl messages.

The ffmpegx built binary is .kodi/addons/tools.ffmpeg-tools/bin/ffmpeg

Guessing the kernel update. - 6.15.6 to 6.16

Is ssh / samba working? Just the display (or all)

Should be fixed by https://github.com/LibreELEC/LibreELEC.tv/pull/10624

lutz108 both LE12.2 and LE13 have librespot 0.7.1 which incorporates the fixes you have referenced.

Moving all the reports from GitHub to here.
- https://github.com/LibreELEC/LibreELEC.tv/issues/7166
- https://github.com/LibreELEC/LibreELEC.tv/issues/8731
- https://github.com/LibreELEC/LibreELEC.tv/issues/7353
- https://github.com/LibreELEC/LibreELEC.tv/issues/10573
- https://github.com/LibreELEC/LibreELEC.tv/issues/8762
- https://github.com/LibreELEC/LibreELEC.tv/issues/8760

Some of the feedback / known issue / suggestions on the issues - please try these first.

• Disabling fast-transition (FT) in access-point radio properties (this may be resolved in current connman/iwd/drivers, there have been changes in all 3 code bases around this)
• Not using WPA3 (this may be resolved in current connman/iwd/drivers, there have been changes in all 3 code bases around this)
• Moving the device closer to the access-point to improve signal strength

**not recommended** - but has helped some.
/etc/modprobe.d/iwlwifi-opt.conf
Add the line "options iwlwifi 11n_disable=1" (without the quotes)

There is a report that on “unclean restart” connman always returns “invalid”

LE12.2 (nightly) and LE13 (nightly) both have the most recent iwd and connman. So any testing should be done against these releases. The kernel on 12.2 (nightly (6.16.12)) has diverged from LE13 - which is now 6.17.x on all except RPi, so testing should be performed on LE13 if not RPi.

As in the issue logs a number of detailed scenarios have been run though, with some success. There seems to be a number of corner cases that cause the issue (including the known ones above) - the interesting observation on https://github.com/LibreELEC/Libr…ment-3395445892 is the DFS and 80. E.g. Does this occur on a simple 20 channel…

Note - I test using a C9130AXI-Z 802.11ax 2.4 GHz/5 GHz access point at 20 MHz, no FT, no WPA3. Also test against Unifi AC Mesh.

iwd and connman are synced up to that of LE13.

Correct there is no b43 in LE12/13. I don’t see the wl driver returning in LE with “patches”, the decision to drop it was only made after the inability to obtain working patches across multiple kernel releases, and lack of support (community) - lots of reading and research done in the PR and issue, with references to the issue.

The wireless positive with LE12.2/13 is the now available upstreamed rtw88 wireless.

Here is the background. https://github.com/LibreELEC/LibreELEC.tv/pull/9522. there was some work being done in other patches that may have worked in later kernels, but didn’t work in the LE kernels, so it was dropped.

Quote from Jeffrey

For the Inter DG1, is the following change still necessary?

/flash/syslinux.cfg

It will default to i915 or XE depending on the how the drivers/pciids have been updated by Intel. To swap to the “other driver” will require the force_probe.

Fixed in https://github.com/LibreELEC/LibreELEC.tv/pull/10359 and https://github.com/LibreELEC/LibreELEC.tv/pull/10360

Some change in arguments that I can see. Taking a further look. The addon interface in LE Kodi looks right with a default of 0.0.0.0:8384

Aug 14 22:13:51 nuc12 systemctl[2790811]: Failed to stop service.system.syncthing.service: Unit service.system.syncthing.service not loaded.
Aug 14 22:13:51 nuc12 systemctl[2790813]: Failed to disable unit: Unit service.system.syncthing.service does not exist
Aug 14 22:13:51 nuc12 systemctl[2790814]: Created symlink '/storage/.config/system.d/service.system.syncthing.service' → '/storage/.kodi/addons/service.system.syncthing/system.d/service.system.syncthing.service'.
Aug 14 22:13:51 nuc12 systemctl[2790814]: Created symlink '/storage/.config/system.d/kodi.target.wants/service.system.syncthing.service' → '/storage/.kodi/addons/service.system.syncthing/system.d/service.system.syncthing.service'.
Aug 14 22:13:52 nuc12 systemd[1]: Starting service.system.syncthing.service...
Aug 14 22:13:52 nuc12 systemd[1]: Started service.system.syncthing.service.
Aug 14 22:13:52 nuc12 sh[2790904]: syncthing: error: unknown flag -o, did you mean one of "-h", "-C", "-D", "-H"?
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=80/n/a
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'.
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 1.
Aug 14 22:13:52 nuc12 systemd[1]: Starting service.system.syncthing.service...
Aug 14 22:13:52 nuc12 systemd[1]: Started service.system.syncthing.service.
Aug 14 22:13:52 nuc12 sh[2790978]: syncthing: error: unknown flag -o, did you mean one of "-h", "-C", "-D", "-H"?
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=80/n/a
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'.
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 2.
Aug 14 22:13:52 nuc12 systemd[1]: Starting service.system.syncthing.service...
Aug 14 22:13:52 nuc12 systemd[1]: Started service.system.syncthing.service.
Aug 14 22:13:52 nuc12 sh[2791028]: syncthing: error: unknown flag -o, did you mean one of "-h", "-C", "-D", "-H"?
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=80/n/a
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'.
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 3.
Aug 14 22:13:52 nuc12 systemd[1]: Starting service.system.syncthing.service...
Aug 14 22:13:52 nuc12 systemd[1]: Started service.system.syncthing.service.
Aug 14 22:13:52 nuc12 sh[2791077]: syncthing: error: unknown flag -o, did you mean one of "-h", "-C", "-D", "-H"?
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=80/n/a
Aug 14 22:13:52 nuc12 systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'.
Aug 14 22:13:53 nuc12 systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 4.
Aug 14 22:13:53 nuc12 systemd[1]: Starting service.system.syncthing.service...
Aug 14 22:13:53 nuc12 systemd[1]: Started service.system.syncthing.service.
Aug 14 22:13:53 nuc12 sh[2791127]: syncthing: error: unknown flag -o, did you mean one of "-h", "-C", "-D", "-H"?
Aug 14 22:13:53 nuc12 systemd[1]: service.system.syncthing.service: Main process exited, code=exited, status=80/n/a
Aug 14 22:13:53 nuc12 systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'.
Aug 14 22:13:53 nuc12 systemd[1]: service.system.syncthing.service: Scheduled restart job, restart counter is at 5.
Aug 14 22:13:53 nuc12 systemd[1]: service.system.syncthing.service: Start request repeated too quickly.
Aug 14 22:13:53 nuc12 systemd[1]: service.system.syncthing.service: Failed with result 'exit-code'.
Aug 14 22:13:53 nuc12 systemd[1]: Failed to start service.system.syncthing.service.