no wifi since zypper up

caprus · March 2, 2013, 2:33pm

When I saw “security-announce” notices from the forumsadmin yesterday I ran
zypper patch on one laptopPC only. I would have done more but…

Since then this laptop has been effectively crippled, as there’s no longer any
functional wifi.

Prior to the patch this lappy was consistently able to ping the router in under
1.2 ms with 0& packet loss.

Now:

--- 192.168.12.1 ping statistics ---
124 packets transmitted, 90 received, 27% packet loss, time 140124ms
rtt min/avg/max/mdev = 0.985/187.509/2492.460/472.099 ms, pipe 3


64 bytes from 192.168.12.1: icmp_seq=232 ttl=64 time=169 ms
64 bytes from 192.168.12.1: icmp_seq=233 ttl=64 time=40.1 ms
64 bytes from 192.168.12.1: icmp_seq=234 ttl=64 time=9.60 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

Some data:

# uname -a
Linux P580.cutbeach 3.4.28-2.20-desktop #1 SMP PREEMPT Tue Jan 29 16:51:37 UTC 
2013 (143156b) x86_64 x86_64 x86_64 GNU/Linux

# lspci -nn

02:00.0 Network controller [0280]: Intel Corporation Centrino Wireless-N 2200 
[8086:0891] (rev c4)

I’m running 12.2 with KDE 4.10, network is controlled by NetworkManager

I’ve tried switching to ifup. I can now ping the router, but there’s still
a problem as indicated by fast ping times are longer by 20%, and packet loss is
still increased from pre-patch 0% to

--- 192.168.12.1 ping statistics ---
99 packets transmitted, 52 received, +4 errors, 47% packet loss, time 98066ms
rtt min/avg/max/mdev = 0.930/21.361/1013.596/138.961 ms, pipe 4

--- 192.168.12.1 ping statistics ---
305 packets transmitted, 203 received, 33% packet loss, time 304263ms
rtt min/avg/max/mdev = 0.914/5.501/238.029/24.248 ms

Furthermore I have no Internet access

~> ping 8.8.8.8
connect: Network is unreachable

~> ping 192.168.12.1
PING 192.168.12.1 (192.168.12.1) 56(84) bytes of data.
64 bytes from 192.168.12.1: icmp_seq=2 ttl=64 time=1.06 ms
64 bytes from 192.168.12.1: icmp_seq=3 ttl=64 time=284 ms
64 bytes from 192.168.12.1: icmp_seq=4 ttl=64 time=21.2 ms
64 bytes from 192.168.12.1: icmp_seq=5 ttl=64 time=1.03 ms
^C
--- 192.168.12.1 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 4003ms
rtt min/avg/max/mdev = 1.033/77.050/284.887/120.276 ms

Note: no other changes made in the past week, none ex. zypper up

caprus · March 2, 2013, 2:53pm

# zypper ve
Retrieving repository 'Packman Repository' metadata ..................................................................................................................[done]
Building repository 'Packman Repository' cache .......................................................................................................................[done]
Retrieving repository 'kde-extra' metadata ...........................................................................................................................[done]
Building repository 'kde-extra' cache ................................................................................................................................[done]
Loading repository data...
Reading installed packages...

Dependencies of all installed packages are satisfied.

P580:~ # zypper patch
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Nothing to do.

knurpht · March 2, 2013, 3:03pm

Have you tried resetting/rebooting the router?
Tried a static IP address, with google’s DNS’s, and router-IP as the gateway?

knurpht · March 2, 2013, 3:09pm

Have you tried resetting/rebooting the router?
Tried a static IP address, with google’s DNS’s, and router-IP as the gateway?

caprus · March 2, 2013, 3:12pm

Yes, no change

Tried a static IP address, with google’s DNS’s, and router-IP as the gateway?

Yes, no change

Also tried with 12.3 booting off a thumb drive, Works fine. (not ready to upgrade the OS as a workaround for unrelated reasons, though I will if all else fails.)

tsu2 · March 2, 2013, 5:06pm

