Here are the log files from a Lenovo laptop I have Peppermint 7 running on. It has an older 2.4GHz (802.11b/g) card inside and still fails using the “flush” option. The Raspberry PI3B runs perfectly using the “flush” option. Dan Dan Kosek daniel.kosek@xxxxxxxxx
Attachment:
auth.log
Description: Binary data
Attachment:
dpkg.log
Description: Binary data
Attachment:
kern.log
Description: Binary data
Attachment:
syslog
Description: Binary data
> On Aug 7, 2018, at 5:41 PM, Dan Kosek <daniel.kosek@xxxxxxxxx> wrote: > > Here are the Raspberry Pi 3B log files. > > I will be sending the one from the test laptop I have later this evening. > > Dan > > Dan Kosek > daniel.kosek@xxxxxxxxx > <Raspberry Pi 3B Log Files.zip> > >> On Aug 6, 2018, at 5:17 AM, Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote: >> >> + linux-wireless >> >> On 8/5/2018 4:59 AM, Dan Kosek wrote: >>> Arend, >>> >>> Thank you for getting back to me. Adding the “flush” variable to the command fixes the issue on both systems. Wow is the single channel scan fast with the flush. Is appears the full scan (all channels) is faster with the flush option as well. >> >> Glad it worked for you. >> >>> I have attached my bash logs. >>> >>> No I have don’t have kernel logfiles. >>> >>> I would be glad to collect the kernel log files for you tomorrow. >> >> There is not really an issue here so no need. >> >>> Can you provide me some instructions or a reference and I will forward them. >>> (I am a wireless engineer my trade and learning to program now.) >> >> Welcome to the dark side :-p Getting the logs depends on you linux distro, but using dmesg tends to work on most of them. >> >> Regards, >> Arend >> >
