Re: [CentOS] skypeforlinux lacks dependencies, won't update

[wwp]

Hello Peter,


On Tue, 21 Nov 2017 20:39:41 +1300 Peter  wrote:

> On 21/11/17 19:55, wwp wrote:
>  Maybe. Unpacking the rpm works, anyway, I never encountered a single
>  binary issue since I use it like that (ordinary use, I probably don't
>  use that text encoding or whatever submodule which depends on a newer
>  libstdc++).
> 
> 
>  Please explain "Unpacking the RPM".  How is one to do that when there
> >>> are broken dependencies?
> >>
> >> Easy.
> >> rpm2cpio /path/to/whatever.rpm | cpio -idm
> >>
> >> Probably best to do that in a temporary directory and see what you get.
> >> See the cpio manpage for other options.  
> > 
> > Exactly. One could also install using `rpm -Uvh --nodeps
> > skypeforlinux-64-0.rpm`, that worked too even if NOT solving the dep
> > for uninstalled lib for the specific skype module.  
> 
> The issue here is that the reason it's a dep is because at least some
> component of the skype package was built against a libstdc++ that in
> turn was built against a newer glibc than that provided by CentOS 7.
> You are playing with fire trying to bypass the dep and install it
> anyways.  You are much better off getting the skype from the insider
> channel which was built without the newer library requirements.  After
> installing it you can disable the insider repo and then you'll get newer
> updates from the stable repo instead (which should hopefully work in the
> future).

I think that it's clear that installing the package that way is
potentially unsafe (well, when you know what module may crash, you
don't risk much), is tricky and just a workaround. At the time there
was no insider package that fixes it, there was no alternative but this
hack. I personally faced no issue at all w/ that workaround and am
waiting for the next stable to jump in, I consider the insider one as
less reliable.


Regards,

-- 
wwp


pgp7oW33EeSfI.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[Peter]

On 21/11/17 19:55, wwp wrote:
 Maybe. Unpacking the rpm works, anyway, I never encountered a single
 binary issue since I use it like that (ordinary use, I probably don't
 use that text encoding or whatever submodule which depends on a newer
 libstdc++).


 Please explain "Unpacking the RPM".  How is one to do that when there  
>>> are broken dependencies?  
>>
>> Easy.
>> rpm2cpio /path/to/whatever.rpm | cpio -idm
>>
>> Probably best to do that in a temporary directory and see what you get.
>> See the cpio manpage for other options.
> 
> Exactly. One could also install using `rpm -Uvh --nodeps
> skypeforlinux-64-0.rpm`, that worked too even if NOT solving the dep
> for uninstalled lib for the specific skype module.

The issue here is that the reason it's a dep is because at least some
component of the skype package was built against a libstdc++ that in
turn was built against a newer glibc than that provided by CentOS 7.
You are playing with fire trying to bypass the dep and install it
anyways.  You are much better off getting the skype from the insider
channel which was built without the newer library requirements.  After
installing it you can disable the insider repo and then you'll get newer
updates from the stable repo instead (which should hopefully work in the
future).


Peter



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[wwp]

Hello,


On Mon, 20 Nov 2017 19:22:19 -0600 Robert Nichols  
wrote:

> On 11/20/2017 07:13 PM, Mark LaPierre wrote:
> > On 11/20/17 03:44, wwp wrote:  
> >> Hello,
> >>
> >>
> >> On Mon, 20 Nov 2017 12:58:21 +1300 Peter  wrote:
> >>  
> >>> On 20/11/17 11:30, milos.blazevic wrote:  
>  There's the unstable version that installs and works:
>  https://www.skype.com/en/insider/  
> >>>
> >>> Thanks for pointing this out, it looks like they removed the newer
> >>> GLIBCXX requirement that was added for 8.10, possibly due to popular 
> >>> demand?  
> >>
> >> Maybe. Unpacking the rpm works, anyway, I never encountered a single
> >> binary issue since I use it like that (ordinary use, I probably don't
> >> use that text encoding or whatever submodule which depends on a newer
> >> libstdc++).
> >>
> >>
> > > Please explain "Unpacking the RPM".  How is one to do that when there  
> > are broken dependencies?  
> 
> Easy.
> rpm2cpio /path/to/whatever.rpm | cpio -idm
> 
> Probably best to do that in a temporary directory and see what you get.
> See the cpio manpage for other options.

Exactly. One could also install using `rpm -Uvh --nodeps
skypeforlinux-64-0.rpm`, that worked too even if NOT solving the dep
for uninstalled lib for the specific skype module.


Regards,

-- 
wwp


pgplRZ5hYuKtN.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] File access in Apache 2.4

[david]

Folks

I'm having file-access problems in Apache 2.4 under Centos 7.  In particular:

- I have a file that's readable to every user and every application, 
(writeable by only one user), but my CGI scripts cannot read it.


- Some of my CGI scripts need temporary storage for some files.  They 
are, for example, some internal log files, tnat get cleaned up over 
time, but I want to be able to look at them (as root).  Where would 
you suggest they be placed?  I've tried /tmp/my_private_files/, and 
/var/tmp/my_private_files/, but Apache fails to find even the directory.


Any suggestions?

PS:  Centos 6 had no such problems, and the file locations worked just fine.

David

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

Re: [CentOS] Announcement: 32 bit Wine repo for RHEL and CentOS 7

[Fred Smith]

On Sun, Oct 08, 2017 at 07:43:57PM +0100, Richard Grainger wrote:
> Hi all
> 
> I've created a yum repo for 32 bit wine packages on RHEL and CentOS 7:
> 
> https://harbottle.gitlab.io/wine32/7/i386/
> 
> The Wine packages work on both 32 bit and 64 bit RHEL/CentOS 7. There is no
> 32 bit version of the EPEL repo, where the standard RHEL/CentOS Wine
> packages can be found, so you may find this new repo useful if you need to
> run Windows software that requires the 32 bit version of Wine.
> 
> The packages are all built from the EPEL source RPMs.  I had to tweak the
> spec file for wine itself slightly, but for the dependencies it's all pure
> rebuilds.
> 
> Instructions:
> 
> Code:
> yum -y install https://harbottle.gitlab.io/wine32/7/i386/wine32-release.rpm
> yum -y install wine.i686
> 
> 
> Please give it a try and tell me what you think!  It probably needs more
> testing.

So I've installed it, which seemed to go fine.

so then I attempt to install Amazon Kindle Reader for PC, which 
spews errors (not unexpected, since wine is and forever will be
incomplete):

/usr/bin/wine32 Kindle_for_PC_1.17-Download.exe
wine: created the configuration directory '/home/fredex/.wine'
err:ole:marshal_object couldn't get IPSFactory buffer for interface 
{0131---c000-0046}
err:ole:marshal_object couldn't get IPSFactory buffer for interface 
{6d5140c1-7436-11ce-8034-00aa006009fa}
err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
err:ole:CoMarshalInterface Failed to marshal the interface 
{6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
err:ole:get_local_server_stream Failed: 80004002
err:ole:marshal_object couldn't get IPSFactory buffer for interface 
{0131---c000-0046}
err:ole:marshal_object couldn't get IPSFactory buffer for interface 
{6d5140c1-7436-11ce-8034-00aa006009fa}
err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hres=0x80004002
err:ole:CoMarshalInterface Failed to marshal the interface 
{6d5140c1-7436-11ce-8034-00aa006009fa}, 80004002
err:ole:get_local_server_stream Failed: 80004002
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
err:mscoree:LoadLibraryShim error reading registry key for installroot
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x6a07afa1, context 
0xa33b50, init_notify 0, handle 0x130e804): stub
fixme:iphlpapi:CancelMibChangeNotify2 (handle (nil)): stub
wine: configuration in '/home/fredex/.wine' has been updated.

so if I assume it actually installed something, how do I find it so
I can run it?

/home/fredex/.wine/drive_c/Program Files/Amazon/kindle exists, but
is empty. 

Does that mean installation failed, or that I'm too stupid
to be turned loose with a computer? :) :)

Suggestions welcomed, thanks in advance!

Fred

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
 God made him who had no sin
  to be sin for us, so that in him
 we might become the righteousness of God."
--- Corinthians 5:21 -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[Robert Nichols]

On 11/20/2017 07:13 PM, Mark LaPierre wrote:

On 11/20/17 03:44, wwp wrote:

Hello,


On Mon, 20 Nov 2017 12:58:21 +1300 Peter  wrote:


On 20/11/17 11:30, milos.blazevic wrote:

There's the unstable version that installs and works:
https://www.skype.com/en/insider/


Thanks for pointing this out, it looks like they removed the newer
GLIBCXX requirement that was added for 8.10, possibly due to popular demand?


Maybe. Unpacking the rpm works, anyway, I never encountered a single
binary issue since I use it like that (ordinary use, I probably don't
use that text encoding or whatever submodule which depends on a newer
libstdc++).




Please explain "Unpacking the RPM".  How is one to do that when there
are broken dependencies?


Easy.
   rpm2cpio /path/to/whatever.rpm | cpio -idm

Probably best to do that in a temporary directory and see what you get.
See the cpio manpage for other options.

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.

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

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[Mark LaPierre]

On 11/20/17 03:44, wwp wrote:
> Hello,
> 
> 
> On Mon, 20 Nov 2017 12:58:21 +1300 Peter  wrote:
> 
>> On 20/11/17 11:30, milos.blazevic wrote:
>>> There's the unstable version that installs and works:
>>> https://www.skype.com/en/insider/  
>>
>> Thanks for pointing this out, it looks like they removed the newer
>> GLIBCXX requirement that was added for 8.10, possibly due to popular demand?
> 
> Maybe. Unpacking the rpm works, anyway, I never encountered a single
> binary issue since I use it like that (ordinary use, I probably don't
> use that text encoding or whatever submodule which depends on a newer
> libstdc++).
> 
> 

Please explain "Unpacking the RPM".  How is one to do that when there
are broken dependencies?

-- 
_
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/




signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] grub To grub2 Migration

[Eugene Poole]

I'm trying to move to CentOS 7.  One of my concerns is how to make the 
changes to grub that supports booting from either of the disk partitions 
that make up /dev/md0 (/dev/sda1 and /dev/sdb1) or whatever it would be 
under CentOS 7.


Is there some document or tutorial available on making the move from 
CentOS 6 to CentOS 7?


--
Eugene Poole
Woodstock, Georgia

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

Re: [CentOS-es] DHCP por departamentos usando MacAdress

[LLANO, Venzy (Cuba)]

Puedes usar VLAN y DHCP helper en el switch para lograrlo. 

-Mensaje original-
De: CentOS-es [mailto:centos-es-boun...@centos.org] En nombre de Fermin 
Francisco
Enviado el: sábado, 18 de noviembre de 2017 11:03 a.m.
Para: centos-es@centos.org
Asunto: [CentOS-es] DHCP por departamentos usando MacAdress

Buenos días!!
Tengo una pregunta y la cuales la siguiente:
Puede uno configurar un DHCP por departamento?
Ejemplo:
Departamento de contabilidad ip dinamico 192.168.80.1 hasta 
192.168.80.20Departamento de recursos humanos ip dinámico 192.168.80.21 hasta 
192.168.80.30Departamento de Tecnología ip dinámico 192.168.80.31 hasta 
192.168.80.45 Una idea que tengo es que se estas direcciones ip se generaran 
por departamento gracias a que se tienen la dirección MacAddress de la tarjeta 
de red de cada PC registradas en un archivo o algo así, de manera organizada 
para que no tome el rango de ip de otro departamento.
Se podrá realizar algo así??


José Fermín Francisco Ferreras Registered User #579535 (LinuxCounter.net) 
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[Peter]

On 21/11/17 02:21, milos.blazevic wrote:
> Judging by the comments in the original announcement:
> https://answers.microsoft.com/en-us/skype/forum/skype_linux-skype_startms-skype_installms/the-new-skype-for-desktop-is-here/dba5e41b-126a-4221-9e28-e1266d235689?auth=1
> I'd say yes.
> 
> Sadly, no one from M$/Skype team bothered to point us in the right
> direction.

I'm impressed that they listened at all.


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

[CentOS-es] Migrar openfire

[Roberto Bermúdez]

Saludos a todos de la comunidad, esperando que todos se encuentren de lo
mejor, me dirijo a ustedes para hacerles una consulta, saben se alguna
manera para poder migrar openfire de un servidor a otro? Pues necesito
hacerlo y no perder ni las credenciales de los usuarios ni los históricos
que se han guardado hasta la fecha, agradezco de antemano sus comentarios
que siempre son bienvenidos


Att
Roger
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS] CentOS Atomic and OpsWorks?

[Dave Johansen]

Has anyone used CentOS Atomic with OpsWorks? My searches on the internet
haven't turned anything up, so I wanted to see if there was any
experience/advice on here.
Thanks,
Dave
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4

[Valeri Galtsev]

On Mon, November 20, 2017 7:13 am, Johnny Hughes wrote:
> On 11/20/2017 05:23 AM, Kretschmer, Jens wrote:
>> Hi Mark,
>>
>> did you manage to sort out messages from Dracut and /sbin/weak-modules
>> you received while installing kmod-nvidia? We get the same messages
>> while installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4
>> with the kernel 3.10.0-693.5.2.el7.x86_64.
>>
>
> weak modules allow modules built on one kernel version to apply to
> another kernel as long as the 'build dependencies' are the same.  There
> are many individual drivers,

My comment here may seem to be completely off topic. However:

it is not nvidia driver that you, folks, build/compile. Nvidia driver
comes from nvidia as precompiled binary, and neither of nvidia drivers was
ever disclosed to anybody outside their company. Even the specifications
of their hardware are not fully disclosed, therefore programmers who wrote
open source drivers for nvidia hardware could not write better driver that
they wrote. Not their fault: they just don't have all necessary
information.

Repeating wrong words "compiling nvidia drivers" creates misperception,
which is wide spread for long time. It is not the driver you are
compiling, but merely interface between binary nvidia driver and
particular kernel.

I probably should add rant tags as I am ranting about the fact that some
company seems friendlier to open source than it actually is...

Valeri

> etc in a given kernel and not all changes
> involve all areas.  If the things that were used to build a given module
> did not change, it can still be run.  If some dependency did change, the
> module needs to be rebuilt.  The exact error wording is important .. it
> could be a warning or it could be an error requiring module rebuild.
>
> You might get a warning if you do not have the kernel version that the
> original module was built on, but it might be (most likely is) OK to run
> anyway so long as no deps are changed.
>
> Anyway, the elrepo guys and gals should know if you need a new module or
> not for a specific kernel version.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] gnome boot problem

[dominic adair-jones]

On Mon, Nov 20, 2017 at 8:42 AM, Johnny Hughes  wrote:
> On 11/17/2017 09:04 AM, m.r...@5-cent.us wrote:
>> dominic adair-jones wrote:
>>> On Fri, Nov 17, 2017 at 9:14 AM,   wrote:
 dominic adair-jones wrote:
> going to run journalctl this evening when i get in and relay any errors
> i see.
>
> On Thu, Nov 16, 2017 at 6:01 PM, Pete Biggs  wrote:
>> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>>> Ok that's what I figured Ive narrowed it down to Plymouth but I
>>> haven't found much info on what the fix is.
>>
>> No, plymouth is the process that controls the booting process. It is
>> not the problem. It is doing exactly what it's supposed to be doing -
>> waiting for a process to finish before going on to its next task. You
>> should use journalctl to see what task it is waiting on.
>>
>>>  As of now I can ctl alt f2 and run
>>> startx to get to a desktop.
>>
>> What graphics card do you have?
>>
>>>  When I try to run gui (such as keepnote or
>>> chromium) from within my vms now tho I get errors.
>>
>> What errors.
>>
 Please stop top posting.

 It really sounds like a graphics driver error. Have you looked in
 /var/log/Xorg.0.log?
