Posts by frakkin64

    if I had said something like that to a customer, if I were to blindly guess their problem, I would have been fired before a second had passed

    Your not a f**king customer, you entitled sh!t heel. This isn't a company, you didn't buy a product, it's an open source / free software project. It's really quite unbelievable your mindset. If you have a problem, then isolate it, and go to the upstream project that maintains the software and get their help. It's unreasonable to ask a team of 6 or 8 people to support you, your hardware, your network, your life, for free.

    Users like you are why projects like these fall apart, and people lose interest in contributing. You have a problem, then contribute to the solution rather than being a bunch of whiners. Take some damn responsibility, or pay someone to support your lazy ass.

    The main issue why I'm searching for this is (due to switch from MEZ to MESZ) that EPG is off-by-one within Kodi.

    Maybe a dumb question, but did you restart Kodi? I don't really use the EPG guide a whole lot any more, because I usually just schedule recordings on Tvheadend web GUI, but I remember it used to always have this problem with time zones switched between standard & daylight savings time and a restart of Kodi would fix it.

    I am fairly sure connman has nothing to do with your problem, in fact this looks like connman is probably reverse mapping to the first timezone that matches your offset.

    wpa_supplicant is not onboard anymore, or what did you mean by mention that?

    No. I think the supplicant (iwd/wpa_supplicant) can request the driver to handle authentication (driver offloading) or it can handle it by receiving the raw frames. It's possible wpa_supplicant version used in 10.x didn't support driver offloading, or it had workarounds to handle driver problems, or the drivers have issues, really could be a dozen different things. Taking driver offloading out of the picture should eliminate the wifi firmware/driver code from the authentication problem, or it could still be iwd. This is just speculation, like many others I don't really have a problem, so no direct experience to speak of.

    I think the only other thing to try out to eliminate the kernel/driver/firmware would be to revert to wpa_supplicant and see how that goes. You should be able to revert to wpa_supplicant by reversing this commit, but that won't be a permanent fix as they could drop the wpa_supplicant package and it may not receive any future updates since the distribution has moved on.

    Edit: BTW, I doubt it's kernel or firmware, Raspberry Pi OS also pushed out the same kernel recently, and would think there would be posts on the forums. LE appears to coordinate with Raspberry Pi teams.

    ajbathe You can give this a shot, I do have devices on 6.1.19 with brcmfmac and haven't noticed any issues, but it may be specific to features your using that I am not, or perhaps wpa_supplicant didn't support offloading by default. It's just interesting they single out brcmfmac.

    offloading [Wiki]

    Code
    cat > /storage/.config/modprobe.d/brcmfmac_disable_fw_offload.conf << 'EOF'
    options brcmfmac feature_disable=0x82000
    EOF

    I am confused as to why the RPI4 folder has all AARCH 64 updates which when I tried of course says Incompatible with my Raspberry Pi4

    I think the intent is to move to aarch64 for LE 12 and later for devices that support it / where it is feasible. It has been mentioned in the forum that basic intent, but I don't think there is anything yet on how to transition.

    LE 12 is a development build, so if you don't know how to handle problems with it then you might want to wait until it is fleshed out further or released. There is a way to force the installation, but all binaries not part of the image (i.e. addons) would be incompatible, broken, and could cause crashing, so if you don't know how to handle all of that then you should do a fresh install or wait. You may also find some addons are not compatible/available yet, as some of the addons did have to change to accommodate aarch64. And naturally it could be unstable, as it's a development build.

    If your going to do it, would recommend a fresh install to a new SD card, so it's easier to move back.

    see the full journalctl versions :)

    http://ix.io/4rMQ & http://ix.io/4rMR - I already thought that iwd log could not be meaningful enough

    duh, so fixated on iwd logs.

    This is where things go sideways. Result 2 means NETDEV_RESULT_ASSOCIATION_FAILED, good scenario is 0. Then it sends back a failed via dbus to connman. Where to go from here, not sure, it doesn't really tell you a whole lot about what's going on, so maybe you have to debug the kernel at this point.

    Code
    station.c:station_connect_cb() 3, result: 2

    By the way there are reports a few years ago of iwd + brcmfmac driver problems (but I think that was in AP mode, didn't really read into it too far), that is probably one other important difference for me as I don't use built-in wifi. I use realtek 802.11ac dongles. The built-in wifi on the Pi4 is constrained to an effective ~80Mbps by the SDIO bus.

    ok: autoconnect after boot; nok: passphrase-request

    Not an expert on iwd debugging, but a few interesting things:

    1. regulatory domain is set after the scan is triggered in the "nok" version, and before in the "ok" version. not sure if that matters.

    2. the "nok" version seems to have been disconnected and reconnected, no idea why but this section is different (this appears to be the reconnect, work item 3 was the original connect attempt, then it moves on to work item 4 & 5 to retry).

    This bit below seems to always happen regardless of good/bad connects, I am guessing the way connman/iwd integrate is connman has the passphrase so it probably asks iwd to scan, then tells iwd to connect, iwd says got a connect/handshake but what's the passphrase, connman sends it. So perhaps the issue is if it went through this sequence and received a disconnect and is asked again it doesn't quite know how to handle it. Line 218 is the start of the first connect attempt, then line 255 is the second one in the "nok" file.

    Code
    network.c:network_connect_psk() ask_passphrase: true
    agent.c:agent_request_passphrase() agent 0x15765f8 owner :1.6 path /net/connman/iwd_agent
    agent.c:agent_send_next_request() send request to :1.6 /net/connman/iwd_agent
    agent.c:agent_receive_reply() agent 0x15765f8 request id 33

    It's possible all of the reported invalid key situations are in fact the same problem, no idea really. It might be useful to send this over to the connman/iwd mailing lists, or wait for one of the developers and see if they have any other insight.

    BTW, If you have paired connman & iwd debug logs that would probably be useful to the mailing lists exhibiting good/bad at the same time.

    The statement that the bug lies between connman and iwd is right.

    It might be useful to capture iwd debug logging. Try this and you will find debug logging in journalctl --unit=iwd.

    Code
    mkdir -p /storage/.config/system.d/iwd.service.d
    cat > /storage/.config/system.d/iwd.service.d/debug.conf << EOF
    [Service]
    ExecStart=
    ExecStart=/usr/lib/iwd -d
    EOF

    nope, my passphrase are only numbers. but I can state: 11.01 is better and manually usable, but who want's to connect after every (re)boot

    Yeah weird. By the way the Frequency thing is nothing as far as I know. Mine is also 0, and no problems choosing the 5GHz band and auto-connecting, so I don't know if I would waste a lot of time on chasing that one.

    kernel 6.1.19 was the one to save us all but failed. what is the name of the next savior? and don't say jesus.

    If you go back and read, that is not what was said. In fact it was explicitly stated it may not fix your issue.


    I can report some success: with LE11.0.1 on my RPi4 I can connect to Wifi again

    Based on logs I have seen, the problem seems to be communication/signaling between connman & iwd. It might be a good idea to see if connman developers have any insight (see below for their details). There is also a patch specifically about hidden SSIDs & invalid-key, which I think was your problem? This would require you to apply the patch to LE, rebuild, and test. Author is waiting for feedback from others to see if it resolves the problem. I think the problem your finding here is no one from the development team seems to have the problem. I am also using RPi4 with LE12 & LE11, and don't have any issues. So it's either hidden SSIDs, or perhaps something illegal about the passphrase that iwd doesn't like, don't really have any clue.

    [PATCH] service: Fix hidden service with wrong passphrase - VAUTRIN Emmanuel (Canal Plus Prestataire)

    when you know what the error is, spend more time troubleshooting before you release a new version

    Because people will start asking when Kodi 20.1 will be released, and other fixes are delivered. Even commercial products will do this -- this is why they have known issues in release notes.

    I turn off logging and use shared MySQL database on a server, haven't really had problems with SDs and some of them have been in there for 2 or 3 years constantly on. Eventually they will die, and I have backups and spares. I just use base Kodi and pvr.hts and youtube, so not a lot of writes going on.


    Code
    <advancedsettings version="1.0">
        <!-- https://kodi.wiki/view/Log_file/Advanced -->
    
        <!--
           -1 = no logging
            0 normal logging
            1 debug logging
        -->
        <loglevel hide="true">-1</loglevel>
    </advancedsettings>


    Another option is network booting, I don't know if anyone actually uses it, I have not tested it. I suppose you could use a hybrid option with SD boot and NFS-mounted storage. It's only noted as supported on select devices, Pi4 supports PXE booting but this wiki entry doesn't mention how to configure it, but guessing the DHCP server needs to push a tftp host to the client to configure it. I am fairly sure this presumes ethernet only as well -- which is why I haven't tried it or the hybrid option.

    https://wiki.libreelec.tv/configuration/network-boot


    Disabling logging and shared MySQL db has been working fine for me. It would be nice if I could offload the PVR channel data and textures data too.

    (I do not know anymore why I added PATH=/build/build.LibreELEC-RPi4.arm-11.0-devel/toolchain/bin:$PATH, so it might not be required)

    It should not be required, I don't use LE's Docker files, but their jammy Dockerfile is the same as mine except I run with UID/GID from the outside user so I don't had to fiddle with permissions with the mounted volumes.

    Running the container looks like this:

    docker run -it --rm -v $(pwd):/build -w /build -e PROJECT=RPi -e DEVICE=RPi4 -e ARCH=ARM libreelec make image

    Docker already will wrap it in /bin/sh -c. No path modifications, no symlinks, nothing. It just works. You may want to make sure your permissions are umask 022.

    Is anyone going to put the drivers into version 10 for the Pi 4?

    I would just upgrade to LE11, otherwise vendor driver is probably your best bet. In both cases for RPi4 you will have to build your own image, guessing we won't see rtw88 native until LE12 for RPi4. I believe the main reason it is in Allwinner builds is because some of the boards are using the SDIO-based rtw88 chips.

    https://github.com/RinCat/RTL88x2BU-Linux-Driver`

    This is more or less the patch you would need to apply for that vendor driver:

    Also lots of USB cables are poorly made, have thin 5V and GND strains, thus a high resistance and drop A LOT of (milli-)volts under high currents. Finding proper cables isn't easy (most of them are just crap).

    Thank you for this, never really thought about this but it makes sense. Also read up on this problem, and the author's rationale why Raspberry Pi and others are pushing 5.1V PSUs:

    USB Cable Resistance: Why your phone/tablet might be charging slow
    Tablets and smartphones are now ubiquitous, and almost universally, they rely on some form of USB connection to provide the power to charge the device. This…
    goughlui.com