current state of the services network and NetworkManager
by Steffen Maier
Hi all,
while I was trying to get all different kinds of network device types of
s390x working (bug reports in bugzilla pending), I got it working nicely
with the traditional network service, which is what users would
typically use in a data center.
NetworkManager requires the activation (chkconfig) of the services
messagebus, haldaemon. Then NM works with static IP settings through
nm-system-settings, which is what we need in
linuxrc.s390/loader/anaconda, and seems to detect at least qeth and lcs
devices (it doesn't touch ctc and netiucv). Tested with
NetworkManager-0.7.1-4.git20090414.fc11.1.s390x.
Support for the s390 bus types ccw, ccwgroup, and iucv (which is
sufficient for all network types as well as dasd, zfcp, and tape) has
been in HAL since 2005
[http://lists.freedesktop.org/archives/hal/2005-June/002628.html,
http://cgit.freedesktop.org/hal/commit/?id=2ed3c042c13f741b8a2166e4551d9d...].
Only when NM changes to udev for device sensing there might need to be
new support for s390. See the attachment for an example output of lshal
of a z/VM 5.3 guest on a z10 with 12 different types of network devices
as well as dasd and zfcp.
If lo and eth0 (a real OSA NIC) are the only network devices defined by
means of ifcfg file in /etc/sysconfig/network-scripts/ and they have
been brought up by the network service on boot, I can startup NM and
eth0 keeps working. This is what I see in syslog-ng:
> Jun 21 19:12:44 h4245010 NetworkManager: <info> starting...
> Jun 21 19:12:44 h4245010 NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess
> Jun 21 19:12:44 h4245010 NetworkManager: <info> (eth0): new Ethernet device (driver: 'qeth')
> Jun 21 19:12:44 h4245010 NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_02_00_00_eb_a5_4b
> Jun 21 19:12:44 h4245010 NetworkManager: <info> Trying to start the supplicant...
> Jun 21 19:12:44 h4245010 NetworkManager: <info> Trying to start the system settings daemon...
> Jun 21 19:12:44 h4245010 NetworkManager: <info> (eth0): carrier now ON (device state 1)
> Jun 21 19:12:44 h4245010 nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
> Jun 21 19:12:44 h4245010 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
> Jun 21 19:12:44 h4245010 nm-system-settings: ifcfg-rh: read connection 'System eth0'
> Jun 21 19:12:44 h4245010 nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 1 -> 2
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): preparing device.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): deactivating device (reason: 2).
> Jun 21 19:12:48 h4245010 NetworkManager: <WARN> check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 2 -> 3
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) starting connection 'System eth0'
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 3 -> 4
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 4 -> 5
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> (eth0): device state change: 5 -> 7
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
> Jun 21 19:12:48 h4245010 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
> Jun 21 19:12:49 h4245010 NetworkManager: <info> (eth0): device state change: 7 -> 8
> Jun 21 19:12:49 h4245010 NetworkManager: <info> Policy set 'System eth0' (eth0) as default for routing and DNS.
> Jun 21 19:12:49 h4245010 NetworkManager: <info> Activation (eth0) successful, device activated.
> Jun 21 19:12:49 h4245010 NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
> # nm-tool
>
> NetworkManager Tool
>
> State: connected
>
>
> ** (process:2189): WARNING **: error: failed to read connections from org.freedesktop.NetworkManagerUserSettings:
> The name org.freedesktop.NetworkManagerUserSettings was not provided by any .service files
> - Device: eth0 [System eth0] --------------------------------------------------
> Type: Wired
> Driver: qeth
> State: connected
> Default: yes
> HW Address: 02:00:00:EB:A5:4B
>
> Capabilities:
> Carrier Detect: yes
> Speed: 1000 Mb/s
>
> Wired Properties
> Carrier: on
>
> IPv4 Settings:
> Address: X.Y.108.140
> Prefix: 22 (255.255.252.0)
> Gateway: X.Y.108.1
>
> DNS: X.Y.120.241
> DNS: X.Y.64.172
Also the output of nm-tool looks promising. If I start "anaconda -t -T",
I find the following in /tmp/anacdump.txt after it bails out on sensing
DASDs:
> id.network: Network instance, containing members:
> id.network.netdevices: {'eth0': DEVICE=eth0
> BOOTPROTO=none
> DNS1=X.Y.120.241
> DNS2=X.Y.64.172
> HWADDR=02:00:00:EB:A5:4B
> IPADDR=X.Y.108.140
> NETMASK=255.255.252.0
> NETTYPE=qeth
> ONBOOT=yes
> SUBCHANNELS=0.0.f5f0,0.0.f5f1,0.0.f5f2
> USERCTL=no
>
> }
> id.network.ksdevice: None
> id.network.overrideDHCPhostname: False
> id.network.hostname: XYZ.boeblingen.de.ibm.com
> id.network.domains: [boeblingen.de.ibm.com ibm.com]
This seems to be very good with regard to network so far.
Steffen
Linux on System z Development
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
14 years, 9 months
RE: kernel panic in hercules snapshot
by Ivan Warren
(this message will probably not appear with proper threading because I
subscribed after the message was sent)
Peter,
SVN 5178 should have solved this.. The Macro is now defined as :
#define _PSW_IA(_regs, _n) \
(VADR)((_regs)->AIV + ((intptr_t)(_regs)->ip - (intptr_t)(_regs)->aip)
+ (_n))
--Ivan
14 years, 10 months
Dependency problem with pyxf86config
by Karsten Hopp
Hello,
anaconda requires system-config-keyboard which in turn requires
pyxf86config.
pyxf86config isn't available as we don't have an xorg-x11-server-devel
package
with the libxf86config library on s390x.
We can't fix it in system-config-keyboard as that's a noarch package and
I don't want to make it an arch package only to make %ifnarch work.
The best way would be to drop the system-config-keyboard requirement in
anaconda,
but I'd think that means that the screen with keyboard selection needs
to be disabled
on s390 and s390x.
Do we loose anything by doing that ? AFAIK that's only required for the
XOrg config
(which we don't have on s390*) and for the text consoles (we have x3270
consoles only
and those use the settings of your local machine). Am I wrong here or
can we do this fix ?
Karsten
14 years, 10 months
rawhide kernel in Fedora 11
by Dan Horák
I have done a scratch built for today's rawhide kernel - download the
rpms from https://s390.koji.fedoraproject.org/koji/taskinfo?taskID=83115
But zipl (v1.8.0) can't install the kernel/initrd to be available for
booting, it throws an error. Looks like the vmlinuz image is too large.
-bash-4.0# zipl
Using config file '/etc/zipl.conf'
Building bootmap in '/boot/'
Building menu 'rh-automatic-menu'
Adding #1: IPL section '2.6.31-0.33.rc1.git2.fc11.s390x'
Error: Component overlap: kernel image and initial ramdisk
-rwxr-xr-x 1 root root 6929920 26. kvě 01.40 vmlinuz-2.6.29.3-159.fc11.s390x
-rwxr-xr-x 1 root root 6929920 24. čen 15.10 vmlinuz-2.6.29.5-191.fc11.s390x
-rwxr-xr-x 1 root root 12161536 29. čen 03.30 vmlinuz-2.6.31-0.33.rc1.git2.fc11.s390x
Dan
14 years, 10 months
hercules snapshot pb.
by Peter Sylvester
The bug about a hercules snapshot that I reported had been corrected
in a later snapshot.
but since sanpshot 5280 an EXTENDED_DIAG204 is enabled by default
and fedora doesn't like it. disabling in the feature header make fedora
work.
/PS
14 years, 10 months
kernel panic in hercules snapshot
by Peter Sylvester
hi,
on a linux 32bit the hercules snapshot 5166 breaks the fedora image.
in opcode.h :
works:
#define _PSW_IA(_regs, _n) \
((_regs)->AIV + (intptr_t)((_regs)->ip - (_regs)->aip) + (VADR)(_n))
doesn't work:
#define _PSW_IA(_regs, _n) \
((_regs)->AIV + (uintptr_t)((_regs)->ip - (_regs)->aip) + (VADR)(_n))
I don't know whether this a hercules bug or a fedora pb.
peter sylvester
14 years, 10 months
kernel issue(s)
by Harold Grovesteen
I updated my system with yum. The update created a new kernel. When it
boots it hangs while building udev. Booting of the default kernel that
came with the distribution is fine.
2.6.29.3-159.fc11.s390x - no problem
2.6.29.4-167.fc11.s390x - hangs (loops?)
Two others have reported to me personally that they are experiencing a
"crash" (no specifics) and a "kernel panic." I recommended both to post
here.
Harold Grovesteen
14 years, 10 months
gcc on Fedora 11 on Hercules
by Harold Grovesteen
Where is gcc? If it isn't part of the distribution, how do I install it?
I might have missed the directory when I was hunting for it, so I
figured I would ask here for the real answer. I still don't have a clue
how to get and install a package with Fedora.
Thanks,
Harold Grovesteen
14 years, 10 months
Running Fedora11.390 under Hercules
by Bernie VK2KAD
>>Upgrade your Hercules to 3.06 or put CU=3990-3 in your Hercules
>>configuration file for any 3390 device.
>>
>>Harold Grovesteen
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Many thanks for this tip - it helped me to get Fedora11 up and running.
I tried several methods and eventually ended up with a VMware guest running
Fedora 11 running Hercules3.06
The above explains why my attempts with Ubuntu failed - my Ubuntu Hercules
is at 3.05 because that is what Aptitude found and installed for me whereas
with my Fedora system, "yum install Hercules" installs Hercules3.06.
I did find some threads regarding PAV support which yielded the same errors
I was seeing. Overriding the CU to a back level obviously bypasses PAV
processing.
Thanks again to Harold
Bern - VK2KAD
14 years, 10 months
