-
Search Results
-
Buck Fankers
1. I don’t understand clearly what you like to do.Why not booting a working mx-installation and use the live-usb-maker and there use the full.featured mode for the antix17.2.iso ? This will create a usb-stick with persistence with antix17.2.
2.Is the 4.14.0.3-amd64 smp kernel a debian kernel or a mx-kernel ? Because if it is a mx-kernel you have to add the mx-repos to the sources-list on the antix-live-stick to be able to install it.
There’s a video about updating a kernel on a live-stick.
https://www.youtube.com/watch?v=UWvwbwTGOZ83.Hopefully the stick will boot with another kernel and sure you can install it then.
But maybe someone else can say something to the screenshots you have taken.
1 – trying to use live antiX usb to boot so I can install it on computer. So far only MX17 works. Thanks for the tip for live-usb-maker, never use it yet, I’m new at MX, will look into it and see if I can figure this out.
2 – I wouldn’t know if it is MX or antiX or Debian kernel, there are so many options in synaptic my head is spinning, until today I didn’t even realized there are different kernels, this complicates my task. Thanks you for pointing out about adding repos and for link to the relevant video, it’s now on my to-do list to watch it. (to-do part to understand it may be a problem) 😉
caprea
1. I don’t understand clearly what you like to do.Why not booting a working mx-installation and use the live-usb-maker and there use the full.featured mode for the antix17.2.iso ? This will create a usb-stick with persistence with antix17.2.
2.Is the 4.14.0.3-amd64 smp kernel a debian kernel or a mx-kernel ? Because if it is a mx-kernel you have to add the mx-repos to the sources-list on the antix-live-stick to be able to install it.
There’s a video about updating a kernel on a live-stick.
https://www.youtube.com/watch?v=UWvwbwTGOZ83.Hopefully the stick will boot with another kernel and sure you can install it then.
But maybe someone else can say something to the screenshots you have taken.
In reply to: Favorite Linux Desktop?
rokytnji
Thanks. Giving it a go on this 16 gig ram IBM T430 for starters
harry@biker:~ $ cat /etc/preload.conf [model] # cycle: # # This is the quantum of time for preload. Preload performs # data gathering and predictions every cycle. Use an even # number. # # Note: Setting this parameter too low may reduce system performance # and stability. # # unit: seconds # default: 20 # cycle = 20 # usecorrelation: # # Whether correlation coefficient should be used in the prediction # algorithm. There are arguments both for and against using it. # Currently it's believed that using it results in more accurate # prediction. The option may be removed in the future. # # default: true usecorrelation = true # minsize: # # Minimum sum of the length of maps of the process for # preload to consider tracking the application. # # Note: Setting this parameter too high will make preload less # effective, while setting it too low will make it eat # quadratically more resources, as it tracks more processes. # # unit: bytes # default: 2000000 # minsize = 2000000 # # The following control how much memory preload is allowed to use # for preloading in each cycle. All values are percentages and are # clamped to -100 to 100. # # The total memory preload uses for prefetching is then computed using # the following formulae: # # max (0, TOTAL * memtotal + FREE * memfree) + CACHED * memcached # where TOTAL, FREE, and CACHED are the respective values read at # runtime from /proc/meminfo. # # memtotal: precentage of total memory # # unit: signed_integer_percent # default: -10 # memtotal = -10 # memfree: precentage of free memory # # unit: signed_integer_percent # default: 50 # memfree = 50 # memcached: precentage of cached memory # # unit: signed_integer_percent # default: 0 # memcached = 0 ########################################################################### [system] # doscan: # # Whether preload should monitor running processes and update its # model state. Normally you do want that, that's all preload is # about, but you may want to temporarily turn it off for various # reasons like testing and only make predictions. Note that if # scanning is off, predictions are made based on whatever processes # have been running when preload started and the list of running # processes is not updated at all. # # default: true doscan = true # dopredict: # # Whether preload should make prediction and prefetch anything off # the disk. Quite like doscan, you normally want that, that's the # other half of what preload is about, but you may want to temporarily # turn it off, to only train the model for example. Note that # this allows you to turn scan/predict or or off on the fly, by # modifying the config file and signalling the daemon. # # default: true dopredict = true # autosave: # # Preload will automatically save the state to disk every # autosave period. This is only relevant if doscan is set to true. # Note that some janitory work on the model, like removing entries # for files that no longer exist happen at state save time. So, # turning off autosave completely is not advised. # # unit: seconds # default: 3600 # autosave = 3600 # mapprefix: # # A list of path prefixes that controll which mapped file are to # be considered by preload and which not. The list items are # separated by semicolons. Matching will be stopped as soon as # the first item is matched. For each item, if item appears at # the beginning of the path of the file, then a match occurs, and # the file is accepted. If on the other hand, the item has a # exclamation mark as its first character, then the rest of the # item is considered, and if a match happens, the file is rejected. # For example a value of !/lib/modules;/ means that every file other # than those in /lib/modules should be accepted. In this case, the # trailing item can be removed, since if no match occurs, the file is # accepted. It's advised to make sure /dev is rejected, since # preload doesn't special-handle device files internally. # # Note that /lib matches all of /lib, /lib64, and even /libexec if # there was one. If one really meant /lib only, they should use # /lib/ instead. # # default: (empty list, accept all) mapprefix = /usr/;/lib;/var/cache/;!/ # exeprefix: # # The syntax for this is exactly the same as for mapprefix. The only # difference is that this is used to accept or reject binary exectuable # files instead of maps. # # default: (empty list, accept all) exeprefix = !/usr/sbin/;!/usr/local/sbin/;/usr/;!/ # maxprocs # # Maximum number of processes to use to do parallel readahead. If # equal to 0, no parallel processing is done and all readahead is # done in-process. Parallel readahead supposedly gives a better I/O # performance as it allows the kernel to batch several I/O requests # of nearby blocks. # # default: 30 processes = 30 # sortstrategy # # The I/O sorting strategy. Ideally this should be automatically # decided, but it's not currently. One of: # # 0 -- SORT_NONE: No I/O sorting. # Useful on Flash memory for example. # 1 -- SORT_PATH: Sort based on file path only. # Useful for network filesystems. # 2 -- SORT_INODE: Sort based on inode number. # Does less house-keeping I/O than the next option. # 3 -- SORT_BLOCK: Sort I/O based on disk block. Most sophisticated. # And useful for most Linux filesystems. # # default: 3 sortstrategy = 3 harry@biker:~ $ sudo cp /etc/preload.conf /etc/preload.conf.bk harry@biker:~ $ cd /etc harry@biker:/etc $ ls abcde.conf cups gshadow ld.so.cache mtab rc2.d ssh acpi cupshelpers gshadow- ld.so.conf mtools.conf rc3.d ssl adduser.conf dbus-1 gss ld.so.conf.d nanorc rc4.d staff-group-for-usr-local adjtime debconf.conf gtk libao.conf netconfig rc5.d subgid alternatives debian_version gtk-2.0 libaudit.conf netscsid.conf rc6.d subgid- antix-version default gtk-3.0 libgda-5.0 network rc.local subuid apm defaultdomain gufw libnl-3 networks rc.local.dpkg-old subuid- apparmor.d deluser.conf hdparm.conf libpaper.d newsbeuter rcS.d sudoers apt desktop-session host.conf libreoffice newt request-key.conf sudoers.d asciidoc dhcp hostname libuser.conf nsswitch.conf request-key.d sysctl.conf asound.conf dictd hosts live obex-data-server resolvconf sysctl.d avahi dictionaries-common hosts.allow locale.alias openal resolv.conf systemd bash.bashrc dillo hosts.deny locale.gen opt rmt terminfo bash_completion dkms hp locale.gen.all os-release rpc timezone bash_completion.d dpkg iceweasel locale.gen.net pam.conf rsyslog.conf tmpfiles.d bindresvport.blacklist drirc idmapd.conf localtime pam.d rsyslog.d ucf.conf bluetooth elinks ifplugd logcheck papersize samba udev bogofilter.cf emacs ImageMagick-6 login.defs passwd sane.d udevil bootchartd.conf environment init logrotate.conf passwd- screenrc udisks2 ca-certificates esound init.d logrotate.d pcmcia s-distro-level ufw ca-certificates.conf firefox-esr initramfs-tools lsb-release perl s-distro-version uniconf.conf ca-certificates.conf.dpkg-old fish inittab magic pm securetty updatedb.conf calendar fonts inputrc magic.mime pmount.allow security UPower chatscripts fstab insserv mail pnm2ppa.conf selinux usb_modeswitch.conf chromium.d fstab.bk insserv.conf mailcap polkit-1 sensors3.conf usb_modeswitch.d clicompanion.d fstab.hotplug insserv.conf.d mailcap.order ppp sensors.d vdpau_wrapper.cfg conf.d fuse.conf inxi.conf mailname preload.conf services vim conky fuse.conf.bk ioctl.save manpath.config preload.conf.bk sgml wgetrc console gai.conf iproute2 mc profile shadow wicd ConsoleKit gconf irssi.conf menu profile.d shadow- wildmidi console-setup gftp iso-snapshot.conf menu-methods protocols shells wodim.conf cron.d ghostscript issue mime.types pulse skel wpa_supplicant cron.daily gnome-vfs-mime-magic issuebk mke2fs.conf python slim.conf wvdial.conf cron.hourly GNUstep issue.net modprobe.d python2.7 smartd.conf X11 cron.monthly gpm.conf jwm modules python3 smartmontools xdg crontab groff kbd modules.bk python3.4 smxi.conf xlock.staff cron.weekly group kernel modules-load.d ranger spacefm xml cruft group- kernel-img.conf motd rc0.d spamassassin xpdf crypttab grub.d ldap mpv rc1.d splash harry@biker:/etc $ apt-cache policy preload preload: Installed: 0.6.4-2 Candidate: 0.6.4-2 Version table: *** 0.6.4-2 0 500 http://ftp.gr.debian.org/debian/ jessie/main i386 Packages 100 /var/lib/dpkg/statusSometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsMore helpful would be if you can get a picture with a camera of the error and the menu that you get.
Will do!
Other than that as in my last post, load the usb without using dd so that the persistent option would work and boot the usb on a working computer. Then install and switch to using the debian kernel that mx 17.1 is using. Followed by trying to load the usb with the new kernel on the chromebook
I’m trying to understand this, very noob here, haven’t use persistent antiX/MX USB so far. Let me see if I understand the steps. I’m not sure how to prepare USB from iso without using DD. Ahh, maybe I understand, here are steps:
– 1 – on working computer boot (latest?) antiX iso from one USB and install it on to another USB, to get persistent USB.
– 2 – on same working computer boot from newly installed persistent usb and replace current kernel with the one, that is the same as on chromebook (working MX) has.
– 3 – once kernel is replaced, use this persistent usb and try to boot chromebook off it.If upper steps are correct, I may be able to pull this off. 🙂
There are so many kernels available, (with the same version number) I may need a help which one exactly I should install.If the simpler command also does not work, then I’d suspect either media issues or a problem with the connection where you are plugging in the USB.
Thanks, I didn’t know potential issues when using more flags, but yes makes sense, more options, more chances something may go wrong. I will use from now on simple syntax to avoid possible problems.
That being said, I would like to point out, that all these DD’s works great on two other computers, they always boot without the problem. The only problem I have is, getting them to boot on this Chromebook converted laptop. I can get MX 17.1 to boot but none of antiX would boot. I tried full, base and core iso for all three versions, 17.2.1, 17.1 and 17. Since MX 17.1 does boot I’m hoping I can get antiX on this laptop. New beta MX 18 is behaving exactly the same way with the same errors as all antiX versions.
Since laptop is slow and weak i would really like to get antiX working on it instead MX. Beside, if I can’t solve the problem, future versions of MX will not work either, based on the same problems I have with beta MX 18.
Bottom line is, media (USB sticks) are OK, I’m using several different and all of them works great on two other computers with these same antiX ISO files.
- This reply was modified 4 years, 5 months ago by Buck Fankers.
Brian Masinick
If the options you have used work for you, then I’d say “great”, but since you were having problems, I’d suggest trying the simpler syntax.
I have seen the status=progress clause; recently it did not work for me on at least one of my systems. I believe that I have experienced similar issues with the conv=fsync clause too, which is why I omitted them both from my simple example; they may work on some systems and I’ve seen them mentioned in the documentation, but I’ve had at least one (if not more than one) instance in which they did not work.If the simpler command also does not work, then I’d suspect either media issues or a problem with the connection where you are plugging in the USB.
I hope these things are helpful; try the simpler command because I have always experienced success using it.
A sample dd command that is syntactically valid is:
sudo dd if=/home/my-UID/myUSB.iso of=/dev/sdb bs=4M; sudo sync
Thank you, will try with your command next
Here is what i used so far: (running it from folder where iso file is, to make the command simpler)‘sudo dd if=image.iso of=/dev/sdX bs=4M status=progress && conv=fsync’
And when writing is finished, I type sync on more time just to be on a safe side
- This reply was modified 4 years, 5 months ago by rokytnji.
--
Brian MasinickBrian Masinick
The correct usage of the dd command will create a usable USB that can be used to boot the system.
A sample dd command that is syntactically valid is:
sudo dd if=/home/my-UID/myUSB.iso of=/dev/sdb bs=4M; sudo sync
Replace the file in the if= subcommand by the location of your bootable image, and of= by the device file of your USB device.
--
Brian MasinickI replaced BIOS with MrChromebook, MX 17 works on it although without sound.
But antiX would be more suitable for this weak laptop. I can’t get any antiX to even boot from live USB.
I tried:
17.2_x64-full
17.1_x64-full
17_x64-full
17.2_x64-base
17.2_386-base
Same with latest mx 18.1 beta all give me the same errorFirst I see: Error: unknown filesystem, press any key to continue
Few seconds later or it I press a key, I see asci like boot menu, no graphic, no F options at the bottom, there are two boot options (none works, screen just goes dark and stays tat way, cant switch to TTY, third option is memory test and if I choose it, i get another error:
Error: disk ‘hd0 msdos2’ not found
Interestingly, MX 17 does bot and I managed to install it.
But new beta MX 18.1 is acting the same as all 17 antix versions.Does anyone have any suggestions? Specs:
My guess/hope is, since MX uses antiX base and since MX 17 works, maybe I can get antiX on it too somehow
$ inxi -Fxrz
System: Host: mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3
Distro: MX-17.1_x64 Horizon March 14 2018 base: Debian GNU/Linux 9 (stretch)
Machine: Type: Laptop System: GOOGLE product: Celes v: 1.0 serial: <filter>
Mobo: GOOGLE model: Celes v: 1.0 serial: <filter> UEFI: coreboot v: MrChromebox date: 08/27/2018
Battery: ID-1: BAT0 charge: 28.1 Wh condition: 34.6/33.4 Wh (103%) model: SDI 4352D44 status: Discharging
CPU: Topology: Dual Core model: Intel Celeron N3060 bits: 64 type: MCP arch: Airmont rev: 4
L2 cache: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400
Speed: 1971 MHz min/max: 480/2480 MHz Core speeds (MHz): 1: 1666 2: 705
Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics driver: i915
v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366×768~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 400 (Braswell) v: 4.5 Mesa 13.0.6 direct render: Yes
Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio
driver: snd_hda_intel v: kernel bus ID: 00:1b.0
Sound Server: ALSA v: k4.15.0-1-amd64
Network: Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel port: 1000 bus ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Drives: Local Storage: total: 14.68 GiB used: 7.04 GiB (48.0%)
ID-1: /dev/mmcblk0 model: DF4016 size: 14.68 GiB
Partition: ID-1: / size: 11.18 GiB used: 7.04 GiB (63.0%) fs: ext4 dev: /dev/mmcblk0p2
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/mmcblk0p3
Sensors: System Temperatures: cpu: 54.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://iso.mxrepo.com/antix/stretch stretch main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1:$ inxi -Fxrz
- This topic was modified 4 years, 5 months ago by Buck Fankers.
- This topic was modified 4 years, 5 months ago by Buck Fankers.
- This topic was modified 4 years, 5 months ago by Buck Fankers.
BobC
I downloaded and installed antiX-17.2_x64-full.iso, then added the dev repo.
When I did the apt-get update I did get warnings, but assume that was ok
I then installed the lumina-desktop, which went ok.
I tried changing to it and that works, but you don’t know it because an “Other Desktops” window opens saying “your window manager is not one of the supported window managers” and if you pick one, it doesn’t open the lumina desktop. Cancel gets you to the desktop.
I do like that it put up icons for the volumes, but the color of the text used under the icons is almost the same as the background, and the font is too large for the icon spacing. I also had the same problem with the tray volume icom and time.
Firefox and Spacefm work, but I can’t see how to resize windows. I can move or make them full screen or minimize, but can’t use the mouse to resize them.
The terminal option on the menu wants to open xterm it looks, but if you use the applications menu, root terminal goes nowhere, too. Lxterminal did work.
The start menu looks like it was intended to shop applications, but its empty.
Memory usage is significant, partly because its trying to run wicd which I had booted the flashdrive with NOWICD, but forgot to check the use boot options when installing, possibly. I see an icon in the tray that says “not connected” as I type this.
I like my IceWM better, but will leave Lumina installed in case you want me to try any other tests with it, and appreciate your willingness and time/effort making other environments available. I may try some of the others available from the package installer.
$ su Password: root@HPdv9917:/home/bobc# ps_mem.py Private + Shared = RAM used Program 140.0 KiB + 41.0 KiB = 181.0 KiB ifplugd 164.0 KiB + 55.5 KiB = 219.5 KiB gnome-pty-helper 224.0 KiB + 33.0 KiB = 257.0 KiB gpm 268.0 KiB + 58.0 KiB = 326.0 KiB init 296.0 KiB + 39.5 KiB = 335.5 KiB acpid 336.0 KiB + 41.5 KiB = 377.5 KiB wpa_cli 332.0 KiB + 70.5 KiB = 402.5 KiB irqbalance 336.0 KiB + 101.5 KiB = 437.5 KiB cron 360.0 KiB + 99.5 KiB = 459.5 KiB dbus-launch 500.0 KiB + 51.5 KiB = 551.5 KiB rpc.idmapd 444.0 KiB + 157.0 KiB = 601.0 KiB rpcbind 392.0 KiB + 238.0 KiB = 630.0 KiB udevil 352.0 KiB + 575.0 KiB = 927.0 KiB avahi-daemon (2) 680.0 KiB + 313.0 KiB = 993.0 KiB devmon 740.0 KiB + 312.5 KiB = 1.0 MiB gconfd-2 876.0 KiB + 207.5 KiB = 1.1 MiB rpc.statd 1.0 MiB + 164.5 KiB = 1.2 MiB sshd 900.0 KiB + 327.0 KiB = 1.2 MiB desktop-session 904.0 KiB + 518.0 KiB = 1.4 MiB getty (6) 1.5 MiB + 65.5 KiB = 1.5 MiB udevd 1.2 MiB + 364.0 KiB = 1.6 MiB xscreensaver 1.5 MiB + 79.0 KiB = 1.6 MiB rsyslogd 1.0 MiB + 666.0 KiB = 1.7 MiB polkitd 1.2 MiB + 615.0 KiB = 1.8 MiB dbus-daemon (3) 1.2 MiB + 950.0 KiB = 2.1 MiB su 2.1 MiB + 442.0 KiB = 2.6 MiB wpa_supplicant 1.7 MiB + 1.1 MiB = 2.7 MiB cupsd 2.2 MiB + 705.0 KiB = 2.9 MiB dhclient (2) 3.2 MiB + 26.0 KiB = 3.3 MiB haveged 2.9 MiB + 503.0 KiB = 3.4 MiB at-spi2-registryd 2.9 MiB + 669.5 KiB = 3.6 MiB at-spi-bus-launcher 3.6 MiB + 545.5 KiB = 4.1 MiB console-kit-daemon 3.4 MiB + 823.0 KiB = 4.2 MiB bash (2) 1.6 MiB + 2.9 MiB = 4.5 MiB lumina-open 4.0 MiB + 939.0 KiB = 4.9 MiB fluxbox 4.1 MiB + 1.0 MiB = 5.1 MiB conky 2.4 MiB + 3.2 MiB = 5.7 MiB volumeicon 2.4 MiB + 4.9 MiB = 7.3 MiB start-lumina-desktop 7.0 MiB + 981.0 KiB = 7.9 MiB pulseaudio 4.8 MiB + 3.4 MiB = 8.1 MiB lxterminal 12.9 MiB + 1.6 MiB = 14.5 MiB slim 18.1 MiB + 5.2 MiB = 23.4 MiB wicd-client 23.3 MiB + 2.3 MiB = 25.6 MiB applet.py 17.2 MiB + 13.5 MiB = 30.7 MiB Xorg 64.6 MiB + 19.2 MiB = 83.8 MiB lumina-desktop --------------------------------- 270.7 MiB =================================- This topic was modified 4 years, 5 months ago by BobC.
Attachments:
In reply to: Hello, I want to try Antix, but…
Anonymous
@skidoo: about “alternative facts” — please see the image below … no proofreading, just a plain ol’ c&p 😉
Now NOT alternative facts:
1. Multi-boot USB is not as reliable as Single-boot USB.
2. There are different ways how the ISO’s are created and many different ways how the (single- or multi-) boot pendrives can be written / created.
3. Installing any OS from a USB on some old machines, +/- year 2000 ~ 2003, can be very challenging, even for people who exactly know what they do.
4. USB & USB-Ports compatibility is a known problem — general recommendation if something does not work is still the same since there is USB boot:
–> use same USB pen drive speed as the USB-ports (USB1 on USB1 port, USB2 on USB2 port, USB3 on USB3 port).
5. Multi-boot needs a certain degree of knowledge and understanding …
Even if one makes it to boot from USB, using PLOP as a boot manager means, one has to know where to put Grub or Syslinux, so that Linux boots but, so that PLOP doesn’t get killed.
Multi-boot of “Mixed environment” (Linux, Mac, Solaris & Windows for example) is very challenging task — one has to know exactly what one’s doing and why so and not different.
Which system has to be installed first, which one last, which one will overwrite what or how, which settings to make inside of each system to keep it working after install …Proper answer (explanation and description of complete process) to the question of a thread starter would make enough material for a book or at least a booklet. There’s just too much that can go wrong in such use cases like the one described at the beginning.
@olsztyn: Don’t understand me wrong, I don’t mind old machines but, …
… close to 20 years old PIII Thinkpad T23, also with USB 1.1 and Antix runs fine on it.
“Runs fine” is a very personal opinion and not questionable but, there is another much more relevant part to it: what for are you doing it exactly?
If you only see it as a challenge and a “just killing time” occupation / hobby, then it’s fine.
If you want a machine that serves any other purpose then just “trying to see if I can make it”, then you can forget it.
Such old things just can’t do any serious work today, no matter from which point of view you look at it.
Screen with very low resolution, processor speed is to low, energy consumption too high, if laptop, then battery died 15 years ago, if you start web browser, machine stops responding … and even if it still works somehow, do you really want to rely on 20 years old HD or even processor for any serious work?
In reply to: Hello, I want to try Antix, but…
olsztyn
Mr. skidoo – I am surprised you can be so funny, considering you have taken so seriously my Greek comments in Greek Kafeneio…
Regarding this issue brought up to attention by new AntiX user I see the positive side: AntiX is known to be so good that it boots on almost anything, regardless of conditions… This is the perception and (high) level of expectation of AntiX it seems…User iNeedHelp:
Do not be discouraged. What is the exact model of your laptop and does it have CD drive?
I can tell you that among my many laptops one of them is about like yours – close to 20 years old PIII Thinkpad T23, also with USB 1.1 and Antix runs fine on it.
Never mind Virtualbox on a different laptop story, just try to boot AntiX from ISO on CD drive and see what you get…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersIn reply to: Hello, I want to try Antix, but…
Let us see the facts first:
What we have is:
1. I’m new to Antix (and Linux too)
2. Very old laptop with Intel Celeron and 256+128mb RAM … which was junk 10 years ago
3. MultinootUSB
4. plop bootmanager installed with BOOTICE
5. Antix not starting (tried laptop and VirtualBox)
6. SparkyLinux and MS-DOS also copied to pendrive boots well
7. I’m new … I want a lot … I know too little … I use something that 15 years ago had to be replaced with a computer …🙂 🙂 🙂 🙂 🙂
(Sorry, didn’t mean anything bad but, just couln’t resist)
My suggestion is as following: start from the beginning and start with “known working.
And … start with a Pen Drive that works on other old machines.
Get yourself Rufus:
and then i386 / i486 copy of antiX:
https://ftp.nluug.nl/os/Linux/distr/mxlinux-cd/ANTIX/Final/antiX-17.1/antiX-17.1_386-full.iso
Take OLDEST WORKING USB flash drive you can find (15 year old USB1 1GB would be perfect) and MAKE SURE you can boot it on some other very, very old Laptop BEFORE you continue.
If you make it to boot on your computer, start with NOMODESET and ACPI=OFF options.
When you are so far, you can tell us how’s going.
Good luck!
possible FAQs, prior to testing and feedback:
Q: Can I use isofromlive during a livession when persistence is enabled?
A: Yes, and it can also be used during a NON persistence session.Q: Will the iso reflect even the changes I made, packages I installed, 5 minutes ago?
A: Yes. (independent of persistence, it creates a point-in-time copy, doesn’t require persist-save in advance)Q: Can I run this utility on an installed-to-HDD antiX system? Howabout on a Mint system?
A: No.
A: No.Q: Can I run this utility on MX Linux, during a liveboot session?
A: To be safe, wait for the MX developers to check/tweak it (handle any differing details) + issue a renamed version.Q: Screenshot text says “MANY minutes”. How long does it actually take to make the copy?
A: It’s hugely a YMMV thing. On a 12-core CPU @3.9GHz, tested average time to completion (using default config) was 3min 15sec (1.0Gb iso)Q: Can I still use isofromlive if I’ve wholedisk encrypted my boot partition?
A: Yes, probably (untested). Bear in mind: contents within the fresh linuxfs copy will be unencrypted.Q: What is “Live-USB-Storage”? I can’t find that on my antiX live system.
A: doc: “The live-usb-store feature creates a Live-usb-storage/ subdirectory in your home directory that gives you access to all of the remaining storage space on the main live-usb partition.” A couple dolphin_oracle videos demonstrate it / provide a detailied explanation, e.g. https://www.youtube.com/watch?v=qq0mRZh2hiY&t=503Q: Does EVERYTHING get copied? Part of the motivation for my custom iso is get a smaller, leanermeaner version.
A: isofromlive ships with a curated list of paths//files to be omitted during the copy operation. Please inspect this list, and edit it to suit your preferences.hi everyone, this is me and thanks to user SPARTAK77 to have introduced my issue with Antix so i am the guy with the trouble.
Obviously i am walker1 member of italian forum too:
http://www.istitutomajorana.it/forum2/Thread-linux-Antix-kernelSo, i have no CD available at the moment so i burned Antix iso to my bootable USB key that i created by using Rufus and Unetbooting.
Anyway, the issue comes when i boot my pc by USB key because it happens Antix logo appears but i can NOT move any key of my keyboard and same for my mouse so i have to turn my pc off everytime i boot like that.My keyboard keys ALWAYS works when i boot a lot of other old Linux iso’s but they don’t with Antix 17.2 iso so my issue is not fault of my keyboard hardware but of iso’s.
Infact my keyboard PERFECTLY works when i boot Puppy Linux Tahr 6.0 (very old Linux iso) by USB key.So how can i enable my keyboard keys at “Antix 17.2” USB boot ?
By myself i think my pc is very very old (purchased in year 2004) so same for hardware inside my pc so that’s way USB boot gets that issue.
Maybe, could you give me an alternative Antix 17.2 modified iso in order i can boot without use keyboard keys ?This is Antix USB boot logo where my keboard never works:
Spartak77
In a general computer forum, I’m trying to help a user who wants to install antiX 17.2 on an old PC by a pendrive obtained with unbooting
The Thread in the forum is this:
http://www.istitutomajorana.it/forum2/Thread-linux-Antix-kernelThe computer is Fujitsu SCENIC E600 CPU 4 2.4 GHz RAM 500 MB – 40 GB
These are the features:Processor / Chipset • CPU Intel Pentium 4 2.4 GHz • Data Bus Speed 800 MHz • Chipset Type Intel 865G • Processor Main Features Hyper-Threading Technology • Processor Socket Socket 478 Cache Memory • Installed Size L2 cache - 512 KB • Cache Per Processor 512 KB • Type L2 cache • Per Processor Size 512 KB • Installed Size 512 KB Memory • Max Supported Size 2 GB • Form Factor DIMM 184-pin • Slots Qty 2 Storage • Interface Type ATA-100 • Type none • Read Speed 48x (CD) / 16x (DVD) RAM • Memory Speed 400 MHz • Memory Specification Compliance PC3200 • Technology DDR SDRAM • Installed Size 512 MB • Rated Memory Speed 400 MHz Audio & Video • Memory Allocation Technology Shared Video Memory Technology 2.0 Hard Drive • Type HDD • Interface Type ATA-100 • Spindle Speed 7200 rpm • Type HDD • Interface Class Parallel ATA • Installed Qty 1 • Capacity 40 GB Storage Controller • Interface Type Serial ATA-150 • Type Serial ATA • Installed Qty 1 Storage Controller (2nd) • Controller Interface Type ATA-100 • Installed Qty 1 Processor • Installed Qty 1 • Max Supported Qty 1 • Type Pentium 4 • Manufacturer Intel • Clock Speed 2.4 GHz Optical Storage • Drive Type CD/DVD • Type DVD-ROM • Interface Type IDE Miscellaneous • Features USB port control, administrator password, chassis intrusion detection, hard drive password, system password, thermal monitoring • Compliant Standards ACPI, CSA, ISO 9241, UL, EN 60950, EN 61000-3-2, EN 61000-3-3, EN55022, EN55024, FCC Class B certified, GS, IEC 60950 Networking • Data Link Protocol Ethernet, Fast Ethernet, Gigabit Ethernet • Remote Management Protocol DMI 2.0 • Form Factor integrated • Features Alert on LAN 2, Wake on LAN (WoL) System • Type personal computer • Hard Drive Capacity 40 GB Graphics Controller • Form Factor integrated • Graphics Processor Intel Extreme Graphics 2 Dynamic Video Memory Technology 2.0 • Video Interfaces VGA Mainboard • Processor Socket Socket 478 • Data Bus Speed 800 MHz • Chipset Type Intel 865G Audio Output • Form Factor integrated • Sound Output Mode stereo • Compliant Standards AC '97The problems encountered are these:
In the Live boot phase, this message comes out:gfxboot: not a com32 image
However, by pressing the TAB key, the user can move forward and load the Live
When the Live opens, the user said that the system did not see the hard disk.
Then on my directions, telling him to use SpaceFM as Window Manager and using Center Control → Disk → Mount Device
System finally sees the hard disk.
But when he proceeds with the installation, the installer reports this message:
“partition sda1 is not internal device and you are not a root user”
I advised to go in
Start-Menu → Run
and type
minstall
with the “Run as Root” option
Unfortunately it seems that this is not enough.
I could recommend to login as root user but I do not know if it is a good thingNote. I have advised him to try using a CD or DVD for installation but it does not have a burner and at the moment it does not find anyone who burns the DVD.
Note. The computer has old ports with aptii attack for the connection with the keyboard, the user does not have a keyboard that connects with that old attack, I think he has borrowed one to try to do the installation, but he has a USB keyboard that the system does not recognize. He would like to use this but he did not give informations to me to identify the keyboard. I asked to type:
lsusb
on another computer with another linux system that can recognize the keyboard, but at the moment it is not able to give me directions.
However, the keyboard is a problem to be solved later, while I would like to help him about the problem of installing the system.
Failing to help him, I had already suggested to join the forum and ask for help directly here. Meanwhile, I introduced here the problem to solve and then I will invite him to write directly because it’s not helpful if I am an intermediary- This topic was modified 4 years, 6 months ago by Spartak77.
- This topic was modified 4 years, 6 months ago by Spartak77.
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