>>> sorry about that first time publicly posting like this. I will check
>>> this evening. I did remove the x0rg drivers and plymouth but didnt
>>> check the logs as it got late.
>>
>> Reading the thread in this post, I see you saying that startx works
>> That would suggest that graphics works, but something in trying to go into
>> runlevel 5 is funny.
>>
>> Stupid question: how long have you waited? C7 seems to take an
>> unconsciously long time for the X login to come up.
>>
>> Do you see the screen go into graphical mode during the boot? You know,
>> when it'll go black, then smaller fonts, and more lines on the screen?
>>
>> Starting to wonder about a timing issue, with a driver not loading.
>>
>
> This sounds like some kind of GDM issue to me.
>
> I am not sure the OP has ever answered the question of what video card
> is installed.
>
> OP:  If you look at Xorg.0.log that should tell you if there is a
> problem starting X.  If you use /var/log/messages, dmseg, and/or
> journalctl it might give you an init type error output.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
thanks, looking thru the log i attached i did notice the gdm error. As
a workaround i installed/switched over to lightdm. still going to
figure out what went wrong with gdm.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] gnome boot problem

[Johnny Hughes]

On 11/17/2017 09:04 AM, m.r...@5-cent.us wrote:
> dominic adair-jones wrote:
>> On Fri, Nov 17, 2017 at 9:14 AM,   wrote:
>>> dominic adair-jones wrote:
 going to run journalctl this evening when i get in and relay any errors
 i see.

 On Thu, Nov 16, 2017 at 6:01 PM, Pete Biggs  wrote:
> On Thu, 2017-11-16 at 22:45 +, dominic adair-jones wrote:
>> Ok that's what I figured Ive narrowed it down to Plymouth but I
>> haven't found much info on what the fix is.
>
> No, plymouth is the process that controls the booting process. It is
> not the problem. It is doing exactly what it's supposed to be doing -
> waiting for a process to finish before going on to its next task. You
> should use journalctl to see what task it is waiting on.
>
>>  As of now I can ctl alt f2 and run
>> startx to get to a desktop.
>
> What graphics card do you have?
>
>>  When I try to run gui (such as keepnote or
>> chromium) from within my vms now tho I get errors.
>
> What errors.
>
>>> Please stop top posting.
>>>
>>> It really sounds like a graphics driver error. Have you looked in
>>> /var/log/Xorg.0.log?
>> sorry about that first time publicly posting like this. I will check
>> this evening. I did remove the x0rg drivers and plymouth but didnt
>> check the logs as it got late.
> 
> Reading the thread in this post, I see you saying that startx works
> That would suggest that graphics works, but something in trying to go into
> runlevel 5 is funny.
> 
> Stupid question: how long have you waited? C7 seems to take an
> unconsciously long time for the X login to come up.
> 
> Do you see the screen go into graphical mode during the boot? You know,
> when it'll go black, then smaller fonts, and more lines on the screen?
> 
> Starting to wonder about a timing issue, with a driver not loading.
> 

This sounds like some kind of GDM issue to me.

I am not sure the OP has ever answered the question of what video card
is installed.

OP:  If you look at Xorg.0.log that should tell you if there is a
problem starting X.  If you use /var/log/messages, dmseg, and/or
journalctl it might give you an init type error output.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Intel Bluetooth problems - "Invalid request code (56)" - on CentOS 6.9

[Johnny Hughes]

