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
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
expected speed. However that's as far as things get.
On eth0, running tcpdump shows me all my outgoing packets (DHCP/ARP) and
RIP packets from the router it's attached to, but nothing else. No DHCP
the router. Putting on a static IP doesn't help either.
On eth1, things are slightly worse. All the same problems as eth0, but
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
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)
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: _/: 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: 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
[ 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?
arm mailing list