Ok, so this is what I understand. I am new to the bug tracking process in Ubuntu. Please bear with me if I sound quite naive :-)
Jaunty has openchrome:713 in it and they may or may not upgrade to 737 in Jaunty. The changes required to support NC20 is added in 737 and later which will go into a future releases of Ubuntu and may be Jaunty too. So, if I want to use openchrome with Jaunty, in the meanwhile, I should follow the procedure described in links you suggested which basically means getting the a version of openchrome later than 737. Fair enough. I will upgrade to Jaunty when I get some time. Thanks very much. But for a new user, this is a hurdle to install Jaunty. The installation program could use a default usable display (driver "vesa") which may not be the best for NC20 (i.e. openchrome 737 or later). Somehow this is done in Ubuntu 8.04 and the installation has no problem although the display is not very good. That is fine. I believe that if no suitable display driver is available, there should be a default scheme which works in any case. This may not be implemented correctly in Jaunty. Could you please correct this until a stable openchrome goes into Jaunty. May be then this is not an openchrome issue, but an xorg or installation script issue. -- Samsung NC20 installation problem(test pattern on screen) https://bugs.launchpad.net/bugs/374090 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
