On Sun, 27 Aug 2006 14:16:41 +0200 Christian Perrier <[EMAIL PROTECTED]> wrote:
> > > > If that's not the case and it locks hard, you can try to unload some > > modules first; the usb and ieee1394 modules for example. > > > I tried unloading all the ieee1394 stuff and as much USB stuff as > possible but it didn't give much results. OK, this sounds as a real regression. I'll send your report upstream to the people that made s2ram, but maybe it needs to go to the kernel guys too. They will probably ask you this too: To narrow this down could you try again from the console with a much modules unloaded as you can, e.g. wireless (ipw2200), your graphics (drm, i915, intel_agp, agpgart), usb (ehci_hcd,uhci_hcd, usbcore), (eth1394, ohci1394, ieee1394), pcmcia (yenta_socket, rsrc_nonstatic, pcmcia_core) maybe even sound (snd_intel8x0,snd_ac97_codec,snd_pcm_oss, snd_pcm). If it then works, try adding drivers untill it stops working, then we can poke the maintainer of that driver;) I know it's a frustrating work... I hope s2disk does work for you, that should be easier to get to work. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
