Mattias Millbro | 25 May 16:39
Picon
Picon
Favicon

Kernel 3.1.14 usb mount issue on BeagleBone

Hi all,

I'm glad that my previous email to this list lead to a fix of the 
missing hashes in python-crypt. Unfortunately I'm experiencing a new issue.

I'm using my BeagleBone for logging serial data, using the usbserial and 
ftdi-sio kernel modules. Installing them with opkg will update the 
kernel to 3.1.14, which is fine, apart from the fact that the serial 
data is to be saved on a usb-drive. As you probably know, usb-drives is 
not mountable in 3.1.14 as they do not show up as a mountable device in 
/dev/ (as discussed here: 
https://groups.google.com/forum/?fromgroups#!topic/beagleboard/IwzUbg3JY3c 
).

Im working against a very tight deadline, so I have the following question:

- Where can I find older versions of the packages 
kernel-module-usbserial and kernel-module-ftdi-sio that has a lower 
kernel version dependency? I've spent hours in the feed browser without 
sucess.

- Do you know what is causing the usb-drive issue?

Grateful for any kind of feedback and keep up the good work!
/Mattias
Gyorgy Kovesdi | 23 May 15:46
Picon

problem with 'init'

Hi,

I have a Beagleboard C4

I tried to build systemd-gnome-image by Narcissus and on my machine too. Some other
packages are tried as well with the same result, but i would like to use this one.
Using the latest version i have problem with 'init'. I found that no init scripts are executed (at lest
for levels 3 and 5) and therefore e.g. the X is not started after boot.
Executing 'init 5' or 'init 3' does nothing. However, 'init 0' and 'init 6' are work as expected.
I have the file '/etc/inittab' , but its content is also ignored.
I can start the X by executing '/etc/init.d/gdm start'. However, its link in /etc/rc5.d/ is also ignored
by init.

How can i build working init?

Thanx in advance
Gyorgy Kovesdi
Gyorgy Kovesdi | 23 May 10:16
Picon

Problem with usbhid kernel module

Hi,

I have a Beagleboard C4, using it with USB keyboard and mouse.
Building the current version of Angstrom results a non-functional keyboard and mouse at the first boot.
After some digging, i found that the kernel module "usbhid" is not compiled in. It is built as a module (m), but
is not loaded during startup. Some weeks ago, it was compiled in (y) in the default kernel config of Beagle.

This way the only possibility to get it working is to log in using the serial port, and set up manually.
I think it is related to other Beagle boards (e.g. xM), however, other people reported that it is working. Do they
use it other way, or do i made something wrong?

Regards
Gyorgy Kovesdi
Picon

Information about angstrom version to use with openembedded

Hi all,
I hope this is the right place to ask. I've checked the FAQ and
searched on the internet but I didn't find an answer.
I've downloaded a rootfs image from narcissus for "beagleboard" based
on 2011.03 release. SDK is named "Angstrom-2012.05...". In
Openembedded/bitbake "build/conf/local.conf", which version named
"angstrom-20yy.m" I have to use? I have tried both of them but bitbake
fails to build every package.
Thanks

--

-- 
Francesco Brundu
chrbruno | 22 May 12:56
Picon
Favicon

compiling a kernel module

Hello (I'm new to angstrom),

I'm working on a kernel module on Beagleboard / Angstrom but I can't 
find a way to modify and recompile it

I followed the procedure on 
http://www.angstrom-distribution.org/building-angstrom
It generates correctly the kernel and rootfs

To keep the sources, i have removed the line INHERIT += "rm_work" from 
my conf/local.conf

The problem is that I cannot find a way to recompile this kernel module

I used :
bitbake virtual/kernel -c compile -f
... but i cannot find the module on disk, or it is not recompiled
( I work on

setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/beagleboard-angstrom-linux-gnueabi/linux-mainline-3.2.16-r120d/git/drivers/media/video/em28xx/em28xx.ko 
)

I am missing something ?
Your help would be greatly appreciated

Best Regards,

Chris
Kövesdi György | 20 May 09:53
Picon

maintenance-2011.03 compilation problem

Hi,

Unfortunately i have no success with the current version, so i tried to compile
an older one, which was successful some time ago:

git clone git://github.com/Angstrom-distribution/setup-scripts.git
git checkout -b local maintenance-2011.03
MACHINE=beagleboard ./oebb.sh config beagleboard
. ~/.oe/environment-2008
bitbake virtual/kernel
....
| gcc 
-isystem/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include
-O2 -g -Wunused -Wall -static
-L/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib
-Wl,-rpath-link,/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib
-Wl,-rpath,/home/kgy/work/Angstrom/2011.03/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib
-Wl,-O1 -o insmod.static insmod.o libmodtools.a
| /usr/lib/gcc/i586-suse-linux/4.6/../../../../i586-suse-linux/bin/ld: cannot find -lc
| collect2: ld returned 1 exit status
| make: *** [insmod.static] Error 1
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL: 'oe_runmake failed'
| FATAL: oe_runmake failed
| + exit 1
NOTE: package module-init-tools-cross-3.12-r6: task do_compile: Failed

Really, there is no libc in the directory build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/lib
What can be wrong? Is it a dependency problem?
(Continue reading)

matti kaasinen | 20 May 08:58
Picon

Recipes

Hi!
I would like to share couple of my recipes with you. Some of them have
more functionality than I have needed, so those parts are not tested.
Some are not tested at all, just tested to bitbake without complaints.
Recipes:
1) kernel module for isl 12026 rtc.
I rewrote buglabs driver so that there is none of the buglabs
architecture dependent parts.
All the functionality of original code is maintained, in fact ioctl
functionality was disabled in the original code. Now it's enabled.
Doubts:
a) Interrupt line is not connected. Therefore, I wrote the code so,
that interrupt code can be cut off by bitbake variable. Anyhow,
interrupt related code is not tested.
b) chip internal eeprom. I have not tried to read/write to isl 2026
eeprom - code is there, though.
c) Basic communication with chrony (ntp) works fine. However, if
enable hwclock tuning, chrony hangs. This may be related with that
interrupt communication that is not enabled in my set-up.

2) chrony
Version available in Ångstöm (chrony_git.bb) does not install all the
necessary, like chrony daemon and client binaries. I fixed those and
added some start-up scripts.
I also upgraded chrony to newer version.
Doubts:
a) Hwclock tuning hangs chrony - it can be related to missing
interrupt functionality in my rtc set-up (see above).
b) If-up trigger does not work quite well with dhcp. Dhcp connection
seems not to be quite 'UP' when if-up trigger is taking place. Chrony
(Continue reading)

Kövesdi György | 19 May 18:20
Picon

linux-mainline and beagleboard

Hi,

The current version compiles the linux-mainline 3.2.16 for Beagleboard. I found that it
completely unusabe: any X image do not even recognize the USB keyboard and mouse, while
older kernels do (3.0.28, 2.6.39). Starting init level 5 from console do not do anything.
However, all necessary kernel modules seem to be selected by default (AFAIK).

Any help would be appreciated
Gyorgy Kovesdi
Vidal, Edward Jr. | 19 May 15:14
Picon
Favicon

kernel beagleboard/beaglebone


all,

I am having problems with bitbake virtual/kernel when configured for beagleboard but
MACHIME=beaglebone bitbake virtual/kernel works okay.
Checking meta-ti/conf/machine/beagleboard.conf &  meta-ti/conf/machine/beaglebone.conf I see the following:
PREFERRED_PROVIDER_virtual/kernel = "linux-mainline" for the beagleboard
PREFERRED_PROVIDER_virtual/kernel = "linux-ti33x-psp" for the beaglebone

Is it possible to use "linux-ti33x-psp" for the beagleboard?
Thanks
Jérôme OLIVIER | 19 May 06:05
Picon
Favicon

applying patch Angstrom and OE


Hello everyone,

I'm trying to get the SPI working on ; BeagleBoard-xM rev.C by rebuilding the Kernel with OE.

Let's see the steps I'm following : http://www.facebook.com/note.php?note_id=10150130372674362

I'm stuck at theses steps : 
                 * Patch the Linux Kernel 2.6.32 BeagleBoard board specific 
arch/arm/mach-omap2/board-omap3beagle.c so that the SPI pins get 
configured correctly and the SPIDEV driver is made aware of the SPI 
devices on the board.
                  *Once the kernel was patched I used the Angstrom distribution OpenEmbedded build environment to re-build
the kernel.

For now I have followed this page : http://www.angstrom-distribution.org/building-angstrom
but before building : MACHINE=beagleboard ./oebb.sh bitbake virtual/kernel, I'd like to apply this
patch :
http://elinux.org/BeagleBoard/SPI/Patch-2.6.37

I have been searching a lot on the internet and each source give different way but never just following : http://www.angstrom-distribution.org/building-angstrom

http://elinux.org/BeagleBoardLinuxKernel#OE says that I should change recipes or changes fils arm/arch/...
or other sources build out of the OE tree.
The problem is that I cannot find in the setup-script folder any of these file and I don't understand how to
apply this patch in OE.

I hope I was enough clear
Waiting for some help,
Jerome
(Continue reading)

Kevin | 19 May 02:21
Picon

reproduce Narcissus build locally using setup-scripts for Beagleboard xM

From Narcissus webpage (http://www.angstrom-distribution.org/builder/):

1. I selected BeagleBoard for my BeagleBoard-xM;
2. I selected simple; and console only.
3. In the “Platform Specific Packages” check “Texas Instruments OMAP3x/AM3x
family:-->Bootloader Files (x-load/u-boot/scripts)”.
4. Click the “build me!” button on the bottom of the page and wait for the
“builder” to generate the “*.tar.gz” file.  Download the “*.tar.gz” file
into my local working directory.
5. deploy the MLO/uImage/u-boot.bin/uEnv.txt and rootfs.tar.gz to uSD card

I am glad that this prebuilt image boots up my BBxM board. Now I am
wondering how to reproduce above steps and build such a .tar.gz file
locally.

I guess the start point could be your setup-scripts.

What I did is:

   - MACHINE=beagleboard ./oebb.sh config beagleboard
   - MACHINE=beagleboard ./oebb.sh update
   - MACHINE=beagleboard ./oebb.sh bitbake virtual/bootloader
   - MACHINE=beagleboard ./oebb.sh bitbake console-image

My question are:

After doing above steps, where are the MLO/uImage/u-boot.bin/uEnv.txt and
rootfs.tar.gz I can use to put into uSD card? Are those 4 steps enough to
generate all files? Can anybody give me some guidance?

(Continue reading)


Gmane