I just wanna say thanks for you guys hard work This is really starting to work with Windoze functionality without the security issues and the horrible coding which requires literally hundreds of hotfixes http://thehotfixshare.net/board/index.php?s=e697ef6d106102eed4f3527fb3689c5e...
I had a previous question about the kernel build, but I solved that by modifying the spec file to point to my kernel config. I have built and am using the 2.6.23-0.170 kernel.
The main problem is that the kernel source tree used an i386 subdirectory to group architectural specific files. Building a kernel with those files (and booting it) produces essentially an i386 kernel. At that point kmods can't be built because i386 it not an option Probably yall know this already...
[gjohnson@localhost ~]$ rpmbuild --rebuild madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm Installing madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 [gjohnson@localhost ~]$ rpmbuild --rebuild nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm Installing nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 [gjohnson@localhost ~]$ uname -a Linux localhost.localdomain 2.6.23-0.170.rc5.git1.GAJ3 #1 SMP Tue Sep 11 02:02:51 EDT 2007 i686 i686 i386 GNU/Linux [gjohnson@localhost ~]$
Thanks alot , Rawhide works better then XP IMHO
On 09/11/2007 10:08 AM, gjohnson5 wrote:
I just wanna say thanks for you guys hard work This is really starting to work with Windoze functionality without the security issues and the horrible coding which requires literally hundreds of hotfixes http://thehotfixshare.net/board/index.php?s=e697ef6d106102eed4f3527fb3689c5e...
I had a previous question about the kernel build, but I solved that by modifying the spec file to point to my kernel config. I have built and am using the 2.6.23-0.170 kernel.
The main problem is that the kernel source tree used an i386 subdirectory to group architectural specific files. Building a kernel with those files (and booting it) produces essentially an i386 kernel. At that point kmods can't be built because i386 it not an option Probably yall know this already...
Thanks for replying That's my next question in terms of development (not the docs) The rawhide kernels use a script merge.pl in an attempt to create dynamic configuration files based on architecture. Then the kernel.spec will attempt to guess the correct architecture . next build a kernel with that configuration.
What are plans for that as far as like adding /proc/config.gz? or evne parsing dmesg (not sure how helpful that would be)...
But at this point the latest kernel from koji definitely boots and runs on my system [gjohnson@localhost ~]$ uname -a Linux localhost.localdomain 2.6.23-0.171.rc5.git1.BLAH1 #1 SMP Tue Sep 11 13:33:02 EDT 2007 i686 i686 i386 GNU/Linux [gjohnson@localhost ~]$ So the kernel build procedure that you pointed out (with slight alterations) does work for 2.6.23
Thanks
Chuck Ebbert-2 wrote:
On 09/11/2007 10:08 AM, gjohnson5 wrote: .............. See http://fedoraproject.org/wiki/Docs/CustomKernel
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
Thanks for replying That's my next question in terms of development (not the docs) The rawhide kernels use a script merge.pl in an attempt to create dynamic configuration files based on architecture. Then the kernel.spec will attempt to guess the correct architecture . next build a kernel with that configuration.
Really? I thought
--target=`uname`
did that. If you want to specify a particular arch then follow the guide Chuck pasted in and use --target=i686 or whatever.
Cheers Chris
On Tue, 11 Sep 2007, Christopher Brown wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
Thanks for replying That's my next question in terms of development (not the docs) The rawhide kernels use a script merge.pl in an attempt to create dynamic configuration files based on architecture. Then the kernel.spec will attempt to guess the correct architecture . next build a kernel with that configuration.
Really? I thought
--target=`uname`
did that. If you want to specify a particular arch then follow the guide Chuck pasted in and use --target=i686 or whatever.
you might be thinking of `uname -m`.
rday
On 11/09/2007, Robert P. J. Day rpjday@mindspring.com wrote:
On Tue, 11 Sep 2007, Christopher Brown wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
Thanks for replying That's my next question in terms of development (not the docs) The rawhide kernels use a script merge.pl in an attempt to create
dynamic
configuration files based on architecture. Then the kernel.spec will attempt to guess the correct architecture . next build a kernel with that configuration.
Really? I thought
--target=`uname`
did that. If you want to specify a particular arch then follow the guide Chuck pasted in and use --target=i686 or whatever.
you might be thinking of `uname -m`.
Umm, yeah thats what I said. Build for current arch with that or specify a different one (ie. not the host arch) with --target=ppc64 or whatever. Not completely understanding the question doesn't help though... :p
Chris
And I wish I had full understanding of where this is going. With the new kernels follow the document for building a custom kernel
1. su -c 'yum-builddep kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm' 2. rpm -Uvh kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm 3. rpmbuild -bp --target=i686 (or `uname -m`) kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm go to source tree 4. cd /home/gjohnson/rpmbuild/BUILD/kernel-2.6.22/linux-2.6.22.i686/configs 5. head the config file [gjohnson@localhost configs]$ head kernel-2.6.23-i686-PAE.config # i386 <------------------ (Here's the issue) # # Automatically generated make config: don't edit # Linux kernel version: 2.6.23-rc5-git1 # Tue Sep 11 13:31:28 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_CLOCKSOURCE_WATCHDOG=y [gjohnson@localhost configs]$
So even though you are building with an i686 target the kernel seems to think it's still an i386 kernel. Not sure how to ask the question because I don't know what's going on
Christopher Brown-10 wrote:
On 11/09/2007, Robert P. J. Day rpjday@mindspring.com wrote:
On Tue, 11 Sep 2007, Christopher Brown wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
Thanks for replying That's my next question in terms of development (not the docs) The rawhide kernels use a script merge.pl in an attempt to create
dynamic
configuration files based on architecture. Then the kernel.spec will attempt to guess the correct architecture . next build a kernel with that configuration.
Really? I thought
--target=`uname`
did that. If you want to specify a particular arch then follow the
guide
Chuck pasted in and use --target=i686 or whatever.
you might be thinking of `uname -m`.
Umm, yeah thats what I said. Build for current arch with that or specify a different one (ie. not the host arch) with --target=ppc64 or whatever. Not completely understanding the question doesn't help though... :p
Chris
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
And I wish I had full understanding of where this is going. With the new kernels follow the document for building a custom kernel
- su -c 'yum-builddep kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm'
- rpm -Uvh kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm
- rpmbuild -bp --target=i686 (or `uname -m`)
kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm go to source tree 4. cd /home/gjohnson/rpmbuild/BUILD/kernel-2.6.22/linux-2.6.22.i686 /configs 5. head the config file [gjohnson@localhost configs]$ head kernel-2.6.23-i686-PAE.config # i386 <------------------ (Here's the issue)
Why is that an issue? That is the optimization flag for gcc. Is your build failing for some reason?
Chris
The kernel builds succeed. Adding kmods to this kernel fail due to arch mismatch
[gjohnson@localhost ~]$ rpmbuild --rebuild madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm Installing madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 <--------------------------- arch mismatch [gjohnson@localhost ~]$ rpmbuild --rebuild nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm Installing nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 <------------------------- arch mismatch
I'll have to see if I can find ones that work. But I think one problem is that these are expecting an i686 kernel. So things are changing (not sure what) but things a are definitely in a state of flux [gjohnson@localhost ~]$ uname -a Linux localhost.localdomain 2.6.23-0.170.rc5.git1.GAJ3 #1 SMP Tue Sep 11 02:02:51 EDT 2007 i686 i686 i386 GNU/Linux [gjohnson@localhost ~]$
Christopher Brown-10 wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
And I wish I had full understanding of where this is going. With the new kernels follow the document for building a custom kernel
- su -c 'yum-builddep kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm'
- rpm -Uvh kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm
- rpmbuild -bp --target=i686 (or `uname -m`)
kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm go to source tree 4. cd /home/gjohnson/rpmbuild/BUILD/kernel-2.6.22/linux-2.6.22.i686 /configs 5. head the config file [gjohnson@localhost configs]$ head kernel-2.6.23-i686-PAE.config # i386 <------------------ (Here's the issue)
Why is that an issue? That is the optimization flag for gcc. Is your build failing for some reason?
Chris
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
The kernel builds succeed. Adding kmods to this kernel fail due to arch mismatch
[gjohnson@localhost ~]$ rpmbuild --rebuild madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm Installing madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 <--------------------------- arch mismatch [gjohnson@localhost ~]$ rpmbuild --rebuild nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm Installing nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 <------------------------- arch mismatch
I'll have to see if I can find ones that work. But I think one problem is that these are expecting an i686 kernel. So things are changing (not sure what) but things a are definitely in a state of flux [gjohnson@localhost ~]$ uname -a Linux localhost.localdomain 2.6.23-0.170.rc5.git1.GAJ3 #1 SMP Tue Sep 11 02:02:51 EDT 2007 i686 i686 i386 GNU/Linux [gjohnson@localhost ~]$
Christopher Brown-10 wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
And I wish I had full understanding of where this is going. With the new kernels follow the document for building a custom kernel
- su -c 'yum-builddep kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm'
- rpm -Uvh kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm
- rpmbuild -bp --target=i686 (or `uname -m`)
kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm go to source tree 4. cd /home/gjohnson/rpmbuild/BUILD/kernel-2.6.22/linux-2.6.22.i686 /configs 5. head the config file [gjohnson@localhost configs]$ head kernel-2.6.23-i686-PAE.config # i386 <------------------ (Here's the issue)
Why is that an issue? That is the optimization flag for gcc. Is your build failing for some reason?
Chris
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
--
I have a related wierd problem
I have a kernel source 2.6.23-2 (src RPM) updated to 2.6.22.5 (fine)
However when I patch to 2.6.23.rc5 from ftp.kernel.org I get when I try to make config variations of
scripts/kconfig/gconf arch/i386/Kconfig init/Kconfig:695: unexpected end statement drivers/misc/Kconfig:211: unexpected 'endmenu' within if block drivers/Kconfig:94: 'endmenu' in different file than 'menu' drivers/misc/Kconfig:16: location of the 'menu' make[1]: *** [gconfig] Error 1 make: *** [gconfig] Error 2
never came across this before
On 09/11/2007 07:14 PM, Mike Martin wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
The kernel builds succeed. Adding kmods to this kernel fail due to arch mismatch
[gjohnson@localhost ~]$ rpmbuild --rebuild madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm Installing madwifi-kmod-0.9.3.1-2.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 <--------------------------- arch mismatch [gjohnson@localhost ~]$ rpmbuild --rebuild nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm Installing nvidia-kmod-100.14.11-1.2.6.22.4_65.fc7.src.rpm warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: Architecture is not included: i386 <------------------------- arch mismatch
I'll have to see if I can find ones that work. But I think one problem is that these are expecting an i686 kernel. So things are changing (not sure what) but things a are definitely in a state of flux [gjohnson@localhost ~]$ uname -a Linux localhost.localdomain 2.6.23-0.170.rc5.git1.GAJ3 #1 SMP Tue Sep 11 02:02:51 EDT 2007 i686 i686 i386 GNU/Linux [gjohnson@localhost ~]$
Christopher Brown-10 wrote:
On 11/09/2007, gjohnson5 tonyjohn5@yahoo.com wrote:
And I wish I had full understanding of where this is going. With the new kernels follow the document for building a custom kernel
- su -c 'yum-builddep kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm'
- rpm -Uvh kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm
- rpmbuild -bp --target=i686 (or `uname -m`)
kernel-2.6.23-0.171.rc5.git1.fc8.src.rpm go to source tree 4. cd /home/gjohnson/rpmbuild/BUILD/kernel-2.6.22/linux-2.6.22.i686 /configs 5. head the config file [gjohnson@localhost configs]$ head kernel-2.6.23-i686-PAE.config # i386 <------------------ (Here's the issue)
Why is that an issue? That is the optimization flag for gcc. Is your build failing for some reason?
Chris
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
--
I have a related wierd problem
I have a kernel source 2.6.23-2 (src RPM) updated to 2.6.22.5 (fine)
However when I patch to 2.6.23.rc5 from ftp.kernel.org I get when I try to make config variations of
scripts/kconfig/gconf arch/i386/Kconfig init/Kconfig:695: unexpected end statement drivers/misc/Kconfig:211: unexpected 'endmenu' within if block drivers/Kconfig:94: 'endmenu' in different file than 'menu' drivers/misc/Kconfig:16: location of the 'menu' make[1]: *** [gconfig] Error 1 make: *** [gconfig] Error 2
never came across this before
The 2.6.23-rc5 patch is against 2.6.22, not 2.6.22.5.
On Tue, 2007-09-11 at 10:53 -0400, Chuck Ebbert wrote:
Ew, no. Just check it out from CVS and run 'make ppc' or whatever.