User talk:Fredix

Hello,

I am using Beagle Board Rev. C4 and ran omapfbplay sample application for Angstrom. The app shows video but no audio. However, the mplayer plays audio. Is it any setting on the omapfbplay application to turn it on/off?

Thanks, Fredix

omapfbplay does not support sound.--Wmat 20:39, 11 August 2011 (UTC)

Hello,

I am using Angstrom newest version for beagle board Rev.c4. I downloaded uImage from same angstrom beagleboard.org proposed site.

I have seen in the Internet that there are a lot of discussions about how to setup the NFS server in the beagleboard and angstrom. I followed some recommendations provided by eLinux.org document file BeagleBoardFAQ#NFS. I followed procedure step by step but my NFS connection does not work.However with another system I am working on a DM355, the NFS works fine, meaning that the NFS server is setup properly on the Host PC.

It seems that the problem is that the beagleboard network connection is not initialized properly before the NFS. However USB/ETH driver is recognized (ASIX AX88772), but not mounted. Please see some portion of the trace below. Thanks.

[  19.529113] Power Management for TI OMAP3. [  19.533721] usb 2-2: new high speed USB device using ehci-omap and address 2 [  19.541290] SmartReflex driver initialized [  19.556274] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1 [  19.565002] registered taskstats version 1 [  19.588500] Console: switching to colour frame buffer device 80x30 [  19.614227] regulator_init_complete: incomplete constraints, leaving VAUX3 on [   19.621704] regulator_init_complete: incomplete constraints, leaving VDAC on [   19.629547] omap_vout omap_vout: probed for an unknown device [  19.723480] usb 2-2: New USB device found, idVendor=05e3, idProduct=061 [  19.730316] usb 2-2: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [   19.737579] usb 2-2: Product: USB2.0 Hub [  19.742736] hub 2-2:1.0: USB hub found [  19.746978] hub 2-2:1.0: 4 ports detected [  19.846893] mmc0: new SD card at address aaaa [  19.851867] mmcblk0: mmc0:aaaa SD02G 1.84 GiB [  19.856994]  mmcblk0: p1 p2 p3 [   20.050354] usb 2-2.2: new high speed USB device using ehci-omap and address 3 [  20.136230] IP-Config: No network devices available. [  20.141357] Looking up port of RPC 100003/2 on 192.168.1.31 [  20.176361] usb 2-2.2: New USB device found, idVendor=0451, idProduct=9261 [  20.183349] usb 2-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [  20.190765] usb 2-2.2: Product: TUSB9261 Firmware v1 [   20.195770] usb 2-2.2: Manufacturer: Texas Instruments [  20.200958] usb 2-2.2: SerialNumber: 193F6072887E45D8 [  20.207885] scsi0 : usb-storage 2-2.2:1.0 [  20.300354] usb 2-2.3: new low speed USB device using ehci-omap and address 4 [  20.432983] usb 2-2.3: New USB device found, idVendor=0518, idProduct=0001 [  20.439910] usb 2-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [  20.447326] usb 2-2.3: Product: USB-compliant keyboard [  20.452575] usb 2-2.3: Manufacturer: Plus More Enterprise LTD. [   20.465240] input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/platform/ehci-omap.0/usb2/2-2/2-2.3/2-2.3:1.0/input/input2 [  20.478240] generic-usb 0003:0518:0001.0001: input: USB HID v1.10 Keyboard [Plus More Enterprise LTD. USB-compliant keyboard] on usb-ehci-omap.0-2.3/input0 [  20.499389] input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/platform/ehci-omap.0/usb2/2-2/2-2.3/2-2.3:1.1/input/input3 [  20.512695] generic-usb 0003:0518:0001.0002: input: USB HID v1.10 Mouse [Plus More Enterprise LTD. USB-compliant keyboard] on usb-ehci-omap.0-2.3/input1 [  20.612976] usb 2-2.4: new high speed USB device using ehci-omap and address 5 [  20.751098] usb 2-2.4: New USB device found, idVendor=0b95, idProduct=772a [  20.758056] usb 2-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [  20.765563] usb 2-2.4: Product: AX88772A [  20.769531] usb 2-2.4: Manufacturer: ASIX Elec. Corp. [  20.774627] usb 2-2.4: SerialNumber: 000004 [  21.615570] eth0: register 'asix' at usb-ehci-omap.0-2.4, ASIX AX88772 USB 2.0 Ethernet, 00:50:c2:0d:f1:50 [  25.207580] scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDS5C302 A580 PQ: 0 ANSI: 6 [  25.217041] sd 0:0:0:0: Attached scsi generic sg0 type 0 [  25.223602] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [  25.234558] sd 0:0:0:0: [sda] Write Protect is off [  25.239562] sd 0:0:0:0: [sda] Assuming drive cache: write through [  25.248046] sd 0:0:0:0: [sda] Assuming drive cache: write through [  25.254272]  sda: sda1 [  25.298553] sd 0:0:0:0: [sda] Assuming drive cache: write through [  25.304779] sd 0:0:0:0: [sda] Attached SCSI disk [  50.143615] rpcbind: server 192.168.1.31 not responding, timed out [  50.149932] Root-NFS: Unable to get nfsd port number from server, using default [  50.157348] Looking up port of RPC 100005/1 on 192.168.1.31 [  80.159301] rpcbind: server 192.168.1.31 not responding, timed out [  80.165588] Root-NFS: Unable to get mountd port number from server, using default [  80.173370] Root-NFS: Server returned error -101 while mounting /opt/pedro/filesys [  80.181121] VFS: Unable to mount root fs via NFS, trying floppy. [  80.187988] VFS: Cannot open root device "nfs" or unknown-block(2,0) [  80.194427] Please append a correct "root=" boot option; here are the available partitions: [  80.202911] 1f00             512 mtdblock0 (driver?) [  80.207977] 1f01            1920 mtdblock1 (driver?) [  80.212982] 1f02             128 mtdblock2 (driver?) [  80.218017] 1f03            4096 mtdblock3 (driver?) [  80.223083] 1f04          255488 mtdblock4 (driver?) [  80.228088] b300         1931264 mmcblk0 driver: mmcblk [  80.233856]   b301           72261 mmcblk0p1 [  80.238220]   b302          963900 mmcblk0p2 [  80.242523]   b303          891607 mmcblk0p3 [  80.246887] 0800      1953514584 sda driver: sd [   80.251464]   0801      1953512001 sda1 [  80.255371] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

First off, you'd get many more answers on the BeagleBoard mailing list. Second, it would appear that you're not running the services necessary for NFS on 192.168.1.31. --Wmat 23:50, 15 August 2011 (UTC)