If you’re unable to reach a remote network, it’s usually either a routing problem or a problem with the router.

If you’re pinging your default gateway and experiencing loss, I agree you have a significant problem.

Recommend you post your NIC network configuration

ip addr

and your routing table

ip route

IMO although loss might be related to a driver, your network configuration and routing issues almost certainly are unrelated to running zypper.

TSU

caprus · March 2, 2013, 6:04pm

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 9c:4e:36:30:04:38 brd ff:ff:ff:ff:ff:ff
    inet 192.168.12.3/24 brd 192.168.12.255 scope global wlan0

and your routing table

ip route

# ip route
default via 192.168.12.1 dev wlan0  proto static 
192.168.12.0/24 dev wlan0  proto kernel  scope link  src 192.168.12.3

IMO although loss might be related to a driver, your network configuration and routing issues almost certainly are unrelated to running zypper.

IMHO I would be very surprised if it were not the direct result of the zypper patch. Here’s my basis for that:This LAN has the following:
[INDENT=2]1 this pc, 12.2 kde 4.10
2 a pc, 12.2 kde 4.10
3 a pc, 12.2 kde 4.9
4 tablet running Android
5 phone running IOS
6 pc #1 above dual booting Win7 (seldom accessed ex. to test this issue today)
7 pc #3 above dual booting WinVista (seldom accessed ex. to test this issue today)[/INDENT]
None had any problems until yesterday, very stable LAN
Now only one has a problem, and that is #1, all others are still fine.
#1 is the only one that’s had any change
#1 has had only one change - zypper patch

Interestingly, when I reboot the router (Buffalo whrhpg300n. firmware v. pro-v24sp2-19154) the problem does resolve, but not for more than a few minutes.

user · March 2, 2013, 6:28pm

On 03/02/2013 02:36 PM, caprus wrote:
>
> When I saw “security-announce” notices from the forumsadmin yesterday I
> ran zypper patch on one laptopPC only.
> [snip]
> Note: no other changes made in the past week, _none_ ex. zypper up

which did you run “zypper patch” or “zypper up”??

and, please show us the terminal output and input, as well as the
beginning prompt and exit prompt, from


zypper lr -d
tail -n50 /var/log/zypp/history

i see you are not running the KDE which came with 12.2, i wonder if
you accidentally ran “zypper up” or even “zypper dup” with a bunch of
potentially conflicting repos enabled–that will often kill a lot
more than just wifi!!

–
dd
http://tinyurl.com/DD-Caveat

caprus · March 2, 2013, 7:17pm

Definitely “zypper patch” only. “zypper up” was run a few weeks ago, but system has been stable until now.

please show us the terminal output and input, as well as the
beginning prompt and exit prompt, from

zypper lr -d
tail -n50 /var/log/zypp/history

P580:~ # zypper lr -d#  | Alias                         | Name                                | Enabled | Refresh | Priority | Type     | URI                                                                              | Service
---+-------------------------------+-------------------------------------+---------+---------+----------+----------+----------------------------------------------------------------------------------+--------
 1 | Downloads                     | Downloads                           | No      | No      |   99     | plaindir | dir:///home/greyshark/Downloads                                                  |        
 2 | KDE_4.9                       | KDE 4.10                            | Yes     | Yes     |   92     | rpm-md   | http://download.opensuse.org/repositories/KDE:/Release:/410/openSUSE_12.2/       |        
 3 | Packman Repository            | Packman Repository                  | Yes     | Yes     |   90     | rpm-md   | http://packman.inode.at/suse/12.2/                                               |        
 4 | Printing                      | Printing                            | Yes     | Yes     |   85     | rpm-md   | http://download.opensuse.org/repositories/Printing/openSUSE_12.1/                |        
 5 | Wine                          | Wine                                | No      | No      |   99     | rpm-md   | http://download.opensuse.org/repositories/Emulators:/Wine:/STABLE/openSUSE_12.2/ |        
 6 | download.opensuse.org-Stable  | openSUSE BuildService - LibreOffice | Yes     | Yes     |   95     | rpm-md   | http://download.opensuse.org/repositories/LibreOffice:/Stable/openSUSE_12.2/     |        
 7 | download.opensuse.org-mozilla | openSUSE BuildService - Mozilla     | No      | No      |   99     | rpm-md   | http://download.opensuse.org/repositories/mozilla/openSUSE_12.2/                 |        
 8 | google-chrome                 | google-chrome                       | No      | No      |   99     | rpm-md   | http://dl.google.com/linux/chrome/rpm/stable/x86_64                              |        
 9 | google-earth                  | google-earth                        | Yes     | Yes     |   99     | rpm-md   | http://dl.google.com/linux/earth/rpm/stable/x86_64                               |        
10 | graphics                      | graphics                            | No      | No      |   99     | rpm-md   | http://download.opensuse.org/repositories/graphics/openSUSE_12.2/                |        
11 | home:Lazy_Kent                | home:Lazy_Kent                      | No      | No      |   99     | rpm-md   | http://download.opensuse.org/repositories/home:/Lazy_Kent/openSUSE_12.2/         |        
12 | home:ocefpaf                  | home:ocefpaf                        | No      | No      |   99     | rpm-md   | http://download.opensuse.org/repositories/home:/ocefpaf/openSUSE_12.2/           |        
13 | kde-extra                     | kde-extra                           | Yes     | Yes     |   99     | rpm-md   | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_12.2/              |        
14 | libdvdcss repository          | libdvdcss repository                | No      | No      |   99     | rpm-md   | http://opensuse-guide.org/repo/12.2/                                             |        
15 | openSUSE-12.2-1.5             | openSUSE-12.2-1.5                   | No      | No      |   99     | yast2    | hd:///?device=/dev/disk/by-id/usb-SanDisk_Cruzer_1740011B77C2AD5C-0:0            |        
16 | repo-debug                    | openSUSE-12.2-Debug                 | No      | No      |   99     | NONE     | http://download.opensuse.org/debug/distribution/12.2/repo/oss/                   |        
17 | repo-debug-update             | openSUSE-12.2-Update-Debug          | No      | No      |   99     | NONE     | http://download.opensuse.org/debug/update/12.2/                                  |        
18 | repo-debug-update-non-oss     | openSUSE-12.2-Update-Debug-Non-Oss  | No      | No      |   99     | NONE     | http://download.opensuse.org/debug/update/12.2-non-oss/                          |        
19 | repo-non-oss                  | openSUSE-12.2-Non-Oss               | Yes     | No      |   99     | yast2    | http://download.opensuse.org/distribution/12.2/repo/non-oss/                     |        
20 | repo-oss                      | openSUSE-12.2-Oss                   | Yes     | No      |   99     | yast2    | http://download.opensuse.org/distribution/12.2/repo/oss/                         |        
21 | repo-source                   | openSUSE-12.2-Source                | No      | No      |   99     | NONE     | http://download.opensuse.org/source/distribution/12.2/repo/oss/                  |        
22 | repo-update                   | openSUSE-12.2-Update                | Yes     | Yes     |   99     | rpm-md   | http://download.opensuse.org/update/12.2/                                        |        
23 | repo-update-non-oss           | openSUSE-12.2-Update-Non-Oss        | Yes     | Yes     |   99     | rpm-md   | http://download.opensuse.org/update/12.2-non-oss/

i see you are not running the KDE which came with 12.2, i wonder if
you accidentally ran “zypper up” or even “zypper dup” with a bunch of
potentially conflicting repos enabled–that will often kill a lot
more than just wifi!!

I appreciate your concern, and I understand the reason for it, however I can state with certainly that the command was “zypper patch”


