Koen-
Thanks for the reply. I actually just found the problem, which was a
configuration in the /etc/X11/Xserver which was forcing it to 240x320, and
was fighting the kernel parameters which I had changed to 320x240.
Bill
On Wed, Sep 3, 2008 at 12:06 PM, Koen Kooi <[EMAIL PROTECTED]>wrote:
> Bill Russell wrote:
>
>> Hi - I am new to OpenEmbedded angstrom and I hope this is a good place to
>> post this.
>>
>> I am running the full angstrom X11 demo build on an Atmel at91sam9263 EVB,
>> working fine with the default board.
>>
>> I have replaced the original 240x320 LCD with a bigger 320x240 one.
>>
>> In the kernel board file, I had to reverse the .xres and .yres of course,
>> among other things.
>>
>> [code]
>> static struct fb_videomode at91_tft_vga_modes[] = {
>> {
>> .name = "FG050701DSSWBG02",
>> .refresh = 60,
>> .xres = 320, // orig = 240
>> .yres = 240, // orig = 320
>> .pixclock = KHZ2PICOS(6411),
>>
>> .left_margin = 20,
>> .right_margin = 38,
>>
>> .upper_margin = 3,
>> .lower_margin = 15,
>>
>> .hsync_len = 30,
>> .vsync_len = 4,
>>
>> .sync = 0,
>> .vmode = FB_VMODE_NONINTERLACED,
>> [/code]
>>
>> When I boot I get the angstrom splash and it fills the screen with
>> expected
>> orientation - looks great.
>>
>> Now the problem: when it gets to gpe-dm, the LCD turns to garbage and I
>> get
>> a bunch of divide by zero errors and memory dump, etc.
>>
>>
>> [code]
>> starting GPE display manager: gpe-dm
>>
>> .-------.
>> | | .-.
>> | | |-----.-----.-----.| | .----..-----.-----.
>> | | | __ | ---'| '--.| .-'| | |
>> | | | | | |--- || --'| | | ' | | | |
>> '---'---'--'--'--. |-----''----''--' '-----'-'-'-'
>> -' |
>> '---'
>>
>> The Angstrom Distribution at91sam9263ek ttyS0
>>
>> Angstrom at91-20080806 at91sam9263ek ttyS0
>>
>> at91sam9263ek login: Division by zero in kernel.
>> [<c002c5bc>] (dump_stack+0x0/0x14) from [<c002c5e8>] (__div0+0x18/0x20)
>> [<c002c5d0>] (__div0+0x0/0x20) from [<c0111688>] (Ldiv0+0x8/0x10)
>> [<c012e5c8>] (atmel_lcdfb_check_var+0x0/0x20c) from [<c0121758>]
>> (fb_set_var+0xd4/0x250)
>> [<c0121684>] (fb_set_var+0x0/0x250) from [<c0121de4>]
>> (fb_ioctl+0x154/0x4a8)
>> [<c0121c90>] (fb_ioctl+0x0/0x4a8) from [<c008d47c>] (do_ioctl+0x64/0x74)
>> r7:00000004 r6:00004601 r5:00004601 r4:c3fa6d20
>> [<c008d418>] (do_ioctl+0x0/0x74) from [<c008d6e4>] (vfs_ioctl+0x258/0x288)
>> r5:bec69a38 r4:c3fa6d20
>> [<c008d48c>] (vfs_ioctl+0x0/0x288) from [<c008d754>] (sys_ioctl+0x40/0x64)
>> r7:00000036 r6:00004601 r5:fffffff7 r4:c3fa6d20
>> [<c008d714>] (sys_ioctl+0x0/0x64) from [<c0027e00>]
>> (ret_fast_syscall+0x0/0x2c)
>> r6:00108690 r5:001074e8 r4:00000010
>> Division by zero in kernel.
>>
>> ..more like this..
>>
>> [/code]
>>
>>
>> If I put the .xres and .yres back to original, it works, however the
>> orientation is rotated of course, and a chunk of the screen is black, as
>> would be expected with reversed x and y.
>>
>> So, I believe this is a problem with gpe possibly? The fact that the
>> angstrom splash looks right should mean the LCD is set up right in the
>> kernel.
>>
>> The output of fbset looks like:
>> mode "240x320-0"
>> # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
>> geometry 240 320 240 320 16
>> timings 0 0 0 0 0 0 0
>> accel false
>> rgba 5/0,5/5,5/10,0/0
>> endmode
>>
>>
>> Anyone have any ideas on what might be the issue?
>>
>
> I suspect X11 is doing some ioctl that the lcd driver doesn't like. Have
> you contacted atmel about this already? They should have a clue if the error
> is in the driver or not.
>
> regards,
>
> Koen
>
>
>
>> Thanks!
>>
>
>
>
> _______________________________________________
> Angstrom-distro-users mailing list
> [email protected]
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
>
_______________________________________________
Angstrom-distro-users mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-users
