no network after updrade

jpff · February 17, 2018, 8:46pm

My 32bit laptop has been running 13.3 but today I decided i should upgrade to tumbleweed (all my other machines are 64bit and run Leap 42.3) I did an online upgrade, and after many hours and installing 2177 packages it said it was done and I rebooted

First oddity was the boot messages were all shown twice (I hit ESC to see them) but it boote. BUT it was not connected to my lan. iwconfig saidd it was up but not assosiated with wifi AP. Tried using yast2 to configure and it looked OK apart from asking bout a zone – which I have not seen before. No ifconfig program either.

Two immediate questions:

1: How do I get a wifi connection?

2: what should i do about zones?

and bonus question, why double messages?

I do not run gnome or kde; just fvwm + xterms+emacs

deano_ferrari · February 17, 2018, 9:38pm

You’re best advised to start separate threads for each of the issues you’ve encountered. With respect to the wireless issue, a good start would be to post the hardware details eg via lspci or hwinfo…

/usr/sbin/hwinfo --netcard

Which network devices are present?

ip a

deano_ferrari · February 17, 2018, 9:41pm

Also, you didn’t mention whether you are using NetworkManager or wicked to manage your network interfaces. That can be configured via

YaST > System > Network Settings > Global Settings

jpff · February 17, 2018, 10:52pm

[QUOTE=deano_ferrari;2855903]You’re best advised to start separate threads for each of the issues you’ve encountered. With respect to the wireless issue, a good start would be to post the hardware details eg via spci or hwinfo…

/usr/sbin/hwinfo --netcard

Hum. I can run it and I have but caoturung the output is harder (it is not onnected). Will have to find a memory stick.

It is using ipw2200 driver

[QUOTE]
Which network devices are present?

ip a

eth0 is a wred ethernet, eth1 is wireless. Also exists an ir and something else I forget.

I used to have eth1 start ob boot with static I address, and as far as I can tell from yast2 that is what is set

iwlist scan sees the AP as well. The wifi-active light goes on and off during boot but off when booted.

Will look for a memory stick

Sorry about the multiple questions – I thought they were related.

jpff · February 17, 2018, 10:54pm

Using wicked and set that way. Never could get the network manager to do anything and I am rather old-school, or even old to learn new tricks.

deano_ferrari · February 17, 2018, 10:56pm

Yes, that’s what would normally be recommended when wired ethernet not available.

It is using ipw2200 driver

Ok.

deano_ferrari · February 17, 2018, 10:58pm

Good to know. That helps with any configuration advice that may be given (rather than assuming NM is in use as with most laptop users).

deano_ferrari · February 17, 2018, 11:14pm

Check that the ‘ipw-firmware’ package is installed

rpm -qa|grep ipw-firmware

Check for firmware issues reported at boot

dmesg|egrep "ipw|firmware"

deano_ferrari · February 17, 2018, 11:31pm

If the firmware checks out ok, try observing dmesg output while connecting. To do this open a terminal window and do

dmesg -w

Open another and do

sudo ifdown eth1

sudo ifup eth1

That should help with determining if there are any authentication issues preventing association.

jpff · February 18, 2018, 12:52pm

I checked the firmware and the package exists.
warning: Unsupported version of key: V3
ipw-firmware-9-20.4.noarch

In dmesg the ipw stuff looks OK. Will send when I get to a connection computer with USB.

Tried the ifdown/ifup experiment and on the calling xterms it said


# ifdown eth1
eth1            device-ready
# ifup eth1
eth1            device-not-running
#

But nothing appeared in dmesg.

jpff · February 18, 2018, 4:07pm

The results of hwinfo and ip etc


# hwinfo --netcard
11: PCI 202.0: 0282 WLAN controller
  [Created at pci.378]
  Unique ID: JNkJ.yFKtihCJThD
  Parent ID: 6NW+.+ISWpD3pbdC
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:02.0
  SysFS BusID: 0000:02:02.0
  Hardware Class: network
  Model: "Intel IBM ThinkPad R50e"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4220 "PRO/Wireless 2200BG [Calexico2] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x2712 "IBM ThinkPad R50e"
  Revision: 0x05
  Driver: "ipw2200"
  Driver Modules: "ipw2200"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xd0220000-0xd0220fff (rw,non-prefetchable)
  IRQ: 21 (41 events)
  HW Address: 00:12:f0:46:37:dc
  Permanent HW Address: 00:12:f0:46:37:dc
  Link detected: no
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484
  WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004220sv00008086sd00002712bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #8 (PCI bridge)

19: PCI 201.0: 0200 Ethernet controller
  [Created at pci.378]
  Unique ID: rBUF.VMP_4zV+wdE
  Parent ID: 6NW+.+ISWpD3pbdC
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:01.0
  SysFS BusID: 0000:02:01.0
  Hardware Class: network
  Model: "Intel 82541GI Gigabit Ethernet Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x1077 "82541GI Gigabit Ethernet Controller"
  SubVendor: pci 0x1014 "IBM"
  SubDevice: pci 0x055b 
  Driver: "e1000"
  Driver Modules: "e1000"
  Device File: eth0
  Memory Range: 0xd0200000-0xd021ffff (rw,non-prefetchable)
  I/O Ports: 0x7000-0x703f (rw)
  IRQ: 20 (no events)
  HW Address: 00:0a:e4:32:99:a4
  Permanent HW Address: 00:0a:e4:32:99:a4
  Link detected: no
  Module Alias: "pci:v00008086d00001077sv00001014sd0000055Bbc02sc00i00"
  Driver Info #0:
    Driver Status: e1000 is active
    Driver Activation Cmd: "modprobe e1000"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #8 (PCI bridge)

# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN group default qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:0a:e4:32:99:a4 brd ff:ff:ff:ff:ff:ff
4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:12:f0:46:37:dc brd ff:ff:ff:ff:ff:ff

# dmesg|egrep "ipw|firmware"
   11.966903] psmouse serio1: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
   45.465903] libipw: 802.11 data/management/control stack, git-1.1.13
   45.465909] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
   45.685820] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kdmprq
   45.685825] ipw2200: Copyright(c) 2003-2006 Intel Corporation
   45.686384] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
   46.194689] thinkpad_acpi: WARNING: Outdated ThinkPad BIOS/EC firmware
   46.194691] thinkpad_acpi: WARNING: This firmware may be missing critical bug fixes and/or important features
   46.216504] ipw2200: Detected geography ZZR (14 802.11bg channels, 0 802.11a channels)

jpff · February 20, 2018, 10:18pm

I managed to find enough kit to try a wired ethernet and that worked ok apart from having to change the routing, but this is not a working solution for the use of this machine.

So I am still hoping for some suggestions about getting wifi to work.

deano_ferrari · February 20, 2018, 11:46pm

What is reported if you attempt to bring the interface up like this?

sudo ip link set eth1 up

Perhaps check that the wifi device is not soft-blocked.

/usr/sbin/rfkill list

If it is, do…

sudo /usr/sbin/rfkill unblock wifi

Just for completeness perhaps share the config file for eth1 in /etc/sysconfig/network/ifcfg-eth1

jpff · February 21, 2018, 9:35pm

Humm… a new problem; it will not allow me to log in – tried three different users and all say incorrect password.

It as OK when I used it on Monday! Need to find/create a rescue CD/DVD or USB stick I guess

jpff · February 23, 2018, 12:58pm

It just returned with no messages. What should I expect? What should I check? Did not seem to give a connection, and iwconfig showed no associaton with theAP

Perhaps check that the wifi device is not soft-blocked.

/usr/sbin/rfkill list
If it is, do…

sudo /usr/sbin/rfkill unblock wifi
Just for completeness perhaps share the config file for eth1 in /etc/sysconfig/network/ifcfg-eth1

Device was not blocked. I get here my /etc/sysconfig/network/ifcfg-eth1 with the local password removed – and yes it is correct


BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
INTERFACETYPE='wlan'
IPADDR='172.16.4.17/24'
MTU='1492'
NAME='PRO/Wireless 2200BG [Calexico2] Network Connection'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='1'
WIRELESS_AUTH_MODE='psk'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE='TTLS'
WIRELESS_ESSID='CODEMIST'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='64'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='redacted_password'
PREFIXLEN='16'

knurpht · February 23, 2018, 6:05pm

Like I already wrote in the other thread, perform a clean install. You may solve this issue, but my bet is that you will run into more issues.
http://repos.opensuse.org/tumbleweed/iso/openSUSE-Tumbleweed-DVD-i586-Current.iso

jpff · February 24, 2018, 1:04am

if I have to do a clean install then I alsp need to consider if tumbleweed is the correct system, which has seemed less than stable.

I do need to limit the number of different distros I have, and Leap is certainly needed but perhaps I should go to a duplicate, like Debian
which i have when it was not possible to install SuSE on a particular machine years ago.

I need to consider te options

knurpht · February 24, 2018, 1:17am

That’s a conclusion you cannot draw after performing a non-supported upgrade. IME Tumbleweed is rock stable and has been ever since it’s been built en tested like it is now.

I do need to limit the number of different distros I have, and Leap is certainly needed but perhaps I should go to a duplicate, like Debian
which i have when it was not possible to install SuSE on a particular machine years ago.
I need to consider te options

Leap is out of the question, since your machine is 32bit, and Leap is 64bit only. Right now, Tumbleweed is the only openSUSE option you have.
AFAIK from talking to people from other distros, openSUSE is not the only distro dropping support for 32bit systems. It’s simply not worth the effort, time, computer power to keep on maintaining 32bit for an audience that’s becoming smaller and smaller.

deano_ferrari · February 24, 2018, 1:19am

It’s not clear to me why it fails to activate/associate. I was expecting you to report an error message given that this does not cause wicked to activate the device and associate with your AP. You could observe the journal logging while bringing eth1 up…so this in one terminal

sudo journalctl -f

and this executed from another

sudo ip link set eth1 up

Knurpht’s advice might be the best course of action given you have other issues with this install.

FWIW, I don’t have “USERCONTROL=‘no’” in my working configuration, and I’m using “STARTMODE=‘ifplugd’”, but ‘auto’ should be ok IMHO.

deano_ferrari · February 24, 2018, 1:22am

Ah, I wasn’t aware that this user had used an unsupported upgrade method. That is likely to be relevant here somehow.