Debian Configuration :: Cannot Check Battery Status In Jessie ASUS EeeBook X205TA
Jul 22, 2015
I use jessie-32bit of kernel 4.1.3 on ASUS EeeBook X205TA. But it doesn't recognize buttery status.Result of my investigation, the incomprehensible ponts is below.
・"acpi -b" outputs no information.
・There is not "battery" directory in /proc/acpi/. (button only exists.)
The following is my system informations.
Code: Select allacpi -V
Adapter 0: on-line
Cooling 0: intel_powerclamp no state information available
Cooling 1: Processor 0 of 10
[code]...
I want to check battery in console and fluxbox Desktop.
I use jessie-32bit of kernel 4.1.3 on ASUS EeeBook X205TA.
And I use Japanese Model. There are key 【,|】and【,_】in this model keyboard. [URL] .... But my system does not recognize the two keys.
In /etc/default/keyboard, edit below XKBMODEL="jp105" XKBLAYOUT="jp"
I can japanese layout, but the two keys is nonreactive.
And i can not dpkg-reconfiguration keyboard-configuration. It's no response. No appear.
Code: Select all#dpkg-reconfiguration keyboard-configuration update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
I use jessie-32bit of kernel 4.1.3 on ASUS EeeBook X205TA.
And I use Japanese Model. There are key 【,|】and【,_】in this model keyboard.
But my system does not recognize the two keys.
In /etc/default/keyboard, edit below XKBMODEL="jp105" XKBLAYOUT="jp"
I can Japanese layout, but the two keys is nonreactive.
And I cannot dpkg-reconfiguration keyboard-configuration.
Code: Select all#dpkg-reconfiguration keyboard-configuration update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
I am the author of an internet radio for the Raspberry PI originally running on Debian Wheezy. The radio (radiod) service is started and stopped using the usual service commands:
service radiod start|stop|status
Since upgrading to Debian Jessie the service status and stop routines in my radio daemon are no longer called.
For example:
# service radiod status ● radiod.service - LSB: Raspberry PI Radio Daemon Loaded: loaded (/etc/init.d/radiod) Active: active (running) since Thu 2016-03-31 20:17:07 CEST; 15h ago Process: 380 ExecStart=/etc/init.d/radiod start (code=exited, status=0/SUCCESS) CGroup: /system.slice/radiod.service └─603 python /usr/share/radio/ada_radio.py start
If I call my program (which runs as a daemon) I see the status message from my program
# ./radiod.py status radiod running pid 603
I have established that service stop never calls my program routines to shutdown the radiod daemon when the system is rebooted (I see that from my log files).
The reboot hangs for about 5 minutes whilst stopping the radiod service (because stop never calls my stop routines).
Below is my radiod script, which is fairly conventional, and which has been working all the time until I ported to Debian Jessie.
/etc/init.d/radiod #!/bin/sh # ### BEGIN INIT INFO # Provides: radiod # Should-Start: # Should-Stop:
since I am on a Dell inspiron 1545 laptop, being able to display my battery charge is critical. After some extensive googling, I found I need a command 'acpi', which does not exist on my computer. I cannot seem to find it in the packages database; the closest thing being 'acpi-support' apt-get install also can't find it.
I tried cat /proc/acpi/battery/BAT0/state, but that only shows me if the battery is discharging or charging and doesn't give me an actual percentage.
I'm using debian testing on my Asus UX305. When my laptop is connected to power, the power notification still shows "discharging". And The battery part of the laptop feels unusually hot.
while connected to power, "acpi -b" gives me this information: Battery 0: Discharging, 98%, discharging at zero rate - will never fully discharge.
This problem was reported by some ubuntu users too: [URL] ....
I recently bought a used Asus eee 1001PX. It came installed with some spyware called windows which I replaced with jessie. Everything works great but one thing. When I plug in headphones I get no sound in the headphones. If I have some audio running and plug them in while it's playing it doesn't cut the audio from the built in speakers off like it should do. If I start and look at Output Devices in pauvcontrol it seems like it at least recognizes that I have headphones inserted.
I didn't have a chance to test if the physical audio jack was broken while it had Windows running on it but assuming that it's not physically broken, what might be wrong? I know very little about audio, alsa, pulse and that kind of stuff so I hardly know even where to start.
Some info: Code: Select alllspci -v
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Device 8437 Flags: bus master, fast devsel, latency 0, IRQ 44 Memory at f7cf8000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
I'm using Debian squeeze and for an assignement, i have create 2 virtual pdf cups printers. Both are working very well. To test the different administion command; i try to disable one of the printer and move his queue file to the second one. I'm able to do it easily.
Now, i wish to write a bash script that wil test the status of the printer. So that,if the printer is disable, it just execute the "move" script. Is there a way to know the status of a cups printer and use that information in a script?
For example, a command/function that can return "O" is the cups printer is enable and "1" if not.
Is there any way to allow normal fsck boot-time checks when running on battery power? After looking around, the only solution I've seen is to manually alter the /etc/init.d/checkfs.sh and /etc/init.d/checkroot.sh files and remove the AC power check. There must be a better way than that surely?
Having downloaded 11.4 Gnome, finding it did not install I bought it on DVD from ebay, when trying DVD installation my PC is displaying: There is a problem with the configuration server (/usr/lib/Gconf-sanity- check - 2 exited with status 256, I would like to install this rather then just run it off disk
I have looked all over the place but I can't find if this is possible. I am running Debian 6 as a media server (SMB) and it is tied to a UPS, I used gnome power management to set up a low battery shutdown but this UPS also is powering another embedded computer. So, I was wondering if it was possible to have a script run (to log in and shut down the embedded system) before gnome power management shuts down the Debian server. I know I could probably get it to run on every shutdown, but I am looking for low power only.
It seems like ifconfig used to show which DNS servers were being addressed, but something has changed, I need to know whether I am referencing what I think I am... I have search this forum, googled, and come up empty... did the metrics go away with 8.2? Was I dreaming at 7.5?
I installed Debian Jessie on my Hummingbaord. I use it with apache, owncloud and minidlna but after some days i rebooted the system and then i can't log in with SSH anymore.
The message I get:
Access denied Using keyboard-interactive authentication. Password:
And this again and again, although I enter the right password. If I login directly on the Hummingboard all works normally...
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 ..
I have a relative fresh install of jessie in which I face a high cpu usage of java (top shows about 165% CPU and 12% MEM). The problem occurs right after booting the computer. These values stay constantly high for days if I leave the box running. This happens even if the computer is just sitting there without doing anything.
I have to kill java to go back to normal. So, when I do a Code: Select allkillall -KILL java the problem goes away. After that it doesn't reappear and I can use all apps installed without a problem.
Currently I am based on openjdk Code: Select allupdate-alternatives --display java java - auto mode link currently points to /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java - priority 1071 slave java.1.gz: /usr/lib/jvm/java-7-openjdk-amd64/jre/man/man1/java.1.gz Current 'best' version is '/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java'.
But I have also tried the SUN version with the same result.
Where to look to find more information on what exactly java app is using so much resources and how I can solve it? I guess I could just put somewhere in rc.d a kill java command and forget about it but I would really like to find out whats going on...
When i'm tried google there is lots of bootlogd related document there. [URL] .... Yes there is documentation. But I'm only need "enable boot logging","reading boot log". Bootlogd not worked on jessie/stretch.
I got a brandnew Acer Travelmate Timeline X (13"). I do not really know if this is the right topic for my problem. But here it comes: The Acer uses a special smart battery with special chips in it controling the powermanagement of the battery and the system. In general there is a kernel module to handle this (sbs). But for me this does not work.I am using Squeeze and it does not recognize the battery. It always acts like being on AC power. If I unplugg the AC it runs with the battery till it is empty. But the ACPI can not recognize the battery and can not read how much lifetime it has. I tried the reassambling method. But this method does not work for me. Nevertheless I think the reassambling method does not run because there is no more developing on it because of the kernel modul.
What can I do? Will I have to wait till a new workaround of sbs comes out, which can handle my battery? I read about a BIOS hack that disables the smart battery functions. Should I try this? But I am not really firm in that kind of stuff and I will loose the guarantee. Has anyone got an idea?
I have a strange problem with the ACPI in my laptop, the problem start some days ago, I don't remember exactly the day.
The first symptom is with de Gnome Power Manager, only show me when I disconnect de AC power, but when connect it again the Power Manager icon disappear and the energy battery stay in the same value.
After search for a while, all the post I read talking about the /proc/acpi/battery directory, but this directory not exist on my laptop.
I have a laptop Lenovo G460. My OS is Squeeze. My Kernel is 2.6.38-bpo.2-amd64, because the 2.6.32 version of the kernel don't recognize well my audio card.
I can't attach the dmesg and the lsmod output because I receive a message "Sorry, the board attachment quota has been reached.", both file are compressed.
Configuring gpsd with Wheezy was a breeze. Just had to run "sudo dpkg-reconfigure gpsd", answer a few questions, and it worked like a charm. With Debian Jessie the following happens:
tsi@sxf-tsi:~$ sudo dpkg-reconfigure gpsd Warning: Stopping gpsd.service, but it can still be activated by: gpsd.socket Creating/updating gpsd user account... tsi@sxf-tsi:~$
How does one bring up the gpsd configuration dialog with Jessie?
I've after latest jessie update a problem with service samba restart. If I use "service samba restart", there is a timeout (after long time) and error.
Output of "systemctl status samba.service":
Code: Select all● samba.service - LSB: ensure Samba daemons are started (nmbd and smbd) Loaded: loaded (/etc/init.d/samba) Active: failed (Result: timeout) since Mo 2014-10-20 02:16:57 CEST; 7s ago Process: 6205 ExecStart=/etc/init.d/samba start (code=killed, signal=TERM)
Okt 20 02:16:57 server systemd[1]: samba.service start operation timed out. Terminating. Okt 20 02:16:57 server systemd[1]: Failed to start LSB: ensure Samba daemons are started (nmbd and smbd).
[Code] ....
Whats going wrong. "service samba restart" should bring no error message if the service is not running previously.
I am having trouble using touch pad in jessie. My touch pad was ok when it's in wheezy but after i updated to jessie, i can't really get used to it.
I don't know whether i setting it up wrongly, sometimes, my touchpad will keep dragging, without releasing. And if I click the bottom right of the touch pad, it's not right click; instead i have to use two fingers.
etc. So how can i change to back to a more traditional usage? Also, do jessie have a setting like ubuntu saying disable touch pad while typing?
After installing Jessie, apt-get gives me a huge list of packages with the suggestion to autoremove them. Now, I've tried auto-remove once and was left with a naked Gnome, so I was wondering if there's another way to find out which packages I should keep and which I can safely remove. Is it safe to delete packages that cannot be found using the search function for the stable release? I checked them one by one here URL....How about linux images that won't appear in the above search?
Upgraded webserver to Jessie as an upgrade to Wheezy produced errors, and before reboot everything was up and running, but as all upgrade docs and info I read, I rebooted the server. However it never came back. I have the original backup files before I did the Wheezy upgrade. I also have access by Rescue to the server.Made a back up of critical files and have a 24GB tar file and I can connect by SFTP.
how to check the Debian files... Grub etc.. I would prefer to find the issue than start again.I am not able to sudo from Putty. I cannot run apt-get update. I did go to chroot, but then I get unable to resolve host errors and Could not open lock file because Permission denied errors and asking if I am root.There is information by googling for start up issues, but as I am working remotely with a Rescue set up, a lot of the commands I see and have tied do not work.
A few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.
umount My passport fdisk -l (to see device name) mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4 dmesg | tail [ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found [ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through
After changing my video cards from gigabyte HD5450 and saphire X550 to two saphire r7 240s one of my debian installs no longer supports rotating the monitors either with 'Monitor Settings' or xrandr. The only difference between these 2 Jessie installs is that one was upgraded and the other one was fresh. The problem is with the upgraded one. On the fresh installed debian I just put the ati proprietary driver so I won't do further testing on it but xrandr was working fine on it before that.
I tried going over the ATIHowTo [URL] .... and everything looks good. Tried purging the non free firmware and reinstalling. I verified the version numbers of libxrandr2 and kernel of both installs. It is either some scrap left over from wheezy or a configuration file I am not aware of.
So what actually happens is xrandr does not say anything, blanks out all windows on the screen with only their background color and title bar showing, changes the lxpanel to its background pattern except for 2 blanked out boxes almost to the right of the screen( I have 10 tray icons there before it blanks), activates the screen I wanted to rotate with the proper rotation. On my main screen I can't click on anything. On the rotated screen I can right click and I get my openbox right click menu like I do on my main monitor before the command but when I try to run something nothing happens. The only way I can get out of this situation is to go to ctrl-alt-f1, log in as root and type 'service lightdm restart'.
Both of these monitors are connected to the primary video card, an ati r7 240 saphire. The main one is on vga and the other one is on DVI. I also have another monitor connected to HDMI but it's not being used. I have yet another monitor connected to the VGA of the secondary GPU I don't think it's a problem is it? I tried not using 'xrandr --setprovideroutputsource 1 0' and it still did the same thing.
I tried just launching openbox with no LXDE and it did the same thing.
Also another strange thing is when I stop the lightdm service and try to 'startx' or 'xinit' my screens go blank; numlock, control-alt-delete and control-alt-f1 do nothing and the only thing I can do is an emergency REISUB. I didn't configure this install to use startx or xinit yet but should it really lock up my system?
On the affected system my script looks like this (I already did this step by step and the 'rotate left' line is causing the problem):
