On Monday, May 8, 2017 at 8:01:11 PM UTC-5, RobertCNelson wrote:
>
> On Mon, May 8, 2017 at 7:17 PM, Mark Copper <[email protected]
> <javascript:>> wrote:
> >
> >> btw, one issue with this new setup, WiFi is slower with the dual
> >> connections, in my testing switching from v4.4.x -> v4.9.x saw an
> >> increase from 55kb/s -> 1,600kb/s
> >>
> >> $ cd /opt/scripts/tools/
> >> $ git pull
> >> $ sudo ./update_kernel.sh --ti-kernel --lts-4_9
> >>
> > Did I bonk my BBB by updating my kernel with this recipe 6 months later?
>
> It "shouldn't" right now as the only developers behind "--ti-kernel
> --lts-4_9" is ti.com, at this point i'm just rebasing to keep the same
> setup..
>
> >
> > The device boots up but messages of "direct firmware load for
> am335x-pru0-fw
> > failed with error -2" are written to console.
>
> This is normal, and ported from teh --lts-4_4 branch by ti.com, it's
> the pru interface. You as the end user have the abilty to load two pru
> firmwares and run what ever you want on the pru.
>
> > "ifconfig" freezes the command
> > line and can no longer ssh in via wlan0.
>
> AH this is odd.. I'll look into this tomorrow..
>
> >
> > I'll look into it more carefully later. BBB and bonehead error.
> >
> > #uname -a
> > Linux beaglebone 4.9.25-ti-r32 #1 SMP PREEMPT Fri May 5 19:10:28 UTC
> 2017
> > armv7l GNU/Linux
A little more data in case useful.
By isolating ifconfig in a separate screen window, it appears that ifconfig
process starts but does not return and is not using any CPU. Similarly for
"ip link show" and "ip a".
root@beaglebone:~# cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
usb0: 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
wlan0: 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
usb1: 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0
lo: 25280 320 0 0 0 0 0 0
25280 320 0 0 0 0 0 0
The commands "service networking stop/start" do return after timing out and
leaving systemd messages like this:
May 9 00:46:05 beaglebone systemd[1]: Starting Raise network interfaces...
May 9 00:51:05 beaglebone systemd[1]: networking.service: Start operation
timed out. Terminating.
May 9 00:51:05 beaglebone systemd[1]: Failed to start Raise network
interfaces.
May 9 00:51:05 beaglebone systemd[1]: networking.service: Unit entered
failed state.
May 9 00:51:05 beaglebone systemd[1]: networking.service: Failed with
result 'timeout'.
Finally, there is this message in syslog:
May 8 23:33:43 beaglebone systemd-udevd[566]: seq 2224
'/devices/platform/ocp/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx.1.auto/net/wlan0'
killed
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/74d6b865-67b0-45f1-bdb1-a09a5a657612%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
