Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
Hi! I no longer have a working pi3 around, but last time I checked, all the way through the 5.X series... it was ok, and this was at least until 5.8.X or 5.9.X. So, I'd say this is solved, at least for the Pi 3 b, which was the one I used to have around and which was presenting this on 4.19. I believe you can close this. Regards. El dom, 2 may 2021 a las 9:32, Salvatore Bonaccorso () escribió: > > Control: tags -1 + moreinfo > > On Mon, Dec 31, 2018 at 12:15:35AM +0100, Santiago Garcia Mantinan wrote: > > > > >> 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? > > What is the status of this bug? has the issue been fixed upstream? > Does it happen still with a recent kernel from unstable or > buster-backports? > > Regards, > Salvatore > -- Manty/BestiaTester -> http://manty.net
Bug#856505: Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
Control: tags -1 + moreinfo On Mon, Dec 31, 2018 at 12:15:35AM +0100, Santiago Garcia Mantinan wrote: > > > >> 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? What is the status of this bug? has the issue been fixed upstream? Does it happen still with a recent kernel from unstable or buster-backports? Regards, Salvatore
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
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-ker...@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/ |
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-ker...@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 >
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-ker...@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/ |
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
Bug#911443: linux-image-4.18.0-2-arm64: wlan0 no longer present
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
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/3f30.sdhci/mmc_host/mmc1/mmc1:0001/mmc1:0001:1 Under 4.18 there is no longer any mmc1:* under /sys/devices/platform/soc/3f30.sdhci/mmc_host/mmc1/ -- Package-specific info: ** Version: Linux version 4.18.0-2-arm64 (debian-ker...@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=4800 smsc95xx.macaddr=xx:xx:xx:xx:xx:xx vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 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 3f30.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 3f30.sdhci [3f30.sdhci] using PIO [6.151028] dwc2 3f98.usb: 3f98.usb supply vusb_d not found, using dummy regulator [6.164524] dwc2 3f98.usb: 3f98.usb supply vusb_a not found, using dummy regulator [6.228602] dwc2 3f98.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 3f98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [6.254860] mmc0: new high speed SDHC card at address [6.264824] dwc2 3f98.usb: dwc2_check_params: Invalid parameter besl=1 [6.264833] dwc2 3f98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [6.274839] mmcblk0: mmc0: SL08G 7.40 GiB [6.305103] dwc2 3f98.usb: DWC OTG Controller [6.305941] mmcblk0: p1 p2 [6.312508] dwc2 3f98.usb: new USB bus registered, assigned bus number 1 [6.327511] dwc2 3f98.usb: irq 41, io mem 0x3f98 [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: 3f98.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 . [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 [
