headers
Benjamin Rose | 1 Jun 2011 01:13
Favicon

puias-arm official alpha release

Target audience,

PUIAS-arm is an effort to bring a stable, long-term support rpm-based
Linux distribution to the arm architecture. This would be functionally
equivalent to CentOS-arm or RHEL-arm (if they existed).

I've put the official announcement here:
http://allmybase.com/2011/05/31/puias-arm-alpha-release/

Download/install instructions and associated administrivia here:
http://allmybase.com/puias-arm/

ball.rolling == true

--

-- 
Benjamin Rose
Network & Security Administrator
Institute for Advanced Study, Princeton NJ
brose@...
Permalink | Reply | 4 comments |
headers
alxx | 1 Jun 2011 03:54
Picon

Re: Pandaboard Enclosure

Case looks okay, maybe depends on location if it provides enough
cooling/airflow.

Would be nice to have a case available from ponoko or similar.

Need a pandaboard case that can be fitted with a small fan(and filter)
and battery.

Looking at designing one myself (if I ever get enough time)
with a small solar panel on top , external antenna for bt/wifi, with a
fan and battery(+charger/regulator).
Something similar(but smaller) to the cases that get used for the
navigation/marker lighting around Sydney harbour/waterways.

Alex

On Jun 1, 7:13 am, JC <jcchas...@...> wrote:
> Hi All,
>
> Has anyone ordered or seen this new Pandaboard case?
>
> http://www.amazon.com/gp/product/B0050R7QI2
>
> I emailed the company and it seems they will also open source their
> CAD files for this and other enclosures and accessories they are
> designing. Very cool.
>
> JC
(Continue reading)

Permalink | Reply | 1 comment |
headers
suoko | 1 Jun 2011 03:51
Picon

Re: Pandaboard Enclosure

I'd design a better CAD file to have nice and open source android
tablets.

On 31 Mag, 23:13, JC <jcchas...@...> wrote:
> Hi All,
>
> Has anyone ordered or seen this new Pandaboard case?
>
> http://www.amazon.com/gp/product/B0050R7QI2
>
> I emailed the company and it seems they will also open source their
> CAD files for this and other enclosures and accessories they are
> designing. Very cool.
>
> JC
Permalink | Reply | 0 comments |
headers
신호준 | 1 Jun 2011 03:48
Picon

I have several questions about Android on PandaBoard.

Hello.

I am Hojoon Shin, CEO of MightyWorks.

I met OMAP team of TI, and they suggested us porting our solution(2-microphone noise suppression) on PandaBoard, Android OS.

So, we tried to port, but we faced to some problems.

Please tell me the way to solve these problems.

 

 

1. WAV file playing

We built and loaded Android Proyo on TI's PandaBoard, but we happen to know that wave file is not played ordinarily.
Please check whether wave file can be played or not on this version
Board version : PandaBoard Rev A2
Loaded Binary : http://www.omappedia.com/wiki/PandaBoard_L27.10.2-P1_Release_Notes
Played file : attached

Status value is -22, that means abnormal, and playing is progressed, but we cannot hear sound.

**********************************************
********** AUDIO HAL TEST FRAMEWORK **********
**********************************************

Play: start playback
Play: wav_play
Play: open file "rainbow_mono.wav"
Play: 1 ch, 22050 hz, 16 bit, PCM
Play: file size=180224
Using device 2
Play: status=-22
Play: buffer size=8192
Play: no more data

 

 

2. Stereo microphone input

We happen to know that stereo microphone input is not possible on PandaBoard.
PandaBoard supports only differential microphone input.

We referred this link and attached file(schematic).
http://omappedia.org/wiki/PandaBoard_FAQ#When_I_record_audio_it_seems_to_be_in_mono_only.3F

Please tell me how to get stereo microphone input on PandaBoard.

 

3. Bluetooth or Wifi on PandaBoard
We also want to know whether audio input through bluetooth or Wifi is possible.
And bluetooth on PandaBoard doesn't seems to be run nomarlly, can you teach me how to solve that problem?

 

I hope we integrate our solution into PandaBoard soon with your help.
Thank you.
 