On 11/20/2017 03:33 AM, Toralf Lund wrote:
> Hi,
> 
> I have Lenovo laptop with an Intel wireless and Bluetooth adapter,
> running CentOS 6.9. The wireless works just fine, but I can't seem to
> get Bluetooth to work. When I try to force it up from the command line I
> get
> 
> # hciconfig hci0 up
> Can't init device hci0: Invalid request code (56)
> 
> There is also a similar message message in /var/log/messages from
> start-up on boot. The device info from "hciconfig" also seems a bit
> suspicious to me - notice how the address has all 0s:
> 
> # hciconfig -a
> hci0:    Type: BR/EDR  Bus: USB
>     BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
>     DOWN
>     RX bytes:48 acl:0 sco:0 events:8 errors:0
>     TX bytes:24 acl:0 sco:0 commands:12 errors:4
> 
> /var/log/messages indicates that firmware is loaded correctly
> 
> # egrep "iwlwifi.*firmware" /var/log/messages
> Nov 20 09:24:16 osl-97214 kernel: iwlwifi :04:00.0: firmware:
> requesting iwlwifi-8000C-17.ucode
> Nov 20 09:24:16 osl-97214 kernel: iwlwifi :04:00.0: firmware:
> requesting iwlwifi-8000C-16.ucode
> Nov 20 09:24:16 osl-97214 kernel: iwlwifi :04:00.0: loaded firmware
> version 16.242414.0 op_mode iwlmvm
> 
> and I think the following shows that the device is actually there
> 
> # lsusb
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
> Bus 001 Device 003: ID 17ef:1010 Lenovo
> Bus 001 Device 004: ID 8087:0a2b Intel Corp.
> Bus 001 Device 005: ID 5986:0706 Acer, Inc
> Bus 002 Device 002: ID 17ef:1010 Lenovo
> Bus 001 Device 006: ID 2109:3431 VIA Labs, Inc. Hub
> Bus 001 Device 007: ID 17ef:100f Lenovo
> Bus 002 Device 003: ID 2109:8110 VIA Labs, Inc. Hub
> Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
> 
> # lsusb -s 001:004 -v | grep bInterface
>   bInterfaceNumber    0
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
>   bInterfaceNumber    1
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
>   bInterfaceNumber    1
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
>   bInterfaceNumber    1
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
>   bInterfaceNumber    1
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
>   bInterfaceNumber    1
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
>   bInterfaceNumber    1
>   bInterfaceClass   224 Wireless
>   bInterfaceSubClass  1 Radio Frequency
>   bInterfaceProtocol  1 Bluetooth
> 
> The bluetooth kernel modules should be loaded, too (but perhaps I need
> some extra driver or whatever?)
> 
> # lsmod  | grep bluetooth
> bluetooth  97799  6 sco,bnep,l2cap,btusb
> rfkill 19255  5 cfg80211,bluetooth,thinkpad_acpi
> 
> Does anyone have any idea what's wrong here? Is there any way at all I
> can enable Bluetooth on this system?

I have never actually tried to use bluetooth on CentOS Linux 6.  I use
bluetooth all the time on CentOS Linux 7.

