USB Wireless AP dying loosing cameras
Posted: Wed May 11, 2016 7:37 am
Hello,
Just want to share what I did and why.
Problem: USB Wireless AP that listens to cameras and feeds the sygnal to zoneminder dies every week or so. System logs show that hostapd cannot start due to lack of the net interface that should get created for that AP.
Solution: remotely reboot the system so that the AP gets initialized (gets power) from he USB port. Unforunately Fedora 22 which I am using does not reboot the hardware effectively. It should do cold reboot, but it does not. So the USB Wireless AP is not present in the system.
Tweak:
Edit /etc/default/grub file adding to the GRUB_CMDLINE_LINUX="...reboot=p"
grub2-mkconfig -o /boot/grub2/grub.cfg
The kernel line parameter reboot=p[ci] causes a power cycle reset. Which I was aiming at thinking it might help solve my problem, and it did.
Other parameters available
/* reboot=b[ios] | s[mp] | t[riple] | k[bd] | e[fi] [, [w]arm | [c]old] | p[ci]
warm Don't set the cold reboot flag
cold Set the cold reboot flag
bios Reboot by jumping through the BIOS (only for X86_32)
smp Reboot by executing reset on BSP or other CPU (only for X86_32)
triple Force a triple fault (init)
kbd Use the keyboard controller. cold reset (default)
acpi Use the RESET_REG in the FADT
efi Use efi reset_system runtime service
pci Use the so-called "PCI reset register", CF9
force Avoid anything that could hang.
*/
regards
Lin Pro
Just want to share what I did and why.
Problem: USB Wireless AP that listens to cameras and feeds the sygnal to zoneminder dies every week or so. System logs show that hostapd cannot start due to lack of the net interface that should get created for that AP.
Solution: remotely reboot the system so that the AP gets initialized (gets power) from he USB port. Unforunately Fedora 22 which I am using does not reboot the hardware effectively. It should do cold reboot, but it does not. So the USB Wireless AP is not present in the system.
Tweak:
Edit /etc/default/grub file adding to the GRUB_CMDLINE_LINUX="...reboot=p"
grub2-mkconfig -o /boot/grub2/grub.cfg
The kernel line parameter reboot=p[ci] causes a power cycle reset. Which I was aiming at thinking it might help solve my problem, and it did.
Other parameters available
/* reboot=b[ios] | s[mp] | t[riple] | k[bd] | e[fi] [, [w]arm | [c]old] | p[ci]
warm Don't set the cold reboot flag
cold Set the cold reboot flag
bios Reboot by jumping through the BIOS (only for X86_32)
smp Reboot by executing reset on BSP or other CPU (only for X86_32)
triple Force a triple fault (init)
kbd Use the keyboard controller. cold reset (default)
acpi Use the RESET_REG in the FADT
efi Use efi reset_system runtime service
pci Use the so-called "PCI reset register", CF9
force Avoid anything that could hang.
*/
regards
Lin Pro