antonio montagnani wrote: > I updated kernel yumming it > > 1) at reboot, the madwifi driver from freshrpms didn't build against dkms > 2) after upgrading I should have the following two kerenels: > > 2.6.22.1-27 > 2.6.21-1.3228. Which kernel were you actively running when you upgraded. My understanding is that the yum installonlyn plugin keeps the new one and the one you are currently running. If you have a newer one you are not currently running, it punts it in favor of the new one. > surprise!!! I found 2.6.21-1.3194 but no 2.5.21-1.3228 >From which I would infer that you were running the 3194 kernel when you did the yum update. > And I had to restart by 2.6.21-1.3194 > > What is happening??? Just my thoughts on the issue. -- Kevin J. Cummings kjchome@xxxxxxx cummings@xxxxxxxxxxxxxxxxxx cummings@xxxxxxxxxxxxxxxxxxxxxxx Registered Linux User #1232 (http://counter.li.org)