> Make me nearly cry... What is strange is that now we use CONFIG_M386 but > if I do a 'uname -a' I got i686. I say that because we though these > kernel panic came from our new kernel and the config M486, but it seems > not. >
But is uname's output of 686 related to CONFIG_M**386***? i think not, uname -m prints out machine processor, i think config_M486 is an optimization; have you tried with i386? and what about CONFIG_X86_GENERIC? > We can't say M386 dropped hardware support since you got a fairly new > processor. So next I think we must try to upgrade the kernel since > 2.3.37 may be buggy in this area. > > - Christophe --- SliTaz GNU/Linux Mailing list - http://www.slitaz.org/
