Ubuntu Known Issues

From OMAPpedia

Revision as of 11:43, 30 July 2011 by Fisuk (Talk | contribs)
Jump to: navigation, search

The page details the known issues with Ubuntu on OMAP4 (PandaBoard). The below is is current as of:

Ubuntu on OMAP: 10.10 (Maverick Meerkat)
TI Addon packages (ubuntu-omap4-extras) : 15-Oct-2010

Contents

Known Issues

Full HD clips dont playback on non-full HD displays

Decoding full HD clips on monitor that do not support full HD, when decoding full HD streams on monitor that does not support such resolution, the image is rescaled after decoding. If the rescaling is important you might see some garbage on the screen, you need to try to maximize the windows to full screen. Even in such conditions, we are observing system failure/breaks/bad image quality. It is really recommended to run all full HD tests on full HD resolution monitors.

Problems when connecting to some displays

The display driver supports automatic detection of the screen maximum resolution. With some monitors this does not seem to work well. If the UI does not come up, or is completely messed up you might be using a not supported monitor. If your monitor is full HD, and does not work, one workaround which is known to work on some monitors is to turn it OFF, boot the board, wait for some time (give it enough time to start X), and start the monitor.

Screen Blanking

With some full HD monitors, the screen can sometimes become completely black, with FIFO underflow errors being logged in the console. When this happens, the screen can be restored by using the following work around key sequence: Ctrl-Alt-F1 then Ctrl-Alt-F7 (this forces text console then restores the graphical UI).

Kernel crash when booting with headset plugged in

When booting with headset, the kernel might be crashing. It is more frequent on some boards than other. You can boot without headset and plug it after boot completed.

Instabilities when using 1GB RAM support

There are some known instabilities when enable highmen to leverage the full 1GB on PandaBoard. The default and default and recommended bootargs are set to use max 460MB+256MB, to avoid using highmem.

GStreamer piplelines on /dev/video1 might not work

The GStreamer pipelines on /dev/video1 might not work. In such case, the xf86-video-v4l2 shall be removed:

$ sudo apt-get purge xf86-video-v4l2
$ sudo service gdm restart

Kernel oops during startup and UI does not comeup

Kernel oops during startup, then the UI does not appear. One kernel module is unstable, joydev. Try to rename it:

$ cd /lib/modules/2.6.35-ti903-omap4
$ sudo mv joydev.ko joydev.ko.old

When recording WAV audio file using line-in the audio seems to skip

No workaround present.

HD video playback via Totem seems to be unstable

There are some instabilies with Totem when playing video. You can try starting the video playback from command line which is more realiable.

* Start a video manually from command prompt in fullscreen: "$ totem --fullscreen <video file> &"
* Get back to the terminal with "Alt+Tab" and stop running instance of totem: "$ totem --quit"
* Start a new video in totem with first command

HD video files need to be on USB storage

When you are playing back a HD video file you they work well only when they are on a USB storage device and not on MMC card.

No HD video acceleration on Natty Narwhal

The packages required are not yet ready.

When installing TI OMAP Addon's the Installation appears stalled

When using the software center on an OMAP4 PandaBoard, installing TI OMAP extras/add-on with the desktop icon just after installing the preinstalled maverick image, debconf dialogs are hidden. For example, license agreements windows asking the user to confirm.

If the user does not notice the window in the top bar, it seems as if the installation of the packages is "stalled" (but this is not the case). Ref

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox