Posts by jim_p

  • Adding boot parameters to the rpi (and any arm build probably)

    Good boot

    http://ix.io/3IV8

    Bad boot

    http://ix.io/40Ae

    I had to connect via ethernet so as to ssh to it and do all that. The 2 minutes of waiting that you asked were checked via uptime, because I am no good at timing stuff without a clock :P

    Weird thing of the day is that the first boot was a good one, the second was a bad one and the third was a good one too. I booted for the third time because I wanted to check dmesg about wlan0 and it does say whatever is mentioned above with the warning.

  • Adding boot parameters to the rpi (and any arm build probably)

    Thank you for the info.

    I tested wifi on le 11 x64 a bit more, like so: boot > libreelec settings > connection > check if wireless is (at least) available in there right after boot > reboot and repeat. Out of 10 boots, the wifi was available only in 2 or 3 of them and never twice in a row. The good part on that is that is was also connected those 2-3 times it was available.

  • Adding boot parameters to the rpi (and any arm build probably)

    I just noticed that wlan0 is not mentioned anywhere in dmesg of the rpi. Is this logical? I checked on yesterday's and today's nightlies, i.e. before and after the upgrade.

    Also, has the nightly for le 10 moved to iwd yet? I may switch my 10.0.2 x64 installation to nightly and check if those dropped frames still happen. I am totally giving up on le 11 on x64 by the end of the month because of that wifi issue.

    ---edit

    In case anyone has any idea, this is the... horror that happens on dmesg when I run ifconfig wlan up to bring up the wifi

    This does not happen on le 10 or 9 on x64 on the same hw.

  • Adding boot parameters to the rpi (and any arm build probably)

    Another day, another new weird thing comes up. As usual, the rpi did not connect wirelessly on first boot, so I went wired to do today's update.

    First, it stopped at like 95% of the download, so I had to cancel it with ctrl+c and continue it with wget's -c parameter and it completed it after a few seconds. This was happening at the start due to poor wireless signal, but why did it happen on wired connection too?

    Second, I did the usual connman procedure of connecting it wirelessly, but connman returned no propmt for the key this time, so I thought it connected successfully. But it did not, according to iwconfig and ifconfig, so I tried again and this time I got this new output of the connection being in progress

    Code
    connmanctl> connect wifi_bxxx_4xxx_managed_psk
Error /net/connman/service/wifi_bxxx_4xxx_managed_psk: In progress

    I retried again after like 1 minute but it showed the same, so I let it continue for a couple of minutes, did the procedure again and I was prompted for the key like usual.

    Third, once the update was downloaded (and after checking its sum with the same file downloaded on my pc), I issued a reboot. Unlike previous versions where the connection was terminated instantly (especially via ethernet), le 11 takes some to disconnect and putty to report that the connection was terminated. After like 1 minute, putty was still on and returned to the prompt so as to run another command. I then ran dmesg, which showed the usual cec errors that come up when it is not connected to the tv, but nothing more related to the filesystem.

    Then I decided to run htop to check if some other process is delaying it, and it said "sh: htop: access denied" (or something like that). Its green led was permanently on, not blinking, so I hesitated to pull the plug. But I pulled the ethernet cable and after like 30 seconds, I finally saw the green led come of and back on again.

    Long story short, it booted to the new nightly, I sshed to it, checked dmesg again for filesystem issues, but still no luck. I ran connman again, reconnected to the wireless (it did not ask for the key this time), rebooted, and luckily wireless was active again after the reboot.

  • Adding boot parameters to the rpi (and any arm build probably)

    That change was done only 1 month ago. 1 month ago I wasn't even using the nightly on the rpi, let alone on x64.

    And the issue with that message has appeared very recenty, like 3-4 nighlies ago. Did something else change recently, e.g. the kernel maybe? I am sad, because 11 fixed the framedrops issue that 10 has but introduced that wifi issue. Anyway, I will keep looking.

  • shell script to get the latest nightly (old)

    There you go.

  • Adding boot parameters to the rpi (and any arm build probably)

    Back to the rpi with a new error in connman. As usual, 1st boot of the day, it does not connect wirelessly so I connect the cable, ssh to it to launch connman to see what is going on. First try returned no prompts to enter the key or anything

    Code
    connmanctl> connect wifi_bxxx_4xxx_managed_psk
connmanctl> exit

    I waited a bit, checked ifconfig, checked iwconfig and it had not connected yet. Back to connman for another try and I get this progress error for the first time ever

    Code
    connmanctl> connect wifi_bxxx_4xxx_managed_psk
Error /net/connman/service/wifi_bxxx_4xxx_managed_psk: In progress
connmanctl> exit

    I waited a bit more, checked ifconfig again, checked iwconfig again and still nothing. So I tried again and this time it popped the usual "the network exists and has this key" prompt

    Code
    connmanctl> connect wifi_bxxx_4xxx_managed_psk
Agent RequestInput wifi_bxxx_4xxx_managed_psk
Passphrase = [ Type=psk, Requirement=mandatory ]
PreviousPassphrase = [ Type=psk, Requirement=informational, Value=mywifikey ]
Passphrase? mywifikey
connmanctl> exit

    And it finally connected!

  • Update URL/channel for nightly builds

    What type of magic do I have to do so as to add test.libreelec.tv (or any of its subdirectories) as a source in kodi's file manager? I add it like in the picture, but when I access it, it is completely empty.

    (screenshot is from my pc running kodi 19.4 on debian testing/unstable x64, but you get the idea)

  • shell script to get the latest nightly (old)

    Quote from JoeAverage

    But I told you in another thread: don't use the script anymore

    Well, I had to test its complete functionality, even for once!

    As for /etc/issue, it shows exactly what you see in the motd when you log in via ssh, e.g.

    Code
    ##############################################
#                 LibreELEC                  #
#            https://libreelec.tv            #
##############################################


LibreELEC (community): nightly-20220612-363112b (RPi2.arm)

    The text in the parentheses is the only thing that mentions the architecture. On x64 it says "generic.x86_64".

  • Adding boot parameters to the rpi (and any arm build probably)

    I know that about dmesg. Wouldn't the kernel find a wireless interface at boot and name it wlan, like I mentiona above? Why is it not in dmesg then? I will keep searching, athough I do not know how much longer I can keep that installation.

    Also, I noticed that wl is used for it, like in le 10 and 9. How can I blacklist it and test b43 that also supports it?

    In other news, one thing I managed to test on x64 le 11 was video playback on my old laptop. One of the reasons I have not yet moved to le 10 there is because I get frame drops on every video (file or stream), regardless of resolution.

    The stream/file plays fine, the cpu usage is at normal levels, but the motion is not as smooth as in le 9. It seems as if it skips some frames and it happens even on low resolutions like 360p. So, I discovered that it does not happen on le 11 and I am pleased :)

    ---edit

    Well, this happened on the first boot of today's nightly. It is on dmesg and it seems serious.

    Code
    [  206.501651] netdevice: wlan0: Incorrect netdev->dev_addr

    ---reedit

    I just found the way to blacklist a module.
    https://wiki.libreelec.tv/how-to/blacklist-kernel-module

    But there is no b43!

    Code
    # modinfo b43
modinfo: ERROR: Module b43 not found.

  • Update URL/channel for nightly builds

    Quote from CvH

    you can crossgrade between generic and generic-legacy without any problem, if you are unsure what you want to use then go for "generic"

    Are you sure about that? Yesterday I upgraded from generic to generic-legacy with no issues. And I tried to do the same today, but the other way round (generic-legacy to generic) and an error came up at boot saying something about a file named ".nocompat". It did not upgrade and it still is on yesterday's nightly.