Re: [CentOS] Nvidia-detect error with on HP Z4 (CentOS 6.9)

[Danny Smit]

On Fri, Apr 13, 2018 at 8:50 PM, Phil Perry  wrote:
>
> Your device is supported:
>
> $ nvidia-detect -l | grep -i 1cb2
> [10de:1cb2] NVIDIA Corporation GP107GL [Quadro P600]
>
> Support was added in the 375.39 NVIDIA driver. I assume the driver works as
> expected for you?

Yes it works perfectly fine.

> If you are able to offer any more clues, please feel free to open a bug
> report on elrepo.org/bugs for us to track. Happy to help if I can.
>

I created a bugreport: http://elrepo.org/bugs/view.php?id=839

>># lspci | grep VGA
>>00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4
>>21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1
>>
>># lspci -n | egrep '00:1f.5|21:00.0'
>>00:1f.5 : 8086:a2a4
>>21:00.0 0300: 10de:1cb2 (rev a1)

This part makes me wander though, if I'm correct the second column in
the "lspci -n" output seems to be the class identification. If you
look at the first line of the lcpi output, lspci (or the kernel?)
doesn't seem to recognize the class of some other Intel device, that
probably has nothing to do with the nvidia device at all. It's numeric
class identification seems to be "" though (for unclassified?)

Could it be that in the piece of code below (from nvidia-detect), the
device_class is zero because of that line, and nvidia-detect exits?

if (!dev->device_class) {
fprintf(stderr, "Error getting device_class\n");
ret = -1;
goto exit;
}

-- 
Regards,
Danny
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Nvidia-detect error with on HP Z4 (CentOS 6.9)

[Phil Perry]

On 13/04/18 16:21, Danny Smit wrote:

Hi all,



Hi Danny, I'm the author of nvidia-detect.


I'm testing an installation of nvidia drivers on a HP Z4 workstation
(nvidia Quadro P600) with CentOS 6.9. Running nvidia-detect with this
setup gives the following output:

   # nvidia-detect
   Error getting device_class



nvidia-detect scans the pci bus and checks the returned device_class for 
display controllers. In your case, the scan is not returning any devices 
(or rather the device_class for any pci devices)



nvidia-detect also quits with exit-code 255.


The internal error checking is displaying the above error message and 
exiting with the appropriate error code, as intended.



Could this be a bug in nvidia-detect? Or is it an unsupported configuration?



Good question, and I've no idea why it's not working on your machine.


The following hardware is detected, it seems some sort of unknown
Intel device is detected by the OS:

   # lspci | grep VGA
   00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4
   21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1)

   # lspci -n | egrep '00:1f.5|21:00.0'
   00:1f.5 : 8086:a2a4
   21:00.0 0300: 10de:1cb2 (rev a1)

Tested with the following version (with equal results):

   nvidia-detect-390.25-1.el6.elrepo.x86_64.rpm
   nvidia-detect-390.48-1.el6.elrepo.x86_64.rpm



Your device is supported:

$ nvidia-detect -l | grep -i 1cb2
[10de:1cb2] NVIDIA Corporation GP107GL [Quadro P600]

Support was added in the 375.39 NVIDIA driver. I assume the driver works 
as expected for you?


If you are able to offer any more clues, please feel free to open a bug 
report on elrepo.org/bugs for us to track. Happy to help if I can.


Phil
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Nvidia-detect error with on HP Z4 (CentOS 6.9)

[Akemi Yagi]

On Fri, Apr 13, 2018 at 8:21 AM, Danny Smit  wrote:
> Hi all,
>
> I'm testing an installation of nvidia drivers on a HP Z4 workstation
> (nvidia Quadro P600) with CentOS 6.9. Running nvidia-detect with this
> setup gives the following output:
>
>   # nvidia-detect
>   Error getting device_class
>
> nvidia-detect also quits with exit-code 255.
> Could this be a bug in nvidia-detect? Or is it an unsupported configuration?
>
> The following hardware is detected, it seems some sort of unknown
> Intel device is detected by the OS:
>
>   # lspci | grep VGA
>   00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4
>   21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1)
>
>   # lspci -n | egrep '00:1f.5|21:00.0'
>   00:1f.5 : 8086:a2a4
>   21:00.0 0300: 10de:1cb2 (rev a1)
>
> Tested with the following version (with equal results):
>
>   nvidia-detect-390.25-1.el6.elrepo.x86_64.rpm
>   nvidia-detect-390.48-1.el6.elrepo.x86_64.rpm
>
> --
> Regards,
> Danny

You want to post this to the elrepo mailing list.

Akemi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Nvidia-detect error with on HP Z4 (CentOS 6.9)

[Danny Smit]

Hi all,

I'm testing an installation of nvidia drivers on a HP Z4 workstation
(nvidia Quadro P600) with CentOS 6.9. Running nvidia-detect with this
setup gives the following output:

  # nvidia-detect
  Error getting device_class

nvidia-detect also quits with exit-code 255.
Could this be a bug in nvidia-detect? Or is it an unsupported configuration?

The following hardware is detected, it seems some sort of unknown
Intel device is detected by the OS:

  # lspci | grep VGA
  00:1f.5 Non-VGA unclassified device: Intel Corporation Device a2a4
  21:00.0 VGA compatible controller: NVIDIA Corporation Device 1cb2 (rev a1)

  # lspci -n | egrep '00:1f.5|21:00.0'
  00:1f.5 : 8086:a2a4
  21:00.0 0300: 10de:1cb2 (rev a1)

Tested with the following version (with equal results):

  nvidia-detect-390.25-1.el6.elrepo.x86_64.rpm
  nvidia-detect-390.48-1.el6.elrepo.x86_64.rpm

-- 
Regards,
Danny
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

[m . roth]

Toralf Lund wrote:
> Hi,
>
> I just found myself having to set up a new CentOS 6 system with a nearly
> identical configuration to an existing host, so I thought I would just
>
>  1. Do a minimal install to set up partitions etc. on the new system.
>  2. Create an image of the existing system using Clonezilla
> (http://www.clonezilla.org)
>  3. Run a Clonezilla restore on the new system.
>
> - as I though it would be a lot simpler than replicating the exact
> package selection, installing the same users, doing the same manual
> config edits (which are required) etc.
>
> It turns out that it wasn't quite as easy, though. The problem is that
> the system use LVM2 volumes for the filesystems, and the new host has a
> slightly smaller disk than the other, and Clonezilla seems unable to
> restore to a volume that's smaller than the one that was cloned - even
> if the actual data fits.
>
> I guess I could temporarily reduce the LVM volume sizes on the existing
> units and clone again, but I'd rather not if I can avoid it. Just
> copying file-by-file could be an option, too, but I somehow feel less
> comfortable doing that than the above; there is something about the way
> I could end up with a mixture of my "minimal install" and the "cloned"
> data, I suppose.
>
> Does anyone have any other ideas about how I might achieve what I want?

Manually clone it.

On the new machine:
mkdir /new
mkdir /boot/new
rsync -HPavzx --exclude=/old --exclude=/var/log/wtmp $machine:/. /new/.
rsync -HPavzx $machine:/boot/. /boot/new/.

where $machine is the system you're cloning from. You might want to
exclude other logfiles.

To prevent problems with the Ethernet interfaces:

rsync -HPavzx /etc/sysconfig/network-scripts/ifcfg-eth*
/new/etc/sysconfig/network-scripts
rsync -HPavzx /etc/sysconfig/hwconf /new/etc/sysconfig
rsync -HPavzx /boot/grub/device.map /boot/new/grub/
rsync -HPavzx /etc/udev/rules.d/70-persistent-net.rules
/new/etc/udev/rules.d/

Clean log files - you don't really want any of the old systems:

find /new/var/log/ -type f -exec cp /dev/null {} \;

Copy the original SSH keys - you do *not* want the keys of the system
you're cloning from:

rsync -HPavzx /etc/ssh/ssh_host* /new/etc/ssh

Now rotate: zsh, because it lets you load it's builtin-s, so mv works

zsh
zmodload zsh/files

cd /boot
mkdir old
mv * old
mv old/lost+found .
mv old/new/* .

# Root partition.
cd /
mkdir old
mv * old
mv old/lost+found .
#mv old/root . -- WHY?
mv old/scratch .
mv old/new/* .

sync
sync

Also you might want to

  touch /.autorelabel

to shut up selinux.

Note that this assumes the same CPU, etc, Otherwise, you might need to
make a new initrd.

  mark

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [Marketing Mail] Re: [External] Re: [Marketing Mail] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

[Lange, Markus]

Hi,

I could be wrong, but afaik clonezilla makes bit-accurate copies of the file
system like dd does. Therefore, no configurations should be adapted. Usually
Linux doesn't care where it runs, as long as the underlying 'hardware' (or
virtual hardware) architecture matches.

However, there are a number of configuration files that need to be modified for
such clones, including network settings (local or on your dhcp server),
{crypt,fs}tab (if no bit-accurate copy of the filesystem was used),
/etc/host{s,name} depending on your network setup.

best regards,
 - MarkusOn Fr, 2018-04-13 at 15:45 +0200, Toralf Lund wrote:
> On 13/04/18 15:32, Lange, Markus wrote:
> > 
> > Hi,
> > 
> > You can simply boot a live system to create your partition layout and copy
> > it
> > over the existing system with rsync. Once your system is copied, you will
> > need
> > to customize all hardware-dependent configuration files such as
> > {crypt,fs}tab,
> > network configurations, bootloader and so on depending on your setup.
> > 
> > Don't forget to install the bootloader afterwards!
> > 
> > You can also install a minimal system and use a live system to copy the
> > files
> > from the existing server to the new one (e.g. with rsync -a). This way you
> > do
> > not have to create the partition layout and bootloader manually.
> > 
> > Using clonezilla would only replace the part of copying the files and
> > installing
> > the bootloader, all other settings still have to be made.
> Actually, I don't believe that's quite true. I've "cloned" to dissimilar 
> hardware in the same manner before, and found that there was special 
> handling of various hardware dependent config files, so that I didn't 
> get set-up  for the "wrong" type.
> 
> - Toralf
> 
> > 
> >   Rsync should be much
> > faster for data transfer.
> > 
> > Best regards,
> >   - Markus
> > On Fr, 2018-04-13 at 14:46 +0200, Toralf Lund wrote:
> > > 
> > > Hi,
> > > 
> > > I just found myself having to set up a new CentOS 6 system with a nearly
> > > identical configuration to an existing host, so I thought I would just
> > > 
> > >   1. Do a minimal install to set up partitions etc. on the new system.
> > >   2. Create an image of the existing system using Clonezilla
> > >  (https://urldefense.proofpoint.com/v2/url?u=http-3A__www.clonezilla.o
> > > rg=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q0oqxzgUp3xCCI
> > > iJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-
> > > Vakjf6lKeZVlmfp_AaqPakYDOV1c=7DzBbYmBU7fUsxgvVL-
> > > 59HG_y2uuwR1jxcbXX5skfGM= )
> > >   3. Run a Clonezilla restore on the new system.
> > > 
> > > - as I though it would be a lot simpler than replicating the exact
> > > package selection, installing the same users, doing the same manual
> > > config edits (which are required) etc.
> > > 
> > > It turns out that it wasn't quite as easy, though. The problem is that
> > > the system use LVM2 volumes for the filesystems, and the new host has a
> > > slightly smaller disk than the other, and Clonezilla seems unable to
> > > restore to a volume that's smaller than the one that was cloned - even
> > > if the actual data fits.
> > > 
> > > I guess I could temporarily reduce the LVM volume sizes on the existing
> > > units and clone again, but I'd rather not if I can avoid it. Just
> > > copying file-by-file could be an option, too, but I somehow feel less
> > > comfortable doing that than the above; there is something about the way
> > > I could end up with a mixture of my "minimal install" and the "cloned"
> > > data, I suppose.
> > > 
> > > Does anyone have any other ideas about how I might achieve what I want?
> > > 
> > > - Toralf
> > > 
> > > ___
> > > CentOS mailing list
> > > CentOS@centos.org
> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mail
> > > man_listinfo_centos=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ
> > > =Q0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-
> > > Vakjf6lKeZVlmfp_AaqPakYDOV1c=qjiIy57nu_S3OjTO1LYJjQmDFY6GkzLkKvn2F5IrUqo
> > > =
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailma
> > n_listinfo_centos=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q
> > 0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-
> > Vakjf6lKeZVlmfp_AaqPakYDOV1c=qjiIy57nu_S3OjTO1LYJjQmDFY6GkzLkKvn2F5IrUqo
> > =
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] YUM4/DNF for CentOS updates announcement

[Marek Blaha]

I am pleased to announce some significant updates to our ConfigManagement
Special Interest Group for YUM4. This provides YUM4, based on DNF
technology, for testing on CentOS Linux 7/x86_64. These updates are based
on feedback from our prior test release last October. It includes signed
packages, core DNF plugins, and uses a version of RPM very similar to and
compatible with the upcoming version of CentOS 7.5.

This initiative is based on a partnership with the upstream YUM and DNF
maintainers for the future of package management. Our testing thus far
indicates no major problems, but we would love to find out how it fits into
your existing YUM 3 workflows. So please consider filling out the short
survey - your feedback helps us all get better.

YUM 4 provides significant improvements such as fast dependency resolution
and a stable, documented API. See the references below for detailed
improvements. We have made every effort to preserve the existing end-user
experience that is available with YUM 3. This is the primary reason for
making YUM 4 available for testing now.

For detailed information and instructions to install YUM4 on your CentOS
machine, please visit our wiki:
https://wiki.centos.org/SpecialInterestGroup/ConfigManagementSIG/YUM4

And remember to submit feedback in the short survey to help us understand
how it can be improved further:
https://goo.gl/forms/H1SL1HaEjdV9EUGH3

Many thanks to the CentOS Project team for their assistance in making this
happen!

Regards,

Marek Blaha
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [External] Re: [Marketing Mail] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

[Toralf Lund]

On 13/04/18 15:32, Lange, Markus wrote:

Hi,

You can simply boot a live system to create your partition layout and copy it
over the existing system with rsync. Once your system is copied, you will need
to customize all hardware-dependent configuration files such as {crypt,fs}tab,
network configurations, bootloader and so on depending on your setup.

Don't forget to install the bootloader afterwards!

You can also install a minimal system and use a live system to copy the files
from the existing server to the new one (e.g. with rsync -a). This way you do
not have to create the partition layout and bootloader manually.

Using clonezilla would only replace the part of copying the files and installing
the bootloader, all other settings still have to be made.
Actually, I don't believe that's quite true. I've "cloned" to dissimilar 
hardware in the same manner before, and found that there was special 
handling of various hardware dependent config files, so that I didn't 
get set-up  for the "wrong" type.


- Toralf


  Rsync should be much
faster for data transfer.

Best regards,
  - Markus
On Fr, 2018-04-13 at 14:46 +0200, Toralf Lund wrote:

Hi,

I just found myself having to set up a new CentOS 6 system with a nearly
identical configuration to an existing host, so I thought I would just

  1. Do a minimal install to set up partitions etc. on the new system.
  2. Create an image of the existing system using Clonezilla
 
(https://urldefense.proofpoint.com/v2/url?u=http-3A__www.clonezilla.org=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-Vakjf6lKeZVlmfp_AaqPakYDOV1c=7DzBbYmBU7fUsxgvVL-59HG_y2uuwR1jxcbXX5skfGM=
 )
  3. Run a Clonezilla restore on the new system.

- as I though it would be a lot simpler than replicating the exact
package selection, installing the same users, doing the same manual
config edits (which are required) etc.

It turns out that it wasn't quite as easy, though. The problem is that
the system use LVM2 volumes for the filesystems, and the new host has a
slightly smaller disk than the other, and Clonezilla seems unable to
restore to a volume that's smaller than the one that was cloned - even
if the actual data fits.

I guess I could temporarily reduce the LVM volume sizes on the existing
units and clone again, but I'd rather not if I can avoid it. Just
copying file-by-file could be an option, too, but I somehow feel less
comfortable doing that than the above; there is something about the way
I could end up with a mixture of my "minimal install" and the "cloned"
data, I suppose.

Does anyone have any other ideas about how I might achieve what I want?

- Toralf

___
CentOS mailing list
CentOS@centos.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-Vakjf6lKeZVlmfp_AaqPakYDOV1c=qjiIy57nu_S3OjTO1LYJjQmDFY6GkzLkKvn2F5IrUqo=

___
CentOS mailing list
CentOS@centos.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.centos.org_mailman_listinfo_centos=DwIGaQ=KV_I7O14pmwRcmAVyJ1eg4Jwb8Y2JAxuL5YgMGHpjcQ=Q0oqxzgUp3xCCIiJDwS-RbNDndQ-KZDhj8wwveNoqU4=LuCuhEh29vlP9l-Vakjf6lKeZVlmfp_AaqPakYDOV1c=qjiIy57nu_S3OjTO1LYJjQmDFY6GkzLkKvn2F5IrUqo=



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [Marketing Mail] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

[Lange, Markus]

Hi,

You can simply boot a live system to create your partition layout and copy it
over the existing system with rsync. Once your system is copied, you will need
to customize all hardware-dependent configuration files such as {crypt,fs}tab,
network configurations, bootloader and so on depending on your setup.

Don't forget to install the bootloader afterwards!

You can also install a minimal system and use a live system to copy the files
from the existing server to the new one (e.g. with rsync -a). This way you do
not have to create the partition layout and bootloader manually.

Using clonezilla would only replace the part of copying the files and installing
the bootloader, all other settings still have to be made. Rsync should be much
faster for data transfer.

Best regards,
 - Markus
On Fr, 2018-04-13 at 14:46 +0200, Toralf Lund wrote:
> Hi,
> 
> I just found myself having to set up a new CentOS 6 system with a nearly 
> identical configuration to an existing host, so I thought I would just
> 
>  1. Do a minimal install to set up partitions etc. on the new system.
>  2. Create an image of the existing system using Clonezilla
> (http://www.clonezilla.org)
>  3. Run a Clonezilla restore on the new system.
> 
> - as I though it would be a lot simpler than replicating the exact 
> package selection, installing the same users, doing the same manual 
> config edits (which are required) etc.
> 
> It turns out that it wasn't quite as easy, though. The problem is that 
> the system use LVM2 volumes for the filesystems, and the new host has a 
> slightly smaller disk than the other, and Clonezilla seems unable to 
> restore to a volume that's smaller than the one that was cloned - even 
> if the actual data fits.
> 
> I guess I could temporarily reduce the LVM volume sizes on the existing 
> units and clone again, but I'd rather not if I can avoid it. Just 
> copying file-by-file could be an option, too, but I somehow feel less 
> comfortable doing that than the above; there is something about the way 
> I could end up with a mixture of my "minimal install" and the "cloned" 
> data, I suppose.
> 
> Does anyone have any other ideas about how I might achieve what I want?
> 
> - Toralf
> 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Create CentOS 6 system as "clone" of another - with LVM and different disk sizes

[Toralf Lund]

Hi,

I just found myself having to set up a new CentOS 6 system with a nearly 
identical configuration to an existing host, so I thought I would just


1. Do a minimal install to set up partitions etc. on the new system.
2. Create an image of the existing system using Clonezilla
   (http://www.clonezilla.org)
3. Run a Clonezilla restore on the new system.

- as I though it would be a lot simpler than replicating the exact 
package selection, installing the same users, doing the same manual 
config edits (which are required) etc.


It turns out that it wasn't quite as easy, though. The problem is that 
the system use LVM2 volumes for the filesystems, and the new host has a 
slightly smaller disk than the other, and Clonezilla seems unable to 
restore to a volume that's smaller than the one that was cloned - even 
if the actual data fits.


I guess I could temporarily reduce the LVM volume sizes on the existing 
units and clone again, but I'd rather not if I can avoid it. Just 
copying file-by-file could be an option, too, but I somehow feel less 
comfortable doing that than the above; there is something about the way 
I could end up with a mixture of my "minimal install" and the "cloned" 
data, I suppose.


Does anyone have any other ideas about how I might achieve what I want?

- Toralf

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Help with yum

[Liam O'Toole]

On 2018-04-13, Paul R. Ganci
 wrote:

[...]

> Then it was just a matter of:
>
> > yum groupinstall "MATE Desktop"
> > systemctl set-default graphical.target
> > reboot
>
> Voila... I have a desktop running MATE!

Glad you got it working.

I thought I'd mention that the reboot is not strictly necessary. The
command

yum isolate graphical.target

will switch the system immediately to the named target.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos