This started happening after I started working on the kernel image and initramfs tools configurations basically started trying to make my system work the way I wanted.I can be doing anything like playing worms or being on this forum and the screen turns black but I don't lose energy just nothing shows on the screen and my keyboard doesn't respond the num lock doesn't turn either state,
View 5 RepliesSo it's a beautiful day and I'll be happily using my computer when I realise that the screen is no longer showing that I'm typing or moving my mouse (or finger across a touch-pad). I can leave my computer in this frozen/crashed state for hours. My only recourse is to drain the battery or hold down the power button until the computer shuts down. The computer is a Dell Inspiron 6400 laptop/notebook. As my memory serves, it has an ATI graphics thingy. Radeon 1400, maybe. But I've had the computer for years and this behaviour has emerged only the past couple of months, with seemingly increasing frequency.
The OS is
# uname -a
Linux polaris 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux
(aka Squeeze?)
Sometimes this happens within minutes of turning the computer on and logging into Gnome. Sometimes this happens only hours after I've started using the computer (mainly just surfing the web). Sometimes it is preceded by a loud boop sound and the following if I have console open, sometimes not. So maybe that's unrelated. But that happened just now so I thought I'd throw it in.
One weird thing: Usually this happens within an hour of starting to use the computer, but one occasion I noticed I had not had the problem for several hours. On that occasion, the only thing I noticed I was doing that was also unusual: I had turned on and forgotten about a kvm virtual machine. After I shut down the vm, I had about only a minute before the freeze. I'm surprised now that it hasn't frozen since I started typing thing. Maybe I should always keep this forum open in a browser window.
I am running testing (with fluxbox) and my keyboard periodically freezes, meaning whatever I type in it doesn't respond. This lasts a few seconds (can be 2-3 or sometimes even more like 10) and one's it comes back I get all the keystrokes I was typing during the freeze. The frequency of the freezes can be like 4-5 times every hour and are very annoying. I can't seem to relate them to anything, they can occur during heavy usage but also when the box is doing absolutely nothing but waiting lazily for me to type some google search terms.
Can anybody help me track this problem down? At the moment I am using a wireless keyboard but this must be unrelated since I tested a couple of other keyboards (both wireless and wired) and the problem persists.
I have this machine (motherboard ITX Jetaway NF94-270-LF based on CPU Atom N270, full specs here) as a server for some time now (about 4 years). Debian 8.1 is installed on it.
Two days ago, after a power failure, the machine was not able to complete the boot process. I attached a keyboard and a monitor (on VGA port, the motherboard also as a DVI one, but I don't have a suitable monitor) to be able to see what's happening and interact with the machine. Unluckily, at a certain point during the booting sequence the screen goes blank and the monitor goes in standby mode; apart from that, the boot process continues in the background.
As far as I can recall, this behaviour existed for at least a couple of years (if not from the beginning) and the boot process was always completed successfully until two days ago.
The screen goes blank after the setup of the keyboard mapping. I tried everything to avoid the screen going blank: in the Grub menu I set the "vga" parameter, the "nomodeset" parameter, the grub_gfxmode parameter, I removed the "quiet" option, I removed the "load_video" line, I forced the BIOS to only use the VGA port for the video and so on, in order to disable or configure differently the video and the framebuffer. All these stuff had no effect at all: the screen keeps going blank at the same point during the boot process.
The only way I was able to use a fully booted system through keyboard and monitor was via the rescue mode of the Debian 8.1 netinst image. But that way, of course, I wasn't able to observe the normal boot process. So, I checked the boot parameters of the rescue mode and I found that the only usefull parameter was "vga", which I already used and was ineffective.
I'm always getting a blank console screen after booting a 2.6.32-trunk-amd64 kernel in squeeze. I still can read the line "Loading, please wait ..." in the display for a second - then it's completely black until X windows is starting. When I try switching from the X console to another virtual console (by pressing Ctrl-Alt-F1 e. g.), the complete system freezes. I have to hard reboot then.When I boot the previous 2.6.32-3-amd64 kernel instead, everything is fine as expected, though.There's a line "GRUB_GFXMODE=1024x768x16@60" in /etc/default/grub as well as a line "set gfxpayload=keep" in /etc/grub.d/00_header. So the problem might be framebuffer related in any way. Any ideas what could be tried?The system is a Latitude E6500 with a Mobile 4 Series Chipset Integrated Graphics Controller
View 2 Replies View Relatedand this morning's updates broke x. I get a blank screen instead of the login. I'm running an Nvidia 7900GS. I tried re-installing the Nvidia drivers... no good. I switched to the nv drivers and got further; I got the login screen, but when I try to log in it gives me the KDE splash screen and then takes me back to the login screen. I'm not sure what to try next.
View 13 Replies View RelatedI've been using ubuntu on a new desktop for a couple of months, but i had an old HP that was given to me in my basement. It has 384Mb of ram, and thats because i had a 256Mb stick laying around. I installed debian becuase it is more suited for older hardware (at least from what I've read). It installed fine, but it boots to a blank screen, and pressing ctrl+alt+F2 bring me to the command line. I checked /etc/X11/xorg.conf to change the driver to vesa, to find out my video card isn't even shown. I ran lspci and I found that it says my graphics card is Intel Corporation 82810E DC-133 (CGC) Chipset graphics controller (rev3) In the device section of xorg.conf, it merly says Identifier"Configured Video Device"
View 12 Replies View RelatedI have Fed 12, running on kernel 2.6.31.5-127.fc12.i686 I have newer kernels installed, but they will not boot into X.
The updater installed the kernel 2.6.32.21-166.fc12.i686. I can boot into runlevel 3. But if I then give the command startx, I almost get an x-window, I can see the top and bottom, ermm, wadjecallems, beams, but the screen is blank, and then the machine freezes. I can only switch off.
I am trying to install fedora 10, 64 bit on computer with the following specification but the installation stops during installation (mouse , keyboard, screen freezes).
Motherboard Gigabyte GA-MA790GP-ud4h rev.1.0
processor AMD phenom ii 940
I have updated the bios to the latest version.
i installed suselinux 11.3 on my lenovo t410 and i am using kde4. since then, i have the following problem: the screen freezes suddenly and the keyboard doesn't work anymore. i can move the mouse cursor, but clicking doesn't work. funny enough, the sound still works. the only way to restart the laptop is by pushing the power button for 10 seconds.
so far, there was no real pattern about the 'when does that happen?'. it happens sometimes when i am surfing on 'innocent' webpages like wikipedia or spiegel.de, not very often while watching videos. once it happened when i was only using kile for latex. it happened while i was experimenting with kdenlive. another time when i opened 2 vcl player in order to watch 2 videos simultanously.
sometimes there are days without trouble, sometimes i have to restart the laptop 5 times (like today...). is there a way to find out what is actually wrong? and how to get rid of the problem? (how do i create a proper bug report of these incidents?)
I am learning linux commands. I just wanted to see what happens when I type
Code:
The screen became blank. Keyboard was not responding. I couldn't do a proper shutdown. I switched off computer by pulling out the plug. When I restarted, I heard a series of beeps (approximately 10 beeps). Then I was dropped to the grub prompt. The problem now is I can not type anything into the grub prompt, because the character 'c' is continously printed across the screen like this:
Code:
I couldn't stop the character 'c' from printing (I tried pressing Esc, Ctrl+C)
The solution is easy. I can reinstall grub from a livecd. Or even reinstalling the entire operating system wouldn't take more than 30 minutes. But I want to know:
1) What exactly happened to grub? What stage does this error belong to (1, 1.5 or 2)? What is the error number?
2) How can running "sudo kill -9 -1" affect grub?
My screen is frequently freezing and even the keyboard or mouse doesn't work. I've been told to read the logs, But I don't know where thy are or what to look for?
View 3 Replies View RelatedI installed the new 9.12 cat drivers in the usual way (init 3; rpm -e the old drivers; generate new rpm; rpm -i new drivers; init 5), but instead of starting like I expected, I got a blank screen and what appeared to be a hard lock (keyboard lights don't toggle, Ctrl + Alt + Backspace and Ctrl + Alt + F1 don't do anything).
I switched back to radeonhd, but I'd like to get the proprietary drivers working if possible.
The usual listings
Code:
[nathan@ebisu ~] lsmod | grep fgl
fglrx 2323096 0
[nathan@ebisu ~] modprobe -l | grep fgl
extra/fglrx.ko
Looks like the driver loaded OK...
Code:
[nathan@ebisu ~] dmesg | grep fgl
code....
i'm using ubuntu since 8.04, and the current (9.10) is a fresh install on new hdd.the problem was the same each version (8.04, 8.10, 9.04, 9.10) - while i'm playing the video (no matter if i use mplayer [smplayer], gstreamer [totem] or adobe flash plugin [videos]) the playback freezes randomly for about 5-10 sec. during the freeze the movie is still played, i can hear the sound is ok. if i press [space] in smplayer it pauses the playback, so the responses for keyboard actions are ok. not for the mouse clicks however. i can still move the cursor around the screen but it seems the system is not aware of it (clicking on the "pause" button doesnt pause the movie). except the cursor, nothing changes on the screen (if the im [pidgin] window was blinking because of new message, it freezes etc etc).
is there any kind of log i could look into just to try figuring out the problem?it is impossible to watch any movie on my pc (currently i don't have tv)i installed windows on external hdd once and it played videos fine so i suppose it's not hardware problem .
As the title say, I'm having this odd problem, consistently, if I disconnect the USB keyboard from the box, it hangs after initializing md0 (raid of 10 sata disks).. The cursor blinks, but it never gets further, I've had it hanging like that for a day (I started the box before I went to school, and when I got home, I found that it never booted completely)
If I connect the keyboard, the box boots fine..
I am having the same problem, as soon as X tries to load my screen just goes blank. I have an ATI Radeon 9550. At first I tried switching between VGA and DVI as well but upon ruling that out, I switch to my on-board video card and that is working thus far, but I'm trying very hard to figure out a way to be able to switch back. Anyways I'll check back in later on if I have any new information I will post.
View 3 Replies View RelatedI am using Debian with a gnome desktop.
Code: Select alluname -a
returns
Code: Select allLinux app-server 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
My desktop sometimes freezes and does not respond to keyboard or mouse. I initially thought the CPU was overheating but it froze tonight when my CPU temperature was 32C and it has been up to 50C without freezing. I am beginning to think it is a software issue rather than a hardware issue but do not know. I looked at the pm-powersave.log and user.log but did not see anything suspicious.
I have two systems, both running Squeeze, one (desktop) executes Java applications perfectly while the other (laptop) doesn't.
I found two small examples:
http://www.x2d.org/java/projects/fluffschack.jnlp
works well on both systems
[Code]....
All the online Java tests I have found tells me that all is fine. I've browsed around quite a bit, and some are suggesting incompatibilities between Java and certain display drivers, but unsure of how to proceed.
We have several systems (DELL-Server PowerEdgde) installed with Debian Jessie 8.4 (physical server and VM) and if the server has big Disk I/O (copy, backup with Backup Exec) the VMs freeze.
Console output:
[168960.072192] INFO: task jbd2/xvda2-8:139 blocked for more than 120 seconds.
[168960.072209] Not tainted 3.16.0-4-amd64 #1
[168960.072213] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[168960.072220] jbd2/xvda2-8 D ffff8803e72946e8 0 139 2 0x00000000
[code]....
The system installed: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06)
I installed Jessie with ext4 and ext3, same error!
I have a Dell Latitude E6410 which I can boot from an Iomega external hard drive when I want to run Linux on it. It is a work issued Windows XP laptop and when I travel, I am more comfortable with Linux, so I created a dual boot option without touching their hardware. The external hard drive plugs in to the USB ports and the BIOS picks it up as the primary boot media, although the internal drive is still present. (That is the desired outcome).The problem is that the system periodically locks up solid and only a forced power off will get it to respond. The system seems to go into a kernel panic and fails to write anything before dying. The system completely locks up and stops responding to mouse and keyboard. It also seems to drop off the network. When I look at the logs after restarting, nothing at all shows up related to a kernel panic or anything else. To further complicate the diagnosis, on the reboots, sometimes the boot process locks up at "Starting GDM3", sometimes it doesn't, and wont for several attempts but eventually will boot to gnome. Some times it runs fine for a few hours, sometimes for only a few minutes. Can anyone recommend a way to diagnose this?I am trying to run Debian 6.0 32-bit with the defaults.
View 8 Replies View RelatedAfter the mass amount of updates that appeared for Debian, my DVD drive seems to detect a burned DVD I have as blank now. And when i put in the disc, there's two copies of the DVD drive on Computer, both of which are labeled CD/DVD Drive: Blank DVD-ROM Disc. I have gone in to disc manager and found that it is possible to mount the volume on the disc, and on the second icon it will appear and work. However, this is annoying having two icons.
Now, when I don't have a disc in there, it only shows one drive. My PC may have messed up during the updates, because I just let it update in the background while my sister was using it to show my mom's friends pictures and she randomly closed out of one of the windows without asking me anything (ffff), so that may have messed something up. Does anyone know how I would go about fixing this?
I just upgraded from Lenny to Squeeze and now when I enter startx I get a solid black screen and the computer does not respond to any keyboard input. Ctrl-Alt-Backspace, Ctrl-Alt-Delete, Esc, Alt-F2, Alt-F4, etc. all do nothing. No beeps or anything. I have an NVidia graphics card and have been using the proprietary NVidia drivers. I originally thought the problem might be related to this driver but I tried both the nv and vesa drivers and got the same results.
Attached is my Xorg.log.0 file. It just ends after the GLX extension initialization.I am able to use ssh to login after running startx. Running "ps aux" from the remote machine I did not see a process for X. I copied the output below the Xorg.log.0 file.
I'm hoping someone can help me. I upgraded my server from Lenny to Squeeze this afternoon following the release notes at http://www.debian.org I had no issues and everything is still running. I then installed Sqeeze via the Net Install disc into a virtual machine for some testing. Once the install was complete I found that apt was not working. It turned out the sources file was blank. I manually added the official repos and did an update. There were no new packages for installation.
Now, after a reboot, I get the Grub error:
error: ELF header smaller than expected
Entering rescue mode...
grub rescue>
I have no idea why this happened because I've not changed grub, just played around with apt. Has anybody any idea why apt had a blank sources file and grub is now failing?
After a successful install of the MFC-J4420DW printer and scanner using Brother's install utility, I am experience severe battery drain and xsane freezes (total system lockup, requiring using CONFIG_MAGIC_SYSRQ keyboard command REISUB or hard reset).
The Brother support page and utility/drivers are found here: URl....My laptop is the HP Elitebook 8540W and I am running Debian 8 using LVM, separate partitions for /home, /var, /temp, /swap, and /. I have looked at logs in /var/log. kern.log, daemon.log, messages and dmesg, but have not found any relevant info ...
I purged all drivers/packages and tried a manual install using each deb package, but ran into some permission errors, so I purged again. I also purged xsane and reinstalled it, then did a complete printer reinstall using the brother Driver Install Tool.The tool works great, full functionality for the MFC-J4420DW. But I know I can't live with the power drain, and I would really prefer to use Gimp and the xsane plugin rather than simple scan ..
Up until a couple days ago, my computer had no problems suspending to ram. However, now when I suspend, and later hit a key on the keyboard (usually space) to resume, all I see is an illuminated black screen. I can't even open a tty via Ctrl+Alt+F1. I can however ssh into the machine.he only possibility I can think of is that I am no longer running kdm. I just use "startx" to star an openbox-session.
View 8 Replies View RelatedI have an system that d8.2 appears to install correctly. On first (or subsequent) boot, I get the DB8 load screen, then a quick fsck, then nothing. I appear to have some sort of environment running as I can move a mouse pointer, but nothing else.
CTRL-ALT-F2 results in the mouse pointer vanishing, but nothing else. I expected to end up at the CLI.
I have tried different installs and options, always the same result. This machine ran an earlier version with issues.
I have some problem with Debian 7. Just installed Debian 7 wheezy.
Motherboard Intel D2500CC, graphics - Intel GMA 3600. Monitor (BenQ V2200 Eco) connected via VGA cable. No X server installed.
After GRUB boot as soon as modesetting kicks in, the monitor loses the signal and goes black. Keyboard does appear to be active, as Ctl-Alt-Del will cause a reboot.
I tried nomodeset, vga=791, 771 etc kernel parameters, but this won't work.
I installed wheezy/LXDE yesterday in my HP netbook (first-time Debian user) and I am unable to get suspend/hibernate to work properly: after I come back all I get is a blank screen, although the computer seems responsive (CapsLock and such do respond).
I installed firmware-realtek from non-free (for rtl_nic/rtl8105e-1.fw, which was missing at install), nothing changed. I have acpi installed (it came by default). My graphics card is an Intel GMA 3650 (I see in internet that this is a problematic one). I just want a lightweight Linux to replace the default W7S.
I run an old Toshiba Satellite M35x S114 Laptop with Debian Testing, it always runned smoothly - although it IS testing . Since the latest update to kernel 2.6.32 , the X server just freezes. The init goes all the way to gdm, and then a blank screen , no mouse pointer, no way to get out of this screen (not CTRL+ALT+BACSPACE not CTRL+ALT+F1 / F2 ... etc) just a hard reset.
I can boot to the older .30 kernel with absolutely no problem, gdm starts normally login successfull (as I am able to write this on the reffered machine and all).
Here comes the gory details:
>>> The graphic card:
lspci | grep gra
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
>>> When it works with .30 kernel:
cat /var/log/Xorg.0.log
code....
Noting that there are no more Modlines in the new Xorg.0.log
Besides, X is disabling the mouse and keyboard in the configuration.
I've run into an issue that I'm not sure how to address. I'm running Squeeze and upgraded my system this morning.
The packages upgraded were:
About 10 seconds after upgrading, the system froze completely and I had to do a hard restart. The system froze again 10 seconds after the bash login prompt was displayed (I'm not using a display manager) after reboot. The source of the problem appears to be my Realtek 8192SE wireless driver. I was able to boot the kernel in recovery mode and uninstall it, which has fixed the issue. Rebuilding the driver causes the problem again.
I suspect that something to do with the sysv and init packages affected the driver in this way, but I've no idea where to start in trying to fix this. I can't imagine this is a fault of the Realtek driver as it worked just fine up until this point.