robertcnelson/linux-dev

This is just a set of scripts to rebuild a known working kernel for ARM devices.

Script Bugs: "[email protected]"

Note, for older git tag's please use: https://github.com/RobertCNelson/yakbuild

Dependencies: GCC ARM Cross ToolChain

Linaro: http://www.linaro.org/downloads/

Dependencies: Linux Kernel Source

This git repo contains just scripts/patches to build a specific kernel for some ARM devices. The kernel source will be downloaded when you run any of the build scripts.

By default this script will clone the linux-stable tree: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git to: ${DIR}/ignore/linux-src:

If you've already cloned torvalds tree and would like to save some hard drive space, just modify the LINUX_GIT variable in system.sh to point to your current git clone directory.

Build Kernel Image:

./build_kernel.sh

Optional: Build Debian Package:

./build_deb.sh

Development/Hacking:

first run (to setup baseline tree): ./build_kernel.sh then modify files under KERNEL directory then run (to rebuild with your changes): ./tools/rebuild.sh

linux-dev's Issues

./tools/install_kernel.sh --not working

I see...
fdisk -l:
Disk /dev/mmcblk0: 7948 MB, 7948206080 bytes
Disk /dev/mmcblk1: 1920 MB, 1920991232 bytes
Disk /dev/mmcblk1boot1: 1 MB, 1048576 bytes
Disk /dev/mmcblk1boot0: 1 MB, 1048576 bytes
Disk /dev/sda: 1948 MB, 1948254208 bytes

lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 1.8G 0 disk
└─sda1 8:1 1 1.8G 0 part
mmcblk1boot0 179:16 0 1M 1 disk
mmcblk1boot1 179:24 0 1M 1 disk
mmcblk0 179:0 0 7.4G 0 disk
├─mmcblk0p1 179:1 0 96M 0 part /boot/uboot
└─mmcblk0p2 179:2 0 7.3G 0 part /
mmcblk1 179:8 0 1.8G 0 disk
├─mmcblk1p1 179:9 0 70.6M 0 part
└─mmcblk1p2 179:10 0 1.7G 0 part

Are you 100% sure, on selecting /dev/sda? y

Debug: Existing Partition on drive:

Disk /dev/sda: 1948 MB, 1948254208 bytes
48 heads, 47 sectors/track, 1686 cylinders, total 3805184 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sda1 141 3805183 1902521+ b W95 FAT32

Unmounting Partitions

Starting Partition Search

Trying: [/dev/sda1]
Partition: [/dev/sda1] trying: [vfat], [ext4]
Partition: [vfat]
/home/debian/linux-dev-am33x-v3.13

This script has finished...
For verification, always test this media with your end device...

debian@arm:~/linux-dev-am33x-v3.13$

---

but there is not anything on mmc..

No bandgap sensor for am335x-3.12

As of 3.12.6-bone11 release, the on chip temperature sensor is not working, unlike am335x-3.8 brach.
I did not find anything like those mentioned in patches like https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline-3.8/resources/0021-hwmon-add-driver-for-the-AM335x-bandgap-temperature-.patch Is there a problem implementing at the moment?

am33x-v3.8 Issues

Hi,
This is using the following built image 3.8.0-rc5-bone1 using the build_kernel.sh script

pwm interface doesn't show up in /dev/ or /sys/class/pwm

dmesg shows

[ 0.461436] platform 48300200.ehrpwm: alias tbclk already exists
[ 0.461640] ehrpwm 48300200.ehrpwm: unable to select pin group
[ 0.462654] platform 48302200.ehrpwm: alias tbclk already exists
[ 0.462843] ehrpwm 48302200.ehrpwm: unable to select pin group
[ 0.463655] platform 48304200.ehrpwm: alias tbclk already exists
[ 0.463841] ehrpwm 48304200.ehrpwm: unable to select pin group

Full dmesg is here http://pastebin.com/r84aJmLs

A quick grep of the .config shows that the pwm code should be building into the kernel

CONFIG_PWM_TIEHRPWM=y
CONFIG_PWM_TIPWMSS=y

Edit:
Also the ain interfaces aren't showing up in /sys/devices/platform

Thanks,
Greg

3.8.13-bone41 on BeagleBone Black does not boot after installing generated .debs

I built the 3.8.13-bone41 kernel on my laptop (Ubuntu 13.10) with the build_kernel.sh script (turning on a few config options related to enable some packet scheduler features), and then built Debian packages of it with the build_deb.sh script. I then fired up my BeagleBone Black with a fresh install of ubuntu-13.10-console-armhf-2014-02-16 from the demo image provided on the wiki (which shipped with the 3.8.13-bone40 kernel), SCP'd all the generated .deb files over, and dpkg -i'd them. Upon reboting the board, it did not come up on the network, so I'm presuming it didn't boot (as I don't have the hardware to check any other way).

1. Should this have worked? Or are the .deb packages for that kernel not supposed to install and boot on that system? Do I need to do something like replace the boot image manually, or configure uboot to choose among installed kernel versions, or uninstal the existing kernel first? Is the bone41 version not going to install cleanly over the bone40 version?
2. Is there a way to install a custom kernel with the setup_sdcard.sh script? I looked through it and it looks like the kernel build script does not generate an initrd.img, which the install script needs, and does build headers, firmware, and modules files, which the install script does not appear to call for.
3. How can I get a system installed with setup_sdcard.sh to run a custom-compiled kernel? Is install_kernel.sh with the SD card in the build host the only way? Is that tested to work on top of the demo images?

Scripts do not detect build dependencies well on multiarch/ARM systems

Self hosted build on Beagleboard xM for Beaglebone on Ubuntu 12.04 armhf does not pick up installed libraries.
Libraries are under multiarch path which is based on new/strange armhf names.
Patch to follow (where did the pull request button go!)

usb traces (3.8.13-bone43 and 3.13)

I got a few of those traces while using an usb-wifi-adapter + usb hub.. these are from 3.8 but issue persists with 3.13.

http://pastebin.com/kKniMB4p

Kernel 3.2 for BeagleBone Black needed. Can it be used?

I'm experiencing the same issue mentioned by this fellow here: https://groups.google.com/forum/#!searchin/beaglebone/3.8$203.2$20kernel/beaglebone/Bl4UbhIXNfY/1SBLKeovzxEJ

Meaning that trying to capture video through USB will fail unless very low-speed (transfer) methods are used.

The person says it used to work with kernel 3.2, and the CircuitCo person confirms.

I would change my current 3.8 for 3.2 kernel right away if it could solve the issue, but I can't find an image for BB-Black with 3.2.

Also, I could custom-compile my 3.2 kernel, but the instructions on elinux.org say to use 3.8 for BB-Black.

So I'm asking you since you would know better: should I even try to compile a 3.2 kernel for my BB-Black? Could it work?

Any hints and help are appreciated as 3.8 has serious issues with BB-Black when it comes to USB video capture (which is what many hobbyists are doing).

dev-mmcblkxxx takes too long to mount

Hello,

I hope this is the right place to post this issue. I´ve been fighting to reduce the boot time on several Debian images and I´ve been hiting two big obstacles in the process. "Networking.service" is the biggest time consumer during boot up, followed by "dev-mmcblk1p1.device", this last one is the mounting process of the SD card? How can I reduce this times? This happens with the internal emmc as well and with most 4.4.xx kernels.

root@beaglebone:/etc/modules-load.d# cat /etc/dogtag
BeagleBoard.org Debian Image 2017-09-01
root@beaglebone:/etc/modules-load.d# uname -r
4.4.84-ti-r120
root@beaglebone:/etc/modules-load.d# systemd-analyze blame
1min 33.080s networking.service
57.921s dev-mmcblk1p1.device
7.059s generic-board-startup.service
3.054s loadcpufreq.service
2.544s systemd-logind.service
2.229s systemd-udev-trigger.service
1.882s udhcpd.service
1.869s bb-wl18xx-wlan0.service
1.647s rsyslog.service
1.563s pppd-dns.service
1.150s systemd-user-sessions.service
1.129s systemd-journald.service
1.075s rc-local.service
1.012s hostapd.service
998ms dnsmasq.service
565ms cpufrequtils.service
549ms systemd-tmpfiles-setup-dev.service
484ms capemgr.service
421ms systemd-modules-load.service
368ms sys-kernel-debug.mount
358ms dev-mqueue.mount
347ms systemd-udevd.service
342ms systemd-remount-fs.service
311ms kmod-static-nodes.service
287ms sys-fs-fuse-connections.mount
276ms systemd-timesyncd.service
261ms sys-kernel-config.mount
235ms mnt-ramdisk.mount
220ms systemd-update-utmp.service
206ms systemd-journal-flush.service
198ms var-log.mount
189ms bb-wl18xx-bluetooth.service
187ms systemd-tmpfiles-setup.service
179ms systemd-random-seed.service
173ms systemd-update-utmp-runlevel.service
94ms systemd-sysctl.service
root@beaglebone:/etc/modules-load.d#

USB Host

I checked out a kernel a while ago and recently got around to testing the USB and couldn't get anything to even make a peep in dmesg or on console when inserting and removing devices.

Has this been fixed in a recent build?

Add support for kali-rolling

The problem when building on kali rolling :

+ Detected build host [Kali GNU/Linux Rolling]
+ host: [x86_64]
+ git HEAD commit: [9b9c936a2950210e70d9d1cd37e60088c0dff314]
Dependency check skipped, you are on your own.
-----------------------------
Unrecognized deb based system:
-----------------------------
Please cut, paste and email to: [email protected]
-----------------------------
git: [9b9c936a2950210e70d9d1cd37e60088c0dff314]
git: [url=https://github.com/RobertCNelson/linux-dev]
uname -m: [x86_64]
lsb_release -a:
No LSB modules are available.
Distributor ID: Kali
Description:    Kali GNU/Linux Rolling
Release:        kali-rolling
Codename:       kali-rolling
-----------------------------
* Failed dependency check

root@lead:~# cat /etc/issue
Kali GNU/Linux Rolling \n \l
root@lead:~# uname -a
Linux lead 4.0.0-kali1-amd64 #1 SMP Debian 4.0.4-1+kali2 (2015-06-03) x86_64 GNU/Linux

Adding

if [ "x${deb_distro}" = "kali-rolling" ] ; then
            #lsb_release -a
            #Distributor ID: Kali
            #Description:    Kali GNU/Linux Rolling
            #Release:        kali-rolling
            #Codename:       kali-rolling

            deb_distro="sid"
        fi

To tools/host_det.sh should fix this. I do not know if kali-rolling is sid or still jessie, from what i understand it is sid

beagleboard: nand/omap2 module is not created if onenand/omap2 is

Hello,
Using kernels from the rcn-ee Debian Jessie repository: 4.1.5-armv7-x2 or 4.2.0-rc6-armv7-x0, my beagleboard does not see its nand (mtd).
Those kernels have the onenand/omap2.ko driver but not the nand/omap2.ko.

Compiling a kernel without onenand (CONFIG_MTD_ONENAND not set) builds nand/omap2.ko, and the nand shows up on the system when loading the module.

Looks like having the same name for both modules causes the issue?

how to flash emmc of bbb

hi,,
I follow http://eewiki.net/display/linuxonarm/BeagleBone+Black
and it works..
Now my compiled kernel boot from external memory card.
now i want to flash this to emmc(internal) of beaglebone black..
kindly reply ..

am33x-v3.8 Issues

I am using https://rcn-ee.net/deb/microsd/wheezy/BBB-debian-7.3-2013-12-17-4gb.img.xz

and i have error when loading kernel module..

[ 142.264209] BUG: spinlock bad magic on CPU#0, lircd/988
[ 142.269761] lock: hardware+0x18/0xfffffddc [lirc_serial], .magic: 00000000, .owner: /-1, .owner_cpu: 0

Beaglebone Black with Xenial : double USB eth bridge

Hi Robert,

First, big props for making the Ubuntu images for the Beaglebone - I use them as a base to build the Umikaze2 images for Replicape-powered 3D printers.

I'm trying to build an image of Umikaze which will work equally on the regular ethernet variant of the BBB, and on the newer wireless board. With the default kernel shipping it works fine (4.4.59-ti-r96). However since the 16.04.2 release, I've noticed that there are now two USB-ethernet interfaces showing up!
usb0 on 192.168.7.2 as expected
usb1 on 192.168.6.2 where I suspect hostapd being at fault.

For Umikaze we prefer using network-manager through the command line (nmtui) instead of connman so the script changes that part of the setup but usb1 is still present after reboot.

I've looked quite a bit in the /etc/interfaces* files but could find no reference to 192.168.6.2... How do I disable it?

I get the same issue with the wireless board, so it's consistent at least.

LCD Touchscreen Jitter fix still not working

G'day to all.

BBB hardware: Revision A5C
Software: Debian 7.3 wheezy kernel 3.8.13-bone40.1 ( With 3.8 patch set )

LCD Testing:

7" inch resistive touchscreen LCD 4DCAPE-70T from 4D systems on the Beaglebone Black.

I used the TSLIB calibration tools as well as running LXDE. Cursor still jumps to bottom left of the screen.

With the same hardware set up, I installed the Android 4.2.2 (k3.8.13) image from
http://www.elinux.org/Beagleboard:Android port page.

LCD and touch works perfectly fine.

Are we sure this is a driver level issue or is Android using some other touchscreen driver or subsystem?

Best regards.

Vaughn

ttyO1 not working

I try to upgrade to the 3.12 kernel to escape the 3.8 mmc bug, but now on 3.12 I cant make any uart work :S. got any idea what the problem?

Unrecognized deb based system: am33x-v3.13 branch

I have had this working before, but not on this branch (am33x-v3.13). When running ./build_kernel.sh I get this output:

+ Detected build host [Linux Mint 17 Qiana]
+ host: [x86_64]
+ git HEAD commit: [03ed3adc765644274981c461d25d1e576adceeff]
Dependency check skipped, you are on your own.
-----------------------------
Unrecognized deb based system:
-----------------------------
Please cut, paste and email to: [email protected]
-----------------------------
git: 03ed3adc765644274981c461d25d1e576adceeff
uname -m
x86_64
lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:    Linux Mint 17 Qiana
Release:    17
Codename:   qiana
-----------------------------
* Failed dependency check

That was after I did a fresh clone.

I'll check through the script and see if I can figure it out...

looking for linux-headers-4.4.30-ti-r64_1jessie_armhf.deb

Hi RobertCNelson,

I tried to install 3rd-part software package on debian 8.6 with beaglebone black. However, it is missing /lib/module/4.4.30-ti-r64/build directory, therefore, I am looking for linux-headers-4.4.30-ti-r64_1jessie_armhf.deb

according to https://groups.google.com/forum/#!topic/beagleboard/82th72jb5F8, the file was stored @ http://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/linux-headers-4.4.30-ti-r64_1jessie_armhf.deb

but it is no longer exist any more.

Please kindly advise where I can locate linux-headers-4.4.30-ti-r64_1jessie_armhf.deb

thanks in advance,

Michael

Customisation

Hello,

What is the best way to apply some customisation to the source?

I want to apply some data similar to http://mythopoeic.org/pi-ntp/ to enable GPIO 31 as a PPS source and think that the build scripts here are overwriting my changes. Is there a way of me making changes that will then be compiled in?

beaglebone usb audio noise

iMic is used for beaglebone audio

I installed ubuntu 11.10 r5 on the beaglebone, further installed alsa-utils and run alsamixer to adjust the volume.

line in and line out is connected to iMic.

Here is the problem: if I run the command

arecord | aplay

I can hear the noise (sometimes when system is a little bit busy, say if another ssh remote connected to beaglebone and run top command, anytime the statistics is updated, a noise is shown up).

This problem doesn't happen on beagleboard.

After check with top command. I found the difference is: in beaglebone, if I run aplay a.wav or arecord | alay, a busy kworker is shown up, this kworker consumes more than 90% CPU. In beagleboard, no busy kworker is shown up when aplay is running.

Beaglebone black capes does not work

[ 2.504767] bone-capemgr bone_capemgr.6: slot #3: Requesting firmware 'BB-BONE-LCD4-01-00A1.dtbo' for board-name '4D 4.3 LCD CAPE- 4DCAPE-43T ', version '00A1'
[ 2.567178] bone-capemgr bone_capemgr.6: slot #3: dtbo 'BB-BONE-LCD4-01-00A1.dtbo' loaded; converting to live tree
[ 2.578638] of_resolve: Could not find symbol 'ocp'
[ 2.583835] bone-capemgr bone_capemgr.6: slot #3: Failed to resolve tree
[ 2.590931] bone-capemgr bone_capemgr.6: loader: failed to load slot-3 BB-BONE-LCD4-01:00A1 (prio 0)
[ 2.600620] bone-capemgr bone_capemgr.6: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 2.609461] bone-capemgr bone_capemgr.6: loader: check slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 2.618206] bone-capemgr bone_capemgr.6: loader: check slot-4 BB-BONE-
[ 2.636603] bone-capemgr bone_capemgr.6: loader: after slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 2.645395] bone-capemgr bone_capemgr.6: loader: after slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[ 2.689363] bone-capemgr bone_capemgr.6: slot #5: Requesting firmware 'BB-BONELT-HDMI-00A0.dtbo' for board-name 'Bone-Black-HDMI', version '00A0'
[ 2.735359] bone-capemgr bone_capemgr.6: failed to load firmware 'BB-BONELT-HDMI-00A0.dtbo'
[ 2.744219] bone-capemgr bone_capemgr.6: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)
[ 2.753829] bone-capemgr bone_capemgr.6: slot #4: Requesting part number/version based 'BB-BONE-EMMC-2G-00A0.dtbo
[ 2.764761] bone-capemgr bone_capemgr.6: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 2.775075] hub 2-0:1.0: USB hub found
[ 2.779138] bone-capemgr bone_capemgr.6: slot #4: Requesting firmware 'BB-BONE-EMMC-2G-00A0.dtbo' for board-name 'Bone-LT-eMMC-2G', version '00A0'
[ 2.793093] hub 2-0:1.0: 1 port detected
[ 2.805459] bone-capemgr bone_capemgr.6: failed to load firmware 'BB-BONE-EMMC-2G-00A0.dtbo'
[ 2.814443] bone-capemgr bone_capemgr.6: loader: failed to load slot-4 BB-BONE-EMMC-2G:00A0 (prio 1)
[ 2.824461] bone-capemgr bone_capemgr.6: loader: check slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 2.842319] bone-capemgr bone_capemgr.6: loader: after slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 2.861396] bone-capemgr bone_capemgr.6: slot #6: Requesting part number/version based 'BB-BONELT-HDMIN-00A0.dtbo
[ 2.880810] bone-capemgr bone_capemgr.6: slot #6: Requesting firmware 'BB-BONELT-HDMIN-00A0.dtbo' for board-name 'Bone-Black-HDMIN', version '00A0'

[ 2.910602] bone-capemgr bone_capemgr.6: failed to load firmware 'BB-BONELT-HDMIN-00A0.dtbo'
[ 2.919551] bone-capemgr bone_capemgr.6: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 2.930121] of_get_named_gpio_flags exited with status 6
[ 2.930145] of_get_named_gpio_flags: can't parse gpios property of node '/ocp/mmc@48060000[0]'
[ 2.930167] of_get_named_gpio_flags: can't parse gpios property of node '/ocp/mmc@48060000[0]'
[ 2.935642] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[ 2.942898] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[ 2.981465] of_get_named_gpio_flags: can't parse gpios property of node '/ocp/mmc@481d8000[0]'
[ 2.981491] of_get_named_gpio_flags: can't parse gpios property of node '/ocp/mmc@481d8000[0]'
[ 2.981513] of_get_named_gpio_flags: can't parse gpios property of node '/ocp/mmc@481d8000[0]'

beaglebone: USB-to-Ethernet interface not working

Ubuntu on Beaglebone: how to have USB-to-Ethernet interface working?

I am using Beaglebone booted with Ubuntu following the direction from:

http://elinux.org/BeagleBoardUbuntu#Demo_Image

I also use Ubuntu on my host PC connected to the Beaglebone by a USB
cable only (no LAN cable).
In this configuration USB-to-serial works and I have the very useful
Beaglebone console.
If I boot with Angstrom USB-to-Ethernet works. That is done via an
eth2 interface that appears on my PC and I give it the address
192.168.7.1 (the Beaglebone answer from 192.168.7.2). The USB-to-
Ethernet functionality starts disconnecting the Beaglebone-Angstom USB
mass storage (as I red from the related Beaglebone README.htm). But
when the Beaglebone boots with Ubuntu I have no USB mass storage to
disconnect and no eth2, or similar, interface appears.
So please give me some advice in order to solve my problem.

