Re: iBook G3 owners
> 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.
There isn't that much genius in there, and I still have no explanation
why that works in fact. There is something really strange happening with
those machines.
> 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.
There are still issues with USB, I would be careful if I were you, that
is unplug stuffs before suspend.
> 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:
The X server behaviour has nothing to do with the kernel here.
> (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,
The problem is that the dislay in this machine doesn't do DDC and the X
server is too dumb to try to obtain the panel size without it. Just do
what you did, that is put some wide enough refresh ranges and tell it to
do 1024x768x60.
Ben.
Reply to: