FC28 Intel wireless-N 1000 stopped working - driver or hardware?
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 6 of 6
  1. #1
    Join Date
    Feb 2019
    Location
    AT
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    FC28 Intel wireless-N 1000 stopped working - driver or hardware?

    Hi!
    My wifi stopped working on a Lenovo T420 (cca. 9 years old). I run on FC28 currently, but it stopped working very suddenly under FC27 yesterday. i do not really use graphical tools, so pls i need command line help.
    for starting up the wifi i got the following script:

    #!/bin/bash
    sudo killall wpa_supplicant
    sudo killall dhclient

    sleep 2

    sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 &
    sudo dhclient


    [barb@galaxy ~]$ lspci -v -s 03:00.0
    03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak]
    Subsystem: Intel Corporation Centrino Wireless-N 1000 BGN
    Flags: bus master, fast devsel, latency 0, IRQ 29
    Memory at f3800000 (64-bit, non-prefetchable) [size=8K]
    Capabilities: <access denied>
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi


    If i add the driver in wpa_supplicant (-d iwlwifi), it tells me, driver unknown. if i run my script, i get the following:

    Successfully initialized wpa_supplicant
    Could not set interface wlan0 flags (UP): Input/output error
    nl80211: Could not set interface 'wlan0' UP
    nl80211: deinit ifname=wlan0 disabled_11b_rates=0
    wlan0: Failed to initialize driver interface
    RTNETLINK answers: Input/output error

    i re-installed all intel drivers (ipw2100 and iwl). Is there a way to tell, whether the hardware is broken? Are the drivers no longer supported? as it happened suddenly, i believe it might be hardware.

    i find in /var/log/messages yesterday around that time the following:

    Feb 11 10:25:48 localhost NetworkManager[1111]: <info> [1549877148.0361] wifi-nl80211: (wlan0): using nl80211 for WiFi device control
    Feb 11 10:25:48 localhost NetworkManager[1111]: <info> [1549877148.0389] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
    Feb 11 10:25:48 localhost NetworkManager[1111]: <info> [1549877148.0427] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', internal state 'external')
    Feb 11 10:25:48 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

    Feb 11 10:25:49 localhost NetworkManager[1111]: <info> [1549877149.0847] sup-iface[0x1bdec78,wlan0]: supports 5 scan SSIDs
    Feb 11 10:25:49 localhost NetworkManager[1111]: <info> [1549877149.0857] device (wlan0): supplicant interface state: starting -> ready
    Feb 11 10:25:49 localhost NetworkManager[1111]: <info> [1549877149.0857] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', internal state 'managed')
    Feb 11 10:25:49 localhost kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

    Feb 11 11:24:15 localhost kernel: wlan0: HW problem - can not stop rx aggregation for ac:22:05:cc:e8:a5 tid 0
    Feb 11 11:24:15 localhost kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
    Feb 11 11:24:15 localhost kernel: wlan0: HW problem - can not stop rx aggregation for ac:22:05:cc:e8:a5 tid 1
    Feb 11 11:24:15 localhost kernel: ieee80211 phy0: Hardware restart was requested
    Feb 11 11:24:15 localhost kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
    Feb 11 11:24:15 localhost kernel: wlan0: HW problem - can not stop rx aggregation for ac:22:05:cc:e8:a5 tid 4
    Feb 11 11:24:15 localhost kernel: iwlwifi 0000:03:00.0: Fw not loaded - dropping CMD: 18
    Feb 11 11:24:15 localhost kernel: wlan0: HW problem - can not stop rx aggregation for ac:22:05:cc:e8:a5 tid 7
    Feb 11 11:24:15 localhost kernel: WARNING: CPU: 0 PID: 4139 at drivers/net/wireless/intel/iwlwifi/dvm/../iwl-trans.h:1045 iwlagn_mac_flush+0x188/0x1b0 [iwldvm]

    Feb 11 11:25:42 localhost kernel: iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 8 [0x077f0001]
    Feb 11 11:25:42 localhost kernel: ieee80211 phy0: Hardware restart was requested
    Feb 11 11:25:42 localhost kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3
    Feb 11 11:25:42 localhost kernel: iwlwifi 0000:03:00.0: Radio type=0x0-0x0-0x3
    Feb 11 11:25:50 localhost kernel: wlan0: authenticate with ac:22:05:cc:e8:a5
    Feb 11 11:25:50 localhost kernel: wlan0: send auth to ac:22:05:cc:e8:a5 (try 1/3)
    Feb 11 11:25:50 localhost kernel: wlan0: authenticated
    Feb 11 11:25:50 localhost kernel: wlan0: associating with AP with corrupt probe response
    Feb 11 11:25:50 localhost kernel: wlan0: associate with ac:22:05:cc:e8:a5 (try 1/3)
    Feb 11 11:25:50 localhost kernel: wlan0: RX AssocResp from ac:22:05:cc:e8:a5 (capab=0x411 status=0 aid=1)
    Feb 11 11:25:50 localhost kernel: wlan0: associated
    Feb 11 11:25:50 localhost systemd-udevd[4963]: Process '/usr/sbin/crda' failed with exit code 255.
    Feb 11 11:25:50 localhost systemd-logind[1047]: Lid closed.
    Feb 11 11:25:50 localhost systemd-logind[1047]: Suspending...
    Feb 11 11:25:50 localhost NetworkManager[1111]: <info> [1549880750.1951] manager: sleep requested (sleeping: no enabled: yes)
    Feb 11 11:25:50 localhost kernel: wlan0: deauthenticating from ac:22:05:cc:e8:a5 by local choice (Reason: 3=DEAUTH_LEAVING)
    Feb 11 11:25:50 localhost NetworkManager[1111]: <info> [1549880750.1951] manager: sleeping...
    Feb 11 11:25:50 localhost NetworkManager[1111]: <info> [1549880750.1953] device (wlan0): state change: unavailable -> unmanaged (reason 'sleeping', internal state 'managed')
    Feb 11 11:25:50 localhost avahi-daemon[1049]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Feb 11 11:25:50 localhost avahi-daemon[1049]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.157.
    Feb 11 11:25:50 localhost avahi-daemon[1049]: Withdrawing address record for 192.168.0.157 on wlan0.
    Feb 11 11:25:50 localhost dhclient[2632]: receive_packet failed on wlan0: Network is down
    Feb 11 11:25:50 localhost NetworkManager[1111]: <info> [1549880750.2221] device (wlan0): set-hw-addr: reset MAC address to 8C:A9:82:AE:2F:48 (unmanage)
    Feb 11 11:25:50 localhost NetworkManager[1111]: <info> [1549880750.2236] manager: NetworkManager state is now ASLEEP

    I appreciate any help on this.
    brrb

  2. #2
    Join Date
    Feb 2019
    Location
    AT
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC28 Intel wireless-N 1000 stopped working - driver or hardware?

    Update on this issue:
    wireless started working again. no clue why, but i hope my old machine keeps up the good work.

  3. #3
    Join Date
    Dec 2012
    Location
    santa barbara, CA
    Posts
    1,177
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC28 Intel wireless-N 1000 stopped working - driver or hardware?

    are you sure there isn't a "button" or "slider" somewhere on the laptop, which turns off the wifi ?
    in one of my wife's old vaios, the submental engineer who designed it, put an invisible slider button on the edge of the laptop facing you, so every time she took the laptop to her bed, she would randomly lose wifi lol, until I intervened, and "extracted" the button for good.
    "monsters John ... monsters from the ID..."
    "ma vule teva maar gul nol naya"

  4. #4
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    7,156
    Mentioned
    6 Post(s)
    Tagged
    1 Thread(s)

    Re: FC28 Intel wireless-N 1000 stopped working - driver or hardware?

    Quote Originally Posted by bobx001
    are you sure there isn't a "button" or "slider" somewhere on the laptop, which turns off the wifi ?
    in one of my wife's old vaios, the submental engineer who designed it, put an invisible slider button on the edge of the laptop facing you, so every time she took the laptop to her bed, she would randomly lose wifi lol, until I intervened, and "extracted" the button for good.
    those sliders used to be required because of airport security and were common on laptops. okay the positioning probably could have been better but I guess they were trying to keep it discrete being VAIO.

    basically you'd slide the switch into the off position and show the security desk that wireless and bluetooth were disabled on the laptop so as not to interfere with in-flight systems. If you weren't able to do so, they were entitled to refuse boarding to a flight. these days, using the Fn Key is enough but if the battery is removable you have to do that. The battery issue stems from exploding lithium ion batteries, not the wireless interference risk.

  5. #5
    Join Date
    Feb 2019
    Location
    AT
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC28 Intel wireless-N 1000 stopped working - driver or hardware?

    Hi!
    i still have a hardware switch, but it i checked it of course before i wrote in the forum. so that was not the case. also the whole trouble story would imho not point at all (by behaviour) to the fact it could've been the switch.
    it still does a few funny things - i have to restart wireless twice - otherwise it cannot resolve nameservers. but i keep a bootable usb ready to check next time for hardware issues.

  6. #6
    Join Date
    Dec 2012
    Location
    santa barbara, CA
    Posts
    1,177
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: FC28 Intel wireless-N 1000 stopped working - driver or hardware?

    Quote Originally Posted by brrrb
    i have to restart wireless twice - otherwise it cannot resolve nameservers

    that sounds like the typical NetworkManager issue, which sometimes writes /etc/resolv.conf , and sometimes not, kind of a hit-n-miss.
    In my installations, I always do : systemctl disable NetworkManager ; systemctl enable network , then reboot, and then I go configure the stuff by hand, it makes much more sense for me, and I don't have "ghosts" in the machine.
    "monsters John ... monsters from the ID..."
    "ma vule teva maar gul nol naya"

Similar Threads

  1. Audio stopped working, FC28
    By yaxattax in forum Hardware & Laptops
    Replies: 15
    Last Post: 1st July 2018, 12:02 PM
  2. [SOLVED]
    VM hardware acceleration stopped working after yum upgrade
    By setthemfree in forum Hardware & Laptops
    Replies: 3
    Last Post: 16th February 2015, 06:38 PM
  3. Replies: 0
    Last Post: 28th May 2012, 03:02 PM
  4. Replies: 0
    Last Post: 16th November 2010, 02:58 PM
  5. Replies: 11
    Last Post: 5th December 2007, 03:35 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •