Folks,
I ran "yum update" late Saturday, and when I re-booted the machine, it
couldn't find my Netgear WG311T. The first couple of lines in
".../dmesg" looked like:
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet )
Linux version 2.6.12-1.1456_FC4 ([EMAIL PROTECTED])
(gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 Thu Sep 22 02:11:36
EDT 2005
If I back off to the previous configuration, I get
Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet )
Linux version 2.6.12-1.1447_FC4 ([EMAIL PROTECTED]) (gcc
version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 Fri Aug 26 20:35:25 EDT 2005
Nosing about in Google to try to figure out what had gone wrong, I
stumbled upon atrpms.net/dist/fc4/madwifi, which I recognized as the
source of the version of madwifi that used to work (I need to take
better notes!). IIRC, last time I clicked on the rpm, clicked on the OK
for "install process," and magically got the driver installed, and
working (or nearly so), but then I was running the same kernel version
as the rpm.
If I install the 2.6.12-1.1456 madwifi rpm while running the 1447
kernel, will I make a worse mess, or is that the solution? Or do I need
to fetch the lan cable, and reboot in 1456 to fix the 1456 kernel?
I'm pretty new at this. I think I have the original problem figured
out, but don't want to add any complexity I don't need.
Is it the case that "kmdl" indicates a patch to a kernal, and that I can
run yum as much as I want, until the kernel version changes, and then I
have to come back here and install the new patch? At least until
madwifi goes GA?
Many thanks,
Chuck Sardeson
_______________________________________________
atrpms-users mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/atrpms-users
