Currentlty I'm favouring patch4. Possible random crashes maybe with
patch3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch 215_glx_drawable_refcounting.diff for
Sorry about the delay, I've been trying to figure out if there is a
difference between the performance of the two patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please
This should be basically the patch here
https://bugs.freedesktop.org/show_bug.cgi?id=28181#c40
** Attachment added: patch4
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3637040/+files/patch4
** Patch removed: Remove upstream commit and re-apply
Right, the above patches should be correct now (he says hopefully). I
don't know which is the best to use.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch
This patch removes commit b5093063b5d76ff31519a2daf85ea32808f1afe6 and
replaces it with the old 215_glx_drawable_refcounting.diff
** Attachment added: patch3
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3637039/+files/patch3
** Bug watch added:
Do I need to raise an explicit SRU request or is this bug report good
enough?
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, stupid question alert - how do I assign 'canonical-x' because it
won't let me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch 215_glx_drawable_refcounting.diff
Hi Paul, do you still have this problem? I saw this thread on the
Gentoo forum and thought it might be your problem
http://forums.gentoo.org/viewtopic-t-945822.html?sid=61a9538d70fc4e756c8f321a76eefa94
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ah, okay. I think I understand. I should of downloaded the source code
instead of browsing the online version. Sorry for wasting your time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043066
Are you sure? When I browsed the code of ubiquity, yaboot-installer
hadn't been updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043066
Title:
Test Case dwi001- Full disk install PPC
I've just checked again and ubiquity does not contain the patch. Am I
being stupid or something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043066
Title:
Test Case dwi001- Full disk install
I see the patch still hasn't made it into Ubiquity in 13.04. Any chance
the latest yaboot-installer can be pushed into Ubiquity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1043066
Title:
Test
Apologies, reviewing those patches I seem to have sucked in a random
nouveau line or two. I'll check them some more and re-submit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Public bug reported:
Hello,
This bug affects oneiric and precise. Previous versions of Ubuntu used
to carry a patch 215_glx_drawable_refcounting.diff . This came about
because of this upstream bug report
https://bugs.freedesktop.org/show_bug.cgi?id=28181 .
The patch was removed in oneiric
** Attachment added: Log of a crash
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3600792/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
** Attachment added: Remove upstream commit and re-apply
215_glx_drawable_refcounting.diff
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3600793/+files/patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: Refreshed comment 40 patch
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903/+attachment/3600794/+files/patch2
** Tags added: precise
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1160903
Title:
Please re-patch 215_glx_drawable_refcounting.diff for precise (12.04)
To manage notifications about this bug go
I opened a new bug about the kwin crashing with patches to fix it here
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1160903
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946677
Title:
PowerPC + radeon + Kernel Mode Setting (KMS) has problems with AGP. If
you force pci mode radeon.agpmode=-1 does this help?
Userspace mode setting with radeon was dropped after Ubuntu 12.04/Debian
wheezy so you have to use KMS in 12.10 onwards. KMS on PowerPC is
something that really needs
I just tried Xubuntu without the composting manager and see this problem
also. The only exception is the terminal program which has the correct
colours. If I disable the composite extension in an xorg.conf then this
also has messed up colours. Some sort of endian problem in the radeon
driver?
I also should add that in addition to this problem, there are a few
colour issues with radeon KMS. A lot of fixes have gone in, and it is
much better than it was, but last time I tried I was still getting this
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
ati/+bug/1052619 . If
I have this exact same problem, only I'm on 12.04. Pretty sure it was
fixed for me in 12.10 when I tried that, but I'd really like it fixed in
12.04. PowerPC iBook with b43 module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Krister, apologies for spamming your bug report, but I thought it was
probably worth adding that this occurs with every variant of ubuntu I
tried - Lubuntu, Xubuntu, Ubuntu (2D), Kubuntu. When connecting, the
wireless name is displayed under 'Wireless Networks' in the menu, but
disappears when it
The proper fix for this is at the kernel level (has anybody reported it
on the powerpc kernel mailing list?), but it is also caused by
snd_powermac being liberally modprobed when it shouldn't be. The casper
script /scripts/casper-bottom/23etc_modules does it on the live cd and
then it is done
*** This bug is a duplicate of bug 1130857 ***
https://bugs.launchpad.net/bugs/1130857
** This bug has been marked a duplicate of bug 1130857
Some images have a blue tint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the mozilla bug with workaround
https://bugzilla.mozilla.org/show_bug.cgi?id=844436 .
** Bug watch added: Mozilla Bugzilla #844436
https://bugzilla.mozilla.org/show_bug.cgi?id=844436
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=844436
Importance:
This bug https://bugzilla.mozilla.org/show_bug.cgi?id=817356 has just
popped up on the debina mailing list. It appears to contain a patch for
this problem?
** Bug watch added: Mozilla Bugzilla #817356
https://bugzilla.mozilla.org/show_bug.cgi?id=817356
--
You received this bug notification
I think this is fixed for me too in 19, although I haven't yet looked
into it closely like I did above. I have a new problem though with some
pictures not having the correct colour (a blueish hint). Sigh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I think this is fixed for me too in 19, although I haven't yet looked
into it closely like I did above. I have a new problem though with some
pictures not having the correct colour (a blueish hint). Possibly this
bug https://bugzilla.mozilla.org/show_bug.cgi?id=844436 for any PowerPC
users who
I've been through old versions of firefox and the last good version was
the final release of firefox 17. I'll attach a screenshot.
** Attachment added: Firefox 17 with good font rendering
This is hopefully going to be a duplicate of this bug
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1097763 . Will
wait and see if Firefox 19 fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Same again, but full hint
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1105328/+attachment/3521110/+files/full-hint.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: reKong and Firefox with slight hint
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1105328/+attachment/3521109/+files/slight-hint.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm also seeing poorly rendered faults. It is very noticable on certain
sites, for example the ubuntuforums.org site. I'll attach some
screenshots. I've done fresh installs and tried different derivatives,
played around with the font settings etc, but I can't cure it. The
suggestion in post #2
It is only when you take a screenshot that you can appreciate the
difference between the two browsers! All the text in reKonq is so much
clearer. Even the web address is rendered better!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Medium hint and no sub pixel rendering
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1105328/+attachment/3521169/+files/medium-nosub.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: No hinting and no sub pixel rendering
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1105328/+attachment/3521170/+files/nohint-nosub.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Under the medium hint +no sub pixel setting both Firefox and rekonq seem
to display the same. All the other pictures are different. But my eyes
are shot now so I could be seeing things!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I posted a bit of a hacked solution to this here
http://ubuntuforums.org/showthread.php?t=2083770
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989477
Title:
Unity launcher does not re-appear when
Commits 3a3dd0186f619b74e61e6f29dddcaf59af7d3cac and
26b0d14106954ae46d2f4f7eec3481828a210f7d came in at 3.5.0-17-26 so they
were indeed the cause of this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Greg, can you get a photo of the error message?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
powerpc: Fixing recursive fault but reboot is needed!
To manage notifications about
@John thanks that's another confirmation of this bug. Unity/compiz
won't work with the fbdev xorg driver (...or more correctly it is
supposed to work with llvmpipe, but there are still issues). If you
want to try KMS which may work with unity then you can define an
xorg.conf like I did
This is obviously (and always has been) a duplicate of bug 1066435 .I
don't know why you were told to create a new bug, it is wasting your
time and others. The workaround is here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066435/comments/62
--
You received this bug notification
*** This bug is a duplicate of bug 1066435 ***
https://bugs.launchpad.net/bugs/1066435
** This bug has been marked a duplicate of bug 1066435
powerpc: Fixing recursive fault but reboot is needed!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I see the commits mentioned in post 64 are in the latest kernel
(3.5.0-18.29) so that should solve some people's sound problems. I
still can't get sound though, I'm wondering if the relevant bit of code
just hasn't been written yet (something to do with the fabric layout
module?). For me
Yeah I'm pretty sure now it's snd-powermac causing the problem.
I don't know if Colin Watson is still monitoring this bug, but snd-
powermac is force loaded on the live ISOs in /etc/modules. It is also
loaded in hw-detect in discover-mac-io.sh (and the other sound modules
blacklisted) - the
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
powerpc: Fixing recursive fault but reboot is needed!
To
Bug 1066435 is what I referred to in post 24. Turns out it was a
problem with the snd-powermac module. 2blue, I think you just needed to
use ctrl-alt-f1 to get to a command login prompt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Greg, where you are getting that error from in the bug report? The
second lot of logs in that bug report (1067899) are not even PowerPC!
Something I did notice though was SMP NR_CPUS=4 which is surely a
problem since we all have 1 CPU?!? Btw Walter, the non-SMP kernel was
removed in 12.04.
Can
Am I being thick, but the second lot of logs appear to be from an
entirely different computer i.e. an intel one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067899
Title:
ubiquity fails
I probably should clarify post 59 in that I have no idea what NR_CPUS
stands for. It is probably just a poorly chosen variable name and
MAX_NR_CPUS would be more appropriate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Greg, have you tried removing snd-powermac from /etc/modules? This
appears to let me boot okay. Also remove the sound modules from
/etc/modprobe.d/blacklist.local.conf or delete the whole file to load
new sound modules.
--
You received this bug notification because you are a member of Ubuntu
Can people try out the boot parameter:
snd-powermac.blacklist=yes
as a fix for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
powerpc: Fixing recursive fault but reboot is
No I couldn't get alsamixer to load, although my whole 12.10 system is a
wreck at the moment (my doing probably). I've never really had to look
into sound modules before, it has always just worked. I occasionally
skim read the powerpc developers list and I remember reading something
about some
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
powerpc: Fixing recursive fault but reboot is needed!
To manage
In my experience of this bug the problem doesn't show on logs. What I
mean by this is that the failed boot does not get logged at all, even
when I turn off caching.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christopher, I don't know why you are commenting on this bug. You are
not part of the kernel team and you are certainly not helping.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug 1066435 is the latest problem as referred to in post 20.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040526
Title:
Graphics dithered on Desktop image
To manage notifications about this bug
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
powerpc: Fixing recursive fault but reboot is needed!
To manage
The title of this bug should be changed as it has nothing to do with the
debian installer. It applies equally to a live ISO as well as an
installed system that is updated to the latest kernel.
Don't waste your time with single/recovery modes. The only way I have
been able to boot is to force a
The problem started in 3.5.0-17-26
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066435
Title:
Debian-installer powerpc recursive fault
To manage notifications about this bug go to:
The above is now all academic since the current kernel boots to an oops
and instruction dump. The only way to get the kernel to boot is by
forcing a 32 bit depth on radeonfb. There is no way to get radeon KMS
(and consequently the radeon xorg driver) working as far as I can see.
--
You
There seems to be a new problem - the kernel is currently screwed when
using KMS. It won't even boot. I think this is the problem you were
hitting 2blue. A serious regression just at the end of testing. I
don't think 12.10 should be released in this state.you can only
stretch workarounds
Nvidia cards will also have this problem when they turn of KMS (nomodeset or
nouveau.modeset=0) . At present it is likely to be a lot worse for them; they
will possibly only have 16 colours due to the limitations of the openfirmware
framebuffer. To solve this you will have to build back in
Nvidia cards will also have this problem when they turn off KMS (nomodeset or
nouveau.modeset=0) . At present it is likely to be a lot worse for them; they
will possibly only have 16 colours due to the limitations of the openfirmware
framebuffer. To solve this you will have to build back in the
Attached is a patch for yaboot-installer. It shows how easily this bug
could be fixed on an installed system by just using the vt.handoff=7
boot parameter (the same as Grub2 does). It also creates a recovery
option (the same as Grub2). This is therefore a low risk solution to
the problem.
The
@gregfaith if you want to use the radeon modules then you need to
disable the radeonfb framebuffer. If you don't do this then the radeon
modules don't do anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also, you haven't turned off just 3d acceleration, but ALL acceleration
from what I understand. To turn off 3d you'd have to disable DRI or
turn off AIGLX so that the software rasteriser is used. Something like
that anyway. I think your problem is possibly EXA related, but FYI if
you wish you
I have described the problem:
I'm on PowerPC and the 'hd0' I think should be just 'hd' (the
openfirmware devalias).
hd0 is wrong on PowerPC. It doesn't work. It should be just hd.
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Confirmed
** Description changed:
Hi, in my
Also, the current setup (particularly in quantal) produces unnecessarily
long and complex grub.cfg files. It makes it harder for the user to
understand. I think that is also a valid bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Ron thanks that confirms my problem in that the radeon card is not
detected and the Xorg server is not starting. It seems for you,
additionally, the radeondrmfb is not working correctly (hence the blank
screen).
@2blue thanks for trying to help out, but those logs have nothing to do
with this
** Tags removed: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058753
Title:
Radeon driver nolonger works on PowerPC without drm
To manage notifications about this bug go to:
For my new suggestion on how to fix this, see the kernel mailing list
thread https://lists.ubuntu.com/archives/kernel-
team/2012-October/022270.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's probably worth pointing out that you had to define an xorg.conf
because you got No devices detected in the Xorg.0.log. A similar
problem to what is currently happening to some (all?) radeon cards with
PowerPC at the moment since the latest update to the radeon driver - bug
1058641 .
--
You
@2blue I don't understand. Either you have mis-typed or there is
something weird happening with your foreign keyboard.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058641
Title:
No devices
@2blue, the boot parameter is 'video=ofonly', not offonly. The radeon
xorg driver will only work in 12.10 on PowerPC if you disable the
radeonfb framebuffer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please post your Xorg.0.log (in the /var/log directory) when using the
video=ofonly parameter.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058641
Title:
No devices detected radeon regression
To
Maarten, thanks for the comment, although I am not sure I follow it (!)
I know UMS has been dropped. I know it is never coming back. And I'm
not suggesting for one minute that it should (the last version of radeon
with UMS was largely broken from what I can gather).
I just need confirmation
A lot of the Apple PowerPC users will be using a radeon 9200 card or
something similar. It is probably worth pointing out that there has
been a kernel release note about these cards for a long time now:
On systems with an ATI Radeon 9200 graphics card the system will boot
to a black screen. As a
@wxl and lars. You are not understanding this bug report.
video=radeonfb:1024x768-32 etc is using the fbdev driver. It is not
using the radeon xorg driver.
If you are on PowerPC and you want to test for this bug then you need to
turn off radeonfb using the video=ofonly (or video=radeonfb:off).
@wxl you've provided a lot of logs there, but have you actually looked
at them youself? I haven't read all the posts here, but it is fairly
clear to me that you have a different problem to the original poster.
But, just to be sure, have you tried turning off the splash screen? On a
PowerPC
Just to correct my post #55, since on the logs nouveaufb looks like it
is loading fine for you then you can use the fbdev driver with that.
All you need to do is create an xorg.conf that specifies fbdev (don't
use the nomodeset parameter). If you still get 8 bit graphics then you
need to increase
Note, in all the logs I've disabled the radeonfb framebuffer (still
built in on PowerPC) to allow KMS. You do this either via the
video=ofonly or video=radeonfb:off boot parameters on PowerPC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Another thing that is possibly worth a mention is if I don't have the
line:
BusID PCI:0:16:0
then the computer seems to freeze. (Obviously the value you write is
computer dependant)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In the 12.04 Xorg.0.log I have the line
[39.624] (II) RADEON(0): Color tiling enabled by default
If it was using KMS then it should be (*I think*) something like ths:
[98.582] (II) RADEON(0): KMS Color Tiling: disabled
[98.582] (II) RADEON(0): KMS Pageflipping: enabled
This is why
*** This bug is a duplicate of bug 1044180 ***
https://bugs.launchpad.net/bugs/1044180
** This bug has been marked a duplicate of bug 1044180
Screen Freeze on Bootup - Lubuntu 12.10 PPC Alternate Aug 30 Build
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Testing the quantal daily/live ISOs I've noticed a regression with the
radeon driver. The last ISO I tested was from the 19th of Sept and that
was fine. Yesterdays live/desktop ISO (28/9/2012) fails to start the
Xorg server. It reports that no devices are detected.
** Attachment added: No xorg.conf
https://bugs.launchpad.net/bugs/1058641/+attachment/3355290/+files/Xorg.0.log-no-xorg-conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058641
Title:
No
** Attachment added: With xorg.conf
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058641/+attachment/3355291/+files/Xorg.0.log-with-xorg-conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note, there is a new bug when using KMS - see bug 1058641 . The kernel
config can't be now changed until that is sorted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040526
Title:
Graphics
Just for completeness I'll add the Xorg.0.log using the previous version
of the ati/radeon driver. It boots fine without any xorg.conf.
** Attachment added: Xorg.0.log-6.99.99~git20120713.6ef1ad6a-0ubuntu1
Public bug reported:
Hi, I'm trying to find out the best radeon setup for PowerPC in quantal
and need some advice! The PowerPC kernel is currently setup with KMS
enabled, BUT the legacy framebuffer radeonfb is still built in.
Although this is obviously not an ideal setup it seemed to work okay
Under 12.04:
dmesg | grep drm
[ 38.849798] [drm] Initialized drm 1.1.0 20060810
[ 39.102286] [drm] radeon defaulting to kernel modesetting.
[ 39.102301] [drm] radeon kernel modesetting enabled.
** Attachment added: 12.04 default Xorg.0.log
** Attachment added: 12.10 Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1058753/+attachment/3356097/+files/Xorg.0.log-default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looking at the various logs that are spread out over the various bug
reports I'm guessing that under 12.04 the radeon driver was using UMS
despite it saying it was using KMS. Once somebody with expertise can
confirm this then we can push to have the kernel config and PowerPC boot
message updated
I've also asked the X people in bug 1058753 if they can confirm what is
going on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040526
Title:
Graphics dithered on Desktop image
To manage
** Description changed:
Hi, I'm trying to find out the best radeon setup for PowerPC in quantal
and need some advice! The PowerPC kernel is currently setup with KMS
enabled, BUT the legacy framebuffer radeonfb is still built in.
Although this is obviously not an ideal setup it seemed
Still present in quantal, although the search fs-uuid is now more
complicated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048763
Title:
grub-mkconfig/probe gives incorrect device name on
@Ron please ignore the comments I made about modelines in post 29. The
10-monitor.conf you have in post 16 should work under KMS too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044180
Title:
1 - 100 of 303 matches
Mail list logo
