Posts by ajbathe

Quote from Reddirt

AJ must own an unfractured crystal ball. Solved the issue in a nano second and Thank You!

no, I studied the log on my machine and the solution was my 1st comment

just install that one: https://github.com/add-ons/script….3+matrix.1.zip

isAlive() has to be changed to is_alive()

I changed KERNEL and SYSTEM of LE11 on raspi4 with the old kernel 5.x, but saw the same behaviour, so I don't guess it's kernel related. Maybe the reason can be in the fact that wpa_supplicant was kicked out and iw is used now? As long as you can't establish a connection via console commands (like above), the way over GUI won't do it, wouldn't it?

I can offer some small script (named remount-flash); remove the txt-extension - was needed to upload here ...

I try to follow the way described in Connman and wifi - no connection so far

connmanctl
agent on
scan wifi
services

works as expected, but

connect wpa_your_network_psk

gives this message

Error /net/connman/service/wifi_e45f01a86411_4c696e75782d4e6574776f726b_managed_psk: Input/output error

Agent request cancelled by ConnMan

Retry (yes/no)? connmanctl>

a try with the gui immediately after my input of the password gets this message seen by journalctl -f

Mar 10 14:01:50 raspi4 dbus-daemon[380]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.10" (uid=0 pid=1058 comm="/usr/lib/kodi/kodi.bin --standalone -fs") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.4" (uid=0 pid=729 comm="/usr/sbin/connmand -nr --config=/etc/connman/main.")

I also switched off the 2.4 GHz network and only use 5 GHz for better connections. Hope, this problem can be solved soon. I tried many images of nighties and betas ... all the same. I suspect the iw-subsystem what replaces wpa_supplicant; but who handles now the psk-password-stuff?

I face the same problem, had a working configuration, but don't know when the bug appeared in the near past. But when doing some tests und checking, I realized that some parameter got changed wihtin the setting of my WiFi-configuration:

my old setting within ~/.cache/connman/wifi_[...]_managed_psk was:

Name=[deleted]

SSID=[deleted]

Frequency=5200

Favorite=true

AutoConnect=true

Modified=2021-02-02T16:29:52Z

Passphrase=****************

IPv4.method=dhcp

IPv4.DHCP.LastAddress=192.168.0.38

IPv6.method=off

IPv6.privacy=disabled

after trying to connect via connmanctl (see above) I got:

Name=[deleted]

SSID=[deleted]

Frequency=0

Favorite=true

AutoConnect=true

Modified=2023-03-09T14:42:47Z

Passphrase=****************

IPv4.method=dhcp

IPv6.method=off

IPv6.privacy=disabled

So the parameter of frequency changed from a working setting of 5200 to 0. Maybe this might help to track down this bug.

Normaly I use a LAN connection, but a new Raspberry Pi 4 with LibreELEC 11.0 wants to be at a friends house where only WiFi is possible.

This NUC BIOS is really strange:

When I select boot device via F10 to UEFI : USB : SanDisk : Part 0 : OS Bootloader, the Options menu will be printed, I can type run and "Loading /KERNEL... ok" is printed. Hangs!

With "Boot USB Devices First" selected within BIOS setup and no user interaction, the boot process will continue.

Intel VisualBIOS quality ... BTW, the stick gets booted with no problem on other machines in UEFI mode.

Thanx for the debug hint. I doubt that Intel will fix this BIOS bug as it was not able to fix the FASTBOOT problem. Can be closed.

Flashed an USB-stick with LibreELEC-Generic.x86_64-9.95.1.img.gz (and also LibreELEC-Generic.x86_64-10.0-nightly-20210323-32b3089.img.gz). Both images show the option screen, but can't boot installer, live or run image.

I guess it has something to do with the UEFI-only boot method. Secure boot is disabled. LibreELEC-Generic.x86_64-9.2.6 is able to start (and actually in use on a SDD). Wanted to test the BETA from the USB-stick.

LibreELEC (official): 9.2.4 on Intel NUC7PJYH -> LibreELEC-Generic.x86_64-9.2.4.img

[ 1743.230466] ------------[ cut here ]------------

[ 1743.230482] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out

[ 1743.230516] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230

[ 1743.230517] Modules linked in: 8021q rfcomm bnep iwlmvm mac80211 rc_su3000(O) ds3k(O) iwlwifi wl(PO) snd_hda_codec_hdmi intel_rapl intel_powerclamp snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep cfg80211 pcc_cpufreq btusb btrtl btbcm btintel bluetooth dvb_usb_dw2102(O) dvb_usb(O) rc_core(O) dvb_core(O) videobuf2_vmalloc(O) videobuf2_memops(O) videobuf2_common(O) ecdh_generic rfkill videodev(O) media(O) wireguard ip6_udp_tunnel udp_tunnel

