Re: ACPI hw.acpi.video.* OID's not showing up witth acpi_video on Dell D610

[email protected]
Newsgroups gmane.os.freebsd.devel.mobile,gmane.os.freebsd.devel.acpi
Message-ID <[email protected]>
> Hi John,
>
> I've discovered that if I omit acpi acpi_video and drm from my kernel,
> and load them later on as modules the OID's do appear correctly.

yes, but do they (OIDs, drm, agp) work correctly afterwords?

my experience was that on 6.1-RELEASE if i loaded agp and/or  i915drm
after acpi_video then they wouldnt work, xorg would fail with a message
along the lines of

"/dev/agpgart" no such file or directory

and the sysctls for turning on and off the screen from acpi_video wouldnt
do anything.

as always, YMMV, :-)

johnu

>
> John Baldwin wrote:
>> On Tuesday 20 June 2006 21:25, Colin Faber wrote:
>>
>>> Hello Guys,
>>>
>>> First, sorry for the cross posting, I'm not sure if someone in mobile
>>> or
>>> acpi can help me out with this one..
>>>
>>> In Any event, I'm running a Dell Latitude D610 with FreeBSD 6.1-STABLE.
>>> The last  cvsup on my source tree was Jun 19th.
>>>
>>> The problem I'm having is, for the life of me I can't seem to get
>>> hw.acpi.video OID entries to show up. I've followed every bit of advice
>>> I could  find on the mailing lists and usenet postings.
>>>
>>> I've compiled and installed acpi_video,  ACPI does work and events are
>>> trapped.
>>>
>>
>>
>> drm(4) is using the device node that acpi_video(4) wants to use.  You
>> can
>> either update to -CURRENT where this is fixed, or you can turn off
>> drm(4) so
>> you can use acpi_video(4).
>>
>>
>
> _______________________________________________
> [email protected] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
> To unsubscribe, send any mail to "[email protected]"
>
>


_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.