
I don't quite understand why people are having a problem clicking a url link.kowal wrote:I'm unable to resolve your domain name. dnsstuff.com resolved it to 83.223.98.63 which stil doesn't work as below--17:54:38-- http://83.223.98.63/nitro/ebuilds/nitro ... -r2.ebuild
=> `nitro-sources-2.6.10-r2.ebuild'
Connecting to 83.223.98.63:80... connected.
HTTP request sent, awaiting response... 404 Not Found
17:54:41 ERROR 404: Not Found.
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
detect_version
IUSE=""
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"
KEYWORDS="~x86 ~amd64"
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
ewarn "Now compile this beauty, reboot, and fasten your seatbelts to experience the fastest desktop you've ever seen!"
echo
}
Something is not right with my ISP, it's unable to resolve your domain name. I managed to access your site thru an outside proxy.PickledOnion wrote:I don't quite understand why people are having a problem clicking a url link.kowal wrote:I'm unable to resolve your domain name. dnsstuff.com resolved it to 83.223.98.63 which stil doesn't work as below--17:54:38-- http://83.223.98.63/nitro/ebuilds/nitro ... -r2.ebuild
=> `nitro-sources-2.6.10-r2.ebuild'
Connecting to 83.223.98.63:80... connected.
HTTP request sent, awaiting response... 404 Not Found
17:54:41 ERROR 404: Not Found.
No one is aksing anyone to resolve ip numbers or browse directories.
It's quite simple:
Click here for the ebuild and
click here for the patch.
If ayone is having problem with clicking the link, could they let me know (so far, 2091 people have managed ok).
edit: apologies if this seems slightly rude, but why someone needs to resolve a link with dnsstuff.com is beyond me
At least you have it now.kowal wrote:Something is not right with my ISP, it's unable to resolve your domain name. I managed to access your site thru an outside proxy.
paste your grub config for this kernel pleaser@mbo wrote:my frame buffer messes up saying it has to be a multiple of 4 with mtrr or something - I can't really tell..
Yeah, I am also curious about this. Is this a somehow-improved version of the driver?GentooBox wrote:what is with the sk98lin driver ?
I use the driver, and its included in the official tree. - right ?
So nitro's more my cup of coffee. How about morph-sources?Darckness wrote:GentooBox: This is a different driver than the standard one.
racoontje: nitro-sources is not meant to be better or worse than any other kernel. The point of it is to give users a (mostly) working patchset with patches that they want that do not necessarily exist together within the official gentoo kernels. If you like ikke's patches better than nitro's, than ikke is better. If you don't, then nitro is better. That's all there is to it.
That being said, ikke-sources is meant to be mm-based, whereas nitro-sources is strictly ck-based (possibly including some fixes from mm where applicable). If you like mm (love-sources was mm-based), you'll probably like ikke.
As a side note, ikke-sources are meant to be a stable alternative to those offered in portage. nitro-sources offers no guarantee of stability. For that reason, nitro may contain more recent and developmental patches than ikke.
Hope that helps!



He has a LOT of CK stuff in his that you have in yours too. Of course, cuz you're both basicly CK based. BUT with morph8 he took out some CK stuff including schedulers and a few other things and guess what -- his patch now causes no audio problems for me while yours make me audio useless still.Darckness wrote:racoontje: From what I've seen morph-sources is ck-based, but really it would be more accurate to say that it's closer to cko-based since it has so much extra crap like supermount (yeah, I'm one of those guys) in it. In the released of morph and nitro, one usually comes out with something immediately (or very soon after) the other, which makes it seem almost like a race sometimes. I say this since I noticed that he switched to ckdev at the exact same time I did (at the urging of bollucks). Maybe it is some sort of race that I was not alerted to?
Anyway, what I notice in morph-sources (recently, since I haven't really been keeping tabs on it for long) is that he's put in a lot of untested/experimental/bad patches that he later has had to revert in order to fix other stuff. I'm not saying you shouldn't try/use it by any means, but it seems almost as though he's trying to take on too many extra patches to make them all work right (sorry yardbird, I DO respect your work, but that's just the way it seems to me).
Off that topic, I'll probably have a new nitro out in a day or two (or three). Anyone have anything they want added? First person to say "supermount" wins a link referring them to the ivman howto...
Given that these guys are just slapping together patches that other people are making, why not contact ck directly or on his mailing list and ask him? It doesn't help development if you don't tell the person who's making the patches.feld wrote:He has a LOT of CK stuff in his that you have in yours too. Of course, cuz you're both basicly CK based. BUT with morph8 he took out some CK stuff including schedulers and a few other things and guess what -- his patch now causes no audio problems for me while yours make me audio useless still.I think you should both work together to find out what is causing the problems.....
-Feld
Well, yes and no. -cko has loads of stuff I never use and thus won't be in -morph. My policy with -morph is that I put in only stuff that I use and test extensively and that is not likely to interfere with other parts of the kernel in case of a breakage.Darckness wrote:racoontje: From what I've seen morph-sources is ck-based, but really it would be more accurate to say that it's closer to cko-based since it has so much extra crap like supermount (yeah, I'm one of those guys) in it.
Actually I did not switch to ckdev, I included only some minor updates plus the io-priority patch. And yes, I keep an eye on nitro to see if interesting stuff gets inDarckness wrote:In the released of morph and nitro, one usually comes out with something immediately (or very soon after) the other, which makes it seem almost like a race sometimes. I say this since I noticed that he switched to ckdev at the exact same time I did (at the urging of bollucks). Maybe it is some sort of race that I was not alerted to?
Not really. In the first place I marked the whole 2.6.10-morph series as experimental (as clearly stated in the changelog); secondly, I reverted some parts of the ck patch that, according to many reports, caused interactivity problems in all -ck based kernels. It is true that I try to be as up-to-date as possible, but, apart from the ck issues, I have never reverted back a patch because it caused problems.Darckness wrote:Anyway, what I notice in morph-sources (recently, since I haven't really been keeping tabs on it for long) is that he's put in a lot of untested/experimental/bad patches that he later has had to revert in order to fix other stuff.
I don't understand much all this dislike for supermount. It is pretty easy to setup and it does things that ivman does not (for example forcing the umount of a cdrom when a damn userspace app tries to lock it regardless). I know it won't ever make it into mainline, but I doubt that ivman is the right-way (tm) to do things either.Darckness wrote:First person to say "supermount" wins a link referring them to the ivman howto...
AFAIK Con Kolivas is aware of the problems and working to resolve them. There were some bugreports on the -ck mailing list too.bollucks wrote:Given that these guys are just slapping together patches that other people are making, why not contact ck directly or on his mailing list and ask him? It doesn't help development if you don't tell the person who's making the patches.
http://www.bluescarni.infoAlbert Einstein wrote:I consider it [...] urgently necessary for [...] workers to get together, both to protect their own economic status and [...] to secure their influence in the political field.
Code: Select all
LD .tmp_vmlinux1
drivers/built-in.o(.text+0x9ca9f): In function `input_open_file':
: undefined reference to `.L617'
make: *** [.tmp_vmlinux1] Error 1well someone should clue him in. I dont run Wine or Cedega nor do I renice X. Every kernel I've used that has all his stuff in breaks my sound in OpenAL games.bollucks wrote:I follow the ck mailing list and as far as he knows the problem is limited to wine and cedega games or people renicing X to -ve values.yardbird wrote:AFAIK Con Kolivas is aware of the problems and working to resolve them. There were some bugreports on the -ck mailing list too.