Best Regards.
Shin 

 


 

 

 

 

 

 

 

----- Original Message -----

From: Thomas, Eric (WBU) [ethomas <at> ti.com]

To: Bhat, Nagaraj [nagaraj.bhat <at> ti.com], 신호준 [signaljoon <at> mightyworks.co.kr]

Cc: 송청담 [cdsong <at> bsecm.com], 김세웅 [bandwalk <at> mightyworks.co.kr]

Sent: Wed , June 01, 2011 07:47 AM

Subject: RE: Hello, I'm Hojoon Shin of MightyWorks.

 

Hello Shin.
Thank you for following-up.

Unfortunately, I am not familiar with the technical aspects of Android on PandaBoard.
I suggest that you direct your question to the mailing list or IRC channel listed on this site:
http://www.pandaboard.org/node/225/

There are several TI employees who participate on this list and can help debug the problem to understand why you do not hear any audio.

Best regards,
Eric

________________________________________
From: 신호준 [signaljoon <at> mightyworks.co.kr]
Sent: Sunday, May 29, 2011 8:45 PM
To: Thomas, Eric (WBU); Bhat, Nagaraj
Cc: 김세웅; 송청담
Subject: Hello, I'm Hojoon Shin of MightyWorks.

Hello

I am Hojoon Shin of MightyWorks who met you last February with Mr. Song of BSE(Bosung Electronics).

We introduced our acoustic solution(2-mic noise suppression) and you suggested us porting our solution on PandaBoard, Android OS.

So, we built and loaded Android Proyo on TI's PandaBoard, but we happen to know that wave file is not played ordinarily.

Please check whether wave file can be played or not on this version



Board version : PandaBoard Rev A2
Loaded Binary : http://www.omappedia.com/wiki/PandaBoard_L27.10.2-P1_Release_Notes
Played file : attached

Status value is -22, that means abnormal, and playing is progressed, but we cannot hear sound.

**********************************************
********** AUDIO HAL TEST FRAMEWORK **********
**********************************************

Play: start playback
Play: wav_play
Play: open file "rainbow_mono.wav"
Play: 1 ch, 22050 hz, 16 bit, PCM
Play: file size=180224
Using device 2
Play: status=-22
Play: buffer size=8192
Play: no more data



I hope we integrate our solution into PandaBoard soon with your help.

Thank you.



Best Regards.

Shin







[http://mail.mightyworks.co.kr/option/option_mail_signature_download.php?path=/data/mightyworks.co.kr/signaljoon/.1269487612292220&type=image&subtype=jpeg]

  Hojoon Shin
  MightyWorks, Inc.
  CEO
  Tel : +82-2-871-9628    Fax : +82-2-871-3798    Mobile : +82-10-3017-4279




 

 

Permalink | Reply | 2 comments |
headers
Jeffrey Wang | 1 Jun 2011 04:23
Picon

Re: Mount Android Filesystem on NFS

I'm using L27.10.2-P1, so WLAN should worked fine.

The boot step is , First put SD card into the slot and power up , and
boot up to u-boot. Then load kernel to memory (I think the command
fatload should load it to memory... am I wrong ?) , then take off the
SD card to release the SD slot, then boot. Here are the boot arguments
I use to mount AFS on NFS:

bootargs = androidboot.console=ttyO2 console=ttyO2,115200n8
mem=456M <at> 0x80000000 mem=512M <at> 0xA0000000  init=/init vram=32M
omapfb.vram=0:16M,1:16M consoleblank=0 smsc95xx.macaddr=76:2F:97:85:4F:
56 root=/dev/nfs rw nfsroot=192.168.2.109:/media/
afs,nolock,wsize=1024,rsize=1024 ip=DHCP rootdelay=2

I just can't figure out why WLAN can work fine with standard boot
procedure but can not work fine if I try to mount AFS on NFS T_T

Thanks for all your replies.

Best Regards
Jeffrey Wang

On 6月1日, 上午12時33分, Vladimir Pantelic
<vlado...@...> wrote:
> orbarron wrote:
> > Hello Jeffrey,
>
> > What release are you using? In the latest draft release (L27.12.1-P2)
> > WLAN is not working. We are testing this atm and hope to have
> > something in the near future.
>
> >>  I try to mount AFS on NFS to free my SD slot. I put x-loader , u-boot
> >>  and kernel on SD card , load it to memory ,and boot up without SD
> >>  card.
>
> > Not sure how you are doing this... panda has no memory for you to
> > store these values at.
>
> it has 1GB of memory last time I checked :)
Permalink | Reply | 0 comments |
headers
B U J J I | 1 Jun 2011 05:57
Picon

