From: Jan Rychter <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: video module limited after suspend
Date: Wed, 22 Jun 2005 11:17:09 +0200 [thread overview]
Message-ID: <m2k6kmagyy.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: m28y199cf4.fsf@tnuctip.rychter.com
> Hi,
> I have ACPI compiled into the kernel and various subsystems as
> modules. The 'video' module seems to have a problem, though -- it works
> great on first boot, but doesn't work correctly after a suspend/resume
> (I'm using suspend2, unloading and reloading the video module after
> resuming).
>
> The symptoms are that all subdirectories of /proc/acpi/video/VGA/
> disappear -- which means I can no longer set the LCD brighness. All I
> have is this:
>
> total 0
> -r--r--r-- 1 root root 0 Jun 17 18:25 DOS
> -r--r--r-- 1 root root 0 Jun 17 18:25 POST
> -r--r--r-- 1 root root 0 Jun 17 18:25 POST_info
> -r--r--r-- 1 root root 0 Jun 17 18:25 ROM
> -r--r--r-- 1 root root 0 Jun 17 18:25 info
>
> Any hints?
To narrow things down a bit: I've found out that it isn't really
suspending that matters -- just doing
modprobe video; rmmod video; modprobe video
gets me a system without the CRT, LCD, DVI and TV directories.
As a workaround, I've just compiled video into the kernel (e.g. not
modularized) and I'm fine.
Is anyone actually interested in those bug reports? Should I bother?
--J.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-06-22 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 16:27 video module limited after suspend Jan Rychter
2005-06-22 9:17 ` Jan Rychter [this message]
[not found] ` <m2k6kmagyy.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2005-06-23 16:39 ` Bruno Ducrot
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=m2k6kmagyy.fsf@tnuctip.rychter.com \
--to=jan-jaspcfd0eodbdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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