The Official HWF Kernel Repo

Kernel 2.6.30.5 available

sabashuali said:
Long awaited? 'twas only today that the previous kernel was shipped out! :dry:
Bloody hell! Talk about quick turnaround! :chk:

Thanks AT.....
Click to expand...
People have been waiting for 2.6.31 for a while, and there have been a whopping 9 release candidates for it. So yeah, it's long awaited in those terms. :) But I did build them as quickly as I could, hehe.
 
Kernel 2.6.30.5 available

2.6.30.7 is built and syncing to kernel.hardwareforums.com. As a bugfix release, it is recommended for anyone running a 2.6.30.x kernel.

 
Kernel 2.6.30.5 available

2.6.30.8 and 2.6.31.1 are built and syncing to kernel.hardwareforums.com. As usual with bugfix releases, it is recommended to upgrade if you're running a HWF kernel.


P.S. - [STRIKE]My script somehow failed to build the P3 flavor first time around, but it's building now. As soon as it's ready I'll upload that as well. Sorry for the inconvenience.[/STRIKE] Complete! P3 builds syncing now.
 
Kernel 2.6.30.5 available

Guess what? It's that time again! 2.6.31.4 is built and synced to kernel.hardwareforums.com. As usual with bugfix releases, it is recommended to upgrade if you're running a HWF kernel. Note that I skipped building 2.6.31.3, since there was only a single commit which wouldn't affect most desktops.

 
Kernel 2.6.30.5 available

2.6.31.5 is built and currently being synced to kernel.hardwareforums.com. As usual with bugfix releases, it is recommended to upgrade if you're running a HWF kernel.

 
I get the following Error :-
sudo dpkg -i linux-image-2.6.30.9*
Selecting previously deselected package linux-image-2.6.30.9.prescott.hwf.01.
(Reading database ... 109028 files and directories currently installed.)
Unpacking linux-image-2.6.30.9.prescott.hwf.01 (from linux-image-2.6.30.9.prescott.hwf.01_2.6.30.9.prescott.hwf.01_i386.deb) ...
Done.
Setting up linux-image-2.6.30.9.prescott.hwf.01 (2.6.30.9.prescott.hwf.01) ...

Hmm. There is a symbolic link /lib/modules/2.6.30.9.prescott.hwf.01/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/2.6.30.9.prescott.hwf.01/build


Hmm. The package shipped with a symbolic link /lib/modules/2.6.30.9.prescott.hwf.01/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.30.9.prescott.hwf.01/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Running postinst hook script update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.30.9.prescott.hwf.01
Found kernel: /boot/vmlinuz-2.6.28-11-generic
Found kernel: /boot/memtest86+.bin
Updating /boot/grub/menu.lst ... done

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/nvidia-common
run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 20
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-2.6.30.9.prescott.hwf.01.postinst line 1186.
dpkg: error processing linux-image-2.6.30.9.prescott.hwf.01 (--install):
subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
linux-image-2.6.30.9.prescott.hwf.01
Click to expand...

i have build-essential, other required packages installed which are required to install / compile kernel packaged
i m using Linux Mint Gloria Main Edition 7 GNOME on my Pentium D 2.66GHZ computer.
 
Mint = Ubuntu, which doesn't tend to play nice with 3rd party kernels. I'm afraid if you want to run a custom kernel, mainline Debian might be a better option.
 
Hey
Thank you for the quick reply.
Ummm . . can i get some help regarding a statement here in this thread :
and the schedulers set to be aggressively desktop-friendly
Click to expand...
What does done to the schedulers?
Also could please share as to what did you edit / change apart from make menuconfig as in the files . . . .
Also would take the effort to clear to me what is and how to use sysctl ?
Last question do you suggest noatime in fstab and if yes then is it beneficial in case of /home and/ or / only.
Thank you in advance
 
scars230 said:
...What does done to the schedulers?
Click to expand...
The HWF kernel is tuned for low-latency usage, e.g. to be ideal for desktop, gaming, multimedia, or game-server usage. The kernel timers are set for 1000Hz, and all applicable preemption settings are enabled.

scars230 said:
Also could please share as to what did you edit / change apart from make menuconfig as in the files . . . .
Click to expand...
Each kernel is built from vanilla sources from kernel.org. The configuration is based on Debian's default kernel configs, then hand-tuned to be a good fit for the architecture in question. Afterwards, the kernel is compiled with architecturally-optimized GCC cflags and packaged into .deb files. Other than the custom Tux logo, the HWF kernel is based solely off of the kernel.org vanilla sources.

scars230 said:
Also would take the effort to clear to me what is and how to use sysctl ?
Click to expand...
This should really be in a new thread, but in a nutshell sysctl in Linux is a way to dynamically tune kernel and network parameters on top of procfs and sysfs.

