On Wed, Dec 22, 2004 at 09:57:28AM -0600, Michael Lambert wrote:
> qeth: Trying to use card with devnos 0x770/0x771/0x772
> qdio : response upon setting indicators is 0x3.
> qdio : response upon setting indicators is 0x3.
> qeth: There were problems in hard-setting up the card.
Unfortunately, des
1:18 PM
To: LINUX-390@vm.marist.edu
Subject: Re: SUSE kernel 2.4.21-266 qeth driver problem
Sounds like a bad kernel update got released. In your position, I would
downgrade to the prior known good kernel, and report the problem to SUSE (or
whomever is your support provider).
verify it with VM's
virtual hipersockets, anyone seeing this problem with real hipersockets?
Steve
-Original Message-
From: Mark Post [mailto:[EMAIL PROTECTED]
Sent: Monday, December 27, 2004 11:18 PM
To: LINUX-390@vm.marist.edu
Subject: Re: SUSE kernel 2.4.21-266 qeth driver problem
PROTECTED]
Sent: Monday, December 27, 2004 1:11 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SUSE kernel 2.4.21-266 qeth driver problem
Hi Folks,
I am having the exact problem as Michael is. I did the kernel (-266)
maintenance to one of my guests this morning that previously had a working
connection to
e I applied SuSE's maintenance this morning.
Steve
-Original Message-
From: Dennis Musselwhite [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 23, 2004 9:40 AM
To: LINUX-390@vm.marist.edu
Subject: Re: SUSE kernel 2.4.21-266 qeth driver problem
Hi Michael,
I'm not aware of a
> I'm not aware of any changes in the qeth driver that would have affected
> the HiperSockets initialization (but I'm no expert on the Linux
> implementation). It sounds like you are keeping your Linux users
> up-to-date. What level of CP are you running (and what Guest LAN
> maintenance level is
Hi Michael,
I'm not aware of any changes in the qeth driver that would have affected
the HiperSockets initialization (but I'm no expert on the Linux
implementation). It sounds like you are keeping your Linux users
up-to-date. What level of CP are you running (and what Guest LAN
maintenance level
> Michael,
>
> I've been through similar struggles lately so I can sympathize. The first
> question I have is, are you using a hipersocket guest lan or a qdio
> guest lan? You refer to both in the note, but they are not the same thing.
> Since you have an interface named hsi0, then I guessing tha
y, December 22, 2004 2:15 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SUSE kernel 2.4.21-266 qeth driver problem
Michael,
I've been through similar struggles lately so I can sympathize. The first
question I have is, are you using a hipersocket guest lan or a qdio
guest lan? You refer to b
Michael,
I've been through similar struggles lately so I can sympathize. The first
question I have is, are you using a hipersocket guest lan or a qdio
guest lan? You refer to both in the note, but they are not the same thing.
Since you have an interface named hsi0, then I guessing that you reall
Michael,
You should also have an add_parms line for that card. Do you?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Michael Lambert
Sent: Wednesday, December 22, 2004 10:57 AM
To: LINUX-390@VM.MARIST.EDU
Subject: SUSE kernel 2.4.21-266 qeth
I'm running SLES 8 guests on a z/800 using hipersocket guestlans with a
linux image handling routing. I installed the just-released SUSE kernel
2.4.21-266-default on a test image this morning and found that my qdio
hipersockets interface was no longer initializing correctly.
Whenever I attempt to
12 matches
Mail list logo
