unknown
1970-01-01 00:00:00 UTC
I can confirm that missing firmware doesn't work.
I just attempted to load garbled firmware, but it failed some sanity
checks; this leaves open the possibility of corrupted firmware loading
if it passes these sanity checks.
The old firmware I had sitting around could have been corrupted (I had a
hard disk failure in the time since I had last downloaded the firmware),
or suspend2/tuxonice might have been doing something the driver didn't
like for several intermediate versions.
In any event, thanks for the comments -- and for working on the driver!
(For those searching these archives in the future, my kernel is Gentoo
source 2.6.23-tuxonice.)
Best,
Sourav
I just attempted to load garbled firmware, but it failed some sanity
checks; this leaves open the possibility of corrupted firmware loading
if it passes these sanity checks.
If not, I can only wonder why the driver works better now ... fewer
kernel oops'es, better performance under tuxonice hibernation.
I have no idea.kernel oops'es, better performance under tuxonice hibernation.
hard disk failure in the time since I had last downloaded the firmware),
or suspend2/tuxonice might have been doing something the driver didn't
like for several intermediate versions.
In any event, thanks for the comments -- and for working on the driver!
(For those searching these archives in the future, my kernel is Gentoo
source 2.6.23-tuxonice.)
Best,
Sourav