From: "Georg C. F. Greve" <greve-mXXj517/zsQ@public.gmane.org>
To: Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: VGA patch by Bruno Ducrot -- no success yet
Date: Fri, 13 Feb 2004 00:04:52 +0100 [thread overview]
Message-ID: <m3r7wzx5kb.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <20040212223706.GA13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> (Bruno Ducrot's message of "Thu, 12 Feb 2004 23:37:06 +0100")
[-- Attachment #1.1: Type: text/plain, Size: 2917 bytes --]
|| On Thu, 12 Feb 2004 23:37:06 +0100
|| Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote:
>> cat ./LCDD/brightness
>> <not supported>
bd> For an LCD device, that not very fun unfortunately :(
I'm not sure how these relate to each other, but we're talking ASUS
M2N here, which uses the acpi4asus code, in which
/proc/acpi/asus/
|-- brn
|-- disp
|-- info
|-- lcd
`-- mled
exist. And therefore
/proc/acpi/asus/brn
normally regulates background display brightness for the LCD, while
lcd toggles the backlight on/off. Unfortunately both have no effect on
the dead screen after S3.
Don't know whether/how this interacts with your code.
>> cat ./ROM
>> <TODO>
bd> Well, that need to be done as said, even though in fact that is
bd> really uncommon though.
I know -- just wanted to give you the complete picture. .)
>> Feb 12 21:54:30 myhost kernel: Uninitialised timer!
>> Feb 12 21:54:30 myhost kernel: This is just a warning. Your computer is OK
>> Feb 12 21:54:30 myhost kernel: function=0x00000000, data=0x0
>> Feb 12 21:54:30 myhost kernel: Call Trace:
>> Feb 12 21:54:30 myhost kernel: [check_timer_failed+99/101] check_timer_failed+0x63/0x65
>> Feb 12 21:54:30 myhost kernel: [del_timer+26/135] del_timer+0x1a/0x87
>> Feb 12 21:54:30 myhost kernel: [_end+541737980/1069013880] ehci_stop+0x73/0xde [ehci_hcd]
>> Feb 12 21:54:30 myhost kernel: [preempt_schedule+42/67] preempt_schedule+0x2a/0x43
bd> Is the system more stable without preempt, btw?
I'll try... although it shouldn't make a difference, or should it?
>> Hope this helps with the debugging... :-)
bd> Yes, at least for the latter oops, I will be gratefull if you
bd> send me a brown bag...
There is always one of the little suckers that you didn't think of. .-)
bd> --- video.c 2004/02/12 22:26:41 1.1
bd> +++ video.c 2004/02/12 22:34:21
bd> @@ -617,6 +617,9 @@
bd> if (!dev || count + 1 > sizeof str)
bd> return_VALUE(-EINVAL);
bd> + if (!dev->brightness)
bd> + return_VALUE(-ENODEV);
bd> +
bd> if (copy_from_user(str, buffer, count))
bd> return_VALUE(-EFAULT);
Yeah, that should get rid of that one.
But since it probably won't help bringing the display back to life I
won't recompile for that fix, I guess.
>> P.S. Oh yeah, machine is ASUS M2N, Intel 855GM, more info:
>> http://bugme.osdl.org/show_bug.cgi?id=1774#c3
bd> Thanks for testing!
Thanks for tackling that issue!
When you have another version you think might help with the dead
screen issue or need more input, please let me know. I don't really
have a lot of time but compiling a kernel by the side is usually
possible. :)
Regards,
Georg
--
Georg C. F. Greve <greve-mXXj517/zsQ@public.gmane.org>
Free Software Foundation Europe (http://fsfeurope.org)
Brave GNU World (http://brave-gnu-world.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 258 bytes --]
next prev parent reply other threads:[~2004-02-12 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 21:38 VGA patch by Bruno Ducrot -- no success yet Georg C. F. Greve
[not found] ` <m3u11wnflb.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-02-12 22:37 ` Bruno Ducrot
[not found] ` <20040212223706.GA13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-12 23:04 ` Georg C. F. Greve [this message]
[not found] ` <m3r7wzx5kb.fsf-glUV91rXKAHWIjgkaejU9x2eb7JE58TQ@public.gmane.org>
2004-02-12 23:22 ` Bruno Ducrot
[not found] ` <20040212232230.GC13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-13 10:13 ` VGA patch by Bruno Ducrot -- no success yet (includes request to our Intel people) Georg C. F. Greve
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=m3r7wzx5kb.fsf@reason.gnu-hamburg \
--to=greve-mxxj517/zsq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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