Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 261 online users. » 0 Member(s) | 259 Guest(s) Bing, Google
|
Latest Threads |
The Next Few Months... DS...
Forum: DSL News
Last Post: John
12-16-2024, 01:32 AM
» Replies: 0
» Views: 585
|
Legacy DSL issue
Forum: Help Section
Last Post: grindstone
12-13-2024, 01:29 PM
» Replies: 3
» Views: 607
|
Installing NetworkManager
Forum: User Feedback
Last Post: kayakerkey
12-10-2024, 03:14 AM
» Replies: 2
» Views: 1,880
|
No GPU acceleration suppo...
Forum: User Feedback
Last Post: barkerxavierr
12-04-2024, 04:03 AM
» Replies: 3
» Views: 3,144
|
Release Candidate 7 Now A...
Forum: DSL News
Last Post: salmawis
12-03-2024, 01:31 AM
» Replies: 2
» Views: 4,131
|
Keyboard navigation
Forum: User Feedback
Last Post: grindstone
11-26-2024, 10:51 AM
» Replies: 1
» Views: 931
|
Graphics error after boot...
Forum: Help Section
Last Post: grindstone
11-23-2024, 09:29 PM
» Replies: 25
» Views: 5,066
|
only able to get shell sc...
Forum: Help Section
Last Post: grindstone
11-23-2024, 09:08 PM
» Replies: 1
» Views: 388
|
Roadmap questions
Forum: Other Topics
Last Post: MrAureliusR
11-05-2024, 12:07 PM
» Replies: 2
» Views: 1,079
|
Another JWM project
Forum: Other Topics
Last Post: Rev
10-29-2024, 09:27 AM
» Replies: 23
» Views: 22,699
|
|
|
RC6: With optimization of initrd, it boots the installation with 64 MB! |
Posted by: mifritscher - 10-02-2024, 10:26 PM - Forum: User Feedback
- Replies (1)
|
|
The Initrd of an installed version as grown to compressed 40 MB. This means that it needs at least 256 MB RAM (on 128 MB, it decompresses but chrashes later)
So: Is there a method to archive a smaller initrd?
The main contents:
* 7 MB intel microcode (I think these get purged early, so no problem)
* 32 MB "main" initrd", which gets decompressed to 76 MB
the main initrd:
Most in lib
* 12 MB firmware
* 14 MB lib
* 49 MB modules
Most of the firmware is for network stuff. Perhaps it is useful to ask whether it should be used for PXE boot - because if not this is not needed ;-)
Lib: Crypto is about 5 MB. Only needed for crypted devices. (and why libntfs?)
modules:
1.1 M crypto - only needed for cryptsetup and perhaps enforcing secure boot
39 MB drivers
16 MB net - only needed for PXE-boot
1,5 MB infiniband - I think nobody starts this from infiniband^^
8 MB scsi, ok, needed. Exceptions:
1 MB lpfc - "Emulex LightPulse Fibre Channel" - is not exactly used that often for boot
0,9 MB qla2xxx - "QLogic Fibre Channel HBA Driver" - is not exactly used that often for boot
0,5 MB bfa - "QLogic BR-series Fibre Channel" - is not exactly used that often for boot
5.3 MB fs - 1.2 MB nfs, only needed for pxeboot
1.5 MB net - only needed for pxeboot
so about 38 MB could be saved.
I want ahead. this made about 37 MB initrd, which gets compressed to 14 MB.
Ok now I got more aggressive and killed more (iscsi, ntfs-3g, fuse, btrfs/f2fs/jfx/xfs, sound) - 31/11 MB.
This did not work, because busybox has an hard dependency to libcrypto. But after adding that back (36/13,7 MB) I got it to work with 128 MB RAM! The whole system needs, regarding the desktop, 52 MB RAM + 7 MB swap.
This works even with only 96 MB. Even with 80 (getting an error not having an suitable RAM region for KASL, but started to desktop). The absolute minimum is 79 MB - Linux reports 63 MB then, the rest (16 MB) got eaten by the kernel.
But my target machine has even less RAM - 64 MB. 15 MB still missing.
Additionally, I think the kernel can use squashfs as initrd, so there is no decompression needed.
Problem: The kernel can not use squashfs as initramfs...
Next try: xz. Important: use --check=crc32, else the kernel can not work with it.
-6 made a 9.9 MB image, but needs too much memory for decompress.
-2 made a 11,4 MB image, but still 79 MB RAM is needed.
No compression of the initrd let grub bark out at a OOM - so no help here as well.
Ok, now I got way more aggressive and delete lots of stuff (forgotten btrfs binary, lots of modules)
-> 29,6 / 11,6 MB
The new RAM limit: 70 MB. Ok, 6 MB to go.
Ok, more killing. I tried to leave most of usb, scsi, ide, pcmcia intact.
Also removed the bin versions of the modules-files.
Additionally, somehow the hard link to busybox between bin and sbin got broken, fixed it with a
while [ true ]; do rdfind -makehardlinks true . ; done
(Type Ctrl+C when no dupplicates are found anymore)
-> 26,8/10,6 MB
The new RAM limit: 66 MB. Only 2 to go!
Tried upx on libcrypto.so.3, libext2fs.so.2.4 and libzstd.so.1.5.4 -> but not good as it kills the exports.
Used it on every binary but the busybox (I'm afraid that this hurts the perfomance too much), killed a forgotten ntfs-3g....
-> 25,6 / 10,5 MB
And it BOOTED with 64 MB!
Edit: You can download the last version of the initrd on
https://mifritscher.de/austausch/dsl/2024-rc6/initrd7 and
https://mifritscher.de/austausch/dsl/202...initrd7.gz .
And a Screenshot:
https://mifritscher.de/austausch/dsl/202...enshot.png
|
|
|
Release Candidate 7 Now Available |
Posted by: John - 09-18-2024, 02:11 AM - Forum: DSL News
- Replies (2)
|
|
Added German, French, Spanish, Portuguese language support to the "low ram" faster boot startup option
Fixed Mouse Config and Edit Config Files errors in the Control Center
Enabled Root term window option in file manager
|
|
|
Paste files into directory requiring root |
Posted by: CalY - 09-10-2024, 05:53 PM - Forum: Help Section
- No Replies
|
|
Wish to copy Xmms input plugins that should be have been included: Flac, Musepack, Wavpack and Monkey's Audio to usr/lib/xmms/input. Mod plugin included when most users today don't know what a Mod format is.
Using Zzz fm, under File, Root window, nothng happens. Some days a new window would popup, not now.
How can I copy the files as Root to above directory?
Is there a method to determine either in the install or on CD what the version number of DSL is? Have cd from about June 2024 but did not notice any version number on it.
|
|
|
eth0 is showing two IP addresses no matter what I do to fix it! |
Posted by: xsilentmurmurx - 09-02-2024, 10:52 PM - Forum: Help Section
- Replies (1)
|
|
Hello everyone! I am new to the forum and I am happy that DSL is back in action! Thank you John for resurrecting this awesome project!.
That being said, I installed DSL on a Qemu/libvirt/kvm VM on Arch Linux and even though it installed correctly, no matter what I do, I cannot get the network to work properly. When I do a ip addr show, it shows two IP addresses for the eth0 interface: A 192.168.122.x address, and a 169.254.x.x address. Also my /etc/resolv.conf file has no nameservers defined in it. I tried to reconfigure the interface using the Network interface tool in Control Center, and I configured the IP to be set by DHCP, but no matter how many times I restart the networking, using ifdown eth0/ifup eth0, after a minute or so, the damn 169 address appears again and networking completely stops. I even tried setting the IP as a static IP, but still, the 169 address shows up. Any idea as to what might be the issue and how I can fix this permanently? or is this a misconfiguration in the base install of DSL?
Thank you and please let me know if you need any more information!
|
|
|
Unable to boot on old Toshiba laptop |
Posted by: majenko - 08-08-2024, 02:51 PM - Forum: Help Section
- Replies (6)
|
|
I have a Toshiba Satellite Pro 4200 (P3, 533MHz, 128MB RAM) and am really having a hard time getting DSL to boot.
Before we begin, I'm a Linux veteran of 30 years, so talk technical, as I shall be doing.
Firstly, the live CD will not boot. Or not past loading the kernel. It just kernel panics. Which is no biggie really, there's ways around that. I'm running the laptop on an 8GB SD card in a 44-pin IDE to SD adapter. So I can install "offline" using my main PC and QEmu, which I have done. I've made an image of the OS, fully working, using QEmu running with the same specs as the laptop (P3 cpu, 128MB). That was tricky to begin with, as the initrd is too big for 128MB RAM - you can't have an initrd that is more than 1/4 the amount of available space, and at 39MB that's just a few MB too many. But rebuilding the initrd with modules=dep brings it down to a mere 8MB which is perfect.
So... moving it on to the laptop. The kernel boots, and the initrd loads. Then it tries to (as far as I can tell) mount the root filesystem, and fails, and can't run init. But I cannot work out why. It doesn't tell me that is what is happening, in so many words, it's what I have inferred from the debug output I can get. Which is (I had to video capture this and step it frame by frame to get the juicy bits...):
Code: /init: line 7: mkdir: Value too large for defined data type
/init: line 8: mkdir: Value too large for defined data type
/init: line 9: mkdir: Value too large for defined data type
/init: line 10: mkdir: Value too large for defined data type
/init: line 11: mkdir: Value too large for defined data type
/init: line 12: mkdir: Value too large for defined data type
/init: line 13: mount: Value too large for defined data type
/init: line 14: mount: Value too large for defined data type
/init: line 17: cat: Value too large for defined data type
Loading, please wait...
/init: line 36: mount: Value too large for defined data type
/init: line 39: ln: Value too large for defined data type
... and so on for a number of lines and commands up to line 89 ...
Begin: Loading essential drivers ... done.
/init: line 149: cat: Value too large for defined data type
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Then the kernel panics. "Attempted to kill init! exit code = 0x00000100"
There might be something inbetween the last Begin: and the kernel panic, but if there is, it goes past too quiclky even for the video capture to get it.
I thought at first it might be balking at the ext4 filesystem I had for root, but I have rebuilt the image with ext2 and it's identical in behaviour.
Here's the full kernel panic data:
The full boot sequence can be grabbed here: https://majenko.co.uk/i/dsl-boot.mkv
I am out of ideas. I've even tried booting the root FS direct without the initrd, using various paths for the root (direct /dev, label, uuid, etc) and using /bin/bash as the init (linux ... root=/dev/sda2 init=/bin/bash ...) to no avail - all panic.
I've been tearing my hair out for days with this, even having people live on my twitch stream trying to help me get it going, with no luck.
.... help?
Update: I have cranked the frame rate of my capture dongle, and got an extra message that flew by too quickly before:
No root device specified. Boot arguments must include a root= parameter
Spoiler.... there *is* a root= parameter, and I have tried various different permutations to no avail....
Looking at the init scripts that are executing it could be that `cat` isn't functioning (along with the other essential commands) because of this "Value too large for defined data type" problem, which means the big `case` for setting the environment variables (including ROOT) from the kernel command line parameters (which uses cat to grab them from /proc) fails miserably.
To further cloud the waters, here's what I found on stack exchange for that error:
Quote:The error message you get matches the error code EOVERFLOW, which in the open system call is returned if a 32-bit application tries to open a large (>= 2 GB) file:
Quote:EOVERFLOW
pathname refers to a regular file that is too large to be opened. The usual scenario here is that an application compiled on a 32-bit platform without -D_FILE_OFFSET_BITS=64 tried to open a file whose size exceeds (1<<31)-1 bytes;
As the text hints, 32-bit applications can access larger files, iff they are compiled with the necessary settings (using larger integers for the relevant data types, and calling the proper versions of the system calls).
It would seem that the application you are running isn't compiled to support large files. And no, you can't change that except by recompiling it or getting a version with large file support.
Could it be that we can't have a filesystem of > 2GB or something silly like that? Lemme just "quickly" rebuild my image on smaller SD card... (actually on second thoughts, that can't be it, since it boots with this same image fine on qemu, so it's something specific to this laptop) ... (also you need 3.2GB for the root partition, so no... that's 100% not it.... Just rubberducking here....)
|
|
|
|