Hi,
When updating the TI kernel from 4.4.14-ti-r34 to 4.4.15-ti-r35 on Debian
8.5, the kernel failed to
boot cleanly. On connecting a console, the boot process failed in initramfs
when trying to mount the
real boot partition (the eMMC). The mount command from initramfs was
complaining about
On further investigation, first failure is from udev:
/scripts/init-top/udev: line 14: can't create /sys/kernel/uevent_helper:
Permission denied
Think because of this udev is not populating /dev/disk/by-uuid/ hence
subsequent failure.
On Thursday, 14 April 2016 09:14:44 UTC+1, Steve Osselton
Hi,
Have just updated a a board from 4.1.18-ti-r56 to 4.4.6-ti-r17 using
"update_kernel.sh --lts-4_4".
This now fails to reboot. Looking at console is stuck in initramfs where it
looks there has been a failure
to find the actual file system by uuid:
ALERT!
interface
(you see the ethXX device but without an IPv4 address). Installing udhcpd
makes everything work - might
be worth adding to default image so works out of the box ?
On Monday, 19 January 2015 08:25:25 UTC, Steve Osselton wrote:
All is now clear Thanks.
On Friday, 16 January 2015 14:36:51
This issue is that the image is missing /usr/sbin/udhcpd. It
has /usr/sbin/dnsmasq which causes
g_ether to load, but doesn't work properly without /usr/sbin/udhcpd.
Cheers Steve.
On Monday, 15 June 2015 15:01:16 UTC+1, RobertCNelson wrote:
On Mon, Jun 15, 2015 at 4:14 AM, Steve Osselton
Think there is a typo in the latest bbb-eMMC-flasher-eewiki-ext4.sh (from
/opt/scripts/tool/eMMC):
--- a/tools/eMMC/bbb-eMMC-flasher-eewiki-ext4.sh
+++ b/tools/eMMC/bbb-eMMC-flasher-eewiki-ext4.sh
@@ -73,7 +73,7 @@ check_eeprom () {
eeprom=/sys/bus/i2c/devices/0-0050/eeprom
Are you running a TI kernel? I think by default these are build with USB
gadget support enabled for both CDC ECM and RNDIS.
I have found that if CDC ECM support is enabled in the kernel then
usb/ethernet does not work with the windows driver. To
fix this I rebuild the TI kernel from source (on
Hi,
I have two pretty much identical blacks that I regularly update using the
update_kernel.sh script.
Have just updated from v3.14.35-ti-r56 to v3.14.37-ti-r57. The first bone
rebooted as normal, whereas the
second now hangs (output from serial console), anyone any ideas what might
have gone
I had a problem using the latest TI kernel and the windows USB/ethernet
driver. Seemed to be some issue with the
windows driver expecting RNDIS where the kernel USB gadget support was
configured to support both CDC ECM and
RNDIS by default. Changing the USB gadget support to just support RNDIS
All is now clear Thanks.
On Friday, 16 January 2015 14:36:51 UTC, RobertCNelson wrote:
On Fri, Jan 16, 2015 at 7:23 AM, Steve Osselton
steve.o...@prismtech.com javascript: wrote:
I have been maintaining an up to data Ubuntu 14.04.1 image and TI kernel
on
an SD card
then flashing
I have been maintaining an up to data Ubuntu 14.04.1 image and TI kernel on
an SD card
then flashing to the eMMC using bbb-eMMC-flasher-eewiki-ext4.sh
Now when I do this the Bone appears not to have USB ethernet after
rebooting to eMMC,
am pretty sure this has worked previously. Booting from
Having upgraded to the latest TI kernel, I noticed a large number of timer
interrupts. From itop:
INTNAME RATE MAX
57 [ 10.ethernet] 6 Ints/s (max: 7)
58 [ 10.ethernet] 6 Ints/s (max: 6)
84 [_timer] 10203
Hi,
I used /opt/scripts/tools/update_kernel.sh --ti-kernel) to move from
a 3.8.13-bone kernel to
the latest 3.14 TI kernel. This worked fine, however when I subsequently do
update_kernel.sh
(after rebooting) it once again downloads and re-installs the same TI
kernel. Any idea what is
happening
13 matches
Mail list logo
