You are not logged in.
How does a user edit kernel 2.6.10 with abs?
Abs downloads the latest kernel for pkgbuild.
Desire to change one entry in kernel 2.6.10 kconfig and generate a custom kernel separately bootable from kernel 2.6.10.
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
The config for kernel 2.6.10 can be found in the CVS entires for kernel26 on the web:
http://cvs.archlinux.org/cgi-bin/viewcv … cvs-markup
To make a unique kernel you would be best to use my custom kernel PKGBUILD. There is a detailed guide and you simply use the config mentioned above and make the changes you desire. You will also need to change LOCALVERSION in the config. My PKGBUILD uses this variable to create a unique name for the pkg which allows it to be installed alongside a stock kernel.
Offline
I have the config from kernel 2.6.10 already in /boot, have copied it and changed the desired entry and am prepared to enter it into pkgbuild hopefully without encountering patches or other modifications.
Is this a possibility?
You mention Local Version and the config change necessary. Does that apply to the config I have already prepared?
Is there a different config provided by abs?
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
It will apply for the config you have - if you look LOCALVERSION will be equal to "-ARCH" - you MUST change that before you build your new kernel
Offline
Have downloaded the PKGBUILD for custom kernel per the wiki.
I have edited my config to change:
General Setup:.....CONFIG-LOCALVERSION="-ARCH"....
to:.....CONFIG-LOCAL VERSION="-custom"...
or does it have to be in caps?
Now that PKGBUILD is in /root, I moved it to /var/abs/local.
The procedure calls for patches in PKGBUILD. Are there patches in Kernel 2.6.10 that have to be entered? I wish only to change one entry in kconfig.
What other items have to be changed or edited besides selecting ..make xconfig...?
Will I have a message during the build to permit config changes which I cancel? This then permits the config file I have modified to be entered.
I have the config file and PKGBUILD in the same directory, /var/abs/local. There are no other elements present. What comes next?
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
Uname -r in my system lists the kernel revision as 2.6.10-ARCH.
Is this what I must enter into PKGBUILD? Is this the pkg name or pkg rev?
After the PKGBUILD is readied, how is the process initiated? This is not in the wiki.(WIKI means quick).
After the process is finished, what appears in /var/abs/local for my case.
If using lilo, what identifier is required for the new custom kernel.
Is there to be a new vmlinuz identifier?
Such information would be very useful before starting a custom kernel install.
I assume that pacman has to be used to load the new kernel...no mention of that in the wiki.
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
Entered 2.6.10-3 as the kernel version..
Entered 4 as the pkgrel
Attempted to ......makepkg....
cd /var/abs/local
makepkg -g PKGBUILD.custom_kernel
Received error.... ./PKGBUILD.custom_kernel does not exist
What is wrong?
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
always just makepkg -g that will be enough, you should only ever have one PKGBUILD in there at a time so no need for an option or name to be passed
Offline
shouldn't you be using the redirection operators when specifying the file after -g? ie makepkg -g >>PKGBUILD.custom_kernel
Offline
I tried both suggestions and always receive error....
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
you really should name it PKGBUILD. Its not going to generate the sums for anything but that.
Offline
Performed rename to PKGBUILD...
Received error...pkgver cannot have hyphens
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
Rechecked wiki which disagrees with itself..
It requests entry of 2.6.x.y...This corresponds to 2.6.10-3 in standard nomenclature.
In parens the wiki states (2.6.9) in another statement concerning pkgver!!
Very confusing!
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
Retried makepkg after change to pkgver
Error this time: install scriptlet (kernel26 install) does not exist.
I had no inkling of any scriptlet...large or small? Maybe I need to run it in red type?
I downloaded the PKGBUILD from the custom kernel wiki ...download here...
It came addressed as PKGBUILD.custom_kernel.
I have renamed it and changed the pkgver to eliminate errors but generate errors anyhow.
Frustration rules!!!!!!
I just wanna change one line in the kconfig 2.6.10 kernel!!!! I am advised I can't just change one line..I have to change LOCAL VERSION= "ARCH" also.
Where did sciptlet come from? Guess there is another line to be changed!
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
Listed in ..pacman -Q is the kernel pkg version as 2.6.10-3.
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
The following listing shows scriptlet kernel26.install as present in the pkgbuild listing....
----------------------------------------------------------------------------------
# Contributor: dibblethewrecker <dibblethewrecker.at.jiwe.org>
pkgname=kernel26
pkgver=2.6.10
pkgrel=4
pkgdesc="The Linux Kernel 2.6.x.y and modules (IDE support)"
url="http://www.kernel.org"
depends=('module-init-tools')
install=kernel26.install
##### add any patch sources to this section
source=(config ftp://ftp.kernel.org/pub/linux/kernel/v … er.tar.bz2 )
# Function to grab var from src
getvar() {
old=$(cat Makefile | grep "^$1")
echo $(echo ${old/"$1 ="/} | sed -e "s/[ ]*(.*)[ ]*/1/g")
return 0
}
build() {
cd $startdir/src/linux-$pkgver
##### Uncomment and apply any patches here
#patch -Np1 -i ../patchname || return 1
# get rid of the 'i' in i686
carch=`echo $CARCH | sed 's|i||'`
cat ../config | sed "s|#CARCH#|$carch|g" >./.config
##### Load config - uncomment your preferred config method
#yes "" | make config
#make oldconfig || return 1
#make menuconfig
make xconfig
make gconfig
##### NO USER CHANGES BELOW HERE #####
# save the current pkgname
old_pkgname=$pkgname
# set pkgname for build purposes - DO NOT alter!
pkgname=kernel26
# save the updated config to build with today's date
cp ./.config $startdir/config-$(date +%b%d-%Hh)
# get EXTRAVERSION from Makefile to create a unique pkgname and /usr/src directory
_kernextra=$(getvar "EXTRAVERSION")
# grab the 2.6.x.y version suffix from pkgver
_y="`echo $pkgver | cut --delim "." --fields 4`"
# remove .y version suffix from _kernextra
_kernextra="`echo $_kernextra | sed "s|.$_y||g"`"
# Read the full kernel version info from new config to use in pathnames and pkgname
. ./.config
# Kernel custom - to create a unique pkgname (see below)
_kerncust="${_kernextra}${CONFIG_LOCALVERSION}"
# Kernel release - will be the same as Makefile
_kernrel="${pkgver}${_kerncust}"
# Get the pkgver suffix for unique pkgname and /boot file suffices
_pkgversuf="`echo $pkgver | sed "s|2.6.||g" | sed "s|.||g"`"
# Set /boot file suffices from kernel release and pkgver suffix
_kernboot="${_pkgversuf}${_kerncust}"
# Set a new pkgname from kernel release and pkgver suffix
pkgname="${pkgname}${_pkgversuf}${_kerncust}"
# build!
echo
echo -n "Do you want to make clean (default YES)? (YES/NO): "
read choice
echo
echo -n "Press any key to start make or CTRL+C to quit"
read anykey
if [ "${choice}" = "NO" ] ; then
make bzImage modules || return 1
else
make clean bzImage modules || return 1
fi
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${_kernboot}
cp arch/i386/boot/bzImage $startdir/pkg/boot/vmlinuz26${_kernboot}
install -D -m644 Makefile
$startdir/pkg/usr/src/linux-${_kernrel}/Makefile
install -D -m644 .config
$startdir/pkg/usr/src/linux-${_kernrel}/.config
install -D -m644 .config $startdir/pkg/boot/kconfig26${_kernboot}
mkdir -p $startdir/pkg/usr/src/linux-${_kernrel}/include
mkdir -p $startdir/pkg/usr/src/linux-${_kernrel}/arch/i386/kernel
for i in acpi asm-generic asm-i386 config linux math-emu net pcmcia scsi video; do
cp -a include/$i $startdir/pkg/usr/src/linux-${_kernrel}/include/
done
# copy files necessary for later builds, like nvidia and vmware
cp Module.symvers $startdir/pkg/usr/src/linux-${_kernrel}
cp -a scripts $startdir/pkg/usr/src/linux-${_kernrel}
mkdir -p $startdir/pkg/usr/src/linux-${_kernrel}/.tmp_versions
cp arch/i386/Makefile $startdir/pkg/usr/src/linux-${_kernrel}/arch/i386/
cp arch/i386/kernel/asm-offsets.s
$startdir/pkg/usr/src/linux-${_kernrel}/arch/i386/kernel/
# copy in Kconfig files
for i in `find . -name "Kconfig*"`; do
mkdir -p $startdir/pkg/usr/src/linux-${_kernrel}/`echo $i | sed 's|/Kconfig.*||'`
cp $i $startdir/pkg/usr/src/linux-${_kernrel}/$i
done
cd $startdir/pkg/usr/src/linux-${_kernrel}/include && ln -s asm-i386 asm
chown -R root.root $startdir/pkg/usr/src/linux-${_kernrel}
cd $startdir/pkg/lib/modules/${_kernrel} &&
(rm -f source build; ln -sf /usr/src/linux-${_kernrel} build)
# Correct the pkgname in our PKGBUILD - this allows correct gensync operation
# NOTE: pkgname variable must be declared with first 10 lines of PKGBUILD!
cd $startdir
sed -i "1,11 s|pkgname=$old_pkgname|pkgname=$pkgname|" ./PKGBUILD
}
# vim:syntax=sh
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
In the wiki...Kernel Compilation with ABS.... step 3 states as follows:
-------------------------------------------------------------------
Change the pkgrel for your current revision. You should increment this each time you make changes to the kernel config and want to build a REPLACEMENT pkg. If you don't want to replace the previous build but rather install in parallel you should use LOCALVERSION to create a unique pkg.
This step addresses two different approaches ..REPLACEMENT and LOCAL VERSION. It is not clear whether LOCAL VERSION requires the same change to pkgrel as does REPLACEMENT.
It would seem that any reference to LOCAL VERSION should be addressed much before reaching this entry and not be inserted to confuse the user as to what is to be entered into pkgrel. If it is the same entry, why is it necessary to call attention to the REPLACEMENT versus LOCAL VERSION? If it is not the same entry, what is done in LOCAL VERSION which must therefore be different?
Why is there an entry ....install=kernel26.install..... in the download? Does it belong there? No other wiki in the kernel area lists that entry that I can find.
------------------------------------------------------------------------------------
If one who is very familiar with what he knows to be correct reads a passage which confuses another, he finds no confusion in it!!!!
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
So far, I have downloaded from wiki related PKGBUILD.custom_kernel that would not start in ....makepkg ....because it had to be renamed...not covered in wiki!
The information relating to LOCAL VERSION in step three of the wiki procedure leaves the user with the impression that pkgrel is different than the pkgrel for REPLACEMENT but doesn't clarify what is to be entered in the LOCAL VERSION install of a unique install(therefore not in the pkgrel sequence since it is deemed to be unique).
Next...after entering the pkgrel as 4, and fixing the PKGBUILD rename, the result was an error stating.....install scriptlet (Kernel26.install) does not exist.
This is an item in the PKGBUILD listing and seems from the error that it doesn't belong there. This is not covered in the wiki!!
What will happen next?
Do I delete the offending scriptlet? Put that in the wiki if so!!!!
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
Do I need anything else in the directory holding PKGBUILD and KCONFIG26custom? Is KCONFIG26custom nomenclature allowed?
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
The wiki says to run lilo after. Does this mean to modify lilo.conf first and then run /sbin/lilo? If so, say so.
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
Sorry, no offense but you clearly have not read the wiki OR you lack the necessary basic knowledge to understand the process. All of the information you need is contained in the wiki. All PKGBUILDs have to be named PKGBUILD, this is basic ABS knowledge. The .install script can be found in abs as explained in the usage note on the wiki. KCONFIG26custom is NOT a suitable name - it should simply be named config or it will not be detected by the PKGBUILD - again this is basic ABS knowledge. All kernels use an install script. The use of pkgrel is basic ABS knowledge.
The explanaition of LOCALVERSION (NOT LOCAL VERSION) vs pkgrel is CRYSTAL clear - if you understand the normal usage of pkgrel and have understood the usage of LOCALVERSION then you should understand the reason for emphasizing the difference in results that they produce IN THIS SPECIAL CASE.
OK - I just read a few more of your posts regarding things that are "missed" in the wiki:
this is NOT an ABS howto - to successfully follow this HOWTO a working knowledge of building pkgs with ABS is ESSENTIAL - please read ABS - The Arch Build System, The Arch package making HOW-TO - with guidelines and Patching in ABS
You clearly have not read my wiki page or these documents properly as 99% of all your questions are already answered within them.
Nobody wants to help someone who doesn't appear to make the best use of material available to them, especially someone such has me that has spent significant time simplifying these processes as much as possible already.
Please do the hard working members of this community the courtesy of reading the work they have put in before you spam the forums with previously answered questions.
Offline
Rechecked wiki which disagrees with itself..
It requests entry of 2.6.x.y...This corresponds to 2.6.10-3 in standard nomenclature.
In parens the wiki states (2.6.9) in another statement concerning pkgver!!
Very confusing!
Only if you are not aware of the 2.6.x.y branches that include 2.6.12.3 etc
Offline
dibblethe wrecker;
I have run ABS before at least a dozen times to make custom kernels.
I have no recollection of instructions regarding LOCAL VERSION in previous custom builds.
As I stated, I had modified my kconfig to change one line of code. You replied that would be OK to use in PKGBUILD. This turns out to be incorrect since the LOCAL VERSION entry has to be changed in my kconfig...not specifically called out when I queried you.
The nomenclature PKGBUILD.custom_kernel is the nomenclature your download provided and is incorrect by your own statement.
Trying to establish a background on ABS to have your in-depth knowledge requires reading all of the wikis on the subject but I am interested in using just one of the ABS wiki formats. Following the stated steps has me in a quandry.
If there are more than one ID formats for kernel ID, please include a statement delineating the differences. Is pacman -Q not the pkgvers listing?
I have attempted to sort out the wiki as it now stands and find it confusing to follow. I feel that one should not put all one's eggs in one basket.
As I pointed out earlier, one who is familiar with ABS procedure cannot recognize the confusion others encounter when trying to interpret the statements.
Why is it necessary in pkgrel to confuse things by digressing to mention the unique character of LOCAL VERSION which I interpret to mean a different unique pkgrel. !!!!
I am now asking you whether the entry...install=kernel26install.. is a correct entry in PKGBUILD as downloaded from your wiki reference. The error I encountered says it doesn't recognize it.
I have run ABS for two years at various times, each time I have encountered changes which caused additional steps to make a simple
kernel change.
I asked via aur for the kernel change to enable the config step. I was told it would "bloat" the kernel.
In previous ABS kernel changes, I had more than PKGBUILD and kconfig to place in the working directory so it is more confusing for me.
Perhaps being 80 and a little slow is against the principles of ABS, too.
I can change the kconfig..does it need to be in caps as you show it in your post?
How do I treat the scriptlet error?
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 have decided that I will forego the kernel change in view of my stupidity concerning ABS and will not again approach the forum for help in this regard.
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 have successfully created via ABS (with modifications) a custom kernel kernel2610-custom with associated vmlinuz2610-custom and kconfig2610-custom and installed same into my system. It works fine with the custom change to one entry.
I attempted to utilize ABS as it stands, which means, use the kernel26 elements downloaded via ABS. These included patches, config, PKGBUILD. Installed all elements in /var/abs/local and modified the config including the LOCALVERSION="-custom" entry. Made my CONFIG_CRAMFS=y entry. Entered the pkg vers 2.6.10 and pkgrel 4. Commented out make gconf and enabled make xconfig.
cd /var/abs/local
makepkg PKGBUILD
The result much later was kernel26-2.6.10 was generated. Not a custom package. Deleted the data in /var/abs/local and reinstalled kernel26 elements therein.
I then decided to try a different pkgbuild. Replaced the downloaded PKGBUILD from ABS and obtained PKGBUILD_custom_verbose from the wiki maze.
I re-named the file to PKGBUILD as required by the arch system. I then added the changes outlined previously.
cd /var/abs/local
makepkg PKGBUILD
The package was successful in generating kernel1210-custom with the associated kconfig1210-custom, vmlinuz1210-custom, and kernel1210-custom-2.6.10-4.pkg.tar.gz.EDIT: Kernel 2610-custom in each reference, sorry
This kernel was installed with pacman, lilo.conf image established, and /sbin/lilo performed. The lilo.conf step is usually skipped in descriptions even with custom builds.
The system booted ok to arch logo desktop and operates correctly. Cramfs files executed on selection.
Thus, ABS doesn't always work and PKGBUILDS aren't all the same....so much for the expression "CODE is king!" since it is different in PKGBUILDS and there are more kings!
Hope this experience helps another user to change to a -custom kernel with the latest ABS. (I had done a -custom before when it was easier to follow).
I realize I left out patches in this discussion because I didn't need them for my custom kernel.
The wiki describes how to handle patches in PKGBUILD file.
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