Regarding omx h264 decoder delay in live video streaming

Hi all,

I am using Pandaboard with Ubuntu 10.10 for developing a videoconferencing system. I read through the "Ducati for Dummies" document and understood the architecture. Also, based on the previous mail, I understood that the code that runs on the Ducati system (Cortex-M3) are available only as binaries and those are integrated into the Ubuntu to be loaded/run on boot on the Cortex-A9. Hope my understandings are correct till this.

A little background, I have worked with DM368 dvsdk4 to build a videoconferencing system (h264 based). We used gstreamer to do the encode/decode. The decode would usually start after 4 to 5 seconds of starting to receive media data. This was because of the dmaibuffer that was buffering data (as the decoder should be feed with only >= 1 frame worth of data) in gstreamer, after optimizing the buffer size, I was able to get realtime decode. Now with that as background, I now see a similar effect with Pandaboard(Ducati system). So I was wondering if there is a similar buffering, if so is there some way to tune the buffers to reduce the latency or any alternatives? One more test that makes me think of possibility of buffering is that when I send stream <at> 800Kbps the delay to start decode is more (5-7secs) and when I send 2Mbps stream the decode starts in 3-4 secs.

Also, the "Ducati for Dummies" page reports that codecs are available for various formats H264, H263, etc. but I see that in the Ubuntu 10.10, GStreamer only the h264 decoder is available. Is it that the other codes are NOT available or they are not integrated in Gstreamer?


Thanks,
Bujji 
Permalink | Reply | 26 comments |
headers
Vladimir Pantelic | 1 Jun 2011 07:52
Picon

Re: puias-arm official alpha release

Benjamin Rose wrote:
> Target audience,
>
> PUIAS-arm is an effort to bring a stable, long-term support rpm-based
> Linux distribution to the arm architecture. This would be functionally
> equivalent to CentOS-arm or RHEL-arm (if they existed).
>
> I've put the official announcement here:
> http://allmybase.com/2011/05/31/puias-arm-alpha-release/
>
> Download/install instructions and associated administrivia here:
> http://allmybase.com/puias-arm/
>
> ball.rolling == true

"...I have finished compiling the source RPMs for the ARM architecture,
specifically the armv5tel instruction set. This should make the project
backwards-compatible with less recent ARM hardware and ensure that a large
  amount of patching is not required..."

armv5? really?
Permalink | Reply | 3 comments |
headers
siva | 1 Jun 2011 07:31
Picon

Re: HDMI GUI blanks (Ubuntu 11.04)

All:

=================================================================
[    23.502]
X.Org X Server 1.10.0
Release Date: 2011-2-25
[    23.502] X Protocol Version 11, Revision 0
[    23.502] Build Operating System: Linux 2.6.35-22-omap armv7l
Ubuntu
[    23.502] Current Operating System: Linux panda11 2.6.38-1207-omap4
#10-Ubuntu SMP PREEMPT Sat Mar 26 14:03:09 UTC 2011 armv7l
[    23.502] Kernel command line: splash quiet fixrtc
root=UUID=d1fbc026-8693-4a4a-82ff-0548a1f11ac8 mem=256M <at> 0xA0000000
mem=460M <at> 0x80000000 vram=32M ro elevator=noop quiet splash fixrtc
[    23.503] Build Date: 25 March 2011  02:51:08AM
[    23.503] xorg-server 2:1.10.0-0ubuntu2 (For technical support
please see http://www.ubuntu.com/support)
[    23.503] Current version of pixman: 0.20.2
[    23.503] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[    23.503] Markers: (--) probed, (**) from config file, (==) default
setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    23.504] (==) Log file: "/var/log/Xorg.0.log", Time: Mon May 16
11:02:31 2011
[    23.546] (==) Using system config directory "/usr/share/X11/
xorg.conf.d"
[    23.547] (==) No Layout section.  Using the first Screen section.
[    23.547] (==) No screen section available. Using defaults.
[    23.547] (**) |-->Screen "Default Screen Section" (0)
[    23.547] (**) |   |-->Monitor "<default monitor>"
[    23.548] (==) No monitor specified for screen "Default Screen
Section".
	Using a default monitor configuration.
[    23.548] (==) Automatically adding devices
[    23.548] (==) Automatically enabling devices
[    23.548] (WW) The directory "/usr/share/fonts/X11/cyrillic" does
not exist.
[    23.548] 	Entry deleted from font path.
[    23.548] (WW) The directory "/usr/share/fonts/X11/100dpi/" does
not exist.
[    23.548] 	Entry deleted from font path.
[    23.549] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not
exist.
[    23.549] 	Entry deleted from font path.
[    23.549] (WW) The directory "/usr/share/fonts/X11/100dpi" does not
exist.
[    23.549] 	Entry deleted from font path.
[    23.549] (WW) The directory "/usr/share/fonts/X11/75dpi" does not
exist.
[    23.549] 	Entry deleted from font path.
[    23.549] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/Type1,
	/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
	built-ins
[    23.549] (==) ModulePath set to "/usr/lib/xorg/extra-modules,/usr/
lib/xorg/modules"
[    23.549] (II) The server relies on udev to provide the list of
input devices.
	If no devices become available, reconfigure udev or disable
AutoAddDevices.
[    23.549] (II) Loader magic: 0x14215c
[    23.549] (II) Module ABI versions:
[    23.549] 	X.Org ANSI C Emulation: 0.4
[    23.549] 	X.Org Video Driver: 10.0
[    23.549] 	X.Org XInput driver : 12.3
[    23.549] 	X.Org Server Extension : 5.0
[    23.550] (II) LoadModule: "extmod"
[    23.578] (II) Loading /usr/lib/xorg/modules/extensions/
libextmod.so
[    23.579] (II) Module extmod: vendor="X.Org Foundation"
[    23.579] 	compiled for 1.10.0, module version = 1.0.0
[    23.579] 	Module class: X.Org Server Extension
[    23.579] 	ABI class: X.Org Server Extension, version 5.0
[    23.579] (II) Loading extension MIT-SCREEN-SAVER
[    23.580] (II) Loading extension XFree86-VidModeExtension
[    23.580] (II) Loading extension XFree86-DGA
[    23.580] (II) Loading extension DPMS
[    23.580] (II) Loading extension XVideo
[    23.580] (II) Loading extension XVideo-MotionCompensation
[    23.580] (II) Loading extension X-Resource
[    23.580] (II) LoadModule: "dbe"
[    23.581] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[    23.581] (II) Module dbe: vendor="X.Org Foundation"
[    23.581] 	compiled for 1.10.0, module version = 1.0.0
[    23.582] 	Module class: X.Org Server Extension
[    23.582] 	ABI class: X.Org Server Extension, version 5.0
[    23.582] (II) Loading extension DOUBLE-BUFFER
[    23.582] (II) LoadModule: "glx"
[    23.583] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    23.584] (II) Module glx: vendor="X.Org Foundation"
[    23.584] 	compiled for 1.10.0, module version = 1.0.0
[    23.584] 	ABI class: X.Org Server Extension, version 5.0
[    23.584] (==) AIGLX enabled
[    23.584] (II) Loading extension GLX
[    23.584] (II) LoadModule: "record"
[    23.585] (II) Loading /usr/lib/xorg/modules/extensions/
librecord.so
[    23.592] (II) Module record: vendor="X.Org Foundation"
[    23.592] 	compiled for 1.10.0, module version = 1.13.0
[    23.592] 	Module class: X.Org Server Extension
[    23.592] 	ABI class: X.Org Server Extension, version 5.0
[    23.592] (II) Loading extension RECORD
[    23.592] (II) LoadModule: "dri"
[    23.599] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[    23.600] (II) Module dri: vendor="X.Org Foundation"
[    23.600] 	compiled for 1.10.0, module version = 1.0.0
[    23.600] 	ABI class: X.Org Server Extension, version 5.0
[    23.600] (II) Loading extension XFree86-DRI
[    23.600] (II) LoadModule: "dri2"
[    23.608] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[    23.611] (II) Module dri2: vendor="X.Org Foundation"
[    23.612] 	compiled for 1.10.0, module version = 1.2.0
[    23.613] 	ABI class: X.Org Server Extension, version 5.0
[    23.613] (II) Loading extension DRI2
[    23.615] (II) LoadModule: "omapfb"
[    23.636] (WW) Warning, couldn't open module omapfb
[    23.637] (II) UnloadModule: "omapfb"
[    23.637] (II) Unloading omapfb
[    23.637] (==) Matched fbdev as autoconfigured driver 0
[    23.637] (==) Assigned the driver to the xf86ConfigLayout
[    23.637] (II) LoadModule: "fbdev"
[    23.638] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    23.638] (II) Module fbdev: vendor="X.Org Foundation"
[    23.638] 	compiled for 1.10.0, module version = 0.4.2
[    23.638] 	ABI class: X.Org Video Driver, version 10.0
[    23.638] (II) FBDEV: driver for framebuffer: fbdev
[    23.639] (++) using VT number 7

