Hello, I have no solutions to the problems you encounter. But I can share experiences as I run a very similar machine using a 2.6.11.4 kernel, compiled myself from upstream source (kernel-package is my friend).
libook:/home/henning# cat /proc/cpuinfo processor : 0 cpu : 750FX temperature : 28 C (uncalibrated) clock : 700MHz revision : 1.2 (pvr 7000 0102) bogomips : 1389.36 machine : PowerBook4,3 motherboard : PowerBook4,3 MacRISC2 MacRISC Power Macintosh detected as : 257 (iBook 2 rev. 2) pmac flags : 0000001b L2 cache : 512K unified memory : 640MB pmac-generation : NewWorld Francis J. Lacoste schrieb: > I have an iBook G3 700Mhz, dual USB and run Sid. Besides that I run a mix-up of hoary, sarge and sid. > With kernel-image-2.6.10, when I ran fblevel 0 (or when the screensaver does > the equivalent) the display becomes white with a ghost image of what was > previously on the screen. I had that issue with earlier kernels as well. > eth0: suspending, WakeOnLan disabled > radeonfb: suspending to state: 3... > radeonfb: switching to D2 state... > cpufreq: resume failed to assert current frequency is what timing core thinks > it is. > radeonfb: switching to D0 state... > radeonfb: resumed ! > eth0: resuming > PHY ID: 4061e4, addr: 0 > ide_pmac: Set UDMA timing for mode 2, reg: 0x1090038c > hda: Enabling Ultra DMA 2 > ide_pmac: Set UDMA timing for mode 2, reg: 0x1090038c > hdb: Enabling Ultra DMA 2 > adb: starting probe task... > agpgart: Putting AGP V2 device at 0000:00:0b.0 into 2x mode > agpgart: Putting AGP V2 device at 0000:00:10.0 into 2x mode > adb devices: [2]: 2 c4 [3]: 3 1 [7]: 7 1f > ADB keyboard at 2, handler 1 > ADB mouse at 3, handler set to 4 (trackpad) > adb: finished probe task... > eth0: Link is up at 10 Mbps, half-duplex. > eth0: Pause is disabled > > On 2.6.11 only the two first messages appear on the console after I open the > lid. (Actually, the second message also contains the PCI device number). > Full ACK. I'm having issues related to suspend-resume and power management in general but lack time to hunt down on my own. Is there a comprehensive guide to debug such problems efficiently? Kind regards, Henning Lorenzen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
