Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #62396 > unrolled thread

Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

Back to article view | Back to linux.debian.kernel

Contents

  Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Göran Weinholt <weinholt@debian.org> - 2018-10-20 11:10 +0200
    Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Matthias Luescher <lueschem@gmail.com> - 2018-11-29 22:30 +0100
      Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Stefan Wahren <stefan.wahren@i2se.com> - 2018-11-29 23:20 +0100
        Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Matthias Luescher <lueschem@gmail.com> - 2018-11-30 22:30 +0100
          Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Stefan Wahren <stefan.wahren@i2se.com> - 2018-12-01 02:00 +0100
            Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Matthias Luescher <lueschem@gmail.com> - 2018-12-01 22:50 +0100
              Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Stefan Wahren <stefan.wahren@i2se.com> - 2018-12-02 20:40 +0100
                Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1) Matthias Luescher <lueschem@gmail.com> - 2018-12-03 09:00 +0100
    Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2018-12-18 21:10 +0100
      Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Santiago Garcia Mantinan <manty@debian.org> - 2018-12-19 00:00 +0100
        Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2018-12-19 09:20 +0100
          Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Stefan Wahren <stefan.wahren@i2se.com> - 2018-12-19 12:10 +0100
            Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2018-12-19 12:30 +0100
              Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present Santiago Garcia Mantinan <manty@debian.org> - 2018-12-31 00:30 +0100
    Processed: Re: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no  longer present "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-12-18 21:10 +0100

#62396 — Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

Package: src:linux
Version: 4.18.10-2
Severity: important

Dear Maintainer,

The wlan0 interface of the Raspberry Pi 3 Model B is no longer present.
Downgrading to linux-image-4.17.0-3-arm64 4.17.15-1 restores it.

Under 4.17 it is present here:
/sys/devices/platform/soc/3f300000.sdhci/mmc_host/mmc1/mmc1:0001/mmc1:0001:1

Under 4.18 there is no longer any mmc1:* under
/sys/devices/platform/soc/3f300000.sdhci/mmc_host/mmc1/

-- Package-specific info:
** Version:
Linux version 4.18.0-2-arm64 (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-29)) #1 SMP Debian 4.18.10-2 (2018-10-07)

** Command line:
bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2709.boardrev=0xa02082 bcm2709.serial=0xc3d8c1f2 bcm2709.uart_clock=48000000 smsc95xx.macaddr=xx:xx:xx:xx:xx:xx vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=tty0 console=ttyS1,115200 root=/dev/mmcblk0p2 rw elevator=deadline fsck.repair=yes net.ifnames=0 rootwait

** Not tainted

** Kernel log:
[    5.578576] hctosys: unable to open rtc device (rtc0)
[    5.596621] Freeing unused kernel memory: 4928K
[    5.989258] usb_phy_generic phy: phy supply vcc not found, using dummy regulator
[    6.008474] i2c-bcm2835 3f805000.i2c: Could not read clock-frequency property
[    6.032557] sdhci: Secure Digital Host Controller Interface driver
[    6.041336] sdhci: Copyright(c) Pierre Ossman
[    6.051348] sdhci-pltfm: SDHCI platform and OF driver helper
[    6.060731] usbcore: registered new interface driver usbfs
[    6.062878] sdhci-iproc 3f300000.sdhci: allocated mmc-pwrseq
[    6.068897] usbcore: registered new interface driver hub
[    6.085153] usbcore: registered new device driver usb
[    6.106560] sdhost-bcm2835 3f202000.mmc: loaded - DMA enabled (>1)
[    6.114535] mmc1: SDHCI controller on 3f300000.sdhci [3f300000.sdhci] using PIO
[    6.151028] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not found, using dummy regulator
[    6.164524] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not found, using dummy regulator
[    6.228602] dwc2 3f980000.usb: dwc2_check_params: Invalid parameter lpm=1
[    6.232285] mmc0: host does not support reading read-only switch, assuming write-enable
[    6.238118] dwc2 3f980000.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1
[    6.254860] mmc0: new high speed SDHC card at address aaaa
[    6.264824] dwc2 3f980000.usb: dwc2_check_params: Invalid parameter besl=1
[    6.264833] dwc2 3f980000.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1
[    6.274839] mmcblk0: mmc0:aaaa SL08G 7.40 GiB 
[    6.305103] dwc2 3f980000.usb: DWC OTG Controller
[    6.305941]  mmcblk0: p1 p2
[    6.312508] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1
[    6.327511] dwc2 3f980000.usb: irq 41, io mem 0x3f980000
[    6.335689] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.18
[    6.349176] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.359177] usb usb1: Product: DWC OTG Controller
[    6.366590] usb usb1: Manufacturer: Linux 4.18.0-2-arm64 dwc2_hsotg
[    6.375647] usb usb1: SerialNumber: 3f980000.usb
[    6.383868] hub 1-0:1.0: USB hub found
[    6.390412] hub 1-0:1.0: 1 port detected
[    6.790550] usb 1-1: new high-speed USB device number 2 using dwc2
[    6.813969] random: fast init done
[    6.843897] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    7.014766] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    7.027991] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    7.038588] hub 1-1:1.0: USB hub found
[    7.044940] hub 1-1:1.0: 5 ports detected
[    7.338492] usb 1-1.1: new high-speed USB device number 3 using dwc2
[    7.446907] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    7.460223] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    7.662758] systemd[1]: System time before build time, advancing clock.
[    7.801709] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    7.831681] systemd[1]: Detected architecture arm64.
[    7.875595] systemd[1]: Set hostname to <upshot>.
[    8.660509] random: systemd: uninitialized urandom read (16 bytes read)
[    8.670602] systemd[1]: Listening on LVM2 metadata daemon socket.
[    8.694623] random: systemd: uninitialized urandom read (16 bytes read)
[    8.704055] systemd[1]: Reached target Remote File Systems.
[    8.726564] random: systemd: uninitialized urandom read (16 bytes read)
[    8.739535] systemd[1]: Created slice system-arpwatch.slice.
[    8.763459] systemd[1]: Listening on Journal Audit Socket.
[    8.794268] systemd[1]: Listening on Syslog Socket.
[    8.802248] random: crng init done
[    8.808830] random: 2 urandom warning(s) missed due to ratelimiting
[    8.832208] systemd[1]: Created slice system-getty.slice.
[    8.854641] systemd[1]: Reached target Swap.
[    9.259751] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    9.824049] systemd-journald[215]: Received request to flush runtime journal from PID 1
[   10.276263] bcm2835-rng 3f104000.rng: hwrng registered
[   10.286381] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[   10.698614] smsc95xx: unknown parameter 'macaddr' ignored
[   10.707134] smsc95xx v1.0.6
[   10.780465] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, xx:xx:xx:xx:xx:xx
[   10.799385] usbcore: registered new interface driver smsc95xx
[   10.844225] vc4_hdmi 3f902000.hdmi: ASoC: Failed to create component debugfs directory
[   10.863801] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping ok
[   10.873780] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name!
[   10.886995] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[   10.899735] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4])
[   10.910176] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[   10.919786] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[   10.930024] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[   10.940154] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[   10.974596] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
[   10.983587] checking generic (3eb75000 85400) vs hw (0 ffffffffffffffff)
[   10.983594] fb: switching to vc4drmfb from simple
[   10.990722] Console: switching to colour dummy device 80x25
[   10.998207] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0
[   11.004998] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[   11.011763] [drm] Driver supports precise vblank timestamp query.
[   11.038715] Console: switching to colour frame buffer device 90x30
[   11.069622] vc4-drm soc:gpu: fb0:  frame buffer device
[   11.443898] audit: type=1400 audit(1529665912.775:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/mdnsd" pid=260 comm="apparmor_parser"
[   11.462354] audit: type=1400 audit(1529665912.791:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/avahi-daemon" pid=261 comm="apparmor_parser"
[   11.489902] audit: type=1400 audit(1529665912.795:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/apt-cacher-ng" pid=263 comm="apparmor_parser"
[   11.531701] audit: type=1400 audit(1529665912.863:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="syslog-ng" pid=262 comm="apparmor_parser"
[   11.569099] audit: type=1400 audit(1529665912.899:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/identd" pid=264 comm="apparmor_parser"
[   11.597173] audit: type=1400 audit(1529665912.899:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="klogd" pid=267 comm="apparmor_parser"
[   11.640189] audit: type=1400 audit(1529665912.971:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/smbd" pid=265 comm="apparmor_parser"
[   11.670664] audit: type=1400 audit(1529665913.003:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/nscd" pid=268 comm="apparmor_parser"
[   11.716215] audit: type=1400 audit(1529665913.047:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="ping" pid=270 comm="apparmor_parser"
[   11.759280] audit: type=1400 audit(1529665913.091:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/dnsmasq" pid=271 comm="apparmor_parser"
[   13.126173] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   13.141374] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.760999] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   14.776410] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[   15.736603] tun: Universal TUN/TAP device driver, 1.6

** Model information
Device Tree model: Raspberry Pi 3 Model B Rev 1.2

** Loaded modules:
tun
ip6t_REJECT
nf_reject_ipv6
ip6table_filter
ip6_tables
ipt_REJECT
nf_reject_ipv4
xt_tcpudp
xt_comment
iptable_filter
nls_ascii
nls_cp437
vfat
fat
vc4
snd_soc_core
snd_pcm_dmaengine
snd_pcm
snd_timer
smsc95xx
snd
usbnet
soundcore
mii
cec
drm_kms_helper
drm
bcm2835_thermal
pwm_bcm2835
bcm2835_wdt
bcm2835_rng
rng_core
leds_gpio
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
aes_arm64
dwc2
udc_core
sdhci_iproc
sdhci_pltfm
usbcore
sdhci
usb_common
bcm2835
i2c_bcm2835
phy_generic

** Network interface configuration:
source-directory /etc/network/interfaces.d

** Network status:
*** IP interfaces and addresses:
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 pfifo_fast state UP group default qlen 1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::ba27:ebff:fed8:c1f2/64 scope link 
       valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:    4067      40    0    0    0     0          0         0     4067      40    0    0    0     0       0          0
  eth0:  166722     695    0    0    0     0          0         0   158268     582    0    0    0     0       0          0

*** Protocol statistics:
Ip:
    Forwarding: 2
    721 total packets received
    0 forwarded
    0 incoming packets discarded
    719 incoming packets delivered
    581 requests sent out
    80 dropped because of missing route
    4 reassemblies required
    2 packets reassembled ok
Icmp:
    1 ICMP messages received
    0 input ICMP message failed
    ICMP input histogram:
        destination unreachable: 1
    3 ICMP messages sent
    0 ICMP messages failed
    ICMP output histogram:
        destination unreachable: 3
IcmpMsg:
        InType3: 1
        OutType3: 3
Tcp:
    13 active connection openings
    1 passive connection openings
    3 failed connection attempts
    0 connection resets received
    3 connections established
    547 segments received
    423 segments sent out
    0 segments retransmitted
    0 bad segments received
    5 resets sent
Udp:
    168 packets received
    3 packets to unknown port received
    0 packet receive errors
    172 packets sent
    0 receive buffer errors
    0 send buffer errors
UdpLite:
TcpExt:
    4 TCP sockets finished time wait in fast timer
    11 delayed acks sent
    181 packet headers predicted
    85 acknowledgments not containing data payload received
    184 predicted acknowledgments
    1 connections reset due to unexpected data
    TCPRcvCoalesce: 11
    TCPAutoCorking: 11
    TCPOrigDataSent: 310
    TCPDelivered: 320
IpExt:
    InOctets: 170136
    OutOctets: 145416
    InNoECTPkts: 721


** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 4.18.0-2-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.18.0-2-arm64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.132
ii  kmod                                    25-1
ii  linux-base                              4.5

Versions of packages linux-image-4.18.0-2-arm64 recommends:
ii  apparmor             2.13-8
ii  firmware-linux-free  3.4
ii  irqbalance           1.3.0-0.1+b1

Versions of packages linux-image-4.18.0-2-arm64 suggests:
pn  debian-kernel-handbook  <none>
pn  linux-doc-4.18          <none>

Versions of packages linux-image-4.18.0-2-arm64 is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
ii  firmware-brcm80211        20180825+dfsg-1
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#62598 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

[Multipart message — attachments visible in raw view] — view raw

Hi Gunnar

I must say, I have not been able to find WiFi (not even a "firmware
> required" message). Could you help me find it, so it makes its way into
> raspi3-image-spec <https://github.com/debian/raspi3-image-spec>? Thanks -
> I'm closing this MR.
>

I have also struggled with WiFi. Could the "missing WiFi" issue be related
to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911443?
The WiFi (wlan0) reappears if I combine the 4.18 kernel with the device
tree binary of the 4.17 kernel.
The device tree change causing the absence of wlan0 might be this one:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/bcm2837-rpi-3-b.dts?h=v4.20-rc4&id=b1b8f45b3130dbd8704e5ea0d82b49b1d929498e

@Stefan and @Eric: As you are the experts here: Can you give us a clue why
the wlan0 interface disappears if we take the latest device tree binary
from 4.18 vanilla kernel?

Best regards
Matthias

>

[toc] | [prev] | [next] | [standalone]

#62599 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi,

> Matthias Luescher <lueschem@gmail.com> hat am 29. November 2018 um 22:18 geschrieben:
> 
> 
> Hi Gunnar
> 
> I must say, I have not been able to find WiFi (not even a "firmware
> > required" message). Could you help me find it, so it makes its way into
> > raspi3-image-spec <https://github.com/debian/raspi3-image-spec>? Thanks -
> > I'm closing this MR.
> >
> 
> I have also struggled with WiFi. Could the "missing WiFi" issue be related
> to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911443?
> The WiFi (wlan0) reappears if I combine the 4.18 kernel with the device
> tree binary of the 4.17 kernel.
> The device tree change causing the absence of wlan0 might be this one:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/bcm2837-rpi-3-b.dts?h=v4.20-rc4&id=b1b8f45b3130dbd8704e5ea0d82b49b1d929498e
> 
> @Stefan and @Eric: As you are the experts here: Can you give us a clue why
> the wlan0 interface disappears if we take the latest device tree binary
> from 4.18 vanilla kernel?

Which RPi 3 variant do you use (B or B+)?

Could you please provide a reduced kernel config?

Is armhf (32 bit) affected, too?

Stefan

> 
> Best regards
> Matthias
> 
> >

[toc] | [prev] | [next] | [standalone]

#62609 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

[Multipart message — attachments visible in raw view] — view raw

Hi Stefan

> Which RPi 3 variant do you use (B or B+)?

Today I have tested on the Raspberry Pi 3 B with arm64.

I was able to reproduce it also with kernel 4.19.5. wlan0 remains absent
with this newer kernel version.
Based on 4.19.5 I reverted commit b1b8f45b3130dbd8704e5ea0d82b49b1d929498e
and then wlan0 was back.

 > Could you please provide a reduced kernel config?

Here is more information:

Kernel configuration:
https://drive.google.com/open?id=1ZI3MeGB2fkYMsEjzGQYXUk2wqr0h9h7R

linux-image-4.19.5-v8_4.19.5-v8-1_arm64.deb (wlan0 is absent):
https://drive.google.com/open?id=1QCNZcpxeeCBGNb0dsZBBZD9i2Y1kCeib

dtb with b1b8f45b3130dbd8704e5ea0d82b49b1d929498e reverted (wlan0 is back):
https://drive.google.com/open?id=11O0c-StAUvV7IXFIs1UBlzeu-CTP3KVt

 > Is armhf (32 bit) affected, too?

I think so - but I did not test it yet.

Best regards
Matthias

[toc] | [prev] | [next] | [standalone]

#62614 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi Matthias,

> Matthias Luescher <lueschem@gmail.com> hat am 30. November 2018 um 22:20 geschrieben:
> 
> 
> Hi Stefan
> 
> > Which RPi 3 variant do you use (B or B+)?
> 
> Today I have tested on the Raspberry Pi 3 B with arm64.

i want to play safe. Could you please check the Rev of your 3 B board? You can find it on the upside of the PCB below the GPIO pin header (e.g. i have Rev 1.2).

> 
> I was able to reproduce it also with kernel 4.19.5. wlan0 remains absent
> with this newer kernel version.
> Based on 4.19.5 I reverted commit b1b8f45b3130dbd8704e5ea0d82b49b1d929498e
> and then wlan0 was back.

Btw the intention of this patch was to enable Wifi. Could you please provide a complete dmesg in case wlan0 is absent?

> 
>  > Could you please provide a reduced kernel config?
> 
> Here is more information:
> 
> Kernel configuration:
> https://drive.google.com/open?id=1ZI3MeGB2fkYMsEjzGQYXUk2wqr0h9h7R

Interesting SDHCI and BRCMFMAC are compiled as a module. Maybe this causes the issue. I tested today 4.20rc-1 with arm64/defconfig and wlan0 is always there. Could you please change your config to:

CONFIG_MMC_SDHCI_IPROC=y

and on the other side i will test your config.

Regards
Stefan

> 
> linux-image-4.19.5-v8_4.19.5-v8-1_arm64.deb (wlan0 is absent):
> https://drive.google.com/open?id=1QCNZcpxeeCBGNb0dsZBBZD9i2Y1kCeib
> 
> dtb with b1b8f45b3130dbd8704e5ea0d82b49b1d929498e reverted (wlan0 is back):
> https://drive.google.com/open?id=11O0c-StAUvV7IXFIs1UBlzeu-CTP3KVt
> 
>  > Is armhf (32 bit) affected, too?
> 
> I think so - but I did not test it yet.
> 
> Best regards
> Matthias

[toc] | [prev] | [next] | [standalone]

#62620 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

[Multipart message — attachments visible in raw view] — view raw

Hi Stefan

> i want to play safe. Could you please check the Rev of your 3 B board?
> You can find it on the upside of the PCB below the GPIO pin header (e.g.
i have Rev 1.2).

Mine is also a "Raspberry Pi 3 Model B V1.2".

> Could you please provide a complete dmesg in case wlan0 is absent?

Here is the dmesg without wlan0:
https://drive.google.com/open?id=1O-aYZreN_7ziHiVsxMc-zNoMAwKLB-UV

And here is one with wlan0:
https://drive.google.com/open?id=1rD2BcEbxjxrpyrXqRglkyS3t1VkCXJ6l

> Could you please change your config to:
> CONFIG_MMC_SDHCI_IPROC=y

This change does indeed make wlan0 appear! Unfortunately this is probably
not a viable solution for the (generic) arm64 Debian kernel.

Many thanks already for your great support!

Best regards
Matthias

[toc] | [prev] | [next] | [standalone]

#62631 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

Hi Matthias,

> Matthias Luescher <lueschem@gmail.com> hat am 1. Dezember 2018 um 22:38 geschrieben:
> 
> 
> Hi Stefan
> 
> > i want to play safe. Could you please check the Rev of your 3 B board?
> > You can find it on the upside of the PCB below the GPIO pin header (e.g.
> i have Rev 1.2).
> 
> Mine is also a "Raspberry Pi 3 Model B V1.2".
> 
> > Could you please provide a complete dmesg in case wlan0 is absent?
> 
> Here is the dmesg without wlan0:
> https://drive.google.com/open?id=1O-aYZreN_7ziHiVsxMc-zNoMAwKLB-UV
> 
> And here is one with wlan0:
> https://drive.google.com/open?id=1rD2BcEbxjxrpyrXqRglkyS3t1VkCXJ6l

very strange. Only in the case CONFIG_MMC_SDHCI_IPROC=m the power sequence seems to be active:

[    2.244705] sdhci-iproc 3f300000.sdhci: allocated mmc-pwrseq

So after fixing the polarity of the wifi-reset everything works as expected.

- reset-gpios = <&expgpio 1 GPIO_ACTIVE_HIGH>;
+ reset-gpios = <&expgpio 1 GPIO_ACTIVE_LOW>;

I think this should be acceptable as a stable fix for 4.19 LTS.

Stefan

> 
> > Could you please change your config to:
> > CONFIG_MMC_SDHCI_IPROC=y
> 
> This change does indeed make wlan0 appear! Unfortunately this is probably
> not a viable solution for the (generic) arm64 Debian kernel.
> 
> Many thanks already for your great support!
> 
> Best regards
> Matthias

[toc] | [prev] | [next] | [standalone]

#62635 — Bug#911443: raspi3-firmware | Add board-specific firmware files for RPi 3B+ WiFi (!1)

[Multipart message — attachments visible in raw view] — view raw

Hi Stefan


> So after fixing the polarity of the wifi-reset everything works as
> expected.
>
> - reset-gpios = <&expgpio 1 GPIO_ACTIVE_HIGH>;
> + reset-gpios = <&expgpio 1 GPIO_ACTIVE_LOW>;
>
> I think this should be acceptable as a stable fix for 4.19 LTS.
>

Great!

I applied the same change to arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts and
now it also works on the Raspberry Pi 3 B+.

Many thanks!!!

Best regards
Matthias

[toc] | [prev] | [next] | [standalone]

#62779

Control: tag 911443 + pending

I just added the commit from v4.20-rc7 that fixes this problem to the
Linux package git repository. It will be part of the next upload of
v4.19.x to unstable.

https://deb.li/lpFA

Best regards
Uwe

[toc] | [prev] | [next] | [standalone]

#62781 — Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

> I just added the commit from v4.20-rc7 that fixes this problem to the
> Linux package git repository. It will be part of the next upload of
> v4.19.x to unstable.

And could we have the patch I sent on #856505 to enable sound on this
machines applied as well?

I sent this to the lkml as you sugested but with little luck, it looks like
nobody cares.

For me it would be good to recover not only the wifi but also the audio.

Regards...
-- 
Manty/BestiaTester -> http://manty.net

[toc] | [prev] | [next] | [standalone]

#62786 — Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

Hello,

On Tue, Dec 18, 2018 at 11:49:33PM +0100, Santiago Garcia Mantinan wrote:
> > I just added the commit from v4.20-rc7 that fixes this problem to the
> > Linux package git repository. It will be part of the next upload of
> > v4.19.x to unstable.
> 
> And could we have the patch I sent on #856505 to enable sound on this
> machines applied as well?
> 
> I sent this to the lkml as you sugested but with little luck, it looks like
> nobody cares.

I didn't suggest to send to lkml, did I? You seem to have skipped
reading section 5 of the link I provided. You should address the mail to
the broadcom maintainers (see MAINTAINER file) and carbon copy
linux-arm-kernel@lists.infradead.org (which for reasons unknown to me
isn't listed in the broadcom entry).

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[toc] | [prev] | [next] | [standalone]

#62787 — Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

Hi Santiago,

Am 19.12.18 um 09:15 schrieb Uwe Kleine-König:
> Hello,
>
> On Tue, Dec 18, 2018 at 11:49:33PM +0100, Santiago Garcia Mantinan wrote:
>>> I just added the commit from v4.20-rc7 that fixes this problem to the
>>> Linux package git repository. It will be part of the next upload of
>>> v4.19.x to unstable.
>> And could we have the patch I sent on #856505 to enable sound on this
>> machines applied as well?
>>
>> I sent this to the lkml as you sugested but with little luck, it looks like
>> nobody cares.

i assume you are talking about:

arm: bcm2835-audio: Document the device tree node to enable
bcm2835-audio driver

This patch will not be accepted. For a explanation please refer to:

https://lkml.org/lkml/2018/10/16/1615

The proper solution is called:

staging: bcm2835-audio: Drop DT dependency

and is in linux-next since a week.

> I didn't suggest to send to lkml, did I? You seem to have skipped
> reading section 5 of the link I provided. You should address the mail to
> the broadcom maintainers (see MAINTAINER file) and carbon copy
> linux-arm-kernel@lists.infradead.org (which for reasons unknown to me
> isn't listed in the broadcom entry).

scripts/get_maintainers.pl will be your friend

Regards
Stefan

>
> Best regards
> Uwe
>

[toc] | [prev] | [next] | [standalone]

#62788 — Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

On Wed, Dec 19, 2018 at 12:05:27PM +0100, Stefan Wahren wrote:
> Am 19.12.18 um 09:15 schrieb Uwe Kleine-König:
> > Hello,
> >
> > On Tue, Dec 18, 2018 at 11:49:33PM +0100, Santiago Garcia Mantinan wrote:
> >>> I just added the commit from v4.20-rc7 that fixes this problem to the
> >>> Linux package git repository. It will be part of the next upload of
> >>> v4.19.x to unstable.
> >> And could we have the patch I sent on #856505 to enable sound on this
> >> machines applied as well?
> >>
> >> I sent this to the lkml as you sugested but with little luck, it looks like
> >> nobody cares.
> 
> i assume you are talking about:
> 
> arm: bcm2835-audio: Document the device tree node to enable
> bcm2835-audio driver
> 
> This patch will not be accepted. For a explanation please refer to:
> 
> https://lkml.org/lkml/2018/10/16/1615
> 
> The proper solution is called:
> 
> staging: bcm2835-audio: Drop DT dependency
> 
> and is in linux-next since a week.
> 
> > I didn't suggest to send to lkml, did I? You seem to have skipped
> > reading section 5 of the link I provided. You should address the mail to
> > the broadcom maintainers (see MAINTAINER file) and carbon copy
> > linux-arm-kernel@lists.infradead.org (which for reasons unknown to me
> > isn't listed in the broadcom entry).
> 
> scripts/get_maintainers.pl will be your friend

It doesn't list lakml for the dt file under discussion though[1]. That's
why I added here explicitly.

Best regards
Uwe

[1] scripts/get_maintainer.pl -f arch/arm/boot/dts/bcm283x.dtsi

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[toc] | [prev] | [next] | [standalone]

#62904 — Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

> > >> And could we have the patch I sent on #856505 to enable sound on this
> > >> machines applied as well?
> > 
> > i assume you are talking about:
> > 
> > arm: bcm2835-audio: Document the device tree node to enable
> > bcm2835-audio driver
> > 
> > This patch will not be accepted. For a explanation please refer to:
> > 
> > https://lkml.org/lkml/2018/10/16/1615
> > 
> > The proper solution is called:
> > 
> > staging: bcm2835-audio: Drop DT dependency
> > 
> > and is in linux-next since a week.

I've been playing with those patches for a while on 4.19, but those patches
won't work on their own, they depend on some other stuff that has been
commited as well. All that would mean a lot of changes.

So, it seems that 4.21 will have a solution for this through a lot of
changes and updates on the drivers, ...

But, if we are going to go with 4.19 I believe that the simple change I was
proposing which works as expected is going to give us audio on the pi and
only affects the pi, is a clean solution that would solve the problem.

I don't see the problem on applying this patch on Debian while upstream
evolves the drivers even more on 4.21 and next versions, all we do is enable
what is available on 4.19 like it was coded.

Any chance for this to happen?

Regards.
-- 
Manty/BestiaTester -> http://manty.net

[toc] | [prev] | [next] | [standalone]

#62780 — Processed: Re: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present

Processing control commands:

> tag 911443 + pending
Bug #911443 [src:linux] linux-image-4.18.0-2-arm64: wlan0 no longer present
Bug #915808 [src:linux] Current dtb for raspberry pi 3b doesn't allow wifi to be used
Added tag(s) pending.
Added tag(s) pending.

-- 
911443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911443
915808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915808
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web