Toshiba suspend from command line

[Ian Knopke]

I'd like to be able to put my toshiba laptop in suspend mode from the 
command line. Currently I can do it using the wmtuxtime applet in 
Windowmaker, that comes in the toshutils package. Is there a way to do 
this without the applet?

:i


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Toshiba suspend from command line

[Ian Knopke]

Yep, that does it. Thanks! The command is apm --suspend or apm -s. A guy 
sure learns a lot on this list...

I was just starting to poke through the wmtuxtime code. It seems to
accomplish the same thing using an ioctl call and dumping a struct 
directly into /proc/toshiba, while apm works with /proc/apm.

The nice thing about wmtuxtime is that the applet seems to work from a
normal user, whereas apm runs but cannot open the device. Of course it 
works with sudo, but I'd like to automate a shutdown after a task.

So now I have new questions: 

How would I adjust the permissions so apm -s could be run by a normal
user? 
Does this require me to adjust permissions to the /proc directory?  
How would I do that anyways? 
And, for my own curiosity, why can a windowmaker applet cause a suspend
when the normal user can't?

:i



On Sun, 1 Aug 2004, dircha wrote:

> Ian Knopke wrote:
> > I'd like to be able to put my toshiba laptop in suspend mode from the 
> > command line. Currently I can do it using the wmtuxtime applet in 
> > Windowmaker, that comes in the toshutils package. Is there a way to do 
> > this without the applet?
> 
> I'm not familiar with that applet. Are you using APM or ACPI?
> 
> Also, do you mean suspend to RAM, or suspend to disk?
> 
> If you are using APM, see 'man APM' for the list of commands you can use 
> with the command-line client 'apm' for 'apmd'.
> 
> If you are using ACPI, 'echo [n] > /proc/acpi/sleep' where 'n' is the 
> sleep state you desire to put the machine into.
> 
> --dircha
> 
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Onboard soundcard just disappearing...

[Ian Knopke]

Hi Tom,

Are you sure the hardware is still working properly? I have had soundcards 
fail permanently before. 

Also, if it is a PCI card, you might want to open the case and check that 
it is still pushed into the slot properly, or take it out and put it back 
in again. Did you move the computer around recently?

What kind of soundcard is it exactly?

:i



On Wed, 4 Aug 2004, Tom wrote:

> Hey all,
> 
> I was listening to some radio broadcast with MPlayer. I quit MPlayer to 
> start listening some music with XMMS, but without any apparent reason, 
> XMMS couldn't output any sound at all any more. It didn't show the 
> usual error dialog, though ("please check that..."), but since I 
> started it from the command line, I noticed an endless chain of alsa 
> errors ("broken pipes, alsa_free(), failed" is the gist of it as far as 
> I recall).
> 
> In the meantime, I've recompiled my kernel some times and generally 
> tried about anything I could think of (not that much, I'm afraid, since 
> I've never had this kind of audio problem before).
> 
> "alsaconf" no longer detects any PCI or PnP cards, alsamixer of course 
> can't mix anything at all. I was about to wonder whether my onboard 
> sound thingy just exploded or something, but judging from the output of 
> both dmesg (1) and lspci (2), it seems to be there and to be noticed 
> just fine.
> 
> (1) intel8x0_measure_ac97_clock: measured 49260 usecs
> intel8x0: clocking to 48000
> ALSA device list:
> #0: Virtual MIDI Card 1
> #1: Intel 82801BA-ICH2 at 0xa800, irq 17
> (2) :00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM
>   AC'97 Audio (rev 04)
> Subsystem: Asustek Computer, Inc.: Unknown device 8095
> Flags: bus master, medium devsel, latency 0, IRQ 17
> I/O ports at a800 [size=256]
> I/O ports at a400 [size=64]
> 
> At this point, I'm getting out of ideas. Kernel version is 2.6.7. I'd 
> say I've done something wrong compiling it with alsa support, but that 
> can't be it, since it has been functioning for quite some time now, and 
> just suddenly refused to continue to do so.
> 
> Could anybody please help me find out what's wrong here...?
> 
> Greets,
> Tom
> 
> 
> 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]