Hi Peter,
I had used bbswitch which installed from apt-get with the same result. I
didn't use any particular compiler on my machine.
tye@tye-VPCZ135GW:~$ gcc --version
gcc (Ubuntu 4.8.2-19ubuntu1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source
I'm using Sony VAIO VPCZ135GW.
I realized that bbswitch failed to be manipulated on my machine, and it also
blocked the way to suspend, hibernate
root@tye-VPCZ135GW:~# cat /proc/acpi/bbswitch
Segmentation fault
root@tye-VPCZ135GW:~# rmmod bbswitch
(rmmod hung)
root@tye-VPCZ135GW:~# echo -n
it might be an issue with the DVI/HDMI interface, I don't think I had an
issue with the VGA port.
it's running headless right now so I can't test it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@thedanyes, I'm intrigued, can you play full screen openGL apps for long
periods without crashes? some good tests are Marble Arena 2 or XBMC in
full screen playing high-res video. if so, do you have links to the two
motherboard firmware versions, or at least version numbers of both?
update for
What I don't get is that I have tried installed 304.37 invidia-current,
but the driver in use (as per System Settings Additional Drivers) is
nvidia-current-updates, and that is 295.49. Do I need to uninstall
nvidia-current-updates?
switch it to nvidia-current in the Additional Drivers tool.
--
@ragtag, if you use Ubuntu then in a terminal do:
sudo apt-add-repository ppa:ubuntu-x-swat/x-updates; sudo apt-get
update; sudo apt-get upgrade
info about the ppa:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/
--
You received this bug notification because you are a member of Ubuntu
@ag-restringere,
you aren't supposed to install the drivers from the .run while X is running. if
you took the time to read the README, you would have seen this:
Before you Begin
Before you begin the installation, exit the X server and terminate all OpenGL
applications (note that it is possible
@ag-restringere, my bad, I misunderstood what you were saying
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096
Title:
Nvidia driver causes xorg crash
To manage notifications about this bug go
@tye3ow: In that case, you are probably experiencing a different issue,
as we have identified a specific problem that was introduced between the
290 and 295 series of drivers that we believe is responsible for many of
the reports here.
The next 304 release (the fix is not in 304.32) will contain
apparently not a duplicate as it is only for logouts, not system
freezes. I guess we'll see if we garner any attention or intent to
actually fix this one now that the other one is actually resolved
(although, given the history on this one, I doubt it)
lately my system will not always black out
downgrading to 290.10 didn't have any effect at all for me, which it
took only a couple of minutes of Marble Arena to verify
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/973096
Title:
Nvidia
still present in 12.04 (64bit) with the 295.49 (X-Updates) drivers on
the GeForce 210. I don't know if it is a heat issue or if heat
generation is just a symptom of whatever issue is causing the problems.
I sure would like for the problems to go away though, as this is the
second release with the
oh yes, update: the screen no longer goes black, but instead as Sergio
pointed out, it freezes which I suppose might sound like progress,
except that the system reboots itself after a few seconds and the
problem still renders OpenGL useless.
--
You received this bug notification because you are
this might be a duplicate of this bug, I have written quite extensively on how
I reproduce this on my GT218 [GeForce 210] (rev a2)
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/882710
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'm not sure if this is a duplicate of this bug or not:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096
the same indications of both reproduction and anecdotal fixes are
present there. I might give the upgraded kernel a try but I loathe using
packages so far ahead of
to allow Samba access from my network I use:
sudo ufw allow from 192.168.0.0/24 to any port 137:139,445 proto tcp
sudo ufw allow from 192.168.0.0/24 to any port 137:139,445 proto udp
the Samba profile doesn't include port 445 which may cause some
functionality to fail with some Windows boxes.
@Strange_cathect, what version of the drivers are you using? the
'version-current' in the repos is still 280.13 (unless you're using the
x-updates repo)
tye@T:~$ apt-cache policy nvidia-current nvidia-current-updates
nvidia-current:
Installed: 295.33-0ubuntu1~oneiric~xup1
Candidate: 295.33
what happens when you use an intensive OpenGL app? XBMC in windowed mode is a
good place to start, since you can minimize it and watch your heat, or rather
anything using windowed mode+OpenGL at any larger scale. you can watch your
heat with this (it's what I have in conky lol):
nvidia-settings
I figured I'd give it a go and see if the problem might be fixed so I
fired up some Marble Arena 2 in Desura and played it for a little bit,
and then same problem
---
Mar 28 04:42:04 T kernel: [94085.118038] CPU0: Core temperature above
threshold, cpu clock throttled (total
it seems to be heat generation as I can load and minimize XBMC 11.0 and
then watch my GPU temperature climb to above 100°C. this issue is not
present in 11.04 which might be something to do with Gnome3 rather than
Gnome2 or the nVidia drivers (but that is just a guess at this point)
--
You
still happens all the time, one of the reasons I was reluctant to
upgrade to 11.10 and sadly the more it happens the more I think about
going back to 11.04 (as it never happened in 11.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
still getting GPU has fallen off the bus errors even with 295.20 (from
x-updates). same if I force the driver to 280.13 (from official repos).
I'm using Gnome Shell, and I experience it most often when I have
intensive OpenGL apps running (Trine 1 2 running under WINE, Marble
Arena 2 running
Public bug reported:
Maximus does not undecorate WINE apps while undecorate is enabled. all
other apps seem to behave correctly (undecorated while maximized).
Ubuntu 11.10
tye@T:~$ apt-cache policy maximus
maximus:
Installed: 0.4.14-1ubuntu5
Candidate: 0.4.14-1ubuntu5
Version table
Public bug reported:
Binary package hint: evolution
Hello,
This is a feature mainly needed for GMail users as GMail works differently
than most IMAP servers (although the Spam folder is doubly useful for any email
service which also uses a spam folder)
I would like to see a feature which
I managed to get the rest of Hardy installed from the online
repositories over the weekend, complete and current as of yesterday
(Sun27Jan08). Nothing has improved in re: this bug -- X still aborts at
startup with the same error and backtrace:
===
(WW) imstt(0): Mode pool is empty
(EE) imstt(0):
No proper Alphas exist for my PowerPC port, but I've tried to install a
few recent daily PPC builds from ISOs and also tried network
installation directly from the online repositories (my preferred method,
successful for previous releases). I can always get the base Hoary
system installed just
Public bug reported:
Binary package hint: xorg
Already reported upstream to Xorg as their Bugzilla # 13949
(http://bugs.freedesktop.org/show_bug.cgi?id=13949), apologies if that
precludes submitting it here, just covering all relevant/helpful bases:
As of Ubuntu 7.10 Gutsy, and also appearing
$ uname -a
Linux vesta 2.6.22-14-powerpc-smp #1 SMP Tue Dec 18 09:17:24 UTC 2007 ppc
GNU/Linux
$ sudo ddcprobe
oem: IMS TT (IBM)
memory: 4096kb
noedid
--
X aborts w/ backtrace: 'Mode pool is empty' and 'No valid modes found'
https://bugs.launchpad.net/bugs/180960
You received this bug
** Attachment added: Output of 'lspci -vvnn'
http://launchpadlibrarian.net/11182486/lspci-vvnn.txt
--
X aborts w/ backtrace: 'Mode pool is empty' and 'No valid modes found'
https://bugs.launchpad.net/bugs/180960
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Log generated w/ std. xorg.conf in place
http://launchpadlibrarian.net/11182488/Xorg.0.log
--
X aborts w/ backtrace: 'Mode pool is empty' and 'No valid modes found'
https://bugs.launchpad.net/bugs/180960
You received this bug notification because you are a member of
** Attachment added: Log generated by 'failsafe X' vesa fallback process
http://launchpadlibrarian.net/11182489/Xorg.0.log-failsafe
--
X aborts w/ backtrace: 'Mode pool is empty' and 'No valid modes found'
https://bugs.launchpad.net/bugs/180960
You received this bug notification because you
Oops, disregard the above log attachment; that one was before I realized
the vesa driver didn't get installed in the first place (strange to have
a fallback-to-vesa process without installing vesa!).
This one is the correct log produced by the fallback-X after I installed
vesa manually.
**
** Attachment added: Log produced when xorg.conf is absent
http://launchpadlibrarian.net/11182492/Xorg.0.log-noconf
--
X aborts w/ backtrace: 'Mode pool is empty' and 'No valid modes found'
https://bugs.launchpad.net/bugs/180960
You received this bug notification because you are a member of
** Attachment added: xorg.conf (w/ commented experimental entries included)
http://launchpadlibrarian.net/11182496/xorg.conf
** Description changed:
Binary package hint: xorg
- Already reported upstream to Xorg as their Bug # 13949
+ Already reported upstream to Xorg as their Bugzilla #
I notice you have partitions /dev/sdc[1-7] listed in Feisty, but no
partitions on /dev/sd[abd]. If you could dmesg | grep for lines
matching 'scsi' OR 'mesh' (sorry, don't know the correct grep syntax for
this) -- or maybe just do 'dmesg | grep -A1 -B1 scsi' -- that could give
clearer context of
Public bug reported:
Binary package hint: linux-image-2.6.20-16-powerpc
On my PowerPC Mac with an internal Fast SCSI-2 bus built-in on the
motherboard (uses 'mesh' driver as do all pre-IDE Macs), the Feisty
kernel (2.6.20-series) during boot detects and then promptly offlines
all except one SCSI
** Attachment added: dmesg output
http://launchpadlibrarian.net/7922505/dmesg.txt
--
Disks on internal SCSI bus offlined during Feisty boot, no I/O thereafter
https://bugs.launchpad.net/bugs/118319
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Attachment added: lsmod output
http://launchpadlibrarian.net/7922506/lsmod.txt
--
Disks on internal SCSI bus offlined during Feisty boot, no I/O thereafter
https://bugs.launchpad.net/bugs/118319
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
38 matches
Mail list logo
