I see this has been marked as an opinion. To clarify, the opinion is
this "one should not be able to break his Ubuntu system by installing a
package with apt-get"
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://
http://www.h-online.com/open/features/What-s-new-in-
Linux-2-6-34-1000122.html writes: "On some laptops equipped with both
onboard graphics and a separate graphics chip, the kernel can now switch
between the two and switch off whichever is not being used in order to
save power. 'VGA Switcheroo' cur
I tried installing the restricted driver for my ATI card on Lucid, and
then switching to Intel at boot time. The system was not able to bootup
until I removed the fglrx package.
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete => New
--
mesa doesn't work when fglrx is installed
I'm afraid I cannot test this, as I do not have a Matrox card anymore.
--
[RV280] 320x240 screen mode not supported
https://bugs.launchpad.net/bugs/183913
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-mga in ubuntu.
___
I've added a bug regarding graphics card _cold_ switch, which also turns out to
be broken on some systems.
See https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/505560
--
support graphics card hot switch
https://bugs.launchpad.net/bugs/312756
You received this bug notification because y
Public bug reported:
When I installed Ubuntu my system had an ATI graphics card. Once I got
to the desktop I used "System -> Administration -> Hardware Drivers" to
install a driver for it. Later I wanted to use an Intel graphics card,
so I disabled the ATI card from bios and enabled the Intel card
How did you kill it? My Lenovo Thinkpad T500 supports selecting graphics
cards from BIOS. So that is very close to selecting it on boot time,
right? Your bios doesn't support this?
--
support graphics card hot switch
https://bugs.launchpad.net/bugs/312756
You received this bug notification becaus
My bottom line is. It should atleast be possible to make video cards
work by switching the actual hardware or by toggling it from bios. I'm
ok with asking the user to install another driver when the new card is
detected. I'm not ok with asking the user remove one driver to make
another card work.
Did you know there is a bug for not being able to switch graphics card on the
fly.
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/312756
I do understand that getting that feature will take some time. However,
it is ridiculous that Windows users can switch their graphics card on
the
Errors with my Intel card might have been different from this bug.
However, I got rid of them by removing restricted ATI driver packages.
So, in case some of you have restricted driver packages installed for
other video cards, I'd try removing them for a while, and reporting
back, if this fixed the
Removing package xorg-driver-fglrx fixes the problem, so I assume the
problem is in that package instead.
** Package changed: xserver-xorg-video-intel (Ubuntu) => fglrx-installer
(Ubuntu)
--
glxgears fails in Karmic
https://bugs.launchpad.net/bugs/442574
You received this bug notification becaus
Needless to say (I hope), having drivers installed for one video card
should not break operation of another video card?
--
glxgears fails in Karmic
https://bugs.launchpad.net/bugs/442574
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installe
So what does a previously installed system do differently from a system booted
from the livecd?
Is it that the installation would detect the video hardware and do something
special based on that?
Are some driver left out, if the video card doesn't seem to be present?
--
glxgears fails in Karmic
I tried booting from the Karmic beta livecd, and glxgears worked fine.
See the attached xorg log file which I copied to a usb stick while being
in live system.
** Attachment added: "xorg log file from livecd boot"
http://launchpadlibrarian.net/33245052/Xorg.0.log
--
glxgears fails in Karmic
h
I'm on a Lenovo Thinkpad T500. My Xorg falls back to a generic vga
driver with the same error...
cybe...@eval:~$ cat /var/log/Xorg.0.log|grep "(EE)"
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Failed to load module "i810" (module does not exist, 0)
(EE) GLX error: Ca
I have the same problem with this card.
01:00.0 VGA compatible controller: nVidia Corporation NV44 [Quadro NVS 285]
(rev a1)
Subsystem: nVidia Corporation Device 029d
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at f600 (32-bit, non-prefetchable) [size=16M]
The confusion is my fault. At some point I just noticed I had been
testing on multiple systems. After that I wanted to find out whether or
not the bug was video card specific. It turns out to be such and Matrox
seems to currently have the error, so concentrating on Matrox in future
will probably ma
I made some tests with *Jaunty*, as that is what I happen to have
installed on my systems.
On Jaunty the bug does not exist for "ATI Technologies Inc Mobility
Radeon HD 3650"
On Jaunty the problem depicted in my screen shot from 2008-09-04 is
still relevant for "Matrox Graphics, Inc. MGA G400/G45
In that case I opt to test it with Karmic once it has been released, and
if it doesn't work I retest it with Karmic+1, when I happen to have that
at hand. I'm not going to take the risk that someone might not work on
it before Karmic, even if I tested it. The time when this gets fixed is
not that c
If I try it and it doesn't work, is someone going to fix it before
Karmic gets released? Otherwise I'd rather just test it later when I
happen to have the new version at hand.
--
[RV280] 320x240 screen mode not supported
https://bugs.launchpad.net/bugs/183913
You received this bug notification be
20 matches
Mail list logo
