Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've followed everything and on the first try I had an error that had been easily addressed. It was a problem with the vlan keyword on the NETTYPE.
After this I've issued the installer_launch script but after the tipical kernel messages it starts complaining with:
Code:
[ 170.107314] Run /init as init process
/etc/rc.d/rc.modules-arm: line 67: 108 Segmentation fault $MP $mod > /dev/null 2>&1
/etc/rc.d/rc.modules-arm: line 67: 109 Segmentation fault $MP $mod > /dev/null 2>&1
/etc/rc.d/rc.modules-arm: line 67: 110 Segmentation fault $MP $mod > /dev/null 2>&1
and does this for many lines.
At the end f this errors I get a prompt, but whichever command I issue I get a kernel panic and the only thing I have to do is kill the qemu-system-arm ( from antoher windows ):
Code:
[ 934.152688] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 934.154074] CPU: 0 PID: 1 Comm: init Not tainted 5.4.18-armv7 #2
[ 934.154891] Hardware name: ARM-Versatile Express
[ 934.156754] [<c030f480>] (unwind_backtrace) from [<c030a8e4>] (show_stack+0x10/0x14)
[ 934.158127] [<c030a8e4>] (show_stack) from [<c09edd48>] (dump_stack+0xb8/0xdc)
[ 934.159417] [<c09edd48>] (dump_stack) from [<c033e708>] (panic+0xe8/0x2fc)
[ 934.160774] [<c033e708>] (panic) from [<c0341a58>] (do_exit+0x1a0/0x9b0)
[ 934.161711] [<c0341a58>] (do_exit) from [<c0342db8>] (do_group_exit+0x58/0xb8)
[ 934.162788] [<c0342db8>] (do_group_exit) from [<c034d144>] (get_signal+0x194/0x61c)
[ 934.164075] [<c034d144>] (get_signal) from [<c030a1f0>] (do_work_pending+0xc4/0x34c)
[ 934.165259] [<c030a1f0>] (do_work_pending) from [<c0301064>] (slow_work_pending+0xc/0x20)
[ 934.166401] Exception stack(0xee095fb0 to 0xee095ff8)
[ 934.167369] 5fa0: b6ef3fd0 00000000 00000019 bec6dc81
[ 934.168653] 5fc0: b6f99e00 b6fb9950 00000001 00000002 00000000 00000000 b6fbc000 001017c8
[ 934.169881] 5fe0: 00101308 bec6dc88 00000001 00000000 60010030 ffffffff
[ 934.171634] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
Is there someone that has addressed this problem ?
Is there someone that has addressed this problem ?
Hi, could you post a description on which hardware you're using, and operating systems involved, and why you're cross-compiling? I need some grasp of your setup, what you're trying to achieve, and how you're trying to achieve it. Thanks in advance.
My setup is:
Hw MacbookPro 2011
Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz ( 4 core )
8Gb Ram
O.s. Slackware-current upgraded on Feb 6.
Kernel 5.4.13 #1 SMP x86_64
My need is to have an environment to cross-compile those packages that I cannot directly compile on my Raspberry PI ( 3+ ).
My idea is to have a "VM" using qemu with the same setup of my Pi ( slackware-current ) but with a bit more of resources to achieve those compilations.
In this way I can get the packages ready to be installed on Pi.
I'll have a look at that. Did you follow the installation documents on docs.slackware.com? Is that where you took the script from?
Yes, exactly from there.
Feel free not to be in a hurry. At the moment I have been able to "build" golang directly on Pi, so it' not urgent ( also it it will be easer to work on faster environment )
Thanks for your time.
It works fine here with qemu 4.1.0 on Slackware64-14.2. It seems that the qemu network settings need some work though, because just removing the 'vlan' parameters don't bring up eth0.
If anyone knows how to fix that, let me know: I've looked at the docs just now and it's not as obvious as I'd have hoped.
It works fine here with qemu 4.1.0 on Slackware64-14.2. It seems that the qemu network settings need some work though, because just removing the 'vlan' parameters don't bring up eth0.
If anyone knows how to fix that, let me know: I've looked at the docs just now and it's not as obvious as I'd have hoped.
I've popped a note at the head of the document, in case anyone wants to submit a diff to the helper scripts.
The docs have been updated and a clean qemu vm booted with arm-current on a Slackware64-14.2 host. The Slackwarearm-current qemu guest changelog is dated Sun Sep 20 08:08:08 UTC 2020.
@Pigi_102: If you are trying to boot an aarch64 or arm64 kernel with Slackwarearm, this has not been tested. Slackware ARM is based on x86. Also, I test in qemu with the stock 14.2 kernel (4.4.227 at this time). The stable release is the host target and the qemu guest targets arm-current.
Please mark this thread as solved if none of this applies any longer.
EDIT:
The installer boots and installs, it just takes a long long time.
I booted the resulting install with the disk_launch script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
) 
