Home of the Squeezebox™ & Transporter® network music players.
Page 118 of 135 FirstFirst ... 1868108116117118119120128 ... LastLast
Results 1,171 to 1,180 of 1349
  1. #1171
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    190
    Quote Originally Posted by paul- View Post
    Maintained by user solves the quote issues, as the file is used without modification, but Iĺll take another look at that method you used.

    No quotes around country code is per spec......and country code is required for certain frequencies permitted in Europe to work.

    He has done it via the web interface too. In all methods, dmesg shows his issue is the WiFi drivers and firmware is not loading. I guess I never asked him for the contents of /mnt/mmcblk0p2/tce/onboot.lst
    ****Update****

    My issue seemed to be Mac OS TextEdit not giving me a clean simple text edit, I changed to using Notepad++ on Windows and all was good using the documented procedure here https://www.picoreplayer.org/how_to_...ethernet.shtml
    or by modifying the sample wpa_supplicant.conf as outlined by Paul- here https://forums.slimdevices.com/showt...l=1#post965405

    More details of my fix here...

    https://forums.slimdevices.com/showt...l=1#post965559

    Probably a better read than the red herring below

    **************

    OK, I left the "Maintained by user" bit out as I hadn't fully investigated that setting and didn't want to confuse things further - I posted at 2am after several hours of testing/playing around with wifi settings and needed to get some sleep.

    This morning I've tested the "Mbu" setting.

    So to clarify last nights testing was all with this in the boot partition wpa_supplicant.conf

    # If you want to manually configure wifi, and maintain all settings manually.
    # Changes would be made by saving a new file on the boot partition.
    # no part of pCP would modify this file. Ensure the file contains this following line.
    #
    Maintained by user
    #
    # If you would like to maintain wifi settings in the web interface remove the above line.

    and what I reported stands.

    If Maintained by user is commented out... (that's how it was set in my downloaded b9 image wpa_supplicate.conf.sample)

    # If you want to manually configure wifi, and maintain all settings manually.
    # Changes would be made by saving a new file on the boot partition.
    # no part of pCP would modify this file. Ensure the file contains this following line.
    #
    # Maintained by user
    #
    # If you would like to maintain wifi settings in the web interface remove the above line.

    Then using the wpa_supplicant.conf file in the boot partition does not work, regardless of what's in quotes and what isn't

    with ssid and psk in quotes, then everything looks OK but it just doesn't connect and get an IP address
    with ssid and psk no quotes then I see the same behaviour for psk as before - it populates the PSK Passphrase box and no connection
    with ssid no quotes and psk quotes then again everything looks OK but it just doesn't connect and get an IP address

    There are so many permutations it's hard to write down everything clearly, and maybe not necessary, I'll have a think about the best way to write up everything I've seen and tried, I need a break and the dog needs her morning walk.

    But the bottom line for me and my suggestion for Zabizabo to try is

    1. Start with a fresh image
    2. Open image boot partition rename wpa_supplicant.conf.sample to wpa_supplicant.conf
    3. Edit wpa_supplicant.conf...

    Delete the line # Maintained by user
    country=country code (no quotes)
    ssid=yourSSID (no quotes)
    psk="yourPSK" (make sure quotes are used)

    4. Save the edits
    5. Boot Pi from new image with edited and renamed wpa_supplicant.conf Note: DO NOT plug in ethernet cable
    6. Wait 2-3 of minutes
    7. Pi should have connected to wifi, scan for ip address (I use LanScan) or check router for ip address
    8. If successfully found, connect to pCP using ip address in web browser
    9. Go to Wifi Settings page, in Set Wifi Config section re-enter your SSID, PSK passcode and Country code and click on Save
    10. Wait for save to complete
    11. Click on Diagnostics button
    12. Diagnostics summary should show correct ssid, country code and have a passphrase rather than passcode
    13. Shutdown and power cycle Pi to check settings have stuck
    14. Reconnect via web interface and configure up the rest of pCP

    This has worked every time for me.

    Cheers

    Kev

    PS for Paul, appreciate you've seen some other issues in your trouble shooting with Zabizabo and I obviously bow to your in depth knowledge on those things, if there's other issues at play here then obviously the above may not work, but having seen how confusing it can all get, starting from the known state of a fresh image with the above procedure hopefully will work for Zabizabo as well, that's how I've been testing, fresh image every time I tried something new.
    If we can get hm up and running then if needed I'm happy to help with further investigations on why the normal method of using wpa_supplicant.conf in the boot partition doesn't work.

    PPS after clarification by Greg, some of my assumptions around manipulating "Maintained by user" above are wrong, I'm not going to re-write everything, but I have corrected to procedure to reflect that new understanding.
    Here's that discussion with Greg... https://forums.slimdevices.com/showt...l=1#post965492
    Last edited by KeBul; 2020-02-21 at 14:51.

  2. #1172
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    190
    Mine reports the same Revision (c03111) and PCB Revision (1.1) as Man in a van's

    Kev
    Last edited by KeBul; 2020-02-21 at 03:06.

  3. #1173
    Senior Member Greg Erskine's Avatar
    Join Date
    Sep 2006
    Location
    Sydney, Australia
    Posts
    1,798
    If you want to maintain your own wpa_supplicant.conf you must put *exactly* this in your file.

    # Maintained by user

    Comment is required in first column. Space between # and Maintained is required. Exact capitalization is required.

    The hash prevents the line being interpreted by wpa.

    This is IMPORTANT: Without this exact line, piCorePlayer will take control. It read your wpa_supplicant.conf and create a brand new one formatted correctly 99% of the time. It will handle most common formatting issues we have seen people do.

    Obviously, if you decide to maintain your own wpa_supplicant.conf you must make it 100% correct.

  4. #1174
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    190
    Quote Originally Posted by Greg Erskine View Post
    If you want to maintain your own wpa_supplicant.conf you must put *exactly* this in your file.

    # Maintained by user

    Comment is required in first column. Space between # and Maintained is required. Exact capitalization is required.

    The hash prevents the line being interpreted by wpa.

    This is IMPORTANT: Without this exact line, piCorePlayer will take control. It read your wpa_supplicant.conf and create a brand new one formatted correctly 99% of the time. It will handle most common formatting issues we have seen people do.

    Obviously, if you decide to maintain your own wpa_supplicant.conf you must make it 100% correct.
    Thanks for the explanation Greg, reading your post more carefully (and Paul's last one) I think I fully get "Maintained by user", the misunderstanding on my part was thinking "remove the above line" meant comment it out, not delete it completely (and that explains the reverse behaviour I was seeing and not understanding, but thought I'd address that separately once Zabizabo was sorted).

    However, esssentially the behaviour I've been seeing remains the same...

    ****Update****

    My issue seemed to be Mac OS TextEdit not giving me a clean simple text edit, I changed to using Notepad++ on Windows and all was good

    More details of my fix here...

    https://forums.slimdevices.com/showt...l=1#post965559

    **************

    In the boot partition wpa_supplicant.conf,

    Leaving # Maintained by user in and having ssid in quotes = no connection

    Removing # Maintained by user and leaving the quotes off the ssid = connection

    I have edited the procedure in my previous post to reflect the correct way of removing # Maintained by user hopefully reducing any confusion.

    Cheers

    Kev
    Last edited by KeBul; 2020-02-21 at 14:55.

  5. #1175
    Member
    Join Date
    Jan 2020
    Location
    Bordeaux, France
    Posts
    60
    Quote Originally Posted by KeBul View Post
    OK, I left the "Maintained by user" bit out as I hadn't fully investigated that setting and didn't want to confuse things further - I posted at 2am after several hours of testing/playing around with wifi settings and needed to get some sleep.

    .
    Hiv Kev,

    Hope you will be able to take a nap today

    Thanks for your help, I will try this taking into account the discussions ongoing.

    Regards,

    Christophe

  6. #1176
    Senior Member KeBul's Avatar
    Join Date
    Sep 2009
    Location
    London
    Posts
    190
    Quote Originally Posted by Zabizabo View Post
    Hiv Kev,

    Hope you will be able to take a nap today

    Thanks for your help, I will try this taking into account the discussions ongoing.

    Regards,

    Christophe
    Thanks, maybe later this afternoon.

    Hopefully we'll get your Rpi 4 up and running soon.

    Kev

  7. #1177
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    2,478
    Is there a way to force the WiFi firmware to load from the command line and see what, if any, errors it gives?
    Paul Webster
    http://dabdig.blogspot.com
    Author of "Now Playing" plugins covering Radio France (FIP etc), KCRW, Supla Finland, ABC Australia, CBC/Radio-Canada and RTE Ireland

  8. #1178
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,077
    This quote thing is bothersome. Here is the full wpa_supplicant.conf, with notes from w1.fi https://w1.fi/cgit/hostap/tree/wpa_s...upplicant.conf

    There is a ton of unneeded stuff in there, but the network block starts at line 805. The various examples start at line 1569

    # ssid: SSID (mandatory); network name in one of the optional formats:
    # - an ASCII string with double quotation
    # - a hex string (two characters per octet of SSID)
    # - a printf-escaped ASCII string P"<escaped string>"
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  9. #1179
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    3,077
    Quote Originally Posted by Paul Webster View Post
    Is there a way to force the WiFi firmware to load from the command line and see what, if any, errors it gives?
    The kernel notifies udev to load it automatically

    1) If the wifi chip is detected
    2) If the files are present on the drive.

    The files are located in
    wireless-KERNEL.tcz and firmware-rpi-wifi.tcz

    You can validate if they are loaded by running.
    tce-load -i firmware-rpi-wifi.tcz
    tce-load -i wireless-KERNEL.tcz

    As soon as those are loaded, you should see this in dmesg.(This is a rpi3b+)
    Code:
    [333480.822855] cfg80211: Loading compiled-in X.509 certificates for regulatory database
    [333480.843465] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
    [333480.860368] brcmfmac: F1 signature read @0x18000000=0x15264345
    [333480.864582] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
    [333480.865941] usbcore: registered new interface driver brcmfmac
    [333481.093732] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
    [333481.102520] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  10. #1180
    Senior Member
    Join Date
    Oct 2016
    Posts
    240

    Interesting

    Interesting read on all the WiFi RPi4 issues.

    I have two RPi4's, getting wifi to work has always been a piece of cake. Maybe flashed a couple dozen times between the two.

    Lots of great info, just in case I have an issue one day.

    FWIW, I just connect to Ethernet first then use the GUI to start and connect to wifi. Seems to be a robust method for me at least.


    Thank you Paul for all your work, and everyone else too.


    ~Ed

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •