Hi,
I cross-compiled the latest (3.16) linaro kernel from source using the linaro aarch64 toolchain (gcc-linaro-aarch64-linux-gnu-4.8-2014.04_linux). I am also using the linaro armv8 disk image (linaro-image-minimal-genericarmv8-20140127-635).
At first I used defconfig to compile the kernel. When I boot the system and run "ifconfig -a", I only see the loopback device:
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:784 (784.0 B) TX bytes:784 (784.0 B)
I then took the .config generated by defconfig and opened it with menuconfig. Inside menuconfig, I believe I enabled all the configuration options related to ethernet/networks. After re-compiling and booting, "ifconfig -a" shows this:
bond0 Link encap:Ethernet HWaddr CA:FB:D0:02:D0:7E BROADCAST MASTER 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
dummy0 Link encap:Ethernet HWaddr 02:58:3E:AF:F3:41 BROADCAST NOARP 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:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:784 (784.0 B) TX bytes:784 (784.0 B)
Unfortunately, I still do not see eth0. Any help would be greatly appreciated!
Thank you,
Ivan
On Thu, 2014-08-07 at 17:07 -0400, Ivan Stalev wrote:
Hi,
I cross-compiled the latest (3.16) linaro kernel from source using the linaro aarch64 toolchain (gcc-linaro-aarch64-linux-gnu-4.8-2014.04_linux). I am also using the linaro armv8 disk image (linaro-image-minimal-genericarmv8-20140127-635).
At first I used defconfig to compile the kernel.
That _may_ be part of the problem, we generally don't use the defconfig for building arm64 kernels, we use the config produced by running something like...
ARCH=arm64 scripts/kconfig/merge_config.sh \ linaro/configs/linaro-base.conf \ linaro/configs/linaro-base64.conf \ linaro/configs/distribution.conf \ linaro/configs/big-LITTLE-MP.conf \ linaro/configs/vexpress64.conf
This is assuming you're using ARM's Juno board or FVPs (a.k.a. RTSM a.k.a. Fast Models).
I am running it using the GEM5 full system simulator, so it is not actually real hardware. The simulator does support ethernet. I tried using the dummy0 device for ethernet traffic but it didn't work. Is there a particular option I can enable in order to have eth0?
Thanks,
Ivan
On Fri, Aug 8, 2014 at 4:30 AM, Jon Medhurst (Tixy) tixy@linaro.org wrote:
On Thu, 2014-08-07 at 17:07 -0400, Ivan Stalev wrote:
Hi,
I cross-compiled the latest (3.16) linaro kernel from source using the linaro aarch64 toolchain
(gcc-linaro-aarch64-linux-gnu-4.8-2014.04_linux).
I am also using the linaro armv8 disk image (linaro-image-minimal-genericarmv8-20140127-635).
At first I used defconfig to compile the kernel.
That _may_ be part of the problem, we generally don't use the defconfig for building arm64 kernels, we use the config produced by running something like...
ARCH=arm64 scripts/kconfig/merge_config.sh \ linaro/configs/linaro-base.conf \ linaro/configs/linaro-base64.conf \ linaro/configs/distribution.conf \ linaro/configs/big-LITTLE-MP.conf \ linaro/configs/vexpress64.conf
This is assuming you're using ARM's Juno board or FVPs (a.k.a. RTSM a.k.a. Fast Models).
-- Tixy
linaro-kernel@lists.linaro.org
-
Ivan Stalev -
Jon Medhurst (Tixy)