Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 103 online users. » 0 Member(s) | 102 Guest(s) Applebot
|
Latest Threads |
AMD Geode driver
Forum: User Feedback
Last Post: thomasfrank
07-04-2025, 07:49 AM
» Replies: 3
» Views: 568
|
how do i use persistance ...
Forum: Help Section
Last Post: thomasfrank
07-04-2025, 07:46 AM
» Replies: 2
» Views: 753
|
RC7: can not boot from US...
Forum: User Feedback
Last Post: grindstone
07-03-2025, 01:47 PM
» Replies: 5
» Views: 4,012
|
Good Show
Forum: User Feedback
Last Post: Teredly
07-03-2025, 10:16 AM
» Replies: 2
» Views: 430
|
DSL 2024 = impressive
Forum: User Feedback
Last Post: grindstone
06-30-2025, 06:34 PM
» Replies: 2
» Views: 605
|
You're The Program That I...
Forum: Help Section
Last Post: grindstone
06-25-2025, 11:05 PM
» Replies: 1
» Views: 329
|
Keyboard navigation
Forum: User Feedback
Last Post: Twels1962
06-25-2025, 08:41 AM
» Replies: 3
» Views: 4,148
|
Suggestions driver, firmw...
Forum: User Feedback
Last Post: Letion1998
06-25-2025, 03:04 AM
» Replies: 14
» Views: 26,551
|
dsl on my little netbook ...
Forum: Other Topics
Last Post: col2025
06-23-2025, 01:51 PM
» Replies: 0
» Views: 266
|
The Next Few Months... DS...
Forum: DSL News
Last Post: Gyro
06-18-2025, 06:26 PM
» Replies: 4
» Views: 9,926
|
|
|
Graphics error after boot menu, boot unsuccessful. |
Posted by: Cactus2580 - 10-23-2024, 11:06 PM - Forum: Help Section
- Replies (25)
|
 |
Hello all, I have been greatly enjoying testing out the rc7 release of DSL2024! It has ran flawlessly on all the hardware I've attempted to run it on so far, however when attempting to boot it on an Acer Aspire One AO722 netbook I have ran into an interesting graphics error that prevents booting.
The situation is as follows:
Netbook successfully makes it to the boot menu, no issues there, but upon choosing any of the options on the boot menu it proceeds to a nice looking loading bar followed immediately after by a graphics error resembling a rainbow version of CRT TV 'snow' and boot does not proceed. "Safe video mode","virtual box video","failsafe boot", and "text" mode all have the same results. Any suggestions?
Some more information:
The Acer aspire one 722 supposedly has a screen resolution of 1366x768 which -IS- an option in the "F7- console" setting of the boot menu, but selecting that resolution results in "undefined video mode number: 37f" error and a selection of other resolutions. All choices result in graphics error and no boot. This netbook will run other Linux/BSD/Haiku with no graphical errors, and it would be perfect for DSL. Namely, it boots fine on other extremely cut down Linux distributions such as Tinycore, etc, can't quite figure out why this wouldn't work with DSL.
I have also successfully ran DSL2024.RC7 on an older Acer Aspire One ZG5 (4 years older than the AO722) and it booted and ran flawlessly.
Is this an issue of hardware compatibility, an issue of drivers, or some form of operator error? Would love to run this as the primary operating system on this netbook.
Any help would be much appreciated!
EDIT:
After some testing, I was able to run the netbook with various resolution modes via KolibriOS, and it will run a number of display modes which are options given by the DSL2024 boot menu with no issues, yet DSL can not do this? Is there a boot flag I need to set for things to operate properly?
After some more testing, I was able to run the exact same flash drive containing DSL2024.rc7 on a Dell laptop which also has a 1366x768 resolution with no errors, runs flawlessly, resolution number provided by Conky from within DSL. This rules out some sort of corrupted data on the flash drive. What gives? The netbook has an AMD C-60 APU, integrated graphics and processor, is that the likely culprit? I will experiment further, perhaps try a different kernel?
|
|
|
Desktop Icons |
Posted by: erico - 10-15-2024, 03:05 AM - Forum: Help Section
- Replies (2)
|
 |
Hi All,
Saved a Asux Eee PC from the recycle bin. Loaded up easy with the 2024 DSL. Installed putty (terminal program) for talking to amateur radio terminal node controller (TNC).
Being simple minded, I can not get icons to go with desktop shortcuts. Can I get a hint on how do add icons to the desktop links?
Thank you,
Erico
|
|
|
RC6: Needs a 686, a 586 is not enough :-( |
Posted by: mifritscher - 10-02-2024, 10:44 PM - Forum: User Feedback
- Replies (3)
|
 |
While the kernel can work with a 586, it seems that init does need at least a 586 :-( The kernel cries with "Attempting to kill init" - the backtrace shows a exception regarding an illegal exception.
Tested with
qemu-system-x86_64 -m 256 -cpu 'pentium2-v1' /dev/sdd
.
The culprit: /lib/runit/runit-init uses CMOV (2 times in the whole binary), and this is supported only on Pentium Pro onwards.
Would it be possible to recompile the binaries with march=586 (or pentium)? Then I could probably run it on an IBM Thinkpad 760 (P1-133 and 64 MB RAM - for the RAM see the other thread) :-)
Btw, even the K6... K6-3 are 586 class CPUs.
Another way to fix this would by to apply the kernel patch found under https://lore.kernel.org/lkml/20210626130...@orca.pet/ .
This way, the user mode binaries do not to be changed :-)
|
|
|
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 (4)
|
 |
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
- No Replies
|
 |
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!
|
|
|
|