Quantcast
Channel: Intel Communities: Message List
Viewing all articles
Browse latest Browse all 17366

Re: Failed to start Hostapd on boot

$
0
0

I want to use edison as AP with hostapd. I notice that on a fresh install, if I add hostapd at boot with "systemctl enable hostapd", it works fine.

In my installation, I've some configurations maybe I've some conflict, then if I add hostapd at boot with "systemctl enable hostapd", when I reboot it doesn't work.

 

I have:

[  OK  ] Started Network Name Resolution.

[  OK  ] Started Hostap daemon service.

[  OK  ] Started Login Service.

[  OK  ] Found device /sys/subsystem/net/devices/wlan0.

         Starting WPA supplicant service...

         Starting Load/Save RF Kill Switch Status of rfkill3...

         Starting Load/Save RF Kill Switch Status of rfkill4...

         Starting udhcpd daemon for hostapd...

[  OK  ] Started Load/Save RF Kill Switch Status of rfkill3.

[  OK  ] Started Load/Save RF Kill Switch Status of rfkill4.

         Starting Daemon to receive the wpa_supplicant event...

[  OK  ] Started Daemon to receive the wpa_supplicant event.

[  OK  ] Started WPA supplicant service.

[  OK  ] Started udhcpd daemon for hostapd.

         Stopping udhcpd daemon for hostapd...

[  OK  ] Stopped udhcpd daemon for hostapd.

         Stopping Hostap daemon service...

         Stopping Daemon to receive the wpa_supplicant event...

[  OK  ] Stopped Daemon to receive the wpa_supplicant event.

         Starting Load/Save RF Kill Switch Status of rfkill6...

[  OK  ] Stopped Hostap daemon service.

[  OK  ] Started Load/Save RF Kill Switch Status of rfkill6.

         Starting Load/Save RF Kill Switch Status of rfkill5...

         Expecting device /sys/subsystem/net/devices/wlan0...

[  OK  ] Started Load/Save RF Kill Switch Status of rfkill5.

[  OK  ] Found device /sys/subsystem/net/devices/wlan0.

         Starting Daemon to receive the wpa_supplicant event...

[  OK  ] Started Daemon to receive the wpa_supplicant event.

 

 

If I type "systemctl status hostapd" the result is:

● hostapd.service - Hostap daemon service

   Loaded: loaded (/lib/systemd/system/hostapd.service; enabled)

   Active: failed (Result: exit-code) since Wed 2015-01-14 15:43:09 UTC; 18s ago

  Process: 272 ExecStopPost=/sbin/modprobe bcm4334x (code=exited, status=0/SUCCESS)

  Process: 265 ExecStopPost=/sbin/modprobe -r bcm4334x (code=exited, status=0/SUCCESS)

  Process: 246 ExecStart=/usr/sbin/hostapd /etc/hostapd/hostapd.conf (code=exited, status=1/FAILURE)

  Process: 224 ExecStartPre=/sbin/modprobe bcm4334x op_mode=2 (code=exited, status=0/SUCCESS)

  Process: 199 ExecStartPre=/sbin/modprobe -r bcm4334x (code=exited, status=0/SUCCESS)

Main PID: 246 (code=exited, status=1/FAILURE)

 

 

Jan 14 15:43:06 wiicom_edison systemd[1]: Started Hostap daemon service.

Jan 14 15:43:08 wiicom_edison systemd[1]: hostapd.service: main process exited, code=exited, status=1/FAILURE

Jan 14 15:43:08 wiicom_edison systemd[1]: Stopping Hostap daemon service...

Jan 14 15:43:08 wiicom_edison hostapd[246]: Configuration file: /etc/hostapd/hostapd.conf

Jan 14 15:43:08 wiicom_edison hostapd[246]: Could not set channel for kernel driver

Jan 14 15:43:08 wiicom_edison hostapd[246]: wlan0: Unable to setup interface.

Jan 14 15:43:08 wiicom_edison hostapd[246]: wlan0: Could not connect to kernel driver

Jan 14 15:43:08 wiicom_edison hostapd[246]: hostapd_free_hapd_data: Interface wlan0 wasn't started

Jan 14 15:43:09 wiicom_edison systemd[1]: Stopped Hostap daemon service.

Jan 14 15:43:09 wiicom_edison systemd[1]: Unit hostapd.service entered failed state.

 

 

I don't know where can be te problem....


Viewing all articles
Browse latest Browse all 17366

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>