Actually, the only way I fixed this issue on my pc was to use LILO with the
lba32 option, by creating an appropriate /etc/lilo.conf file(in this case,
since on my pc there was also Opensuse, I edited the /etc/lilo.conf file
created by Yast2 to make it work with Ubuntu's liloconfig, however it is
The reason why I reported the bug recently is that the AGP slot of my
second-hand pc didn't work anymore, so I had to revert to my old
computer with a 28-bit lba, which of course had the same problem as
before, since I have a 160GB-large HD. Furthermore, a friend of mine
also had this problem on hi
Public bug reported:
Binary package hint: grub
When you have a computer whose motherboard has only 28-bit lba support,
if you use an hard disk of more than 128 GB and GRUB tries to read a
sector whose sector number is higher than the highest sector number you
would have using a 128 GB hard disk (
The best thing to do is actually reading the manual of the motherboard,
or the new features introduced with the BIOS update, if you updated the
BIOS.
--
grub fails to boot on computers having a 28-bit lba and an hard disk larger
than 128 GB
https://bugs.launchpad.net/bugs/279307
You received thi
No regressions on the 13.11 beta V9.4 drivers (version
2:13.250-0ubuntu1) as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid ATI/Intel GPU syst
@naught101: this bug report originally was referring to Ubuntu 12.10 and
was later extended to Ubuntu 13.04, however I don't think it has yet
been extended to Ubuntu 13.10 (it is not mentioned in the table above).
Anyway, the bug is similar to the one I reported, but by watching the
Xorg log file,
@naught101:I would suggest using the default intel drivers and mesa version
with the default kernel as well, I think the new drivers should be used with
the new kernel you were using, this is why I recommended them in the first
place.
If you still have this bug with all the packages from the def
Filing on AMD's bug tracker is the right thing to do, if you want you
can also file here on Launchpad (try using Apport/ubuntu-bug).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low
@Romano Giannetti:The bug treated here is related to the binary Catalyst
drivers, if you have the bug you mentioned with the open source drivers
of the Ubuntu repositories you can file a new bug here on Launchpad, you
can also report bugs about open source drivers on
https://bugs.freedesktop.org/.
@kpijarski: The bug niniendowarrior talked about is this
http://ati.cchtml.com/show_bug.cgi?id=848
I don't know how to solve your problem. I'm using the fglrx drivers version
13.11 beta version 6 (2:13.250-0ubuntu1 on Ubuntu 12.10 64 bit) and only the
secondary monitor to have its full resolutio
@niniendowarrior:if you want to try the new dynamic power management on the
open source drivers you should add
radeon.dpm=1
to the
GRUB_CMDLINE_LINUX_DEFAULT
line on the /etc/default/grub file and then run
sudo update-grub
as specified on https://help.ubuntu.com/community/RadeonDriver
You should
If you have the dual head bug with the drivers provided by the fglrx or the
fglrx-updates package, the command to file a new bug should be
ubuntu-bug fglrx
(or fglrx-updates)
but if you are experiencing this bug only with the drivers downloaded from
AMD's site then I think you should not file a n
You can find them using this link:
http://www2.ati.com/drivers/linux/amd-catalyst-13.9-linux-x86.x86_64.zip
Sometimes AMD allows downloading their drivers before the official page is up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
As expected, these new drivers (whose version is the same:
2:13.200-0ubuntu1) show no significant regressions regarding the solved
bugs I talked about. Is the dual head situation the same on Ubuntu
13.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Is there a bug regarding this dual head problem on Ubuntu 13.04? If not,
it could be useful to file a new bug so that Ubuntu developers (and
hopefully also AMD's ones) are correctly informed about this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
In case someone was wondering, no regressions on the 13.12 drivers
(version 2:13.251-0ubuntu1) either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybri
The result is
Description:Ubuntu 12.10
Release:12.10
xorg-driver-fglrx:
Installato: (nessuno)
Candidato: (nessuno)
Tabella versione:
fglrx-kernel-source:
Installato: (nessuno)
Candidato: (nessuno)
Tabella versione:
fglrx-amdcccle-updates:
Installato: (nessuno)
Candidat
No significant regression also with the 13.11 beta drivers (version
2:13.200-0ubuntu1), as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid
I tried the new 13.2 beta driver from AMD (2:12.100-0ubuntu1) and they work
correctly with the Intel driver from 12.10 repository (2:2.20.9-0ubuntu2)!
I think it is important to verify whether this problem is finally solved by the
new 13.2 beta driver also for other users.
--
You received this
As a side note: with the 13.2 beta driver the integrated GPU too works fine
without having to apply the patch for direct rendering.
It must be verified, however, if this is true also for systems where the patch
was never applied.
--
You received this bug notification because you are a member of
I think the message is not a real problem, but some kind of workaround.
My system too give me this message when I switch to the discrete GPU:
sudo amdconfig --px-dgpu
PowerXpress info: Diagnostic output from /usr/lib64/fglrx/switchlibglx:
update-alternatives: attenzione: viene forzata l'installazi
In the 13.2 beta 6 drivers (2:12.100-0ubuntu1) the situation is more or less
the same as that with the beta 3 drivers, the periodic crashes of the Xserver
when using the iGPU are there as well.
However, I noted that with the 13.2 beta drivers (both version 3 and 6) XvBA
seems to be broken:
when
Yes, this is what I was trying to explain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx
upgrade
To manage not
For those who were wondering, the new Catlayst 13.1 driver apparently
still has this bug. However, those with PowerXpress 3.0 cards (Mobility
Radeon HD 5000 series, HD 6500M series cards and probably also HD 6300M
cards) and who were having the "this is a Muxless PX A+I platform, we
doesn't support
With Catalyst 13.2 beta7 (2:12.100-0ubuntu1) not much has changed (not even the
version number!), so to sum it up:
-2D and 3D acceleration is mostly fine with both the iGPU and dGPU (at least
Unity and some OpenGL appplications such as glxgears work correctly)
-XvBA seems to be broken (or the xvb
On my system the driver works fine both with dgpu and the igpu, excpet
for a bug which should be the same as Bug #1088220. Basically, when
using the iGPU some periodic crashes of the X server with subsequent Low
Graphics Mode are experienced. However, the main bug reported here seems
to be solved.
P.S.: the "amd13_2_betacrashdmesg" file contains the dmesg output for
one of the periodic crashes so that it is possible to verify if it is
the same issue as in Bug #1088220.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Public bug reported:
After installing the latest fglrx-updates package on Ubuntu 12.10
(fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was
present before AMD fixed switchable graphics on PowerXpress 4.0 cards
(such as my HD 6470M coupled with the intel HD Graphics 3000 of my intel
** Summary changed:
- Switchable graphics on 6470M (Powerxpress 4.0) not working again
+ Switchable graphics on 6XXXM (PowerXpress 4.0/Dynamic Switchable Graphics)
not working again
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
After installing the latest fglrx-updates package on Ubuntu 12.10
(fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was
present before AMD fixed switchable graphics on
I'm adding some information to this report (obtained using fglrx
2:9.000-0ubuntu3/fglrx_9.000-0ubuntu3_amd64.deb):
dmesg output(in the dmesgfglrx file)
Xorg log (in the Xorglogfglrx file)
lshw output (in the lshwfglrx file)
uname -a output (in the unamefglrx file)
fglrx package details given by dpk
When running
apport-collect -p fglrx-installer 1068404
I get the following output:
dpkg-query: nessun pacchetto corrispondente a fglrx-installer
Traceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 588, in
app.run_argv()
File "/usr/lib/python2.7/dist-packages/appor
apport information
** Tags added: apport-collected compiz-0.9 precise referred-by-support
running-unity ubuntu
** Description changed:
After installing the latest fglrx-updates package on Ubuntu 12.10
(fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was
present before AMD fi
apport information
** Attachment added: "BootLog.gz"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409528/+files/BootLog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Sw
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409529/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409530/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409531/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409532/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Ti
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409533/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Swit
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409534/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Swit
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409535/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409536/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409537/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409538/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Sw
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409539/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409540/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409541/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409542/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Ti
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409544/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1068404/+attachment/3409543/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Sw
These apport information was generated with Ubuntu 12.04.1 LTS Desktop
version for 64 bit architecture
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Switchable graphics on 6XXXM (Powe
I can confirm that the xserver-xorg-video-
intel_2.20.0-0~andrik1_amd64.deb from Nick Andrick's PPa is enough to
solve the issue with the fglrx-updates_9.000-0ubuntu3_amd64 from the
official quantal/restricted repository. The driver is working correctly
now, but the discrete GPU has to be used in o
The xserver-xorg-video-intel_2.20.0-0~andrik1_amd64.deb package is also able to
solve the issue with the fglrx drivers installed with the
fglrx_9.000-0ubuntu3_amd64.deb package (again, Unity works only with the
discrete GPU).
Thank you very much, Nick and Christopher!
--
You received this bug
Regarding the first part of the bug (Unity not working after installing fglrx),
this is a known bug (when using the integrated GPU after installing fglrx,
direct rendering has problems) which is now more apparent becuse it seems that
Unity 2d is no longer present on Ubuntu 12.10. There is a solu
regarding Unity not working after installing fglrx, the workaround is described
in step 2 of the first message of this thread:
http://ubuntuforums.org/showthread.php?t=1930450
I tried that myself and now Unity works even when using the integrated GPU with
fglrx installed.
Regarding the steps to
I can confirm that with the package xserver-xorg-video-
intel_2.20.9-0ubuntu2+andrik2_amd64.deb both the fglrx drivers from
fglrx and fglrx-updates packages from official quantal/restricted
repository work correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Nothing new with the 13.3 beta 3 drivers regarding this bug, as far as I
know (even the version is the same: 2:12:100ubuntu1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphi
The new 13.3 beta 2 drivers (still 2:12.100-0ubuntu1 !) behave more or
less the same as I written in the previous post about the 13.2 beta 7
drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10684
P.S.: since I reported this bug with Ubuntu 12.10 I think I'm going to
use it until this bug is solved, so unfortunately I cannot help those
who have Ubuntu 13.04 and are having issues with the X server different
from those I reported.
--
You received this bug notification because you are a membe
With the new 13.4 drivers (version 2:12.104-0ubuntu1) the situtaion is
the same as reported in my previous post about the 13.2 beta 7 drivers.
P.S.: @Nick Andrik: Even if late, I would like to thank you again for
your precious aid in solving this bug!
--
You received this bug notification becaus
P. P. S.: my message is late, your help was fast!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1068404
Title:
Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx
upgrade
To man
Here is the lsmod output, dmesg log and Xorg log for the XvBa crash
(modules, dmesgXvBAcrash and Xorglogcrash respectively) and the lsmod
output, dmesg log, syslog and Xorg log for the crash while restarting Xorg
with iGPU selected (modulesintel, dmesgintelcrash, syslogintelcrash and
Xorglogintelcr
This is correct. Regarding the crash when iGPU is selected, since it is similar
to Bug #1088220 I didn't report a new bug, but I can if you think it is useful,
regarding the bug with XvBA, I reported it as bug 789 on the unofficial ATI
Bugzilla, since the new drivers are apparently not available
Public bug reported:
While the previous benchmarks done with GNOME Disk Utility generated raw
data which were cached in ~/.cache/gnome-disk-utility/drive-benchmark
and were in a human readable form which could be easily parsed and then
analyzed with programs such as Libreoffice Calc, the new GNOME
To clarify the issue, I attach the cached raw data about my laptop's HDD.
ATA-TOSHIBA MK6476GSX-GS001C-81TEC0UJT was generated with
gnome-disk-utility version 3.0.2-2ubuntu7 on Ubuntu 12.04 Desktop 32-bit,
while TOSHIBA_MK6476GSX_81TEC0UJT.gnome-disks-benchmark was generated with
gnome-disk-utility
@Nick: I noticed that Freedesktop's bug 56494 affects a system based on AMD
Radeon HD 6550M which uses PowerXpress 3.0/Switchable graphics and not
PowerXpress 4.0/Dynamic Switchable graphics. It is likely that the bug is not
the same.
To clarify the version of PowerXpress supported by the variou
With the latest OpenGL 4.3 beta drivers (version 2:13.150-0ubuntu1)
there isn't any apparent regression regarding the three bugs I mentioned
in my previous posts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Basically the bug treated here (#1068404), the one similar to bug
#1088220 and the problem with XvBA reported as bug 789 on the unofficial
ATI Linux Driver Bugzilla are not present in the OpenGL 4.3 beta
drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
With Catalyst 13.6 beta drivers (version 2:13.101-0ubuntu1) again this
bug seems to be solved (as in previous versions), but also the two other
bugs I mentioned (the one similar to bug #1088220 and the one reported
as bug 789 on the unofficial ATI Bugzilla) are apparently corrected
too. Now, if ot
Apparently with Catalyst 13.6 beta drivers (version 2:13.101-0ubuntu1)
this bug is solved, could the other people experiencing this bug (except
for Nick) confirm this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I would like to point out that, since the bug was originally found on
Ubuntu Desktop 12.10 64 bit edition, I am still using this version of
Ubuntu to verify if it has been solved, so my report is about the state
of the bugs on Ubuntu Desktop 12.10. Users of Ubuntu 13.04 may still
find that some of
With the 13.8 beta drivers (version 2:13.200-0ubuntu1) there isn't any
apparent regression regarding the aforementioned three bugs on Ubuntu
Desktop 12.10 64-bit. What is the situation with Ubuntu 13.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
72 matches
Mail list logo