[    23.639] (WW) Falling back to old probe method for fbdev
[    23.639] (II) Loading sub module "fbdevhw"
[    23.639] (II) LoadModule: "fbdevhw"
[    23.642] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    23.645] (II) Module fbdevhw: vendor="X.Org Foundation"
[    23.646] 	compiled for 1.10.0, module version = 0.0.2
[    23.647] 	ABI class: X.Org Video Driver, version 10.0
[    23.649] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    23.650] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    23.650] (II) FBDEV(0): using default device
[    23.651] (WW) VGA arbiter: cannot open kernel arbiter, no multi-
card support
[    23.653] (II) FBDEV(0): Creating default Display subsection in
Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    23.653] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[    23.654] (==) FBDEV(0): RGB weight 888
[    23.655] (==) FBDEV(0): Default visual is TrueColor
[    23.656] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[    23.660] (II) FBDEV(0): hardware: omapfb (video memory: 8100kB)
[    23.661] (II) FBDEV(0): checking modes against framebuffer
device...
[    23.661] (II) FBDEV(0): checking modes against monitor...
[    23.661] (--) FBDEV(0): Virtual size is 1920x1080 (pitch 1920)
[    23.661] (**) FBDEV(0):  Built-in mode "current": 148.5 MHz, 67.5
kHz, 60.0 Hz
[    23.662] (II) FBDEV(0): Modeline "current"x0.0  148.50  1920 2008
2052 2200  1080 1084 1089 1125 -hsync -vsync -csync (67.5 kHz)
[    23.662] (==) FBDEV(0): DPI set to (96, 96)
[    23.662] (II) Loading sub module "fb"
[    23.662] (II) LoadModule: "fb"
[    23.662] (II) Loading /usr/lib/xorg/modules/libfb.so
[    23.663] (II) Module fb: vendor="X.Org Foundation"
[    23.663] 	compiled for 1.10.0, module version = 1.0.0
[    23.668] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    23.668] (**) FBDEV(0): using shadow framebuffer
[    23.668] (II) Loading sub module "shadow"
[    23.668] (II) LoadModule: "shadow"
[    23.669] (II) Loading /usr/lib/xorg/modules/libshadow.so
[    23.669] (II) Module shadow: vendor="X.Org Foundation"
[    23.669] 	compiled for 1.10.0, module version = 1.1.0
[    23.669] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    23.669] (==) Depth 24 pixmap format is 32 bpp
[    23.868] (==) FBDEV(0): Backing store disabled
[    23.869] (==) FBDEV(0): DPMS enabled
[    23.869] (==) RandR enabled
[    23.869] (II) Initializing built-in extension Generic Event
Extension
[    23.869] (II) Initializing built-in extension SHAPE
[    23.870] (II) Initializing built-in extension MIT-SHM
[    23.870] (II) Initializing built-in extension XInputExtension
[    23.870] (II) Initializing built-in extension XTEST
[    23.870] (II) Initializing built-in extension BIG-REQUESTS
[    23.870] (II) Initializing built-in extension SYNC
[    23.870] (II) Initializing built-in extension XKEYBOARD
[    23.870] (II) Initializing built-in extension XC-MISC
[    23.870] (II) Initializing built-in extension SECURITY
[    23.870] (II) Initializing built-in extension XINERAMA
[    23.870] (II) Initializing built-in extension XFIXES
[    23.870] (II) Initializing built-in extension RENDER
[    23.870] (II) Initializing built-in extension RANDR
[    23.870] (II) Initializing built-in extension COMPOSITE
[    23.870] (II) Initializing built-in extension DAMAGE
[    23.870] (II) Initializing built-in extension GESTURE
[    23.911] (II) AIGLX: Screen 0 is not DRI2 capable
[    23.911] (II) AIGLX: Screen 0 is not DRI capable
[    23.911] (II) AIGLX: Trying DRI driver /usr/lib/dri/swrast_dri.so
[    23.927] (II) AIGLX: Loaded and initialized swrast
[    23.927] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    23.987] (II) XKB: reuse xkmfile /var/lib/xkb/server-
B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
[    24.061] (II) config/udev: Adding input device Logitech USB
Optical Mouse (/dev/input/event1)
[    24.062] (**) Logitech USB Optical Mouse: Applying InputClass
"evdev pointer catchall"
[    24.062] (II) LoadModule: "evdev"
[    24.068] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    24.070] (II) Module evdev: vendor="X.Org Foundation"
[    24.070] 	compiled for 1.9.99.902, module version = 2.6.0
[    24.070] 	Module class: X.Org XInput Driver
[    24.070] 	ABI class: X.Org XInput driver, version 12.3
[    24.070] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    24.070] (**) Logitech USB Optical Mouse: always reports core
events
[    24.070] (**) Logitech USB Optical Mouse: Device: "/dev/input/
event1"
[    24.094] (--) Logitech USB Optical Mouse: Found 3 mouse buttons
[    24.094] (--) Logitech USB Optical Mouse: Found scroll wheel(s)
[    24.094] (--) Logitech USB Optical Mouse: Found relative axes
[    24.094] (--) Logitech USB Optical Mouse: Found x and y relative
axes
[    24.094] (II) Logitech USB Optical Mouse: Configuring as mouse
[    24.094] (II) Logitech USB Optical Mouse: Adding scrollwheel
support
[    24.094] (**) Logitech USB Optical Mouse: YAxisMapping: buttons 4
and 5
[    24.094] (**) Logitech USB Optical Mouse: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    24.095] (**) Option "config_info" "udev:/sys/devices/platform/
ehci-omap.0/usb1/1-1/1-1.2/1-1.2.3/1-1.2.3:1.0/input/input1/event1"
[    24.095] (II) XINPUT: Adding extended input device "Logitech USB
Optical Mouse" (type: MOUSE)
[    24.095] (II) Logitech USB Optical Mouse: initialized for relative
axes.
[    24.095] (**) Logitech USB Optical Mouse: (accel) keeping
acceleration scheme 1
[    24.095] (**) Logitech USB Optical Mouse: (accel) acceleration
profile 0
[    24.095] (**) Logitech USB Optical Mouse: (accel) acceleration
factor: 2.000
[    24.095] (**) Logitech USB Optical Mouse: (accel) acceleration
threshold: 4
[    24.097] (II) config/udev: Adding input device Logitech USB
Optical Mouse (/dev/input/mouse0)
[    24.097] (II) No input driver/identifier specified (ignoring)
[    24.099] (II) config/udev: Adding input device CHICONY HP Basic
USB Keyboard (/dev/input/event2)
[    24.099] (**) CHICONY HP Basic USB Keyboard: Applying InputClass
"evdev keyboard catchall"
[    24.099] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    24.100] (**) CHICONY HP Basic USB Keyboard: always reports core
events
[    24.100] (**) CHICONY HP Basic USB Keyboard: Device: "/dev/input/
event2"
[    24.125] (--) CHICONY HP Basic USB Keyboard: Found keys
[    24.125] (II) CHICONY HP Basic USB Keyboard: Configuring as
keyboard
[    24.125] (**) Option "config_info" "udev:/sys/devices/platform/
ehci-omap.0/usb1/1-1/1-1.2/1-1.2.4/1-1.2.4:1.0/input/input2/event2"
[    24.125] (II) XINPUT: Adding extended input device "CHICONY HP
Basic USB Keyboard" (type: KEYBOARD)
[    24.125] (**) Option "xkb_rules" "evdev"
[    24.125] (**) Option "xkb_model" "pc105"
[    24.125] (**) Option "xkb_layout" "us"
[    24.146] (II) config/udev: Adding input device twl4030_pwrbutton (/
dev/input/event3)
[    24.146] (**) twl4030_pwrbutton: Applying InputClass "evdev
keyboard catchall"
[    24.146] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    24.146] (**) twl4030_pwrbutton: always reports core events
[    24.146] (**) twl4030_pwrbutton: Device: "/dev/input/event3"
[    24.195] (--) twl4030_pwrbutton: Found keys
[    24.195] (II) twl4030_pwrbutton: Configuring as keyboard
[    24.195] (**) Option "config_info" "udev:/sys/devices/platform/
omap/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input3/event3"
[    24.195] (II) XINPUT: Adding extended input device
"twl4030_pwrbutton" (type: KEYBOARD)
[    24.195] (**) Option "xkb_rules" "evdev"
[    24.195] (**) Option "xkb_model" "pc105"
[    24.196] (**) Option "xkb_layout" "us"
[    24.208] (II) config/udev: Adding input device SDP4430 Headset
Jack (/dev/input/event0)
[    24.208] (II) No input driver/identifier specified (ignoring)

