Debian Configuration :: Console Dims On Booting And Stays Dark
Oct 25, 2015
Since moving my debian server over to a Gigabyte H97N-WIFI motherboard the console dims on booting and generally stays dark. Strangely the screen the brightens up if I go to an emergency shell, but if the boot runs successfully I don't see the resulting login prompts. Also, during the boot process the messages to the console are too dark to see.
I've tried the i915.invert_brightness=1 fix mentioned here [URL].... but that seems to have no effect. I'm assuming that this has something to do with moving to intel graphics as my previous hardware had a radeon graphics card and didn't display this problem.
I'm using Debian Sid xfce on my lenovo laptop. When i try to shutdown, the screen always stays on (the fans turn off). It says "reached target shutdown", then this happens: [URL] .... and then it hangs. I have to press the power button to shut it down. (I have the same problem with reboot). I had the same issues with Jessie.
Things i tried so far and didn't work:
Code: Select allshutdown -h now shutdown -p now halt poweroff systemctl poweroff init 0
I edited /etc/default/grub and added the following options at "GRUB_CMDLINE_LINUX_DEFAULT":
acpi=force, acpi=off*, acpi=noirq
*acpi=off: shutdown (not reboot) worked a few times but i didn't have wifi and power manager didn't seem to work
none of them worked..
I have no energy or wake up options at my BIOS.
I found out that i can normally reboot with the Alt + sysrq + REISUB key combination.
I just recently updated wicd from backports on lenny to version 1.6.2.2. And with my static ip configuration in wicd, when i click on the Scripts button in the network profile properties window the gui part of wicd totally freezes. This literally means that the tray icon becomes unusable although the connection stays alive. I would like to setup some scripts to automatically activate my vpn connection through pptp, which already works manually, but i would like to do it somehow through wicd. The wicd wiki talks about it vaguely so i figured i try it. I also tried to post this question on the wicd forum but registering is disabled for the time beeing.. though luck i guess.
So anyway does anyone else has these sympthoms with the backports version of wicd ?
I recently got an upgrade from my mobile broadband provider (3 UK) that included a ZTE MF112 modem. I found that (unlike the Hauwei modem that preceeded it) this item did not work "out of the box". After a bit of googling around I decided that a good starting place would be to upgrade the OS on my laptop. I've been meaning to do this for a while anyway so have just installed Squeeze (the i386 version, on Thinkpad x61). I think it's now pretty close to working "out of the box" but annoyingly isn't quite there. I thought of getting a ZTE modem to work say that usb-modeswitch needs to be used to make it not load as a cdrom. However, it appears to load correctly without any alteration (in fact, adding the /etc/udev/rules.d/zte_eject.rules file I have found described appear to do the reverse and make it load as a storage device - at least an icon for it appears on screen).
lsusb correctly lists it as device 19d2:0031 and identifies the device as a ZTE MF636 (though it says MF112 on the package). Looking at the Network Connections tool there is an entry for 3 mobile that is, afaik, correctly configured. If I click on the network applet on the toolbar, there is a bit of contradiction: towards the top of the drop-down list it reports mobile broadband as not enabled, but further down under the "available" list is an entry for "3 internet". I haven't paid too much attention to the not enabled entry because it also reports the wired network as not managed, so maybe this is just a quirk of network manager. - I know you have to comment out eth0 entries in /etc/network/interfaces to have network manager deal with the interface in Squeeze. There are no entries for the mobile connection in the interfaces file.
If I click on the 3 internet entry the applet goes momentarily into trying to connect mode (the circling dot) but very quickly pops up a Disconnected box, and that's all that ever happens. I note that the light on the modem stays permanently red. On the old Huwei it started green but went blue, and I think I read something about it also changing colour on the ZTE. On the other hand, the Hauwei didn't show up on the network manager list until the light had turned blue, whereas this does seem to be there. It looks as if the problem is something fairly trivial since the device appears to be both recognised and (almost!) correctly configured. How to sort this.
I'm trying to manually boot (from the GRUB console) into a system set up as follows: crypt partition -> LVM -> root LV, and I'm having some trouble figuring out how to do this from the GRUB console.
I have successfully manually booted a system which is set up as just LVM -> VG -> root LV. All I have to do is load the LVM module. In GRUB, that partition shows up as (hd0,gpt5). Once I load the GRUB LVM module, I can see the logical volume within the LVM as well. (My volume group name is "caesar", and the single logical volume is named "root".)
Code: Select allgrub> ls ... (hd0,gpt5) ... grub> insmod lvm grub> ls ... (lvm/caesar-root) ...
It's fairly simple to manually boot:
Code: Select allgrub> set root=(lvm/caesar-root) grub> linux /vmlinuz root=/dev/mapper/caesar-root grub> initrd /initrd.img grub> boot
Where I am having difficulty is in trying to insert crypt before LVM. I can set up such a scheme, and put a minimal installation on it, without issues. It's booting into it upon reboot that I can't figure out. Once I load the GRUB crypto, cryptodisk and luks modules, I can mount the crypto partition:
Attempting to decrypt master key... Enter passphrase for hd0,gpt5 (<long hex string here>): <type my password> Slot 0 opened grub> ls ... (crypto0) ...
At this point, GRUB sees the crypto partition as (crypto0). But the GRUB LVM module doesn't see "inside" of the crypto partition, so I don't see the root logical volume within the LVM listed; all I see is (crypto0).
Code: Select allgrub> insmod lvm grub> ls ... (crypt0) ...
Setting it as root doesn't work:
Code: Select allgrub> set root=(crypto0) grub> ls / error: disk `crypto0' not found.
So, How do I get GRUB to "see" LVM inside the crypto partition?
I have a PC104 running debian. I have 3 hard drives (in addition to the one booting) mounted in fstab by UUID. I use the options defaults,error=remount-ro. However, this means that when I boot with the hard drives not attached, I have to press Ctrl-D to bypass when the boot discovers the drives are missing. Is there a timeout commandoption I can add to fstab so that it automatically continues booting even if the hard drives are not attached? I could not find anything on a timeout command. (I tried adding timeout=1000 but no-random guess)
I have a Gateway NV59C09u laptop, I tried running both maverick and the latest beta of natty as live usb's to no avail. It boots fine, but at the first screen the light is so dark that I can't really read anything nor see the mouse pointer, I can just barely make out a window-looking thing. Trying to increase the brightness using my F-keys doesn't do anything.
It's gotta be some kind of graphics related issue, because booting the alternate iso works fine. If I could figure out a way to boot the ubuntu-desktop live image via a different video driver that would probably work, but I'm not sure how to do that (ctrl+alt+f1 does nothing).
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?
I would like to put an image in the background of my console (tty) like done by Gentoo or Suse : I found several tracks to follow, but I would like to have your advice on the best way to do that for Debian.
I'm trying Debian again just for fun after using Slackware for years. When I "su -" on Konsole in Debian I get this for my prompt: Code: darksaurian@darkswamp:~$ su - Password: darkswamp:~# darkswamp is my hostname that I made up when I installed. On Slackware I'm used to it saying: root@darkswamp or something like that. I'm starting Konsole the same way on both: konsole -e $SHELL -l I kind of wish it still said "root" just because I'm used to it.
I know there are many threads regarding this topic.I probably read most of them. At installation time I told Debian to use German keyboard layout (since I am from Germany). Now I want to switch it to American keyboard layout. In X this was no problem. But in the tty consoles I cant get it changed. It does not matter to me if it is system wide or user wide because I am the only user. (system wide would be a little bit more preferrable because it would affect the super user too, I think).I tried dpkg-reconfigure console-data and selecting my desired layout. This changes the Layout to American until reboot
I've been scouring the internet for an answer to this problem. I am using Squeeze and have properly configured Grub2 to set my console screen resolution to 1024x768x32 (as per updating /etc/default/grub to contain 'GRUB_GFXMODE=1024x768x32' and updating /etc/grub.d/00_header to contain 'set gfxpayload=keep') and everything works wonderfully. My resolution is set as it should be. However upon installing Xorg (aptitude install xorg ratpoison), my console resolution gets changed to what appears to be 1280x1024.
I thought that this was due to xrandr, however when I issue:
# xrandr -s 1024x768
only the X resolution is changed. When I then CTRL-ALT-F1 back to the console, the resolution is still at 1280x1024 (I am aware that xrandr only affects X, but I assumed that because my console resolution was correct before installing X there might have been some correlation).
I would like for my console resolution to stay at 1024x768 as per Grub2's configuration and for X's resolution to be at 1280x1024.
PS I also noticed that prior to installing Xorg, my CPU boots up without any screen blanking (only for a second or so). However, after installing Xorg, during the boot process the screen does blank briefly. It is at that time that the resolution gets changed to the 1280x1024 setting.
I installed the base of Debian (only CD 1) without the desktop environment, so it is console only; also I am dual booting with Windows 7 x64 on this Dell Inspiron 1545 laptop... I have also successfully mounted my usb flash drive and CD drive; the one thing I am finding rather hectic is finding a way to connect to my wireless network with a "WPA2 Personal" Security and "TKIP/AES" Encryption with a Dell Wireless 1397 WLAN Mini-Card... I doubt that the drivers are actually installed, and Idk how to install them.Google searches on this yield confusing results, so I need help. So far, the most useful help I have found is the link posted here: http://en.community.dell.com/support-fo ... 29916.aspx but I have no idea on how to install that, if it is even what I need.
Reinstalled Debian Squeeze (64bit/gnome) on my Notebook using Netinstall. Everything worked like always but in the setup instead of typing in a root password as asked to i just pressed enter (in the hope of not having to type in a pw in the console later, just having to press enter then)
When i needed rootpw to install some software (using SoftwareDownloader) the normal loginpw seemed to work, but not in the console. ari@HP625:~$ su - Password: su: Authentication failure
I just installed Debian 6 and need to change the console keyboard layout (I am not running any sort of gui).I installed 'console-data' and ran:# dpkg-reconfigure console-dataThis assigns my Apple keyboard keys perfectly but it won't survive a reboot, which is really important for entering passwords
I'm using the shiki colors theme from the repos right now. "Shiki-Noble" to be specific. When typing something into Firefox's URL bar the internet addresses have got a dark font color and are hard to read on the dark background. Here's a screenshot: FF.jpg
I've had similar issues with other themes and Firefox's URL bar before.
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
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.
After install debian 8, I can't see system start and stop message from console ... How can I enable system message from console in debain 8?
debian 7 output ---------------------------------------------- root@demo:~# service apache2 restart [ ok ] Restarting web server: apache2 ... waiting . root@demo:~#
debian 8 output ----------------------------------------------- root@demo:~# service apache2 restart root@demo:~# <=============================== No message (start or stop)
After an update on squeeze about a week or two ago, my console font turned green. I'm not exactly sure of the timing, because I switch between lenny and squeeze, and some time passed between the update and the reboot in squeeze.
During the update, I was asked if I wanted to keep my altered /etc/grub.d/00_header or take the package maintainer's version. I took the PM's version, knowing I'd lose my edit (set gfxpayload=1024x768x16). When I add that line to the new 00_header, run update-grub and reboot, the console font is the size I want, but it's a dull green. Reminds me of my first computer. How do I get it back to white and keep the 1024x768 resolution?
Currently booting with grub-legacy and chainloading grub2. If I boot entirely with grub-legacy, and pass vga=791, the console font will be white. It doesn't matter which kernel I use. Currently, I'm running 2.6.32-3-686. Same behavior exists if I use 2.6.30-2-686. If I use 1024x768x8 I get a dull gray instead of dull green.
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.
I have been using my system for couple of weeks, and normally update software when the icon is displayed on top bar (gnome). Last couple of days there were updates for X, and I am not sure whether that is the cause of my problem. Once bootup, I get the login screen. When enter the password the login screen keep coming back. there is no error about any password issue, or anything. It keeps prompt me to enter the password.
I could login back the following way.
1. ctrl + alt + F1 , and login with the same username/pwd as for X 2.change to root 3.pkill gdm3 4.exit from root to user privilege 5. startx
The system starts X correctly and no login screen is displayed. I could use the system as usual.
The only thing I did custom to my system was upgrading to the latest kernel (2.6.38) using the source. This was to get support for my hardware, but that was about a month ago. I do not see anything in /var/log (X, demesg etc).
I installed 2.6.38 from backports. It boots OK, and among the start-up messages it says it has started kdm, but then it offers only a console login prompt, no GUI. I assumed (perhaps optimistically?) that newer kernels would be backward-compatible, and that any dependencies on other software would be enforced by the package mechanisms. Running amd64, Squeeze, KDE.
I'm having an issue with my display. Every few minutes or so it dims and a 4 note chord is played.
I have isolated it to: "new-host-5org.kde.powerdevil.backlighthelperQDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave".
And it most certainly is misbehaving. I'm running Jessie 8.2 with the KDE desktop on a HP Elitebook 8730w with NVIDIA Quadro G94GLM graphics.
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
Want to boot from ISO on usb with grub. Both the netinst and hd-media netinst initrds have no findiso/iso-scan/fromiso option that allows me to locate the iso file in question. Is there a boot parameter that does it? Do I need to download a new initrd version? Is there any debian build AT ALL that allows mounting iso from usb?
My system is a three days old Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) with an Intel(R) Core(TM) i7 CPU 60 @ 2.80GHz. It does start, goes through the grub and then spits out strange messages and just freezes before the KDE can be started. I have to restart again, until it really boots everything. This is happening in a random pattern.
I activated bootlog, but as far as I can see, the log only tracks, if the system is really booting. So I also have the dmesg copied into pastebin. These are the only two logs I know, now.
The code of the boot log goes here- Wed Aug 17 10:24:19 2011: Setting parameters of disc: (none). Wed Aug 17 10:24:19 2011: Setting preliminary keymap...done. Wed Aug 17 10:24:19 2011: Activating swap...done.
