Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=16468
Ubuntu | linux
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |major
------- Additional Comments From [EMAIL PROTECTED] 2005-10-11 14:43 UTC -------
(In reply to comment #0)
This same problem occured with the RC1 Breezy LiveCD on the iMac. The card is a
Ati Technologies, Inc. Rage 128 Pro Ultra (TR). The LiveCD loaded the ati driver
with the same negative results. I was able to fix the problem by changing the
driver to "r128" and putting r128 and agpgart in /etc/modules. Now the Breezy
iMac is working fine with two days to go before final. If the final Breezy will
use the same installroutine as the LiveCD, then this type of iMac (see original
report) will be configured with a non-working xorg.
> After ugrading the kernel on iMac 600Mhz running Breezy Kubuntu to 2.6.12-xxx
> I
> can no longer login with KDM. It takes a long time before the screen gets
> drawn
> and the login boxes appear. When they do, the keyboard is unresponsive. This
> happens with all the 2.6.12 builds from Ubuntu that I've tried, and also with
> the 2.6.13 official Debian kernel from www.ppckernel.org that I tested. I can
> login with ssh from another box and top shows that xorg is eating 99% CPU
> resources. Not sure if this is KDE-specific since I haven't tried loading
> Gnome
> on this iMac. Never any problems with 2.6.11 and below.
>
> [EMAIL PROTECTED]:~$ cat /proc/cpuinfo
> processor : 0
> cpu : 745/755
> temperature : 19-21 C (uncalibrated)
> clock : 600MHz
> revision : 50.20 (pvr 0008 3214)
> bogomips : 1196.03
> machine : PowerMac4,1
> motherboard : PowerMac4,1 MacRISC2 MacRISC Power Macintosh
> detected as : 256 (iMac "Flower Power")
> pmac flags : 00000010
> L2 cache : 256K unified
> memory : 512MB
> pmac-generation : NewWorld
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
--
kubuntu-bugs mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
