Broadcom Network Controller issue when entering Xorg
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
Background
I am setting up an old HP Mini that is partitioned with windows xp that works fine.
Having installed Debian 9 on a partition, I am having issues with the wifi network device. However these issues only occur when I enter Xorg.
The issue
On boot, I enter a tty
and having setup basic wpa2
details in /etc/network/interfaces
, I can run the ifup wlan0
command as root and everything works fine (I can ping
, wget
, etc.).
This is my network config:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# Ethernet adapter
iface enp7s3 inet dhcp
# Wireless adapter
iface wlan0 inet dhcp
wpa-ssid *my SSID*
wpa-psk *my password*
and as I say, all is well in the tty
session.
The problem is when I enter the x-server with xinit
.
The ifup wlan0
command now yields:
Listening on LPF/wlan0/00:21:00:83:40:1c
Sending on LPF/wlan0/00:21:00:83:40:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlan0 interface.
so I can no longer connect when inside the x-server.
Some logs and outputs
The result from rfkill list 1
(since 1
is the number assigned to the device):
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
The relevant end lines from dmesg
(I added a comment from when I entered the x-server):
[ 125.794118] wlan0: authenticate with 00:11:50:0d:88:2e
[ 125.836300] wlan0: send auth to 00:11:50:0d:88:2e (try 1/3)
[ 125.853327] wlan0: authenticated
[ 125.853863] b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 125.853875] b43 ssb0:0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 125.853883] b43 ssb0:0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 125.856556] wlan0: associate with 00:11:50:0d:88:2e (try 1/3)
[ 125.858773] wlan0: RX AssocResp from 00:11:50:0d:88:2e (capab=0x411 status=0 aid=7)
[ 125.859529] wlan0: associated
[ 125.872908] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
#enter x-server here
[ 919.008115] b43-phy0: Radio hardware status changed to DISABLED
[ 919.132191] b43-phy0 ERROR: DMA RX reset timed out
[ 919.372068] b43-phy0 ERROR: DMA TX reset timed out
[ 919.612061] b43-phy0 ERROR: DMA TX reset timed out
[ 919.852114] b43-phy0 ERROR: DMA TX reset timed out
[ 920.092062] b43-phy0 ERROR: DMA TX reset timed out
[ 920.332094] b43-phy0 ERROR: DMA TX reset timed out
So clearly the x-server is causing the b43-phy0: Radio hardware status changed to DISABLED
, but I don't know how to go about debugging the source of this.
Another big problem is the result from lspci
.
The result from lspci -vs 00:02:0
when in the tty
(working):
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev 02)
Subsystem: Hewlett-Packard Company Broadcom 802.11a/b/g WLAN
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at fdffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
but in the x-server, the result from the same command is:
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
So this is where the error lies: !!! Unkown header type 7f
. Somehow the xinit
command which triggers the x-server mucks with the device causing this error.
Maybe a separate, conflicting driver is being activated that overrides the b43
one and this causes the error but again I do not know how to go about debugging this (networking is not my strong suit!).
What have I tried?
As a first punt (before I discovered the error in lspci
), I tired restarting the networking daemon:
systemctl restart networking
when in the x-server but to no avail.
I then worked out you can fiddle with pci
device settings which is what is most likely causing the issue.
So I tried in the /sys/bus/pci
directory to rescan the pci devices:
echo 1 > /sys/bus/pci/rescan
and also resetting the device:
echo 1 > /sys/bus/pci/devices/0000:02:00.0/reset
but no change.
I had another idea to remove the kernel driver (b43
) before running xinit
with:
modprobe -r b43
and then, once inside the x-server, re-adding it with:
modprobe -a b43
but again, the unknown header type
message prevails.
I appreciate anyone who takes the time to read all this and try and decipher my confusion.
At the very least, a possible solution could be to somehow disable the device or similar before starting the x-server and then re-enable it on the inside. This was my attention behind the modprobe
fix, but it had no affect on the logs which all returned the same thing once more.
networking drivers x-server pci
add a comment |Â
up vote
-1
down vote
favorite
Background
I am setting up an old HP Mini that is partitioned with windows xp that works fine.
Having installed Debian 9 on a partition, I am having issues with the wifi network device. However these issues only occur when I enter Xorg.
The issue
On boot, I enter a tty
and having setup basic wpa2
details in /etc/network/interfaces
, I can run the ifup wlan0
command as root and everything works fine (I can ping
, wget
, etc.).
This is my network config:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# Ethernet adapter
iface enp7s3 inet dhcp
# Wireless adapter
iface wlan0 inet dhcp
wpa-ssid *my SSID*
wpa-psk *my password*
and as I say, all is well in the tty
session.
The problem is when I enter the x-server with xinit
.
The ifup wlan0
command now yields:
Listening on LPF/wlan0/00:21:00:83:40:1c
Sending on LPF/wlan0/00:21:00:83:40:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlan0 interface.
so I can no longer connect when inside the x-server.
Some logs and outputs
The result from rfkill list 1
(since 1
is the number assigned to the device):
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
The relevant end lines from dmesg
(I added a comment from when I entered the x-server):
[ 125.794118] wlan0: authenticate with 00:11:50:0d:88:2e
[ 125.836300] wlan0: send auth to 00:11:50:0d:88:2e (try 1/3)
[ 125.853327] wlan0: authenticated
[ 125.853863] b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 125.853875] b43 ssb0:0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 125.853883] b43 ssb0:0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 125.856556] wlan0: associate with 00:11:50:0d:88:2e (try 1/3)
[ 125.858773] wlan0: RX AssocResp from 00:11:50:0d:88:2e (capab=0x411 status=0 aid=7)
[ 125.859529] wlan0: associated
[ 125.872908] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
#enter x-server here
[ 919.008115] b43-phy0: Radio hardware status changed to DISABLED
[ 919.132191] b43-phy0 ERROR: DMA RX reset timed out
[ 919.372068] b43-phy0 ERROR: DMA TX reset timed out
[ 919.612061] b43-phy0 ERROR: DMA TX reset timed out
[ 919.852114] b43-phy0 ERROR: DMA TX reset timed out
[ 920.092062] b43-phy0 ERROR: DMA TX reset timed out
[ 920.332094] b43-phy0 ERROR: DMA TX reset timed out
So clearly the x-server is causing the b43-phy0: Radio hardware status changed to DISABLED
, but I don't know how to go about debugging the source of this.
Another big problem is the result from lspci
.
The result from lspci -vs 00:02:0
when in the tty
(working):
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev 02)
Subsystem: Hewlett-Packard Company Broadcom 802.11a/b/g WLAN
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at fdffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
but in the x-server, the result from the same command is:
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
So this is where the error lies: !!! Unkown header type 7f
. Somehow the xinit
command which triggers the x-server mucks with the device causing this error.
Maybe a separate, conflicting driver is being activated that overrides the b43
one and this causes the error but again I do not know how to go about debugging this (networking is not my strong suit!).
What have I tried?
As a first punt (before I discovered the error in lspci
), I tired restarting the networking daemon:
systemctl restart networking
when in the x-server but to no avail.
I then worked out you can fiddle with pci
device settings which is what is most likely causing the issue.
So I tried in the /sys/bus/pci
directory to rescan the pci devices:
echo 1 > /sys/bus/pci/rescan
and also resetting the device:
echo 1 > /sys/bus/pci/devices/0000:02:00.0/reset
but no change.
I had another idea to remove the kernel driver (b43
) before running xinit
with:
modprobe -r b43
and then, once inside the x-server, re-adding it with:
modprobe -a b43
but again, the unknown header type
message prevails.
I appreciate anyone who takes the time to read all this and try and decipher my confusion.
At the very least, a possible solution could be to somehow disable the device or similar before starting the x-server and then re-enable it on the inside. This was my attention behind the modprobe
fix, but it had no affect on the logs which all returned the same thing once more.
networking drivers x-server pci
Your xinit may starts a network related application ( /etc/X11/Xsession.d ), which takes over your manually configured connection.
â Ipor Sircer
Sep 16 at 20:13
@IporSircer Yes it does (/etc/x11/Xsession
anddwm
is all that I start). I startXSession
because the x-server wouldn't start without it and it was in the system-widexinitrc
. Could you please elaborate what configurations it overrides, why, and in general why it is necessary? Thanks
â Joe Iddon
Sep 16 at 20:19
I used to have an HP mini, it has a wifi switch...also you cannot expect us to guess what is in your system. You are asking too broad questions, it is your job to chase and narrow them down. See our FAQ, our core mission is imparting Unix knowledge, not debugging complex user situations.
â Rui F Ribeiro
Sep 16 at 21:29
@RuiFRibeiro the physical switch is not the issue since I can see it's affect on rfkill. I think it is down to thevia
drivers though which I don't have installed (have been usingopenchrome
). so I will give that a shot. as for the question being broad, I completely accept your point, I am not familiar with this SE site as I am use to stack overflow where the more detail the better in my opinion.
â Joe Iddon
Sep 16 at 21:47
add a comment |Â
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Background
I am setting up an old HP Mini that is partitioned with windows xp that works fine.
Having installed Debian 9 on a partition, I am having issues with the wifi network device. However these issues only occur when I enter Xorg.
The issue
On boot, I enter a tty
and having setup basic wpa2
details in /etc/network/interfaces
, I can run the ifup wlan0
command as root and everything works fine (I can ping
, wget
, etc.).
This is my network config:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# Ethernet adapter
iface enp7s3 inet dhcp
# Wireless adapter
iface wlan0 inet dhcp
wpa-ssid *my SSID*
wpa-psk *my password*
and as I say, all is well in the tty
session.
The problem is when I enter the x-server with xinit
.
The ifup wlan0
command now yields:
Listening on LPF/wlan0/00:21:00:83:40:1c
Sending on LPF/wlan0/00:21:00:83:40:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlan0 interface.
so I can no longer connect when inside the x-server.
Some logs and outputs
The result from rfkill list 1
(since 1
is the number assigned to the device):
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
The relevant end lines from dmesg
(I added a comment from when I entered the x-server):
[ 125.794118] wlan0: authenticate with 00:11:50:0d:88:2e
[ 125.836300] wlan0: send auth to 00:11:50:0d:88:2e (try 1/3)
[ 125.853327] wlan0: authenticated
[ 125.853863] b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 125.853875] b43 ssb0:0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 125.853883] b43 ssb0:0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 125.856556] wlan0: associate with 00:11:50:0d:88:2e (try 1/3)
[ 125.858773] wlan0: RX AssocResp from 00:11:50:0d:88:2e (capab=0x411 status=0 aid=7)
[ 125.859529] wlan0: associated
[ 125.872908] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
#enter x-server here
[ 919.008115] b43-phy0: Radio hardware status changed to DISABLED
[ 919.132191] b43-phy0 ERROR: DMA RX reset timed out
[ 919.372068] b43-phy0 ERROR: DMA TX reset timed out
[ 919.612061] b43-phy0 ERROR: DMA TX reset timed out
[ 919.852114] b43-phy0 ERROR: DMA TX reset timed out
[ 920.092062] b43-phy0 ERROR: DMA TX reset timed out
[ 920.332094] b43-phy0 ERROR: DMA TX reset timed out
So clearly the x-server is causing the b43-phy0: Radio hardware status changed to DISABLED
, but I don't know how to go about debugging the source of this.
Another big problem is the result from lspci
.
The result from lspci -vs 00:02:0
when in the tty
(working):
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev 02)
Subsystem: Hewlett-Packard Company Broadcom 802.11a/b/g WLAN
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at fdffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
but in the x-server, the result from the same command is:
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
So this is where the error lies: !!! Unkown header type 7f
. Somehow the xinit
command which triggers the x-server mucks with the device causing this error.
Maybe a separate, conflicting driver is being activated that overrides the b43
one and this causes the error but again I do not know how to go about debugging this (networking is not my strong suit!).
What have I tried?
As a first punt (before I discovered the error in lspci
), I tired restarting the networking daemon:
systemctl restart networking
when in the x-server but to no avail.
I then worked out you can fiddle with pci
device settings which is what is most likely causing the issue.
So I tried in the /sys/bus/pci
directory to rescan the pci devices:
echo 1 > /sys/bus/pci/rescan
and also resetting the device:
echo 1 > /sys/bus/pci/devices/0000:02:00.0/reset
but no change.
I had another idea to remove the kernel driver (b43
) before running xinit
with:
modprobe -r b43
and then, once inside the x-server, re-adding it with:
modprobe -a b43
but again, the unknown header type
message prevails.
I appreciate anyone who takes the time to read all this and try and decipher my confusion.
At the very least, a possible solution could be to somehow disable the device or similar before starting the x-server and then re-enable it on the inside. This was my attention behind the modprobe
fix, but it had no affect on the logs which all returned the same thing once more.
networking drivers x-server pci
Background
I am setting up an old HP Mini that is partitioned with windows xp that works fine.
Having installed Debian 9 on a partition, I am having issues with the wifi network device. However these issues only occur when I enter Xorg.
The issue
On boot, I enter a tty
and having setup basic wpa2
details in /etc/network/interfaces
, I can run the ifup wlan0
command as root and everything works fine (I can ping
, wget
, etc.).
This is my network config:
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# Ethernet adapter
iface enp7s3 inet dhcp
# Wireless adapter
iface wlan0 inet dhcp
wpa-ssid *my SSID*
wpa-psk *my password*
and as I say, all is well in the tty
session.
The problem is when I enter the x-server with xinit
.
The ifup wlan0
command now yields:
Listening on LPF/wlan0/00:21:00:83:40:1c
Sending on LPF/wlan0/00:21:00:83:40:1c
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
send_packet: Network is down
dhclient.c:2315: Failed to send 300 byte long packet over wlan0 interface.
so I can no longer connect when inside the x-server.
Some logs and outputs
The result from rfkill list 1
(since 1
is the number assigned to the device):
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
The relevant end lines from dmesg
(I added a comment from when I entered the x-server):
[ 125.794118] wlan0: authenticate with 00:11:50:0d:88:2e
[ 125.836300] wlan0: send auth to 00:11:50:0d:88:2e (try 1/3)
[ 125.853327] wlan0: authenticated
[ 125.853863] b43 ssb0:0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 125.853875] b43 ssb0:0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 125.853883] b43 ssb0:0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 125.856556] wlan0: associate with 00:11:50:0d:88:2e (try 1/3)
[ 125.858773] wlan0: RX AssocResp from 00:11:50:0d:88:2e (capab=0x411 status=0 aid=7)
[ 125.859529] wlan0: associated
[ 125.872908] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
#enter x-server here
[ 919.008115] b43-phy0: Radio hardware status changed to DISABLED
[ 919.132191] b43-phy0 ERROR: DMA RX reset timed out
[ 919.372068] b43-phy0 ERROR: DMA TX reset timed out
[ 919.612061] b43-phy0 ERROR: DMA TX reset timed out
[ 919.852114] b43-phy0 ERROR: DMA TX reset timed out
[ 920.092062] b43-phy0 ERROR: DMA TX reset timed out
[ 920.332094] b43-phy0 ERROR: DMA TX reset timed out
So clearly the x-server is causing the b43-phy0: Radio hardware status changed to DISABLED
, but I don't know how to go about debugging the source of this.
Another big problem is the result from lspci
.
The result from lspci -vs 00:02:0
when in the tty
(working):
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev 02)
Subsystem: Hewlett-Packard Company Broadcom 802.11a/b/g WLAN
Flags: bus master, fast devsel, latency 0, IRQ 26
Memory at fdffc000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
but in the x-server, the result from the same command is:
02:00.0 Network controller: Broadcom Limited BCM4311 802.11a/b/g (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb
So this is where the error lies: !!! Unkown header type 7f
. Somehow the xinit
command which triggers the x-server mucks with the device causing this error.
Maybe a separate, conflicting driver is being activated that overrides the b43
one and this causes the error but again I do not know how to go about debugging this (networking is not my strong suit!).
What have I tried?
As a first punt (before I discovered the error in lspci
), I tired restarting the networking daemon:
systemctl restart networking
when in the x-server but to no avail.
I then worked out you can fiddle with pci
device settings which is what is most likely causing the issue.
So I tried in the /sys/bus/pci
directory to rescan the pci devices:
echo 1 > /sys/bus/pci/rescan
and also resetting the device:
echo 1 > /sys/bus/pci/devices/0000:02:00.0/reset
but no change.
I had another idea to remove the kernel driver (b43
) before running xinit
with:
modprobe -r b43
and then, once inside the x-server, re-adding it with:
modprobe -a b43
but again, the unknown header type
message prevails.
I appreciate anyone who takes the time to read all this and try and decipher my confusion.
At the very least, a possible solution could be to somehow disable the device or similar before starting the x-server and then re-enable it on the inside. This was my attention behind the modprobe
fix, but it had no affect on the logs which all returned the same thing once more.
networking drivers x-server pci
networking drivers x-server pci
edited Sep 16 at 21:30
Rui F Ribeiro
36.8k1273117
36.8k1273117
asked Sep 16 at 20:10
Joe Iddon
1082
1082
Your xinit may starts a network related application ( /etc/X11/Xsession.d ), which takes over your manually configured connection.
â Ipor Sircer
Sep 16 at 20:13
@IporSircer Yes it does (/etc/x11/Xsession
anddwm
is all that I start). I startXSession
because the x-server wouldn't start without it and it was in the system-widexinitrc
. Could you please elaborate what configurations it overrides, why, and in general why it is necessary? Thanks
â Joe Iddon
Sep 16 at 20:19
I used to have an HP mini, it has a wifi switch...also you cannot expect us to guess what is in your system. You are asking too broad questions, it is your job to chase and narrow them down. See our FAQ, our core mission is imparting Unix knowledge, not debugging complex user situations.
â Rui F Ribeiro
Sep 16 at 21:29
@RuiFRibeiro the physical switch is not the issue since I can see it's affect on rfkill. I think it is down to thevia
drivers though which I don't have installed (have been usingopenchrome
). so I will give that a shot. as for the question being broad, I completely accept your point, I am not familiar with this SE site as I am use to stack overflow where the more detail the better in my opinion.
â Joe Iddon
Sep 16 at 21:47
add a comment |Â
Your xinit may starts a network related application ( /etc/X11/Xsession.d ), which takes over your manually configured connection.
â Ipor Sircer
Sep 16 at 20:13
@IporSircer Yes it does (/etc/x11/Xsession
anddwm
is all that I start). I startXSession
because the x-server wouldn't start without it and it was in the system-widexinitrc
. Could you please elaborate what configurations it overrides, why, and in general why it is necessary? Thanks
â Joe Iddon
Sep 16 at 20:19
I used to have an HP mini, it has a wifi switch...also you cannot expect us to guess what is in your system. You are asking too broad questions, it is your job to chase and narrow them down. See our FAQ, our core mission is imparting Unix knowledge, not debugging complex user situations.
â Rui F Ribeiro
Sep 16 at 21:29
@RuiFRibeiro the physical switch is not the issue since I can see it's affect on rfkill. I think it is down to thevia
drivers though which I don't have installed (have been usingopenchrome
). so I will give that a shot. as for the question being broad, I completely accept your point, I am not familiar with this SE site as I am use to stack overflow where the more detail the better in my opinion.
â Joe Iddon
Sep 16 at 21:47
Your xinit may starts a network related application ( /etc/X11/Xsession.d ), which takes over your manually configured connection.
â Ipor Sircer
Sep 16 at 20:13
Your xinit may starts a network related application ( /etc/X11/Xsession.d ), which takes over your manually configured connection.
â Ipor Sircer
Sep 16 at 20:13
@IporSircer Yes it does (
/etc/x11/Xsession
and dwm
is all that I start). I start XSession
because the x-server wouldn't start without it and it was in the system-wide xinitrc
. Could you please elaborate what configurations it overrides, why, and in general why it is necessary? Thanksâ Joe Iddon
Sep 16 at 20:19
@IporSircer Yes it does (
/etc/x11/Xsession
and dwm
is all that I start). I start XSession
because the x-server wouldn't start without it and it was in the system-wide xinitrc
. Could you please elaborate what configurations it overrides, why, and in general why it is necessary? Thanksâ Joe Iddon
Sep 16 at 20:19
I used to have an HP mini, it has a wifi switch...also you cannot expect us to guess what is in your system. You are asking too broad questions, it is your job to chase and narrow them down. See our FAQ, our core mission is imparting Unix knowledge, not debugging complex user situations.
â Rui F Ribeiro
Sep 16 at 21:29
I used to have an HP mini, it has a wifi switch...also you cannot expect us to guess what is in your system. You are asking too broad questions, it is your job to chase and narrow them down. See our FAQ, our core mission is imparting Unix knowledge, not debugging complex user situations.
â Rui F Ribeiro
Sep 16 at 21:29
@RuiFRibeiro the physical switch is not the issue since I can see it's affect on rfkill. I think it is down to the
via
drivers though which I don't have installed (have been using openchrome
). so I will give that a shot. as for the question being broad, I completely accept your point, I am not familiar with this SE site as I am use to stack overflow where the more detail the better in my opinion.â Joe Iddon
Sep 16 at 21:47
@RuiFRibeiro the physical switch is not the issue since I can see it's affect on rfkill. I think it is down to the
via
drivers though which I don't have installed (have been using openchrome
). so I will give that a shot. as for the question being broad, I completely accept your point, I am not familiar with this SE site as I am use to stack overflow where the more detail the better in my opinion.â Joe Iddon
Sep 16 at 21:47
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f469434%2fbroadcom-network-controller-issue-when-entering-xorg%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Your xinit may starts a network related application ( /etc/X11/Xsession.d ), which takes over your manually configured connection.
â Ipor Sircer
Sep 16 at 20:13
@IporSircer Yes it does (
/etc/x11/Xsession
anddwm
is all that I start). I startXSession
because the x-server wouldn't start without it and it was in the system-widexinitrc
. Could you please elaborate what configurations it overrides, why, and in general why it is necessary? Thanksâ Joe Iddon
Sep 16 at 20:19
I used to have an HP mini, it has a wifi switch...also you cannot expect us to guess what is in your system. You are asking too broad questions, it is your job to chase and narrow them down. See our FAQ, our core mission is imparting Unix knowledge, not debugging complex user situations.
â Rui F Ribeiro
Sep 16 at 21:29
@RuiFRibeiro the physical switch is not the issue since I can see it's affect on rfkill. I think it is down to the
via
drivers though which I don't have installed (have been usingopenchrome
). so I will give that a shot. as for the question being broad, I completely accept your point, I am not familiar with this SE site as I am use to stack overflow where the more detail the better in my opinion.â Joe Iddon
Sep 16 at 21:47