Hi, I'm still seeing this problem with the i386 version of Ubuntu 7.10, using the LiveCD. So, my experience is that the bug is not amd64 only.
The AGP aperture size is set to 128M in my BIOS. But agpgart only recognizes it to be 4M: [EMAIL PROTECTED]:~$ sudo cat /var/log/dmesg | grep agpgart [ 132.042214] Linux agpgart interface v0.102 (c) Dave Jones [ 132.345993] agpgart: Detected SiS chipset - id:1888 [ 132.346322] agpgart: AGP aperture is 4M @ 0xf0000000 In the xorg log, dri seems to be loading fine but then there is the following error message: [EMAIL PROTECTED]:~$ sudo cat /var/log/Xorg.0.log | grep bind (EE) RADEON(0): [agp] Could not bind I have attached a complete copy of the xorg log. The following error appears in the kernel log: [EMAIL PROTECTED]:~$ sudo cat /var/log/kern.log | grep drm Oct 23 12:57:06 ubuntu kernel: [ 171.618188] [drm] Initialized drm 1.1.0 20060810 Oct 23 12:57:06 ubuntu kernel: [ 171.663073] [drm] Initialized radeon 1.27.0 20060524 on minor 0 Oct 23 12:57:12 ubuntu kernel: [ 173.904447] [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held Oct 23 12:57:12 ubuntu kernel: [ 173.904654] [drm:drm_unlock] *ERROR* Process 8267 using kernel context 0 I have not tried the fix in https://bugs.launchpad.net/bugs/45942 in Ubuntu because I am trying the liveCD. However, I have tried renaming the sis_agp module in a Gentoo installation, with kernels up to 2.6.23, and this did not change how the AGP aperture size was identified as 4M. I've also tried patching the device ids in the kernel so that the particular model of the SIS chipset isn't identified, but that didn't fix things either although I might have made errors with this. Please let me know if other log files from a LiveCD boot would be useful. If anyone is willing to try to fix the issue and needs a tester, I will be happy to install Ubuntu as well. ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/10131005/Xorg.0.log -- sis 760 AGP broken on amd64 https://bugs.launchpad.net/bugs/34144 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
