[Server-devel] XS on ASUS Netbook - Display Problem

[Andra DuPont]

Martin,
Removing the first line from the 80-drivers.rules keeps the screen from going dark, but as best I can tell, it also keeps most of the drivers from being installed. For instance, the ethernet ports are not found when the line is omitted. The line is:

	DRIVER!="?*", ENV{MODALIAS}=="?*", RUN{ignore_error}+="/sbin/modprobe $env{MODALIAS}"
SUBSYSTEM=="pnp", DRIVER!="?*", ENV{MODALIAS}!="?*", \

As best as I can tell, the command uses modprobe to install the appropriate drivers from the modules.alias list in /lib/modules/... directory.

So apparently one of the drivers that is installed is conflicting with the screen brightness.

Do you have any idea where to go from here? I am really surprised because the Acer Aspire One this I'm using in Kenya now did not have this problem, and it has the same Intel GMA 3150 graphics processor as this ASUS Eee PC.

Andy


On Dec 1, 2010, at 1:58 PM, Andra DuPont wrote:

> Martin,
> 
> If I remove just the 80-drivers.rules file from /etc/udev/rules.d
> then the screen does not dim. I actually started in that file
> earlier this morning and tried removing some lines in the graphics
> area but that did not solve the problem.
> 
> I will check into the driver.rules file further this evening and try to
> determine the specific rule that is causing the problem.
> 
> Andy
> On Dec 1, 2010, at 1:15 PM, Martin Langhoff wrote:
> 
>> To capture dmesg output, do
>> 
>>  dmesg > dmesg.log
>> 
>> and now you'll have a dmesg.log file.
>> 
>> Not sure if your rule files are actually to blame, but it's a good
>> starting point.
>> 
>> 
>> 
>> m
>> 
>> On Wed, Dec 1, 2010 at 12:59 PM, Andra DuPont <andradupont at gmail.com> wrote:
>>> Martin,
>>> Attached is the /var/log/messages file
>>> 
>>> Output from dmesg seemed to show things looking normal but I couldn't see the initial output as it scrolled off my screen. What command can I use to have it show me a page at a time?
>>> 
>>> I plan on removing the rule files methodically to isolate the conflicting rule. Thoughts?
>>> 
>>> Andy
>>> 
>>> 
>>> 
>>> 
>>> On Dec 1, 2010, at 11:57 AM, Martin Langhoff wrote:
>>> 
>>>> On Wed, Dec 1, 2010 at 10:03 AM, Andra DuPont <andradupont at gmail.com> wrote:
>>>>> I have installed XS 0.6 on an ASUS 1005PEB Eee PC. The server is running fine except that the screen went dark at server start-up right after the "starting udev" was displayed on the screen. My screen stays dark and can only be reset by restoring the default bios settings. Then it gets set dark again at server startup at the "starting udev" process.
>>>>> 
>>>>> Any idea what rule or other change I could make to keep the screen from going dark?
>>>> 
>>>> Strange! Can you post /var/log/messages and the output from dmesg from
>>>> that server, right after booting?
>>>> 
>>>> cheers,
>>>> 
>>>> 
>>>> m
>>>> --
>>>> martin.langhoff at gmail.com
>>>> martin at laptop.org -- School Server Architect
>>>> - ask interesting questions
>>>> - don't get distracted with shiny stuff  - working code first
>>>> - http://wiki.laptop.org/go/User:Martinlanghoff
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -- 
>> martin.langhoff at gmail.com
>> martin at laptop.org -- School Server Architect
>> - ask interesting questions
>> - don't get distracted with shiny stuff  - working code first
>> - http://wiki.laptop.org/go/User:Martinlanghoff
>