04F3:3186 Touchpad as
/devices/platform/AMDI0010:03/i2c-0/i2c-
MSFT0001:00/0018:04F3:3186.0001/input/input7
This as you may gather stops my trackpad from working and they have suggested I
visit here and ask for
any help!
All the best - Harry
--
You received this bug notification because you
I can confirm that rolling back to linux-firmware=1.173.12 solves the
issue with Kernel: 5.3.0-40-generic x86_64.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1865130
Title:
And... spoke too soon. It happens under xrender as well. Shorter
freezes, frequency is the same.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1811159
Title:
temporary freeze under opengl,
Public bug reported:
Several times an hour, usually when switching focus from one window to
another, all but the mouse will stop changing for a few seconds to a
minute or so. If a video is playing the sound will proceed as if normal
but the screen will not change. The shape of the mouse will
nouveau :01:00.0: bus: MMIO read of FAULT at 10ac08 [ IBUS ]
nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 [ IBUS ]
4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are
comment #39 fixed it for me
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594
Title:
[regression] compiz crashes after Mesa upgrade
To manage notifications about this bug go to:
I'm seeing the exact same problem as Phillip Gemmell in post #243.
When trying to update fglrx with the wily-proposed versions I get the
message "Release 'wily-proposed' for 'flgrx-*' was not found".
This is all happening on a fresh install of 15.10.
--
You received this bug notification
Is this issue ever going to be fixed?
Or no one cares anymore about older Ubuntu versions? 12.04 was supposed
to be LTS!
These issues should have not been neglected, nor allowed to happen in
the first place.
Before that specific update, which i suspect is this one: xkb-data:amd64
Public bug reported:
This problem has plagued me for a few years across different laptops
and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
15z running Ubuntu 14.04 LTS.
It typically starts after I have used the chat or call feature in gmail,
by clicking on the phone icon
This problem happens 'out of the box' using nothing more xubuntu trusty
iso installed on two systems, one running virt-manager and the other
hosting vms. So far, so good.
To reproduce: try a standard xubuntu amd64 install on a vm guest using
qxl as the video driver and spice as the display
Installation has finished. ou can continue testing ubuntu now,
(should be 'You' and 'Xubuntu'.The two buttons are titled 'Continue
esting' and 'Restart ow'.The icons on the home screen have changed
to 'rash' 'ile system' 'ome' nad 'Install ubuntu 14.0'.
Looks to be a strange bug to
If the graphics drivers on the system running spice viewer are relevant,
it's the nvidia 304-updates. I mention this because the nature of the
'visual static' or 'visual artifacts' seems to change when moving from
one to another multi-head monitor. However the missing letters remain
unchanged
On 04/02/2014 10:36 PM, Christopher M. Penalver wrote:
Michal Suchanek / Harry Coin, thank you for your comment. So your hardware
and problem may be tracked, could you please file a new report by executing
the following in a terminal:
ubuntu-bug xorg
Please ensure you have xdiagnose
As I use xubuntu, (standard ubuntu is way too 'heavy' for our purpose)
is there a version from that world you can suggest? Whatever the
regular ubuntu results it won't help me.
On 04/03/2014 08:50 PM, Christopher M. Penalver wrote:
Harry Coin, could you please test for this with the latest
** Bug watch added: Red Hat Bugzilla #805902
https://bugzilla.redhat.com/show_bug.cgi?id=805902
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1301722
Title:
Mouse Scroll Wheel not working
again.
Seems to be an evdev Bug, see solved Fedora Bug:
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=805902
Michal Suchanek / Harry Coin, thank you for your comment. So your hardware and
problem may be tracked, could you please file a new report by executing the
following
Still broken in saucy.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1039523
Title:
Public bug reported:
Description:Ubuntu 12.04.4 LTS
Release:12.04
I run update on Ubuntu 12.04 64Bit on 2014-03-07, and after restarting
my pc, the keyboard volume wheel doesn't adjust the volume in Ubuntu OS
anymore.
Keyboard is Dell X295D Multimedia USB Keyboard (Greek)
I can
Public bug reported:
crash on startup
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xorg 1:7.7+1ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for
perfectly fixed.
Thank you very much
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1187500
Title:
[Saucy] Unity is slow on Intel graphics
To manage notifications about this bug go to:
I found that doing:
mkdir ~/shouldhavebeendoneatcanonicalalongtimeago
cd ~/shouldhavebeendoneatcanonicalalongtimeago
apt-get source xserver-xorg-input-evdev
apt-get build-dep xserver-xorg-input-evdev
http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/log/
download and unpack the tar at
** Summary changed:
- Mouse Scroll Wheel not working
+ Mouse Scroll Wheel not working in spice vm guests
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/1039523
Title:
Public bug reported:
can't set desktop background
no background at all
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xorg 1:7.7+1ubuntu4
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
** Package changed: xserver-xorg-video-nouveau (Ubuntu) = nvidia-
graphics-drivers (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1037896
Title:
Starting Firefox
Nvidia-graphics-drivers (nvidia-current) do not work with xserver_1.13 branch
if a 3d desktop session is selected.
Also when using a 2d desktop (like gnome classic), you cannot use firefox or
thunderbird ATM.
Not even the latest stable nvidia drivers (304.37) work.
--
You received this bug
Confirming this issue.
Workaround goes by downgrading libxfont1 to the previous version (1.4.4-1).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxfont in Ubuntu.
https://bugs.launchpad.net/bugs/992745
Title:
X doesn't load in Quantal,
@Seth
Thanks for the driver on post #466. for over a year now I've been using
the imps hack in /etc/modprobe.d
With this, I am even now able to use touchpad indicator as it correctly
sees the touchpad as a touchpad and not a ps2 mouse. Thank you!!!
I'm running Ubuntu 11.04 on an Acer TimelineX
** Also affects: touchpad-indicator
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/550625
Title:
Alps touchpad is recognized
This is because your setup wasn,t able to load nvidia module, so nvidia-current
is not in use.
Instead your system did load nouveau module, the open source X driver.
See this:
[1284918.684] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please
check your
[1284918.684] (EE) NVIDIA:
Hi Bryce,
Unfortunately I no longer have the hardware I reported this bug on. You
might want to close it for now.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/764379
Title:
Public bug reported:
When hiding all visible windows and making them visible again (via
Ctrl+Alt+D) the titlebars of all windows are not clickable (i.e. when
clicking on the titlebar of a window, it actually becomes unfocused and
the click is picked up by the workspace desktop instead).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/880449
Title:
Problem with titlebar
To manage notifications about this bug go to:
My guess is there is a bug in the video driver that shows when the 3d
section of the video card is used.
Yup, you are 100% correct there.
I've forgotten about this bug - until you commented I got the
notification about it. I suffered from similar problem to you. But I
managed to resolve it by
Hi Seth,
One bad experience I have had since installing the patched kernel. After
countless good boots I decided to add the following lines to
/etc/tc.local in order to use switcheroo:
chown username /sys/kernel/debug/vgaswitcheroo/switch # change username
with your user name
echo OFF
Cool! it seems to be working for me. I even got a little taste of
the Plymouth boot screen which I haven't seen in a long time :)
I'll continue testing and let you know if I experience the B[lack]SOD.
On Fri, Aug 26, 2011 at 8:19 PM, josejuan05
727...@bugs.launchpad.netwrote:
I have 20
The latest cairo update (v. 1.10.2-6ubuntu3) fixes this issue for now as
it is a non gl build.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/821702
Title:
[Oneiric]
** Description changed:
The latest stable nvidia-current from Oneiric repos (280.13-0ubuntu1) hangs
up my system.
- This happens every time I start synaptic.
- Then, if I try to close it, it won't close until the system asks to force
quit it.
- Then, however, the whole system hangs (speeding
So I have done some more testing now.
NVidia proprietary drivers are really not compatible with libgl-mesa build
which is gl-enabled.
This is the issue.
Workaround:
I installed the latest cairo build from Oneiric official repos, that is a non
gl build (1.10.2-2ubuntu4).
Then I installed the
Public bug reported:
The latest stable nvidia-current from Oneiric repos (280.13-0ubuntu1) hangs up
my system.
This happens every time I start synaptic.
Then, if I try to close it, it won't close until the system asks to force quit
it.
Then, however, the whole system hangs (speeding up CPU).
If
You cannot remove that package.
The mesa package libgl1-mesa-dri depends on all three libdrm packages
(libdrm-intel1, libdrm-nouveau1a, libdrm-radeon1).
The main xserver (xserver-xorg-core) depends on those same three libdrm
packages (via libdrm2).
Thus xserver, drm and mesa are linked together.
Sorry to sound stupid, but I think there are many people affected by
this in layman terms, what's the status of this issue?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
I can confirm the nvidia-current_275-09-07-0ubuntu2 works with
mesa_7.10.3-0ubuntu1.
That first mesa 7.10.3 build does not break the 275.09 series nvidia-current.
The breakage was added to the later builds.
So now we need to remove the breakage from the newest mesa_7.10.3.
However,
@Seth I still can't seem to find the error message that I see on boot
freeze in the logs. I tired taking a photo of it. Maybe it'll help?
uname -a
Linux ClarifyUbuntu 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC
2011 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: screens of
@Seth You wouldn't know how to fix this would you? :)
I do worry about it though as i am constantly having to reboot many
times until I finally get into Ubuntu.
It's annoying as well as embarrassing around my Mac and Window using
colleagues. They think I'm an idiot for using Ubuntu... maybe I
Chris,
No, apt did not remove anything nor did suggest it.
I did the upgrade with synaptic, so nothing wrong about that (no errors).
There was only the notification to upgrade xorg-server to the version 1.10.2
first, which is a new dependency.
But as I mentioned, I downgraded the mesa back to
One more note.
The package libgl1-mesa-glx 7.10.3-0ubuntu1 breaks:
fglrx (= 2:8.850-0ubuntu1)
nvidia-173 (= 173.14.30-0ubuntu2)
nvidia-current (= 270.41.19-0ubuntu1)
However, as I said above, I use nvidia-current_275.09.07, which is the latest
stable in Oneiric official repos.
Thus the
Bryce,
I am sorry but I do not have apport installed.
I am using a very minimalistic setup.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/798007
Title:
[Oneiric] Latest mesa (7.10.3) breaks 3D
*** This bug is a duplicate of bug 798007 ***
https://bugs.launchpad.net/bugs/798007
** This bug has been marked a duplicate of bug 798007
[Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
--
You received this bug notification because you are a member of Ubuntu-X,
which is
There is another bug report on this very same issue:
Bug #798049
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/798007
Title:
[Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
To
Public bug reported:
Latest mesa upgrade from 7.10.2 to 7.10.3 breaks 3D capabilites.
Gnome-shell falls back to gnome-panel.
This happens in my setup with Nvidia graphics card and latest nvidia-current
(275.09.07) in use.
The .xsession-errors file gives this message:
@Seth, Does it matter that the error occurs before the drives are
mounted? I'm not sure it's actually saving the log when the error
occurs.
Either way, on the next occurrence, I'll send this log.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Seth, yeah I'm on natty. Can you help me identify the log you need? I'm
not sure which is relevant.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/727620
Title:
[Radeon HD
I just wanted to add that with the HD5650 on an Acer Aspire I have the
same issues. One thing that doesn't seem to get mentioned here much is
the vesafb. More than half the time I boot I get an error stating that
their was an error inserting vesafb. I sometimes also receive an error
stating that
Just an observation... In my dual boot environment (Windows7 and Ubuntu)
the longer I stay in Ubuntu without switching Windows the worse and more
frequent my video issues happen. Once I log into windows, even if just
for a minute, when I boot back into Ubuntu, I am then able to add a
monitor
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/764379
Title:
Partial screen
The excellent video of Lucazade shows clearly how gnome-settings daemon first
works, but is then killed.
It really may be that gnome-settings-daemon somehow is still hanging after
first login, but is killed after a new logout/login.
--
You received this bug notification because you are a
I can confirm the race situation is fixed with this new package in PPA.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
https://bugs.launchpad.net/bugs/649809
Title:
the session settings manager can try
It's been almost three weeks since my post. Any chance this issue could
get fixed soon?
After all the patch exists already so there's not much to do but to
apply and release it. This is easily solved but very important to us
because Xorg seem to update every now and then and when updated everyone
Public bug reported:
Nvidia proprietary dirvers in Natty repos (nvidia-current v. 260.19.29) do not
support the latest xserver 1.10 rc2 in Natty repos.
So please upgrade the nvidia-current to the latest beta (version 270.29) to get
the support for this X 1.10 rc2.
This driver is available from
This wish has been fixed with the upgrade of nvidia-graphics-
drivers_270.29-0ubuntu2.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in
I am still seeing this issue in 2:1.9.0-oubuntu7.3 using the NVIDIA
driver version NVIDIA-Linux-x86-260.19.12 or NVIDIA-Linux-x86-260.19.29
No wonder. I verified the issue exists still by doing this:
$ apt-get source xserver-common
$ zgrep -A2 -B2 650539 xorg-xserver_1.9.0-0ubuntu7.3.diff.gz
+
** Package changed: xorg-server (Ubuntu Natty) = xserver-xorg-input-
evdev (Ubuntu Natty)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/709977
Title:
Xorg crashed with
*** This bug is a duplicate of bug 709977 ***
https://bugs.launchpad.net/bugs/709977
Yes it is the bug # 709977
Backtrace:
[11.120] 0: /usr/bin/X (xorg_backtrace+0x26) [0x45be16]
[11.120] 1: /usr/bin/X (0x40+0x59c9a) [0x459c9a]
[11.120] 2: /lib/libpthread.so.0
*** This bug is a duplicate of bug 709977 ***
https://bugs.launchpad.net/bugs/709977
This segfaulting bug has been fixed with a new evdev driver.
Old driver: 2.6.0-1ubuntu1
New driver: 2.6.0-1ubuntu2
Bug #709977
** This bug has been marked a duplicate of bug 709977
Xorg crashed with
I very much doubt this is a bug in xorg-server (xserver 1.9 series).
The crash ([ 11.710] segmentation fault at address 0x1010) happens very clearly
with Nvidia graphics cards and with nvidia-current binary drivers.
In fact with nvidia, the system will not even boot to gdm.
Also using wireless
With NVidia GTX 285, Natty-64 bit, workaround #68 did really fix this theme
issue.
Confirming, it is a gdm bug.
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
Yes I can confirm this error occuring with the nvidia-current_270.18 and
xserver 1.9.99.901 (1.10 rc1).
GLX module shared object (libglx.so) does not support server ABI and loading
fails.
This happens even if IgnoreABI is used.
If IgnoreABI is not used in xorg.conf, gdm and x are not loaded
Anyway this drivers offers a preliminary support for xserver 1.10, not
full support.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/703688
Title:
[Natty] Need X-server
The fix has been released in Natty:
nvidia-current_260.19.29-0ubuntu1
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
Public bug reported:
In Natty repos we have the version nvidia-current_260.19.21.
However Nvidia Corporation has raised the status of the version 260.19.29 to
stable.
This has been published on 2010.12.13.
Users can find the stable version also in the Xorg-Edgers PPA.
Here are the release
And not even driver-by-driver basis, more like by graphics card basis.
For me (with Nvidia 285 GTX) nvidia-current has always worked OK.
Now I am using the latest beta from X-Updates (X-Swat): 260.19.26-0ubuntu1
And yes, I use the line gfxpayload=keep in my /etc/grub.d/00_header
resulting a
*** This bug is a duplicate of bug 683775 ***
https://bugs.launchpad.net/bugs/683775
** This bug has been marked a duplicate of bug 683775
Natty Alpha 1, i915 has blank screen after boot
* You can subscribe to bug 683775 by following this link:
I'm also getting this error 1 out of 5 times during suspend on Maverick (kernel
2.6.35.4). Hardware: laptop: HP Compaq 6830s with ATI video.
regards,
Harry
--
Error shown on screen after resume with radeon card
https://bugs.launchpad.net/bugs/618253
You received this bug notification because
I have not seen any instability issues with the new beta driver 260.19.06 in my
maverick 64-bit setup.
The sluggishness issue is completely gone and also gnome-shell works fluently
now.
Please pay attention to that Brandon Snider has uploaded this new beta driver
(nvidia-current) in X Updates
Yes I confirm what maba just wrote in comment #22.
I only downloaded the packages nvidia-current and nvidia-settings from that PPA.
Then I installed them with dpkg in terminal.
There is no need to change sources.list that way.
Anyway, the driver runs well in maverick too. The PPA itself is for
Now that we have a fix for this bug, could perhaps Alberto Milone build this
into maverick's repos.
This sluggishness issue is after all quite an annoying one.
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received
NoahY,
Like Daniel wrote (comment 10), this beta driver does not yet contain that bug
fix.
It will be included into the next version, perhaps into the stable 260 series
driver.
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Invalid
--
Incompatibility with the new X.org 8.0 ABI
https://bugs.launchpad.net/bugs/630105
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
And that might be an update to the newly released beta driver 260.19.04.
See: http://www.phoronix.com/scan.php?page=news_itempx=ODU3NQ
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received this bug notification because
If you want to test this beta driver 260.19.04,
you will find it here (X-Updates):
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received this bug notification
Could perhaps Robert Hooker or Alberto Milone comment on this.
The development of the kernel 2.6.36 is quite far now and a number of
interested users might want to try it in Maverick.
--
Malformed patch, package nvidia-current 256.53-0ubuntu1 failed to
install/upgrade: nvidia-current kernel
Yes I can confirm there is a regression issue with xserver 1.9 (at least
up to 1.9.0-0ubuntu4) and nvidia-current (at least up to 256.53).
This is most prominent when scrolling in some applications.
I have found that synaptic is a very good example of this one.
Scrolling is severely influenced
Just out of curiosity,
could this bug have something to do with desktop sluggishness that was observer
to be caused by libcairo?
The libcairo code was temporarily changed in order to overcome the
incompatibility with nvidia-current back then.
See the bug #605979
And one more thing.
This bug
Opengeek,
The new nvidia-current_256.53 is not incompatible with the new xserver 1.9.
What driver version are you using?
If not v. 256-53, do an upgrade.
--
Incompatibility with the new X.org 8.0 ABI
https://bugs.launchpad.net/bugs/630105
You received this bug notification because you are a
An addition,
the link Opengeek provided in the description is outdated and way too
complicated.
It must also be noted that it is for Lucid (10.04) and not for Maverick (10.10).
Experienced users may use terminal and sudo apt-get to install
applications and drivers, but for beginners it is safer
Brian, this bug (X won't start since 1.9 update, no screens found) has been
fixed and the fix has been released.
I can confirm nvidia-current_256.53 fixes this bug.
The performance issue is another bug and that one is dealt elsewhere,
see the bug #629910
--
nVidia card : X won't start since
*** This bug is a duplicate of bug 616023 ***
https://bugs.launchpad.net/bugs/616023
** This bug has been marked a duplicate of bug 616023
nVidia card : X won't start since 1.9 update, no screens found
--
nVidia drivers in Maverick do not work due to ABI level
*** This bug is a duplicate of bug 616023 ***
https://bugs.launchpad.net/bugs/616023
** This bug has been marked a duplicate of bug 616023
nVidia card : X won't start since 1.9 update, no screens found
--
[Maverick] Please update nvidia-current to 256.53
*** This bug is a duplicate of bug 616023 ***
https://bugs.launchpad.net/bugs/616023
** This bug has been marked a duplicate of bug 616023
nVidia card : X won't start since 1.9 update, no screens found
--
NVIDIA driver not loadable
https://bugs.launchpad.net/bugs/629451
You received this
Tim Jones and Randall Ross,
The beta freeze is over and new packages are being built in Launchpad all the
time.
So new stable nvidia-current_256.53 will soon find its way there.
But,
I do not expect it to resolve any of the sluggisshness issues, though.
There are not too many changes in the
Hi Randall,
You are correct about the new issue of 2D and 3D acceleration sluggishness.
The 2D sluggishness in scrolling for instance can clearly be seen like this:
open synaptic and try to scroll the package list with mouse.
However, this may not be a driver issue after all.
At least NVidias
Aaron,
Thank you for your heads up. I made an error in my comment #69 above.
What I wanted to say was that nvidia-current worked very fluently with xserver
1.8 regarding any scrolling.
This is true for both Lucid Lynx (10.04) and Maverick Merkaat (10.10).
And once again, immediately after
Alberto,
please build the deb packages from the new stable version 256.53 (publiced
31.8.2010).
--
nVidia card : X won't start since 1.9 update, no screens found
https://bugs.launchpad.net/bugs/616023
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
So NVidia has now publiced a new driver pre-release 256.52.
That one does support new video ABI xserver xorg 8, which is required by the
xserver 1.9.
Now this will fix this bug. It is no more needed to put ignoreAbi text into the
xorg.conf to bypass this issue.
So, please do build a
Jeff,
Only Nvidia folks know that, like Aaron Plattner. Perhaps he could
comment this.
However, by applying the IgnoreAbi option we can make maverick boot again.
But there are a lot of other issues with the recent nvidia-current_265.44
drivers, that need to be fixed.
So this is only a partial
Aaron,
Thank You for the news.
About the driver compatibility.
I did mean the same issue we see when we compare the driver performance on
xserver 1.8 branch:
with nvidia proprietary drivers any scrolling action is very fluent, but with
open source ati drivers it certainly is not.
Now I see
*** This bug is a duplicate of bug 623399 ***
https://bugs.launchpad.net/bugs/623399
This is a duplicate bug report to the bug #623399
** This bug has been marked a duplicate of bug 623399
nvidia drivers fail to start in Maverick X11
--
nvidia drivers fail to start in Maverick X11
Hi Jeff Craig,
NVidia proprietary drivers (nvidia-current) do not accept the new ABI, which is
required by the xserver 1.9 branch.
In order to avoid this you need to add the following lines to your xorg.conf.
Section ServerFlags
Option ignoreABI True
EndSection
Nvidia-settings actually should not set that option.
The option IgnoreAbi is in use now with xserver 1.9 because there are no
nvidia drivers around to fully support this new xserver.
So, IgnoreAbi is a workaround, not a fix.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New =
Vipul,
Did you manually add the following necessary lines to the xorg.conf
Section ServerFlags
Option ignoreABI True
EndSection
And, do you use the latest nvidia-current_256.44-0ubuntu1 drivers?
--
When booting with Nvidia propriety drivers system hangs indefinitly while
booting
1 - 100 of 150 matches
Mail list logo
