[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-28 Thread Matthew Garrett
Ok, that should definitely be enabled. ** Changed in: usplash (Ubuntu) Status: New = Invalid ** Also affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New = Confirmed ** Summary changed: -

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-27 Thread alek du
Matthew and Amit, Updates from my test, I guess this issue was root caused: After one half day tracing and testing, I found actually this issue was caused by another config option CONFIG_VM86 not setting. usplash source code ~/svgalib/src/lrmi.c (Linux real mode interface) with entry function

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-23 Thread Matthew Garrett
-generic only set CONFIG_FB_VESA for a short time due to a mistaken reversion of a patch. What options are you passing to the kernel on boot? CONFIG_FB_VESA will only do something if you pass the vga= argument, which you shouldn't be doing. -- usplash could not run on Ubuntu UME flavored kernel

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-23 Thread alek du
Matthew, no I did not pass any vga= parameters to kernel. So I have to re-do the test and find again which kernel config option broke the usplash. Once confirmed, I would post resut here. -- usplash could not run on Ubuntu UME flavored kernel https://bugs.launchpad.net/bugs/133557 You received

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-22 Thread alek du
By default Ubuntu linux-generic kernel already set CONFIG_FB_VESA=y, and this works fine both for suspend/resume and usplash. We found for UME kernel, this option was not set and usplash will show a red dead screen during booting. Our test board is Crown-beach. -- usplash could not run on

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-21 Thread Matthew Garrett
No, usplash has its own vesa handling code. Setting CONFIG_FB_VESA to y is a bad plan if you want suspend and resume to work reliably. Could you provide more information about your platform and the observed failure? ** Changed in: linux-meta (Ubuntu) Assignee: Amit Kucheria = Matthew Garrett

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-20 Thread Amit Kucheria
Will be enabled in next kernel upload ** Changed in: linux-meta (Ubuntu) Importance: Undecided = Medium Assignee: (unassigned) = Amit Kucheria Status: New = In Progress Target: None = tribe-6 -- usplash could not run on Ubuntu UME flavored kernel

[Bug 133557] Re: usplash could not run on Ubuntu UME flavored kernel

2007-08-20 Thread Amit Kucheria
** Changed in: linux-meta (Ubuntu) Status: In Progress = Fix Committed -- usplash could not run on Ubuntu UME flavored kernel https://bugs.launchpad.net/bugs/133557 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. --