Jan Rychter wrote: >>>>>>"Marcelo" == Marcelo Tosatti writes: > > [...] > Marcelo> 2.6 is already stable enough for people to use it. > > Yes, that's an old post I'm responding to, but I've just given 2.6 a try > on my desktop machine, and the above statement seems even more > annoying. I hit the following problems: > > -- I had to wrestle ATI drivers into compiling, they finally did, but > the kernel prints scary-looking warnings with call stacks, about > "sleeping function called from invalid context at mm/slab.c:1856, I have an nForce2 w/ Radeon 9000. No problems w/ DRI drivers (included in kernel) or thi ATI supplied drivers, which ATI says successfully compiled against 2.6.0-test6. > -- modules don't autoload for some reason (though I'm sure that could > be solved), Make sure you have all the different module options turned on. In 2.6 there are different options for loading, unloading and force unloading modules. > -- bttv does not compile, so no video input for me, I don't know anything about video input. Did you try Google? > -- drivers for my telephony card (from Digium) are not 2.6-ready, so > no telephony support for me, I don't know anything about telephony. Did you try Google? > -- I have just frozen the machine hard by copying files over NFS and > doing a simulation write to an ATAPI CD-RW at the same time. What CPU/chipset do you have? There are timing issues with nForce2 and AMD CPUs. A quick search of the LKML archives will yield lots of discussion and patcheson this issue. > > I haven't even gotten to VMware and user-mode Linux, which I also need, > and I'm not even dreaming about getting my scanner to work. Not to > mention that on my laptop there would be an entirely different set of > issues, and software suspend in 2.6 is, well, still lacking. VMWare won't work (according to the VMWare tech support people), but they will (probably) support 2.6 kernels in their next point release. I assume you are talking about their workstation product. SWSusp works fine on my laptop. > > So, as for me, 2.6 is a definite no-no. I see no advantage whatsoever in > running it, it caused me nothing but pain, and there is no improvement > that I could see that would justify the upgrade. But there is plenty of improvement for plenty of people. > > So please be careful when making statements like that. 2.6 is *NOT* > stable enough nor ready enough for people to use it, unless those people > have a narrow range of hardware on which the 2.6 kernel has actually > been tested (translation: they have the same hardware as the main > developers do). I doubt I have the same hardware as the main developers, but I did read the documentation. Did you? Even if it is stable enough for most people, it is still a beta kernel. > > --J. -Roberto.