Sitsofe Wheeler :
from what i see in my setup, /etc/initramfs-tools/conf.d/resume references a resume image by UUID. Fstab has only UUID references, and i do NOT have the issue with resume images, at least not in that flavor. The boot log says something about resume, but then produces the IRQ timeouts.
That leaves two options:
1.- it is the same problem, but the symptoms differ: if you have UUID references, the isue manifests itself as an IRQ timeout. If you have /dev/ references, the issue manifests itself as a resume image not found.
2.- They are two difernt beasts, one related to a bug in the SATA/PATA controller, other related to obsolete /dev/ references produced by the change in behaviour in disk recognition.
Purely speculating here, though, i don't know a thing about how resume images are created, referenced or loaded, or why a reference problem could be related to a driver issur, but my guess is that 2 is more correct, at least form what i've see in my box, and form the fact that if you have the "resume not found" problem, you still seem to be able to boot, wich is not my case: my box hangs dead in those IRQ timeouts when i try to boot with 2.6.20.16. no "press enter to boot" for me.
LarsBjerregaard :
I have produced my lspci output and it is now posted in the survey as post #305. i'm bukharin in the ubuntu forums.
Sitsofe Wheeler : tools/conf. d/resume references a resume image by UUID. Fstab has only UUID references, and i do NOT have the issue with resume images, at least not in that flavor. The boot log says something about resume, but then produces the IRQ timeouts.
from what i see in my setup, /etc/initramfs-
That leaves two options:
1.- it is the same problem, but the symptoms differ: if you have UUID references, the isue manifests itself as an IRQ timeout. If you have /dev/ references, the issue manifests itself as a resume image not found.
2.- They are two difernt beasts, one related to a bug in the SATA/PATA controller, other related to obsolete /dev/ references produced by the change in behaviour in disk recognition.
Purely speculating here, though, i don't know a thing about how resume images are created, referenced or loaded, or why a reference problem could be related to a driver issur, but my guess is that 2 is more correct, at least form what i've see in my box, and form the fact that if you have the "resume not found" problem, you still seem to be able to boot, wich is not my case: my box hangs dead in those IRQ timeouts when i try to boot with 2.6.20.16. no "press enter to boot" for me.
LarsBjerregaard :
I have produced my lspci output and it is now posted in the survey as post #305. i'm bukharin in the ubuntu forums.