On 21/09/2021 17:27, Steve Cleveland wrote:
I've done some searching, but haven't found anything on this topic yet.
I have a newer workstation with the Intel I219-LM network controller.
The included Intel driver does not support it. I found the elrepo DUD
package that includes the current
On 18/01/2021 20:43, Phil Perry wrote:
On 18/01/2021 18:18, neil watson wrote:
Hi
Firstly thanks for all the work you do to support older kit (eg
older Dell RAID controllers!)
I've had a look
On 11/08/2020 20:09, Phil Perry wrote:
On 11/08/2020 19:32, Akemi Yagi wrote:
On Tue, Aug 11, 2020 at 10:59 AM Manuel Wolfshant
wrote:
On 8/11/20 8:14 PM, Akemi Yagi wrote:
On Mon, Aug 10, 2020 at 2:58 PM Guidroz, Bryan
wrote:
Greetings,
I'm not very familiar with how exactly this
On 10/06/2020 19:43, Phil Perry wrote:
On
10/06/2020 16:35, Nick Howitt wrote:
Hi Gents,
Thanks for all the great work you do. I've just updated a
machine to 7.8 and the drivers were there waiting
Hi Gents,
Thanks for all the great work you do. I've just updated a machine to 7.8
and the drivers were there waiting.
One thing that has popped up is a depmod error on install:
depmod: ERROR: fstatat(9, 88XXau.ko.xz): No such file or directory
Looking for the file I get:
Hi Gents,
I've been trying to find this for a while now and I've had some help
to find a good source. Using
https://github.com/cccooo/rtl8812au-centos-7.6.git and changing the
Makefile, line 220 to "ifeq ($(REDHAT_VER), 7.7)", the module
compiles cleanly and
Try just using the latest version you can see. many of the drivers
probably don't need recompiling for 7.7. I have not tried 7.7 yet, but
as an example, kmod-r8168-8.046.00-1.el7_5 works in 7.5 and 7.6 so there
was no need to recompile it for 7.6.
On 30/08/2019 04:38, d tbsky wrote:
Hi:
On 11/09/2018 16:49, Alan Bartlett
wrote:
Big hints . . .
--define 'dist .el6_10.clearos'
--define 'dist .el7_5.clearos'
Use the above defines on your rpmbuild or mock command lines.
Alan.
Thanks. I am still learning this. I had it set up
On 10/09/2018 20:08, Phil Perry wrote:
Also worth noting is that if you compile
these from the src.rpm, neither the 6_10 nor the 7_5 packages
get the 6_10 or the 7_5 tag in the generated rpm. With the 7.4
packages you overwrote the
On 09/09/2018 13:02, Phil Perry wrote:
On 09/09/18 12:39, Nick Howitt wrote:
Thanks for this.
The el6 version compiles cleanly with a 6.9 kernel. Do you know
if the package is in any way limited to 6.10 kernels as I don't
Thanks for this.
The el6 version compiles cleanly with a 6.9 kernel. Do you know if
the package is in any way limited to 6.10 kernels as I don't have a
current 6.10 installation I can test against.
Regards,
Nick
On 08/09/2018 20:46, Alan Bartlett
And its crashed again on the new kernel. I'll post the info
requested tomorrow.
Nick
On 07/07/2018 10:19, Nick Howitt wrote:
Hi Phil,
I'll temporarily put this on hold as the distro has just pushed
out a new kernel, 3.10.0
On 07/07/2018 10:26, Trevor Hemsley wrote:
On 07/07/18 10:19, Nick Howitt wrote:
Hi Phil,
I'll temporarily put this on hold as the distro has just pushed out a
new kernel, 3.10.0-862.6.3.v7.x86_64. I'll have to see if it still
crashes or I could end up wasting everybody's time. The VM has
:
On 04/07/18 18:18, Akemi Yagi wrote:
On Wed, Jul 4, 2018 at 3:53 AM, Nick Howitt wrote:
Hi,
Following a thread I saw here I am using kmod-tpe in VM in
Virtualbox. The
VM is ClearOS 7.5 beta so is running kernel 3.10.0-862.3.2.v7.x86_64
and I
am getting intermittent kernel dumps on bootup
On 04/07/2018 18:18, Akemi Yagi wrote:
On Wed, Jul 4, 2018 at 3:53 AM, Nick Howitt wrote:
Hi,
Following a thread I saw here I am using kmod-tpe in VM in Virtualbox. The
VM is ClearOS 7.5 beta so is running kernel 3.10.0-862.3.2.v7.x86_64 and I
am getting intermittent kernel dumps on bootup
Hi,
Following a thread I saw here I am using kmod-tpe in VM in Virtualbox.
The VM is ClearOS 7.5 beta so is running kernel 3.10.0-862.3.2.v7.x86_64
and I am getting intermittent kernel dumps on bootup. More often than
not boot goes OK, but a number of times I get a kernel panic.
Hi gents,
I had the zd1211rw driver compiled for 7.4, but it did not do the weak
updates bit to the 7.5 kernel. Recompiling without any source changes it
gave no errors and doing a reinstall has it working with the 7.5 kernel.
This has me confused. Does it mean that other drivers need to be
Symlink them?
On 01/06/2018 04:50, John Adegbile wrote:
So I scrutinized my Xorg.log file as suggested and found some lines
showing failures:
/[ 28.568] (EE) Failed to load
/usr/lib64/xorg/modules/extensions/nvidia/libglx.so:
libnvidia-tls.so.390.59: cannot open shared object file: No
The in-kernel driver does work but I have a problem. My box has both an
r8168 and r8169 card in it. The kmod-r8168 blacklists the r8169 driver to
stop it from loading. If I remove the blacklist, it sometimes loads against
the r8168 card and sometimes it does not. Installing the kmod-r8169
On 22/05/2018 18:02, Akemi Yagi wrote:
On Tue, May 22, 2018 at 4:53 AM, Nick Howitt <n...@howitts.co.uk> wrote:
Hi Phil,
Is there any chance of updating the r8169 driver to be compatible with 7.5?
I am getting the following errors:
/home/build/rpmbuild/BUILD/r8169-6.020.00/src/r81
Hi Phil,
Is there any chance of updating the r8169 driver to be compatible with
7.5? I am getting the following errors:
/home/build/rpmbuild/BUILD/r8169-6.020.00/src/r8169_n.c:2617:9:
error: unknown field 'ndo_change_mtu' specified in initializer
.ndo_change_mtu =
I have no idea. I don't use Ubuntu. Perhaps their wpa_supplicant.conf
has a line calling nl80211,wicd. You can do that with the D switch as well.
On 17/03/2018 17:38, Mahmood Naderan wrote:
So why ubuntu work without problem then?!
On Mar 17, 2018 20:14, "Alan Bartlett"
>>>r8188eu
No. The whole point of the link is to use the wext driver instead of the
default nl80211 so use -Dwext. Also they have bypassed the
/etc/wpa_supplicant/wpa_supplicant.conf file and coded the SSID and
password directly, so try:
wpa_supplicant -B -Dwext -c <(wpa_passphrase "ESSID"
That was a bit unfair to blame wpa_supplicant. It would be nice if
Realtek could release an nl80211 compatible driver rather than one for
the deprecated wext driver.
On 17/03/2018 09:45, Nick Howitt wrote:
Possible link:
http://www.thelinuxrain.com/articles/getting-realtek-8188eu-wireless
Possible link:
http://www.thelinuxrain.com/articles/getting-realtek-8188eu-wireless-adapters-to-work-in-linux-and-possibly-other-wireless-realtek-chipsets.
The issue appears to be wpa_supplicant. Google "r8188eu wpa_supplicant"
Nick
On 17/03/2018 09:39, Mahmood Naderan wrote:
So the output
On 05/03/2018 22:51, Phil Perry wrote:
On 05/03/18 20:29, Nick Howitt wrote:
On 05/03/2018 20:24, Nick Howitt wrote:
On 05/03/2018 20:16, Phil Perry wrote:
On 05/03/18 09:35, Nick Howitt wrote:
Hi,
I have a little USB 802.11ac dongle that I'm trying to get going
in my server. lsusb
On 05/03/2018 20:29, Nick Howitt wrote:
On 05/03/2018 20:24, Nick Howitt wrote:
On 05/03/2018 20:16, Phil Perry wrote:
On 05/03/18 09:35, Nick Howitt wrote:
Hi,
I have a little USB 802.11ac dongle that I'm trying to get going in
my server. lsusb gives:
Bus 002 Device 002: ID
On 05/03/2018 20:24, Nick Howitt wrote:
On 05/03/2018 20:16, Phil Perry wrote:
On 05/03/18 09:35, Nick Howitt wrote:
Hi,
I have a little USB 802.11ac dongle that I'm trying to get going in
my server. lsusb gives:
Bus 002 Device 002: ID 0bda:a811 Realtek Semiconductor Corp
On 05/03/2018 20:16, Phil Perry wrote:
On 05/03/18 09:35, Nick Howitt wrote:
Hi,
I have a little USB 802.11ac dongle that I'm trying to get going in
my server. lsusb gives:
Bus 002 Device 002: ID 0bda:a811 Realtek Semiconductor Corp.
RTL8811AU 802.11a/b/g/n/ac WLAN Adapter
I've
Hi,
I have a little USB 802.11ac dongle that I'm trying to get going in my
server. lsusb gives:
Bus 002 Device 002: ID 0bda:a811 Realtek Semiconductor Corp.
RTL8811AU 802.11a/b/g/n/ac WLAN Adapter
I've had a look at the current kmod driver which is version
2018 08:20, Nick Howitt wrote:
Hi
Phil,
Is there any chance of updating the r8101 driver for el7 x64? I
think this is another one which broke with the 7.4 kernel:
/home/build/rpmbuild/BUILD/r8101-1.027.00/src/r8101_n.c: In
Hi Phil,
Is there any chance of updating the r8101 driver for el7 x64? I think
this is another one which broke with the 7.4 kernel:
/home/build/rpmbuild/BUILD/r8101-1.027.00/src/r8101_n.c: In function
'rtl8101_start_xmit':
Hi Alan,
I've had positive feedback that the niu driver is working.
Thanks,
Nick
On 23/11/2017 22:10, Nick Howitt wrote:
Brilliant. I was watching different mirrors. I can see it now.
Nick
On 23
Thanks very much for your efforts. It has not sync'd to the mirrors yet
so I'll have to wait until tomorrow.
Regards,
Nick
On 23/11/2017 20:36, Phil Perry wrote:
On 23/11/17 19:35, Alan Bartlett wrote:
On 23 November 2017 at 19:02, Nick Howitt <n...@howitts.co.uk> wrote:
H
Hi Alan,
If it covers the right PCI ID that would be brilliant, thanks.
Nick
On 23 November 2017 18:38:32 GMT+00:00, Alan Bartlett <a...@elrepo.org> wrote:
>
>On 23 November 2017 at 17:23, Nick Howitt <n...@howitts.co.uk> wrote:
>> Hi Alan,
>>
>> I shou
to put in
the legwork, I'd be happy to compile any resulting srpm against our
kernel for him.
Thanks,
Nick
On 2017-11-23 16:44, Alan Bartlett wrote:
On 23 November 2017 at 13:34, Nick Howitt <n...@howitts.co.uk> wrote:
Hi,
I am looking for a driver for the PCI ID 108e:abcd and I think
Hi,
I am looking for a driver for the PCI ID 108e:abcd and I think I need
the niu driver. This is not currently provided by ElRepo. Do you know if
it is the correct driver and, if it is, what are the chances of it being
provided?
Thanks,
Nick
___
On 26/10/2017 19:31, Phil Perry wrote:
On 26/10/17 17:25, Nick Howitt wrote:
On 26/10/2017 17:18, Manuel Wolfshant wrote:
On October 26, 2017 5:41:25 PM GMT+03:00, Nick Howitt
<n...@howitts.co.uk> wrote:
Hi,
Can I suggest a change to the packaging of the above three drivers?
I'd
On 26/10/2017 17:18, Manuel Wolfshant wrote:
On October 26, 2017 5:41:25 PM GMT+03:00, Nick Howitt <n...@howitts.co.uk>
wrote:
Hi,
Can I suggest a change to the packaging of the above three drivers? I'd
like to suggest the three drivers are all made dependants of each
Hi,
Can I suggest a change to the packaging of the above three drivers? I'd
like to suggest the three drivers are all made dependants of each other
and that the file \usr\lib\modprobe.d\blacklist-r8169.conf is removed
from the r8101 and r8168 drivers? My reasoning is as follows:
The stock
out the
r8168 and r8169 drivers from my previous correspondence and I needed the
PCI-ID's from this one for completeness.
Regards,
Nick
On 07/10/2017 21:51, Nick Howitt wrote:
One correction below.
From the testing I've done this evening, removing the blacklisting is
important and it m
.
On 07/10/2017 13:06, Nick Howitt wrote:
On 07/10/2017 12:35, Phil Perry wrote:
On 06/10/17 13:45, Nick Howitt wrote:
Hi Phil,
One thing I noticed in the summer last year but did
On 07/10/2017 12:35, Phil Perry wrote:
On 06/10/17 13:45, Nick Howitt wrote:
Hi Phil,
One thing I noticed in the summer last year but did not isolate at
all was that when I was running both the r8168 and r8169 drivers in a
box which had both cards, the 8169 NIC would not come up on boot
#reply-190651
(and the following post) with drivers compiled for 7.4.
Regards,
Nick
On 04/10/2017 19:45, Phil Perry wrote:
On 04/10/17 14:19, Nick Howitt wrote:
Hi Phil,
As the r8169 does not carry 7_4 in its file name, does that mean it
is backwards compatible with earlier kernels/ve
Hi Phil,
As the r8169 does not carry 7_4 in its file name, does that mean it is
backwards compatible with earlier kernels/versions of EL7?
Regards,
Nick
On 2017-10-03 08:06, Nick Howitt wrote:
Hi Phil,
Thanks for these. I'll get them built as soon as possible then try to
track down
Hi Phil,
Thanks for these. I'll get them built as soon as possible then try to
track down the people who requested them to test.
Regards,
Nick
On 2017-10-02 21:04, Phil Perry wrote:
On 01/10/17 20:12, Phil Perry wrote:
On 01/10/17 17:04, Nick Howitt wrote:
Hi Phil,
I've been through all
Hi Phil,
When my box updates (normally a couple of weeks behind the Community
full release) I can check about the r8169 and the weak links. At
some time I would have thought the package would need rebuilding
otherwise anyone wanting to compile from sources would
:04, Nick Howitt wrote:
Hi Phil,
I've been through all the kmod drivers I've compiled for 7.3 and
tried compiling them against ClearOS 7.4. Four of them have
failed to compile:
ath10k
ath10k
Hi Phil,
I've been through all the kmod drivers I've compiled for 7.3 and tried
compiling them against ClearOS 7.4. Four of them have failed to compile:
ath10k
ne2k-pci
r8169
rtl8723be
Of these I am most concerned about the r8169 as it is needed to remove
compatibility with r8168 cards.
thread.
Regards,
Nick
On 30/09/2017 16:06, Phil Perry wrote:
Thanks, that would be hugely appreciated.
Phil
On 30/09/17 15:54, Nick Howitt wrote:
Hi Phil,
Thanks very much for that. The user who had the issue is way more
capable than me so I'll see if he can test it and give feedback
Hi Phil,
Thanks very much for that. The user who had the issue is way more
capable than me so I'll see if he can test it and give feedback to
enable you to promote it.
Regards,
Nick
On 30/09/2017 15:30, Phil Perry wrote:
On 30/09/17 15:19, Nick Howitt wrote:
Hi Phil,
Thanks for looking
orking on 7.4.
Regards,
Nick
On 30/09/2017 12:12, Phil Perry wrote:
On 29/09/17 19:42, Nick Howitt wrote:
Hi,
I've had a report that this driver does not set up the weak-updates
symlinks when upgrading from a 7.3 kernel to a 7.4 kernel but is
seems to function OK you you create the symlinks yo
Hi,
I've had a report that this driver does not set up the weak-updates
symlinks when upgrading from a 7.3 kernel to a 7.4 kernel but is seems
to function OK you you create the symlinks yourself. I've tried
compiling the 1.5.1-2 source against the 7.4 kernel and it also fails with:
make:
On 12/08/2017 11:34, Phil Perry wrote:
On 12/08/17 09:28, Nick Howitt wrote:
Hi,
Hi Nick,
I am trying to build the aacraid-1.2.1-x
driver in ClearOS 7.3 (Centos 7.3 derivative) and I'm getting
Hi,
I am trying to build the aacraid-1.2.1-x driver in ClearOS 7.3
(Centos 7.3 derivative) and I'm getting the following errors:
Installing aacraid-kmod-1.2.1-6.el7.elrepo.src.rpm
warning: aacraid-kmod-1.2.1-6.el7.elrepo.src.rpm: Header V4
DSA/SHA1
There is an ath10k-firmware package e.g
http://elrepo.reloumirrors.net/elrepo/el7/x86_64/RPMS/ath10k-firmware-2.0-1.el7.elrepo.noarch.rpm
On 2016-08-16 16:15, Sean Hancock via elrepo wrote:
I recently installed a dual boot of the CentOS-7-x86_64-DVD iso
alongside an existing Windows 10 Home (V
Thanks for letting me know. I'll give a go in slow time as I managed to
get someone else to build it against an older kernel and I'm not
brilliant using patch (understatement).
Nick
On 17/07/2016 12:40, Phil Perry wrote:
On 16/03/16 22:13, Nick Howitt wrote:
Hi,
I am trying to build
On 02/06/2016 20:10, Phil Perry wrote:
On 02/06/16 18:26, Nick Howitt wrote:
Hi Akemi,
Have you been able to make any progress with this or is it a lost cause?
Regards,
Nick
Hi Nick,
Unfortunately at this point I'd say it's looking like a lost cause -
far too many errors for me
Hi Akemi,
Have you been able to make any progress with this or is it a lost cause?
Regards,
Nick
On 14/05/2016 20:30, Nick Howitt wrote:
Hi Akemi,
That would be brilliant. I wait with hope!
Thanks,
Nick
On 14/05/2016 19:26, Akemi Yagi wrote:
On May 10, 2016 11:11, "Nick Howit
Hi Akemi,
That would be brilliant. I wait with hope!
Thanks,
Nick
On 14/05/2016 19:26, Akemi Yagi wrote:
On May 10, 2016 11:11, "Nick Howitt" <n...@howitts.co.uk>
wrote:
>
> Hi,
Hi,
We have someone in using ClearOS7 (CentOS7 derivative) who is having
problems with the e1000 driver built into the kernel (7.3.21-k8-NAPI
on 3.10.0-327.10.1.v7.x86_64). The latest Intel driver is 8.0.35. In
its change log on sourceforge it says "* Fix driver
Hi,
I am trying to build the kmod-forcedeth driver from the src.rpm on
ClearOS 7.2 (a CentOS 7.2 derivative but with a slightly different
kernel) using rpmbuild, but the build is failing:
Installing forcedeth-kmod-0.64-1.el7.elrepo.src.rpm
warning:
Hi,
I've been using kmod drivers for a few years now - the r8168, e1000e
(no more) and igb and I've recently bumped into an oddity while
helping someone on the ClearOS
forums. I've been used to the idea of the modules installing
in a "week-updates" directory
Hi,
I bumped into an exotic issue trying to install kmod-e1000e-2.5.4
built for ClearOS. A a bit of history I made and installed my own
rpm of the stock e1000e driver and forgot about it. Since then I've
upgraded the kernel so the driver can't be being used. I tried
64 matches
Mail list logo
