Pandaboard rev B3 and Ubuntu

[dkar...@gmail.com]

Hello Group,

I recently got the Rev B3 of the pandaboard with the new memory modules and now have some problems with booting Ubuntu.

First I updated u-boot with patches to get the boot working and tried my existing Ubuntu (12.04 server) install, but no go. After that I tried Linaro Android and that boots just fine. Then I tried to reinstall Ubuntu (13.04 server) and the installer booted up just fine. I was able to setup the install and let it make a ext partition on the SD card. But after install the boot hangs at exactly the same point as my original Ubuntu install.

The boot process on the B2 board just goes without any issues and both the old and new image boot, so my guess is that's a memory setting of the kernel.

My uEnv.txt:
bootcmd=setenv bootargs ro elevator=noop mem=1G@0x80000000 root=/dev/mmcblk0p2 fixrtc splash omapdss.def_disp=dvi omapfb.mode=dvi:1280x1024-16 earlyprintk debug;fatload mmc 0:1 0x80000000 uImage;fatload mmc 0:1 0x81600000 uInitrd; bootm 0x80000000 0x81600000
uenvcmd=boot

Below the boot process:

U-Boot SPL 2013.07 (Aug 01 2013 - 10:53:02)
OMAP4460 ES1.1
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2013.07 (Aug 01 2013 - 10:53:02)

CPU  : OMAP4460 ES1.1
Board: OMAP4 Panda
I2C:   ready
DRAM:  1 GiB
MMC:   OMAP SD/MMC: 0
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  1  0
mmc0 is current device
SD/MMC found on device 0
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
308 bytes read in 3 ms (99.6 KiB/s)
Importing environment from mmc (uEnv.txt)...
Checking if uenvcmd is set ...
Running uenvcmd ...
reading uImage
4285496 bytes read in 195 ms (21 MiB/s)
reading uInitrd
1950115 bytes read in 91 ms (20.4 MiB/s)
## Booting kernel from Legacy Image at 80000000 ...
   Image Name:   kernel 3.5.0-223-omap4
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4285432 Bytes = 4.1 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
   Image Name:   ramdisk 3.5.0-223-omap4
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1950051 Bytes = 1.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.5.0-223-omap4 (buildd@rusalka) (gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) ) #34-Ubuntu SMP PREEMPT Wed Apr 17 18:42:53 UTC 2013 (Ubuntu 3.5.0-223.34-omap4 3.5.7.9)
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: OMAP4 Panda board
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] cma: CMA: reserved 16 MiB at ae000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] omap2_set_globals_tap
[    0.000000] On node 0 totalpages: 261888
[    0.000000] free_area_init_node: node 0, pgdat c092c380, node_mem_map c09f5000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 192784 pages, LIFO batch:31
[    0.000000]   HighMem zone: 528 pages used for memmap
[    0.000000]   HighMem zone: 67056 pages, LIFO batch:15
[    0.000000] omap2_set_globals_tap
[    0.000000] OMAP4460 ES1.1
[    0.000000] PERCPU: Embedded 8 pages/cpu @c11ff000 s11712 r8192 d12864 u32768
[    0.000000] pcpu-alloc: s11712 r8192 d12864 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 259840
[    0.000000] Kernel command line: ro elevator=noop mem=1G@0x80000000 root=/dev/mmcblk0p3 fixrtc splash omapdss.def_disp=dvi omapfb.mode=dvi:1280x1024-16 earlyprintk debug console=tty0 console=ttyO2,115200n8
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] allocated 2097152 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Memory: 759MB 264MB = 1023MB total
[    0.000000] Memory: 1007880k/1007880k available, 40696k reserved, 270336K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc084dd14   (8472 kB)
[    0.000000]       .init : 0xc084e000 - 0xc08afdc0   ( 392 kB)
[    0.000000]       .data : 0xc08b0000 - 0xc092f6f8   ( 510 kB)
[    0.000000]        .bss : 0xc092f71c - 0xc09f4dbc   ( 790 kB)
[    0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:538
[    0.000000] omap_sr_disable: omap_sr struct for sr_wakeup not found
[    0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz
[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[    0.000000] OMAP clocksource: 32k_counter at 32768 Hz
[    0.000000] Console: colour dummy device 80x30
[    0.000000] console [tty0] enabled
[    0.015502] Calibrating delay loop... 1392.74 BogoMIPS (lpj=5439488)
[    0.051696] pid_max: default: 32768 minimum: 301
[    0.056823] Security Framework initialized
[    0.061187] AppArmor: AppArmor initialized
[    0.065551] Yama: becoming mindful.
[    0.069549] Mount-cache hash table entries: 512
[    0.075836] Initializing cgroup subsys cpuacct
[    0.080596] Initializing cgroup subsys memory
[    0.085266] Initializing cgroup subsys devices
[    0.089996] Initializing cgroup subsys freezer
[    0.094665] Initializing cgroup subsys blkio
[    0.099212] Initializing cgroup subsys perf_event
[    0.104339] CPU: Testing write buffer coherency: ok
[    0.109558] ftrace: allocating 22788 entries in 67 pages
[    0.174194] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.180328] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
[    0.188934] Setting up static identity map for 0x805972d0 - 0x80597328
[    0.195739] L310 cache controller enabled
[    0.200012] l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x7e470000, Cache size: 1048576 B
[    0.208618] omap_sar_ram_init
[    0.212005] generating sar_ram layout...
[    0.216278] sar ram layout created
[    0.297851] CPU1: Booted secondary processor
[    0.367858] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.367889] CPU1: Unknown IPI message 0x1
[    0.367919] Brought up 2 CPUs
[    0.367919] SMP: Total of 2 processors activated (2792.83 BogoMIPS).
[    0.368865] devtmpfs: initialized
[    0.375183] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.375213] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.375244] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.377960] omap_hwmod: sl2if: _wait_target_ready error: -16
[    0.377960] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.377960] omap_hwmod: sl2if: cannot be enabled for reset (3)
[    0.378936] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.378967] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.378997] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.379028] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.381713] omap_hwmod: mcpdm: _wait_target_ready error: -16
[    0.381713] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.381713] omap_hwmod: mcpdm: cannot be enabled for reset (3)
[    0.381896] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.382019] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.382049] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.382080] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.382110] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.384033] omap_sr_disable: omap_sr struct for sr_iva not found
[    0.384552] dummy:
[    0.385681] NET: Registered protocol family 16
[    0.386413] Trying to unpack rootfs image as initramfs...
[    0.373352] ttyO2 used as console in debug mode uart2 clocks will not be gated
[    0.529571] Freeing initrd memory: 1904K
[    0.550445] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.558074] GPMC revision 6.0
[    0.561248] gpmc: irq-52 could not claim: err -22
[    0.567932] OMAP GPIO hardware version 0.1
[    0.574493] omap_mux_init: Add partition: #1: core, flags: 2
[    0.581542] omap_mux_init: Add partition: #2: wkup, flags: 2
[    0.588928] omap_mux_get_by_name: Could not find signal uart1_rx.uart1_rx
[    0.616638] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.624999] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.633819] Updated GPU clock source to be dpll_per_m7x2_ck
[    0.641510]  omap-mcbsp.1: alias pad_fck already exists
[    0.647003]  omap-mcbsp.1: alias prcm_fck already exists
[    0.652740]  omap-mcbsp.2: alias pad_fck already exists
[    0.658233]  omap-mcbsp.2: alias prcm_fck already exists
[    0.663940]  omap-mcbsp.3: alias pad_fck already exists
[    0.669464]  omap-mcbsp.3: alias prcm_fck already exists
[    0.675170]  omap-mcbsp.4: alias pad_fck already exists
[    0.680694]  omap-mcbsp.4: alias prcm_fck already exists
[    0.686401]  omap4plus_scm.0: alias fck already exists
[    0.692657] OMAP DMA hardware revision 0.0

At this point the board hangs with the two leds solid on.

Thanks in advance,

Dennis Karmelk

[Robert Nelson]

On Fri, Aug 2, 2013 at 5:14 AM, <dkar...@gmail.com> wrote:
> Hello Group,
>
> I recently got the Rev B3 of the pandaboard with the new memory modules and
> now have some problems with booting Ubuntu.
>
> First I updated u-boot with patches to get the boot working and tried my
> existing Ubuntu (12.04 server) install, but no go. After that I tried Linaro
> Android and that boots just fine. Then I tried to reinstall Ubuntu (13.04
> server) and the installer booted up just fine. I was able to setup the
> install and let it make a ext partition on the SD card. But after install
> the boot hangs at exactly the same point as my original Ubuntu install.
>
> The boot process on the B2 board just goes without any issues and both the
> old and new image boot, so my guess is that's a memory setting of the
> kernel.

Yeap, every existing kernel build is still busted.. We need to go back
and patch/re-build them all, which is going to be a pain..

It might just be easy to go forward instead as in the panda device
tree we define the memory interface:

emif cs defines:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/omap4-panda-common.dtsi#n321

On the new memory only one cs is used..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[xen...@gmail.com]

Hi guys,

Quick question - Robert, does your comment imply it's no longer possible to run the TI PPA 12.04 kernel on a Rev B3 board?

Thanks

[Robert Nelson]

On Tue, Oct 1, 2013 at 8:48 PM, <xen...@gmail.com> wrote:
> Hi guys,
>
> Quick question - Robert, does your comment imply it's no longer possible to
> run the TI PPA 12.04 kernel on a Rev B3 board?

Just patch u-boot first and find out..

on mainline (v2013.07), this what you need to do..

http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-PandaBoardESRevB3:NewMemoryTimings

For device tree and later (aka 3.11.x) i'm still working on something..

[Bob Smiley]

On Tue, Oct 1, 2013 at 10:09 PM, Robert Nelson <robert...@gmail.com> wrote:

On Tue, Oct 1, 2013 at 8:48 PM,  <xen...@gmail.com> wrote:
> Hi guys,
>
> Quick question - Robert, does your comment imply it's no longer possible to
> run the TI PPA 12.04 kernel on a Rev B3 board?

Just patch u-boot first and find out..

Fair enough.  That said, I followed your u-boot install instructions and the board now boots, but then appears to immediately shut down (the LEDs turn off and there is no video).

I got rid of my original boot.scr file (as configured per previous 12.04 TI omap instructions).  When I dropped in the uEnv.txt file, things did not work as it couldn't find my original kernel image (I need to fix the paths).  Before doing that though, I tried to manually boot by specifying the following:

fatload mmc 0:1 0x80000000 uImage

fatload mmc 0:1 0x81600000 uInitrd

setenv bootargs ro elevator=noop console=ttyO2,115200n8 mem=1G@0x80000000 root=/dev/mmcblk0p2 fixrtc splash

bootm 0x80000000 0x81600000

Same problem, board appears to boot then shutdown.  Any suggestions?

Those settings still work on my Rev B2 board with the latest u-boot.  

Here's the boot-up details if helpful:

## Booting kernel from Legacy Image at 80000000 ...

   Image Name:   Ubuntu Kernel

   Image Type:   ARM Linux Kernel Image (uncompressed)

   Data Size:    4416048 Bytes = 4.2 MiB

   Load Address: 80008000

   Entry Point:  80008000

   Verifying Checksum ... OK

## Loading init Ramdisk from Legacy Image at 81600000 ...

   Image Name:   Ubuntu Initrd

   Image Type:   ARM Linux RAMDisk Image (uncompressed)

   Data Size:    4734650 Bytes = 4.5 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Thanks!

on mainline (v2013.07), this what you need to do..

http://eewiki.net/display/linuxonarm/PandaBoard#PandaBoard-PandaBoardESRevB3:NewMemoryTimings

For device tree and later (aka 3.11.x) i'm still working on something..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

--
You received this message because you are subscribed to a topic in the Google Groups "pandaboard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pandaboard/n5h8wKJ84Ok/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pandaboard+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Robert Nelson]

Bummer, you have the correct serial port value so it should show
something. I'm guessing 12.04 ti omap kernel must be directly
accessing the CS lines in the emif (memory) driver. This is the same
issue that is causing issues with device tree boot (v3.11/v3.12-rc) to
eventually fail..

Mainline v3.7/v3.9 (board file) will boot successfully with the
modified u-boot as the kernel lacks the emif driver..

[Bob Smiley]

Thanks for the response.  Sounds like I'm out of luck unless one of the PPA maintainers can come through on this.  Think there's any chance of being able to make the required modifications by hand on the 12.04 kernel source?  Do you know it's a complicated change (I'll admit my kernel hacking skills are amateur at best)?

I'd be OK with moving to a different kernel if I could get the accelerated GLES2 drivers to work.  Think that's possible, or are there far too many dependencies on the TI 3.4 kernel and 12.04 Xorg?

Thanks!

[Bob Smiley]

I think I found a relevant discussion thread:

https://groups.google.com/forum/#!topic/pandaboard/OWvyla72e00

There appears to be a reference to the list of required changes for a 3.4 kernel:

https://docs.google.com/viewer?a=v&pid=forums&srcid=MDY1NzA1NTcyODgyOTA2NTQyNDkBMDkzMjI4OTIwNzQ3MTQ3NjgzNTMBSW5KT3Ywb3Zab1VKATMBAXYy

Do you happen to know if this is the same kernel tree used for the TI PPA?

Thanks!

[Bob Smiley]

One more thing, I just realized I built u-boot with the armel gcc (ubuntu package).  I'm installing armhf gcc now, but do you think that could have really made a difference?

I'm using all the same stuff from my 12.04 image (kernel, rootfs, etc..) with the only change being u-boot.

Thanks!

[Robert Nelson]

On Wed, Oct 2, 2013 at 6:52 PM, Bob Smiley <xen...@gmail.com> wrote:
> One more thing, I just realized I built u-boot with the armel gcc (ubuntu
> package). I'm installing armhf gcc now, but do you think that could have
> really made a difference?

It shouldn't, u-boot has no floating point code and it's built tested
on ancient compiler versions too..

> I'm using all the same stuff from my 12.04 image (kernel, rootfs, etc..)
> with the only change being u-boot.

[Bob Smiley]

Thanks, that's what I figured.

So I think I"ll take a crack at trying to apply the SVTronics mods from the aforementioned thread to the TI kernel pulled from:  git clone git://dev.omapzoom.org/pub/scm/integration/kernel-ubuntu.git

You haven't already tried this, have you?

Thanks!

[Bob Smiley]

So this is pretty neat...I got the board to boot!  Unfortunately I had to apply the SVT changes to branch: ti-ubuntu-3.4-1486.10.  A couple things aren't working like they did in my -1490 kernel (DVI is low res, HDMI works), but we're making progress!

Ideally I'd like to create a new kernel deb package, but the instructions I found on omappedia are not working.  

....../kernel-ubuntu.git# fakeroot debian/rules clean

sh: 1: arm-linux-gnueabihf-: not found

dpkg-architecture: warning: Couldn't determine gcc system type, falling back to default (native compilation)

Clearly it needs the gcc suffix, but I'm not sure why it's not automatically added.  Anyone know?

Ultimately I just need to get the pvr drivers working again so I can get accelerated GLES.  If I can't get my deb package built, which will retrigger the dkms re-build, can I just build and load them manually?

Thanks!

[Nicolas Dechesne]

On Thu, Oct 3, 2013 at 4:55 AM, Bob Smiley <xen...@gmail.com> wrote:
> So this is pretty neat...I got the board to boot! Unfortunately I had to
> apply the SVT changes to branch: ti-ubuntu-3.4-1486.10. A couple things
> aren't working like they did in my -1490 kernel (DVI is low res, HDMI
> works), but we're making progress!
>
> Ideally I'd like to create a new kernel deb package, but the instructions I
> found on omappedia are not working.
>
> ....../kernel-ubuntu.git# fakeroot debian/rules clean
>
> sh: 1: arm-linux-gnueabihf-: not found
> dpkg-architecture: warning: Couldn't determine gcc system type, falling back
> to default (native compilation)
>
> Clearly it needs the gcc suffix, but I'm not sure why it's not automatically
> added. Anyone know?

there are instructions to create .deb for kernel using the ubuntu kernel tree:
http://www.omappedia.com/wiki/Ubuntu_kernel_for_OMAP4

these instructions work both for native and cross compilation, though
it is clearly required to cross compile, you seem to be missing the
cross compiler:

http://www.omappedia.com/wiki/Ubuntu_kernel_for_OMAP4#armhf_cross-compiler_setup

>
> Ultimately I just need to get the pvr drivers working again so I can get
> accelerated GLES. If I can't get my deb package built, which will retrigger
> the dkms re-build, can I just build and load them manually?

a dkms rebuild is needed only when/if the kernel ABI changes.
otherwise you can just keep using the same modules. i haven't looked
at the changes needed for B3, but i don't you are changing ABIs.

note that dkms is 'just' a script that actually rebuilds the kernel
module source code on the target (building against the kernel headers
installed by the kernel .deb file). so you should be able to 'easily'
rebuild the kernel modules 'manually' too, on the target since you
have all you need (source code, gcc, and kernel headers).

[Bob Smiley]

Nicolas, thanks for the reply.  Those actually were the instructions I was following.  I'm pretty sure I have the cross compiler installed correctly as that is what I used to build u-boot and uImage.  I'm just not sure why the debian scripts can't find the tool chain.  Do I need to do some extra configuration step?  I'm pretty sure I followed all the instructions on the site.  I read something about people having a problem running on 64-bit hosts (as I am), but that seems like a long shot.

Note sure if this is related, but I also get the following errors while trying to execute the pacage build process:

# dpkg-checkbuilddeps -a armhf

dpkg-checkbuilddeps: Unmet build dependencies: libelf-dev libnewt-dev binutils-dev libdw-dev libgtk2.0-dev | gtk2-devel

# dpkg-architecture -aarmhf

sh: 1: arm-linux-gnueabihf-: not found

DEB_BUILD_ARCH=amd64

DEB_BUILD_ARCH_BITS=64

DEB_BUILD_ARCH_CPU=amd64

DEB_BUILD_ARCH_ENDIAN=little

DEB_BUILD_ARCH_OS=linux

DEB_BUILD_GNU_CPU=x86_64

DEB_BUILD_GNU_SYSTEM=linux-gnu

DEB_BUILD_GNU_TYPE=x86_64-linux-gnu

DEB_BUILD_MULTIARCH=x86_64-linux-gnu

DEB_HOST_ARCH=armhf

DEB_HOST_ARCH_BITS=32

DEB_HOST_ARCH_CPU=arm

DEB_HOST_ARCH_ENDIAN=little

DEB_HOST_ARCH_OS=linux

DEB_HOST_GNU_CPU=arm

DEB_HOST_GNU_SYSTEM=linux-gnueabihf

DEB_HOST_GNU_TYPE=arm-linux-gnueabihf

DEB_HOST_MULTIARCH=arm-linux-gnueabihf

Pretty sure I installed all the packages on the left.  I've attached my list of packages in the event it is helpful.  Any ideas?

Thanks!

[Nicolas Dechesne]

On Thu, Oct 3, 2013 at 1:08 PM, Bob Smiley <xen...@gmail.com> wrote:
>
> Pretty sure I installed all the packages on the left. I've attached my list
> of packages in the event it is helpful. Any ideas?

the only thing I can think of is that you are running 13.04 (i believe
, from your package list). since you are building a 'precise' package,
you might need to do it on 12.04... i don't remember if i had tried
that, tbh. maybe you can have a quick try in a precise chroot...

[Xavier Boudet]

Hi,

Are you using instructions from http://omappedia.org/wiki/Ubuntu_kernel_for_OMAP4 ?

"sh: 1: arm-linux-gnueabihf-: not found" is really surprising, i5t looks like is there is a spare space in your environment variable CROSS_COMPILE.

Regards,

Xavier Boudet

2013/10/3 Bob Smiley <xen...@gmail.com>

You received this message because you are subscribed to the Google Groups "pandaboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandaboard+...@googlegroups.com.

[Xavier Boudet]

Are you sure you have executed "sudo apt-get build-dep linux-image-$(uname -r)" ? 

On my side, I have indeed binutils-dev, libdw-dev, libelf-dev and libnewt-dev installed, but not libgtk2.0-dev...

Try to install at leat the 4 dev packages...

2013/10/3 Bob Smiley <xen...@gmail.com>

--

You received this message because you are subscribed to the Google Groups "pandaboard" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pandaboard+...@googlegroups.com.

[Bob Smiley]

Not sure I see the space....at least when I look at export > exports.txt.

Yes, I did follow that procedure, but still luck.  I'll try the suggestion of re-running in a 64-bit 12.04 virtual machine as I'm not 100% sure how to do that in a chroot environment.

As far as patching the kernel, here's what I did:

1. Using the omappedia instructions, I downloaded the TI kernel source.

2. Checked out the head of the 1486 branch (1486.10 I believe) and applied the changes provided on this message board from SVTronics.  I tried to apply them to the latest branch, but there appears to have been other changes in the tree which may conflict with theirs.  Here are their changes:

https://groups.google.com/forum/#!topic/pandaboard/OWvyla72e00

3. Couldn't get the debian package installed, but I was able to boot the board by manually copying in the new uImage.  The kernel/module versions don't match so naturally the modules didn't load.

It would be awesome if you could get their changes merged into the latest kernel.  I have to admit I'm pushing the limits of my kernel hacking skills.

Just to confirm, the accelerated GLES2 drivers are only available in the TI kernel tree, correct?  That's what I'm really after :)

Thanks!

[Xavier Boudet]

Hi Bob,

The changes are not defined under flags and are too intrusive to merge them quickly into the kernel.

Can you let me know why you are using the specific 1486 branch? Why don't you use the last kernel, i.e. branch ti-ubuntu-3.4-stable

Can you try the following please and send me the output:

First, backup your current work.

1- go into kernel git tree and clean it: 

$ git reset --hard HEAD; git clean -fdx

2- Ensure you have some necessary dependencies:

$ sudo apt-get install  binutils-dev libdw-dev libelf-dev libnewt-dev

$ sudo apt-get build-dep linux-image-$(uname -r)

3- checkout any reference label: ti-ubuntu-3.4-1486.10 if you really need branch 1486 or ti-ubuntu-3.4.0-1490.25 to get the last kernel.

e.g:

$ git checkout -b test-rebuild ti-ubuntu-3.4.0-1490.25

4- Build:

$ export ARCH=arm

$ export CROSS_COMPILE=arm-linux-gnueabihf-

$ fakeroot debian/rules clean 2>&1 | tee log.txt

Then send me back the log.txt file

Best regards

2013/10/4 Bob Smiley <xen...@gmail.com>

[Bob Smiley]

Hi Xavier,

I will try your instructions, but I should mention that I was able to build the kernel package once I moved to a 12.04 host (a suggestion in the other email thread).  Perhaps there is an incompatibility when trying to run that procedure on a 13.04 host?

The only reason I chose to go with 1486.10 was because the SVTronics changes were applied to that branch, thus the merge was trivial.  If I understand your comment correctly, applying their changes to the latest stable branch/main-line may not be a trivial task.  Is that correct?

Also, is there any way to get the GLES2 accelerated drivers to work in a newer kernel, perhaps in 13.04?  

Thanks!

[Xavier Boudet]

Le 5 oct. 2013 00:40, "Bob Smiley" <xen...@gmail.com> a écrit :
>
> Hi Xavier,
>
> I will try your instructions, but I should mention that I was able to build the kernel package once I moved to a 12.04 host (a suggestion in the other email thread).  Perhaps there is an incompatibility when trying to run that procedure on a 13.04 host?
>
> The only reason I chose to go with 1486.10 was because the SVTronics changes were applied to that branch, thus the merge was trivial.  If I understand your comment correctly, applying their changes to the latest stable branch/main-line may not be a trivial task.  Is that correct?
>

The problem is that the changes are not backward compatible with previous Panda. This is not a merge issue.

> Also, is there any way to get the GLES2 accelerated drivers to work in a newer kernel, perhaps in 13.04?  
>

Not with TI PPA. And not sure you can find it anywhere else.

[Bob Smiley]

ok thanks, so you can't just install pvr-omap4 and get all the drivers on stock armhf 13.04?  I'm not sure I understand what this package is dependent on from the TI PPA as I thought I saw this package for precise, quantal, raring, and saucy.

I re-ran the kernel build procedure on a 12.04 host using the stable branch, it appears to have successfully built the kernel packages.  If I can just get the SVTronics changes correctly merged, I should be up and running with a Rev B3 board.

A slight aside, have you ever seen this error when running chromium with the --use-gl=egl option:

ERROR:gles2_cmd_decoder.cc(5716) PERFORMANCE WARNING: Some textures are unrenderable.  It spits out by just navigating to www.google.com.

Thanks!

[Nicolas Dechesne]

On Sat, Oct 5, 2013 at 1:35 PM, Bob Smiley <xen...@gmail.com> wrote:
> ok thanks, so you can't just install pvr-omap4 and get all the drivers on
> stock armhf 13.04? I'm not sure I understand what this package is dependent
> on from the TI PPA as I thought I saw this package for precise, quantal,
> raring, and saucy.
>

the 'hard' dependency comes from the X11 video drivers. pvr-omap4
comes with X11 video drivers (binary blobs, not source). when loading
X11 drivers the X11 server will verify that the driver is built
against the same ABI the server is running. So a driver built for X11
server 'ABI X' must run against server ABI X. The X server ABI changed
between each Ubuntu release.

[kaid...@gmail.com]

Is anyone working on fixing this, or whats the recommended way of getting 12.04 to boot on the Rev 3b boards ?
If the changeset isnt compatible with older boards and cant be easily ifdefed, maybe a cloned and patched PPA ?

I have a large batch of rev 3b on hand that are next to useless right now ( non-LTS kernels are not an option )

Kaido

[dkar...@gmail.com]

Just for reverence and I haven't tried it yet, but SVTronics made a HowTo for the Rev B3 board (Thanks Chris Dickey for the link)

http://www.svtronics.com/support/pandaboard-es-b3-developers-guide/


Op maandag 7 oktober 2013 09:18:02 UTC+2 schreef ndec:

[Frank Chiang]

hi 

now I use ubuntu core version
but I want to install gnome on pandaboard es rev3,

I executed following step:
1.apt-get install gnome-desktop
2.startx
I get following error message
root@localhost:/tmp# startx

_XSERVTransSocketUNIXCreateListener: …SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running

Fatal server error:
Cannot establish any listening sockets – Make sure an X server isn’t already running

Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at “/var/log/Xorg.0.log” for additional information.

ddxSigGiveUp: Closing log
Invalid MIT-MAGIC-COOKIE-1 keyxinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

how do I solve this problem?

dkar...@gmail.com於 2013年10月24日星期四UTC+8下午3時08分11秒寫道：