>>> On 10/30/2012 at 08:24 AM, "van Sleeuwen, Berry" >>> <[email protected]> wrote: > Hi Ursula, > > Thanks. That might be something then. We have 2.6.32.12-0.7 in these guests. > > Is there any way to go around this issue? Can we activate the OSA outside > udev?
Updating the kernel would be the most appropriate way, of course. Upgrading to a supported version of SLES is another, even better way. :) Activating an OSA manually is certainly a choice you can make, but not one I would recommend. However: echo 0.0.efac,0.0.efad,0.0.efad > /sys/bus/ccwgroup/drivers/qeth/group udevadm settle If /sys/bus/ccwgroup/drivers/qeth/0.0.efac already exists, those two commands can be skipped. Not having such hardware to test with, I don't know if it needs to be in Layer 2 mode or Layer 3. For Layer 2: echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.efac/layer2 For Layer 3: echo 0 > /sys/bus/ccwgroup/drivers/qeth/0.0.efac/layer2 Followed by: echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.efac/online Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
