Are there pre-built images for this or would I need to assemble all the pieces myself?
Also are there any general 3D object browsers that are already working with the 3D acceleration in the 3530’s?
Hey Dan,
Only partially built... (SGX stuff is non distributable)...
armv7-a optimized would be 'lucid'
Either use rootstock, or start with this base image:
http://elinux.org/BeagleBoardUbuntu#Lucid_10.04_.28alpha-3.29
You'll have to bug Sakoman for his kernel for the overo, as i don't
have one too test...
As a note, lucid requires 3 very specific defconfig settings to boot,
that may or may not be already enabled in overo's kernel...
http://bazaar.launchpad.net/~beagleboard-kernel/%2Bjunk/2.6-stable/annotate/head%3A/readme.txt
Best of all, CONFIG_DEVTMPFS=y breaks jaunty/karmic lenny/squeeze/sid... 
Regards,
Hi Robert-
Thanks. As a sanity check I first used the image you suggested on the
beagle to first see what it *should* do before I took a bash at the
Overo. I'm most interested in getting a factional Ubuntu desktop so I
did a "sudo apt-get install xfce4 gdm xubuntu-gdm-theme xubuntu-
artwork" as you suggested but the results were disappointing. The
"desktop" I got had a mouse pointer but nothing else except for the
upper left quarter of the screen in which there was a non-resizable
and non-movable terminal window. No icons, menus, or anything else
GUI-ish. Does this sound familiar? How to get something like the
full Ubuntu desktop?
Also I tried changing the password once and forever after whenever I
need to do a "sudo" the system insists that I change my password again
(and it rejects any attempt to change it to something simple).
Is there a way around these problems?
Thanks,
Dan
Hi Robert-
Thanks. As a sanity check I first used the image you suggested on the
beagle to first see what it *should* do before I took a bash at the
Overo. I'm most interested in getting a factional Ubuntu desktop so I
did a "sudo apt-get install xfce4 gdm xubuntu-gdm-theme xubuntu-
artwork" as you suggested but the results were disappointing. The
"desktop" I got had a mouse pointer but nothing else except for the
upper left quarter of the screen in which there was a non-resizable
and non-movable terminal window. No icons, menus, or anything else
GUI-ish. Does this sound familiar? How to get something like the
full Ubuntu desktop?
Yeap, that's familiar and an annoying bug.. You've loaded xterm.. On
boot, when the gdm login appears, enter/click the user name. If your
resolution is correct, do you notice a drop down menu on the bottom
with the setting "xterm"? Switch that to "xfce4", note this only
shows up with 'xubuntu-gdm-theme' which is why i had you install
that.. Now when you complete login, you'll start xfce4.
Note the --seed i recommended is the absolute minimum for a working
xfce4 window interface. If you want a full blown ubuntu desktop, use
'xubuntu-desktop'.. But you'll need a 4Gb+ card and a large swap
partition..
Also I tried changing the password once and forever after whenever I
need to do a "sudo" the system insists that I change my password again
(and it rejects any attempt to change it to something simple).
Yeah, that's annoying, here's my workaround..
sudo ntpdate pool.ntp.org (make sure time is correct is crucial)
sudo su
passwd <user>
exit
Regards,
Hi Robert-
Thanks for the tips- I now have Ubuntu up on the beagle and I like what I
see so far. But despite following the http://elinux.org/BeagleBoardUbuntu
site SGX does not seem to be working. All the steps seem to succeed but
ChameleonMan still fails with the error "Unable to open X displayInitOS
failed!":
ubuntu@beagleboard:~$ sudo rm /etc/powervr-esrev
ubuntu@beagleboard:~$ sudo depmod -a omaplfb
ubuntu@beagleboard:~$ sudo /etc/init.d/pvr restart
Stopping PVR
Starting PVR
Starting SGX fixup for ES3.x
ubuntu@beagleboard:~$ cd
OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan
ubuntu@beagleboard:~/OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan$
GLESChameleonManrd:~/OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan$
./O
Unable to open X displayInitOS failed!
ubuntu@beagleboard:~/OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan$
Any ideas?
I've decided to retreat to the beagle and do all my code development on it
to take advantage of all the online support and then jump to the Overo as a
final step. But to make development on the beagle easier I'd really like to
get an NFS mount working. Have you been able to accomplish this using a USB
etherne dongel?
Thanks,
Dan
Behalf Of Robert Nelson
One more thing; once the SGX OGLES acceleration is up should the GL Ubuntu
screen savers start using it automatically? Thanks, Dan
Hi Robert-
Thanks for the tips- I now have Ubuntu up on the beagle and I like what I
see so far. But despite following the BeagleBoardUbuntu - eLinux.org
site SGX does not seem to be working. All the steps seem to succeed but
ChameleonMan still fails with the error "Unable to open X displayInitOS
failed!":ubuntu@beagleboard:~$ sudo rm /etc/powervr-esrev
ubuntu@beagleboard:~$ sudo depmod -a omaplfb
ubuntu@beagleboard:~$ sudo /etc/init.d/pvr restart
Stopping PVR
Starting PVR
Starting SGX fixup for ES3.x
ubuntu@beagleboard:~$ cd
OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan
ubuntu@beagleboard:~/OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan$
GLESChameleonManrd:~/OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan$
./O
Unable to open X displayInitOS failed!
ubuntu@beagleboard:~/OGLES/SDKPackage/Binaries/CommonX11/Demos/ChameleonMan$Any ideas?
I've decided to retreat to the beagle and do all my code development on it
to take advantage of all the online support and then jump to the Overo as a
final step. But to make development on the beagle easier I'd really like to
get an NFS mount working. Have you been able to accomplish this using a USB
etherne dongel?Thanks,
Dan
Hi Dan,
Strange, Is this with xorg running in a windows manager session?
Nothing weird in dmesg after the loading of the modules? Are you
using the uImage and modules from the bzr script?
One more thing; once the SGX OGLES acceleration is up should the GL Ubuntu
screen savers start using it automatically? Thanks, Dan
Sadly, no... The SGX is pretty limited, it only supports opengl-es,
not the full opengl spec... Although in the last year more
applications have been ported from the full opengl to the opengl-es to
be used on arm devices n900/beagle/etc...
Regards,
Hi Robert-
It does work but only if the demo is launched from a terminal window
ON the xorg screen; strangely it cannot be launched from a serial
terminal.
About Overo support you suggested getting an Overo Ubuntu kernel from
Sakoman- is it that easy? More specifically what I'm asking is do you
know that all the code that will differ between the Overo and the
Beagleboard is confined to the kernel? And can we expect that if a
rootfs works fine under a Beagleboard kernel on a Beagleboard then
that exact same rootfs is guaranteed to work fine under an Overo
kernel on an Overo board?
I have been searching for a clear summary of the hardware differences
between the Overo and the Beagleboard and what that implies about what
code changes will be required to port code from one to the other.
I've looked at rootstock and there is the "--fqdn" field... if I just
choose "--fqdn overo" will that activate all the relevant compile
options to build for the Overo?
Thanks,
Dan
Hi Robert-
It does work but only if the demo is launched from a terminal window
ON the xorg screen; strangely it cannot be launched from a serial
terminal.
This is standard X behaviour - there is no window environment when
running from the serial terminal. You can get it though - just execute
this line before any others:
$ export DISPLAY=:0.0
$ sudo /etc/init.d/pvr restart
Hello,
Hi Robert-
It does work but only if the demo is launched from a terminal window
ON the xorg screen; strangely it cannot be launched from a serial
terminal.
Actually I've done it previously from a serial terminal window, but
yes it's way more straight forward to do it in an active xorg terminal
window...
About Overo support you suggested getting an Overo Ubuntu kernel from
Sakoman- is it that easy? More specifically what I'm asking is do you
know that all the code that will differ between the Overo and the
Beagleboard is confined to the kernel? And can we expect that if a
rootfs works fine under a Beagleboard kernel on a Beagleboard then
that exact same rootfs is guaranteed to work fine under an Overo
kernel on an Overo board?
Yes, the same rootfs would work under the Overo.. Why wouldn't it? As
the only specific thing is the uImage you boot with on your SD card
and the modules for that uImage that we installed into
/lib/modules/...
Note: The kernel uImage you used for the beagleboard, might work with
the overo, as I have most of the other omap3 boards enabled. But it
only would be whatever is in the original 2.6.32 kernel. As i don't
have an overo board and didn't patch any external overo patches.
I have been searching for a clear summary of the hardware differences
between the Overo and the Beagleboard and what that implies about what
code changes will be required to port code from one to the other.
I've looked at rootstock and there is the "--fqdn" field... if I just
choose "--fqdn overo" will that activate all the relevant compile
options to build for the Overo?
Nope... rootstock isn't that advanced yet.. fqdn = "fully qualified
domain name"
so: --fqdn <hostname>
Regards,
Hi Robert-
I did try your kernel and roots on my Overo and got the result below.
What can you tell me about these errors?:
init: ureadahead main process (38) terminated with status 5
mountall: Could not connect to Plymouth
init: procps main process (67) terminated with status 255
Thanks,
Dan
3141024 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3140960 Bytes = 3 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing
Linux.............................................................................................................................................................................................................
do.
[ 0.000000] Linux version 2.6.32.9-l9.1 (root@beagle-256mb-0) (gcc
version 4.4.3 (Ubuntu 4.4.3-1ubuntu1) ) #1 PREEMPT Thu Feb 25 02:09:36
UTC 2010
[ 0.000000] CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7),
cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing
instruction cache
[ 0.000000] Machine: Gumstix Overo
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] OMAP3430/3530 ES2.1 (l2cache iva sgx neon isp )
[ 0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size:
0x100000
[ 0.000000] Reserving 12582912 bytes SDRAM for VRAM
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS2,115200n8 vram=12M
omapfb.mode=dvi:800x600MR-24@60 omapfb.debug=y omapdss.def_disp=dvi
root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5,
131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536
bytes)
[ 0.000000] Memory: 128MB 128MB = 256MB total
[ 0.000000] Memory: 240512KB available (5976K code, 735K data, 192K
init, 0K highmem)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:402
[ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/331/500 MHz
[ 0.000000] Reprogramming SDRC clock to 331882352 Hz
[ 0.000000] GPMC revision 5.0
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96
interrupts
[ 0.000000] Total of 96 interrupts on 1 active controller
[ 0.000000] OMAP GPIO hardware version 2.5
[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Calibrating delay loop... 499.92 BogoMIPS (lpj=1949696)
[ 0.000000] Security Framework initialized
[ 0.000000] Smack: Initializing.
[ 0.000000] Mount-cache hash table entries: 512
[ 0.000000] CPU: Testing write buffer coherency: ok
[ 0.000000] devtmpfs: initialized
[ 0.000000] regulator: core version 0.5
[ 0.000000] NET: Registered protocol family 16
[ 0.000000] Found NAND on CS0
[ 0.000000] Registering NAND on CS0
[ 13.935577] OMAP DMA hardware revision 4.0
[ 13.943572] bio: create slab <bio-0> at 0
[ 13.945373] SCSI subsystem initialized
[ 13.947113] usbcore: registered new interface driver usbfs
[ 13.947296] usbcore: registered new interface driver hub
[ 13.947509] usbcore: registered new device driver usb
[ 13.960144] i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz
[ 13.963043] twl4030: PIH (irq 7) chaining IRQs 368..375
[ 13.963104] twl4030: power (irq 373) chaining IRQs 376..383
[ 13.963439] twl4030: gpio (irq 368) chaining IRQs 384..401
[ 13.964416] regulator: VUSB1V5: 1500 mV normal standby
[ 13.964691] regulator: VUSB1V8: 1800 mV normal standby
[ 13.964996] regulator: VUSB3V1: 3100 mV normal standby
[ 13.968811] twl4030_usb twl4030_usb: Initialized TWL4030 USB module
[ 13.969268] regulator: VMMC1: 1850 <--> 3150 mV normal standby
[ 13.983581] i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
[ 13.984954] Bluetooth: Core ver 2.15
[ 13.985168] NET: Registered protocol family 31
[ 13.985198] Bluetooth: HCI device and connection manager
initialized
[ 13.985198] Bluetooth: HCI socket layer initialized
[ 13.985229] NET: Registered protocol family 8
[ 13.985260] NET: Registered protocol family 20
[ 13.985351] NetLabel: Initializing
[ 13.985351] NetLabel: domain hash size = 128
[ 13.985382] NetLabel: protocols = UNLABELED CIPSOv4
[ 13.985473] NetLabel: unlabeled traffic allowed by default
[ 13.985809] Switching to clocksource 32k_counter
[ 13.999389] musb_hdrc: version 6.0, musb-dma, otg (peripheral
+host), debug=0
[ 13.999725] musb_hdrc: USB OTG mode controller at fa0ab000 using
DMA, IRQ 92
[ 14.000396] NET: Registered protocol family 2
[ 14.000671] IP route cache hash table entries: 2048 (order: 1, 8192
bytes)
[ 14.001464] TCP established hash table entries: 8192 (order: 4,
65536 bytes)
[ 14.001800] TCP bind hash table entries: 8192 (order: 3, 32768
bytes)
[ 14.001922] TCP: Hash tables configured (established 8192 bind
8192)
[ 14.001953] TCP reno registered
[ 14.002288] NET: Registered protocol family 1
[ 14.004760] VFS: Disk quotas dquot_6.5.2
[ 14.004882] Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
[ 14.008117] fuse init (API version 7.13)
[ 14.009338] Btrfs loaded
[ 14.009490] msgmni has been set to 470
[ 14.010742] alg: No test for stdrng (krng)
[ 14.010833] io scheduler noop registered
[ 14.010864] io scheduler anticipatory registered
[ 14.010864] io scheduler deadline registered
[ 14.011138] io scheduler cfq registered (default)
[ 14.024230] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 14.045898] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a
ST16654
[ 14.066558] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a
ST16654
[ 14.087188] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a
ST16654
[ 14.541320] console [ttyS2] enabled
[ 14.553314] brd: module loaded
[ 14.560729] loop: module loaded
[ 14.565429] omap2-nand driver initializing
[ 14.569824] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba
(Micron NAND 256MiB 1,8V 16-bit)
[ 14.579101] cmdlinepart partition parsing not available
[ 14.584442] Creating 5 MTD partitions on "omap2-nand":
[ 14.589660] 0x000000000000-0x000000080000 : "xloader"
[ 14.596282] 0x000000080000-0x000000240000 : "uboot"
[ 14.602783] 0x000000240000-0x000000280000 : "uboot environment"
[ 14.609741] 0x000000280000-0x000000680000 : "linux"
[ 14.617218] 0x000000680000-0x000010000000 : "rootfs"
[ 14.729217] smsc911x: Driver version 2008-10-21.
[ 14.734802] smsc911x-mdio: probed
[ 14.738281] eth0: attached PHY driver [Generic PHY]
(mii_bus:phy_addr=ffffffff:01, irq=-1)
[ 14.746795] net eth0: MAC Address: 00:15:c9:28:c7:57
[ 14.752502] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
Driver
[ 14.759460] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 14.765563] ehci-omap ehci-omap.0: new USB bus registered, assigned
bus number 1
[ 14.773437] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 14.790679] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[ 14.796630] usb usb1: New USB device found, idVendor=1d6b,
idProduct=0002
[ 14.803527] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 14.810821] usb usb1: Product: OMAP-EHCI Host Controller
[ 14.816192] usb usb1: Manufacturer: Linux 2.6.32.9-l9.1 ehci_hcd
[ 14.822265] usb usb1: SerialNumber: ehci-omap.0
[ 14.827423] usb usb1: configuration #1 chosen from 1 choice
[ 14.833343] hub 1-0:1.0: USB hub found
[ 14.837219] hub 1-0:1.0: 3 ports detected
[ 14.841888] Initializing USB Mass Storage driver...
[ 14.847045] usbcore: registered new interface driver usb-storage
[ 14.853088] USB Mass Storage support registered.
[ 14.857849] g_ether gadget: using random self ethernet address
[ 14.863769] g_ether gadget: using random host ethernet address
[ 14.870208] usb0: MAC d2:75:35:72:fc:0a
[ 14.874084] usb0: HOST MAC 4a:3b:9f:49:2e:7c
[ 14.878479] g_ether gadget: Ethernet Gadget, version: Memorial Day
2008
[ 14.885192] g_ether gadget: g_ether ready
[ 14.889221] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 14.894836] musb_hdrc musb_hdrc: new USB bus registered, assigned
bus number 2
[ 14.902282] usb usb2: New USB device found, idVendor=1d6b,
idProduct=0002
[ 14.909179] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 14.916473] usb usb2: Product: MUSB HDRC host driver
[ 14.921478] usb usb2: Manufacturer: Linux 2.6.32.9-l9.1 musb-hcd
[ 14.927551] usb usb2: SerialNumber: musb_hdrc
[ 14.932495] usb usb2: configuration #1 chosen from 1 choice
[ 14.938323] hub 2-0:1.0: USB hub found
[ 14.942260] hub 2-0:1.0: 1 port detected
[ 14.947265] mice: PS/2 mouse device common for all mice
[ 14.953735] input: twl4030_pwrbutton as /devices/platform/i2c_omap.
1/i2c-1/1-0049/twl4030_pwrbutton/input/input0
[ 14.964660] i2c /dev entries driver
[ 14.969360] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
[ 15.080749] Advanced Linux Sound Architecture Driver Version
1.0.21.
[ 15.087829] usbcore: registered new interface driver snd-usb-audio
[ 15.094207] No device for DAI twl4030
[ 15.097961] No device for DAI twl4030 Voice
[ 15.102172] No device for DAI omap-mcbsp-dai-0
[ 15.106689] No device for DAI omap-mcbsp-dai-1
[ 15.111175] No device for DAI omap-mcbsp-dai-2
[ 15.115661] No device for DAI omap-mcbsp-dai-3
[ 15.120147] No device for DAI omap-mcbsp-dai-4
[ 15.124633] Not OMAP3 EVM!
[ 15.127380] ALSA device list:
[ 15.130371] No soundcards found.
[ 15.133880] oprofile: using arm/armv7
[ 15.137939] TCP cubic registered
[ 15.141815] NET: Registered protocol family 10
[ 15.147277] lo: Disabled Privacy Extensions
[ 15.152099] NET: Registered protocol family 17
[ 15.156616] NET: Registered protocol family 15
[ 15.161346] Bluetooth: L2CAP ver 2.14
[ 15.165039] Bluetooth: L2CAP socket layer initialized
[ 15.170196] Bluetooth: SCO (Voice Link) ver 0.6
[ 15.174774] Bluetooth: SCO socket layer initialized
[ 15.180664] Bluetooth: RFCOMM TTY layer initialized
[ 15.185668] Bluetooth: RFCOMM socket layer initialized
[ 15.190887] Bluetooth: RFCOMM ver 1.11
[ 15.194885] ThumbEE CPU extension supported.
[ 15.199218] Power Management for TI OMAP3.
[ 15.216339] VFP support v0.3: implementor 41 architecture 3 part 30
variant c rev 1
[ 15.225097] registered taskstats version 1
[ 15.229461] omapfb omapfb: no displays
[ 15.233276] omapfb omapfb: failed to setup omapfb
[ 15.238067] omapfb: probe of omapfb failed with error -22
[ 15.244384] Waiting for root device /dev/mmcblk0p2...
[ 15.478210] usb 2-1: new high speed USB device using musb_hdrc and
address 2
[ 15.509582] mmc0: host does not support reading read-only switch.
assuming write-enable.
[ 15.517761] mmc0: new SD card at address e624
[ 15.522766] mmcblk0: mmc0:e624 SU02G 1.89 GiB
[ 15.527740] mmcblk0: p1 p2
[ 15.619720] mmc1: new SDIO card at address 0001
[ 15.628173] usb 2-1: New USB device found, idVendor=05e3,
idProduct=0608
[ 15.636138] usb 2-1: New USB device strings: Mfr=0, Product=1,
SerialNumber=0
[ 15.643402] mmcblk0: retrying using single block read
[ 15.648529] usb 2-1: Product: USB2.0 Hub
[ 15.653259] usb 2-1: configuration #1 chosen from 1 choice
[ 15.659484] hub 2-1:1.0: USB hub found
[ 15.663726] hub 2-1:1.0: 4 ports detected
[ 15.955017] usb 2-1.2: new low speed USB device using musb_hdrc and
address 3
[ 16.086425] usb 2-1.2: device v046e p550f is not supported
[ 16.091979] usb 2-1.2: New USB device found, idVendor=046e,
idProduct=550f
[ 16.098937] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 16.106353] usb 2-1.2: Product: USB Multimedia Keyboard
[ 16.111633] usb 2-1.2: Manufacturer: BTC
[ 16.116180] usb 2-1.2: configuration #1 chosen from 1 choice
[ 16.204956] usb 2-1.3: new low speed USB device using musb_hdrc and
address 4
[ 16.326324] usb 2-1.3: device v045e p0737 is not supported
[ 16.331909] usb 2-1.3: New USB device found, idVendor=045e,
idProduct=0737
[ 16.338867] usb 2-1.3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 16.346252] usb 2-1.3: Product: Compact Optical Mouse 500
[ 16.351684] usb 2-1.3: Manufacturer: Microsoft
[ 16.356719] usb 2-1.3: configuration #1 chosen from 1 choice
[ 17.879547] EXT3-fs warning: maximal mount count reached, running
e2fsck is recommended
[ 17.887695] kjournald starting. Commit interval 5 seconds
[ 17.958435] EXT3 FS on mmcblk0p2, internal journal
[ 17.963317] EXT3-fs: recovery complete.
[ 17.971832] EXT3-fs: mounted filesystem with writeback data mode.
[ 17.978027] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 17.986328] devtmpfs: mounted
[ 17.989410] Freeing init memory: 192K
init: ureadahead main process (38) terminated with status 5
mountall: Could not connect to Plymouth
init: procps main process (67) terminated with status 255
Ubuntu lucid (development branch) beagleboard ttyS2
beagleboard login: ubuntu
Password:
Last login: Wed Dec 31 17:01:20 MST 1969 on ttyS2
Linux beagleboard 2.6.32.9-l9.1 #1 PREEMPT Thu Feb 25 02:09:36 UTC
2010 armv7l
For official documentation, please visit:
* http://help.ubuntu.com/
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
ubuntu@beagleboard:~$
Hello,
Hi Robert-
I did try your kernel and roots on my Overo and got the result below.
What can you tell me about these errors?:init: ureadahead main process (38) terminated with status 5
init: procps main process (67) terminated with status 255
These are safe to ignore...
mountall: Could not connect to Plymouth
This could be solved with putting plymouth in an initramfs and it
would give us a fancy boot screen... safe to ignore..
Otherwise, very cool... The kernel worked... 
Regards,
Hi Robert-
With the realization that ubuntu will run on my Overo I've decided
upon that distro for my development. To verify that I could actually
build this all using rootstock as your page explains I ran:
sudo rootstock --fqdn beagleboard --login ubuntu --password temppwd --
imagesize 2G --seed wget,nano,linux-firmware,wireless-tools,usbutils --
dist lucid --serial ttyS2 --script fixup.sh --kernel-image
http://rcn-ee.net/deb/kernel/beagle/lucid/v2.6.32.9-l9.1/linux-image-2.6.32.9-l9.1_1.0lucid_armel.deb
but I got:
...
I: First stage install done
I: Downloading kernel image (deb) from external site
I: linux-image-2.6.32.9-l9.1_1.0lucid_armel.deb download complete
I: Setting up serial tty in image
I: Creating swapfile in tmpfs for VM
I: Getting Virtual Machine kernel from the server
I: Switching to Virtual Machine for second stage processing
E: Second stage build in Virtual Machine failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: A logfile was saved as /home/dwright/lucidrootstock/
rootstock-201003110857.log
I: done ...
dwright@dwright-Ubuntu:~/lucidrootstock$
The end of the log file shows:
...
I: Configuring libc-bin...
I: Configuring initramfs-tools...
I: Base system installed successfully.
248+0 records in
248+0 records out
260046848 bytes (260 MB) copied, 0.284801 s, 913 MB/s
Setting up swapspace version 1, size = 253948 KiB
no label, UUID=f8499174-99b3-4902-99cb-f17bc2b0cd1d
--2010-03-11 09:06:12-- http://people.canonical.com/~ogra//arm/qemu/kernel/vmlinuz-2.6.28-versatile
Resolving people.canonical.com... 91.189.89.62
Connecting to people.canonical.com|91.189.89.62|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1674880 (1.6M) [text/plain]
Saving to: `/tmp/tmp.Av5UhP0BPA/qemu-vmlinuz'
0K .......... .......... .......... .......... .......... 3%
79.3K 20s
50K .......... .......... .......... .......... .......... 6%
288K 12s
100K .......... .......... .......... .......... .......... 9%
363K 9s
150K .......... .......... .......... .......... .......... 12%
620K 7s
200K .......... .......... .......... .......... .......... 15%
631K 6s
250K .......... .......... .......... .......... .......... 18%
606K 5s
300K .......... .......... .......... .......... .......... 21%
618K 5s
350K .......... .......... .......... .......... .......... 24%
631K 4s
400K .......... .......... .......... .......... .......... 27%
606K 4s
450K .......... .......... .......... .......... .......... 30%
138K 4s
500K .......... .......... .......... .......... .......... 33%
910K 4s
550K .......... .......... .......... .......... .......... 36%
1.88M 3s
600K .......... .......... .......... .......... .......... 39%
139M 3s
650K .......... .......... .......... .......... .......... 42%
1.58M 3s
700K .......... .......... .......... .......... .......... 45%
1.12M 2s
750K .......... .......... .......... .......... .......... 48%
357K 2s
800K .......... .......... .......... .......... .......... 51%
313K 2s
850K .......... .......... .......... .......... .......... 55%
620K 2s
900K .......... .......... .......... .......... .......... 58%
605K 2s
950K .......... .......... .......... .......... .......... 61%
618K 2s
1000K .......... .......... .......... .......... .......... 64%
633K 1s
1050K .......... .......... .......... .......... .......... 67%
622K 1s
1100K .......... .......... .......... .......... .......... 70%
633K 1s
1150K .......... .......... .......... .......... .......... 73%
605K 1s
1200K .......... .......... .......... .......... .......... 76%
616K 1s
1250K .......... .......... .......... .......... .......... 79%
637K 1s
1300K .......... .......... .......... .......... .......... 82%
605K 1s
1350K .......... .......... .......... .......... .......... 85%
633K 1s
1400K .......... .......... .......... .......... .......... 88%
618K 0s
1450K .......... .......... .......... .......... .......... 91%
635K 0s
1500K .......... .......... .......... .......... .......... 94%
620K 0s
1550K .......... .......... .......... .......... .......... 97%
618K 0s
1600K .......... .......... .......... ..... 100%
625K=3.5s
2010-03-11 09:06:16 (466 KB/s) - `/tmp/tmp.Av5UhP0BPA/qemu-vmlinuz'
saved [1674880/1674880]
Kernel panic - not syncing: Attempted to kill init!
I: Killed ...
Have you seen this too?
Thanks,
Dan
Nope, i haven't.. I would try again. If it fails again at the same
location, save the log file and I'd ping ogra on #ubuntu-arm qemu
isn't perfect and at times can be pretty random..
Regards,
Hi Robert-
I thought I might avoid the build problems for now and simply use your
images. I'm trying to set up booting your kernel using NFS because
that's so much more convenient during development. Is the pre-build
kernel from your site built without NFS enabled? My attempted NFS
boots fail like so:
...
[ 39.158020] IP-Config:
Complete:
[ 39.161102] device=eth0, addr=192.168.1.64,
mask=255.255.255.0,
gw=192.168.1.254,
[ 39.169067] host=overo, domain=, nis-
domain=(none),
[ 39.174468] bootserver=192.168.1.65, rootserver=192.168.1.65,
rootpath=
[ 39.182800] VFS: Cannot open root device "nfs" or unknown-
block(0,255)
[ 39.189422] Please append a correct "root=" boot option; here are
the available
partitions:
[ 39.197906] 1f00 512 mtdblock0
(driver?)
[ 39.202941] 1f01 1792 mtdblock1
(driver?)
[ 39.207977] 1f02 256 mtdblock2
(driver?)
[ 39.213043] 1f03 4096 mtdblock3
(driver?)
[ 39.218048] 1f04 255488 mtdblock4
(driver?)
[ 39.223083] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,255)
...
Thanks,
Dan
Hi Dan,
Hi Robert-
I thought I might avoid the build problems for now and simply use your
images. I'm trying to set up booting your kernel using NFS because
that's so much more convenient during development. Is the pre-build
kernel from your site built without NFS enabled? My attempted NFS
boots fail like so:...
[ 39.158020] IP-Config:
Complete:
[ 39.161102] device=eth0, addr=192.168.1.64,
mask=255.255.255.0,
gw=192.168.1.254,
[ 39.169067] host=overo, domain=, nis-
domain=(none),
[ 39.174468] bootserver=192.168.1.65, rootserver=192.168.1.65,
rootpath=
[ 39.182800] VFS: Cannot open root device "nfs" or unknown-
block(0,255)
[ 39.189422] Please append a correct "root=" boot option; here are
the available
partitions:
[ 39.197906] 1f00 512 mtdblock0
(driver?)
[ 39.202941] 1f01 1792 mtdblock1
(driver?)
[ 39.207977] 1f02 256 mtdblock2
(driver?)
[ 39.213043] 1f03 4096 mtdblock3
(driver?)
[ 39.218048] 1f04 255488 mtdblock4
(driver?)
[ 39.223083] Kernel panic - not syncing: VFS: Unable to mount root
fs on unknown-block(0,255)
Yeah, it looks like i didn't' enable all the NFS options..
CONFIG_NFS_FS=y & CONFIG_ROOT_NFS=y
Give this attached patch a try against my 2.6-stable tree
and don't forget to also move your eth0 device drive to built-in 'y'
as most are setup as modules...
bzr branch lp:~beagleboard-kernel/+junk/2.6-stable
cd 2.6-stable
patch -p0 < enable-nfs-rootfs.diff
bzr diff to verify...
then run ". build_kernel.sh" It'll tell you how to setup your CC environment..
Regards,
enable-nfs-rootfs.diff (1.24 KB)
Hi Robert-
Thanks. Is this "2.6-stable" kernel source something with Ubuntu-
omap3 specific mods or is this just the standard Linux source with the
appropriate configuration settings?
Also to help you better understand my target application I have made a
small PCB with Bluetooth, a litium-ion battery and power circuitry
that accepts an Overo Water. There is a CPLD and video DACs and this
system connects to (and powers) a pair of eMagine NTE displays (see:
http://www.emagin.com/products/systems/Z800.php). This HW completely
replaces the electronics that come with the displays. The Bluetooth I
use for a wireless mouse.
But these displays rigidly constrain my graphics settings; the only
resolution that this HW supports is 800x600 24bpp. The displays are
capable of sterio display and I hope to hack some existing SGX-
accelerated general 3D object browser to render each 3D scene twice
with a small horizontal displacent in the camera positions to feed to
the right and left displays. This would give interactive 3D. And
since this is running a full desktop perhaps people use this platform
to experiment with sterio 3d UI's.
Do you know if SGX acceleration supports 800x600 24bpp?
Thanks,
Dan
Hi Dan,
Hi Robert-
Thanks. Is this "2.6-stable" kernel source something with Ubuntu-
omap3 specific mods or is this just the standard Linux source with the
appropriate configuration settings?
It's linus' stable branch + tmlind's patches + tweaks and settings for
omap boards. This is where i develop my *.deb files on rcn-ee.net
from..
Also to help you better understand my target application I have made a
small PCB with Bluetooth, a litium-ion battery and power circuitry
that accepts an Overo Water. There is a CPLD and video DACs and this
system connects to (and powers) a pair of eMagine NTE displays (see:
Home - eMagin). This HW completely
replaces the electronics that come with the displays. The Bluetooth I
use for a wireless mouse.
That sounds cool...
But these displays rigidly constrain my graphics settings; the only
resolution that this HW supports is 800x600 24bpp. The displays are
capable of sterio display and I hope to hack some existing SGX-
accelerated general 3D object browser to render each 3D scene twice
with a small horizontal displacent in the camera positions to feed to
the right and left displays. This would give interactive 3D. And
since this is running a full desktop perhaps people use this platform
to experiment with sterio 3d UI's.Do you know if SGX acceleration supports 800x600 24bpp?
I think the latest (3_01_00_02) supports 24 bit mode...
Specially based on the "fbset" setting here:
http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/powervr-drivers/libgles-omap3/rc.pvr
Sorry, other then checking the SGX modules by testing them with a
quick SGX demo I haven't done much with them..
Hopefully someone on this list with more SGX experience will have read
this message and add their 2 cents..
Regards,
Hi Robert-
I applied the patch to 2.6-stable/patches/defconfig and the relevant
network driver is set to be built in. Still it did not work. I did a
comparison between:
2.6-stable/patches/defconfig
and
2.6-stable/KERNEL/.config
and I find that all the NFS settings had reverted back. How can I
force the build use the settins I put into 2.6-stable/patches/
defconfig?
Thanks,
Dan
Hi Dan,
nfs-2.diff (2.28 KB)