[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: WiFi on RPi

Ryutaroh Matsumoto dijo [Mon, Mar 01, 2021 at 11:57:47AM +0900]:
> Hi John,
> > Does anyone have wifi running on an RPi400 with Debian 64 Buster or
> > Bullseye?
> I'm using RPi4B 8GB model, which seems similar to RPi400.
> Without "module_blacklist=vc4" in the kernel command line
> (i.e. "cmdline.txt"), WiFi on my RPi4B does not work.

FWIW, I just popped today's daily image for Buster from
raspi.debian.net in my 8GB RPi4, and:

    /----buster ↓ ---------------------------------------------------------
    | Debian GNU/Linux 10 rpi4-20210226 ttyS1
    | rpi4-20210226 login: root
    | Linux rpi4-20210226 5.9.0-0.bpo.5-arm64 #1 SMP Debian 5.9.15-1~bpo10+1
    | (2020-12-31) aarch64
    | The programs included with the Debian GNU/Linux system are free
    | software;
    | the exact distribution terms for each program are described in the
    | individual files in /usr/share/doc/*/copyright.
    | Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    | permitted by applicable law.
    | root@rpi4-20210226:~# ip l
    | 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    |     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    | 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    |     link/ether dc:a6:32:ae:8d:58 brd ff:ff:ff:ff:ff:ff
    | 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    |     link/ether dc:a6:32:ae:8d:59 brd ff:ff:ff:ff:ff:ff

For some reason I canot set up to debug right now, the serial console
gets garbled up (wrong baud rate or so?) when booting with Bullseye,
but connecting a HDMI monitor, it also works -- screenshot attached

Oh -- And I have just realized no image builds have happened in the
last week (since I did some movements to my build server). I'll try to
fix it and get the builds started  again today (but I'm quite busy,
so.... lets hope it's an easy fix!)

Reply to: