From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: mutex@kerneli.org
Cc: Michel D?nzer <michel@daenzer.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: new ATI sleep code freezes
Date: 05 Jun 2003 18:47:53 +0200 [thread overview]
Message-ID: <1054831673.813.37.camel@gaston> (raw)
In-Reply-To: <20030605163550.GL1982@heliosphan>
On Thu, 2003-06-05 at 18:35, mutex@kerneli.org wrote:
> On Wed, Jun 04, 2003 at 07:15:55PM +0200 or thereabouts, Benjamin Herrenschmidt wrote:
> > Also make sure you have APM emulation working (check XFree log to see if it found & opened the APM device)
>
> from my XF86Config file...
>
> (WW) Open APM failed (/dev/apm_bios) (No such file or directory)
>
> But my kernel config says...
> CONFIG_PMAC_APM_EMU=y
>
> The only thing unusual is I am running devfs..
Poor boy... ;)
> so i checked /dev
>
> heliosphan dev # find . -name *apm*
> ./misc/apm_bios
> ./apm_bios
>
> /dev/misc/apm_bios has perms:
>
> crw------- 1 mutex root 10, 134 Dec 31 1969 apm_bios
>
> are those normal permissions ? Also, I'm running an enlightenment battery applet which afaik uses apm layer to report battery level. So something has to be working.
> Dave
I don't know wtf with devfs & perms, but the problem is here, once you
fix that, it should work much better ;)
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-05 16:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 15:41 new ATI sleep code freezes mutex
2003-06-01 19:36 ` Michel Dänzer
2003-06-04 16:28 ` mutex
2003-06-04 17:15 ` Benjamin Herrenschmidt
2003-06-05 16:35 ` mutex
2003-06-05 16:47 ` Benjamin Herrenschmidt [this message]
2003-06-05 20:20 ` Michel Dänzer
-- strict thread matches above, loose matches on Subject: below --
2003-06-05 21:16 Mich Lanners
2003-06-07 19:28 ` mutex
2003-06-07 20:14 ` Michel Dänzer
2003-07-24 3:24 ` mutex
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1054831673.813.37.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=michel@daenzer.net \
--cc=mutex@kerneli.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).