Thanks

Rino

dmesg+ifconfig on beaglebone:
[ 1.927672] Linux media interface: v0.10
[ 1.932041] lirc_dev: IR Remote Control driver registered, major 250
[ 1.938818] Driver for 1-wire Dallas network protocol.
[ 1.945216] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[ 1.952682] device-mapper: uevent: version 1.0.3
[ 1.958336] device-mapper: ioctl: 4.21.0-ioctl (2011-07-06) initialised: [email protected]
[ 1.967778] device-mapper: multipath: version 1.3.0 loaded
[ 1.973623] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 1.983699] usbcore: registered new interface driver snd-usb-6fire
[ 1.991067] ALSA device list:
[ 1.994193] No soundcards found.
[ 1.997768] oprofile: hardware counters not available
[ 2.003176] oprofile: using timer interrupt.
[ 2.009686] TCP cubic registered
[ 2.014510] NET: Registered protocol family 10
[ 2.024324] NET: Registered protocol family 17
[ 2.029370] Registering the dns_resolver key type
[ 2.034380] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[ 2.042513] ThumbEE CPU extension supported.
[ 2.047037] Registering SWP/SWPB emulation handler
[ 2.053539] omap2_set_init_voltage: unable to get clk dpll1_ck
[ 2.059740] omap2_set_init_voltage: unable to set vdd_mpu_iva
[ 2.065797] omap2_set_init_voltage: unable to get clk l3_ick
[ 2.071779] omap2_set_init_voltage: unable to set vdd_core
[ 2.085394] registered taskstats version 1
[ 2.090218] Detected MACID=d4:94:a1:37:bb:52
[ 2.098657] omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[ 2.108628] Freeing init memory: 324K
[ 2.177925] mmc0: host does not support reading read-only switch. assuming write-enable.
[ 2.193314] mmc0: new SD card at address ffee
[ 2.204998] mmcblk0: mmc0:ffee SU02G 1.89 GiB
[ 2.218768] mmcblk0: p1 p2
[ 2.323506] udevd[69]: starting version 173
[ 3.428783] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 4.146497] init: ureadahead main process (166) terminated with status 5
[ 4.928837] udevd[207]: starting version 173
[ 5.312243] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 6.981551]
[ 6.981561] CPSW phy found : id is : 0x7c0f1
[ 6.988371] PHY 0:01 not found
[ 6.994387] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 9.300668] init: udev-fallback-graphics main process (374) terminated with status 1
ubuntu@omap:~$ ifconfig
eth0 Link encap:Ethernet HWaddr d4:94:a1:37:bb:52
UP BROADCAST ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:40

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

---

dmesg+ifconfig on Ubuntu host PC
844.157992] scsi7 : usb-storage 1-6.2:1.0
[ 845.157681] scsi 7:0:0:0: Direct-Access Linux File-CD Gadget 0316 PQ: 0 ANSI: 2
[ 845.196843] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 845.201288] sd 7:0:0:0: [sdb] 144522 512-byte logical blocks: (73.9 MB/70.5 MiB)
[ 845.202538] sd 7:0:0:0: [sdb] Write Protect is off
[ 845.202544] sd 7:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 845.203818] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 845.209747] sdb:
[ 845.213531] sd 7:0:0:0: [sdb] Attached SCSI removable disk
[ 925.514650] usb 1-6.2: USB disconnect, device number 6
[ 925.539737] sd 7:0:0:0: [sdb] Synchronizing SCSI cache
[ 925.540810] sd 7:0:0:0: [sdb] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[ 938.824550] usb 1-6: USB disconnect, device number 3
[ 938.824556] usb 1-6.1: USB disconnect, device number 4
[ 938.824781] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[ 938.824804] ftdi_sio 1-6.1:1.0: device disconnected
[ 938.827028] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1
[ 938.827047] ftdi_sio 1-6.1:1.1: device disconnected
[ 1000.256044] usb 1-6: new high speed USB device number 7 using ehci_hcd
[ 1000.389560] hub 1-6:1.0: USB hub found
[ 1000.390363] hub 1-6:1.0: 2 ports detected
[ 1000.664656] usb 1-6.1: new high speed USB device number 8 using ehci_hcd
[ 1000.776987] ftdi_sio 1-6.1:1.0: FTDI USB Serial Device converter detected
[ 1000.777018] usb 1-6.1: Detected FT2232H
[ 1000.777020] usb 1-6.1: Number of endpoints 2
[ 1000.777021] usb 1-6.1: Endpoint 1 MaxPacketSize 512
[ 1000.777023] usb 1-6.1: Endpoint 2 MaxPacketSize 512
[ 1000.777025] usb 1-6.1: Setting MaxPacketSize 512
[ 1000.777345] usb 1-6.1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 1000.778736] ftdi_sio 1-6.1:1.1: FTDI USB Serial Device converter detected
[ 1000.778766] usb 1-6.1: Detected FT2232H
[ 1000.778767] usb 1-6.1: Number of endpoints 2
[ 1000.778769] usb 1-6.1: Endpoint 1 MaxPacketSize 512
[ 1000.778771] usb 1-6.1: Endpoint 2 MaxPacketSize 512
[ 1000.778772] usb 1-6.1: Setting MaxPacketSize 512
[ 1000.779073] usb 1-6.1: FTDI USB Serial Device converter now attached to ttyUSB1
[ 1008.776653] usb 1-6.2: new high speed USB device number 9 using ehci_hcd
[ 1008.886651] usb 1-6.2: unable to read config index 0 descriptor/start: -32
[ 1008.886655] usb 1-6.2: chopping to 0 config(s)
[ 1008.886787] usb 1-6.2: no configuration chosen from 0 choices
rino@MCP7A:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:2e:27:de:94
indirizzo inet:192.168.178.66 Bcast:192.168.178.255 Maschera:255.255.255.0
indirizzo inet6: fe80::201:2eff:fe27:de94/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:83265 errors:0 dropped:0 overruns:0 frame:0
TX packets:47508 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:1000
Byte RX:122674569 (122.6 MB) Byte TX:4058402 (4.0 MB)
Interrupt:22 Indirizzo base:0x2000

lo Link encap:Loopback locale
indirizzo inet:127.0.0.1 Maschera:255.0.0.0
indirizzo inet6: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:92 errors:0 dropped:0 overruns:0 frame:0
TX packets:92 errors:0 dropped:0 overruns:0 carrier:0
collisioni:0 txqueuelen:0
Byte RX:9370 (9.3 KB) Byte TX:9370 (9.3 KB)

Does anybody who solved build fail problem?

Hi,

I have a build problem whenever I ran build_kernel.sh in the repository with am33x-v3.8-bone26-xenomai branch.
It stops with those error messages after a while.

(...)
dir: firmware
Applying: firmware: add for beaglebone
dir: xenomai - ipipe
reference: v3.8.13, kernel version: 3.8.13
awk: line 40: syntax error at or near ,
awk: line 48: syntax error at or near ,
awk: line 76: syntax error at or near ,

My OS is debian, kernel version is 3.2.0-4-amd64.

Could you please let me know how I can solve the problem if you already experienced this?

Scripts do not look for lzma package.

build_deb.sh (and friends) do not check for lzma.

Release for linux kernel 4.15, if not then need help for 32-bit linux kernel build for BBB

I wanted to know if there is any release for the linux-dev repo with linux kernel 4.15. I want to build the kernel for 32 bit arch, but when I run build_kernel.sh it downloads the 64bit kernel and tries to build on top of that.
Any help would be appriciated
Thanks

Debugging Kernel - prove locking correctness caused kernel to fail to boot

Using the linux 3.12-rc5 on the Beaglebone Black, I enabled Prove Locking Correctness in my kernel build and it caused the kernel to fail to boot (it pauses at Starting Kernel).

I haven't had time to track it down but if you can confirm or think of a reason why then it would be helpful.

Issues with am33x-v3.7

I've compiled a 3.7 kernel for my beaglebone and found the following issues:

1. On reboot the kernel causes a segmentation fault somewhere at USB shutdown.
2. There is some issue with eth0 MAC config, because I'm getting a random
   MAC instead of the fixed one set by udev rule with 3.2.
3. There is no support for AM3359 built-in RTC. I've tried to add the RTC patches from https://github.com/beagleboard/kernel/tree/3.7/patches/rtc but they cause a segfault when booting the kernel.
4. The cape discovery process on a capeless board is causing about 7 seconds delay on a capeless board booting (this delay was not visible in 3.2).
5. Only UART0 (console) is working. The others are not initialized (can't see them on /proc/iomem).

Best regards,
José Gonçalves

Kernel 3.6 compilation error with module udlfb

I'm using branch am33x-v3.6 to try to compile a kernel 3.6.0-rc6 for beaglebone.

I wanted to add the DisplayLink fb driver (udlfb.ko), but this leads to a build error.

The problem is not related to beagle or linux-dev, but only to ARM kernel sources that didn't export some symbol used in various drivers.. I had to apply the following patch to make it work.

https://patchwork.kernel.org/patch/1361471/

Definitely, this is a kernel issue, but you can add this patch in the meantime.

Hope this helps.

BTW, great work !

Support for enable_partno-parameter in 3.8

Hello,
I have Ubuntu 13.04 with 3.8.13-bone32 on a BBB - and AFAIK this kernel does not yet support the enable_partno parameter. I saw there are patches in kernel version > 3.8 - but if I try to upgrade the kernel to anything above 3.8 I cannot boot (I've tried 3.12-bone8 3.12.6-bone11).
So, 2 questions:

1. is it planned to have enable_partno parameter in 3.8.13?
2. is there any reason for which a kernel update to a different version (e.g. 3.8 -> 3.12) does not work?

Thank you!

USB related system freeze in 4.1.22-ti-r59

We're currently trying to track down a really nasty issue, seemingly related to the USB interface, on the Beaglebone Black. I'll detail the process below:

Kernel version: 4.1.22-ti-r59

• Run mjpg-streamer utility for one of our USB webcams at 720p@30fps
• Anywhere from 2 to 20 minutes later, the entire system will freeze.
• No errors or kernel messages appear on the serial console; no info to go off of to track down the real cause
• Serial console becomes entirely unresponsive
• Power cycle brings the system up again normally

On kernel 4.1.8, I was able to run the camera for several hours without any problem. This is the version that we currently have deployed in our production environment and we've never received any complaints about it.

To make sure I isolated the problem from the actual beaglebone hardware, I ran the test process (start mjpg-streamer and wait until the system crashes) on a fresh, factory flashed BBB with 4.1.8, and it did not crash after several hours. I then inserted a 4.1.22 SD card on the same device and ran the tests again. The system always froze after 2-20 minutes.

Because I had read about past problems concerning freezes as a result of how power is supplied, I have also tried using various methods for supplying power to the board (from the mini USB port, using a 5V-2A supply on the rails, and using a custom 5V supply driven by 18650 li-ion batteries). This didn't seem to have any impact on results.

Coincidentally, I noticed this patch today on the 4.9 kernel: @590da07
Any relation?

I've also read on various message boards that there could supposedly be a silicon defect with the TI AM335x that causes similar problems; any info to confirm or refute this?

Any ideas what might be causing this? I can see that the problem might exist in one of three places: musb, v4l2, or uvcvideo, but my main suspicions lie with musb. I'm currently running the test again on the same hardware using your 4.4.23-ti-r51 build and have not had any problems yet (test 40 minutes underway).

Thanks much.