Re: kernel-headers package is missing in fedora-updates
On 4/25/23 06:43, Nils Smeds wrote: This makes kernel updates break for any user who needs the headers (for example to build 3rd party kernel modules [NVidia]) The kernel headers package is not updated for every kernel release because that's not necessary. Have you tried it? Is compiling not working? ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: kernel-headers package is missing in fedora-updates
This is FC38 [nsmeds-x1(nsmeds):~] sudo dnf list --available kernel-headers kernel [sudo] password for nsmeds: Last metadata expiration check: 0:10:29 ago on Tue 25 Apr 2023 15:33:40 CEST. Available Packages kernel.x86_64 6.2.12-300.fc38 updates kernel-headers.i686 6.2.6-300.fc38 fedora ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
kernel-headers package is missing in fedora-updates
This makes kernel updates break for any user who needs the headers (for example to build 3rd party kernel modules [NVidia]) ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Kernel headers version mismatch?
Dear Qiyu Yan, Thanks; you are correct. I tried a fresh F34 install. The rpm was pulling in kernel-debug-devel not kernel-devel. It then spat: DKMS: add completed. Error! echo Your kernel headers for kernel 5.11.12-300.fc34.x86_64 cannot be found at /lib/modules/5.11.12-300.fc34.x86_64/build or /lib/modules/5.11.12-300.fc34.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located. If I install kernel-devel first it works (well actually it doesn't work but for a quite separate, old, reason which I was hoping F34 might have fixed) Sounds like an issue with the rpm dependencies. But its also a rather unhelpful error message. Bill On 22/04/2021 13:11, Qiyu Yan wrote: 在 2021-04-22星期四的 12:30 +0100，William John Murray写道： Dear all, I wanted to test openafs on Fedora 34 RC1, using jsbillings repo, relying on dkms. The problem is the kernel is 5.11.12, but the kernel-headers is 5.11.11. kernel-headers don't need to exactly match kernel version. I enabled updates-testing and upgraded, to get kernel is 5.11.15, but the kernel-headers is 5.11.14! So dkms cannot build. I don't seem to be able to find matching kernel I think you may need kernel-devel, just dnf install kernel would be fine. & header versions. I can bodge it with a softlink which works, but this may cause others trouble? Bill -- Bill Murray STFC-RAL / Warwick University Sent from my laptop Skype william.john.murray Tel +44 7826 486185 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en- US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraprojec t.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure -- Bill Murray STFC-RAL / Warwick University Sent from my laptop Skype william.john.murray Tel +44 7826 486185 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Kernel headers version mismatch?
在 2021-04-22星期四的 12:30 +0100，William John Murray写道： > Dear all, > > I wanted to test openafs on Fedora 34 RC1, using jsbillings > repo, > relying on dkms. > > The problem is the kernel is 5.11.12, but the kernel-headers is > 5.11.11. kernel-headers don't need to exactly match kernel version. > > I enabled updates-testing and upgraded, to get kernel is 5.11.15, but > the kernel-headers is 5.11.14! > > So dkms cannot build. I don't seem to be able to find matching > kernel I think you may need kernel-devel, just dnf install kernel would be fine. > & header versions. I can bodge it with a softlink which works, but > this > may cause others trouble? > > Bill > > > -- > Bill Murray > STFC-RAL / Warwick University > Sent from my laptop > Skype william.john.murray Tel +44 7826 486185 > ___ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: https://docs.fedoraproject.org/en- > US/project/code-of-conduct/ > List Guidelines: > https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraprojec > t.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure signature.asc Description: This is a digitally signed message part ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Kernel headers version mismatch?
Dear all, I wanted to test openafs on Fedora 34 RC1, using jsbillings repo, relying on dkms. The problem is the kernel is 5.11.12, but the kernel-headers is 5.11.11. I enabled updates-testing and upgraded, to get kernel is 5.11.15, but the kernel-headers is 5.11.14! So dkms cannot build. I don't seem to be able to find matching kernel & header versions. I can bodge it with a softlink which works, but this may cause others trouble? Bill -- Bill Murray STFC-RAL / Warwick University Sent from my laptop Skype william.john.murray Tel +44 7826 486185 ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Older kernel headers
On Thu, 2015-08-20 at 15:27 +0100, Russel Winder wrote: > I try to manage kernels so that I always have the last public release > as > well as the most up to date RC and the previous one. On laptops I > just run > the latest RC as ot always seems to work (except occasionally). For > my > workstation though I need the NVIDIA driver which almost never > compiles > with the latest RC kernel (*). So I generally run the last public > release > kernel on my workstation s as to be able to compile the NVIDIA > driver. Not > usually a problem since kernel updates do not remove kernels, I do > that > manually. However a recent removal of something has led to the 4.1.0 > kernel > header file package being removed, and, of course, it is no longer > available in the Rawhide repository. > > What is the officially correct way of getting back older kernel > header > packages? Grab it from Koji, if it hasn't been garbage-collected. The rules on garbage collection I'm not 100% sure of, but I think packages which made the repos live much longer. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Older kernel headers
I try to manage kernels so that I always have the last public release as well as the most up to date RC and the previous one. On laptops I just run the latest RC as ot always seems to work (except occasionally). For my workstation though I need the NVIDIA driver which almost never compiles with the latest RC kernel (*). So I generally run the last public release kernel on my workstation s as to be able to compile the NVIDIA driver. Not usually a problem since kernel updates do not remove kernels, I do that manually. However a recent removal of something has led to the 4.1.0 kernel header file package being removed, and, of course, it is no longer available in the Rawhide repository. What is the officially correct way of getting back older kernel header packages? (*) Laptops running standard Rawhide kernels, workstation running the special kernels without debugging. -- Russel. = Dr Russel Winder t:+44 20 7585 2200 voip:sip: russel.win...@ekiga.net 41 Buckmaster Road m:+44 7770 465 077 xmpp:rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder signature.asc Description: This is a digitally signed message part -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel-headers for 3.15 rc8 conflict with kernel-headers-3.15.0-0.rc7.git0.1.fc21.x86_64
On 06/05/2014 02:30 PM, Adam Williamson wrote: > On Thu, 2014-06-05 at 13:25 -0500, Kevin Martin wrote: >> Today while doing a dnf upgrade I got a conflict message about the >> kernel-headers for 3.15 rc8 conflicting with 3.15 rc7.git0.1. I >> was forced to rpm -e the rc7 headers (with --nodeps) to be able to install >> the rc8 versions and allow the whole set of necessary >> kernel packages to install so grub2 would update it's config properly. >> >> Just letting you know. > > That sounds like possibly a dnf bug. kernel-headers is like > kernel-devel, not kernel-core: you should only have one kernel-headers > at a time. dnf shouldn't have tried to install them alongside each > other. > > IIRC there was a new release of dnf recently - that could be the issue. > Ales, any ideas? > > It'd help if you had the exact dnf output; I believe dnf history should > be able to show it. > dnf history is not showing that output error but I recall dnf complained about /usr/include/linux/audit.h conflicting between the two kernel-header versions. I'm running dnf-0.5.2-1 fwiw. Kevin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel-headers for 3.15 rc8 conflict with kernel-headers-3.15.0-0.rc7.git0.1.fc21.x86_64
On Thu, 2014-06-05 at 13:25 -0500, Kevin Martin wrote: > Today while doing a dnf upgrade I got a conflict message about the > kernel-headers for 3.15 rc8 conflicting with 3.15 rc7.git0.1. I > was forced to rpm -e the rc7 headers (with --nodeps) to be able to install > the rc8 versions and allow the whole set of necessary > kernel packages to install so grub2 would update it's config properly. > > Just letting you know. That sounds like possibly a dnf bug. kernel-headers is like kernel-devel, not kernel-core: you should only have one kernel-headers at a time. dnf shouldn't have tried to install them alongside each other. IIRC there was a new release of dnf recently - that could be the issue. Ales, any ideas? It'd help if you had the exact dnf output; I believe dnf history should be able to show it. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
kernel-headers for 3.15 rc8 conflict with kernel-headers-3.15.0-0.rc7.git0.1.fc21.x86_64
Today while doing a dnf upgrade I got a conflict message about the kernel-headers for 3.15 rc8 conflicting with 3.15 rc7.git0.1. I was forced to rpm -e the rc7 headers (with --nodeps) to be able to install the rc8 versions and allow the whole set of necessary kernel packages to install so grub2 would update it's config properly. Just letting you know. Kevin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers - Now a BIGGER Issue
On Mon, 2013-01-14 at 09:16 -0700, Christopher A Williams wrote: > O > n Mon, 2013-01-14 at 09:20 -0600, Justin M. Forbes wrote: > > > > > > > > ...And because of the way Workstation 9.0.1 is trying to deal with it, I > > > believe this now falls squarely back on the Fedora team to look at and > > > resolve. You can't blame Workstation or its licensing model - don't even > > > start. > > > > > > > The UAPI changes are upstream starting with 3.7 kernels, and won't be going > > away. VMWare should fix their build scripts at some point, everyone else > > seems to have figured it out early in the RC phase of 3.7. There is nothing > > Fedora specific about this. We aren't doing anything wonky. > > OK, so you're not doing anything unusual with the kernel. Fine. But I > doubt everyone else has figured this out in the 3.7 RC series. > > That said, I am pointing this out within VMware circles as well. I don't > really have the cycles to go poking through everyone's scripts right now > (else I would have already). After some digging tonight, I found the appropriate work-around to get this going on the current 3.7 kernel. Ironically, the statement "The UAPI changes are upstream..." tipped me off. The correct symlink command for the current 3.7 kernel is: ln -s /usr/src/kernels/3.7.2-201.fc18.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.7.2-201.fc18.x86_64/include/linux/version.h When new kernel versions come out, this will need to be modified again until VMware patches their scripts to handle the UAPI changes. Once this symlink is done, Workstation 9.0.1 runs as it should. Chris -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers - Now a BIGGER Issue
O n Mon, 2013-01-14 at 09:20 -0600, Justin M. Forbes wrote: > > > > > ...And because of the way Workstation 9.0.1 is trying to deal with it, I > > believe this now falls squarely back on the Fedora team to look at and > > resolve. You can't blame Workstation or its licensing model - don't even > > start. > > > > The UAPI changes are upstream starting with 3.7 kernels, and won't be going > away. VMWare should fix their build scripts at some point, everyone else > seems to have figured it out early in the RC phase of 3.7. There is nothing > Fedora specific about this. We aren't doing anything wonky. OK, so you're not doing anything unusual with the kernel. Fine. But I doubt everyone else has figured this out in the 3.7 RC series. That said, I am pointing this out within VMware circles as well. I don't really have the cycles to go poking through everyone's scripts right now (else I would have already). Chris -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers - Now a BIGGER Issue
On Mon, Jan 14, 2013 at 08:04:56AM -0700, Christopher A Williams wrote: > > ...And because of the way Workstation 9.0.1 is trying to deal with it, I > believe this now falls squarely back on the Fedora team to look at and > resolve. You can't blame Workstation or its licensing model - don't even > start. > The UAPI changes are upstream starting with 3.7 kernels, and won't be going away. VMWare should fix their build scripts at some point, everyone else seems to have figured it out early in the RC phase of 3.7. There is nothing Fedora specific about this. We aren't doing anything wonky. Justin -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers - Now a BIGGER Issue
On Sun, 2013-01-13 at 07:49 -0800, Tom London wrote: -- Christopher A Williams > > found in: > > > > /usr/src/kernels/3.6.11-3.fc18.x86_64/include/linux > > > > Put that all together and I suspect that the actual issue isn't so much > > the different tree structure - it's consistent on F18 between the 3.6 > > and 3.7 series kernels. Rather, something has changed in the > > updates-testing kernel package which is causing the Workstation scripts > > to not be able to properly traverse the tree to find what they need. > > > > Hope that makes sense! As mentioned, I believe an appropriate symlink > > will provide a work-around, but we should look at both the development > > packages and the workstation scripts to evaluate where the most > > appropriate fix should go. I'm sure this won't be the only package that > > has this issue. > > > > Unfortunately, since I'm getting on another airplane today, I won't have > > much more opportunity to look at this for a while. Hopefully someone > > else will be able to pick things up from here... > > > > Chris > > > > -- > > Christopher A. Williams > > > > Not sure this helps, but: > > [root@tlondon ~]# locate /usr/\*/linux/version.h > /usr/include/linux/version.h > /usr/src/kernels/3.8.0-0.rc2.git3.1.fc19.x86_64/include/generated/uapi/linux/version.h > /usr/src/kernels/3.8.0-0.rc2.git4.2.local.fc19.x86_64/include/generated/uapi/linux/version.h > /usr/src/kernels/3.8.0-0.rc2.git4.2.local2.fc19.x86_64/include/generated/uapi/linux/version.h > /usr/src/kernels/3.8.0-0.rc3.git0.3.local.fc19.x86_64/include/generated/uapi/linux/version.h > [root@tlondon ~]# > [root@tlondon ~]# ls -l $(locate /usr/\*/linux/version.h) > -rw-r--r--. 1 root root 97 Jan 11 10:40 /usr/include/linux/version.h > -rw-r--r--. 4 root root 97 Jan 7 15:25 > /usr/src/kernels/3.8.0-0.rc2.git3.1.fc19.x86_64/include/generated/uapi/linux/version.h > -rw-r--r--. 4 root root 97 Jan 7 15:25 > /usr/src/kernels/3.8.0-0.rc2.git4.2.local2.fc19.x86_64/include/generated/uapi/linux/version.h > -rw-r--r--. 4 root root 97 Jan 7 15:25 > /usr/src/kernels/3.8.0-0.rc2.git4.2.local.fc19.x86_64/include/generated/uapi/linux/version.h > -rw-r--r--. 4 root root 97 Jan 7 15:25 > /usr/src/kernels/3.8.0-0.rc3.git0.3.local.fc19.x86_64/include/generated/uapi/linux/version.h > [root@tlondon ~]# OK - Thanks for extra info. I'm now in a situation where I must do something. The latest kernel update came through this morning and we now have the kernel 3.7 headers problem with Workstation hitting the branched repo as opposed to the updates-testing repo. ...And because of the way Workstation 9.0.1 is trying to deal with it, I believe this now falls squarely back on the Fedora team to look at and resolve. You can't blame Workstation or its licensing model - don't even start. The update to kernel 3.7.2-201.fc18.x86_64 has the same kernel headers problem. Except Workstation comes back with a specific error message saying that it cannot find the header files. It then specifically asks for the location of the header files. it even gives you a nic file picker that's defaulting to the directory /usr/src/kernels for you to start looking. Giving it the location /usr/src/kernels/3.7.2-201.fc18.x86_64 doesn't work. I'm assuming this is the correct location for the kernel header files. Since Workstation is clearly allowing you to specify the location of the header files and still can't find them, something with the new kernel 3.7 is, in my opinion, broken. Can we please have a look at this? I will BZ as necessary... Chris -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sun, Jan 13, 2013 at 7:05 AM, Christopher A. Williams wrote: > On Sat, 2013-01-12 at 19:32 -0700, Christopher A. Williams wrote: > > > >> ...Looked again at this. It's actually not quite what's needed. It says >> to make a symbolic link from: >> >> /usr/src/linux-3.7/include/generated/uapi/linux/version.h >> >> to >> >> /usr/src/linux-3.7/include/linux/version.h >> >> only problem is that this first directory doesn't exist in Fedora from >> what I can see. the file is actually located in: >> >> /usr/src/kernels//include/linux/version.h >> >> Is this a departure in Fedora from the stock kernel 3.7 series? I'll bet >> this is really messing with VMware's scripts if it is. Since I am not >> running Kernel 3.7 at the moment and don't have time to do so now, we'll >> need someone else to have a look at this. I'm sure it's probably an easy >> fix. > > More info from Lawrence Graves (apologize for the cross-post in threads, > but I thought it was important to keep this on the initial thread...) > > > this is the results of trying to apply the fix to kernel headers problem > I am experiencing. > [root@Jehovah ~]# ln > -s /usr/src/linux-3.7/include/generated/uapi/linux/version.h > /usr/src/linux-3.7/include/linux/version.h > ln: failed to create symbolic link > ‘/usr/src/linux-3.7/include/linux/version.h’: No such file or directory > [root@Jehovah ~]# vmware-modconfig --console --install-all > gcc and kernel headers must be installed > [root@Jehovah ~]# > ln /usr/src/linux-3.7/include/generated/uapi/linux/version.h > /usr/src/linux-3.7/include/linux/version.h > ln: accessing > ‘/usr/src/linux-3.7/include/generated/uapi/linux/version.h’: No such > file or directory > [root@Jehovah ~]# ln > -s /usr/src/linux-3.7/include/generated/uapi/linux/version.h > /usr/src/linux-3.7/include/linux/version.h > ln: failed to create symbolic link > ‘/usr/src/linux-3.7/include/linux/version.h’: No such file or directory > > > > This confirms what I was reporting before. The referenced directory > structure reported as a kernel 3.7 fix will not work with the current > 3.7 series kernel in updates-testing. > > Combine this with that Workstation works fine on the 3.6 series kernel > using the same overall directory structure leads me to that the symlink > needs to be adjusted to fit the F18 kernel development directory tree, > at least as a temporary work-around. > > Also note that the appropriate version.h file for kernel 3.6 is indeed > found in: > > /usr/src/kernels/3.6.11-3.fc18.x86_64/include/linux > > Put that all together and I suspect that the actual issue isn't so much > the different tree structure - it's consistent on F18 between the 3.6 > and 3.7 series kernels. Rather, something has changed in the > updates-testing kernel package which is causing the Workstation scripts > to not be able to properly traverse the tree to find what they need. > > Hope that makes sense! As mentioned, I believe an appropriate symlink > will provide a work-around, but we should look at both the development > packages and the workstation scripts to evaluate where the most > appropriate fix should go. I'm sure this won't be the only package that > has this issue. > > Unfortunately, since I'm getting on another airplane today, I won't have > much more opportunity to look at this for a while. Hopefully someone > else will be able to pick things up from here... > > Chris > > -- > Christopher A. Williams > Not sure this helps, but: [root@tlondon ~]# locate /usr/\*/linux/version.h /usr/include/linux/version.h /usr/src/kernels/3.8.0-0.rc2.git3.1.fc19.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.8.0-0.rc2.git4.2.local.fc19.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.8.0-0.rc2.git4.2.local2.fc19.x86_64/include/generated/uapi/linux/version.h /usr/src/kernels/3.8.0-0.rc3.git0.3.local.fc19.x86_64/include/generated/uapi/linux/version.h [root@tlondon ~]# [root@tlondon ~]# ls -l $(locate /usr/\*/linux/version.h) -rw-r--r--. 1 root root 97 Jan 11 10:40 /usr/include/linux/version.h -rw-r--r--. 4 root root 97 Jan 7 15:25 /usr/src/kernels/3.8.0-0.rc2.git3.1.fc19.x86_64/include/generated/uapi/linux/version.h -rw-r--r--. 4 root root 97 Jan 7 15:25 /usr/src/kernels/3.8.0-0.rc2.git4.2.local2.fc19.x86_64/include/generated/uapi/linux/version.h -rw-r--r--. 4 root root 97 Jan 7 15:25 /usr/src/kernels/3.8.0-0.rc2.git4.2.local.fc19.x86_64/include/generated/uapi/linux/version.h -rw-r--r--. 4 root root 97 Jan 7 15:25 /usr/src/kernels/3.8.0-0.rc3.git0.3.local.fc19.x86_64/include/generated/uapi/linux/version.h [root@tlondon ~]# tom -- Tom London -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 2013-01-12 at 19:32 -0700, Christopher A. Williams wrote: > ...Looked again at this. It's actually not quite what's needed. It says > to make a symbolic link from: > > /usr/src/linux-3.7/include/generated/uapi/linux/version.h > > to > > /usr/src/linux-3.7/include/linux/version.h > > only problem is that this first directory doesn't exist in Fedora from > what I can see. the file is actually located in: > > /usr/src/kernels//include/linux/version.h > > Is this a departure in Fedora from the stock kernel 3.7 series? I'll bet > this is really messing with VMware's scripts if it is. Since I am not > running Kernel 3.7 at the moment and don't have time to do so now, we'll > need someone else to have a look at this. I'm sure it's probably an easy > fix. More info from Lawrence Graves (apologize for the cross-post in threads, but I thought it was important to keep this on the initial thread...) this is the results of trying to apply the fix to kernel headers problem I am experiencing. [root@Jehovah ~]# ln -s /usr/src/linux-3.7/include/generated/uapi/linux/version.h /usr/src/linux-3.7/include/linux/version.h ln: failed to create symbolic link ‘/usr/src/linux-3.7/include/linux/version.h’: No such file or directory [root@Jehovah ~]# vmware-modconfig --console --install-all gcc and kernel headers must be installed [root@Jehovah ~]# ln /usr/src/linux-3.7/include/generated/uapi/linux/version.h /usr/src/linux-3.7/include/linux/version.h ln: accessing ‘/usr/src/linux-3.7/include/generated/uapi/linux/version.h’: No such file or directory [root@Jehovah ~]# ln -s /usr/src/linux-3.7/include/generated/uapi/linux/version.h /usr/src/linux-3.7/include/linux/version.h ln: failed to create symbolic link ‘/usr/src/linux-3.7/include/linux/version.h’: No such file or directory This confirms what I was reporting before. The referenced directory structure reported as a kernel 3.7 fix will not work with the current 3.7 series kernel in updates-testing. Combine this with that Workstation works fine on the 3.6 series kernel using the same overall directory structure leads me to that the symlink needs to be adjusted to fit the F18 kernel development directory tree, at least as a temporary work-around. Also note that the appropriate version.h file for kernel 3.6 is indeed found in: /usr/src/kernels/3.6.11-3.fc18.x86_64/include/linux Put that all together and I suspect that the actual issue isn't so much the different tree structure - it's consistent on F18 between the 3.6 and 3.7 series kernels. Rather, something has changed in the updates-testing kernel package which is causing the Workstation scripts to not be able to properly traverse the tree to find what they need. Hope that makes sense! As mentioned, I believe an appropriate symlink will provide a work-around, but we should look at both the development packages and the workstation scripts to evaluate where the most appropriate fix should go. I'm sure this won't be the only package that has this issue. Unfortunately, since I'm getting on another airplane today, I won't have much more opportunity to look at this for a while. Hopefully someone else will be able to pick things up from here... Chris -- Christopher A. Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 2013-01-12 at 09:23 -0700, Christopher A. Williams wrote: > On Sat, 2013-01-12 at 15:26 +, Frank Murphy wrote: > > On Sat, 12 Jan 2013 07:56:40 -0700 > > "Christopher A. Williams" wrote: > > > > > > http://slackblogs.blogspot.ie/2012/12/linux-kernel-37-vmware-workstation-and.html > > thank the great God Google, > > now why didn't I think of that ;) > > Now why didn't I try _that_ search string... > > Ask Google the right question and you get amazing results. ;-) ...Looked again at this. It's actually not quite what's needed. It says to make a symbolic link from: /usr/src/linux-3.7/include/generated/uapi/linux/version.h to /usr/src/linux-3.7/include/linux/version.h only problem is that this first directory doesn't exist in Fedora from what I can see. the file is actually located in: /usr/src/kernels//include/linux/version.h Is this a departure in Fedora from the stock kernel 3.7 series? I'll bet this is really messing with VMware's scripts if it is. Since I am not running Kernel 3.7 at the moment and don't have time to do so now, we'll need someone else to have a look at this. I'm sure it's probably an easy fix. Chris -- Christopher A. Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 2013-01-12 at 15:26 +, Frank Murphy wrote: > On Sat, 12 Jan 2013 07:56:40 -0700 > "Christopher A. Williams" wrote: > > > http://slackblogs.blogspot.ie/2012/12/linux-kernel-37-vmware-workstation-and.html > thank the great God Google, > now why didn't I think of that ;) Now why didn't I try _that_ search string... Ask Google the right question and you get amazing results. ;-) Chris -- Christopher A. Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 2013-01-12 at 15:26 +, "Jóhann B. Guðmundsson" wrote: > On 01/12/2013 02:56 PM, Christopher A. Williams wrote: > > On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote: > >> On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote: > > .. > > > ... > Aren't you just experiencing that broken vmware scripts which cant find > the relocated version.h in the 3.7 series kernels ? > > And that's simply solved by running "ln -s > /usr/src/linux-3.7-X/include/generated/uapi/linux/version.h > /usr/src/linux-3.7-X/include/linux/version.h" Probably. I didn't have much time to really dig into it at the time and it wouldn't surprise me at all if it wasn't something as simple as that. When I looked, a lot of the stuff showing up on Google now wasn't there and I've been riding a lot of airplanes lately. I'll tell Graves (OP) to try this and get back to us. Chris -- Christopher A. Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 2013-01-12 at 10:29 -0500, Matthew Miller wrote: > On Sat, Jan 12, 2013 at 07:56:40AM -0700, Christopher A. Williams wrote: > > On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote: > > VMware Workstation for my work (some things needed for my job require > > Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I > > Any particular reason not to use KVM? Save you some headache. Yes. Actually I do also play around with KVM and a ton of other hypervisors. But I get Workstation basically for free as well. Call it a fringe benefit of having a VCP, VCAP-DCA, and a VCAP-DCD, while leading a rather large Cloud infrastructure practice that specializes in virtualizing business critical applications (aka VBCA) :-) Workstation also works very nicely with all of my vSphere systems that I have to take care of as well. And, to be fair, trading out Workstation for KVM is trading one set of headaches for another. Voice of experience on that one... Chris PS: If you want to know more about VBCA stuff, just Google "Cognizant VBCA" and look for the video VMware posted of me. I'll be teaching the Oracle virtualization course next month at the VBCA Boot Camp at Partner Exchange. Look me up if you're going. -- Christopher A. Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On 01/12/2013 02:56 PM, Christopher A. Williams wrote: On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote: On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote: .. Actually, in this case, the kernel-headers and kernel-devel packages are installed. Further, this appears to only happen with the 3.7 series of the kernel. I know this because I was having the same problem and, because I need VMware Workstation for my work (some things needed for my job require Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I can confirm that VMware Workstation 9.0.1 is working with kernel version 3.6.11-3.fc18.x86_64 - and is working with that kernel unmodified (no patches from VMware needed). Now, I don't recall the exact error message with kernel 3.7 because I reverted back to the 3.6 series (via yum distro-sync), but VMware Workstation 9.0.1 clearly is having trouble finding the kernel headers and other associated components with the 3.7 series of the kernel that is in the updates-testing repository. Aren't you just experiencing that broken vmware scripts which cant find the relocated version.h in the 3.7 series kernels ? And that's simply solved by running "ln -s /usr/src/linux-3.7-X/include/generated/uapi/linux/version.h /usr/src/linux-3.7-X/include/linux/version.h" JBG -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, Jan 12, 2013 at 07:56:40AM -0700, Christopher A. Williams wrote: > On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote: > VMware Workstation for my work (some things needed for my job require > Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I Any particular reason not to use KVM? Save you some headache. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, Jan 12, 2013 at 04:57:49AM -0700, Lawrence Graves wrote: > Everyone is blaming the inability of vmware workstation to compile > on vmware/ nvidia people, when theerror message received says it > can't find where the C file is located to compile. That seems to be > a kernel error not a vmware or nvidia error. Please look into this > minor problem. Probably a file they are looking for changed. They'll need to update their build tools to look in the right place. The kernel makes a guarantee to not cause problems for userspace programs with new versions. It makes no such guarantee for kernel modules. This is one of the reasons the Linux kernel has been able to adapt and grow so well, and also one of the reasons out-of-tree kernel modules (whether commercial or open source) are problematic. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 12 Jan 2013 07:56:40 -0700 "Christopher A. Williams" wrote: http://slackblogs.blogspot.ie/2012/12/linux-kernel-37-vmware-workstation-and.html thank the great God Google, now why didn't I think of that ;) -- Regards, Frank "Still trying to learn, both old and new tricks" --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 2013-01-12 at 07:26 -0500, Scott Robbins wrote: > On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote: > > what the error message says is that it could not find the kernel headers for > > kernel 3.7.1-5. I know that they were installed. So where are the kernel > > header > > file if in fact it was installed. > > Usually, if VMware can't find kernel-headers, you need the kernel-devel > package. > > The kernel-devel package number has to match the result of uname -r. What > I frequently see on the forums is that someone updated, got a newer package > of kernel-devel, but hasn't rebooted, so there will be a version mismatch. > > Also, if running a PAE kernel, one has to specify kernel-PAE-devel. (Which > doesn't seem relevant in your case). Actually, in this case, the kernel-headers and kernel-devel packages are installed. Further, this appears to only happen with the 3.7 series of the kernel. I know this because I was having the same problem and, because I need VMware Workstation for my work (some things needed for my job require Windows - arrgh!!!), I had to roll back to the 3.6 kernel. Currently, I can confirm that VMware Workstation 9.0.1 is working with kernel version 3.6.11-3.fc18.x86_64 - and is working with that kernel unmodified (no patches from VMware needed). Now, I don't recall the exact error message with kernel 3.7 because I reverted back to the 3.6 series (via yum distro-sync), but VMware Workstation 9.0.1 clearly is having trouble finding the kernel headers and other associated components with the 3.7 series of the kernel that is in the updates-testing repository. So, what that means is that something with respect to where the header files are placed and located between these two series of kernels has been changed to the point that applications like VMware Workstaion can no longer find them. I would need to go back to the 3.7 series kernel to get the exact error message. I may have it in an old VMware log file, so I'll check that too next chance. In my case, I'm running the 64-bit kernel, so there's no PAE stuff to worry about. I know that's not all of the information people are asking for, but hopefully it does shed some additional light on the situation... Cheers, Chris -- Christopher A. Williams -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, Jan 12, 2013 at 05:09:41AM -0700, Lawrence Graves wrote: > what the error message says is that it could not find the kernel headers for > kernel 3.7.1-5. I know that they were installed. So where are the kernel > header > file if in fact it was installed. Usually, if VMware can't find kernel-headers, you need the kernel-devel package. The kernel-devel package number has to match the result of uname -r. What I frequently see on the forums is that someone updated, got a newer package of kernel-devel, but hasn't rebooted, so there will be a version mismatch. Also, if running a PAE kernel, one has to specify kernel-PAE-devel. (Which doesn't seem relevant in your case). -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: Isn't that what they called The Slayer? Willow: Buffy, ohh scary. Xander: Someone has to talk to her people. That name is striking fear in nobody's hearts. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, Jan 12, 2013 at 7:16 AM, Frank Murphy wrote: > On Sat, 12 Jan 2013 05:09:41 -0700 > Lawrence Graves wrote: > > > what the error message says is that it could not find the kernel > > headers for kernel 3.7.1-5. I know that they were installed. So > > where are the kernel header file if in fact it was installed. > > This is where the headers should go: 32bit > http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612780 > > 64 bit: > http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612758 > > if you have those files, > then the kernel is most likely not your problem. I've not tried with the latest f18 kernel, but I think the kernel-devel rpm package is required to compile third party kernel modules with shims and whatnot. http://forums.fedoraforum.org/showthread.php?t=149704 Maybe you need to install the correct kernel-devel rpm to match the kernel rpm and that will fix the problems? Cheers, -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 12 Jan 2013 05:09:41 -0700 Lawrence Graves wrote: > what the error message says is that it could not find the kernel > headers for kernel 3.7.1-5. I know that they were installed. So > where are the kernel header file if in fact it was installed. This is where the headers should go: 32bit http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612780 64 bit: http://koji.fedoraproject.org/koji/rpminfo?rpmID=3612758 if you have those files, then the kernel is most likely not your problem. -- Regards, Frank "Still trying to learn, both old and new tricks" --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 12 Jan 2013 05:09:41 -0700 Lawrence Graves wrote: > what the error message says is that it could not find the kernel > headers for kernel 3.7.1-5. I know that they were installed. So > where are the kernel header file if in fact it was installed. Can you not copy the whole error? camera? Oherwise it's a game of charades. Can you keep the reples in the current thread please, your coming in as new threads. -- Regards, Frank "Still trying to learn, both old and new tricks" --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
kernel headers
what the error message says is that it could not find the kernel headers for kernel 3.7.1-5. I know that they were installed. So where are the kernel header file if in fact it was installed. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers
On Sat, 12 Jan 2013 04:57:49 -0700 Lawrence Graves wrote: > Everyone is blaming the inability of vmware workstation to compile > on vmware/ nvidia people, when theerror message received says it > can't find where the C file is located to compile. What c file? can you c&p the error to fpaste.com? -- Regards, Frank "Still trying to learn, both old and new tricks" --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
kernel headers
Everyone is blaming the inability of vmware workstation to compile on vmware/ nvidia people, when theerror message received says it can't find where the C file is located to compile. That seems to be a kernel error not a vmware or nvidia error. Please look into this minor problem. -- All things are workable but don't all things work. Prov. 3:5 & 6 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers mismatch (F15)
On Sun, 2011-05-15 at 21:53 +0800, Frederic Muller wrote: > Hi! > > On that newly re-installed system from RC3 without testing repository > enabled I am running kernel 2.6.38.6-26.rc1.fc15.i686.PAE but the > headers I get are 'only' 2.6.38.5-24.fc15.i686 . > > Trying to install the source rpm gives me that: > yum install kernel-headers-$(uname -r).src.rpm > Loaded plugins: langpacks, presto, refresh-packagekit > Setting up Install Process > No package kernel-headers-2.6.38.6-26.rc1.fc15.i686.PAE.src.rpm available > > What am I doing wrong? Nothing, the updated kernel hasn't hit your mirror yet. It was only pushed stable yesterday. Try again today, or get it from Koji - http://koji.fedoraproject.org/koji/search?terms=kernel-2.6.38.6-26.rc1.fc15&type=build&match=glob . -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers mismatch (F15) [solved]
On Mon, May 16, 2011 at 00:00:25 +0800, Frederic Muller wrote: > > Someone replied off the list: packages are on the RC3 DVD. They are also currently available from the F15 branch repo, but not all mirrors may have the kernel update yet. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: kernel headers mismatch (F15) [solved]
On 05/15/2011 09:53 PM, Frederic Muller wrote: > Hi! > > On that newly re-installed system from RC3 without testing repository > enabled I am running kernel 2.6.38.6-26.rc1.fc15.i686.PAE but the > headers I get are 'only' 2.6.38.5-24.fc15.i686 . > > Trying to install the source rpm gives me that: > yum install kernel-headers-$(uname -r).src.rpm > Loaded plugins: langpacks, presto, refresh-packagekit > Setting up Install Process > No package kernel-headers-2.6.38.6-26.rc1.fc15.i686.PAE.src.rpm available > > What am I doing wrong? > > Thanks. > > Fred Someone replied off the list: packages are on the RC3 DVD. Thank you. Fred -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
kernel headers mismatch (F15)
Hi! On that newly re-installed system from RC3 without testing repository enabled I am running kernel 2.6.38.6-26.rc1.fc15.i686.PAE but the headers I get are 'only' 2.6.38.5-24.fc15.i686 . Trying to install the source rpm gives me that: yum install kernel-headers-$(uname -r).src.rpm Loaded plugins: langpacks, presto, refresh-packagekit Setting up Install Process No package kernel-headers-2.6.38.6-26.rc1.fc15.i686.PAE.src.rpm available What am I doing wrong? Thanks. Fred -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
