> > So I rebooted, turned HAL off, and slept it. I was delighted to see that
it
> > woke back up. But when I tried to do anything, it seemed unable to access
> > the disk.
>
> Hrm... can you try to edit
> arch/ppc/platforms/pmac_cache.S, and spot that bit of code:
>
> /* disp-flush L1 */
> li r4,0x4000
> mtctr r4
> lis r4,0xfff0
> 1: lwz r0,0(r4)
> addi r4,r4,32
> bdnz 1b
> sync
> isync
>
> And change the line
>
> lis r4,0xfff0
>
> to
>
> li r4,0
>
> and tell me if that helps...
Hi Ben,
You're a genius! I gave that a go (actually I made that edit in 3 locations in
that file, per your earlier email on the topic -- was that okay, or should I
do it with just the one line?) and it seemed to help. Sleep seems to work
now, including with the X server (DRI on or off), although I haven't yet
subjected it to more extensive testing (with HAL, playing with USB and
Firewire devices, doing post-wake tests to see if I can reproduce those funny
disk errors, etc). There are several second long delays when the X server is
involved, with lots of onscreen psychadelics. I'll remove the delays in the
radeon driver per your earlier post and see if that helps.
Right now I'm tracking down why the X server won't go past 640x480. It's a
problem also with unpatched 2.6.12-rc2, so now I'm compiling vanilla 2.6.11
to see if the problem manifests itself there. The Xorg log reads:
(II) RADEON(0): I2C bus "DDC" initialized.
(WW) RADEON(0): Video BIOS not detected in PCI space!
(WW) RADEON(0): Attempting to read Video BIOS from legacy ISA space!
(WW) RADEON(0): Unrecognized BIOS signature, BIOS data will not be used
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 2, Detected Type: 0
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): I2C device "DDC:ddc2" registered at address 0xA0.
(II) RADEON(0): I2C device "DDC:ddc2" removed.
(II) RADEON(0): DDC Type: 3, Detected Type: 0
(II) RADEON(0):
(II) RADEON(0): Primary:
Monitor -- NONE
Connector -- DVI-D
DAC Type -- TVDAC/ExtDAC
TMDS Type -- Internal
DDC Type -- DVI_DDC
(II) RADEON(0): Secondary:
Monitor -- NONE
Connector -- VGA
DAC Type -- Primary
TMDS Type -- External
DDC Type -- VGA_DDC
(WW) RADEON(0): Video BIOS not detected, using default clock settings!
(WW) RADEON(0): Failed to probe xtal value ! Using default 27Mhz
(II) RADEON(0): Probed PLL values: xtal: 27.000000 Mhz, sclk: 83.076920 Mhz,
mclk: 83.076920 Mhz
(EE) RADEON(0): MergedFB does not work with Option UseFBDev, MergedFB mode is
disabled
(==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0)
(II) RADEON(0): Validating modes on Primary head ---------
(II) RADEON(0): Color LCD: Using default hsync range of 28.00-33.00 kHz
(II) RADEON(0): Color LCD: Using default vrefresh range of 43.00-72.00 Hz
(II) RADEON(0): Clock range: 12.50 to 350.00 MHz
Now, under Ubuntu's 2.6.10, it also defaulted to 640x480, but by adding...
HorizSync 31.5-48.5
VertRefresh 40-70
...to xorg.conf, I was able to get it to happily do 1024x768. If 2.6.11 also
gives me the problem, can you recommend anything to me? Might there be
something I'm doing wrong in my kernel's .config?
Thanks for all your help Ben,
Steve
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