[ 1743.230603] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 5.1.16 #1

[ 1743.230604] Hardware name: Intel(R) Client Systems NUC7PJYH/NUC7JYB, BIOS JYGLKCPX.86A.0055.2020.0603.1745 06/03/2020

[ 1743.230606] RIP: 0010:dev_watchdog+0x221/0x230

[ 1743.230608] Code: 00 49 63 4e e8 eb 92 4c 89 ef c6 05 40 1c 43 03 01 e8 e3 80 fc ff 89 d9 4c 89 ee 48 c7 c7 70 86 fa b2 48 89 c2 e8 d6 83 13 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48

[ 1743.230610] RSP: 0018:ffffa0eb77a03e68 EFLAGS: 00010286

[ 1743.230627] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000

[ 1743.230628] RDX: 0000000000040400 RSI: 00000000000000f6 RDI: 0000000000000300

[ 1743.230629] RBP: ffffa0eb77a03e98 R08: 000000000000032e R09: 0000000000000001

[ 1743.230630] R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000001

[ 1743.230630] R13: ffffa0eb7518c000 R14: ffffa0eb7518c438 R15: ffffa0eb74dcd880

[ 1743.230632] FS: 0000000000000000(0000) GS:ffffa0eb77a00000(0000) knlGS:0000000000000000

[ 1743.230633] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

[ 1743.230634] CR2: 00007f8e115e87fa CR3: 000000021320e000 CR4: 0000000000140eb0

[ 1743.230635] Call Trace:

[ 1743.230637] <IRQ>

[ 1743.230641] ? pfifo_fast_enqueue+0x120/0x120

[ 1743.230644] call_timer_fn+0x30/0x130

[ 1743.230645] ? pfifo_fast_enqueue+0x120/0x120

[ 1743.230646] run_timer_softirq+0x3ec/0x420

[ 1743.230648] ? ktime_get+0x3c/0xa0

[ 1743.230651] ? __do_softirq+0x9b/0x343

[ 1743.230653] ? irq_exit+0xc0/0xd0

[ 1743.230657] __do_softirq+0x107/0x343

[ 1743.230658] irq_exit+0xc0/0xd0

[ 1743.230660] smp_apic_timer_interrupt+0x71/0x130

[ 1743.230661] apic_timer_interrupt+0xf/0x20

[ 1743.230662] </IRQ>

[ 1743.230665] RIP: 0010:cpuidle_enter_state+0xc4/0x450

[ 1743.230666] Code: 00 00 31 ff e8 bd 86 29 ff 80 7d c7 00 74 12 9c 58 f6 c4 02 0f 85 62 03 00 00 31 ff e8 55 4b 2e ff e8 c0 7f 32 ff fb 45 85 ed <0f> 88 8d 02 00 00 49 63 cd 48 8b 75 d0 48 2b 75 c8 48 8d 04 49 48

[ 1743.230667] RSP: 0018:ffffffffb3203df0 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13

[ 1743.230668] RAX: ffffffffb3203e30 RBX: ffffffffb32c5960 RCX: 000000000000001f

[ 1743.230669] RDX: 00000195e0a1a169 RSI: ffffffffafdfbeb7 RDI: ffffffffafdfbaf0

[ 1743.230670] RBP: ffffffffb3203e30 R08: 0000000000000000 R09: 0000000000020cc0

[ 1743.230671] R10: 000002639bcde538 R11: ffffa0eb77a20564 R12: ffffa0eb77a28e70

[ 1743.230672] R13: 0000000000000007 R14: ffffffffb32c5c18 R15: ffffffffb32c5c00

[ 1743.230674] ? cpuidle_enter+0x17/0x20

[ 1743.230675] ? cpuidle_enter_state+0xc0/0x450

[ 1743.230677] cpuidle_enter+0x17/0x20

[ 1743.230679] call_cpuidle+0x23/0x40

[ 1743.230681] do_idle+0x221/0x260

[ 1743.230682] cpu_startup_entry+0x1d/0x20

[ 1743.230684] rest_init+0xa3/0xa5

[ 1743.230687] arch_call_rest_init+0xe/0x1b

[ 1743.230688] start_kernel+0x46c/0x48f

[ 1743.230690] x86_64_start_reservations+0x24/0x26

[ 1743.230692] x86_64_start_kernel+0x6f/0x72

[ 1743.230694] secondary_startup_64+0xa4/0xb0

[ 1743.230696] ---[ end trace f2f539d2d5598546 ]---

I often see this kernel warning and I am aware that this is seen also on other Linux distributions - but I don't know whether this is serious or can be ignored? Can anybody give me some light to this? Thanx a lot ...