Problems after CPU upgrade

mark-o-solo · 2017-05-21 16:43:49

Hello everyone,

Im not sure about the nature of my problems, so if this is really the right place to post, but Ill try anyway.

I recently upgraded my Lenovo t420's CPU from an i5 2520m to an i7 3632QM. This was possible thanks to coreboot. Now, there are a few problems with that as it seems. The worst of which is that my wifi is hard blocked accoding to rfkill. Ive tried all the forum threads I could find on this, but I cannot unblock it. On a live system, it works like a charm, so it must be arch related. Another problem is that my windows wont boot up, even from the installation usb, but I guess that ones for another forum.

Now my problem might be special, since apparently my chipset wasnt meant to be compatible with my new ivy bridge CPU, but any help is welcome.
Cheers

ewaller · 2017-05-21 17:02:11

First, clean your screen. We have a nice impression of your left thumb there...

What is the chipset for your WiFi?

mark-o-solo · 2017-05-21 17:06:29

Hi, yeah, sorry about that, I really use the sturdyness of my lappie to its full extent
The chipset of the lenovo is: Qualcomm® Gobia 3000 chipset, PCIe Mini Card
However, the wifi card was uprgaded to a killer 1103 with which I got over 30MB/s download prior to the CPU upgrade.

Last edited by mark-o-solo (2017-05-21 17:07:26)

ewaller · 2017-05-21 17:46:49

My thoughts are that the firmware for your WiFi card is not on the install media.
The Gobi chipset is not a WiFi chipset, it is Broadband Wireless chipset.
Killer 1103 seems to be a wireless-N. Did you replace the Broadband Wireless with a WiFi-n?
What are the Vendor and Product ID as provided by lspci -nn ?

mark-o-solo · 2017-05-21 18:09:10

lspci -nn gives:
02:00.0 Network controller [0280]: Qualcomm Atheros AR93xx Wireless Network Adapter [168c:0030] (rev 01)

And everything worked just before the upgrade. Also, it seems to change with whether or not I suspend, at some point, I mannaged to almost get it to work, meaning that it showed my home SSID in connman.
Is there a way to just override the hard block manually ?

ewaller · 2017-05-21 18:43:10

Not a hard block.

You changed both CPU and BIOS(1) at the same time if I understand correctly. Has it ever worked with the new BIOS?

(1) Here I use BIOS in the generic, often incorrect context. Does coreboot for your system provide UEFI? Did you try the intermediate step of using coreboot with your i5?

tom.ty89 · 2017-05-21 19:00:23

Seems like the error pops up before the real root is mounted? Though this can also happen if you use the fallback image, I think, did you configure the initramfs in a some very hardware-specific way? Maybe you should at least regen the image(s) with mkinitcpio?

mark-o-solo · 2017-05-21 19:28:49

UPDATE: as it seems, its only blocked after a hibernation/ suspend. This seems to be the exact same problem as here, however the workaround posted there does not work for me.

R00KIE · 2017-05-21 21:09:30

You could try to remove the driver before hibernation/ suspend and reload it afterwards and see if it helps. But that is only a workaround, you should check if with other distros or older kernels the problem is the same. If the problem stays you might want to contact the coreboot devs and inquire about this, maybe they need to fix something on their end.

loqs · 2017-05-21 22:13:16

From the link in post #8 what were the outputs of the commands in verification 1-3 and also the output of

$ systool -vm asus_nb_wmi

mark-o-solo · 2017-05-22 11:50:05

So the problem occurs both on the standard arch an on the ivybridge-ck kernel. According to lspci -vv, my driver isnt asus_nb_wmi, but ath9k.
The desired outputs:

lspci -nnk | grep -A2 0280                                                 god@god
02:00.0 Network controller [0280]: Qualcomm Atheros AR93xx Wireless Network Adapter [168c:0030] (rev 01)
	Subsystem: Bigfoot Networks, Inc. Killer Wireless-N 1103 Half-size Mini PCIe Card [AR9380] [1a56:2001]
	Kernel driver in use: ath9k

lsmod | grep -e ath9k                                                      god@god
ath9k                 131072  0
ath9k_common           32768  1 ath9k
ath9k_hw              442368  2 ath9k,ath9k_common
ath                    28672  3 ath9k_hw,ath9k,ath9k_common
mac80211              692224  1 ath9k
cfg80211              516096  4 mac80211,ath9k,ath,ath9k_common
led_class              16384  4 sdhci,input_leds,thinkpad_acpi,ath9k

rfkill list all                                                            god@god
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

systool -vm ath9k                                                          god@god
Module = "ath9k"

  Attributes:
    coresize            = "131072"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    blink               = "0"
    bt_ant_diversity    = "0"
    btcoex_enable       = "0"
    led_active_high     = "-1"
    nohwcrypt           = "0"
    ps_enable           = "0"

  Sections:
    .bss                = "0xffffffffa0932840"
    .data.unlikely      = "0xffffffffa09324d0"
    .data               = "0xffffffffa0932000"
    .exit.text          = "0xffffffffa092b655"
    .gnu.linkonce.this_module= "0xffffffffa0932500"
    .init.text          = "0xffffffffa09fc000"
    .note.gnu.build-id  = "0xffffffffa092c000"
    .rodata.str1.1      = "0xffffffffa092febf"
    .rodata.str1.8      = "0xffffffffa092f650"
    .rodata             = "0xffffffffa092c040"
    .smp_locks          = "0xffffffffa0930d70"
    .strtab             = "0xffffffffa0a01c38"
    .symtab             = "0xffffffffa09fd000"
    .text               = "0xffffffffa0916000"
    __bug_table         = "0xffffffffa09315c0"
    __mcount_loc        = "0xffffffffa0930e18"
    __param             = "0xfffff

loqs · 2017-05-22 14:23:12

The link you provided is only relevant if you have both drivers mentioned in use ath9k and asus_nb_wmi. The verification also assumes you have not made adjustments to force the loading of the asus_nb_wmi module.
Please provide the output of the following without changing the commands.

$ lsmod | grep -e ath9k -e asus
$ systool -vm asus_nb_wmi

mark-o-solo · 2017-06-06 21:42:04

Hi, sorry for my absence. The commands give:

~ » lsmod | grep -e ath9k -e asus                                              god@god
ath9k                 131072  0
ath9k_common           32768  1 ath9k
ath9k_hw              442368  2 ath9k,ath9k_common
ath                    28672  3 ath9k_hw,ath9k,ath9k_common
mac80211              692224  1 ath9k
cfg80211              516096  4 mac80211,ath9k,ath,ath9k_common
led_class              16384  4 sdhci,input_leds,thinkpad_acpi,ath9k

~ » systool -vm asus_nb_wmi                                                    god@god
Error opening module asus_nb_wmi

loqs · 2017-06-06 21:48:47

So this fails step 2 of the verification steps from the link you provided:

2) Check if the driver is loaded and if "asus_nb_wmi" driver is also in use :
Code:
lsmod | grep -e ath9k -e asus
(replace "ath9k" with whatever driver is used by your wireless)
Do you see the driver for your card, and "asus_nb_wmi" both in the above output?

The asus_nb_wmi module is not in the output of that command and the systool output also demonstrates the module is not loaded.
Edit:
Grammar link not linked

Last edited by loqs (2017-06-06 21:49:10)

mark-o-solo · 2017-06-26 07:55:52

But then, what can I do to fix the problem ?
If I unloaded my wifi module and reloaded it upon wake up from suspension, would that prevent the hard block ?

Arch Linux

#1 2017-05-21 16:43:49

Problems after CPU upgrade

#2 2017-05-21 17:02:11

Re: Problems after CPU upgrade

#3 2017-05-21 17:06:29

Re: Problems after CPU upgrade

#4 2017-05-21 17:46:49

Re: Problems after CPU upgrade

#5 2017-05-21 18:09:10

Re: Problems after CPU upgrade

#6 2017-05-21 18:43:10

Re: Problems after CPU upgrade

#7 2017-05-21 19:00:23

Re: Problems after CPU upgrade

#8 2017-05-21 19:28:49

Re: Problems after CPU upgrade

#9 2017-05-21 21:09:30

Re: Problems after CPU upgrade

#10 2017-05-21 22:13:16

Re: Problems after CPU upgrade

#11 2017-05-22 11:50:05

Re: Problems after CPU upgrade

#12 2017-05-22 14:23:12

Re: Problems after CPU upgrade

#13 2017-06-06 21:42:04

Re: Problems after CPU upgrade

#14 2017-06-06 21:48:47

Re: Problems after CPU upgrade

#15 2017-06-26 07:55:52

Re: Problems after CPU upgrade

Board footer