Debian :: Jessie Screen Freeze - Requires Hard Reset
Apr 26, 2016
I'm running Jessie 64bit, and after installing the latest image and fully updating it, I get screen freezes using gnome, most oftenly when i press the start button to access gnome app grid. System becomes unusable and I have to hard reset. Just in case, I installed linux firmware from nonfree repos, but the issue persists. I don't use any exotic hardware:
Code: Select all00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
[Code] ....
I'd say it's related to graphics, but I don't know how to get around it...
Basically, when I do a reboot or shutdown and then the system tries to start I get a blank screen thus I have to hit the reset button and then I'm showed a grub menu (not sure why I have it set to autoboot) and then I can boot properly.
Using karmic on acer aspire 5332.Wifi was working from fresh install but would drop out often and sometimes freeze laptop resulting in hard reset.Installed Ndiswrapper to try wireless drivers unfortunately i can't get them to work. How can i revert back to original ubuntu drivers?
If you have a Radeon graphics chip and upgrade to Jessie, install firmware-linux-nonfree, before rebooting.
My dist-upgrade to Jessie seemed flawless until I rebooted and couldn't get into X.
Seems Jessie boots into Gnome by default, but Gnome now requires 3-D acceleration. For my Radeon graphics chip (ATI Radeon 3100), this requires firmware-linux-nonfree, which I didn't need before and was not installed as part of the upgrade.
A boot message alerted me to this need.
I was able to get X going with xinit. I used FVWM; for XFCE I believe the command is:
xinit /usr/bin/xfce4-session -- :1
and from there I installed the package firmware-linux-nonfree.
I have Debian Jessie 8 installed on a Acer 5733 Laptop. After I closed the screen, it goes sleeping, and when I open it, aleatory, it freezes. I don't have graphical interface, and the tty are not accessible. Sometimes, I get access to the computer 10 seconds, and then freeze.I have to shutdown the computer...and lose my work I was doing.I thought it was a X-problem, but the tty don't work too, so it's not ? When I restart the computer, it shows Code: Select allclearing orphaned inode <some inode number.
I just installed openSUSE 11.2 KDE via LiveCD on my desktop computer and have been loving it. The problem is that it will randomly freeze and requires a restart. I've tried booting up in safe-mode, but it still does it. Also, when it does, the screen flickers and flashes in and out before it freezes. And before anyone asks, yes, I have my NVIDIA drivers.
I'm using two screens where one Is cheep Denver TV screen with DVD player. I have just install Jessie on my PC. Before i had Windows and there was no problems finding correct resolution for this screen. Now Jessie recognize it as Unknown and the maximum resolution I can set is 1024x768 what is way to small even for this screen. At Windows resolution was something over 1200px wide. The worst thing about it is that this resolution stretches the display really ugly. You may think I'm making big deal of nothing but for me it is actually a deal. I'm graphical designer and I need to see display as it is.
By freeze, I mean that the mouse can still move, but everything else behind it is frozen entirelyI can switch to a terminal with CTRL+ALT+F1, it's ... I guess... X or gnome-shell or something that's frozen? Not the whole OS thoughThese freezes last anywhere between 5 or 10 seconds and 3-5 minutesI can't predict when they will occur, but often, after a suspend/resume, they will start occuring much more frequently. Also, they often happen after I enter my password and press ENTER on the lock screen after a resume from suspend. But not exclusively -- they can happen at any other time when I'm doing pretty much anything in GNOME...
Things I've Tried...
When frozen, I've tried to CTRL+ALT+F1, login, and run gnome-shell --replace... [*[When frozen, I can successfully CTRL+ALT+F1 and run `service gdm restart`... with the obvious downside of losing everything I have open. But the screen responds immediately and I can log back in to GNOMEI tried running `Xorg -configure` to generate an /etc/X11/xorg.conf file to edit, but received an error about not being able to generate configuration for multiple screens or something (I can retry and provide the exact error if this is a useful direction to try) is it the gnome-shell freezing? Is it X? Is it a problem with the X driver I'm using?
In trying to get openbox running in new Jessie installation, I followed an instruction in openbox.org: Help: XFCE/Openbox.
" If you want to use the Openbox root menu instead of Xfce's, you could terminate Xfdesktop by running the following:"
Code: Select allxfdesktop --quit.
That eliminated everything on the desktop except the Debian8 background image and the panel clock and made it impossible to do anything other than log out via a right click on the panel. Shutting down and rebooting just brings back the same situation. No terminal available.
I can't suspend my laptop because after suspending the system and pressing the power button I only get a black screen. As Debian wiki suggests, if CapsLock LED works the system is still running, which is not my case. I don't know why the system doesn't get back control.
No matter if I press Fn+Sleep keys, go to the Xfce menu, or type:
Code: Select all$ pm-suspend $ systemctl suspend
Anyhow I get the same result.
I've already followed some other posts but they didn't solve my problem:
I found a nice old mini industrial PC with an Jetway NF92 motherboard (Atom N270/Intel GMA945 GPU).
Installed Jessie on it, I have a strange problem under X11: mouse pointer is garbled (looks like somebody cut the arrow in four separate sprite and shake them well , and screen flickering. If I move down the mouse in the lower part of the screen, the screen flicker slowly, if the mouse goes in the top part of the screen, screen flicker rapidly... And finally, putting the pointer on the last line of the screen make the screen stop flickering with perfect screen....
Code: Select allroot@telmat:~# uname -a Linux telmat 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19) i686 GNU/Linux root@telmat:~#
Code: Select allroot@telmat:~# lspci 00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
I'm a relatively new Debian user, having come from Ubuntu. I recently bought a Dell micro-server to function as my Kodi media player. I installed an nVidia GeForce 210 to output to my Pioneer home theatre amplifier. The amp takes all my inputs (eg. Satellite set-top decoder, PS3, Kodi etc) and outputs to the TV. I installed XFCE as my desktop environment so that I could still interact with it via VNC.
Everything is working great except for one exceptionally annoying problem! Every day, I find that I am having to VNC into the desktop, load up nVidia X Settings, and change my screen resolution from Auto to 1920x1080 because it has lost the display configuration and the screen is blank. I presume this happens when the amplifier switches from one input to the next. It doesn't matter if I save the configuration to my X11.conf file or not - it still resets itself.
Before, this setup would run for months without any intervention (Same amplifier + HP microserver + Ubuntu + LXDE + ATI video card), so I'm pretty confident that the issue is either Debian, XFCE, or the nVidia card.
I installed jessie amd64 lxde to a thumb drive to use with a laptop. Vanilla install using the amd64 lxde live cd. Upon booting the usb system, I am presented with a black screen with blinking cursor. No grub screen, no ability to type any commands and no ability to switch to another terminal. I tried booting into the live cd and I could get into the intro splash screen. Booting to the live system from there would also hang at a black screen.
However, using the kernel parameter "nomodeset" from the splash screen did allow the live system to boot to the desktop. I booted the live system, mounted the usb system and chrooted into it. I edited /etc/default/grub to include "nomodeset" in the GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX variables and then ran update-grub.
Upon reboot to the usb system the problem still occurred. The video card in question is a amd firepro 5800m which has an lspci line of mobile radeon 5000 series. This card was supported in wheezy and apparently works with the live system.
After upgrading to Jessie (AMD64) I have a totally blank screen, not even a blinking cursor. The video card is a GeForce 6200 and I have nouveau loaded. I originally had an nvidia module in Wheezy. I decided to use the instructions at the Debian NvidiaGraphicsDriver wiki to install the NVIDIA legacy package. That was worse. The nvidia module was unloaded in the X.org log, and the screen presented as a login console.
I tediously removed all NVIDIA components, and reverted to nouveau since its report in X.org log says it supports GeForce 6 series cards. That brought me back to a totally blank screen. The nouveau module lists as "video" doing lsmod. Both gdm3 and the X server processes are up and running. Other than reporting that "nv" couldn't be loaded, there is nothing in X.org log that appear abnormal. The .xsessions_error log is troubling however, but I don't have the knowledge to interpret.
I recently upgrade my system from Jessie to Stretch, with no problem. A little later I upgrades Enlightenment from e17 to e20, and at some point shortly after that the second screen stopped working.
The nvidia X Server Settings correctly identifies both screens. But Enlightenment and xrandr does not see the second one at all. The second screen are on and the pointer moves correctly onto it, but no activity with left or right click. I have tried with the original xorg.conf, and generated a new one with nvidia-xconfig, but no difference. No obvious errors in any log-files either.
lisa@kitten:~$ sudo uname -a Linux kitten 4.3.0-1-amd64 #1 SMP Debian 4.3.3-2 (2015-12-17) x86_64 GNU/Linux
I want connect from remmina to jessie on another system via xdmcp but only black screen happened.
my daemon.conf Code: Select all[security] DisallowTCP=false
[xdmcp] Enable=true
[debug] Enable = true
And gdm3 listen on udp/177. My syslog :
Code: Select allJul 16 10:17:46 office /usr/bin/dbus-launch[1455]: X Error of failed request: BadValue (integer parameter out of range for operation) Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Major opcode of failed request: 140 (RANDR) Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Minor opcode of failed request: 7 (RRSetScreenSize) Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Value in failed request: 0x0 Jul 16 10:17:46 office /usr/bin/dbus-launch[1455]: Serial number of failed request: 150
Im running opensuse 11.2 on Linux 2.6.31.5-0.1 64Bit, KDE 4.3.1 with 4GB RAM, Intel duo core processor with Intel graphics card. I initially had opensuse 11.1, which i removed and installed 11.2. Initially everything.Then came the problem, the system starts up fine but then after a few hours freezes, monitor powers off and it wont accept commands from the keyboard or mouse. Meanwhile the lights (caps lock, numeric and scroll) on the keyboard blink. The power light is still on and i can hear the hard disk turning.
I have to forcefully turn the power off and restart but can freeze again after random periods.I do lengthy and demanding computations and its common for the PC to run for weeks without turning it off.
I have a second hard disk which has windows and C and D drives partitions. When I boot fedora 13, fedora automatically mounts them as 53 Gb Filessytem and 200 GB Filessytem. But when i try to browse to these filesystem, fedora ask me root password. How I can configure fedora so that it does not ask me root password and this change should be permanent ( surving computer shutdown and restart) ? I want these windows partitions to be reachable by me as the non-root user.Also given /dev/sdb (the windows disk) what is the command line to find out the filesytem path to which various paritions on /dev/sdb are mapped to?
When I install Ubuntu 11.04 with Wubi, I get this freeze screen after I reboot and get past the Ubuntu splash screen: url
As you can see, it's a scrambled picture of my Windows desktop. This happens with every other version of Ubuntu also.
I'm running a 64-bit PC and I don't wanna waste another CD or use a USB to install, because I actually progress further in my efforts whenever I use Wubi.
out of no where it seems ubuntu no longer wants to cooperate when suspending/hibernating. the screen will just turn to a black screen without shutting down. each time i have to maually power down my laptop.
I'm facing a big problem with a corrupted disk on my wife's computer after she hard resetted the box after it froze up solid.Upon restarting it dropped into Busybox reporting something like
Quote:No init found. Try passing init= boot arg BusyBox v1.10.2 (Ubuntu 1:1.10.2.2ubuntu7) built-in shell (ash) (initramfs) ...This is VERY similar to a problem I had just a few weeks back with my own computer - see this thread for details of that. From that problem I learnt a lot, so I thought this would be quite straight forward, but I've ran into problems.The first thing I did was get a live disk, I chose Ubuntu Rescue Remix. It's a command line interface, which I am ok with, but I can't copy/paste the outputs here....so I am currently downloading System Rescue CD.sda1 is the root partition, it is corrupted. I used dd to make a back up of that by mounting sda7, and dding the whole partition image into /mnt/sda7/sda1.img .This seemed to complete properly, but, when I ran e2fsck on that img file, it wouldn't complete, throwing up a lot of errors.
When I download and boot into System Rescue CD, I'll be able to run some more tests, in the mean time,I really want to save this disk otherwise my wife will be back on Windows permanently.
I've been running Ubuntu 10.10 very smoothly for a while now. Decided to upgrade to 11.04 - managed to corrupt the hard disk the first time by letting the laptop hibernate part of the way through but reinstalled from a live CD of 11.04 and it's now working except for this issue.
If I shut the screen on my laptop (or press the screen off button) either the screen won't come back on or it will but frozen (I can move the mouse but not click on anything etc.) In this state music continues to play (from spotify under wine) and if I press my hibernate shortcut (power button) the computer hibernates, only to wake into the same situation. I've got a Dell Latitude D520, upgraded to a bigger hard disk and more ram - the ubuntu partition has 50gb. Windows is working fine.
Edit: I noticed a sticky thread which includes something about a blank screen but I think this is a different issue?
Under 9.10, my laptop frequently freezes up and has to be hard-reset. At first I thought it was a Firefox issue because it happens most often when I'm on the web, but the computer also crashed on me while doing things in Synaptic, so it must be something else. I have an HP Pavilion z5000 with an Ati Radeon 9600 Mobility, 1.25 GB of RAM and 120 GB hard drive.
I've currently got 9.10 and have (somehow) managed to mess the system up already!It's a new computer so I'm not fussed about data loss etc, but is there a way to completely reset the system which will also format the hard drive (as it was a download that has messed it up!) without losing the O/S?
I feel a little awkward in this Control Panel: first time user. I installed the latest version of Ubuntu yesterday. All went smooth until I got to installing printer drivers. The setup went online and my system froze...everything froze. I had to do a hard reset. The printer installation went smooth the second time. So far this is the only problem I've had. No details needed. What I was wondering is if there's any way to check if the hard reset did any damage.
I currently have a problem where when xubuntu is restarted using the power button, it will prompt the user with grub asking which selection to boot (xubuntu recovery or xubuntu) this feature itself is fine, but for some reason there is no timer, which means that unless you hit enter, it will always be stuck on the GRUB selection screen. I am wondering if there is any way to change this, is there anyway to enter a timer into the system so no matter what, after x seconds it will boot xubuntu?
I've been getting a random hard freeze, in both windows and linux, so I'm pretty sure it's not a software thing. I've run memory diagnostics in windows and it came out fine, I'm not sure what other diagnostics I can run. what tools can I run in linux that might help me further diagnose the problem? I haven't installed any new hardware, and I blasted the inside with some compressed air to err on the side of caution, but I still have problems. i'm running the latest ubuntu ver btw
I'm new to Linux, tried Ubuntu, had slow boot problems, tried openSUSE 11.1, still have slow boot problems. The issue seems to be that the ata.0 device is slow to respond (ERROR= -16), the boot system forces a hard reset, then a soft reset, configures for UDMA 133, says the drive is ready, then does it again, three times, and then configures the drive for UDMA 100. It's a brand new Western Digital Caviar drive, and windowsXP likes it just fine. Once SUSE boots, everything seems to work just fine. I thought the problem might be with the drive jumpers, so I reset them from cable detect to master/single. No change in the problem.
First of all, i'll just say this myself. I'm a dumbass and tried to fix somethings that wasn't even a problem from the start and now my 9.10 installation is totally fubar. There, done, now let's move on.
Ok, so I tried to delete a folder after compiling two binaries to the wrong folder and used the Code: rm -r command on what I thought was the folder /home/lars/bin. And to add to the dumbass-ering, I was root while doing this. The computer hangs and leaves me with no other options than doing a hard-reset via power-button.
After rebooting I can't even see the login screen, it just hangs at the Ubuntu symbol.
So I give the recovery mode option in my grub menu a try and it gives me a bunch of lines, all looking good until I get this and the boot just stops with a blinking underscore. code...
Should I just beat myself for a while and then reinstall the OS or what...?
The hardware involved is a Asus EEEpc 1000h.
ps. I'm new to Linux and have so-far managed to get around by following guides and tips, just a heads-up.
