Posted by: Anonymous Coward
on May 05, 2002 03:34 AM
Yes, now I have got to compile, because of the IRQ-routing problem of my laptop. SuSE keeps saying, that noone needs to compile an own kernel. I find this stupid (I agree with you at that point), and let me tell a strange story about SuSE's default kernel. Once I had installed SuSE6.4 on a Abit BE2, with a HPT366 UDMA66 controler. The harddrive was on that controler. The install was nice, and then I decided to compile an own kernel. I had to realize, that the standard kernel did not contain the HTP366 driver, so I applied the patch from Anre Hedrick, but the kernel did not boot. And I saw the coment in the patch, that in its current status it is not bootable. However, the SuSE kernel booted in! So SuSE have modified the patch from Andre removing the "not bootable" restriction. Being a lamer, and having not internet access to get help, I did not find this option so I stayed with the original SuSE kernel. After a very short while, I realized, that is is bloody unstable. I locked up the box on the next day. I was not able ot resolve this, finally I put the harddrive to the normal IDE controler, and everythig went just fine with my own kernel.
So, I just wanted to point out, that SuSE sometimed does strange stuff with its kernel, and it is not certainly good. If I had stayed with the SuSE kernel as they wanted, and I had never tried to apply my own kernel, I would have never figured out why my linux is useless unstable....
So, we agree at last: let's just have our own kernel without the unnecessary craps and undocumented patches.
Re:strange bugs - nice try
Posted by: Anonymous Coward on May 05, 2002 03:34 AMSuSE keeps saying, that noone needs to compile an own kernel. I find this stupid (I agree with you at that point), and let me tell a strange story about SuSE's default kernel.
Once I had installed SuSE6.4 on a Abit BE2, with a HPT366 UDMA66 controler. The harddrive was on that controler. The install was nice, and then I decided to compile an own kernel. I had to realize, that the standard kernel did not contain the HTP366 driver, so I applied the patch from Anre Hedrick, but the kernel did not boot. And I saw the coment in the patch, that in its current status it is not bootable. However, the SuSE kernel booted in! So SuSE have modified the patch from Andre removing the "not bootable" restriction. Being a lamer, and having not internet access to get help, I did not find this option so I stayed with the original SuSE kernel. After a very short while, I realized, that is is bloody unstable. I locked up the box on the next day. I was not able ot resolve this, finally I put the harddrive to the normal IDE controler, and everythig went just fine with my own kernel.
So, I just wanted to point out, that SuSE sometimed does strange stuff with its kernel, and it is not certainly good. If I had stayed with the SuSE kernel as they wanted, and I had never tried to apply my own kernel, I would have never figured out why my linux is useless unstable....
So, we agree at last: let's just have our own kernel without the unnecessary craps and undocumented patches.
Cheers
gaboro
#