El Sábado, 3 de Julio de 2004 13:09, Ed Wildgoose escribió: > >Thanks for the info I don't know why I'm having problems compiling the > > kernel image [1]. It looks like a linking issue or a bad module, but I > > doubt it's easy to solve. I am going to change distro in a few days so I > > think that trying to find a solution might be not worthy :-). > > Unlikely to change anything... Compiling is somewhat independent of the > rest of your system (perhaps depends on gcc version and some other > stuff, but not too much in practice) I think it will change because: I'm not going to use the same distro, but change from Fedora to Suse. What's more, I've managed to compile this same kernel source time ago, so something wrong must be happening :-). > >What's more, I haven't changed the CPU type (Athlon by default) so I'm > > trying to build modules even without having compiled successfully the > > kernel image. > > Aha, but did you do all the "make" commands that you were told to do? > It's important that they are all done Of course I did =). BTW, I've been compiling (successfully most of the time) 2.4.x linux kernels since 2-3 years ago :-P. As I said, I'll get Suse 9.1 Prof soon (the 10th most probably). I'm curious about the PSCHED_CLOCK_SOURCE value. Is it wrong or deprecated the default Fedora's value (PSCHED_JIFFIES instead of PSCHED_CPU)? Or is it just that you have to compile your own kernel in order to get ingress rate policies working fine ? _______________________________________________ LARTC mailing list / LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
