And some more progress.
The network functions fine if and only if I use the network in U-boot,
i.e. a
simple "dhcp ; setenv ethact egiga1 ; dhcp" before booting from the sd
makes everything work, at least temporarily. Bringing the interface up and
down a few times appear to break things again, but as long as I just let it
stay up it functions without any apparent issues.
So I guess this means there might be some initialization missing in the
kernel
driver for the 370 NICs ?
On a bright note, that means I now have both interfaces working on my F18
box as well; the reason eth0 didn't work there but eth1 did, was because
eth1
is used there to network load the kernel/initrd.
I did still have to add a file /etc/udev/rules.d/40-network.rules with
contents
like this:
KERNELS=="d0070000.ethernet", RUN += "/sbin/ip link set dev eth0 address
F0:AD:4E:01:E1:D2"
KERNELS=="d0074000.ethernet", RUN += "/sbin/ip link set dev eth1 address
F0:AD:4E:01:E1:D3"
to make NetworkManager happy (replace those MACs with the ones on the
mirabox label if you're
doing this), since otherwise I still ended up with a new random MAC on
every boot.
I also re-learned that you do indeed have to copy your preferred kernel
to uImage; you can't
symlink it. Otherwise a kernel update through yum will happily overwrite
your kernel. That also
taught me that the updated F19 kernel (3.9.9-302) does not boot on the
mirabox; it's worse
than the 3.9.5-301 in the xz; no kernel output whatsoever.
One last note is on the microSD performance, which appears to be very
slow from u-boot. Loading
the 10MB initrd takes over 45 seconds, as compared to maybe 2 or 3 when
loading from the
network. Under linux, a copy of the same file also takes just a few seconds.
J.
On 7/20/2013 2:49, Jochen De Smet wrote:
Some progress.
Still can't get it to work with the fedora kernel, but I did manage to
get it booted
using the same kernel I use for F18 ; had to explicitly tell dracut to
include the usb
driver to be able to find the root partition.
Also had to enable the serial getty. Is there any particular reason
why this isn't
enabled by default on arm ?
So now I'm booted, but network-wise things are looking rather grim. I
can see both
interfaces, NetworkManager recognizes them, and ethtool confirms link
at the
expected speed. However that's as far as things get.
On eth0, running tcpdump shows me all my outgoing packets (DHCP/ARP)
and even
RIP packets from the router it's attached to, but nothing else. No
DHCP reply from
the router. Putting on a static IP doesn't help either.
On eth1, things are slightly worse. All the same problems as eth0, but
in addition
I'm seeing these when running tcpdump:
mvneta d0074000.ethernet eth1: bad rx status 0cc10000 (crc error),
size=129
mvneta d0074000.ethernet eth1: bad rx status 0cc10000 (crc error),
size=125
mvneta d0074000.ethernet eth1: bad rx status 0cc10000 (crc error),
size=151
mvneta d0074000.ethernet eth1: bad rx status 0cc10000 (crc error),
size=157
mvneta d0074000.ethernet eth1: bad rx status 0cc10000 (crc error),
size=158
J.
On 7/19/2013 16:23, Jochen De Smet wrote:
On 7/19/2013 16:03, Jon wrote:
Here are my notes on MiraBox.
(These are adapted from Jon Masters)
Thanks!
Indeed, the SD reader is behind a usb bus so usb needs to be started
in u-boot to get to the card.
Using those instructions the kernel at least starts booting, makes it
to the initrd but then appears to hang at this point:
[ OK ] Mounted Configuration File System.
Starting LVM2 metadata daemon...
[ OK ] Started Apply Kernel Variables.
[ OK ] Started Create static device nodes in /dev.
Starting udev Kernel Device Manager...
[ OK ] Started LVM2 metadata daemon.
systemd-fsck[239]: _/: clean, 44920/397488 files, 338291/1586914 blocks
[ OK ] Started File System Check on Root Device.
Starting Remount Root and Kernel File Systems...
[ OK ] Started udev Kernel Device Manager.
[ 214.643245] systemd-udevd[250]: starting version 204
[ 214.662018] EXT4-fs (sdb3): re-mounted. Opts: (null)
[ OK ] Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Reached target Local File Systems (Pre).
Starting Configure read-only root support...
[ OK ] Started Monitoring of LVM2 mirrors, snapshots etc.
u...ogress polling.
[ OK ] Started Configure read-only root support.
Starting Load Random Seed...
[ OK ] Started Load Random Seed.
[ OK ] Found device /dev/ttyS0.
[ 215.468098] mvneta d0070000.ethernet eth0: mac: 06:a4:a7:49:fe:24
[ 215.522508] libphy: orion_mdio_bus: probed
I'll leave it alone for a while to see if it eventually makes it
through. Should I expect some
installer to start running at some point? Or is the root partition
inside the image .xz really
just the equivalent of the old FC18 root fs images with no more
changes to it needed?
J.
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
_______________________________________________
arm mailing list
arm@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/arm
