Moderator: Forum moderators
Woof woof!
I was playing with Xenial on my Thinkpad L440 and easily settled connection with iwlwifi driver (Intel Centrino Advanced-N 6235 card) but, after created savefile and rebooted, I noticed that WiFi interface is not starting up automatically. I need everytime to manually setup wireless wizard. Do you know how can I solve this?
What version of Xenialpup 7.5?
32bit or 64bit?
Have you run Quickpet->Info->Xenialpup updates
Saved and rebooted so the new changes are now being used?
What network connection program are you using?
You are selecting the normal boot entry in the boot loader menu?
What device is Xenialpup installed on?
USB drive, internal hard drive, CD/DVD??
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
64 bit
bigpup wrote: Mon Nov 02, 2020 1:51 pmyou run Quickpet->Info->Xenialpup updates
Saved and rebooted so the new changes are now being used?
Not yet, in fact now I remember I have forgotten to do this.
Update: I just installed updates, but same issue
Network wizard
bigpup wrote: Mon Nov 02, 2020 1:51 pmYou are selecting the normal boot entry in the boot loader menu?
What device is Xenialpup installed on?
USB drive, internal hard drive, CD/DVD??
On USB drive, I'm waiting for new dvd burner since this I have is faulty
Some progress in troubleshooting wireless issue at bootup with savefile. I checked and I noticed that an APIPA address (169.254.xxx.xxx) is assigned automatically (issues with dhcp?)
Yes. It's probably a timing problem. Your Internet connection software is trying to acquire an IP address via DHCP before your Ethernet adapter has fully initialized.
So it is the ethernet adapter that is interfering with my wifi?
Sorry. I should have said "WiFi adapter".
dmesg says:
Code: Select all
Intel(R) Wireless WiFi driver for Linux
Copyright(c) 2003- 2015 Intel Corporation
iwlwifi 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
iwlwifi 0000:02:00.0: loaded firmware version 18.168.6.1 op_mode iwldvm
iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUG disabled
iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled
iwlwifi 0000:02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
iwlwifi 0000:02:00.0: Detected Intel(R) Centrino(R) Advanced-N 6235 AGN, REV=0xB0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
input: PC Speaker as /devices/platform/pcspkr/input/input15
Error: Driver 'pcspkr' is already registered, aborting...
Bluetooth: Core ver 2.22
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b398)
uvcvideo 3-12:1.0: Entity type for entity Processing 2 was not initialized!
uvcvideo 3-12:1.0: Entity type for entity Camera 1 was not initialized!
uvcvideo 3-12:1.0: Entity type for entity Extension 4 was not initialized!
input: Integrated Camera as /devices/pci0000:00/0000:00:14.0/usb3/3-12/3-12:1.0/input/input16
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
Console: switching to colour frame buffer device 170x48
snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input17
input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input18
input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input19
e1000e: eth0 NIC Link is Down
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
e1000e: eth0 NIC Link is Down
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
e1000e: eth0 NIC Link is Down
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
ip_tables: (C) 2000-2006 Netfilter Core Team
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
iwlwifi 0000:02:00.0: Radio type=0x2-0x1-0x0
wlan0: authenticate with f0:92:1c:f9:66:e9
wlan0: No basic rates, using min rate instead
wlan0: send auth to f0:92:1c:f9:66:e9 (try 1/3)
wlan0: authenticated
wlan0: associate with f0:92:1c:f9:66:e9 (try 1/3)
wlan0: RX AssocResp from f0:92:1c:f9:66:e9 (capab=0x421 status=0 aid=1)
wlan0: associated
Dingo,
The latest version of the network wizard, network_wizard-2.1.3, waits longer for the wired ethernet adapter. It is available at:
viewtopic.php?p=2241#p2241.
Please try it to resolve the timing issue. If it doesn't, please tell me.
You may have discovered that your wifi device is claimed by multiple drivers. The network wizard might not account for that correctly. I recently updated the simple_network_setup (SNS) tool to handle that situation. So, you could try that tool, simple_network_setup-2.4, available at the same posting.
Richard
rerwin wrote: Sun Nov 15, 2020 7:46 pmDingo,
The latest version of the network wizard, network_wizard-2.1.3, waits longer for the wired ethernet adapter. It is available at:
viewtopic.php?p=2241#p2241.Please try it to resolve the timing issue. If it doesn't, please tell me.
You may have discovered that your wifi device is claimed by multiple drivers. The network wizard might not account for that correctly. I recently updated the simple_network_setup (SNS) tool to handle that situation. So, you could try that tool, simple_network_setup-2.4, available at the same posting.
Richard
network_wizard-2.1.3 failed to solve my issue
While it seems that simple_network_setup-2.4 solved issue. At least, I installed, settled connection, rebooted and at next boot Wlan0 interface was live and working
Dingo wrote: Mon Nov 16, 2020 12:06 pmnetwork_wizard-2.1.3 failed to solve my issue
While it seems that simple_network_setup-2.4 solved issue. At least, I installed, settled connection, rebooted and at next boot Wlan0 interface was live and working
Thank you for this info. It seems that SNS is a success for this problem.
Are you interested in pursuing a fix for network_wizard? We could start by your adding to /usr/local/network-wizard/rc.network, "set -x; exec >&2 #DEBUG" just after the history comments and sending me the /tmp/bootsysint.log and /tmp/xerrs.log, or a pdiag tarball.
My focus has been on perfecting SNS and frisbee. Do you think it would be worthwhile to fix NetWiz?
Richard
rerwin wrote: Mon Nov 16, 2020 5:35 pmDingo wrote: Mon Nov 16, 2020 12:06 pmnetwork_wizard-2.1.3 failed to solve my issue
While it seems that simple_network_setup-2.4 solved issue. At least, I installed, settled connection, rebooted and at next boot Wlan0 interface was live and working
Thank you for this info. It seems that SNS is a success for this problem.
Are you interested in pursuing a fix for network_wizard? We could start by your adding "set -x; exec >&2 #DEBUG" just after the history comments and sending me the /tmp/bootsysint.log and /tmp/xerrs.log, or a pdiag tarball.
My focus has been on perfecting SNS and frisbee. Do you think it would be worthwhile to fix NetWiz?
Richard
Surely. I'm available for testing. Where precisely should I add the line
set -x; exec> & 2 #DEBUG ?
Duh! I remembered as I was eating lunch, that I did not say where to put the line. It's in /usr/local/network-wizard/rc.network.
set -x; exec >&2 #DEBUG
The"#DEBUG" is only to make it easy to find, to remove it or comment it out. I wouldn't put spaces in ">&2", but maybe it would be OK. It puts the trace data into the error log so it will appear in xerrs.log as well as in bootsysinit.log.
rerwin wrote: Mon Nov 16, 2020 7:05 pmDuh! I remembered as I was eating lunch, that I did not say where to put the line. It's in /usr/local/network-wizard/rc.network.
set -x; exec >&2 #DEBUGThe"#DEBUG" is only to make it easy to find, to remove it or comment it out. I wouldn't put spaces in ">&2", but maybe it would be OK. It puts the trace data into the error log so it will appear in xerrs.log as well as in bootsysinit.log.
this is the pdiag tarball, should I add also
bootsysinit.log
xerrs.log ?
Dingo wrote: Tue Nov 17, 2020 11:05 amthis is the pdiag tarball, should I add also
bootsysinit.log
xerrs.log ?
Thank you. Those logs are included in the pdiag.
The bootsysinit.log does not show the trace of rc.network. The logs seem to indicate a successful connection. I need to see what happens when you reboot and do not get automatic connection.
I gave you incomplete instructions about the "set -x..." edit.
Please install network_wizard-2.1.3 and network_connect_update-20200722 from
viewtopic.php?p=2241#p2241, then
Edit /usr/local/network-wizard/rc.network, line 65 (blank) to add:
set -x; exec >&2
Then create a new connection and verify that it works.
Then reboot and (I assume) see Puppy fail to automatically connect.
At that point, run pdiag to create the pdiag tarball.
Sorry for the confusion. I forgot that xenial has rc.network in a different place than more recent pups.
@rerwin
here the pdiag tarball after installing network_wizard-2.1.3 and network_connect_update-20200722
Thanks for the pdiag tarball.
I see that wpa_supplicant fails, but have not determined why. I ran netwiz and discovered that my PC required me to insert a sleep early on, so the pci wifi adapter shows up. But your device is recognized normally.
In the absence of an "ah-hah', please try inserting that sleep in case there is a timing issue that manifests differently on your PC. Using network-wizard-2.1.3, in /usr/local/network-wizard/rc.network, insert after line 351 and before the line "stop_all -a >/dev/null 2>&1":
sleep 4
Then reboot and get a pdiag.
if it works, try reducing the sleep to 2 seconds, which is what my PC required. No additional pdiag needed.
If the sleep doesn't help, another thing to try would be to add the trace statement (set -x; exec >&2) to the SNS 2.4 rc.network and run SNS, reboot and get a pdiag. That way, I can compare the traces to possibly find anything different in the startup of the wifi device. The trace statement should replace SNS 2.4 blank line 39 in /usr/local/simple_network_setup/rc.network.
I think I will also rerun my netwiz test but with a USB dongle, in case that makes a difference (versus the pci adapter).
Richard
I added
Code: Select all
sleep 4to /usr/local/network-wizard/rc.network but without success and this is a pdiag log
Now I'll create another pdiag log running sns
and this is the pdiag while running sns as default tool
Dingo wrote: Thu Dec 03, 2020 11:30 amhere the pdiag tarball after installing network_wizard-2.1.3 and network_connect_update-20200722
---------------
and this is the pdiag while running sns as default tool
Thanks for those pdiags.
The SNS pdiag shows that SNS handles your connection as one would expect. Right?
Although I have been silent for a while, I have been experimenting with the network wizard with PCI and USB wifi interfaces, and both WPA2 and WEP encryption. I found a few things to fix. But I am not sure whether the fixes will help you.
In checking your network wizard pdiag, I see that it does not capture the netwiz setup files. That function was added in bionic pup.
I would like you to test with later versions of netwiz and pdiag, hoping that will get us closer to understanding what is happening.
Please install the following in a fresh xenial pupsave environment:
network_connect_update-20200722 from viewtopic.php?p=2241#p2241
pdiag-20171205 from http://distro.ibiblio.org/puppylinux/pe ... 171205.pet
network_wizard-2.1.4-beta which I sent you in a PM
Run NetWiz and scan and save a profile for your problematic device and network, then use that profile to connect. Save the configuration when prompted. If the device is not detected or the connection fails, get a pdiag.
If the connection succeeds, reboot (saving if necessary) and get a pdiag.
Are you using encryption type WPA or WPA2? Be sure it matches what the network/access point expects.
Thank you for your patience with this process.
Richard