[CentOS] Adjust type of rw in submit_bio from int to unsigned long

[wuzhouhui]

Hi, I am a developer who worked on CentOS. Recently I am working on porting one 
of my
block drivers from CentOS 6.x to CentOS 7.x. In newest kernel 
(kernel-3.10.0-693.17.1.el7)
I found there is an issue in submit_bio()'s first argument:
void submit_bio(int rw, struct bio *bio)
The type of bi_rw of struct bio is unsigned long, and the number of enum 
rq_flags_bits
also exceeds 32, so we should better using unsigned long for rw in 
submit_bio(), like:
void submit_bio(unsigned long rw, struct bio *bio)


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

Re: [CentOS] Allowing non-root users to reboot a workstation

[James Hogarth]

On 2 February 2018 at 18:13,   wrote:
> Felipe Westfields wrote:
>> I would like to be able to allow regular users that don't have admin
>> privileges to be able to reboot their workstation. (they're software
>> developers so rebooting their workstation doesn't affect anybody else)
>>
>> I tried changing the ownership of /sbin/reboot and /sbin/shutdown to
>> root:users and permissions to 550, but that didn't work - it's still
>> asking
>> for root privileges.
>>
>> Possibly the problem might be that there's centralized LDAP
>> authentication, not local, so the changes I made only apply to
>> local accounts?
>>
>> Any suggestions?
>
> Um, I take it that a three-finger kill doesn't work?
>
>mark
>

You;ll want to look at polkit configuration as that's what is used by
systemd, and by gnome as a result, to determine what actions are
permitted

https://www.hogarthuk.com/?q=node/10
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Issues with NVidia video driver and CentOS

[Felipe Westfields]

We do have the elrepo drivers installed. Maybe part of the problem is also
that we're using an IOgear KVM switch?

On Tue, Feb 6, 2018 at 11:58 AM, Phelps, Matthew 
wrote:

> On Tue, Feb 6, 2018 at 11:40 AM, Felipe Westfields <
> felipe.westfie...@gmail.com> wrote:
>
> > I'm having issues with a quad video card on CentOS.
> >
> > We have several systems on CentOS 6.8 and CentOS 6.9. The installed
> > hardware is:
> >
> > Video card - Nvidia NVS quadro 440
> > PC - Dell OptiPlex 9020
> >
> > Whenever you update the kernel, it kills the graphical interface. The
> > system appears to lock up and freeze during a reboot, but you can still
> get
> > into it with SSH, or, if you're at the console, control-alt-F2 gets you
> to
> > a command prompt.
> >
> > If you exclude the kernel update when applying yum update, it is usually
> > fine. If the kernel update is applied, and you roll back the update, that
> > sometimes gets you back into the graphical console, but more likely than
> > not, it won't.
> >
> > Not sure where to go with this.
> >
> > Any suggestions?
> >
> > FW
> > ___
> >
>
> Which version of the driver? How did you install it?
>
> If you're not already using it, I heartily recommend using the ELRepo
> repository, http://elrepo.org/tiki/. We have several dozen CO 6.9 machines
> with various Nvidia cards and except for a recent version that had an issue
> with DVI connections (not the repository's fault), we haven't had any
> problems.
>
> --
> Matt Phelps
> System Administrator, Computation Facility
> Harvard - Smithsonian Center for Astrophysics
> mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
> ___
> 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

Re: [CentOS] kmod c74 broken: howto report it

[Stijn De Weirdt]

hi akemi,

i also forgot about this thread. we already tested the latest kmod last
week and it indeed fixes the issue.

still no clue how to report issues to centos team to doublecheck
packaging mishaps...

stijn

On 02/06/2018 12:49 AM, Akemi Yagi wrote:
> On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi  wrote:
>>
>> On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt  
>> wrote:
> 
>>> latest kmod update 20-15.el7_4.6 is broken on our systems, while
>>> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue).
>>>
>>> the issue is with modules from mellanox kmod rpms that are symlinked in
>>> the weak-updates dir. the config files in /etc/depmod.d look ok (and do
>>> work with previous version): dist.conf has weak-updates after built-in,
>>> and mellanox kmod rpms ship a config that overrides it for all modules.
> 
>> A little late in getting back to your post ...
>>
>> This issue was reported upstream at RH and is being worked on:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1522994
>>
>> Hopefully the fixed version comes out soon.
> 
> For the record, it was fixed in kmod-20-15.el7_4.7 :
> 
> https://access.redhat.com/errata/RHBA-2018:0159
> 
> Akemi
> ___
> 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

Re: [CentOS] Issues with NVidia video driver and CentOS

[Phelps, Matthew]

On Tue, Feb 6, 2018 at 11:40 AM, Felipe Westfields <
felipe.westfie...@gmail.com> wrote:

> I'm having issues with a quad video card on CentOS.
>
> We have several systems on CentOS 6.8 and CentOS 6.9. The installed
> hardware is:
>
> Video card - Nvidia NVS quadro 440
> PC - Dell OptiPlex 9020
>
> Whenever you update the kernel, it kills the graphical interface. The
> system appears to lock up and freeze during a reboot, but you can still get
> into it with SSH, or, if you're at the console, control-alt-F2 gets you to
> a command prompt.
>
> If you exclude the kernel update when applying yum update, it is usually
> fine. If the kernel update is applied, and you roll back the update, that
> sometimes gets you back into the graphical console, but more likely than
> not, it won't.
>
> Not sure where to go with this.
>
> Any suggestions?
>
> FW
> ___
>

Which version of the driver? How did you install it?

If you're not already using it, I heartily recommend using the ELRepo
repository, http://elrepo.org/tiki/. We have several dozen CO 6.9 machines
with various Nvidia cards and except for a recent version that had an issue
with DVI connections (not the repository's fault), we haven't had any
problems.

-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Issues with NVidia video driver and CentOS

[Mikhail Utin]

I think that it is more about the card than the kernel. You may try to install 
different card to test. I would report that to Nvidia. You may also try how it 
works in CentOS 7. Time to move on? I also use 6.9 but in plain configuration.


Mikhail Utin



From: CentOS  on behalf of Felipe Westfields 

Sent: Tuesday, February 6, 2018 11:40
To: CentOS mailing list
Subject: [CentOS] Issues with NVidia video driver and CentOS

I'm having issues with a quad video card on CentOS.

We have several systems on CentOS 6.8 and CentOS 6.9. The installed
hardware is:

Video card - Nvidia NVS quadro 440
PC - Dell OptiPlex 9020

Whenever you update the kernel, it kills the graphical interface. The
system appears to lock up and freeze during a reboot, but you can still get
into it with SSH, or, if you're at the console, control-alt-F2 gets you to
a command prompt.

If you exclude the kernel update when applying yum update, it is usually
fine. If the kernel update is applied, and you roll back the update, that
sometimes gets you back into the graphical console, but more likely than
not, it won't.

Not sure where to go with this.

Any suggestions?

FW
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
CentOS Info Page
lists.centos.org
This is a General discussion list for all issues CentOS. Security updates are 
currently announced on this list once daily. This list is read and reply for 
anyone that ...



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

[CentOS] Issues with NVidia video driver and CentOS

[Felipe Westfields]

I'm having issues with a quad video card on CentOS.

We have several systems on CentOS 6.8 and CentOS 6.9. The installed
hardware is:

Video card - Nvidia NVS quadro 440
PC - Dell OptiPlex 9020

Whenever you update the kernel, it kills the graphical interface. The
system appears to lock up and freeze during a reboot, but you can still get
into it with SSH, or, if you're at the console, control-alt-F2 gets you to
a command prompt.

If you exclude the kernel update when applying yum update, it is usually
fine. If the kernel update is applied, and you roll back the update, that
sometimes gets you back into the graphical console, but more likely than
not, it won't.

Not sure where to go with this.

Any suggestions?

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

[CentOS] libsmbclient conflict problem

[me]

Hi,

I have a c-6 machine that I noticed the following on:

(bugs pts10) # package-cleanup --problems
Loaded plugins: fastestmirror, priorities, refresh-packagekit
Package system-config-printer-libs-1.1.16-26.el6.x86_64 requires 
libsmbclient.so.0()(64bit)
Package kdebase-runtime-libs-4.3.4-9.el6.x86_64 requires 
libsmbclient.so.0()(64bit)

So then I ran:

(bugs pts10) # yum install libsmbclient
Loaded plugins: changelog, fastestmirror, priorities, refresh-packagekit
Setting up Install Process
Loading mirror speeds from cached hostfile
 * base: yumrepo
 * extras: yumrepo
 * fasttrack: yumrepo
 * remi: mirror.team-cymru.org
 * remi-php56: mirror.team-cymru.org
 * updates: yumrepo
138 packages excluded due to repository priority protections
Resolving Dependencies
--> Running transaction check
---> Package libsmbclient.x86_64 0:3.6.23-46el6_9 will be installed
--> Processing Dependency: samba-winbind-clients = 3.6.23-46el6_9 for package: 
libsmbclient-3.6.23-46el6_9.x86_64
--> Processing Dependency: libwbclient.so.0()(64bit) for package: 
libsmbclient-3.6.23-46el6_9.x86_64
--> Running transaction check
---> Package samba-winbind-clients.x86_64 0:3.6.23-46el6_9 will be installed
--> Processing Dependency: samba-winbind = 3.6.23-46el6_9 for package: 
samba-winbind-clients-3.6.23-46el6_9.x86_64
--> Running transaction check
---> Package samba-winbind.x86_64 0:3.6.23-46el6_9 will be installed
--> Processing Dependency: samba-common = 3.6.23-46el6_9 for package: 
samba-winbind-3.6.23-46el6_9.x86_64
--> Running transaction check
---> Package samba-common.x86_64 0:3.6.23-46el6_9 will be installed
--> Processing Conflict: samba4-common-4.2.10-12.el6_9.x86_64 conflicts 
samba-common < 3.9.9
--> Processing Conflict: samba4-winbind-4.2.10-12.el6_9.x86_64 conflicts 
samba-winbind < 3.9.9
--> Processing Conflict: samba4-winbind-clients-4.2.10-12.el6_9.x86_64 conflicts 
samba-winbind-clients < 3.9.9
--> Finished Dependency Resolution
--> Finding unneeded leftover dependencies
Found and removing 0 unneeded dependencies
Error: samba4-winbind conflicts with samba-winbind-3.6.23-46el6_9.x86_64
Error: samba4-winbind-clients conflicts with 
samba-winbind-clients-3.6.23-46el6_9.x86_64
Error: samba4-common conflicts with samba-common-3.6.23-46el6_9.x86_64
 You could try using --skip-broken to work around the problem
** Found 2 pre-existing rpmdb problem(s), 'yum check' output follows:
kdebase-runtime-libs-4.3.4-9.el6.x86_64 has missing requires of 
libsmbclient.so.0()(64bit)
system-config-printer-libs-1.1.16-26.el6.x86_64 has missing requires of 
libsmbclient.so.0()(64bit)
(bugs pts10) #

I have the following samba packages installed:

(bugs pts10) # rpm -qa samba4\*
samba4-winbind-clients-4.2.10-12.el6_9.x86_64
samba4-4.2.10-12.el6_9.x86_64
samba4-client-4.2.10-12.el6_9.x86_64
samba4-common-4.2.10-12.el6_9.x86_64
samba4-winbind-4.2.10-12.el6_9.x86_64
samba4-libs-4.2.10-12.el6_9.x86_64
(bugs pts10)

Can someone tell me what what I need to do to resolve the above conflicts?

There does not seem to be a later version of libsmbclient available.

Regards,

--
Tom m...@tdiehl.org
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Slightly OT : newsletters, mail formatting and netiquette

[hw]

Nicolas Kovacs wrote:

Hi,

This question is not exactly CentOS-related strictly speaking, but here
goes. I'm running a few newsletter servers for myself and a handful of
clients on public CentOS servers with PHPList.

For the last twenty years or so I've followed the basic rule that mails
should have no formatting whatsoever, only simple text. And now I wonder
if that basic rule of netiquette also applies to newsletters.

I'm a subscriber to a series of tech-related newsletters, and I couldn't
help but notice that they all seem to be HTML-formatted, even those from
respectable hardcore geek groups.

So my somewhat naive question: is HTML formatting acceptable in
newsletters?


Most so-called "newsletters" nowadays are only a collection of URLs and do not
contain any news or any information at all.  That totally defeats the purpose
of a newsletter and makes them entirely useless.

So no, it´s unacceptable.  HTML mail automatically goes into my spam folder
anyway, and I avoid subscribing to so-called "newsletters".
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Re-enable grub boot in UEFI (Windows took over it)

[Kay Diederichs]

On 02/05/2018 09:10 PM, Chris Murphy wrote:
> On Mon, Feb 5, 2018 at 8:27 AM, Kay Diederichs
>  wrote:
> 
>> grub-install /dev/nvme0n1
> 
> 
> Running this on computers with UEFI firmware is not good advice, it's
> an obsolete command. People should use the prebaked grubx64.efi binary
> that comes in the grub2-efi package, and is a signed binary so it can
> support UEFI Secure Boot.
> 
> If you run grub2-install, a new unsigned grub binary is created,
> replacing grubx64.efi. If you have Secure Boot enabled, you will not
> be able to boot, until you either reinstall the grub2-efi package (or
> you self-sign the grub2-install created binary and then go through the
> process of informing the firmware this is a valid binary by using
> mokutil - but I estimate maybe 1 in 50 people might do this).
> 
> 
> 
> 

Did you read my sentence "I recovered my Ubuntu grub menu ..." and that
this mentions grub-install, not grub2-install ? The procedure that I
describe is correct for Ubuntu - see e.g.
https://askubuntu.com/questions/831216/reinstalling-grub2-efi-partition
https://help.ubuntu.com/community/Grub2/Installing#Boot_repair_after_a_Windows_Upgrade_on_Ubuntu_14.04_.28non-RAID.29

The important point of my posting was to tell the OP the reason and
mechanism which leads to a loss of the grub menu. The OP already
described how s/he got the machine to boot again.

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