You are not logged in.
Pages: 1
Am I permitted to revise the wiki for custom kernel generation?
If so, how is that done, procedurally? Don't want to upset anyone.
The changes are substantial including example file. Much more detailed.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Just do it!
If you are polite, you may register yourself to the wiki. Then, your changes are signed with your name. As anyone can undo your changes at any time, everyone can add his best ideas and correct errors, the best solution will be the result of the work. This is the wiki concept!
If any person would feel offended by changes of his original wiki text, a wiki was a wrong place for this person to post ideas.
Frumpus ♥ addict
[mu'.krum.pus], [frum.pus]
Offline
Pink Chick;
I have trouble with general statements and no specifics. I guess its me.
Your reference to " register yourself to the wiki" is not a "how to" which is the object of this post.
How to register and get this done?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Can't get into sandbox to test my procedure!!!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
first, go here:
at the bottom of the page is a box that says Sign in:
Enter a name into that box. The name has to be a wikiword, meaning it has to have some mixed caps. I've chosen SawDusty (Sawdusty wouldn't work because it doesn't have mixed caps in the middle of the word). You don't have to do this to edit pages though, all this does is list your name beside any edits you make instead of your IP address.
Then go to the page you want to edit:
http://wiki.archlinux.org/index.php/Ker … ompilation
At the bottom of the page is a Edit button. Click that. You'll get a box where you enter wiki formatting into. You can preview changes you make, so don't worry about screwing up. Also, if a change doesn't seem to work the way you want it, just save the change and somebody else (much likely me :-D) will drop by and try to figure out what's missing.
There are small instructions for wiki content at the bottom of the page. You can also view these pages for advice:
http://wiki.archlinux.org/index.php/GoodStyle
http://wiki.archlinux.org/index.php/TextFormattingRules
http://wiki.archlinux.org/index.php/Arch%20Linux%20Wiki
http://wiki.archlinux.org/index.php/Wiki%20Template
Ironically, you can edit most of those pages too.
Wiki syntax is tricky at first, but its actually quite intelligent after you get into it.
Good luck!
Dusty
Offline
I have the following on my desktop and in a wiki EDIT page but don't know how to enter it into the wiki.
I expect that I can paste it into the wiki if I know where to put it. See it here:::----------------------------------------------------------------------------------
*OVERVIEW*
------------------------------------------------------------------------------------
Command _ABS_ initiates a download into _/var/abs/kernels_ of all up-to-date data (CONFIG and PKGBUILD for example) for all kernels in arch archives (not the full kernels, just the data)
From the above location, the desired kernel data is derived by opening that directory and copying the _CONFIG_ and _PKGBUILD_ files to the _ /var/abs/local_
directory to permit customizing.
The two files are edited to your requirem,ents to prepare them for _makepkg_,(_and they are saved_).
_makepkg PKGBUILD_ generates the new kernel _.pkg.tar.gz_. (This may entail a download of the kernel _.tar.bz2_ if it is not resident in your computer).
_Pacman -A kernel-x.x.x.pkg.tar.gz_ installs the new custom kernel.
_LILO_ or _GRUB_ are then configured. (If _*LILO_*, then _*/SBIN/LILO -v_* to verify correct install and kernel ID).
Reboot and select the new kernel ID at boot prompt.
-------------------------------------------------------------------------------------
Step by step procedure:
1. As root, _abs_ enter. (Download of data from arch archives)
2. _cd /var/abs/kernels_
3. Open desired kernel and _cp CONFIG and PKGBUILD_ files to _/var/abs/local_ directory.
4. _cd /var/abs/local_.
5. Open _CONFIG_ file and edit to your needs. _*SAVE AS CONFIG OVERWRITE_*.
6. Open _PKGBUILD_ file and edit it as follows;
a. Comment out _MD5_ entry
b. Enter at Pkgname...._pkgname=kernel-$pkgver-custom_ ..
Note 1: -custom can be your name selection...
c. Enter at pkgver...pkgver=_X.X.X_ ...(the kernel version numbers)
Note 2: If _conflicts= _ is in the entries set the entry as
follows: _conflicts= ( )_
7. Edit the _build ( ){ section as follows;
entry _yes""|make config_
Note3: If system is X based...change to... just _make xconfig_
Note4: If system is console based...change to..just _make
menuconfig_
8. _*SAVE AS_* PKGBUILD and _*OVERWRITE_*
9. Run _makepkg PKGBUILD_. (A long process with one break _Xqconf<2>_ which you can skip.
10. When makepkg completes, open the /var/abs/local/pkg directory and obtain the ID of the new kernel.tar.gz which is needed verbatim in next step.
11. Run_pacman -A kernel-x.x.x-custom.pkg.tar.gz_
Note5: Use the ID from step 10, verbatim!
12. Its break time while the kernel is installed.
13. At completion of install, open/var/abs/local/pkg/boot and derive the ID of the vmlinuz file. If its ID conflicts with your systems present ID's, rename the vmlinuz file, to say _vmlinuz26a_. (This file must reside in root/boot if you run things from there, so it must be copied to the /boot file that your system uses, possibly in some usr file.
14. _cd_ to root. Edit _*LILO.CONF_* or _*GRUB_* to your new kernel requirements.
Note6: If _*LILO_*, after config and _SAVE_, _cd enter_ , then
run_*/sbin/lilo -v_* to verify the kernel ID entered and
no errors)
15. Reboot and at boot prompt, select your new kernel ID.
--------------------------------------------------------------------------------------
The following is a sample PKGBUILD ready for makepkg which shows the affected entries;
# $Id: PKGBUILD,v 1.14 2004/04/05 08:06:47 judd Exp $
# Maintainer: judd <jvinet@zeroflux.org>
pkgname=kernel-$pkgver-ramfs
pkgver=2.6.5
pkgrel=2
pkgdesc="The Linux Kernel and modules (IDE support)"
url="http://www.kernel.org"
backup=('boot/kconfig26')
depends=('module-init-tools')
install=kernel26.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2
config)
build() {
cd $startdir/src/linux-$pkgver
# get rid of the 'i' in i686
carch=`echo $CARCH | sed 's|i||'`
cat ../config | sed "s|#CARCH#|$carch|g" >./.config
make xconfig
make clean bzImage modules || return 1
mkdir -p $startdir/pkg/{lib/modules,boot}
make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1
cp System.map $startdir/pkg/boot/System.map26
cp arch/i386/boot/bzImage $startdir/pkg/boot/vmlinuz26
install -D -m644 Makefile $startdir/pkg/usr/src/linux-$pkgver/Makefile
install -D -m644 .config $startdir/pkg/usr/src/linux-$pkgver/.config
install -D -m644 .config $startdir/pkg/boot/kconfig26
mkdir -p $startdir/pkg/usr/src/linux-$pkgver/include
mkdir -p $startdir/pkg/usr/src/linux-$pkgver/arch/i386/kernel
for i in asm-generic asm-i386 config linux math-emu net pcmcia scsi video; do
cp -a include/$i $startdir/pkg/usr/src/linux-$pkgver/include/
done
# copy files necessary for later builds, like nvidia and vmware
cp -a scripts $startdir/pkg/usr/src/linux-$pkgver/
cp arch/i386/Makefile $startdir/pkg/usr/src/linux-$pkgver/arch/i386/
cp arch/i386/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-$pkgver/arch/i386/kernel/
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-$pkgver/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-$pkgver/$i
done
cd $startdir/pkg/usr/src/linux-$pkgver/include && ln -s asm-i386 asm
chown -R root.root $startdir/pkg/usr/src/linux-$pkgver
cd $startdir/pkg/lib/modules/$pkgver &&
(rm -f build; ln -sf /usr/src/linux-$pkgver build)
}
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
first, go here...
That's a good overview Dusty. However, I've been looking to add a new page, and not edit one already listed. I can't seem to figure it out, and I don't want to trash up the Wiki.
I want to add a Wiki in the "Hints..." section. I sign in, but how do I start a new document not related to the ones already listed?
thanks.
Offline
Explains it all:
http://wiki.archlinux.org/index.php/HowToUseWiki
http://wiki.archlinux.org/index.php/AddingPages
-wd
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?
Offline
Entered an addendum section to the wiki but the end result differs from the data entered in the PKGBUILD file area.
I am wondering how I should correct that to make it look like the PKGBUILD file that was entered in the EDIT area. The present format is ugly!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
I fixed the problem and invite others to inspect and improve as you will the addendum to the wiki for custom kernels ID is CUSTOM KERNEL WITH ABS (For noobies, too).
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
I'm going to be recmopiling me kernel next week. I'll give your steps a try to see how it works. Thanks for all the effort.
Dusty
Offline
Dusty;
Good luck with it and thanks!
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Yep. Had already been there, done that, and got the t-shirt.
The "adding new page" doc is simple, yet vague, as far as actually outlining steps, such as an actual Wiki would. For someone like myself who has never used a web Wiki, it would be nice. It would alleviate some fears about cluttering present pages with "trial and error" sessions from "first time" Wiki users. That's what I was really asking for.
Outside of that, assuming the Wiki is fairly protected and monitored, I'll give it a cautious shot, to the best of my understanding from the docs I've read.
Offline
I added the following as an addendum to the wiki kernel compilation to help with building custom kernels and found it might be helpful for "experts trying a new procedure for the first time". I hope it helps someone to build a custom kernel:----------------------------------------------------------------------------------
*OVERVIEW*
------------------------------------------------------------------------------------
Command _ABS_ initiates a download into _/var/abs/kernels_ of all up-to-date data (CONFIG and PKGBUILD for example) for all kernels in arch archives (not the full kernels, just the data)
From the above location, the desired kernel data is derived by opening that directory and copying the _CONFIG_ and _PKGBUILD_ files to the _ /var/abs/local_
directory to permit customizing.
The two files are edited to your requirem,ents to prepare them for _makepkg_,(_and they are saved_).
_makepkg PKGBUILD_ generates the new kernel _.pkg.tar.gz_. (This may entail a download of the kernel _.tar.bz2_ if it is not resident in your computer).
_Pacman -A kernel-x.x.x.pkg.tar.gz_ installs the new custom kernel.
_LILO_ or _GRUB_ are then configured. (If _*LILO_*, then _*/SBIN/LILO -v_* to verify correct install and kernel ID).
Reboot and select the new kernel ID at boot prompt.
-------------------------------------------------------------------------------------
Step by step procedure:
1. As root, _abs_ enter. (Download of data from arch archives)
2. _cd /var/abs/kernels_
3. Open desired kernel and _cp CONFIG and PKGBUILD_ files to _/var/abs/local_ directory.
4. _cd /var/abs/local_.
5. Open _CONFIG_ file and edit to your needs. _*SAVE AS CONFIG OVERWRITE_*.
6. Open _PKGBUILD_ file and edit it as follows;
a. Comment out _MD5_ entry
b. Enter at Pkgname...._pkgname=kernel-$pkgver-custom_ ..
Note 1: -custom can be your name selection...
c. Enter at pkgver...pkgver=_X.X.X_ ...(the kernel version numbers)
Note 2: If _conflicts= _ is in the entries set the entry as
follows: _conflicts= ( )_
7. Edit the _build _( ){ section as follows;
entry _yes""|make config_
Note3: If system is X based...change to... just _make xconfig_
Note4: If system is console based...change to..just....
_makemenuconfig_
8. _*SAVE AS_* PKGBUILD and _*OVERWRITE_*
9. Run _makepkg PKGBUILD_. (A long process with one break _Xqconf<2>_ which you can skip.
10. When makepkg completes, open the /var/abs/local/pkg directory and obtain the ID of the new kernel.tar.gz which is needed verbatim in next step.
11. Run_pacman -A kernel-x.x.x-custom.pkg.tar.gz_
Note5: Use the ID from step 10, verbatim!
12. Its break time while the kernel is installed.
13. At completion of install, open/var/abs/local/pkg/boot and derive the ID of the vmlinuz file. If its ID conflicts with your systems present ID's, rename the vmlinuz file, to perhaps: _vmlinuz26a_. (This file must reside in root/boot if you run things from there, or it must be copied to the /boot file that your system uses, possibly in some usr file.
14. _cd_ to root. Edit _*LILO.CONF_* or _*GRUB_* to your new kernel requirements.
Note6: If _*LILO_*, after config and _SAVE_, _cd enter_ , then
run_*/sbin/lilo -v_* to verify the kernel ID entered and
no errors) _IMPORTANT_
15. Reboot and at boot prompt, select your new kernel ID.
--------------------------------------------------------------------------------------
The following is a sample PKGBUILD ready for makepkg which shows the affected entries;
# $Id: PKGBUILD,v 1.14 2004/04/05 08:06:47 judd Exp $
# Maintainer: judd <jvinet@zeroflux.org>
pkgname=kernel-$pkgver-ramfs ...._CHANGE HERE_
pkgver=2.6.5 ...._CHANGE HERE
pkgrel=2
pkgdesc="The Linux Kernel and modules (IDE support)"
url="http://www.kernel.org"
backup=('boot/kconfig26')
depends=('module-init-tools')
install=kernel26.install
source=(ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-$pkgver.tar.bz2
config)
build() {
cd $startdir/src/linux-$pkgver
# get rid of the 'i' in i686
carch=`echo $CARCH | sed 's|i||'`
cat ../config | sed "s|#CARCH#|$carch|g" >./.config
make xconfig ...._CHANGE HERE_
make clean bzImage modules || return 1
mkdir -p $startdir/pkg/{lib/modules,boot}
make INSTALL_MOD_PATH=$startdir/pkg modules_install || return 1
cp System.map $startdir/pkg/boot/System.map26
cp arch/i386/boot/bzImage $startdir/pkg/boot/vmlinuz26
install -D -m644 Makefile $startdir/pkg/usr/src/linux-$pkgver/Makefile
install -D -m644 .config $startdir/pkg/usr/src/linux-$pkgver/.config
install -D -m644 .config $startdir/pkg/boot/kconfig26
mkdir -p $startdir/pkg/usr/src/linux-$pkgver/include
mkdir -p $startdir/pkg/usr/src/linux-$pkgver/arch/i386/kernel
for i in asm-generic asm-i386 config linux math-emu net pcmcia scsi video; do
cp -a include/$i $startdir/pkg/usr/src/linux-$pkgver/include/
done
# copy files necessary for later builds, like nvidia and vmware
cp -a scripts $startdir/pkg/usr/src/linux-$pkgver/
cp arch/i386/Makefile $startdir/pkg/usr/src/linux-$pkgver/arch/i386/
cp arch/i386/kernel/asm-offsets.s $startdir/pkg/usr/src/linux-$pkgver/arch/i386/kernel/
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-$pkgver/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-$pkgver/$i
done
cd $startdir/pkg/usr/src/linux-$pkgver/include && ln -s asm-i386 asm
chown -R root.root $startdir/pkg/usr/src/linux-$pkgver
cd $startdir/pkg/lib/modules/$pkgver &&
(rm -f build; ln -sf /usr/src/linux-$pkgver build)
}
--------------------------------------------------------------------------------------------------------
When is a zero always equal to a one?
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Pages: 1