The base kernel in EL6 is fairly old (2.6.32).  Red Hat backports
(http://red.ht/2h14UtV) changes to the kernel for security and bugfixes,
however they don't back part every driver or firmware .. so sometimes,
some hardware still has the original (older) code.

You could TRY the elrepo kernel(s) for CentOS Linux 6 and see if it
allows the bluetooth to work.

 http://elrepo.org/linux/kernel/el6/x86_64/RPMS/

They have a Long Term (lt) kernel (3.10.x) and a MainLine (ml) kernel
that you can try.

IF you use the XFS file system (instead of ext4) then you will also want
to upgrade your xfsprogs (http://bit.ly/2hOlsec) to this version if you
use a newer elrepo kernel due to this bug (http://red.ht/2hHsJZS ,
http://bit.ly/2mNN9G2).



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[milos.blazevic]

Quoting Peter :


On 20/11/17 11:30, milos.blazevic wrote:

There's the unstable version that installs and works:
https://www.skype.com/en/insider/


Thanks for pointing this out, it looks like they removed the newer
GLIBCXX requirement that was added for 8.10, possibly due to popular demand?

Judging by the comments in the original announcement:  
https://answers.microsoft.com/en-us/skype/forum/skype_linux-skype_startms-skype_installms/the-new-skype-for-desktop-is-here/dba5e41b-126a-4221-9e28-e1266d235689?auth=1 I'd say  
yes.


Sadly, no one from M$/Skype team bothered to point us in the right direction.



Peter
___
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] Semi-OT: hardware: NVidia proprietary driver, C7.4

[Johnny Hughes]

On 11/20/2017 05:23 AM, Kretschmer, Jens wrote:
> Hi Mark,
> 
> did you manage to sort out messages from Dracut and /sbin/weak-modules you 
> received while installing kmod-nvidia? We get the same messages while 
> installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the 
> kernel 3.10.0-693.5.2.el7.x86_64.
> 

weak modules allow modules built on one kernel version to apply to
another kernel as long as the 'build dependencies' are the same.  There
are many individual drivers, etc in a given kernel and not all changes
involve all areas.  If the things that were used to build a given module
did not change, it can still be run.  If some dependency did change, the
module needs to be rebuilt.  The exact error wording is important .. it
could be a warning or it could be an error requiring module rebuild.

You might get a warning if you do not have the kernel version that the
original module was built on, but it might be (most likely is) OK to run
anyway so long as no deps are changed.

Anyway, the elrepo guys and gals should know if you need a new module or
not for a specific kernel version.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Semi-OT: hardware: NVidia proprietary driver, C7.4

[Kretschmer, Jens]

Hi Mark,

did you manage to sort out messages from Dracut and /sbin/weak-modules you 
received while installing kmod-nvidia? We get the same messages while 
installing kmod-nvidia-384.98-1.el7_4.elrepo.x86_64 on RHEL 7.4 with the kernel 
3.10.0-693.5.2.el7.x86_64.

Kr,
Jens


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

[CentOS] Intel Bluetooth problems - "Invalid request code (56)" - on CentOS 6.9

[Toralf Lund]

Hi,

I have Lenovo laptop with an Intel wireless and Bluetooth adapter, 
running CentOS 6.9. The wireless works just fine, but I can't seem to 
get Bluetooth to work. When I try to force it up from the command line I get


# hciconfig hci0 up
Can't init device hci0: Invalid request code (56)

There is also a similar message message in /var/log/messages from 
start-up on boot. The device info from "hciconfig" also seems a bit 
suspicious to me - notice how the address has all 0s:


# hciconfig -a
hci0:    Type: BR/EDR  Bus: USB
    BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
    DOWN
    RX bytes:48 acl:0 sco:0 events:8 errors:0
    TX bytes:24 acl:0 sco:0 commands:12 errors:4

/var/log/messages indicates that firmware is loaded correctly

# egrep "iwlwifi.*firmware" /var/log/messages
Nov 20 09:24:16 osl-97214 kernel: iwlwifi :04:00.0: firmware: 
requesting iwlwifi-8000C-17.ucode
Nov 20 09:24:16 osl-97214 kernel: iwlwifi :04:00.0: firmware: 
requesting iwlwifi-8000C-16.ucode
Nov 20 09:24:16 osl-97214 kernel: iwlwifi :04:00.0: loaded firmware 
version 16.242414.0 op_mode iwlmvm


and I think the following shows that the device is actually there

# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 17ef:1010 Lenovo
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 005: ID 5986:0706 Acer, Inc
Bus 002 Device 002: ID 17ef:1010 Lenovo
Bus 001 Device 006: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 007: ID 17ef:100f Lenovo
Bus 002 Device 003: ID 2109:8110 VIA Labs, Inc. Hub
Bus 001 Device 008: ID 05e3:0610 Genesys Logic, Inc. 4-port hub

# lsusb -s 001:004 -v | grep bInterface
  bInterfaceNumber    0
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  bInterfaceNumber    1
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  bInterfaceNumber    1
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  bInterfaceNumber    1
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  bInterfaceNumber    1
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  bInterfaceNumber    1
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth
  bInterfaceNumber    1
  bInterfaceClass   224 Wireless
  bInterfaceSubClass  1 Radio Frequency
  bInterfaceProtocol  1 Bluetooth

The bluetooth kernel modules should be loaded, too (but perhaps I need 
some extra driver or whatever?)


# lsmod  | grep bluetooth
bluetooth  97799  6 sco,bnep,l2cap,btusb
rfkill 19255  5 cfg80211,bluetooth,thinkpad_acpi

Does anyone have any idea what's wrong here? Is there any way at all I 
can enable Bluetooth on this system?


Thanks,

- Toralf


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

Re: [CentOS] skypeforlinux lacks dependencies, won't update

[wwp]

Hello,


On Mon, 20 Nov 2017 12:58:21 +1300 Peter  wrote:

> On 20/11/17 11:30, milos.blazevic wrote:
> > There's the unstable version that installs and works:
> > https://www.skype.com/en/insider/  
> 
> Thanks for pointing this out, it looks like they removed the newer
> GLIBCXX requirement that was added for 8.10, possibly due to popular demand?

Maybe. Unpacking the rpm works, anyway, I never encountered a single
binary issue since I use it like that (ordinary use, I probably don't
use that text encoding or whatever submodule which depends on a newer
libstdc++).


Regards,

-- 
wwp


pgpRi1j6R93ge.pgp
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos