Bug#451230: linux-image-2.6-s390 / qeth - HSI-interface doesn't come up after reboot

2007-11-15 Thread Joachim Krais

severity 451230 normal
tags 451230 moreinfo

s390 never had automatic setup of devices. Please show your
configuration. The debian installer sets up a configuration in
/etc/sysconfig/hardware which lists all hardware devices which are used
during the installation.

Bastian

---

Our HSI-NIC is integrated in the path /etc/sysconfig/hardware with
config-ccw-0.0.0800. The only content in this file is:

CCWGROUP_CHANS=(0.0.0800 0.0.0801 0.0.0802)

Is this correct that the file has only one line?

Excursion:
==
Sorry, we didn't describe our environment sufficiently.
We running our Linux servers under Z/VM in different LPARs. The NICs and 
other hardware (DASDs) are defined in Z/VM for every guest (Linux). The 
physical hardware adapters so are mapped in virtual addresses. We aren't 
running Linux natively on a LPAR. We use these Linux-servers in a 
productive environment. At maintenance work (for example by a power on 
reset) we load the Linux guests from one LPAR (which will be maintained) 
to another LPAR. So we have the need that it works well. In SLES9 the 
HSI-NIC comes up while rebooting the linux-server by IPL from the Z/VM 
an we have our network connectivity. But we aren't happy about SLES10 
and so we are looking for an alternative distribution.






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#451230: linux-image-2.6-s390 / qeth - HSI-interface doesn't come up after reboot

2007-11-14 Thread Joachim Krais

Package: linux-image-2.6-s390
Version: 2.6.18
Severity: grave


Hello together,

we downloaded Debian4.0 and Debian4.0R1 and detected a bug with the
network-interface. This bug exists in both releases.
We use it on zSeries [architecture is s390].


The problem:

If we reboot the system, the HSI network-interface won't automatically
come up. We have to set them up manually in z/VM with
echo 1 /sys/bus/ccwgroup/drivers/qeth/VIRTUAL_ADR_OF_DEVICE/online
and modify the default-route, IP-address of the network-interface and
reload the ssh daemon. Now we can connect again with putty.


Our solution is a workaround:
=
We append /etc/init.d/network with the echo command at following
position:
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

### Our workaround
echo 1  /sys/bus/ccwgroup/drivers/qeth/VIRTUAL_ADR_OF_DEVICE/online

[ -x /sbin/ifup ] || exit 0

Now the qeth Device comes up at (re)boot automatically and
we can connect with putty to the server.


Our question:
=
Is it possible to fix this problem? We use a lot of z/Linux servers with
more than one network-interface and our workaround is not very efficient ;-)

Thanks a lot!
Joachim Krais



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#451230: linux-image-2.6-s390 / qeth - HSI-interface doesn't come up after reboot

2007-11-14 Thread Bastian Blank
severity 451230 normal
tags 451230 moreinfo
thanks

On Wed, Nov 14, 2007 at 11:12:36AM +0100, Joachim Krais wrote:
 If we reboot the system, the HSI network-interface won't automatically
 come up.

s390 never had automatic setup of devices. Please show your
configuration. The debian installer sets up a configuration in
/etc/sysconfig/hardware which lists all hardware devices which are used
during the installation.

Bastian

-- 
The face of war has never changed.  Surely it is more logical to heal
than to kill.
-- Surak of Vulcan, The Savage Curtain, stardate 5906.5



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]