============================================
FOUND TWO FILES : Xorg.0.log - which is pasted here
There is another file Xorg.0.log.old
============================================

ANY HELP WOULD APPRECIATED

TIA -SIVA

On May 31, 9:37 pm, Rob Clark <robdcl...@...> wrote:
> could you send the xorg log file after this happens?  It will be at
> /var/log/Xorg.0.log before it gets overwritten by restarting the UI..
>
> BR,
> -R
>
>
>
>
>
>
>
> On Tue, May 31, 2011 at 3:00 AM,siva<sivaka...@...> wrote:
> > All:
>
> > I have Pandaboard A1 and installed with Ubuntu natty 11.04. Connected
> > this setup to Samsung HDTV.
> > Everything works fine. HDTV is getting the Ubuntu home screen. Looks
> > nice.
>
> > Now..if i open/run more than 5/6 applications (such as 1 synaptic, 5
> > terminal windows, playing videos on VLC, USB UVC webcam data
> > viewer,etc..)....GUI is getting BLANKED. I observed the same behavior
> > if i keep the board ON for 1 or 2 hrs. I sensed the heat near USB+ETH
> > hub.
>
> > Please help in this regard.
>
> > TiA
> >Siva
Permalink | Reply | 5 comments |
headers
Patrick | 1 Jun 2011 08:22
Picon

Re: Pandaboard Enclosure

On May 31, 7:54 pm, alxx <alxxtheg...@...> wrote:
> Need a pandaboard case that can be fitted with a small fan(and filter)
> and battery.

Like this http://elinux.org/Panda_Bamboo ?
Permalink | Reply | 0 comments |
headers
abcdude | 1 Jun 2011 11:17
Picon

GLBENCHMARK app

hi did anyone run the GlBenchMark app on their pandaboard. did it run ?? if yes can anyone post the test results????

Permalink | Reply | 0 comments |

Gmane