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

[Andra DuPont]

Martin,
Success...

I edited the /boot/grub/menu.lst file so that the kernel line is now

         kernel /vmlinuz-2.6.27.25-78.2.56.fc9.i686 ro root=UUID=58ef33d6-bd02-4a2c-830b-2515ff9368ed rhgb quiet acpi_osi=Linux acpi_backlight=vendor

On the first reboot, the boot process paused for about 30 seconds at
the "starting udev" stage. The screen went dim, but when the server
was fully booted, the fn+F6 key worked to raise the brightness!

On second reboot, the boot process did not pause, and the screen remained bright. Issue solved.

You may want to consider adding this to future server releases, assuming that it doesn't
cause problems on other platforms.

Andy


On Dec 2, 2010, at 11:12 AM, Andra DuPont wrote:

> Martin,
> Looking at some Fedora sites, I see where there are many post of problems with the Eee PC
> and backlighting. Based on what I read, I decided to update the BIOS, and although it didn't fix the
> problem completely, the screen now has about 10% brightness, so I can actually read it if the room
> is not too bright.
> 
> some people have reported a fix in fedora that uses grub kernel options:
> 
> 	acpi_osi=Linux acpi_backlight=vendor
> 
> I will try putting these in the /boot/grub/menu.lst file.
> 
> Is this the right place? Any suggestions?
> 
> Andy
> 
> 
> On Dec 2, 2010, at 10:02 AM, Andra DuPont wrote:
> 
>> Martin,
>> Thanks for the suggestion. I will run lsmod.
>> 
>> After sleeping on it, I think the conflicting driver must
>> be related to the backlighting on the display, not the graphics processor. The Acer and Asus have the same 
>> graphics hardware, but the displays are different.
>> 
>> Andy
>> 
>> On Dec 1, 2010, at 10:43 PM, Martin Langhoff wrote:
>> 
>>> On Wed, Dec 1, 2010 at 8:14 PM, Andra DuPont <andradupont at gmail.com> wrote:
>>>> So apparently one of the drivers that is installed is conflicting with the screen brightness.
>>> 
>>> Your analysis seems 100% correct.
>>> 
>>> I'd suggest -
>>> 
>>> - run lsmod, it'll tell you what modules are being loaded - one of
>>> them will be controlling your video card -- for example an i915 card
>>> loads intel_agp, drm and i915
>>> 
>>> - name those modules in /etc/modules/blacklist.conf so they don't get loaded
>>> 
>>> but I agree with you, it's very strange that you need to go through this dance.
>>> 
>>> 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
>> 
>