I made some modifications to the script was able to get my hands on a Dell Vostro, on this particular system the ASPM states were reporting differently,
I believe this has to do with laptop vendor , bios & pci-e. So I don't think we can use this as a reliable marker to signify when wifi is initializing. Alternatively there was a 6.59 second difference from the time the radio was initialized to wifi actually connect to an access point.
So far I found that Intel , Atheros , Realtek all report WLAN appropriately, I was able to get my hands on a older broadcom chipset which used the TG3 driver, that was really no help as dmesg didn't report much.
I may have to look into tailing the syslog to identify when the network starts up if using a broadcom chipset but thats going to require more time to look into. If anyone else has some ideas let me know.
I made some modifications to the script was able to get my hands on a Dell Vostro, on this particular system the ASPM states were reporting differently,
[ 13.984149] iwlwifi 0000:01:00.0: L1 Enabled; Disabling L0S
[ 13.990844] iwlwifi 0000:01:00.0: Radio type=0x1-0x2-0x0
I believe this has to do with laptop vendor , bios & pci-e. So I don't think we can use this as a reliable marker to signify when wifi is initializing. Alternatively there was a 6.59 second difference from the time the radio was initialized to wifi actually connect to an access point.
So far I found that Intel , Atheros , Realtek all report WLAN appropriately, I was able to get my hands on a older broadcom chipset which used the TG3 driver, that was really no help as dmesg didn't report much.
I may have to look into tailing the syslog to identify when the network starts up if using a broadcom chipset but thats going to require more time to look into. If anyone else has some ideas let me know.