** Tags added: valid-xorg-conf
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Thanks for confirming that the fix works. Closing as fixed.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Fix Released
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ubun
I have Gutsy in PC installed by dist-upgrade
There is no more errors!
thanks
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
** Changed in: xorg-server (upstream)
Status: Unknown => Fix Released
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
ouioui51, according to upstream, it is fixed as of xserver 1.3, which is
available in Gutsy.
Can someone test out one of the Gutsy tribe CD's (tribe 2 was just
released today), and see if the issue is still present?
** Changed in: xorg (Ubuntu)
Importance: Undecided => Medium
Status: N
Hi!
Is there any news about this bug?
Why it isn't confirmed?
Lot of people have the same problem in ubuntu feisty and debian etch.
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ub
Here's the xorg log from the previous message.
** Attachment added: "xorg log when I tried my Edgy xorg.conf in a fresh Feisty
install"
http://librarian.launchpad.net/7615197/Xorg.0.log.edgy
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
Y
I've had the same problem with Feisty - but no problem at all with TV
out in Edgy.
Here's the output of "dpkg -l nvidia-\* | grep ii"
ii nvidia-glx 1.0.9631+2.6.20.5-15.20 NVIDIA binary XFree86
4.x/X.Org driver
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary kernel
I have got the TV to work by specifying it in the same 'ServerLayout' section
as the default monitor.
i.e. I now only have one ServerLayout section.
This is a work around as I would much rather be able to invoke a separate
layout for the TV when I wish from the default monitor.
It is with this i
Thanks. It already is quite 'simple' however.
TV Device Section:
Section "Device"
Identifier "GeForce4 420 Go 32M TVOut"
Driver"nvidia"
Option "TVOutFormat" "SVIDEO"
Option "TVStandard" "PAL-I"
Option "ConnectedMonitor" "TV"
EndSection
Not sure there
I don't know if this makes sense, but dolphinhomer, could you try
changing the config to something simpler. I was given the advice in bug
https://bugs.launchpad.net/bugs/82312 (see there for specifics) to
indicate my tvout config in a different way and it seemed to work (after
messing a round a bit
i have the same problème (feisty and nvidia 9631) in my Xorg.0.log:
(WW) NVIDIA(0): Unable to load "xf86ExecX86int10".
(EE) NVIDIA(0): Unable to initialize the X Int10 module; the console may not
(EE) NVIDIA(0): be restored correctly on your TV.
--
[nvidia-glx] X module Int10 fails to initialize
dolphinholmer:
Yes that came up in
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/89290/comments/15
...
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member
Have found reference to very similar (same?) bug in Debian X -
http://www.mail-archive.com/[EMAIL PROTECTED]/msg60955.html
I didn't mention earlier the xserver-xorg-core package version is
2:1.2.0-3ubuntu8
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bug
I have exactly the same issue using the 9775 driver. My output from dpkg
-l nvidia-\* | grep ii is:
ii nvidia-glx-new 1.0.9755+2.6.20.5-15.20 NVIDIA binary XFree86
4.x/X.Org 'new' driver
ii nvidia-kernel-common 20051028+1ubuntu7 NVIDIA binary kernel
module common files
I
Does anyone suspect this may be resolvable soon-ish? I'll have to re-install
Dapper if not.
Thanks.
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
** Summary changed:
- X module Int10 fails to initialize - Feisty
+ [nvidia-glx] X module Int10 fails to initialize - Feisty
--
[nvidia-glx] X module Int10 fails to initialize - Feisty
https://bugs.launchpad.net/bugs/109703
You received this bug notification because you are a member of Ubuntu
Bu
17 matches
Mail list logo