scars230 said:
Last question do you suggest noatime in fstab and if yes then is it beneficial in case of /home and/ or / only.
Click to expand...
Again, this doesn't have much to do with our custom kernels, so it should really be in a new thread. But noatime is beneficial wherever you run it, since it reduces HDD IO latency by reducing the amount of necessary write operations. Some applications, especially legacy mail or news apps, tend to rely on atime flags. For this reason, 'relatime' is often preferred as a compromise. It doesn't perform as well as noatime though, so if you don't need atime flags that would be the better way to go.
 
Hi there seems to be a problem :-
grep HZ /boot/config-`uname -r`
# CONFIG_NO_HZ is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_MACHZ_WDT=m
Click to expand...
2.6.31.5.x2.hwf.01 #1 SMP PREEMPT Thu Oct 22 22:54:43 PDT 2009 i686 GNU/Linux
Click to expand...
You had written 1000hz.
Please check it.
 
Crap, looks like my build scripts must've stepped on my configs in 2 cases:

Code: 
$ grep CONFIG_HZ_1000 /home/builder/kernel/hwf/BUILDS/*/linux-2.6.31.5/.config

/home/builder/kernel/hwf/BUILDS/centrino/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/core2/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/i586/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/k7/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/k8/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/p3/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/p4/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/phenom/linux-2.6.31.5/.config:CONFIG_HZ_1000=y
/home/builder/kernel/hwf/BUILDS/prescott/linux-2.6.31.5/.config:# CONFIG_HZ_1000 is not set
/home/builder/kernel/hwf/BUILDS/x2/linux-2.6.31.5/.config:# CONFIG_HZ_1000 is not set

I'll restore the configs from backups, double-check them by hand, and re-build those two. Thanks for pointing that out; you're the only one who's noticed it so far.

Edit: Looks like only the kernel timer setting was affected, and I've found the bug in my script that affected the configs. Future builds shouldn't have this problem. The fixed builds of the prescott and x2 builds will be up shortly.
 
sabashuali said:
When do you get these errors? I have never seen them before? I have been using HWF kernel only for ages and never seen any of these messages during installation.... :confused:

Is it wise to re-install the reconfigured kernel or wait until the next version is out?
Click to expand...
They're not errors per se. It's just that the kernel timer should have been 1000Hz and it's actually 250Hz, which is the Linux default value, on the latest prescott and x2 builds. It's not an urgent matter but you will get more responsiveness out of the fixed version than the bugged one. If you're running an affected kernel, I'd suggest replacing it whenever it's convenient to do so.

Speaking of which, the corrected builds of 2.6.30.9 and 2.6.31.5 for prescott and x2 are finished and are currently syncing to the server. You should find that this build has the correctly aggressive kernel timer of 1000Hz. :)

http://kernel.hardwareforums.com/
 
Man you're too quick.... I deleted the post as soon as I realised how irrelevant it was...
But thanks anyway for the confirmation.
 
Setting up linux-image-2.6.31.5.x2.hwf.02 (2.6.31.5.x2.hwf.02) ...

Hmm. There is a symbolic link /lib/modules/2.6.31.5.x2.hwf.02/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/2.6.31.5.x2.hwf.02/build


Hmm. The package shipped with a symbolic link /lib/modules/2.6.31.5.x2.hwf.02/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.31.5.x2.hwf.02/source
Click to expand...
Using mkinitramfs-kpkg to build the ramdisk.
Deprecation WARNING: use update-initramfs(8)
Click to expand...

Setting up linux-headers-2.6.31.5.x2.hwf.02 (2.6.31.5.x2.hwf.02) ...
dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead.
Click to expand...
What does this mean ?
 
These are warnings. It probably means you're installing the kernel on a newer distro than the one it was packaged with (Debian Lenny).
 
Kernel 2.6.30.5 available

Good morning campers. It's new kernel time! 2.6.31.6 is built and syncing to kernel.hardwareforums.com. This build has a heft dose of bugfixes, including patches for a few security issues. As such, it is recommended to upgrade if you're running a HWF kernel.

 
Mr. Trend,
While looking at your kernel i found out that "optimize for size" was enabled.
Doesn't that pass -os flasg instead of -o2 ? which may make it less optimized in performance sense ?

I compiled a kernel for my self using the method you prescribed. The new kernel didn't work out. How do i check what went wrong ?
The machine is in a remote location are there any logs which i can use to identify the problem ?
 
scars230 said:
Mr. Trend,
While looking at your kernel i found out that "optimize for size" was enabled.
Doesn't that pass -os flasg instead of -o2 ? which may make it less optimized in performance sense ?
Click to expand...
Yes, except that I'm overriding the build flags with my build scripts. I've changed it in the defaults though so if anybody chooses to re-use my kernel configs, it will be the option that makes more sense for performance.

[ot]
scars230 said:
I compiled a kernel for my self using the method you prescribed. The new kernel didn't work out. How do i check what went wrong ?
The machine is in a remote location are there any logs which i can use to identify the problem ?
Click to expand...
Do you mean it doesn't fully boot? In that case you may have compiled out something the machine needs to run. A dmesg log can be handy, or a console output during the boot process would be nice.[/ot]
 
You must log in or register to reply here.
Back
Top