You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I can't get rid of a message that flood my terminal (MidnightBSD without X server), concerning problem with wifi connection.
This message is " ath0: ath_legacy_rx_tasklet: sc_inreset_cnt > 0: skipping "
I know I have a problem in my config with my wlan0 interface (no carrier), but I would first prevent those console logs to appear on the screen.
I tried to comment out every lines in /etc/syslog.conf that were redirected to /dev/console
reboot x times
But the messages are still there... I don't know where they are coming from.
I know the problem must be freeBSD related (not only MidnightBSD) but didn't find a way to solve that while searching on the web.
The text was updated successfully, but these errors were encountered:
Thank you. Informations in that thread are actually interestings.
I worked around the problem first by configuring my wifi connection (in fact commands like "/etc/rc.d/netif stop" or "ifconfig wlan0 down" did the trick to stop messages from appearing on the screen)
I still have problems connecting other machine (obviously because of bad ipfw parameters), but that's ok for now.
Hi.
I can't get rid of a message that flood my terminal (MidnightBSD without X server), concerning problem with wifi connection.
This message is " ath0: ath_legacy_rx_tasklet: sc_inreset_cnt > 0: skipping "
I know I have a problem in my config with my wlan0 interface (no carrier), but I would first prevent those console logs to appear on the screen.
I tried to comment out every lines in /etc/syslog.conf that were redirected to /dev/console
reboot x times
But the messages are still there... I don't know where they are coming from.
I know the problem must be freeBSD related (not only MidnightBSD) but didn't find a way to solve that while searching on the web.
The text was updated successfully, but these errors were encountered: