You are not logged in.

#1 2015-12-21 03:52:11

sleepy_cat
Member
From: CHN
Registered: 2015-12-07
Posts: 43

[SOLVED] Unsupported splx structure prompt on bootime

here is a problem with iwlwifi each time i boot up Arch:

# dmesg | grep splx
[    4.185893] iwlwifi 0000:07:00.0: Unsupported splx structure

and each time i want to connect a wifi via wifi-menu -o wlpXsY, i need to activate wifi module manually:

# ip link set wlpXsY up

how to make this command executed on bootime? or how to activate wifi on bootime? be kind :-)

Last edited by sleepy_cat (2015-12-25 01:56:00)


Things being equal, the simplest explanation tends to be the right.

Offline

#2 2015-12-21 05:22:07

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 28,296
Website

Re: [SOLVED] Unsupported splx structure prompt on bootime


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Online

#3 2015-12-21 12:13:38

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 7,630

Re: [SOLVED] Unsupported splx structure prompt on bootime

OP is already using netctl / wifi-menu  jasonwryan.

sleepy_cat, you have read "Wireless network configuration" and Netctl  wiki pages ?
please post full dmesg (or journalctl -b ) output .


Multi-init booting with apg Openrc and systemd coexisting
Automounting : not needed, i prefer pmount
Aur helpers : makepkg + my own local repo === rarely need them

Offline

#4 2015-12-21 14:16:37

sleepy_cat
Member
From: CHN
Registered: 2015-12-07
Posts: 43

Re: [SOLVED] Unsupported splx structure prompt on bootime

is OP stand for Original Poster?
i just skim the wireless page.
and have not read Netctl page.
here is the output of dmesg
here is the output of journalctl -b

Last edited by sleepy_cat (2015-12-21 14:24:28)


Things being equal, the simplest explanation tends to be the right.

Offline

#5 2015-12-21 16:25:23

tom.ty89
Member
Registered: 2012-11-15
Posts: 896

Re: [SOLVED] Unsupported splx structure prompt on bootime

(btw content of dmesg is in journalctl -b as well)

It seems to me that (at least) some NICs is just "down" after boot anyway. Usually the network agent should be able to bring them up automatically, so it might be a netctl issue too. Have you tried other agents like wpa_supplicant+networkd or NetworkManager?
Also I don't seem to see any netctl's log in the journal, can you attached a journal that is captured after you run wifi-menu?

FWIW the only issue I can see in the journal is two required firmware is missing. The reason is currently they are only available on iwlwifi's firmware git repo:
https://git.kernel.org/cgit/linux/kerne … .git/tree/
instead of the general one, which we used to build the linux-firmware package in Arch:
https://git.kernel.org/cgit/linux/kerne … .git/tree/
But this might not be the reason of your problem, and the splx error you see can be irrelevant and even harmless too.

Offline

#6 2015-12-21 17:07:36

tom.ty89
Member
Registered: 2012-11-15
Posts: 896

Re: [SOLVED] Unsupported splx structure prompt on bootime

In any case, if the UP/DOWN thing is the only problem you're experiencing, you can have a udev rule like this:

SUBSYSTEM=="net", KERNEL=="enp3s0", RUN+="/usr/bin/ip l set %k up"

Change the KERNEL match to your wifi adapter's name; %k will be expanded to the matched KERNEL value. Although it doesn't seem necessary, but I guess it's better you prefix the rule file with 81- or above, so that it will be run after 75-net-description.rules and 80-net-setup-link.rules in /usr/lib/udev/rules.d/. Put your file in /etc/udev/rules.d/ btw.

And surely you can try to form a systemd unit instead as well.

Last edited by tom.ty89 (2015-12-21 17:08:48)

Offline

#7 2015-12-21 17:08:48

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,002

Re: [SOLVED] Unsupported splx structure prompt on bootime

sleepy_cat wrote:

is OP stand for Original Poster?

yes smile


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#8 2015-12-22 01:35:25

sleepy_cat
Member
From: CHN
Registered: 2015-12-07
Posts: 43

Re: [SOLVED] Unsupported splx structure prompt on bootime

i've created 81-net-wifi.rules with following content:

SUBSYSTEM=="net", KERNEL=="wlp7s0", RUN+="/usr/bin/ip l set %k up"

but it stil not work, and i activate wlp7s0 manually:

$ sudo ip l set wlp7s0 up
RTNETLINK answers: Operation not possible due to RF-kill

but i haven't install rf-kill package, i don't know why it blocked, so i installed rfkill, and list states of wifi:

rfkill list all
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: yes
	Hard blocked: no

so i unblocked phy0 with sudo rfkill unblock 1, so phy0 as:

1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

and here seems that 81-net-wifi.rules no longer needed.

after reboot, the output of wifi-menu -o wlp7s0:

Scanning for networks... Could not read interface p2p-dev-wlp7s0 flags: No such device

// and wifi gui shown

but it often prompt me CONNECTING FAILED in wifi-menu gui.
and what that Could not read interface p2p-dev-wlp7s0 flags: No such device mean?
can i fix it? i have some kinds of OCD. forgive me :-(

----------------------------------------------------------------------
i've solved the wifi connection problem, but splx prompt still exists. but don't hurt.
make sure ip l | grep wlp output like:

3: wlpXsY: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000

not that

3: wlpXsY: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000

try to type sudo ip l set wlpXsY up or down to switch. i switched to down. but i don't know why that.
you may need rfkill package to check if physical module is blocked by rfkill list
if "Wireless LAN" is blocked, please simply try Fn + F12 to activate and check again. or type sudo rfkill unblock all

Last edited by sleepy_cat (2015-12-25 01:56:47)


Things being equal, the simplest explanation tends to be the right.

Offline

Board footer

Powered by FluxBB