P580:~ # tail -n50 /var/log/zypp/history
# insserv: missing `Required-Stop:'  entry: please add even if empty.
# insserv: script jexec is broken: incomplete LSB comment.
# insserv: missing `Required-Stop:'  entry: please add even if empty.
# insserv: script jexec is broken: incomplete LSB comment.
# insserv: missing `Required-Stop:'  entry: please add even if empty.
# insserv: script jexec is broken: incomplete LSB comment.
# insserv: missing `Required-Stop:'  entry: please add even if empty.
# Scanning scripts ...
# Resolve dependencies ...
# Install symlinks in /lib/mkinitrd/setup ...
# Install symlinks in /lib/mkinitrd/boot ...
# 
# Kernel image:   /boot/vmlinuz-3.4.28-2.20-desktop
# Initrd image:   /boot/initrd-3.4.28-2.20-desktop
# KMS drivers:     i915
# Root device:  /dev/disk/by-id/ata-ST1000LM024_HN-M101MBB_S2U5J9AC511690-part1 (/dev/sda1) (mounted on / as ext4)
# Resume device:        /dev/disk/by-id/ata-ST1000LM024_HN-M101MBB_S2U5J9AC511690-part5 (/dev/sda5)
# modprobe: Module hid_generic not found.
# WARNING: no dependencies for kernel module 'hid-generic' found.
# Kernel Modules:       thermal_sys thermal processor fan scsi_dh scsi_dh_emc scsi_dh_hp_sw scsi_dh_alua scsi_dh_rdac video button i2c-algo-bit drm drm_kms_helper i915 xhci-hcd hid-logitech-dj 
# Features:       acpi kms plymouth block usb resume.userspace resume.kernel
# 
2013-03-01 18:02:12|install|udev|182-4.33.1|x86_64||repo-update|ecb450408e151571b6f9ef4e48eee70e5e38b2e3354cdb42a7fcb22b38b361b4
2013-03-01 18:02:13|install|krb5-devel|1.10.2-3.8.1|x86_64||repo-update|a395657b27d883cd5b5d5cf40be9c1014da3325d3a5275e81c432a13abd3083a
2013-03-01 18:02:13|install|Mesa-libGL1-32bit|8.0.4-20.11.1|x86_64||repo-update|54cc43d982de20b3a30d16cb86a173f4f4ec0059ef1d6e4cfbfbf17842902ee4
2013-03-01 18:02:14|install|Mesa-libGLESv2-2|8.0.4-20.11.1|x86_64||repo-update|f7c695c172f20a7c65492b4cc2541dd6ea8fb8ee8548e77f39f9cf7a79bd9965
2013-03-01 18:02:14|install|Mesa-libGLESv1_CM1|8.0.4-20.11.1|x86_64||repo-update|5f76788ad7208e048d684799b0419199d7440c6a8ec4031abe799d8655b8de26
2013-03-01 18:02:14|install|Mesa-libGL1|8.0.4-20.11.1|x86_64||repo-update|909ed1b337db52f61fa8b2854308acb9e514b02a52c716ceb6bfd9ced1875cde
2013-03-01 18:02:15|install|openssl|1.0.1e-2.8.1|x86_64||repo-update|773b2be44425dc58cb5239c4651e6bccee8ef527b79a0fc870d906e998451921
2013-03-01 18:02:17|install|git-core|1.7.10.4-2.8.1|x86_64||repo-update|0f653fac3a12d940d4450dbc44e079f07352645363c5920477f4c2a7a25703ed
2013-03-01 18:02:17|install|libgbm1-32bit|0.0.0-20.11.1|x86_64||repo-update|6bd1fbef017144a5ec7a704552798f99267c97f7036b3ae945485f2ce4038a6d
2013-03-01 18:02:17|install|libudev0|182-4.33.1|x86_64||repo-update|86845ef15704aca67c8d8780cd9cebe50b1d713a834ba06eabc7ff1fd92a362a
2013-03-01 18:02:17|install|Mesa-libGLU1-32bit|8.0.4-20.11.1|x86_64||repo-update|09a3e0df3c846aa24b28fb91c37783b8d754b749fb5b2ad4f817eb03c13f99c3
2013-03-01 18:02:17|install|Mesa-libGLU1|8.0.4-20.11.1|x86_64||repo-update|1c9391a8d2bfb9aed29cf7b5e492d74a1a97806a7350d14e32add010d96855cc
2013-03-01 18:02:18|install|Mesa-libGL-devel|8.0.4-20.11.1|x86_64||repo-update|cad5a926e5c51d13cea0167995f3c71225e8759534048e75a15a91225542c8c9
2013-03-01 18:02:19|install|libopenssl-devel|1.0.1e-2.8.1|x86_64||repo-update|e797eba2c413cd7b71e13ee97c0412fec34da8fdb254cc12b254812545fcf003
2013-03-01 18:02:19|install|gitk|1.7.10.4-2.8.1|x86_64||repo-update|baaecb21eed3c66dd45b94da75c7c0019c8ae2016fea2612acdcc18d71a13bea
2013-03-01 18:02:20|install|git-gui|1.7.10.4-2.8.1|x86_64||repo-update|8346fd3d29458292d026c805321560a2f89d678698d6e761e41bbdc56681c653
2013-03-01 18:02:20|install|git-email|1.7.10.4-2.8.1|x86_64||repo-update|d4bd516a63762ca87b8a65548e059c46232673cf8e134e217a740c59a3e4f620
2013-03-01 18:02:20|install|Mesa-libEGL1-32bit|8.0.4-20.11.1|x86_64||repo-update|a423617d9172e55ec5b57a4b4e6af501ae14bd23cc913d26c75e3ccbf664d776
2013-03-01 18:02:21|install|libudev-devel|182-4.33.1|x86_64||repo-update|4caf276f57d2bad5c373b1bcb3c0d11b35ba8a8ee7801f56e5545ccaab1267fd
2013-03-01 18:02:21|install|libgbm1|0.0.0-20.11.1|x86_64||repo-update|09ff8e0d2501124dc799c2e80471e0dfef95a2db9441718e3c908a4d12de4f4c
2013-03-01 18:02:21|install|libgudev-1_0-0|182-4.33.1|x86_64||repo-update|a14639fb7d3f99f62c815d48c82030ebdc1270e58006a09ae84075e0ef8534e3
2013-03-01 18:02:21|install|Mesa-libGLU-devel|8.0.4-20.11.1|x86_64||repo-update|f3eea47dc5fc31283dec1c275569d760366f60da7a6bc977f83ff29690c74bd1
2013-03-01 18:02:22|install|libgbm-devel|0.0.0-20.11.1|x86_64||repo-update|891d7c466d839856eba4abcbb9d7a901f247880a344745e724310eab32c8c2bb
2013-03-01 18:02:23|install|Mesa-libEGL1|8.0.4-20.11.1|x86_64||repo-update|1f2167f86a2523899c3cc8c266aca4331ae44bcfcf92c916a79aafc4fefce1a9
2013-03-01 18:02:23|install|Mesa-libEGL-devel|8.0.4-20.11.1|x86_64||repo-update|c53faf45b828c9ec708b1e5c818995f975473623138d498733b6e39144d6f712
2013-03-01 18:02:23|install|Mesa-libGLESv2-devel|8.0.4-20.11.1|x86_64||repo-update|2466177e3d43939d05443a1f907697f885bca3090c90beff5300cc54d5d2bbd5
2013-03-01 18:02:23|install|Mesa-libGLESv1_CM-devel|8.0.4-20.11.1|x86_64||repo-update|b446affcc3f52ad06605eadb7ddd41668f42291df3bcc58d8f023f3a586336b4
2013-03-01 18:02:24|install|Mesa-devel|8.0.4-20.11.1|x86_64||repo-update|253e0ba3171def375001992d0f63ed056f9ea24c9258cefd0b27916427a812a4
P580:~ #

Note: repos # 4,6,9,13 are not normally enabled, careless leftovers from a “zypper up” quite a while ago. Now disabled, thanks for the reminder.

robin_listas · March 2, 2013, 10:10pm

On 03/02/2013 07:26 PM, caprus wrote:


> --------------------
>
>   P580:~ # tail -n50 /var/log/zypp/history
>   # insserv: missing `Required-Stop:'  entry: please add even if empty.
&gt;   # insserv: script jexec is broken: incomplete LSB comment.
&gt;   # insserv: missing `Required-Stop:'  entry: please add even if empty.
>   # insserv: script jexec is broken: incomplete LSB comment.
>   # insserv: missing `Required-Stop:'  entry: please add even if empty.
&gt;   # insserv: script jexec is broken: incomplete LSB comment.
&gt;   # insserv: missing `Required-Stop:'  entry: please add even if empty.

This particular error comes froom the oracle java package. You have to
edit /etc/init.d/jexec to add those missing sections, like this:


### BEGIN INIT INFO
# Provides: binfmt_misc
# Required-Start: $local_fs
# Required-Stop:
# Default-Start: 1 2 3 4 5
# Default-Start: 0 6
# Default-Stop: 0 6
# chkconfig: 12345 95 05
# Description: Supports the direct execution of binary formats.
### END INIT INFO

This is of course unrelated to your other problem.

–
Cheers/Saludos
Carlos E. R. (12.3 Dartmouth test at Minas-Anor)

caprus · March 3, 2013, 12:31am

[QUOTE=robin_listas;2531361
This particular error comes froom the oracle java package. You have to
edit /etc/init.d/jexec to add those missing sections[/QUOTE]

Thanks for the tip

user · March 3, 2013, 9:54am

On 03/02/2013 07:26 PM, caprus wrote:
> I appreciate your concern, and I understand the reason for it, however
> I can state with certainly that the command was “zypper patch”

ok…i just saw both mentioned and didn’t realize they were two
different runs, weeks apart.

seems it is something else entirely:

i see (at the beginning of the output from the tail command) an
indication that you probably had a kernel change! but, i can’t see
when exactly but i guess it ran in on 1 March 2013 [you can run the
tail command again and boost the number of line from -n50 to -100 and
see for sure if that happened about the time your wi-fi stopped working]

if that kernel change killed your wi-fi it may be because you were
using a using a wi-fi driver compiled to work with your former
kernel only…if so, you can recompile against your present kernel
or roll back to using the previous kernel…

if there are multiple kernel versions listed on your first green
screen choose the previous and if wi-fi works then it will confirm
that this is the problem…

sorry, i can’t walk you through making a driver which works with your
new kernel, but i think one or all of the stickies at the top of this
forum has lots of hints…

if not enough info in those, ask again (and include the needed
info–see sticky for that hint) and maybe a wi-fi driver compiling
guru will step up

–
dd

caprus · March 3, 2013, 9:07pm

I’ve been too busy to try anything other than the testing noted above, but now the problem appears to have gone away. About 16 hours now with no issue. That makes no sense whatsoever, and I’ve little confidence that the problem is solved, but for now this issue will have to be put on hold pending another failure.

Thanks to everyone for your efforts.

@dd

if that kernel change killed your wi-fi it may be because you were
using a using a wi-fi driver compiled to work with your former
kernel only
not the case, just the “built-in” driver.

tsu2 · March 5, 2013, 6:14pm

Sorry for the long interval since my last post, and congrats (knock on wood) that your problem seems to have resolved itself.

Personally,
I do not suspect anything on your system. I lean strongly towards the likelihood that a change happened on your network instead. A good start might be whether you have control over your Default Gateway or not to know if something changed there approximately the same time. Also, how complex your network security is, whether you’re running plain vanilla DNS and DHCP or whether you’re running something like AD which fully integrates Domain security, DNS and DHCP.

If as I suspect that a change happened on your network, then machines may need to be re-registered on the network in various ways. Short of making specific changes or running Windows in an AD network (yes, Windows boxes will pick up changes better and faster in a MS network), it can take time for things to work themselves out as likely happened in your case.

To verify the above, if your system is portable (eg laptop), I would have suggested trying your machine on another WiFi connection.

So, I wouldn’t worry much about the stability of your “self-fixed” problem.

TSU