6:17 p.m.
Hi,
Yesterday I downloaded all the F28 packages necessary to upgrade my
system from F27 to F28 by using the following command:
sudo dnf system-upgrade download --refresh --releasever=28
--allowerasing --skip-broken
I added the last 2 parameters because dnf told me there were
packages it could not upgrade because of conflicts and to add those
parameters. Having had the process start it said there were approx. 3540
packages to be downloaded, which took several hours to do.
I ran the dnf system-upgrade reboot command as required, but
because I had other things I needed to do I shut the machine down at the
subsequent grub menu.
This morning I booted Fedora and it booted to the starting offline
install messages that get displayed twice, separated by some sound card
initialisation messages. Dnf then kicked in and displayed some messages
I couldn't read because they scrolled off the screen too quickly, but it
did get to the point of telling me there were 6 F28 packages with broken
dependencies (being 4 Boost packages, qt-qtbase and polkit-qt5-1) and
that I should use --allowerasing and --skip-broken. It then proceeded to
tell me there were 137 packages to install, 3410 packages to upgrade, 13
packages it was going to remove, 6 packages it was going to downgrade,
and 6 packages with broken dependencies. It then proceeded to tell me
there were no packages to download, and that its transaction tests were
successful so it was going to do the install. After pausing for a little
while it then produced a message that started with the work failed
written in red, but the messages scrolled off too quickly to read as it
continued on to boot into F27.
1). Can anyone shed any light on why the install may have failed and
what I need to do to work around it? I'm hoping I don't have to run a
'sudo dnf clean all' and then a 'sudo dnf system-upgrade --refresh
--releasever=28 --allowerasing --skip-broken' to download all the
packages again.
2). Where can I find the logs that would contain the error message so I
can read what it said, given that /var/log/boot.log and /var/log/dnf.log
both don't contain the message?
regards,
Steve
6:47 p.m.
On 07/10/2018 03:17 PM, Stephen Morris wrote:
1). Can anyone shed any light on why the install may have failed and
what I need to do to work around it? I'm hoping I don't have to run a
'sudo dnf clean all' and then a 'sudo dnf system-upgrade --refresh
--releasever=28 --allowerasing --skip-broken' to download all the
packages again.
I wonder if the --skip-broken is a problem. Can you solve that before
doing the upgrade?
I think the packages should still be downloaded.
Check in /var/lib/dnf/system-upgrade
2). Where can I find the logs that would contain the error message so
I
can read what it said, given that /var/log/boot.log and /var/log/dnf.log
both don't contain the message?
Try "dnf system-upgrade log".
6:16 p.m.
On 11/7/18 8:47 am, Samuel Sieb wrote:
On 07/10/2018 03:17 PM, Stephen Morris wrote:
> 1). Can anyone shed any light on why the install may have failed and
> what I need to do to work around it? I'm hoping I don't have to run a
> 'sudo dnf clean all' and then a 'sudo dnf system-upgrade --refresh
> --releasever=28 --allowerasing --skip-broken' to download all the
> packages again.
I wonder if the --skip-broken is a problem. Can you solve that before
doing the upgrade?
I think the packages should still be downloaded.
Check in /var/lib/dnf/system-upgrade
All the packages were still downloaded.
> 2). Where can I find the logs that would contain the error message so
> I can read what it said, given that /var/log/boot.log and
> /var/log/dnf.log both don't contain the message?
Try "dnf system-upgrade log".
I issued that command and all it did was tell me there were 6 boots that
appeared to have upgrade logs, going right back to the upgrade I did of
F23 to F24, but the names it listed were meaningless to me and it didn't
provide any path references to where I might find the logs to be able to
search them.
Following your suggestion I ran a sudo dnf upgrade which produced all
the conflict messages that I worked around by adding --allowerasing and
--skip-broken, but this time dnf said to try --best and --allowerasing,
which I did and that installed all the package updates that caused the
conflicts. Having done this I was able to complete the upgrade to F28,
but now I have big problems.
Under F28 my USB network device doesn't work because dkms can't compile
the driver for it, and, either because of this failure or a compile
failure the drivers for my mouse haven't been installed by dkms either.
Booting into the latest F27 kernel I have installed which is 4.17.3-100,
where both drivers have previously successfully compiled and installed
(which is how I'm able to send this email), the mouse drivers still
compile but the usb device driver fails to compile. Both with the F28
kernel, being 4.17.3-200, and the F27 kernel I mentioned, the compile
fails with stdarg.h not found, so I'm now confused about what the F28
upgrade has done. The F28 upgrade should not have updated the F27 kernel
source that was already installed and hence there should not be any
barriers to compiling the driver against the F27 kernel when under F27
it did compile.
regards,
Steve
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:29 p.m.
On 07/11/2018 03:16 PM, Stephen Morris wrote:
On 11/7/18 8:47 am, Samuel Sieb wrote:
> On 07/10/2018 03:17 PM, Stephen Morris wrote:
>> 2). Where can I find the logs that would contain the error message so
>> I can read what it said, given that /var/log/boot.log and
>> /var/log/dnf.log both don't contain the message?
>
> Try "dnf system-upgrade log".
I issued that command and all it did was tell me there were 6 boots that
appeared to have upgrade logs, going right back to the upgrade I did of
F23 to F24, but the names it listed were meaningless to me and it didn't
provide any path references to where I might find the logs to be able to
search them.
Each line has a number at the front. Run "dnf system-upgrade log
--number=n" to see the corresponding log.
Booting into the latest F27 kernel I have installed which is
4.17.3-100,
where both drivers have previously successfully compiled and installed
(which is how I'm able to send this email), the mouse drivers still
compile but the usb device driver fails to compile. Both with the F28
kernel, being 4.17.3-200, and the F27 kernel I mentioned, the compile
fails with stdarg.h not found, so I'm now confused about what the F28
upgrade has done. The F28 upgrade should not have updated the F27 kernel
source that was already installed and hence there should not be any
barriers to compiling the driver against the F27 kernel when under F27
it did compile.
Why don't the drivers for the previous kernels still exist? The upgrade
shouldn't have removed them. The upgrade will have replaced the
-headers package which is what the drivers will compile against. You
could try replacing it with an earlier -headers package version, but I
doubt that's the problem. This is why I strongly avoid hardware that
requires out-of-tree drivers...
However, this might be the solution:
https://github.com/lwfinger/rtl8723bu/issues/106
6:38 p.m.
On 07/11/2018 03:16 PM, Stephen Morris wrote:
On 11/7/18 8:47 am, Samuel Sieb wrote:
> On 07/10/2018 03:17 PM, Stephen Morris wrote:
>> 1). Can anyone shed any light on why the install may have failed and
>> what I need to do to work around it? I'm hoping I don't have to run a
>> 'sudo dnf clean all' and then a 'sudo dnf system-upgrade --refresh
>> --releasever=28 --allowerasing --skip-broken' to download all the
>> packages again.
>
> I wonder if the --skip-broken is a problem. Can you solve that before
> doing the upgrade?
>
> I think the packages should still be downloaded.
> Check in /var/lib/dnf/system-upgrade
All the packages were still downloaded.
>
>> 2). Where can I find the logs that would contain the error message so
>> I can read what it said, given that /var/log/boot.log and
>> /var/log/dnf.log both don't contain the message?
>
> Try "dnf system-upgrade log".
I issued that command and all it did was tell me there were 6 boots that
appeared to have upgrade logs, going right back to the upgrade I did of
F23 to F24, but the names it listed were meaningless to me and it didn't
provide any path references to where I might find the logs to be able to
search them.
Following your suggestion I ran a sudo dnf upgrade which produced all
the conflict messages that I worked around by adding --allowerasing and
--skip-broken, but this time dnf said to try --best and --allowerasing,
which I did and that installed all the package updates that caused the
conflicts. Having done this I was able to complete the upgrade to F28,
but now I have big problems.
Under F28 my USB network device doesn't work because dkms can't compile
the driver for it, and, either because of this failure or a compile
failure the drivers for my mouse haven't been installed by dkms either.
Booting into the latest F27 kernel I have installed which is 4.17.3-100,
where both drivers have previously successfully compiled and installed
(which is how I'm able to send this email), the mouse drivers still
compile but the usb device driver fails to compile. Both with the F28
kernel, being 4.17.3-200, and the F27 kernel I mentioned, the compile
fails with stdarg.h not found, so I'm now confused about what the F28
upgrade has done. The F28 upgrade should not have updated the F27 kernel
source that was already installed and hence there should not be any
barriers to compiling the driver against the F27 kernel when under F27
it did compile.
Uhm, did you get the libstdc++-devel RPM installed? It provides the
stdarg.h file, specifically:
/usr/include/c++/8/tr1/stdarg.h
Checking an old F26 VM I have, the equivalent file is:
/usr/include/c++/7/tr1/stdarg.h
I believe the C compiler will find it if it's installed. Even if it
does appear to be installed, a "dnf reinstall libstdc++-devel" should
clean up any cruft your messed-up install may have left.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
----------------------------------------------------------------------
7:24 p.m.
On 12/7/18 8:38 am, Rick Stevens wrote:
On 07/11/2018 03:16 PM, Stephen Morris wrote:
> On 11/7/18 8:47 am, Samuel Sieb wrote:
>> On 07/10/2018 03:17 PM, Stephen Morris wrote:
>>> 1). Can anyone shed any light on why the install may have failed and
>>> what I need to do to work around it? I'm hoping I don't have to run
a
>>> 'sudo dnf clean all' and then a 'sudo dnf system-upgrade
--refresh
>>> --releasever=28 --allowerasing --skip-broken' to download all the
>>> packages again.
>> I wonder if the --skip-broken is a problem. Can you solve that before
>> doing the upgrade?
>>
>> I think the packages should still be downloaded.
>> Check in /var/lib/dnf/system-upgrade
> All the packages were still downloaded.
>>> 2). Where can I find the logs that would contain the error message so
>>> I can read what it said, given that /var/log/boot.log and
>>> /var/log/dnf.log both don't contain the message?
>> Try "dnf system-upgrade log".
> I issued that command and all it did was tell me there were 6 boots that
> appeared to have upgrade logs, going right back to the upgrade I did of
> F23 to F24, but the names it listed were meaningless to me and it didn't
> provide any path references to where I might find the logs to be able to
> search them.
>
> Following your suggestion I ran a sudo dnf upgrade which produced all
> the conflict messages that I worked around by adding --allowerasing and
> --skip-broken, but this time dnf said to try --best and --allowerasing,
> which I did and that installed all the package updates that caused the
> conflicts. Having done this I was able to complete the upgrade to F28,
> but now I have big problems.
>
> Under F28 my USB network device doesn't work because dkms can't compile
> the driver for it, and, either because of this failure or a compile
> failure the drivers for my mouse haven't been installed by dkms either.
>
> Booting into the latest F27 kernel I have installed which is 4.17.3-100,
> where both drivers have previously successfully compiled and installed
> (which is how I'm able to send this email), the mouse drivers still
> compile but the usb device driver fails to compile. Both with the F28
> kernel, being 4.17.3-200, and the F27 kernel I mentioned, the compile
> fails with stdarg.h not found, so I'm now confused about what the F28
> upgrade has done. The F28 upgrade should not have updated the F27 kernel
> source that was already installed and hence there should not be any
> barriers to compiling the driver against the F27 kernel when under F27
> it did compile.
Uhm, did you get the libstdc++-devel RPM installed? It provides the
stdarg.h file, specifically:
/usr/include/c++/8/tr1/stdarg.h
Checking an old F26 VM I have, the equivalent file is:
/usr/include/c++/7/tr1/stdarg.h
I believe the C compiler will find it if it's installed. Even if it
does appear to be installed, a "dnf reinstall libstdc++-devel" should
clean up any cruft your messed-up install may have left.
I'll check this out, thankyou. The issue is caused because
/usr/src/kernels/4.17.3-100.fc27.x86_64/include/linux/kernel.h (this is
the location when compiling for the F27 kernel) has the following
include statements, and it is the first one that causes the problem:
#ifndef _LINUX_KERNEL_H
#define _LINUX_KERNEL_H
#include <stdarg.h>
#include <linux/linkage.h>
#include <linux/stddef.h>
#include <linux/types.h>
#include <linux/compiler.h>
#include <linux/bitops.h>
#include <linux/log2.h>
#include <linux/typecheck.h>
#include <linux/printk.h>
#include <linux/build_bug.h>
#include <asm/byteorder.h>
#include <uapi/linux/kernel.h>
regards,
Steve
> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
> - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
> - -
> ----------------------------------------------------------------------
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:27 p.m.
On 12/7/18 9:24 am, Stephen Morris wrote:
On 12/7/18 8:38 am, Rick Stevens wrote:
> On 07/11/2018 03:16 PM, Stephen Morris wrote:
>> On 11/7/18 8:47 am, Samuel Sieb wrote:
>>> On 07/10/2018 03:17 PM, Stephen Morris wrote:
>>>> 1). Can anyone shed any light on why the install may have failed and
>>>> what I need to do to work around it? I'm hoping I don't have to
run a
>>>> 'sudo dnf clean all' and then a 'sudo dnf system-upgrade
--refresh
>>>> --releasever=28 --allowerasing --skip-broken' to download all the
>>>> packages again.
>>> I wonder if the --skip-broken is a problem. Can you solve that before
>>> doing the upgrade?
>>>
>>> I think the packages should still be downloaded.
>>> Check in /var/lib/dnf/system-upgrade
>> All the packages were still downloaded.
>>>> 2). Where can I find the logs that would contain the error message so
>>>> I can read what it said, given that /var/log/boot.log and
>>>> /var/log/dnf.log both don't contain the message?
>>> Try "dnf system-upgrade log".
>> I issued that command and all it did was tell me there were 6 boots
>> that
>> appeared to have upgrade logs, going right back to the upgrade I did of
>> F23 to F24, but the names it listed were meaningless to me and it
>> didn't
>> provide any path references to where I might find the logs to be
>> able to
>> search them.
>>
>> Following your suggestion I ran a sudo dnf upgrade which produced all
>> the conflict messages that I worked around by adding --allowerasing and
>> --skip-broken, but this time dnf said to try --best and --allowerasing,
>> which I did and that installed all the package updates that caused the
>> conflicts. Having done this I was able to complete the upgrade to F28,
>> but now I have big problems.
>>
>> Under F28 my USB network device doesn't work because dkms can't compile
>> the driver for it, and, either because of this failure or a compile
>> failure the drivers for my mouse haven't been installed by dkms either.
>>
>> Booting into the latest F27 kernel I have installed which is
>> 4.17.3-100,
>> where both drivers have previously successfully compiled and installed
>> (which is how I'm able to send this email), the mouse drivers still
>> compile but the usb device driver fails to compile. Both with the F28
>> kernel, being 4.17.3-200, and the F27 kernel I mentioned, the compile
>> fails with stdarg.h not found, so I'm now confused about what the F28
>> upgrade has done. The F28 upgrade should not have updated the F27
>> kernel
>> source that was already installed and hence there should not be any
>> barriers to compiling the driver against the F27 kernel when under F27
>> it did compile.
> Uhm, did you get the libstdc++-devel RPM installed? It provides the
> stdarg.h file, specifically:
>
> /usr/include/c++/8/tr1/stdarg.h
>
> Checking an old F26 VM I have, the equivalent file is:
>
> /usr/include/c++/7/tr1/stdarg.h
>
> I believe the C compiler will find it if it's installed. Even if it
> does appear to be installed, a "dnf reinstall libstdc++-devel" should
> clean up any cruft your messed-up install may have left.
I'll check this out, thankyou. The issue is caused because
/usr/src/kernels/4.17.3-100.fc27.x86_64/include/linux/kernel.h (this
is the location when compiling for the F27 kernel) has the following
include statements, and it is the first one that causes the problem:
#ifndef _LINUX_KERNEL_H
#define _LINUX_KERNEL_H
#include <stdarg.h>
#include <linux/linkage.h>
#include <linux/stddef.h>
#include <linux/types.h>
#include <linux/compiler.h>
#include <linux/bitops.h>
#include <linux/log2.h>
#include <linux/typecheck.h>
#include <linux/printk.h>
#include <linux/build_bug.h>
#include <asm/byteorder.h>
#include <uapi/linux/kernel.h>
regards,
Steve
I've checked things out on this front and among others packages
clang5.0-libs, gcc and libstdc++-devel which are all already installed
have stdarg.h in their various folder structures under their include
folder, hence:
1). What do I need to do to get stdarg.h resolved from the correct
package for any compile done on the system at any time?
2). Why did F28 not add the appropriate folder into the include path
when the packages were upgraded, which seems to have happened when I
upgraded to F27?
regards,
Steve
>
>> ----------------------------------------------------------------------
>> - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
>> - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
>> - -
>> ----------------------------------------------------------------------
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:30 p.m.
On 07/12/2018 03:27 PM, Stephen Morris wrote:
I've checked things out on this front and among others packages
clang5.0-libs, gcc and libstdc++-devel which are all already installed
have stdarg.h in their various folder structures under their include
folder, hence:
1). What do I need to do to get stdarg.h resolved from the correct
package for any compile done on the system at any time?
2). Why did F28 not add the appropriate folder into the include path
when the packages were upgraded, which seems to have happened when I
upgraded to F27?
Did you miss my reply?
See https://github.com/lwfinger/rtl8723bu/issues/106 for a possible
solution.
6:50 p.m.
On 13/7/18 8:30 am, Samuel Sieb wrote:
On 07/12/2018 03:27 PM, Stephen Morris wrote:
> I've checked things out on this front and among others packages
> clang5.0-libs, gcc and libstdc++-devel which are all already
> installed have stdarg.h in their various folder structures under
> their include folder, hence:
>
> 1). What do I need to do to get stdarg.h resolved from the correct
> package for any compile done on the system at any time?
>
> 2). Why did F28 not add the appropriate folder into the include
> path when the packages were upgraded, which seems to have happened
> when I upgraded to F27?
Did you miss my reply?
See https://github.com/lwfinger/rtl8723bu/issues/106 for a possible
solution.
Sorry Samuel, I didn't miss your reply, what I did miss was the link at
the bottom. Having looked at the link the stale file referenced that
'make clean' did not remove existed in my location as well, and when
removed enabled the compile to work with the F27 kernel. I'm about to
reboot into the F28 kernel to check that it compiles with that.
regards,
Steve
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:59 p.m.
On 13/7/18 8:50 am, Stephen Morris wrote:
On 13/7/18 8:30 am, Samuel Sieb wrote:
> On 07/12/2018 03:27 PM, Stephen Morris wrote:
>> I've checked things out on this front and among others packages
>> clang5.0-libs, gcc and libstdc++-devel which are all already
>> installed have stdarg.h in their various folder structures under
>> their include folder, hence:
>>
>> 1). What do I need to do to get stdarg.h resolved from the
>> correct package for any compile done on the system at any time?
>>
>> 2). Why did F28 not add the appropriate folder into the include
>> path when the packages were upgraded, which seems to have happened
>> when I upgraded to F27?
>
> Did you miss my reply?
> See https://github.com/lwfinger/rtl8723bu/issues/106 for a possible
> solution.
Sorry Samuel, I didn't miss your reply, what I did miss was the link
at the bottom. Having looked at the link the stale file referenced
that 'make clean' did not remove existed in my location as well, and
when removed enabled the compile to work with the F27 kernel. I'm
about to reboot into the F28 kernel to check that it compiles with that.
I've just rebooted on the F28 kernel and having already removed
.cache.mk dkms was able to successfully compile the driver at boot time.
Thankyou to everyone who assisted with this issue.
regards,
Steve
>
>
> regards,
>
> Steve
>
>
>> _______________________________________________
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:46 p.m.
On Thu, 12 Jul 2018 08:16:06 +1000
Stephen Morris <samorris(a)netspace.net.au> wrote:
Both with the F28 kernel, being 4.17.3-200, and the F27 kernel I
mentioned, the compile fails with stdarg.h not found, so I'm now
confused about what the F28 upgrade has done. The F28 upgrade should
not have updated the F27 kernel source that was already installed and
hence there should not be any barriers to compiling the driver
against the F27 kernel when under F27 it did compile.
It sounds like you are either missing the package that provides the C
standard library include files, or its location has changed. I doubt
it has anything to do with the kernel.
On my system, I have the following hits when I use:
$ find /usr -iname '*stdarg*'
/usr/lib/dietlibc/include/stdarg-cruft.h
/usr/lib/dietlibc/include/stdarg.h
/usr/lib/gcc/x86_64-redhat-linux/8/include/cross-stdarg.h
/usr/lib/gcc/x86_64-redhat-linux/8/include/stdarg.h
/usr/lib/gcc/x86_64-redhat-linux/3.4.6/include/stdarg.h
/usr/lib64/llvm5.0/lib/clang/5.0.1/include/stdarg.h
/usr/lib64/bcc/include/stdarg.h
/usr/lib64/clang/6.0.0/include/stdarg.h
/usr/lib64/pcc/x86_64-unknown-linux-gnu/1.2.0.DEVEL/include/libpcc_stdarg.h
/usr/lib64/pcc/x86_64-unknown-linux-gnu/1.2.0.DEVEL/include/stdarg.h
/usr/lib64/perl5/stdarg.ph
/usr/share/castxml/clang/include/stdarg.h
/usr/share/root/cling/lib/clang/5.0.0/include/stdarg.h
/usr/share/splint/imports/stdarg.lcs
/usr/share/splint/imports/stdarg.lcl
/usr/share/man/man0p/stdarg.h.0p.gz
/usr/share/man/man3/stdarg.3.gz
/usr/share/sdcc/include/pic16/stdarg.h
/usr/share/sdcc/include/stdarg.h
/usr/include/efi/efistdarg.h
/usr/include/c++/8/tr1/cstdarg
/usr/include/c++/8/tr1/stdarg.h
/usr/include/c++/8/cstdarg
/usr/include/boost/compatibility/cpp_c_headers/cstdarg
I think this
/usr/lib/gcc/x86_64-redhat-linux/8/include/stdarg.h
is the official one, though I'm not sure where the drivers you are
trying to compile are looking. You could look at them (use a grep for
stdarg) in their source directory. The standard version comes from the
gcc package, gcc-8.1.1-1.fc28.x86_64. Is it installed on your system?
7:28 p.m.
Stephen Morris writes:
and that installed all the package updates that caused the conflicts.
Having
done this I was able to complete the upgrade to F28, but now I have big
problems.
Under F28 my USB network device doesn't work because dkms can't compile the
driver for it, and, either because of this failure or a compile failure the
drivers for my mouse haven't been installed by dkms either.
Pardon the interruption, but are you saying that you need to use a binary
blob for a mouse? A mouse?
What kinds of a mouse needs a binary blob driver?
5:57 p.m.
On 12/7/18 9:28 am, Sam Varshavchik wrote:
Stephen Morris writes:
> and that installed all the package updates that caused the conflicts.
> Having done this I was able to complete the upgrade to F28, but now I
> have big problems.
>
> Under F28 my USB network device doesn't work because dkms can't
> compile the driver for it, and, either because of this failure or a
> compile failure the drivers for my mouse haven't been installed by
> dkms either.
Pardon the interruption, but are you saying that you need to use a
binary blob for a mouse? A mouse?
What kinds of a mouse needs a binary blob driver?
I have a bluetooth gaming mouse which has 5 or 6 different drivers to
provide all the functionality the mouse is capable of, and all of these
drivers are linked into the kernel.
The mouse is a Razor Orochi.
regards,
Steve
>
>
>
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
6:16 p.m.
On 07/12/2018 02:57 PM, Stephen Morris wrote:
On 12/7/18 9:28 am, Sam Varshavchik wrote:
> Stephen Morris writes:
>
>> and that installed all the package updates that caused the conflicts.
>> Having done this I was able to complete the upgrade to F28, but now I
>> have big problems.
>>
>> Under F28 my USB network device doesn't work because dkms can't
>> compile the driver for it, and, either because of this failure or a
>> compile failure the drivers for my mouse haven't been installed by
>> dkms either.
>
> Pardon the interruption, but are you saying that you need to use a
> binary blob for a mouse? A mouse?
>
> What kinds of a mouse needs a binary blob driver?
I have a bluetooth gaming mouse which has 5 or 6 different drivers to
provide all the functionality the mouse is capable of, and all of these
drivers are linked into the kernel.
The mouse is a Razor Orochi.
Oh, wow! Razor hardware. Really cool for gaming. Overkill for Fedora-
esque stuff. Never could get used to that woven cover they used on the
cords to keyboards, mice, etc. (we made some gaming stations and needed
corded mice and keyboards). The fabric seems to generate a gravitational
field that selectively attracts any Velcro-type thing in the immediate
vicinity and spot welds to it.
Steve, have you found out whether that RPM had been installed or not,
and if so, reinstalled it? For reference, it's "libstdc++-devel".
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- I won't rise to the occasion, but I'll slide over to it. -
----------------------------------------------------------------------
6:38 p.m.
On 13/7/18 8:16 am, Rick Stevens wrote:
On 07/12/2018 02:57 PM, Stephen Morris wrote:
> On 12/7/18 9:28 am, Sam Varshavchik wrote:
>> Stephen Morris writes:
>>
>>> and that installed all the package updates that caused the conflicts.
>>> Having done this I was able to complete the upgrade to F28, but now I
>>> have big problems.
>>>
>>> Under F28 my USB network device doesn't work because dkms can't
>>> compile the driver for it, and, either because of this failure or a
>>> compile failure the drivers for my mouse haven't been installed by
>>> dkms either.
>> Pardon the interruption, but are you saying that you need to use a
>> binary blob for a mouse? A mouse?
>>
>> What kinds of a mouse needs a binary blob driver?
> I have a bluetooth gaming mouse which has 5 or 6 different drivers to
> provide all the functionality the mouse is capable of, and all of these
> drivers are linked into the kernel.
>
> The mouse is a Razor Orochi.
Oh, wow! Razor hardware. Really cool for gaming. Overkill for Fedora-
esque stuff. Never could get used to that woven cover they used on the
cords to keyboards, mice, etc. (we made some gaming stations and needed
corded mice and keyboards). The fabric seems to generate a gravitational
field that selectively attracts any Velcro-type thing in the immediate
vicinity and spot welds to it.
Steve, have you found out whether that RPM had been installed or not,
and if so, reinstalled it? For reference, it's "libstdc++-devel".
The problem with the mouse was until the drivers were installed the
bluetooth interface couldn't even see the mouse to run it in wireless
mode. At the moment I don't remember whether I needed the drivers to run
the mouse in corded mode.
I checked this morning in libstdc++-devel is already installed as are
several other packages that have stdargs.h, one of which is gcc itself.
I haven't tried reinstalling it yet, I'll do that now.
regards,
Steve
> ----------------------------------------------------------------------
> - Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
> - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
> - -
> - I won't rise to the occasion, but I'll slide over to it. -
> ----------------------------------------------------------------------
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...
10:16 p.m.
Stephen Morris writes:
On 12/7/18 9:28 am, Sam Varshavchik wrote:
> Stephen Morris writes:
>
>> and that installed all the package updates that caused the conflicts. Having
>> done this I was able to complete the upgrade to F28, but now I have big
>> problems.
>>
>> Under F28 my USB network device doesn't work because dkms can't compile
the
>> driver for it, and, either because of this failure or a compile failure the
>> drivers for my mouse haven't been installed by dkms either.
>
> Pardon the interruption, but are you saying that you need to use a binary
> blob for a mouse? A mouse?
>
> What kinds of a mouse needs a binary blob driver?
I have a bluetooth gaming mouse which has 5 or 6 different drivers to
provide all the functionality the mouse is capable of, and all of these
drivers are linked into the kernel.
The mouse is a Razor Orochi.
The problem is that there is absolutely no guarantee whatsoever insofar as
API and ABI compatibility across Linux kernel versions. Internal APIs
between major internal kernel components don't change much, over time. But
when it comes to things like low-level device drivers, you've got no
guarantees that the same source can be compiled against the next kernel
release, unchanged.
The only way to guarantee that a particular driver's code will compile with
the next kernel is for that driver to be a part of the mainline kernel.
That's not an absolute, 100% guarantee, but it's the best that can be hoped
for. If you have a particular driver that was built for a particular kernel
version, but it's not part of the mainline kernel itself, maybe it will
still compile and work properly against the next kernel version, or maybe it
will not. And if it doesn't, there is no magic button one can push, or one
some magic rpm can be installed, to make it compile. One will have to look
the actual compilation error, look at the previous kernel's source, look at
the current kernel's source, figure out what's changed, and figure out what
needs to be changed, in the driver's source, to update it to your current
kernel's version.
For your use case, Fedora is not going to work very well, with new kernel
version updates almost every week. Practically, you should be using Linux
distribution with a stable kernel, that will backport any bug fixes to its
stable kernel version; like Centos/RHEL or Ubuntu LTS. That's what those
distros are for: to provide a stable kernel for the lifetime of the release,
that third party hardware OEM can target their custom kernel drivers for.
2107
days inactive
2110
days old
15 comments
5 participants
participants (5)
-
Rick Stevens -
Sam Varshavchik -
Samuel Sieb -
stan -
Stephen Morris