WiFi issue on live from laptop, works fine after install to HD

Forum Forums Official Releases antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum” WiFi issue on live from laptop, works fine after install to HD

Tagged: 

  • This topic has 9 replies, 4 voices, and was last updated Nov 3-12:50 pm by Brian Masinick.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #28808
    Moderator
    BobC

    On my Dell D620 with BRCM 4311, when I try to connect to WiFi from live it doesn’t see any WiFi connections available, but after installing to HD they appear.

    I think its a network issue, not a Connman one, and I’ve seen 2 other people, plus one Distrowatch review that I think had the same issue.

    If any help is wanted making it fail and pulling data to analyze and solve it, I can use the D620 to help. The ones with the problem are all 64 bit, but I don’t have a 32 bit machine that is reasonable to run uninstalled from to test with.

    #28809
    Forum Admin
    anticapitalista
    Helpful
    Up
    0
    :D

    Could you test MX-19 live and see if the problem exists there? MX-19 uses network-manager.

    Philosophers have interpreted the world in many ways; the point is to change it.

    antiX with runit - leaner and meaner.

    #28810
    Moderator
    BobC
    Helpful
    Up
    0
    :D

    Sure…

    #28821
    Moderator
    BobC
    Helpful
    Up
    0
    :D

    Ok, It had the same problem with mx19-64 live. I ran inxi -Fxz on all 3 in case that might help

    PS: Let me know if there is some other config or log file that would help…

    • This reply was modified 1 year, 7 months ago by BobC.
    #28853
    Moderator
    BobC
    Helpful
    Up
    0
    :D

    Ok, I ran these commands on all 3. Attached is a zip file of the results from each of the 3 all run on the same Dell D620.

    cat /etc/modprobe.d/broadcom-sta-dkms.conf > broadcom-sta-dkms.conf
    lspci -vnn > lspci.txt
    cat /etc/resolv.conf > resolv.conf
    sudo iwconfig > iwconfig.txt
    sudo ifconfig -a > ifconfig.txt
    sudo lsmod > lsmod.txt
    inxi -Fxz > inxi.txt
    
    Attachments:
    #28862
    Moderator
    Brian Masinick
    Helpful
    Up
    0
    :D

    BobC

    I know that this Broadcom device is not (or was not) a standard device that is universally a available.

    I have had this device on past systems though and I don’t remember any problem with it on either antiX or MEPIS. I may have had the device before MX replaced MEPIS.

    On some distributions I had to go get the device config or a driver and manually install it, then it worked. I had a D600 at one time, but I think it had a wireless card that worked on almost anything, never had a problem.

    Brian Masinick

    #28863
    Moderator
    Brian Masinick
    Helpful
    Up
    0
    :D

    I should have said that Broadcom in the past did not provide device driver code, but they usually had driver binaries available.

    Not sure what is available these days. I have not had a system with a Broadcom device recently.

    Brian Masinick

    #28867
    Moderator
    BobC
    Helpful
    Up
    0
    :D

    I have had the broadcom 43xx series wifi devices that came in both hp and Dell laptops.

    I will get a dmesg readout

    #28909
    Member
    Yoghi
    Helpful
    Up
    0
    :D

    I too encountered troubles to connect with antix-19 base from live and I have a Ralink chip not a Broadcom.

    It’s due to a soft rfkill signal if you give the command rfkill list you will see this result
    yoghi@ranger:~
    $ rfkill list
    0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

    give the command rfkill unblock 0 and you are done.

    To anticapitalista to find why this spurious rfkill signal 😛

    Hope this helps

    Yoghi

    • This reply was modified 1 year, 7 months ago by Yoghi.
    #28912
    Moderator
    Brian Masinick
    Helpful
    Up
    0
    :D

    Nice work, Yoghi!

    I too encountered troubles to connect with antix-19 base from live and I have a Ralink chip not a Broadcom.

    It’s due to a soft rfkill signal if you give the command rfkill list you will see this result
    yoghi@ranger:~
    $ rfkill list
    0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no

    give the command rfkill unblock 0 and you are done.

    To anticapitalista to find why this spurious rfkill signal />

    Hope this helps

    Yoghi

    • This reply was modified 1 year, 7 months ago by anticapitalista.

    Brian Masinick

Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.