Larry, Check out https://www.mail-archive.com/linux-390@vm.marist.edu/msg66460.html. I found this issue when I was initially testing SLES 12 (still haven't implemented SLES 12 in production). Your new devices may need to be added to the cio_ignore file.
Harley -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Davis, Larry (National VM Capability) Sent: Tuesday, November 10, 2015 7:08 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES12 - yast does not create a udev rule I have the same problem with Network and DASD devices that I add, I am not sure of the proper procedure but I had to add the network device to the Rules files in /etc/udev/rules.d/70-persistent-net.rules I have also had to add rules for each new DASD device so it is available after an IPL or reboot Larry Davis, VM Capability -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Christer Solskogen Sent: Tuesday, November 10, 2015 4:58 AM To: LINUX-390@VM.MARIST.EDU Subject: SLES12 - yast does not create a udev rule Hi! I've setup the network in YaST, but the device does not start automagicly when I reboot the machine (running as a guest in z/VM). I was pretty sure that YaST would create a file under /etc/udev/rules.d called 51-qeth-0.0.0603.rules (or something) - the address is 603,604 and 605. I can get the device to work if I run znetconf -a 603 manually. Help, please! ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/ *************************************************************************** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ****************************************************************************
