similar to: baby blue screen of permanent death

Displaying 20 results from an estimated 2000 matches similar to: "baby blue screen of permanent death"

2016 Oct 18
2
GM108GLM?
Hi, It would seem like it (attachments are from 4.9-rc1, btw), but it doesn't look like there is any support in the Xorg driver. How can I help with that? Best regards, Sune Mølgaard Translucent ApS On 2016-04-22 09:33, Pierre Moreau wrote: > Hello, > > A patch was merged yesterday to recognise GM108 (see >
2016 Dec 07
2
GM108GLM?
Hi again, It works :-) Reclocking, however, is another kettle of fish. Trying #echo 0f > /sys/kernel/debug/dri/0/pstate hangs X. Trying the same with no X running reveals: Dec 7 10:08:42 dell-smo kernel: [ 728.831020] nouveau 0000:08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to
2016 Dec 08
2
GM108GLM?
Hi, With drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-12-08/ I don't get the error messages, but I still get a soft cpu lockup. What info would you need from me to get it working? Best regards, Sune Mølgaard On 2016-12-08 08:10, Karol Herbst wrote: > hi, > > give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with
2016 Dec 08
2
GM108GLM?
Aha! That seems to do it. If I interpret correctly, it doesn't set it quite to full power, though, but it's certainly an improvement: 07: core 405 MHz memory 810 MHz 0a: core 270-1124 MHz memory 1600 MHz 0f: core 270-1124 MHz memory 2002 MHz AC DC * AC: core 1012 MHz memory 2002 MHz A short run of glmark2 shows aver 100% improvement to ~550 FPS. Interestingly, it's still nowhere
2012 Apr 09
12
[Bug 48464] New: Crash when GLXVBlank set to true
https://bugs.freedesktop.org/show_bug.cgi?id=48464 Bug #: 48464 Summary: Crash when GLXVBlank set to true Classification: Unclassified Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2016 Mar 01
3
[REGRESSION] nouveau: 30 second boot hang after commit 2b700825e
Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only
2016 Jan 06
1
No GUI with CentOS-7.2
Sylvain CANOINE wrote: > Could you share your whole Xorg.0.log ? Do you use a custom xorg.conf, or > custom xorg.conf.d files ? Opensource Ati driver, ou proprietary blobs ? Thank you for your interest. I am running CentOS-7 installed from CentOS-7-x86_64-LiveKDE-1503.iso and later upgraded to CentOS-7.2. The only packages I have installed have been from CentOS and Epel repos. I'm sure
2011 May 03
12
36 FPS using ubuntu-classic desktop, drops to 4 FPS xubuntu
Hello Recently upgraded to Ubuntu 11.04 and not liking unity I swtiched to xubuntu but was perturbed to find my World of Warcraft FPS drop from 36 FPS in Ubuntu 10.10 and Ubuntu 11.04 'ubuntu classic' down to 3/4 FPS xubuntu. Again, to confirm it wasn't anything in the upgrade I made sure that the FPS is as normal in 11.04 when I select 'Ubuntu Classic' when logging in rather
2017 Mar 31
2
Invoking lld for PE/COFF (Windows) linking
On 3/30/2017 9:03 PM, Reid Kleckner via llvm-dev wrote: > On Thu, Mar 30, 2017 at 5:57 PM, Edward Diener via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Actually just doing: > > clang++ -c t.cpp -o t.o --target=x86_64-windows-msvc -fmsc-version=1900 > clang++ t.o -o t.exe --target=x86_64-windows-msvc
2013 Nov 17
4
file managementttttttttttt
Last week, I installed CentOS 6 yet again. I took the default desktop: gnome. Whenever I open a directory, I get a new window. That gets rather annoying, especially when I have to drill down several levels. Is there around that behaviour? If it's in edit->preferences, I didn't find it. Eventually I expect to change desktops. Until then, any ideas? -- Michael hennebry at
2013 Sep 24
5
scanner only works in su mode
Apparently I hadn't done any scanning since my move to centos. hp-scan works for root, but not for me as me. When I try to use xsane, it tells me no device found. When I try to use hp-scan as myself it tells me: error: Unable to locate device hpaio:/usb/Photosmart_C3100_series?serial=CN6ARC321S04KV using SANE backend hpaio:. Please check HPLIP installation. What do I change to make it let me
2017 Mar 31
3
Invoking lld for PE/COFF (Windows) linking
On 3/30/2017 7:59 PM, Reid Kleckner via llvm-dev wrote: > On Thu, Mar 30, 2017 at 6:08 AM, Edward Diener via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Are you saying that once lld is built with mingw-64/gcc on Windows > it is impossible to tell it to handle PE/COFF files when invoking it > from clang++ using the
2013 Sep 08
2
mouse "stuck"
Sommetimes, for no apparent reason, my mouse cursor will become four arrows and suddenly I cannot do anything with my desktop. I can move the cursor and that is it. Clicking has no effect. cnrtl-alt-F6 gave me another virtual console from which I could post this. Other rebooting, how do I fix this? I'm running xfce on 6.2. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday,
2013 Feb 18
1
[OT] how does ELF record file scope things?
fred.c: static void sfunc(int *p) { *p=1; } static int x; void fred(void) { ... sfunc(&x); ... } greg.c: static void sfunc(int *p) { *p=2; } static int x; void greg(void) { ... sfunc(&x); ... } Once the object files from fred.c and greg.c are linked, how does ELF distinguish the sfunc's and the x's? I've been trying to RTFM, but it hasn't helped? -- Michael
2013 Nov 25
4
died again
CentOS 6.4 died on me again. Didn't leave any traces that I could find. The screen just suddenly went black. Couldn't switch to another virtual terminal. Pushing the reset button worked. Didn't have to power off this time. -- Michael hennebry at web.cs.ndsu.NoDak.edu "On Monday, I'm gonna have to tell my kindergarten class, whom I teach not to run with scissors, that my
2016 Dec 31
3
Raspberry PI3 - CentOS armv7hl gnome desktop
Maybe there is a better place to post this message but as my question was still CentOS related thought I would start here. Please advise if there is a better forum of which to ask this question. I am playing around with making a "desktop" workstation out of a Raspberry PI3. I have had no problems installing the OS and pretty much have everything working except a Gnome desktop. I
2015 Aug 13
0
how do I stop automount of Hitichi Lifestudio USB drive
On Wed, 12 Aug 2015, Jonathan Billings wrote: > On Aug 12, 2015, at 5:22 PM, m.roth at 5-cent.us wrote: >> autofs is what's mounting it. But if you turn it off, you'll have to >> manually mount anything that's not in /etc/fstab. >> >> Sounds like gnome's trying to be WinDoze.... > > Its not ?autofs? specifically (which is a simple thing) but udev
2013 Oct 30
2
How should I reinstall CentOS?
> -----Original Message----- > From: Les Mikesell [mailto:lesmikesell at gmail.com] > Sent: Tuesday, October 29, 2013 5:25 PM > To: CentOS mailing list > Subject: Re: [CentOS] How should I reinstall CentOS? > > On Tue, Oct 29, 2013 at 3:47 PM, Michael Hennebry > <hennebry at web.cs.ndsu.nodak.edu> wrote: > > <SNIP> > > > I'm not willing to
2017 Apr 04
47
[Bug 100567] New: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau
2013 Aug 27
1
Message from syslogd@localhost ... kernel:Disabling IRQ #17
" Message from syslogd at localhost at Aug 27 08:57:53 ... kernel:Disabling IRQ #17" is the message I got on all my terminal windows at the time indicated. What is it complaining about? What should I do about it? I got some information from dmesg. It mentions IRQ 17, but the only error is from before the most recent hibernation. Here are some excerpts, in order from dmesg: SELinux: