Debian Configuration :: Blank Console Screen With 2.6.32-trunk-amd64?
Apr 13, 2010
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
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'm using a dell latitude d630 with an nvidia quadro 135M card. I'm able to suspend without any problems while running the X server. If I try to suspend on console without the X server running, the laptop wakes up to a blank screen. The screen remains blank and my only resort is to type sudo halt (with the screen off).I'm using the proprietary nvidia driver with the nvidia-kernel package on testing.
I have a Asus A8N-E motherboard with AMD64 processor and NVidia 6600 GT graphics card.I downloaded the AMD64 version of 10.04 (the boot+live cd) and tried booting with it. After looking at the screen showing Ubuntu loading with 5 dots moving forward for about 5minutes, the screen went blank (not completely blank as power-off but a very dark grey color). I waited for about 10-15 minutes in this state but nothing happened.During this whole 10-15 min period the disk usage on the machine was high.Eventually, I just turned off the machine and booted into windows (which was already present on my machine) successfully.Is that blank screen for such a long duration a normal step during installation or was a different process expected?
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.
This only started after the recent updates which included a lot of sysv stuff in Squeeze. I'm not talking the Gnome or Xwindows consoles, I'm talking the full-on type you get when you do the CTL-ALT-F2 type of console. before those updates, I had no trouble. Now I can't get back into the gui by pressing CTL-ALT-F7 as usual. All i get is just a black screen. I do have the nvidia proprietary driver installed using DKMS, and I am running the latest (I think) liquorix kernel.
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,
I upgraded testing today on my intel laptop. During the upgrade I got the message that the new kernel would require additional firmware, see attached. Is the solution for this to install the driver from Realtek? [URL] If so, the instructions said to check if the driver was already installed, but what does the output below mean?
I'm attempting to install ndiswrapper-dkms package. The installation fails due to the following error:Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. dpkg reports that the source is installed
[code]....
I've been searching google for the past couple of days but haven't found anything specific. Any ideas to get me going in the right direction?
uname -a reports
Linux debtop 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 GNU/Linux
I have my X11 setup configured to rotate 90s counterclockwise for a portrait monitor. But when the system turns on, it's in the framebuffer console which is set to landscape mode. Is there a way to set it so that even the console is rotated in portrait mode? I'd like to do this automatically.
and 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.
I installed linux-image-4.1.0-trunk, when I boot into the kernel there's no wireless available. Dmesg indicates seems like the firmware is loaded, although firmware-iwlwifi is installed: ... [ 11.047031] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-7265D-13.ucode (-2) [ 11.047039] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
My Squeeze installation has the horrific 80x25 line display, and I cannot stand it. I know it can do better, because the grub screen is very tiny. I ran dpkg-reconfigure console-setup, but the offerings there aren't much better. I don't know what happened to the good ol' days of grub when all you had to do was pass vga=791 to the kernel to get a decent console size... but it seems they are gone.
I don't really understand this new v2 grub... I don't know why it was necessary to change how it was configured, when it seemed to work so exquisitely. how I would accomplish the functional equivalent of passing vga=791 (1024x768@75hz) to the kernel in grub
I'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"
I have a dell poweredge server. In the bios, it has the option to redirect the screen to the serial port. There is also the check box "redirection after boot" which from what I understand will let me to continue to use the serial port attached to a terminal as if it was the main VGA monitor with a keyboard attached.
When I start the machine up, everything goes as expected, I see the output from the bios on my serial terminal, until debian actually starts booting. It all goes blank. If i attach a monitor i can see it is indeed booted and waiting at the debian login prompt. What should I do from here? I was under the impression that if i enabled "console redirection after boot" that the os would be none the wiser and i could continue using the serial console as the main screen as needed, but that does not seem to be the case.
My new laptop works out of the box except for the video and the ethernet. For this, I have to use a later kernel than the Debian kernel (debian squeeze is currently 2.6.32). Upgrading to the new kernel (without moving to the testing dist itself) was pretty easy. I just installed linux-image-2.6.38-2-amd64 and linux-base from the testing distribution by manually downloading and using dpkg. After that, ethernet and video started working.
However, my virtualbox installation no longer works because the drivers do not match the kernel. I am used to this; whenever debian upgrades the kernel on me, I have to run "/etc/init.d/vboxdrv setup". This rebuilds the drivers. This failed for me, however, because it could not find the headers. So, I installed some more packages:
Go to "/lib/modules/2.6.32-5-amd64/kernel/drivers/net/e1000e/" and delete the e1000e.ko-file
Then download [URL]
Take the newly downloaded e1000e.ko-file and move it to "/lib/modules/2.6.32-5-amd64/kernel/drivers/net/e1000e/"
And finally load the module with either: "# modprobe e1000e" or "# insmod e1000e".
You should now have a working ethernet connection.
If connection is lost on system restart try rmmod e1000e; modprobe e1000e
I've for the first time installed linux (debian) to my computer. And I have a problem with ethernet that I can't solve.
I have a Asus Sabertooth P67 motherboard with built in ethernet card, I cant find any drivers for linux, I've tried google, Asus support page etc, but can't anything that says it will work with my computer, just a alot of windows drivers.
where I can find the drivers? Or if there's another way to solve the problem. When installing Debian i could choose between different drivers but no one worked, I've also tried with my motherboard CD but there was just windows drivers...
I was using Synaptic to remove unwanted sound & audio programs...it seemed to take out other files that were non-related ?
(1) Now apt-get complains about a "Held Package" and doesn't tell me the pkg name.
(2) Synaptic is broken...error..E: The value 'stable-updates' is invalid for APT::Default-Release as such a release is not available in the sources
E: _cache->open() failed, please report.
stable-updates isn't even in my sources list. I've purged synaptic, and re-installed but remains broken. When you close error msg synaptic disappears ? Therefore can't use synaptic at all.
(3) apt-get says many packages that were available are no longer available...like one of the main repos has disappeared ?
(4) I put the same repos that are working for my brother who is running Debian Jessie also, but didn't improve the number of missing available packages.
deb [URL] ....
deb [URL] ....
How or why things have gone so wrong from just removing unwanted sound pkgs.
To recap problems...apt-get held pkg....broken synaptic....unavailable pkgs.
I ran across something while installing amd64-kernel.I did so cause i wanted to test hadrets xfce-4.8 repo.viewtopic.php?f=16&t=58733#p341988It boots very fast.I usually don't care about such things, cause i am very happy how it is, but i wanted to check if it is a feeling, or for real.I followed gnududes how-to use bootchart:viewtopic.php?f=16&t=38869So, that was the long story, here comes the short version:On i368, but a full installation with all kind of stuff, it takes 20 seconds to boot.On amd64, with only a few basic packages, it takes 8 seconds.Is the fast boot time due to 64, or is it due to the little amount of apps?(that was my question for this thread, in case no one realized).
I wanted to know which is the best firewall application for my debian squeeze amd64 home desktop. I prefer a simple interface yet powerful enough. After googling I found two options - gufw & firestarter. I am not sure which one to choose between these two.
Installed 6.01a from DVD 1 on a system with 4GB ram. Installer installed amd64 version by default. When I try to install amd64.deb files I get "wrong architecture" error messages from the package manager. root@Laptop-RalphDeb:/home/ralphq# uname -r 2.6.32-5-amd64 root@Laptop-RalphDeb:/home/ralphq# uname -p unknown Why I can install amd64 programs and why I get unknown for the uname -p command?
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
I have a computer with internet access with amd64 architecture running Debian stable (Lenny). I have another computer with NO internet access with i386 architecture running Debian stable (Lenny).I want to download some packages for the i386 computer using the amd64 computer. So far, the only way I can see to do this is to use dpkg-architecture to temporarily change to i386 on the internet computer, run aptitude with the download-only option to retrieve the packages I need with all suitable dependencies, then switch the internet computer back over to amd64.
I can't imagine I'm the only person who ever needed to do this, and yet I've had no luck finding any advice. The method I described seems rather awkward - is there a more elegant solution?
I apologize to the membership, I realize now the absurdity of this subject. Having now studied the online repository search functions closer, I see it appears packages are automatically retrieved with all necessary dependencies. As such, it is not necessary to use apt and its various functions to do the job.
I have got the following Problem: I installed the 64 bit lxde Debian version... I couldnt configure the network during the installation because I just have a dsl modem and not a router... so the configuration of the network failed.... after the installation I started debian... and was surprised about the lack of "basic system configuration"-software that had been installed... I couldnt find aptitude or whats the debian-Update-Programm called .... instead I found OpenOffice... HAE? then I tried to configure internet access..... so I started a terminal and tried to start pppoeconf... but the program wasnt found! ARRRGG! What am I doing wrong here.... Why are these system utilities like pppoeconf not always installed...
I'm using Debian 7.8 Wheezy amd64, Gnome classic session. Laptop ASUS F551MAV, Intel HD Graphics (Integrated GPU), xserver-xorg-video-intel 2:2.19.0-6, firmware-linux-free 3.2
Sometimes, after inactivity, the screen turns black, not allowing me to see login screen. If I press CTRL+ALT+F1 (or F2,F3,Fn) nothing happens. The computer is still responsive, as I can reboot it through key shortcuts.
I have search in almost all logs in /var/log, without any information about the cause of the error. The time I was away from computer was between +- 18:10-18:22
Here is the log of daemon.log at the time of rebooting: [URL] ....
I can see one line that seems to be an error with (but it is displayed as warning):
Code: Select allFeb 18 18:21:47 debian gnome-session[3714]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Recurso no disponible temporalmente) on X server :0.#012 Recurso no disponible temporalmente is in english something like: Resource not available temporaly.
Log of syslog at the moment of screen blocked Code: Select allFeb 18 18:17:01 debian /USR/SBIN/CRON[4235]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Feb 18 18:21:36 debian acpid: client 3226[0:0] has disconnected Feb 18 18:21:44 debian shutdown[4411]: shutting down for system reboot
[Code] ....
It is not the first time that this is happens. It already happened a few times, that when I'm away, the screen is simply blocked.
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.
I know that in an xterminal I can redefine the default colour with something like !!red URxvt.color1: rgb:cc/00/00 URxvt.color9: rgb:ef/29/29 Is it possible to do something similar in the Linux (framebuffer) console?
