Debian Bug report logs - #813098
hwup-ccw-group: fail to configure qeth if device is built into kernel

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: hwup-ccw-group: fail to configure qeth if device is built into kernel

Date: Fri, 29 Jan 2016 12:50:45 +0100

Package: sysconfig-hardware
Version: 0.0.11
Severity: normal

Hi,

booting Debian with a kernel that has the qeth device drivers (core, l2, and l3)
compiled into the kernel, the network interfaces fail to come up.

For example, consider this configuration:

	root@localhost:~# cat /etc/sysconfig/hardware/config-ccw-0.0.f100 
	CCWGROUP_CHANS=(0.0.f100 0.0.f101 0.0.f102)
	QETH_PORTNAME=OSAPORT
	QETH_PORTNO=0
	QETH_OPTIONS=()
	INTERFACE_NAME=eth1

running the "hwup" command results in this error message:

root@localhost:~# hwup ccw 0.0.f100
no kernel module for qeth devices available!

Looking at the "hwup-ccw-group" script, the affect place is:

	elif [ "$NAME" == qeth ]; then
	  modprobe qeth 2> /dev/null || :

	  if [ -d $SYSFS/module/qeth ]; then
	    DRIVER=qeth
	  else
	    error "no kernel module for qeth devices available!"
	  fi
	fi

If the qeth device drivers are built into the kernel, the modprobe fails but
this case is properly handled.  However, if qeth is built-in, there is no
"$SYSFS/module/qeth" directory.

The solution is to update the check and test for a different directory.  The
preferred directory is:

	/sys/bus/ccw/drivers/qeth

which will be created when the qeth device driver is loaded (either built-in
or after a modprobe).

Thanks and kind regards,
  Hendrik

Message #10 received at 813098-close@bugs.debian.org (full text, mbox, reply):

From: Philipp Kern <pkern@debian.org>

To: 813098-close@bugs.debian.org

Subject: Bug#813098: fixed in sysconfig 0.0.12

Date: Sun, 07 Feb 2016 00:51:59 +0000

Source: sysconfig
Source-Version: 0.0.12

We believe that the bug you reported is fixed in the latest version of
sysconfig, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 813098@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Philipp Kern <pkern@debian.org> (supplier of updated sysconfig package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 07 Feb 2016 00:58:34 +0100
Source: sysconfig
Binary: sysconfig-hardware
Architecture: source s390x
Version: 0.0.12
Distribution: unstable
Urgency: medium
Maintainer: Debian S/390 Team <debian-s390@lists.debian.org>
Changed-By: Philipp Kern <pkern@debian.org>
Description:
 sysconfig-hardware - Hardware configuration
Closes: 813098
Changes:
 sysconfig (0.0.12) unstable; urgency=medium
 .
   * Deal with qeth being built-in instead of being a module.
     (Closes: #813098)
Checksums-Sha1:
 5356e31fa4eb90dcb874b5c962a0c4862761a6a6 1155 sysconfig_0.0.12.dsc
 a15695c6355701b080164a841ce872f1bda42586 9581 sysconfig_0.0.12.tar.gz
 680faef8665350155a7ba058331d27004172e42a 8956 sysconfig-hardware_0.0.12_s390x.deb
Checksums-Sha256:
 5bebd8a854bf4d293bf6e10cf6da88181067f5a179247f4c700675e7d676c321 1155 sysconfig_0.0.12.dsc
 797a94a0bba7560929277a3e961349ebb28d347dc0fa8391a13dc819bdc7f201 9581 sysconfig_0.0.12.tar.gz
 c449bd90f71dea645d9399c440a69c3180de1bf9fb72de24a596409743650019 8956 sysconfig-hardware_0.0.12_s390x.deb
Files:
 97721f76ef847f717d9e635edb5bf5c3 1155 admin optional sysconfig_0.0.12.dsc
 c151a95184643f07b92dafa38376f62b 9581 admin optional sysconfig_0.0.12.tar.gz
 a1045ad240a9b861f60e8d99dc1bafed 8956 admin standard sysconfig-hardware_0.0.12_s390x.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJWtozEAAoJEERuJUU10FbsrcAH/jbwrp2ftzsvqHbUz5J4nKne
dd+f0UkcCN3N8KMagiV68cdrj8BQxTDL7+eDcH5g0EFGzzhksKI8R6oAaEb16cgB
7NpEw2DHU/R3NRf13ce/EaReQ3NI2oWMvgm107HXk/EYX5TlG4BgKvAzCYkizVEN
DVnzAPXkKv6ZoIJ99dC8/rCtV3ClRWhnXf8zHGv4OC3AWMUGnWo9Hsx16xy6m5Hb
QwDTQVc7GqK3EzbWIaNvmCN1/WxurQzAh1jVFz0cv44pgHpZvk80pYVuc717gfS1
IEPcZ2JvEhFYEjmjksKqUmOi0TAWWfS3aPDY86C+QVCadxBFpJWfeRqN/gAzBzU=
=5kQs
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.