I came back to debian after trying many others because it installed flawlessly and worked. I'm on the testing channel and upgrade nearly everyday and after a recent upgrade my xsession (Xfce4) display won't wake up any more after I close and re-open the lid. I know the box is awake because I can go to a ctr-alt-fn console login and use it normally. How can I track this down? And is there some way I can restart the gui display from the console without losing what was running before I shut the lid? Right now the only way I can recover is to restart the computer.
I am trying to install Ubuntu 10.04 on my Compaq CQ50-215CA laptop. But, instead I am seeing a blank screen. This laptop has Geforce Nvidia 8200G M video card.Not sure whether it is related to the video card or not, but thought it is better to get tips from people who were successful in installing on this type of laptop.
I installed Ubuntu 10.4 on my laptop compaq presario CQ50 I cannot go online, because the drivers does not exist ? where can I download them? the wireless flash blue by the way, and it was working before I switch to Linux is there anyway to find driver for my wireless compatible?
I upgraded from 10.11 to 11.4 and as far as I can see most things work as they did before. However, I have my machine to "go to sleep" (is that suspension or hibernation?) after 2 hours and when I, now after the upgrade, press the "wake up button" the machine fires up but the screen remains down. Ie, the screen is actually not receiving any signals from the computer? Any setting I can change? It worked fine with 10.11!
I have a HP Compaq nx9010 laptop with 1 gig of memory and 128mb being dedicated to video memory. The graphics chip is ATI Radeon IGP 345M.
I can only set my resolution to 1024 X768. If I try to change it to any other size or try to play any games, the video has millions of jerky horizontal lines going through it. If I hookup an external monitor the video works just fine. Being new to linux and even newer to installing on it laptops, can anyone tell me what if any thing can be done to correct this. I am running Ubuntu 10.4 LTS.
I am hosting a home server to make developing stuff easier. And because I don't need my server all day and night I automatically start and shut it down. For starting I use Wake-On-Lan (etherwake) and to shut it down I am using my RaspberryPi. Finally I have a problem doing that: When I use WOL to start my home server it works perfect. But when I try to shut it down, I have to do that twice. After the first shutdown it restarts automatically even when no WOL-Package is sent.
I am using Debian 8.1 Mate as os.
My stop script is:
Code: Select allsshpass -p<password> ssh root@server.home.lan shutdown -h now
I have installed Debian 8.1 with KDE desktop on Lenovo t431s with intel HD4000 graphics.
When using it with dual monitor configuration, I experience the problem when I put system to sleep (by closing the lid), then remove the external monitor cable (from miniDP port) and then try to wake system from sleep. The login screen freezes and I am unable to move the mouse or type in credentials. In case I had music player running I can hear the music after system wake , but it shutters while playing.
This does not happen on some other distributions, but the problem is that I very much like my current setup and I would like to fix this problem and keep it.
I do not know if this problem is due to KDE or KDM or it's Debian base.
I have installed Debian Jessie (<-- brilliant OS ) on my uncles Laptop (it is a Thinkpad E540) with Cinnamon as desktop environment. The installation was no problem. Everything apart from one minor thing works nicely. The minor thing however is the following:
I don't know what it is, but when I don't use a particular usb port for a while and then try to plug in a usb stick or a wacom tablet, it doesn't get recognized, it doesn't show up when I use f.e. Code: Select alllsusb. When I close the lid of the laptop and open it again, then the particular usb device gets recognized and cinnamon asks me what to do, f.e. open a folder and show the content of the usb stick I have plugged in. Because of the success on two other laptops I use the following
to save power on the Thinkpad (this is in no way my service script, I tuned everything using powertop in the terminal after having had logged in, the script above stems from a brilliant user here on the forum). Could it therefore be autosuspend that is not working properly here?
I recently switched back to Debian after getting fed up with Ubuntu. The one feature that I haven't been able to get back since the switch is Wake on LAN.If I turn on the computer and watch tcpdump, I can see the packets hitting my machine. I don't think it's a router configuration issue.If I shut down from windows, WOL works.Another sign that it's not a networking or BIOS thing.Here's some stuff I've tried:When I boot up in linux, if I run ethtool eth0, it tells me that wake is set to g (which every guide I've read says is correct).Just in case, I added "post-up /usr/sbin/ethtool -s $IFACE wol g" to /etc/network/interfaces (as shown here: ewtopic.php?f=5&t=42049&p=244736&hilit=wakeonlan#p244736). Also added same thing for post-down.
In /etc/init.d/halt, I changed NETDOWN to no (also from previous guide) to keep my eth card from being shut down.Also changed /etc/init.d/networking to exclude eth0 (as documented in Added "pre-down false" to /etc/network/interfaces.. trepid+wol), to keep eth0 from being shut off.Anyway, I'm guessing that either there's another script somewhere shutting off eth0 or I'm completely wrong in assuming that's the problem. I've been googling this problem for a couple weeks now and I'm totally out of ideas.
I'm am able to WOL my computer when it has been halted (or shutdown, which is basically the same thing for the problem I'm facing). The problem comes when I try to WOL the computer when it is suspended or hibernated. Then, it does not work.
I've been investigating for a while and have found that when halting, the following is done in the /etc/init.d/halt script:
[code]...
But I don't know which script must be modified in case I want the network not to be brought down when the computer is suspended or hibernated.
Suspend worked before I completely reinstalled Testing from scratch. Now it seems to suspend OK, but when it tries to wake up it fails. Details here: [URL]
I have an Acer 1551 4755, with Debian Squeeze. Normally my Debian Squeeze installations and suspending work fine on my other 2 laptops. For some reason this one is troubled. I can put into sleep with "pm-suspend" or "pm-hibernate" but the thing is that my laptop never wakes up. I endup restarting.
I use my laptop connected to an external monitor, so I would like it to wake up from suspend with a wireless keyboard. I could manage to do it when the lid is open, however, when the laptop lid is closed, it doesn't. So I need to open laptop lid each time and it is annoying.
This is how I make it wake up with wireless keyboard:
Is there a config file to toggle whether the screen is locked after hibernation? I looked all over preferences but if it's there, I missed it. In Ubuntu, the screen was always locked after waking up. In Squeeze, it's going directly to desktop. It's not a biggie but you never know when someone might try to access your account so I kind of liked that it would wake up locked. Maybe it's doing that because I'm the only user on the system?
i have recompiled kernel on my netbook (lenovo s10-3t).suspend works correctly but then i cannot wake up. i think i just missed some kernel options.what options must be set for suspend/wake up?
Have been working on a compaq 610 (64-bit) wireless drivers. I have installed all drivers available for wireless devices from its repo but still, the wireless device isn't working. it does fine in windoz.
when I try to install squeeze on my old compaq nc6000 laptop, installation will freeze at "detecting network hardware"; if I skip the networking steps, it freezes at the "detect harddisk" step.
It's the same behaviour, whether I try to install in text mode or graphic mode, expert install, normal install, whatever.
I also tried different debian ISOs. Same thing.
The screen just stays blank (a blue screen that is in text mode). When I press alt-F4 it reads:
Code: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
That message seems to appear each time my installation freezes.
Searching the web for the message yielded known problems with the kernel vfat driver, which will not be solved. However, nobody else out there seems to have trouble getting their installs done.
So here's my question:
Can I assume this behaviour does have something to do with my windows partition?
As in: Once I have removed my windows partition on the laptop, everything will be cool?
I have a Compaq 8710w and after upgrading to the latest Debian/testing (Linux version 4.1.0-1-amd64)the fan runs at full speed all the time. There seems to be something strange with the temperatures reported by temp4, it is stuck at 100 degrees.:
I heard after I install debian, it could display Chinese information normally without any further work, but I have trouble to see all the Chinese characters.
So I googled and installed Chinese fonts, use dpkg-reconfigure locales to add Chinese support, but none of them work.
I'm having trouble with Debian 8 and using my dual monitor setup. Whenever I install a desktop that uses lightdm as a display manager (XFCE, MATE, Cinnamon) the login screen is cloning the two monitors rather then extending the desktop. I don't have the issue with gnome 3 (gdm) or kde (kdm). I tried installing Slim as well, but that has the same cloning issue.
I had a similar issue with g the XFCE environment, but I was able to resolve it by installing arandr and configuring the monitor layout. Upgrading from Stable to Testing also fixed the XFCE issue with the newest version of XFCE. Unfortunately I still have the display manager issue (lightdm/slim) in Testing as well. I would prefer to use XFCE but I'm willing to move to Gnome 3/KDE if need be to resolve the issue with the login screen.
So when my laptop resumes from suspend (haven't tried hibernate) the screen is black (and stays black) until I hit ctrl-f7is this because its opening the wrong display, or because ctrl-f7 'wakes up' X, or ??? it's not that big of a deal, now that I know how to get back to the X session (at first I thought it was "frozen")but it is sort of inconvenient, is there a way to make the behavior "automatically go back to the x sesson on resume" ?
I'm using a laptop as a mini server, but I haven't figured out how to sleep the display. I am not using the gnome desktop - I shut the lid but the display stays on.
ps - I should note - this is Debian 5.0.3 PPC version running on a PowerBook G4
