Re: SLES12 - yast does not create a udev rule

[Christer Solskogen]

Yes, that gave me a hint.
The udev rules does NOT get created if the qeth device is active.
On Nov 10, 2015 15:49, "Mark Post"  wrote:

> >>> On 11/10/2015 at 04:57 AM, Christer Solskogen <
> christer.solsko...@gmail.com>
> wrote:
> > 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!
>
> I've not seen that problem before.  There should be some hint of what went
> wrong in /var/log/YaST2/y2log.  Look for "qeth_configure" to see if some
> sort of error was returned.
>
>
> Mark Post
>
> --
> 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/
>

--
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/

Re: SLES12 - yast does not create a udev rule

[Mark Post]

>>> On 11/10/2015 at 08:08 AM, "Davis, Larry (National VM Capability)"
 wrote: 
> 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

That file doesn't have anything to do with activating network interfaces.  It 
just helps make sure the names are consistent across reboots.

> I have also had to add rules for each new DASD device so it is available 
> after an IPL  or reboot

The "proper" procedure to get udev rules created is to use YaST, 
dasd_configure, or qeth_configure.  All of those should create the necessary 
udev rules, and update /boot/zipl/active_devices.txt so that they are not in 
the cio_ignore list when booting is complete.  YaST will also re-run mkinitrd 
to make sure things get put into the initrd that are needed there.


Mark Post

--
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/

Re: SLES12 - yast does not create a udev rule

[Davis, Larry (National VM Capability)]

That may be true, like I have said I am not an expert but until I did that I 
would have to manually activate the network device each time Linux was booted.
 

Larry Davis,
VM Capability

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Tuesday, November 10, 2015 9:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES12 - yast does not create a udev rule

>>> On 11/10/2015 at 08:08 AM, "Davis, Larry (National VM Capability)"
<larry.dav...@hpe.com> wrote: 
> 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

That file doesn't have anything to do with activating network interfaces.  It 
just helps make sure the names are consistent across reboots.

> I have also had to add rules for each new DASD device so it is 
> available after an IPL  or reboot

The "proper" procedure to get udev rules created is to use YaST, 
dasd_configure, or qeth_configure.  All of those should create the necessary 
udev rules, and update /boot/zipl/active_devices.txt so that they are not in 
the cio_ignore list when booting is complete.  YaST will also re-run mkinitrd 
to make sure things get put into the initrd that are needed there.


Mark Post

--
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/

--
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/

Re: SLES12 - yast does not create a udev rule

[Mark Post]

>>> On 11/10/2015 at 04:57 AM, Christer Solskogen 
wrote: 
> 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!

I've not seen that problem before.  There should be some hint of what went 
wrong in /var/log/YaST2/y2log.  Look for "qeth_configure" to see if some sort 
of error was returned.


Mark Post

--
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/

Re: SLES12 - yast does not create a udev rule

[Davis, Larry (National VM Capability)]

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/

Re: SLES12 - yast does not create a udev rule

[Harley Linker]

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.