Hendrik Brueckner
2016-01-29 14:30:02 UTC
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:
***@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:
***@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
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:
***@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:
***@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