for some time now (almost a year), when the pi is not connected to the internet, the console is flooded with a brcfmac error, which makes it very difficult to do anything (such as manually enter wifi credentials to connect to the internet).
Today I found that if you add loglevel=3 to /boot/cmdline.txt, it gets rid of these flooding messages. It probably suppresses other messages too that might be helpful, but atleast it stops the flood!
Maybe there is another more robust solution for the future, but I am pleased today to not see those warnings again.
for some time now (almost a year), when the pi is not connected to the internet, the console is flooded with a brcfmac error, which makes it very difficult to do anything (such as manually enter wifi credentials to connect to the internet).
Today I found that if you add loglevel=3 to /boot/cmdline.txt, it gets rid of these flooding messages. It probably suppresses other messages too that might be helpful, but atleast it stops the flood!
Maybe there is another more robust solution for the future, but I am pleased today to not see those warnings again.
cc @glyph
I implemented this loglevel solution on my Pi a year or two ago but never documented it anywhere.
A level of 3 (KERN_ERR) seems reasonable to me. Here is some background on Linux kernel log levels.
Hahaha I know that flood very well :')
I implemented this loglevel solution on my Pi a year or two ago but never documented it anywhere.
A level of 3 (`KERN_ERR`) seems reasonable to me. Here is some background on [Linux kernel log levels](https://linuxconfig.org/introduction-to-the-linux-kernel-log-levels).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
for some time now (almost a year), when the pi is not connected to the internet, the console is flooded with a brcfmac error, which makes it very difficult to do anything (such as manually enter wifi credentials to connect to the internet).
Today I found that if you add loglevel=3 to /boot/cmdline.txt, it gets rid of these flooding messages. It probably suppresses other messages too that might be helpful, but atleast it stops the flood!
Maybe there is another more robust solution for the future, but I am pleased today to not see those warnings again.
cc @glyph
Hahaha I know that flood very well :')
I implemented this loglevel solution on my Pi a year or two ago but never documented it anywhere.
A level of 3 (
KERN_ERR) seems reasonable to me. Here is some background on Linux kernel log levels.