That worked - the error msg. went away, and it shaved about 20 seconds
off the boot time.
This was a new clone of SLES11sp1. So the file must have been created
by yast or something else I did while trying to fix the problem.
Since you're paying taxes in Germany, I suppose you're doing your par
Roger,
good news. I am working in the networking team of Linux on System z
development; thus qeth-related problems are my daily business. But
please do not ask me financial questions ;-)
For your remaining problem: Have you upgraded your system from SLES10?
In this case you may still have old con
Thank you, Ursula
That solved the problem. I can now ping and ftp between my layer3
hipersockets. I still get the "Waiting for mandatory devices.
hsi-bus-ccw-0.0.7000 No interface found " msg. when booting
but now that it works, I'll just stop watching.
You're pretty amazing. Thin
Roger,
when configuring a network interface with yast, a udev-rule is created
for the device containing qeth attribute definitions, among them
attribute layer2. Look into /etc/udev/rules.d and check a rule starting
with 51-...7000... . I assume this rule contains a line with layer2=1.
Change this
Roger,
get rid of the LLADDR='00:00:00:00:00:00' definition. ifup does no
longer work for a zero MAC-address. HiperSockets define a MAC-address;
during initialization Linux determines this MAC-address and uses it, if
LLADDR is not defined.
Ursula
On Tue, 2011-11-08 at 10:47 +0100, Roger Evans wr
Forgot to send the info you requested:
DPRODDB2:/etc/sysconfig/network # cat ifcfg-hsi0
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR='10.5.2.11/16'
LLADDR='00:00:00:00:00:00'
MTU=''
NAME='Hipersocket (0.0.7000)'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
USERCONTROL='no'
-
THanks for that tip. I can't remember having chosen level2, but I see
that my other (older) interfaces are not level2, so, yes, I would like
to switch to level3.
I used the commands (from "Device Drivers, Features...") to to take the
device offline and to make it not level2 (level2=9); After t
Hi Roger,
your boot.messages do not show any message refering to 0.0.7000 or hsi0.
Your hsi0-device is in state SOFTSETUP, which means it has been
activated successfully; just the ifup step fails. The configuration file
for ifup is /etc/sysconfig/network/ifcfg-hsi0. Can you check the
definitions o
Hi, Ursula
uname -a
Linux DPRODDB2 2.6.32.46-0.3-default #1 SMP 2011-09-29 17:49:31 +0200
s390x s390x s390x GNU/Linux
lsqeth
... [other devices]
Device name : hsi0
-
card_type : HiperSockets
cdev0
Roger,
the minimum SLES11 SP1 kernel level should be 2.6.32.29-0.3.1. If you
still have problems with a kernel level greater or equal to this one,
something else is wrong. Which qeth-related messages show up in dmesg?
What does "lsqeth" return?
Regards, Ursula Braun, IBM Germany
On Mon, 2011-11-
Thank you Ursula
I don't seem to have the permissions to read those bugzilla entries, or
maybe I'm looking in the wrong Novell Bugzilla.
Upgrading from sp3 to sp4 solved the problem for SLES10.
I upgraded my SLES11sp1 with all the upgrades SuSE provides, but still
get the following msg:
-
On Fri, 2011-11-04 at 15:18 +0200, Roger Evans wrote:
> Hi Sue
>
> Didn't seem to help. When booting with SLES10v2 I see the following
> when watching the boot from VM:
> -
Display the kernel storage at 10b03a60.8 - in there is the instruction
giving the exception. The b2220030 is the IPM used to retrieve the condition
code from the previous instruction so it can be placed in a C variable.
On 11/4/11 9:18 AM, "Roger Evans" wrote:
> Hi Sue
>
> Didn't seem to help.
Hi Sue
Didn't seem to help. When booting with SLES10v2 I see the following
when watching the boot from VM:
-
eth: IPv6 not supported on
Can you try turning off QIOASSIST for the guest and see
if that makes a difference?
Regards,
Sue Farrell
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: I
> What version of z/VM is this?
z/VM Version 5 Release 4.0, Service Level 1101 (64-bit),
> Do you have all the Linux related maintenance installed for it?
Hard to tell. Is there one place we can go to find out what is needed?
We have installed all the APARS that IBM told us were necessary to run
>>> On 11/1/2011 at 08:12 AM, Roger Evans wrote:
> SuSE 10.2
> uname returns: kernel 2.6.16.60-0.21-default
That's the SLES10 SP2 GA kernel, which is 2.5 years old. I think it might be
time to apply some maintenance. :(
> I'm also trying to configure hsi0 with YAST on SuSE 11sp1
> When I try
SuSE 10.2
uname returns: kernel 2.6.16.60-0.21-default
I'm also trying to configure hsi0 with YAST on SuSE 11sp1
When I try to bring the interface up with ifup, I get:
--
#ifup hsi0
hsi0 name: Hipersocket (0.
>>> On 10/31/2011 at 06:00 AM, Roger Evans wrote:
> Good morning, Mailing list
> We upgraded from a z9 to a z114 during the weekend, Most things seem
> to be working fine, but none of my linux hipersocket interfaces come
> up.
>
-snip-
> None of our VM or linux definitions have changed.
>
> T
19 matches
Mail list logo
