Jump to content

bobjones58

Members
  • Posts

    7
  • Joined

  • Last visited

Posts posted by bobjones58

  1. As requested, fresh sd card with your image Armbian_22.11.0-trunk_Station-p2_sid_edge_6.1.0_xfce_desktop.img.xz:

     

    root@station-p2:~# uname -a
    Linux station-p2 6.1.0-rc4-media-6 #trunk SMP PREEMPT Fri Nov 11 14:46:18 MSK 2022 aarch64 GNU/Linux
    
    root@station-p2:~# ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether d6:e9:5d:4f:8f:67 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.228/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
           valid_lft 43070sec preferred_lft 43070sec
        inet6 fe80::3251:e133:4887:84aa/64 scope link noprefixroute
           valid_lft forever preferred_lft forever
    3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
        link/ether d2:e9:5d:4f:8f:67 brd ff:ff:ff:ff:ff:ff

     

    Console boot log attached.

    minicom.log

  2. admin@station-p2:~$ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host
           valid_lft forever preferred_lft forever
    2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
        link/ether d6:e9:5d:4f:8f:67 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether d2:e9:5d:4f:8f:67 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.227/24 brd 192.168.1.255 scope global dynamic noprefixroute eth1
           valid_lft 34646sec preferred_lft 34646sec
    4: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
        link/ether 18:1d:ea:34:f3:45 brd ff:ff:ff:ff:ff:ff
        altname wlP2p1s0
        inet 192.168.30.151/24 brd 192.168.30.255 scope global dynamic noprefixroute wlan1
           valid_lft 34295sec preferred_lft 34295sec
    5: wlan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
        link/ieee802.11/radiotap 00:c0:ca:a6:73:70 brd ff:ff:ff:ff:ff:ff
    6: mon1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
        link/ieee802.11/radiotap 18:1d:ea:34:f3:45 brd ff:ff:ff:ff:ff:ff
    
    admin@station-p2:~$ sudo airmon-ng
    
    PHY     Interface       Driver          Chipset
    
    phy1    mon1            iwlwifi         00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
    phy1    wlan1           iwlwifi         00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)
    phy2    wlan2           mt76x2u         MediaTek Inc. MT7612U 802.11a/b/g/n/ac

     

    Two wlan adapters show, but one is M.2 and the other is USB based.  So the BCM is not detected here.

     

    In older dmesg logs I used to see this type of entry in both 4.19 and 5.18 kernels:

     

    [    2.249588] mmc3: new ultra high speed SDR104 SDIO card at address 0001

     

    and then  either the wl (4.x kernels) or brcmfmac (5.x kernels) driver would load.  I no longer see this entry in dmesg so

     

    Quote

    Is there an interface in the system ?

     

    I would have to say it is not detected any longer.

     

  3. Quote

    Wi-Fi chip built into P2 now works

     

    I have a hardware failure so sadly I can't benefit from your software work.  As I note here, it used to work but as I experimented with ever newer kernels and other distributions such as slackware in an attempt to get pci working, it has decided to no longer be functional at all, on any old or new kernel.

     

    If you have ideas on any functional troubleshooting I can do to look at the built-in wifi to diagnose, I would give it a try.  But frankly for $255, its cheaper just to buy a new unit and pick up from there with working hardware.  The shipped BCM adapter is only WiFi 6, not 6E, so really is not all that interesting (for my use).  

  4. Werner explained it - use your private images until when/if it gets rolled up into Armbian.  I was ready to try the changes but I forgot about the private repository so I went current and started compiling my own armbian build, hoping that your changes were there.  

     

    Using StationP2 device only but using a converter for the M.2 slot so I can use other, newer, 802.11 Wifi chipsets that need more recent kernels for updated drivers.  I can't test the built-in broadcom wifi chip as it left this world some time ago - does not get detected by any OS anymore.

     

    As Igor says, thank you for supporting my addiction to low-cost ARM hardware.

     

    admin@station-p2:~/software/scripts$ uname -a
    Linux station-p2 6.1.0-rc4-media-6 #trunk SMP PREEMPT Fri Nov 11 14:46:18 MSK 2022 aarch64 aarch64 aarch64 GNU/Linux
    admin@station-p2:~/software/scripts$ lspci
    0002:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01)
    0002:01:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29)

     

  5. In distributions that include 4.x series kernels, pcie is detected and the built-in broadcom wireless chip is functional with the wl driver.  

     

    I would like to move to a 5.x series kernel, but I noticed that pcie is not detected at all, and though wifi is detected with the brcmfmac driver, it will not function to scan or connect to anything.

     

    I grabbed the latest image from this week (have tried many previous, including building my own armbian image) but no luck. Has anyone gotten these items to work with a 5 series kernel?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines