slarm64This forum is for the discussion of slarm64.
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'm trying to make a -15.0 image because I don't care for rolling release. I downloaded the image builder from https://gitlab.com/sndwvs/images_build_kit then tried this command:
I'm trying to make a -15.0 image because I don't care for rolling release. I downloaded the image builder from https://gitlab.com/sndwvs/images_build_kit then tried this command:
That got me a little further, but there is a bug in the build_images.sh script. Basically the system tries to parse html which is unreliable for every mirror. Here is a patch that passes the parsing off to lftp which works much better:
That got me a little further, but there is a bug in the build_images.sh script. Basically the system tries to parse html which is unreliable for every mirror. Here is a patch that passes the parsing off to lftp which works much better:
this is not because of this, but because the link did not have a folder with slarm64-15.0
I was trying to use my own mirror and it wouldn't work either way because my apache doesn't format in a way the script understands. The default is for https://dl.slarm64.org/slackware/ but before yesterday that didn't have the slarm64-15.0 directory in it so that didn't work either.
At any rate, I still recommend using lftp as it's not as fragile.
I was trying to use my own mirror and it wouldn't work either way because my apache doesn't format in a way the script understands. The default is for https://dl.slarm64.org/slackware/ but before yesterday that didn't have the slarm64-15.0 directory in it so that didn't work either.
At any rate, I still recommend using lftp as it's not as fragile.
Onto the next issue. My system (slackware64-15.0 x86_64) can build a legacy image for the c4 just fine, however the kernel doesn't boot. I get this on the console: https://www.icloud.com/iclouddrive/0...LDw#IMG%5F3496
So, I figure I'll try the next kernel and that fails to compile with this error:
Onto the next issue. My system (slackware64-15.0 x86_64) can build a legacy image for the c4 just fine, however the kernel doesn't boot. I get this on the console: https://www.icloud.com/iclouddrive/0...LDw#IMG%5F3496
So, I figure I'll try the next kernel and that fails to compile with this error:
From what I can tell, mkimage doesn't come in any standard slackware package. I think it's looking for one in the build.
Any ideas why this is failing? I'd sure like a stable image based on slackware64-15.0 that I can use long term.
Thanks
yes and no, mkimage should be used from tools/ (kernel dir), try to find it there and try to execute if it works, then add the path to it to PATH (x86_64 was not tested).
assemble another option on the odroid board itself.
|----------- delimiter ----------- "download" "linux-next" -----------|
HEAD is now at fbe1871b5 Linux 6.2.6
error: pathspec 'linux-5.15.y' did not match any file(s) known to git
|----------- delimiter ----------- "download" "linux-next" -----------|
HEAD is now at fbe1871b5 Linux 6.2.6
error: pathspec 'linux-5.15.y' did not match any file(s) known to git
Thanks
if the directory in source/linux-next has not been deleted, you must first delete it.
but do not forget that patches are only suitable for the branch that is configured.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.