PickledOnion wrote:Have you retried?
Code: Select all
% wget http://pickledonion.net/nitro/ebuilds/nitro-sources-2.6.10-r4.ebuild
--15:45:45-- http://pickledonion.net/nitro/ebuilds/nitro-sources-2.6.10-r4.ebuild
=> `nitro-sources-2.6.10-r4.ebuild'
Résolution de pickledonion.net... échec: Hôte non repéré.
zsh: exit 1 wget http://pickledonion.net/nitro/ebuilds/nitro-sources-2.6.10-r4.ebuildSo I will try again and again and ...PickledOnion wrote:The server load is very high and past a certain point you can't connect.
Code: Select all
# Copyright 1999-2004 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
UNIPATCH_LIST="${DISTDIR}/patch-${KV}.bz2"
K_PREPATCHED="yes"
UNIPATCH_STRICTORDER="yes"
K_NOSETEXTRAVERSION="yes"
K_NOUSENAME="yes"
ETYPE="sources"
inherit kernel-2 eutils
detect_version
IUSE="want-mm"
DESCRIPTION="Full sources for the Stock Linux kernel and some various patches to improve desktop performance and experience"
HOMEPAGE="http://sepi.be/nitro.php"
SRC_URI="${KERNEL_URI} http://pickledonion.net/nitro/patches/patch-${KV}.bz2 http://pickledonion.net/nitro/patches/patch-${KV}-mm.bz2"
KEYWORDS="~x86 ~amd64"
src_compile() {
if use want-mm
then
cd ${S}
echo
einfo "Applying mm patch because you wanted it!"
echo
epatch ${DISTDIR}/patch-${KV}-mm.bz2
fi
}
pkg_postinst() {
postinst_sources
ewarn "IMPORTANT:"
ewarn "This is a experimental kernel version, I'm not responsible for breaking your system"
ewarn "ALWAYS keep a second stable and bootable kernel apart in your boot manager"
echo
if use want-mm
then
ewarn "You have enabled mm/bk patches. They've been tested, but only to the compile stage."
ewarn "If bad things happen, remember:"
ewarn "YOU chose it."
ewarn "With that said, I hope it runs great!"
echo
fi
ewarn "Now compile this beauty, reboot, and fasten your seatbelts to experience the fastest desktop you've ever seen!"
echo
}

Is your keyboard some exotic style keyboard? Exotic being not standard PS/2. If so, perhaps you don't have a proper driver compiled in? I can't imagine anything a patchset would do...unless they change the defaults in menuconfig in such a way that your driver for your keyboard doesn't get compiled...nlabadie wrote:I've got a strange keyboard problem on a Dell Inspiron 5150 when using nitro-sources-2.6.10-r4 or mm-sources: the keyboard doesn't work at all. No response, no echos, nothing.
I had the same problem when using mm-sources... it seems to have crept into nitro-sources since patches from mm have been included. When using nitro-sources-2.6.10-r2 the keyboard works fine. When using nitro-sources-2.6.10-r4 (with the same config) the keyboard no longer responds. Any ideas?
Nope, it's a standard Dell Inspiron 5150 laptop keyboard. Like I said, I had the same problems with mm-sources. Now that notro-sources is including patches from mm-sources, I seem to be having the same problem with nitro-sources too. With nitro-sources-2.6.10-r2 the keyboard works fine, with nitro-sources-2.6.10-r4 it's non-responsive. Both are using the same config.Teh Penguin D00d wrote: Is your keyboard some exotic style keyboard? Exotic being not standard PS/2. If so, perhaps you don't have a proper driver compiled in? I can't imagine anything a patchset would do...unless they change the defaults in menuconfig in such a way that your driver for your keyboard doesn't get compiled...


OK, I re-read the first post. I don't see where it mentions whether the mm-patches are an addition to the ck-sources patches, or used instead of the ck-sources patches.PickledOnion wrote:Look at the first post, you know, the one by Darkness when he explains all about the patchset.justanothergentoofanatic wrote:Is this kernel now based upon mm-sources instead of ck-sources?
-Mike

Yeah, how about you give us a chance to use some of these kernels !Darckness wrote:On the next nitro release:
Unless people start giving me tons of patches that they need implemented very soon, or exposing huge bugs in this version, I'm gonna let this one go for a few days. I've been irritating a lot of people on my end with my constant kernel patching, and I think it's time to give them a little break. Of course, if there's need for another release soon I'll be all over it.


I am not shure I am right, but it seems to me you forgot to:Teh Penguin D00d wrote:You guys didn't think you could pull off another Nitro release without hearing from me; did you?
I documented the entire build process, after the ebuild download/digest/merge.
One thing to note...when I did get booted, uname -r output "2.6.10-ck"...not nitro. Even though my symlink is pointing to the proper location. I don't know it's a mistake on my part, or on yours; but...here goes nothing...and yes; it's so verbose I even left the parts where I made typo's in...
Kernelmake.txt, as referenced aboveCode: Select all
Alright...here's to being excessively detailed... root@dustin src # cd /usr/src/ root@dustin src # ls linux linux-2.6.10-nitro4 linux-2.6.9-gentoo-r13 linux-2.6.9-gentoo-r8 xorg-x11-6.7.0-r3 linux-2.6.10-nitro2 linux-2.6.9-gentoo-r1 linux-2.6.9-gentoo-r4 linux-2.6.9-gentoo-r9 linux-2.6.10-nitro3 linux-2.6.9-gentoo-r12 linux-2.6.9-gentoo-r6 linux-2.6.9-nitro4 root@dustin src # rm .linux rm: cannot remove `.linux': No such file or directory root@dustin src # rm ./linux root@dustin src # ls linux-2.6.10-nitro2 linux-2.6.9-gentoo-r1 linux-2.6.9-gentoo-r4 linux-2.6.9-gentoo-r9 linux-2.6.10-nitro3 linux-2.6.9-gentoo-r12 linux-2.6.9-gentoo-r6 linux-2.6.9-nitro4 linux-2.6.10-nitro4 linux-2.6.9-gentoo-r13 linux-2.6.9-gentoo-r8 xorg-x11-6.7.0-r3 root@dustin src # ln -sf ./linux-2.6.10-nitro4 ./linux root@dustin src # ls -l total 8 lrwxrwxrwx 1 root root 21 Jan 8 18:02 linux -> ./linux-2.6.10-nitro4 drwxr-xr-x 20 root root 1400 Jan 6 22:21 linux-2.6.10-nitro2 drwxr-xr-x 20 root root 800 Jan 7 23:19 linux-2.6.10-nitro3 drwxr-xr-x 19 root root 656 Jan 8 17:59 linux-2.6.10-nitro4 drwxr-xr-x 19 root root 1312 Dec 31 17:02 linux-2.6.9-gentoo-r1 drwxr-xr-x 18 root root 664 Dec 24 00:21 linux-2.6.9-gentoo-r12 drwxr-xr-x 18 root root 664 Dec 31 08:15 linux-2.6.9-gentoo-r13 drwxr-xr-x 19 root root 1312 Nov 26 20:28 linux-2.6.9-gentoo-r4 drwxr-xr-x 18 root root 664 Nov 24 15:57 linux-2.6.9-gentoo-r6 drwxr-xr-x 18 root root 696 Dec 2 22:01 linux-2.6.9-gentoo-r8 drwxr-xr-x 18 root root 696 Dec 4 18:05 linux-2.6.9-gentoo-r9 drwxr-xr-x 20 root root 1304 Dec 30 15:23 linux-2.6.9-nitro4 drwxr-xr-x 3 root root 72 Dec 31 19:33 xorg-x11-6.7.0-r3 root@dustin src # cd linux root@dustin linux # make clean root@dustin linux # make mrproper root@dustin linux # make menuconfig ::configures kernel, resulting in the following .config file:: root@dustin linux # make > /home/dustin/kernelmake.txt 2>&1 root@dustin linux # ls /boot/ bzNitroUdev fbsplash grub initrd initrd-gentoo-1280x1024 lost+found (bzNitroUdev is my 2.6.9 Nitro 4 kernel, with working Udev.) root@dustin linux # cp arch/i386/boot/bzImage /boot/bzNitro root@dustin linux # ls /boot/ bzNitro bzNitroUdev fbsplash grub initrd initrd-gentoo-1280x1024 lost+found root@dustin linux # nano -w /boot/grub/grub.conf ::only showing appropriate part:: title Gentoo Dev root (hd0,0) kernel /bzNitro root=/dev/hda3 video=radeonfb:ywrap,mtrr,1280x1024@60 splash=verbose,theme:emergence initrd (hd0,0)/fbsplash ::fbsplash is the initrd holding the config for fbsplash. Yes, it works with the other kernel. Yes, I've tried it without the initrd.:: root@dustin linux # umount /boot root@dustin linux # exit exit dustin@dustin dustin $
.config, again. I rebuild by hand each time; just to see if any new options are there.
I took some advice, and checked for /proc/sys/kernel/hotplug.../proc/sys didn't even exist, though /proc did, along with most of it's directories.
Once again; any help would be beyond appreciated...Code: Select all
1 1033 124 137 14737 14752 15989 16004 16141 16142 16143 16144 16145 16146 16227 16228 16234 18 2 247 248 249 250 2854 2855 3 4 851 9 920 959 acpi asound buddyinfo bus cmdline cpuinfo crypto devices diskstats dma driver execdomains fb fbsplash filesystems fs ide interrupts iomem ioports kallsyms kcore kmsg loadavg locks meminfo misc modules mounts mtrr net partitions scsi self slabinfo stat swaps sysvipc tty uptime version vmstat
::dreams of the day I'll be using a 2.6.10 kernel...::
Code: Select all
cp /usr/src/linux/System.map /boot/System.map
Code: Select all
KDSETKEYCODE: No such device
failed to set scancode f0 to keycode 145
KDSETKEYCODE: No such device
failed to set scancode f1 to keycode 147
KDSETKEYCODE: No such device
failed to set scancode f3 to keycode 153
low latency patch would be the mingo-ll patch that comes from -ck... meaning you've already got it.Darckness wrote:Feld: the reason that the ac is behind in the mm patch is because I got lazy and didn't want to try reversing it and applying the new one. The next nitro's mm version (yes, I think I'll be doing it most of the time unless it gets to be too much of a hassle) will be as cutting edge as you can imagine. Of course, that won't be out until at least Friday/Saturday (I'm hoping I can hold out that long...) unless something big happens before then. I won't stand idly by and let other kernel patchsets get the first crack at 2.6.11-rc1 (not even gentoo-dev).
By the way, did anyone find that genetic algorithm as-sched patch? I can't really put that into the next version if I don't have the patches...
EDIT: Nevermind; just found the patch. Still curious about the low latency patch that was mentioned earlier though.
