Right,
I tried compiling the 2.2.16 from kernelhq. I just
couldn't get it to work well. I could boot, but it
kept hosing up (hard locks) probably due to my abit
mobo with the hpt controllers. The SuSE kernel works
well. My beef was why wouldn't a stock kernel work.
Well it probably would have, if I had compiled it like
the suse kernel, and used modules instead of puting
into the kernel. But, I was informed by another
poster that the 2.2.16 with the support built into the
kernel would be more stable with the BP6. I still get
hard locks. I intend to try and play with the kernel
some more over the weekend. I want to try the Suse
kernel, get it stable, then recompile with built-in
support for the drivers. But, if I may ask, Is there
an initrd issue with on-board UDMA-66 controllers? I
know that ide support is built in, so initrd doesn't
need to preload those. But, doesn't linux tread the
udma-66 and 100's the same as scsi? In this case, I
may have been hosed, as I didn't use the mk_initrd
while compiling.
Any thoughts appreciated... Ron
--- Michael Hasenstein
Ron Heron wrote: ...
BTW: my kernel issue was that the source package from kernelhq wouldn't work, not the binary version. opposite of what you said, the binary works.
The kernel from ftp.kernel.org WILL work, unless you use features we added, like LVM or ReiserFS.
Didn't you have some patch issues? That has nothing to do with the original kernel not running, because it DOES (compile, link and) run.
-- Michael Hasenstein http://www.suse.de/~mha/ SuSE Linux AG, Nuernberg (Germany) SuSE Inc., Oakland, California (US)
__________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq