hallo
attention: for those who got a double linux maschine (e.g. FC5, FC6xy or FC6-devel) and manually changing the boot entries in grub.conf by hand, the extensions has changed (for now ?)
...2328.fc6.... ^^^ (!!!)
hopefully yours will boot, i had no luck (see 2cd attachement to BZ 196871 )
so long
ronald
On Thu, 2006-06-29 at 15:51 +0200, Ronald Warsow wrote:
hallo
attention: for those who got a double linux maschine (e.g. FC5, FC6xy or FC6-devel) and manually changing the boot entries in grub.conf by hand, the extensions has changed (for now ?)
...2328.fc6.... ^^^ (!!!)
The kernel spec has switched over to use the same %dist tag as Extras.
hopefully yours will boot, i had no luck (see 2cd attachement to BZ 196871 )
There are some known issues with that kernel and a few before it that are actively being worked on.
----- Original Message ----- From: "Jarod Wilson" jwilson@redhat.com To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Thursday, June 29, 2006 11:32 AM Subject: RE: rawhide report: 20060629 changes (kernel-2.6.17-1.2328.fc6doesn't boot) On Thu, 2006-06-29 at 15:51 +0200, Ronald Warsow wrote:
hallo
attention: for those who got a double linux maschine (e.g. FC5, FC6xy or FC6-devel) and manually changing the boot entries in grub.conf by hand, the extensions has changed (for now ?)
...2328.fc6.... ^^^ (!!!)
The kernel spec has switched over to use the same %dist tag as Extras.
hopefully yours will boot, i had no luck (see 2cd attachement to BZ 196871 )
There are some known issues with that kernel and a few before it that are actively being worked on.
-- Jarod Wilson jwilson@redhat.com
Well switching over to the "new spec file" causes all the 3rd party module build scripts to fail. The say "kernel configuration not valid - run 'make prepare' in /usr/src/kernels/2.6.17-1.2328.fc6-x86_64 to update it." Are you going back to the old way or are going to have to fix all the builds? I vote for the old way! Using "_FC6" is fine with me. There errors so far are for mvidia, vmware, ntfs, and spca5xx modules.
Jim
On Thursday 29 June 2006 15:50, Jim Bevier wrote:
Well switching over to the "new spec file" causes all the 3rd party module build scripts to fail. The say "kernel configuration not valid - run 'make prepare' in /usr/src/kernels/2.6.17-1.2328.fc6-x86_64 to update it." Are you going back to the old way or are going to have to fix all the builds? I vote for the old way! Using "_FC6" is fine with me. There errors so far are for mvidia, vmware, ntfs, and spca5xx modules.
What are they checking to figure this out?
On 6/29/06, Jesse Keating jkeating@redhat.com wrote:
On Thursday 29 June 2006 15:50, Jim Bevier wrote:
Well switching over to the "new spec file" causes all the 3rd party module build scripts to fail. The say "kernel configuration not valid - run 'make prepare' in /usr/src/kernels/2.6.17-1.2328.fc6-x86_64 to update it." Are you going back to the old way or are going to have to fix all the builds? I vote for the old way! Using "_FC6" is fine with me. There errors so far are for mvidia, vmware, ntfs, and spca5xx modules.
What are they checking to figure this out?
-- Jesse Keating Release Engineer: Fedora
Could this be coming from source/Makefile: # If .config is newer than include/config/auto.conf, someone tinkered # with it and forgot to run make oldconfig. # if auto.conf.cmd is missing then we are probably in a cleaned tree so # we execute the config step to be sure to catch updated Kconfig files include/config/auto.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd ifeq ($(KBUILD_EXTMOD),) $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig else $(error kernel configuration not valid - run 'make prepare' in $(srctree) to update it) endif
tom
----- Original Message ----- From: "Tom London" selinux@gmail.com To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Thursday, June 29, 2006 2:09 PM Subject: Re: rawhide report: 20060629 changes(kernel-2.6.17-1.2328.fc6doesn't boot)
On 6/29/06, Jesse Keating jkeating@redhat.com wrote:
On Thursday 29 June 2006 15:50, Jim Bevier wrote:
Well switching over to the "new spec file" causes all the 3rd party module build scripts to fail. The say "kernel configuration not valid - run 'make prepare' in /usr/src/kernels/2.6.17-1.2328.fc6-x86_64 to update it." Are you going back to the old way or are going to have to fix all the builds? I vote for the old way! Using "_FC6" is fine with me. There errors so far are for mvidia, vmware, ntfs, and spca5xx modules.
What are they checking to figure this out?
-- Jesse Keating Release Engineer: Fedora
Could this be coming from source/Makefile: # If .config is newer than include/config/auto.conf, someone tinkered # with it and forgot to run make oldconfig. # if auto.conf.cmd is missing then we are probably in a cleaned tree so # we execute the config step to be sure to catch updated Kconfig files include/config/auto.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd ifeq ($(KBUILD_EXTMOD),) $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig else $(error kernel configuration not valid - run 'make prepare' in $(srctree) to update it) endif
tom
Tom London
It looks like this is where the message is coming from. For example, spca5xx executes "make -C /lib/modules/`uname -r`/build SUBDIRS=/root/spca5xx-20060501 CC=cc modules" to build the module. The error is coming from the /usr/src/kernels/2.6.17-1.2328.fc6-x86_64/Makefile. Where do I go from here to fix this? I am not a Makefile wizard :-(.
Jim
On 6/29/06, Jim Bevier jim@jbsys.com wrote:
----- Original Message ----- From: "Tom London" selinux@gmail.com To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Thursday, June 29, 2006 2:09 PM Subject: Re: rawhide report: 20060629 changes(kernel-2.6.17-1.2328.fc6doesn't boot)
On 6/29/06, Jesse Keating jkeating@redhat.com wrote:
On Thursday 29 June 2006 15:50, Jim Bevier wrote:
Well switching over to the "new spec file" causes all the 3rd party module build scripts to fail. The say "kernel configuration not valid - run 'make prepare' in /usr/src/kernels/2.6.17-1.2328.fc6-x86_64 to update it." Are you going back to the old way or are going to have to fix all the builds? I vote for the old way! Using "_FC6" is fine with me. There errors so far are for mvidia, vmware, ntfs, and spca5xx modules.
What are they checking to figure this out?
-- Jesse Keating Release Engineer: Fedora
Could this be coming from source/Makefile: # If .config is newer than include/config/auto.conf, someone tinkered # with it and forgot to run make oldconfig. # if auto.conf.cmd is missing then we are probably in a cleaned tree so # we execute the config step to be sure to catch updated Kconfig files include/config/auto.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd ifeq ($(KBUILD_EXTMOD),) $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig else $(error kernel configuration not valid - run 'make prepare' in $(srctree) to update it) endif
tom
Tom London
It looks like this is where the message is coming from. For example, spca5xx executes "make -C /lib/modules/`uname -r`/build SUBDIRS=/root/spca5xx-20060501 CC=cc modules" to build the module. The error is coming from the /usr/src/kernels/2.6.17-1.2328.fc6-x86_64/Makefile. Where do I go from here to fix this? I am not a Makefile wizard :-(.
Jim
I 'fixed' this by doing the following: cd /usr/src/kernels/2.6.17-1.2328.fc6-i686 make prepare
Worked for me after that (i.e., I could build the vmware modules).
tom
----- Original Message ----- From: "Tom London" selinux@gmail.com To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Thursday, June 29, 2006 5:09 PM Subject: Re: rawhide report: 20060629changes(kernel-2.6.17-1.2328.fc6doesn't boot)
On 6/29/06, Jim Bevier jim@jbsys.com wrote:
----- Original Message ----- From: "Tom London" selinux@gmail.com To: "For testers of Fedora Core development releases" fedora-test-list@redhat.com Sent: Thursday, June 29, 2006 2:09 PM Subject: Re: rawhide report: 20060629 changes(kernel-2.6.17-1.2328.fc6doesn't boot)
On 6/29/06, Jesse Keating jkeating@redhat.com wrote:
On Thursday 29 June 2006 15:50, Jim Bevier wrote:
Well switching over to the "new spec file" causes all the 3rd party module build scripts to fail. The say "kernel configuration not valid - run 'make prepare' in /usr/src/kernels/2.6.17-1.2328.fc6-x86_64 to update it." Are you going back to the old way or are going to have to fix all the builds? I vote for the old way! Using "_FC6" is fine with me. There errors so far are for mvidia, vmware, ntfs, and spca5xx modules.
What are they checking to figure this out?
-- Jesse Keating Release Engineer: Fedora
Could this be coming from source/Makefile: # If .config is newer than include/config/auto.conf, someone tinkered # with it and forgot to run make oldconfig. # if auto.conf.cmd is missing then we are probably in a cleaned tree so # we execute the config step to be sure to catch updated Kconfig files include/config/auto.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd ifeq ($(KBUILD_EXTMOD),) $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig else $(error kernel configuration not valid - run 'make prepare' in $(srctree) to update it) endif
tom
Tom London
It looks like this is where the message is coming from. For example, spca5xx executes "make -C /lib/modules/`uname -r`/build SUBDIRS=/root/spca5xx-20060501 CC=cc modules" to build the module. The error is coming from the /usr/src/kernels/2.6.17-1.2328.fc6-x86_64/Makefile. Where do I go from here to fix this? I am not a Makefile wizard :-(.
Jim
I 'fixed' this by doing the following: cd /usr/src/kernels/2.6.17-1.2328.fc6-i686 make prepare
Worked for me after that (i.e., I could build the vmware modules).
I did: cd /usr/src/kernels/2.6.17-1.2336.fc6-x86_64 make prepare vmware-config.pl and it still fails with the same error!
I could not build vmware or spca5xx modules. Ntfs module build worked. It is a src livna modified build.
Is this error 64bit only? Any more ideas of what to try?
Jim
tom
Tom London
On 6/30/06, Jim Bevier jim@jbsys.com wrote:
I did: cd /usr/src/kernels/2.6.17-1.2336.fc6-x86_64 make prepare vmware-config.pl and it still fails with the same error!
I could not build vmware or spca5xx modules. Ntfs module build worked. It is a src livna modified build.
Is this error 64bit only? Any more ideas of what to try?
Jim
Sorry, no..... Not sure about _64 issues....
tom
-
Jarod Wilson -
Jesse Keating -
Jim Bevier -
Ronald Warsow -
Tom London