-
Search Results
-
In reply to: Rox-panel options – how to access?
Anonymous
Hi. You are right, I was not using the stock version of rox-filer when I tested.
So I retested after booting fresh ISO and confirmed the result you reported. Panel context for options is unresponsive.When launched from terminal:
$ killall rox
$ rox -p Default -left=pb_antiX-fluxbox
we can notice error output reported
“** (rox:5264): WARNING **: Failed to load builder file /usr/share/rox/Templates.ui: Failed to open file “/usr/share/rox/Templates.ui”: No such file or directory”The antiX (debian) package is missing an expected file.
I found a copy online:
https://raw.githubusercontent.com/rox-desktop/rox-filer/master/ROX-Filer/Templates.ui
(is it correct for the rox-filer version installed in antiX? I don’t know, didn’t check)$sudo touch /usr/share/rox/Templates.ui
then pasted that that github content into the file
and again from lxterminal
$ killall rox
$ rox -p Default -left=pb_antiX-fluxbox
Now the “panel options” menu item opens the expected dialog
but
transparency is not supported as an option in the stock version of rox-filer
and
even when using the customized (forked) version of rox-filer, activating the “pseudo transparency” feature of fluxbox did not trigger transparency in the rox panel,$ rox -p Default -left=pb_antiX-fluxbox
so I guess panel transparency must require a true compositor like xcompmgr or compton
In reply to: Rox-panel options – how to access?
rej
736b69646f6f-
Thanks for posting the Panel-options screenshot.
You are right about “some”. In checking to see which PCs where the panel was not fully at the top of the screen, it was only in devices with installed Mate or Xfce desktops, yet not occurring in IceWM and Fluxbox sessions on the same PC. Also, some computers with Mate or Xfce installed, did not have this display issue or so slight that it was completely unnoticeable. Likely due to the various screen sizes. Definitely has to do with installed desktops though.
As far as the menu, checked in devices that are running IceWM only, and the Rox-Panel will not display the Panel options.
Purged rox and installed w/ apt-get. When reinstalled, there was no Rox-panel at all. It was not in the applications file or menus. Rebooted – no panel. Checked synaptic to see if it could be installed and did not see it there. Not knowing what else might be missing, reinstalled the system with a recent snapshot.
To try to determine where the menu options begin not showing up, downloaded the final AntiX I.S.O. x64-full and made a bootable live-USB – no Panel options menu in that either. Tried different brand PCs with different graphics cards – no menu.
Could not find a settings configuration file for Rox-panel. Is it possible to adjust the transparency and panel dimensions through command-line?
_________________________
Azrielle-Thank you for your reply.
Being used to another file manager, the Rox-filer seemed to pale in comparison, however, after watching Dolphin’s videos, found it to be fast for transferring files and way more configurable than I was aware of. SpaceFM is also very good – especially the “File search” function.
I gave SpaceFM-IceWM a try and I agree – very nice.
In reply to: Do you Dare to Ask Why?
dolphin_oracle
Well, here’s the thing.
The question you posted over at MX Forums, while I imagine was completely innocent in your case, is very reminiscent of other trollish type posts that apparently had the goal of pitting one group against the other. The mods might have been overzealous in locking the thread, but its from past experience. The mods are not perfect.
We also go out of our way to not attempt to steal users from antiX. and vice versa in the case of antiX pulling users from MX. Rather we try to direct folks to what they want. Often folks come to antiX and immediately throw Xfce on it and wonder why it doesn’t work like MX. And vice versa with folks putting one of the window managers on MX and not getting the antiX experience.
Talking about MX/antiX vs. Ubuntu/puppy/whatever, that would not likely earn the mod’s ire. Or even asking about differences. But your post had the feel of asking folks to convince you to switch. And that we try not to do.
Moving on, if you think antiX and MX are very similar, well you’re right. We make no effort to hide the fact that MX is based on antiX (in our case, a heavily modified antiX-core as a matter of fact). The prime differences are in the desktop environment (xfce vs. the windows managers in antiX), the mx-tools (which isn’t as great a difference as it once was because many of those tools have also come to antiX :happy: ) and the package repositories (mx uses a tremendous amount of packages backported to debian stable and antiX operates a “nosystemd” repo of debian packages redone so they don’t depend on systemd). there are some other choices that affect memory footprint, but those are the big ones.
Incidentally, for those that may come to this thread later, the MX manual is in the menu (as MX-Manual) and does not require an internet connection to view (it’s an on-disk pdf). The installers on antiX and MX are also functionally identical, and once updated isos come out, they will actually be identical (as we just spent a lot of time re-unifying code), and yes, there are further improvements to the efi boots for certain hardware.
Topic: Acer C710 Chromebook
rokytnji
I thought I had a thread here already. Searched for it using the the search box on the top r/h side of the forum page. But it looks like the search terms Chromebook, Acer, C710, c710. Brought me up nothing in results.
Anyways. Here are the specs
harry@biker:~ $ sudo pinxi -U [sudo] password for harry: Starting pinxi self updater. Using curl as downloader. Currently running pinxi version number: 2.9.02 Current version patch number: 02-p Current version release date: 2018-03-20 Updating pinxi in /usr/local/bin using inxi-perl branch as download source... Successfully updated to inxi-perl branch version: 3.0.12 New inxi-perl branch version patch number: 09 New inxi-perl branch version release date: 2018-06-07 To run the new version, just start pinxi again. ---------------------------------------- Starting download of man page file now. Skipping man download because branch version is being used. harry@biker:~ $ pinxi -zv8 -r System: Host: biker Kernel: 4.15.9-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: IceWM 1.4.2 dm: slim Distro: antiX-17_x64-full Heather Heyer 24 October 2017 Machine: Type: Desktop System: Google product: Parrot v: 1.0 serial: <filter> Chassis: type: 3 serial: <filter> Mobo: Google model: Parrot v: 1.0 serial: <filter> BIOS: coreboot v: 4.0-6588-g4acd8ea-dirty date: 09/04/2014 Battery: ID-1: BATX charge: 30.3 Wh condition: 32.6/37.0 Wh (88%) volts: 17.3/14.8 model: SANYO AL12B32 type: Li-ion serial: <filter> status: Charging Memory: RAM Report: permissions: Unable to run dmidecode. Are you root? PCI Slots: Permissions: Unable to run dmidecode. Are you root? CPU: Topology: Dual Core model: Intel Celeron 1007U bits: 64 type: MCP arch: Ivy Bridge rev: 9 L2 cache: 2048 KiB bogomips: 5986 Speed: 1307 MHz min/max: 800/1500 MHz Core speeds (MHz): 1: 1239 2: 878 Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept erms est flexpriority fpu fsgsbase fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pebs pge pln pni popcnt pse pse36 pti pts rdtscp rep_good sep smep ss sse sse2 sse4_1 sse4_2 ssse3 syscall tm tm2 tpr_shadow tsc tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr Graphics: Card-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0156 Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 3.3 Mesa 13.0.6 compat-v: 3.0 direct render: Yes Audio: Card-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 Sound Server: ALSA v: k4.15.9-antix.1-amd64-smp Network: Card-1: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k v: kernel bus ID: 01:00.0 chip ID: 168c:0034 IF: wlan0 state: up mac: <filter> IP v4: <filter> scope: global broadcast: <filter> IP v6: <filter> scope: link Card-2: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe driver: tg3 v: 3.137 port: N/A bus ID: 02:00.0 chip ID: 14e4:16b5 IF: eth0 state: down mac: <filter> WAN IP: <filter> Drives: HDD Total Size: 44.64 GiB used: 25.83 GiB (57.9%) ID-1: /dev/mmcblk0 model: SD32G size: 29.72 GiB serial: <filter> scheme: MBR ID-2: /dev/sda vendor: SanDisk model: SSD U100 16GB size: 14.91 GiB speed: 3.0 Gb/s serial: <filter> rev: 6.14 scheme: MBR Message: No Optical or Floppy data was found. RAID: Message: No RAID data was found. Partition: ID-1: / size: 14.62 GiB used: 4.69 GiB (32.1%) fs: ext4 dev: /dev/sda1 label: rootantiX uuid: ea719934-26e3-4f25-af62-4f54438f456d ID-2: /media/E10C-A032 size: 29.71 GiB used: 21.14 GiB (71.1%) fs: vfat dev: /dev/mmcblk0p1 label: N/A uuid: E10C-A032 Unmounted: Message: No unmounted partitions found. USB: Hub: 1:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 Hub: 1:2 usb: 2.0 type: Intel Integrated Rate Matching Hub chip ID: 8087:0024 Device-1: Foxconn / Hon Hai bus ID: 1:3 usb: 1.1 type: Bluetooth chip ID: 0489:e04e Device-2: Chicony bus ID: 1:4 usb: 2.0 type: Video chip ID: 04f2:b336 Hub: 2:1 usb: 2.0 type: Full speed (or root) hub chip ID: 1d6b:0002 Hub: 2:2 usb: 2.0 type: Intel Integrated Rate Matching Hub chip ID: 8087:0024 Sensors: System Temperatures: cpu: 46.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://repo.antixlinux.com/stretch stretch main nosystemd 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: deb http://ftp.us.debian.org/debian/ stretch main contrib non-free 2: deb http://security.debian.org/ stretch/updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main No active apt repos in: /etc/apt/sources.list.d/onion.list No active apt repos in: /etc/apt/sources.list.d/various.list Processes: CPU top: 5 1: cpu: 82.2% command: firefox-esr pid: 3268 mem: 448.7 MiB (11.5%) 2: cpu: 2.4% command: xorg pid: 2236 mem: 57.3 MiB (1.4%) 3: cpu: 0.4% command: conky pid: 2606 mem: 10.5 MiB (0.2%) 4: cpu: 0.3% command: python pid: 2240 mem: 15.4 MiB (0.3%) 5: cpu: 0.3% command: lxterminal pid: 4921 mem: 19.9 MiB (0.5%) Memory top: 5 1: mem: 448.7 MiB (11.5%) command: firefox-esr pid: 3268 cpu: 82.2% 2: mem: 57.3 MiB (1.4%) command: xorg pid: 2236 cpu: 2.4% 3: mem: 36.4 MiB (0.9%) command: python pid: 2566 cpu: 0.1% 4: mem: 34.3 MiB (0.8%) command: spacefm pid: 2472 cpu: 0.0% 5: mem: 27.6 MiB (0.7%) command: volumeicon pid: 2547 cpu: 0.0% Info: Processes: 132 Uptime: 11m Memory: 3.79 GiB used: 585.2 MiB (15.1%) Init: SysVinit v: 2.88 runlevel: 5 default: 5 Compilers: gcc: 6.3.0 alt: 6 Shell: bash v: 4.4.12 running in: lxterminal pinxi: 3.0.12-9 harry@biker:~ $This was installed using John Lewis SeaBios. The whole thread with my involvement is over here
https://forum.mxlinux.org/viewtopic.php?f=104&t=42545&hilit=chromebooksI put this away in storage after my install. I’ve been mostly on my motorcycle shop Desktop system and IBM T430 since then.
But, I am getting it ready for my trips this summer coming up and it is going to be my saddlebag laptop. So I made it current.
harry@biker:~ $ su Password: root@biker:/home/harry# apt update Get:1 http://ftp.us.debian.org/debian stretch-updates InRelease [91.0 kB] Get:2 http://security.debian.org stretch/updates InRelease [94.3 kB] Ign:3 http://dl.google.com/linux/chrome/deb stable InRelease Get:4 http://dl.google.com/linux/chrome/deb stable Release [1,189 B] Ign:5 http://ftp.us.debian.org/debian stretch InRelease Hit:6 http://ftp.us.debian.org/debian stretch Release Get:7 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B] Get:8 http://ftp.us.debian.org/debian stretch-updates/main i386 Packages.diff/Index [4,180 B] Get:9 http://ftp.us.debian.org/debian stretch-updates/main amd64 Packages.diff/Index [4,180 B] Get:10 http://ftp.us.debian.org/debian stretch-updates/main Translation-en.diff/Index [2,704 B] Get:11 http://ftp.us.debian.org/debian stretch-updates/main i386 Packages 2018-03-28-2029.04.pdiff [4,113 B] Get:12 http://ftp.us.debian.org/debian stretch-updates/main i386 Packages 2018-03-31-1421.39.pdiff [336 B] Get:13 http://ftp.us.debian.org/debian stretch-updates/main i386 Packages 2018-05-05-2031.58.pdiff [329 B] Get:14 http://ftp.us.debian.org/debian stretch-updates/main amd64 Packages 2018-03-28-2029.04.pdiff [4,061 B] Get:15 http://ftp.us.debian.org/debian stretch-updates/main amd64 Packages 2018-03-31-1421.39.pdiff [336 B] Get:16 http://ftp.us.debian.org/debian stretch-updates/main amd64 Packages 2018-05-05-2031.58.pdiff [329 B] Get:13 http://ftp.us.debian.org/debian stretch-updates/main i386 Packages 2018-05-05-2031.58.pdiff [329 B] Get:16 http://ftp.us.debian.org/debian stretch-updates/main amd64 Packages 2018-05-05-2031.58.pdiff [329 B] Get:17 http://security.debian.org stretch/updates/main amd64 Packages [356 kB] Get:18 http://ftp.us.debian.org/debian stretch-updates/main Translation-en 2018-03-28-2029.04.pdiff [2,033 B] Get:18 http://ftp.us.debian.org/debian stretch-updates/main Translation-en 2018-03-28-2029.04.pdiff [2,033 B] Get:20 http://dl.google.com/linux/chrome/deb stable/main amd64 Packages [1,357 B] Get:21 http://security.debian.org stretch/updates/main i386 Packages [357 kB] Get:22 http://security.debian.org stretch/updates/main Translation-en [166 kB] Get:23 http://security.debian.org stretch/updates/contrib i386 Packages [1,776 B] Get:24 http://security.debian.org stretch/updates/contrib amd64 Packages [1,776 B] Get:25 http://repo.antixlinux.com/stretch stretch InRelease [20.7 kB] Get:26 http://repo.antixlinux.com/stretch stretch/main amd64 Packages [169 kB] Get:27 http://repo.antixlinux.com/stretch stretch/main i386 Packages [173 kB] Get:28 http://repo.antixlinux.com/stretch stretch/nosystemd i386 Packages [141 kB] Get:29 http://repo.antixlinux.com/stretch stretch/nosystemd amd64 Packages [141 kB] Fetched 1,739 kB in 6s (258 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 59 packages can be upgraded. Run 'apt list --upgradable' to see them. root@biker:/home/harry# apt list --upgradeable Listing... Done adobe-flash-properties-gtk/stretch 1:20180508.1-1mx17+1 amd64 [upgradable from: 1:20180313.1-1mx17+1] adobe-flashplugin/stretch 1:20180508.1-1mx17+1 amd64 [upgradable from: 1:20180313.1-1mx17+1] antix-installer/stretch 1.0.4.1 amd64 [upgradable from: 0.8.14] antix-libs/stretch,stretch 0.6.8 all [upgradable from: 0.6.7] cli-installer-antix/stretch,stretch 3.17 all [upgradable from: 3.16] control-centre-antix/stretch,stretch 0.6.9 all [upgradable from: 0.6.7] curl/stable 7.52.1-5+deb9u6 amd64 [upgradable from: 7.52.1-5+deb9u5] ds-mouse-antix/stretch,stretch 0.1.9 all [upgradable from: 0.1.7] faq-docs-antix/stretch,stretch 0.5.5 all [upgradable from: 0.5.4] firefox-esr/stable 52.8.0esr-1~deb9u1 amd64 [upgradable from: 52.7.2esr-1~deb9u1] fonts-opensymbol/stable,stable 2:102.7+LibO5.2.7-1+deb9u4 all [upgradable from: 2:102.7+LibO5.2.7-1+deb9u3] gir1.2-packagekitglib-1.0/stable 1.1.5-2+deb9u1 amd64 [upgradable from: 1.1.5-2] google-chrome-stable/stable 67.0.3396.79-1 amd64 [upgradable from: 65.0.3325.181-1] inxi-gui-antix/stretch,stretch 0.3.4 all [upgradable from: 0.3.3] irssi/stable 1.0.7-1~deb9u1 amd64 [upgradable from: 1.0.2-1+deb9u3] iso-snapshot-antix/stretch 0.2.8 amd64 [upgradable from: 0.2.7] iso-template-antix/stretch,stretch 17.6 all [upgradable from: 17.5] libcurl3/stable 7.52.1-5+deb9u6 amd64 [upgradable from: 7.52.1-5+deb9u5] libcurl3-gnutls/stable 7.52.1-5+deb9u6 amd64 [upgradable from: 7.52.1-5+deb9u5] libicu57/stable 57.1-6+deb9u2 amd64 [upgradable from: 57.1-6+deb9u1] libmad0/stable 0.15.1b-8+deb9u1 amd64 [upgradable from: 0.15.1b-8] libnss-myhostname/stable-updates 232-25+deb9u3 amd64 [upgradable from: 232-25+deb9u2] libpackagekit-glib2-18/stable 1.1.5-2+deb9u1 amd64 [upgradable from: 1.1.5-2] libperl5.24/stable 5.24.1-3+deb9u3 amd64 [upgradable from: 5.24.1-3+deb9u2] libreoffice-base-core/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-calc/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-common/stable,stable 1:5.2.7-1+deb9u4 all [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-core/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-draw/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-gtk/stable,stable 1:5.2.7-1+deb9u4 all [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-gtk2/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-impress/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-math/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-style-galaxy/stable,stable 1:5.2.7-1+deb9u4 all [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-systray/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libreoffice-writer/stable 1:5.2.7-1+deb9u4 amd64 [upgradable from: 1:5.2.7-1+deb9u3] libssl1.0.2/stable 1.0.2l-2+deb9u3 amd64 [upgradable from: 1.0.2l-2+deb9u2] libssl1.1/stable 1.1.0f-3+deb9u2 amd64 [upgradable from: 1.1.0f-3+deb9u1] libwavpack1/stable 5.0.0-2+deb9u2 amd64 [upgradable from: 5.0.0-2+deb9u1] live-usb-maker/stretch,stretch 0.3.3 all [upgradable from: 0.3.2] livestreamer/stretch,stretch 1.12.2+streamlink+0.11.0+dfsg-1.1 all [upgradable from: 1.12.2+streamlink+0.10.0+dfsg-1.1] mupdf/stable 1.9a+ds1-4+deb9u3 amd64 [upgradable from: 1.9a+ds1-4+deb9u2] openssl/stable 1.1.0f-3+deb9u2 amd64 [upgradable from: 1.1.0f-3+deb9u1] packageinstaller-pkglist/stretch,stretch 0.2.1 all [upgradable from: 0.2.0] perl/stable 5.24.1-3+deb9u3 amd64 [upgradable from: 5.24.1-3+deb9u2] perl-base/stable 5.24.1-3+deb9u3 amd64 [upgradable from: 5.24.1-3+deb9u2] perl-modules-5.24/stable,stable 5.24.1-3+deb9u3 all [upgradable from: 5.24.1-3+deb9u2] python3-streamlink/stretch,stretch 0.11.0+dfsg-1.1 all [upgradable from: 0.10.0+dfsg-1.1] remaster-antix/stretch,stretch 0.6.6 all [upgradable from: 0.6.5] repo-manager/stretch 0.1.8 amd64 [upgradable from: 0.1.3] smxi-inxi-antix/stretch,stretch 0.4.9 all [upgradable from: 0.4.2] streamlink/stretch,stretch 0.11.0+dfsg-1.1 all [upgradable from: 0.10.0+dfsg-1.1] tzdata/stable-updates,stable-updates 2018e-0+deb9u1 all [upgradable from: 2018c-0+deb9u1] uno-libs3/stable 5.2.7-1+deb9u4 amd64 [upgradable from: 5.2.7-1+deb9u3] ure/stable 5.2.7-1+deb9u4 amd64 [upgradable from: 5.2.7-1+deb9u3] user-management-antix/stretch,stretch 0.3.6 all [upgradable from: 0.3.4] wavpack/stable 5.0.0-2+deb9u2 amd64 [upgradable from: 5.0.0-2+deb9u1] wget/stable 1.18-5+deb9u2 amd64 [upgradable from: 1.18-5+deb9u1] xdg-utils/stable,stable 1.1.1-1+deb9u1 all [upgradable from: 1.1.1-1] root@biker:/home/harry# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libwxbase3.0-0v5 libwxgtk3.0-0v5 Use 'apt autoremove' to remove them. The following NEW packages will be installed: dict ecryptfs-utils grub-efi-ia32-bin installer-data-antix libappindicator3-1 libdbusmenu-gtk3-4 libecryptfs1 libindicator3-7 libmaa3 librecode0 libtspi1 recode The following packages will be upgraded: adobe-flash-properties-gtk adobe-flashplugin antix-installer antix-libs cli-installer-antix control-centre-antix curl ds-mouse-antix faq-docs-antix firefox-esr fonts-opensymbol gir1.2-packagekitglib-1.0 google-chrome-stable inxi-gui-antix irssi iso-snapshot-antix iso-template-antix libcurl3 libcurl3-gnutls libicu57 libmad0 libnss-myhostname libpackagekit-glib2-18 libperl5.24 libreoffice-base-core libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-gtk libreoffice-gtk2 libreoffice-impress libreoffice-math libreoffice-style-galaxy libreoffice-systray libreoffice-writer libssl1.0.2 libssl1.1 libwavpack1 live-usb-maker livestreamer mupdf openssl packageinstaller-pkglist perl perl-base perl-modules-5.24 python3-streamlink remaster-antix repo-manager smxi-inxi-antix streamlink tzdata uno-libs3 ure user-management-antix wavpack wget xdg-utils 59 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 226 MB of archives. After this operation, 7,590 kB of additional disk space will be used. Do you want to continue? [Y/n] y <snip> Writing Menu: openbox Writing Menu: jwm Writing Menu: fluxbox root@biker:/home/harry# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libwxbase3.0-0v5 libwxgtk3.0-0v5 Use 'apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@biker:/home/harry#Did some touchpad editing after helping another chromebook user on MX forums on his AntiX install. Helping him helped me. Just changing 3 finger right click to 2 finger right click. When you 1st install AntiX . The touchpad default after install is 3 fingers for right click copy and paste.
harry@biker:~ $ cd /etc/X11/xorg.conf.d harry@biker:/etc/X11/xorg.conf.d $ ls synaptic.conf.bk synaptics.conf harry@biker:/etc/X11/xorg.conf.d $ cat synaptics.conf Section "InputClass" Identifier "Touchpad" # required MatchIsTouchpad "yes" # required Driver "synaptics" # required Option "MinSpeed" "0.5" Option "MaxSpeed" "1.0" Option "AccelFactor" "0.075" Option "TapButton1" "1" Option "TapButton2" "3" # multitouch Option "TapButton3" "2" # multitouch Option "VertTwoFingerScroll" "1" # multitouch Option "HorizTwoFingerScroll" "1" # multitouch Option "VertEdgeScroll" "1" Option "CoastingSpeed" "8" Option "CornerCoasting" "1" Option "CircularScrolling" "1" Option "CircScrollTrigger" "7" Option "EdgeMotionUseAlways" "1" Option "LBCornerButton" "8" # browser "back" btn Option "RBCornerButton" "9" # browser "forward" btn EndSection harry@biker:/etc/X11/xorg.conf.dThe thread I helped out on is over here
https://forum.mxlinux.org/viewtopic.php?f=40&t=45427&hilit=chromebooksGotta give D.O. respects also for giving me ideas in that thread.
AntiX runs good on chromebooks to. If someone finds my thread I think I made already. I will merge it over here into hardware. 🙂
Happy Trails, Rok.Sometimes 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 problemsIn reply to: Wacom digitizer and antix boot – [solved]
stevesr0
Hi crestiah and @736b69646f6f:
Thanks for comments.
Additional information.
The Lenovo is a newer machine with a 1.83 GHz quad core celeron and 8 gig of RAM and has UEFI system firmware. The Fuitsu has a dual core intel processor (T7250) running at 2 GHz and has 4 gig of RAM and BIOS firmware.I have subsequently checked the times to boot with antix16 and the situation is different: BOTH computers boot in a reasonably short time and the Fujitsu boots FASTER than the Lenovo (24 vs 44 seconds). So, the move from 16 to 17 results in a small increase in boot time for the Lenovo (44 to 55 seconds) and a MASSIVE increase for the Fujitsu (24 to 319 seconds).
I have attached the bootcharts for antix16 to this reply.
My responses follow my quotes of your comments (” “) and are preceded by **.
crestiah 1:
“but basically im going to make an assumption or 2:
antix 16.1 probably uses uefi boot …antix 17 uefi boot possibly includes MpService protocol …if grub2 uefi is setup for multi thread delegation as its preferred first option then its probably trying to pipe multithread exec code through a single thread pipe, this could be done at the same speed, except the dual core processor would need to be at least twice the speed of the quad core.,ie quad core 1.83ghz dual core 4ghz…pipe multithread exec code through a single thread pipe” by this im thinking uefi(multithread)/gpt piped through syslinux bios/mbr.”
**I am ignorant about how the two bootloaders differ in their processes. I will seek to learn about this. Thanks for the references.
The motherboard hosts the hardware and firmware that runs BIOS or UEFI, not the disk drive. My Fujitsu doesn’t have UEFI, my Lenovo does. So the Fujitsu can’t boot via UEFI. I believe (from dolphin_oracle’s comment) that GRUB2 is used as the bootloader on a UEFI system even when running via LiveUSB.“i would be curious to know if the syslinux component is booting with boot=quiet (usually means to me blank screen)”
**I believe so; I didn’t change the default@736b69646f6f: (“@7”)and crestiah both indicate that the black screen is due to the boot running in quiet mode.
** I will change the option to a nonquiet one to view error messages flashing by. If that occurs too fast, I will check the /var/log file for the boot to see if the delay is explained.@736b69646f6f: “Possibly an updated firmware is available from lenovo which would remedy the slow booting.”
** The Fujitsu is slow booting with 17 and there is no update to the BIOS that I can find.Visit F2 bios setup and check whether you can manually choose device boot order, to “usb first, if present” or whatever option is available.
“Check /var/log/ or /var/log/live/ to see what error messages are being spewed to logfile during the 5 minute boot stall. Bootchart indicates “udev” is running for minutes. Struggling to find a driver? Bad/intermittent hardware errors?”
**I will look at those files.“Something in the bootchart about set-console-width…. and same shown at right side of bootchart.
It’s not a solid line like that process was running the whole time. It gets interrupted, suspended, while udev it doing something else???”
**I see a number of processes that look like they stopped. I was looking at avahi-daemon for the same reason. Not obvious to me how to pick out the major blocks to boot from the chart.“…typed a custom boot parameter,..”
**No.“If the boot device is liveusb, I don’t understand how grub2 enters the picture. AFAIK, syslinux provides the liveboot efi bootloader and I see nothing on the syslinux.org site mentioning ability to tweak the behavior for “threads”.”
**According to Dolphin_Oracle, syslinux is used on liveUSB running on BIOS system, GRUB2 on UEFI. Thus, booting from the same liveUSB on my two machines uses different bootloaders.“unetbootin…”
** Used rufus, running in Windows 10 to make all the liveUSBs.responses to crestiah:
“anyway the idea was to lock/jail root to the start of the iso/img file, so anything you did or saved stayed inside that img file. as well as bypass the dos memmory limits.”
** I don’t know how respond to that suggestion.
- This reply was modified 4 years, 11 months ago by stevesr0.
- This reply was modified 4 years, 11 months ago by rokytnji.
In reply to: Wacom digitizer and antix boot – [solved]
crestiah
@736b69646f6f maybe i miss-understood dolphin_oracle previous post and thought it was a 2 stage boot process sorry.
think the problem was with the fujitsu not the lenovo
think the fujitsu is 64bit capable but not recommended kind of like my lenovo g575 (1.3ghz procesor, 8gig ram, doesnt like systemd either at least as a desktop anyway).in terms of the 2 stage boot i was thinking of (passing the buck) syslinux wouldnt need to know what uefi is capable of only to launch it. (hence passing the buck to uefi/grub2 to take-over booting operations/capabilities)
kind of what an acquaintance at puppylinux would do with grub4dos went something like (cant remember the exact command write up but hopefully you get the drift)
Title whatever .iso /.img file
root= (hd0,0) \boot\whatever.iso
boot = \boot\grub\whatever.iso
initrd = \boot\initrd\whatever.isoanyway the idea was to lock/jail root to the start of the iso/img file, so anything you did or saved stayed inside that img file. as well as bypass the dos memmory limits.
- This reply was modified 4 years, 11 months ago by crestiah.
- This reply was modified 4 years, 11 months ago by crestiah. Reason: left out a word or two
- This reply was modified 4 years, 11 months ago by rokytnji.
In reply to: multiboot usb grub iso loop
I’d Be curious to know if this worked with hybrid iso’s
hybrid = cd/uefi booting
puppy linux had a great little multi-boot usb I just cant remember which puppy it came from or the particular script/package it was.
you could how ever drag n drop cd based iso’s, as many as you liked that fit on it.however for some reason anything with a hybrid style on it seemed to come up with a grub error code =60 “must be a continuous disk”
my pre-sumption is that it had something to do with either the uefi style booting or persistance ability just not sure which.
as an example i can run calculate 17.6 for i686 however i cant run devuan 2 ascii i386 from it.after re-examining the puppy multiboot usb found it was based on grub4dos with some auto menu.lst rebuild scripts. i cant read the rebuild scripts, however it probably needs a new entry to rebuild for grub2 start-up.
given the simple beauty of grub4dos i can understand why they used it.
- This reply was modified 4 years, 11 months ago by crestiah.
In reply to: Wacom digitizer and antix boot – [solved]
dolphin_oracle
syslinux would be used for live-boot on MBR systems, that is correct. the partition table doesn’t matter a whole lot as long as your system can boot from a gpt’s protected MBR.
I don’t know the exact history of why syslinux is used, but its used on a lot of distros for iso and live-USB boots. the antiX graphical boot menus were developed before grub2/UEFI came along, so those are kept where they work, and grub2 was tacked on later for UEFI boots.
Topic: CD/DVD work [xfburn]
roland
I’m using 64-bit Berta Caceres 16.3 which I keep updated, I get the following message when initialising Xfburn :-
Failed to initialize gstreamer transcoder: An error occurred setting gstreamer up for transcoding
(falling back to basic implementationHowever it appears to run well for the function I have used, to burn a bootable CD with an ISO file. Is this a problem and if so has anyone got a solution?
Also Xfburn appears to have no option to make a mirror-image copy of any CD or DVD. Is there such an application available, if so can anyone point me to it please?
BobC
I did find a site that explains how to install fonts for xscreensaver, and I actually did get one I had hoped would solve it installed and in use, but it was worse instead. Oh well, another 3 hours wasted on it. Reposting here in case that post goes away. Its close enough to be able to make it work if you had a font that worked…
https://freakarian.blogspot.com/2015/01/howto-install-xscreensaver-packages-on.html
HowTo Install the XScreensaver packages on Ubuntu
The XScreensaver packages are a series of fancy alternate screensavers that have a popular history. They are much more enjoyable than the boring default Ubuntu screensaver which is just… a black screen.
Unfortunately the XScreensavers package hasn’t really been updated in awhile and doesn’t integrate very nicely into the current flavours of Ubuntu without some manual tweaking, so that’s exactly what I’m going to cover right here.
Issues to deal with
This document will cover the following:
Installing the XScreensaver packages Configuring Ubuntu to use XScreensaver instead of the default gnome-screensaver
Configuring Ubuntu to lock the screen with the XScreensaver
Fixing the bad fonts issue in XScreensaver Setting a custom RSS feed for text-based XScreensaver packagesThese instructions have been tested on Ubuntu 12.04 (Precise Pangolin) and 14.04 (Trusty Tahr).
Making it happen
Open a terminal.
.
Uninstall the boring default Ubuntu screensaver with:$ sudo apt-get remove gnome-screensaverInstall the XScreensaver packages with:$ sudo apt-get install xscreensaver*
(note the asterisk on the end to install all xscreensaver packages)
.
Open the Dash (Ubuntu logo at the top-left of screen) and type in the word“start”. An icon will appear referring to “Startup Applications”. Click on it.
.
The window that appears shows which applications will be started when you login to your machine. Click on the “Add” button.
.
In the new window that appears, type “XScreensaver” into the Name field, then type in “xscreensaver -nosplash” into the Command field, then type in“Start the XScreensaver” into the Comment field.
Click on the “Add” button and then click on the Close button on the previous window.
.
That takes care of starting the XScreensaver, so now let’s fix the lock screen keyboard shortcut. Click on the Dash again and type in “keyboard” and then click on the “Keyboard” icon.
.
In the window that appears, click on the “Shortcuts” tab.
.
At the bottom of the left pane, click on “Custom Shortcuts”.
.
Click on the “+” button to add a new custom shortcut.
.
Give the shortcut a name, eg: “Enable the lockscreen”.
.
In the Command field, type in “xscreensaver-command -lock” and then click on the Apply button.
.
You will now see your new shortcut listed, but it doesn’t have a keyboard combo for it yet, so click on the word “Disabled” with your mouse and it will change to “New accelerator…”.
.
Now using your keyboard, press the key combo you’d like to use to lock your PC and start the XScreensaver. The default combo is CTRL+ALT+L but you can use any combo you like. If you do use CTRL+ALT+L you will be told that it’s already in use by the Gnome-Screensaver (which you uninstalled earlier, remember?), so just tell it to reassign it to your shortcut.
Close the keyboard settings window.
.
Now we need to sort out the fonts. The way XScreensaver looks for fonts is not like any other application. It needs to have a predefined list of available fonts, so we need to provide that list. We will get the “Ubuntu Font Family” (that comes with current releases of Ubuntu) enabled for use in XScreensaver, but you can apply this to any of the font folders on your machine.
.
In your terminal, type in the following:$ cd /usr/share/fonts/truetype/ubuntu-font-family $ sudo mkfontscale $ sudo mkfontdirRepeat the above for all the fonts you wish to add to your system, eg: substitute the path /usr/share/fonts/truetype/msttcorefonts for the Microsoft fonts from the ubuntu-restricted-packages meta-package or the ttf-mscorefonts-installer package.
.
Create a new file (or edit any existing file) as follows:$ sudo nano /usr/share/X11/xorg.conf.d/50-fonts.confType/paste in the following into your new file:Section “Files” FontPath “/usr/share/fonts/truetype/ubuntu-font-family” EndSection
Add as many FontPath entries you need between the Section/EndSectionblock for all the fonts you want available that you ran step 18 on.
.
Save your changes with CTRL+X, then “Y” and then Enter.
.
Now type in the following to enable the fonts now (or simply reboot):$ xset +fp /usr/share/fonts/truetype/ubuntu-font-family $ xset fp rehashRepeat the xset +fp <path> command as many times as required to add all the fonts you setup in Step 18 before the xset fp rehash command, or simply reboot to do them all in one hit from your X11 config file in step 21.
.
Now we’re ready to fix the fonts in XScreensaver. In this example we’re going to fix the fonts in the StarWars screensaver. What exactly is wrong with the fonts in the StarWars screensaver I hear you ask? Simply this:Yuck
Click on the Dash and then type in “screensaver”. An icon called “Screensaver”will appear below it. Click on it.
.
In the Screensaver Preferences window that appears, scroll down the list of available screensavers to find “StarWars”. Click on it to highlight it.
A preview of the screensaver will appear in the pane on the right. You will notice that the font in the screensaver looks awful as in the above image.
.
Click on the “Settings…” button. A new window will appear.
.
In the Settings window, click on the “Advanced>>” button at the bottom. The window content will change.
You will see the command line that starts the screensaver. Modify the line so that it looks like:starwars -root -font “-misc-ubuntu-bold-r-normal–180-0-0-0-p-0-iso8859-1”Click OK and repeat this modification to any other screensaver that uses a proportional font in its text, for example the FlipText screensaver.
.
Finally, let’s set a custom RSS feed for the screensavers that use text so that they show something useful. Click on the “Advanced” tab in the Screensaver Preferences window.
At the bottom-left in the “Text Manipulation” section, make sure “URL” is selected and change the URL text to your favourite RSS feed’s URL, for example ITNews’ RSS feed for “all content” ishttp://www.itnews.com.au/RSS/rss.ashxTest the StarWars screensaver now by clicking on the “Display Modes” tab and then select “StarWars” from the left pane to make it appear in the preview window. The time the fonts should look much nicer as follows:
Much nicer!
Now go through the list of screensavers, enabling and disabling those that you want to use. As you click each one, its preview will appear on the right.
.
Set the Blank After, Cycle After and Lock Screen After values accordingly, eg: 10 minutes a piece.
.
Close the Screensaver Preferences window and test locking your PC by pressing CTRL+ALT+L or whatever combo you set in step 15, and your screen should fade out and start displaying a random screensaver from your list of enabled screensavers. When you move the mouse or press a key, a login prompt should appear.
.
Pat yourself on the back. You are done.Choosing your own font to use instead of the Ubuntu Font Family fonts
Choosing your own font is simple. For each set of fonts that you processed in Step 18, type in the following, using the Ubuntu Font Family as this example:$ cat /usr/share/fonts/truetype/ubuntu-font-family/fonts.dirThis lists all the possible fonts available for that family. Copy to the clipboard the font description you wish to use.
.
Paste the description as the font argument in the command line of the screensaver you wish to modify.Note that you will need to adjust the font size/quality value in your command line because they are rendered as scaled bitmaps, not outlines. For example, in Step 32 we specify the font size to be“180” so that the fonts appear smooth and clean when scaled. If you don’t specify this, then the font will be generated into a bitmap using the smallest size before being scaled up in the screensaver, resulting in pixelated fonts.SPECIAL NOTE: Some screensavers require proportional fonts to be used and others require fixed-width fonts. If you try to use the wrong type of font, the screensaver will likely crash.
.
Choose the appropriate font type from the list of available fonts.
.
Preview your screensaver and make adjustments as required. If you’d like to test the screensaver directly without running up the Preferences tool, launch the screensaver binary in a terminal with the font description as an argument.For example, for the StarWars screensaver, you can run it in a window as follows:/usr/lib/xscreensaver/starwars -font “-misc-ubuntu-bold-r-normal–180-0-0-0-p-0-iso8859-1”Pat yourself on the back again. You are done.
Posted 9th January 2015 by Md Ainul Moin Noor ChandanIn reply to: antiX on Asus eee pc 701/4G
pbxxx
Hello,
Thanks for the feedback.
I had seen this same problem with the gui installer on the 17.1 full iso when installing to small drives using the “Auto-install using entire disk”, and it was reported by one other forum member previously. The installer has been updated and this bug has been fixed.
If you boot from your live-usb and enter into a terminal:
sudo apt update sudo apt install antix-installer cli-installer-antixIt didn’t quite work out. I booted from DVD and did that. I don’t remember the problem that occured, but I thought maybe it is because I’m running live from DVD. So I put it on a stick with the MX Linux tool (I have MX Linux on a Thinkpad X200), but to my surprise the persistence doesn’t seem to work properly. :-/ Anyhow, after trying to install antiX base on my eeePC, at startup, I would only have a blinking cursor in the top left corner. (That is, after the grub.)
So, I just figured my eeePC is cursed to never have a working DE. 😀 I just reinstalled antiX core and it is working great, aside the quirk of not having manpages, which is the only drawback. I really want to say again that the nice tools you put on core are really great!
So, I gave up on getting it working with a DE for now, because I don’t want to spend too much time trouble shooting it. Someday, I might consider installing a DE on top of core to see if this works, but it is just a big maybe for now.
If you select “Custom install on existing partitions” and select one of the btrfs compression options on the next screen, you can get antiX-full installed using less than 1.5GB of the eee’s 4GB of space.
I chose not to do this, because I fear that might slow down the system considerably.
On a side note, I noticed the cli-installer is much better for the eeePC because of the limited screen space available. With the gui installer, some windows don’t fit properly, which obscures buttons on the bottom of the window. This can be quite a bit awkward.
Thanks again for all your feedback! 🙂
In reply to: antiX on Asus eee pc 701/4G
rob
I tried to install antiX-base and antiX-full. With both I had the same problem, that, at the end of installation, the generation of logins wouldn’t work.
I had seen this same problem with the gui installer on the 17.1 full iso when installing to small drives using the “Auto-install using entire disk”, and it was reported by one other forum member previously. The installer has been updated and this bug has been fixed.
If you boot from your live-usb and enter into a terminal:
sudo apt update sudo apt install antix-installer cli-installer-antix(If not using persistence, you would need to do this each time you boot from your live-usb)
Using the default (ext4) installation, you can fit antix-base onto the 4GB eee-pc with plenty of space left over.
If you select “Custom install on existing partitions” and select one of the btrfs compression options on the next screen, you can get antiX-full installed using less than 1.5GB of the eee’s 4GB of space.
- This reply was modified 5 years ago by rob.
Myrddin
Recently, I had the opportunity to test both antiX 17.1 & MXLinux 17.1 AMD64 images on some unique & new hardware. I happened get my hands on a laptop with a Ryzen 7 2700U with Vega 10 embedded graphics (i.e., https://en.wikichip.org/wiki/amd/ryzen_7/2700u). Unfortunately, the X.org server could not start due to a lack of kernel support for my graphics.
The latest Refracta ISOs behaved better on my hardware and X11 started (i.e., a Devuan derivative). I installed and tested Refracta, updated the kernel to 4.15 backport and then compiled and installed Mesa3D 18.0.2. Liquorix latest kernel would not boot at all regardless of which boot parameters are set. After a few hours’ configuration, I had everything working as expected except backlight brightness & suspend/resume. It seems my display driver wasn’t detecting the monitor properly after resume. I suspect both issues were interrelated. lspci noticeably reported a lack of any Ryzen graphics even with linux 4.15. PCLinuxOS shared the same issues with Devuan. I soon became convinced newer hardware support was necessary.
PCLinuxOS latest, Devuan Ascii, and Fedora 28 will all boot properly on my hardware. XUbuntu 18.04, antiX 17.1, MXLinux 17.1, Calculate Linux 17.12.2, and Artix linux all fail to boot graphically. At least antiX and MXLinux could still boot to console. Ubuntu couldn’t make it that far with a series of dramatic kernel panic messages relating to my CPU.
After about 2 days’ testing time, I finally settled for Fedora 28. With the 4.16 kernel and Mesa 3d 18.0.1 drivers, everything was detected properly without additional configuration, suspend and resume worked flawlessly, and my backlight was finally working as acpi_video0 wasn’t the only driver available. Debian won’t have a stable 4.16 kernel for some time; for the time being, I’m staying with Fedora for the hardware support. I just wanted to post some of my testing results on this new hardware to draw some attention towards Ryzen mobile support on linux systems. I’ve lurked many years on these forums. Consider this my first contribution. Thank you anticapitalista, dolphin_oracle, fungalnet, fatmac, BobC, Xaver, greyowl, and the rest of the antiX/MX Linux Community. I appreciate your cumulative efforts over the years!
ramchip
*STOP PRESS* Thanks sleek, but I have discovered that the checksum of the downloaded iso does NOT match the one published on https://antixlinux.com/download/.
The first two bytes of my checksum are “be12” and the website gives “14f3”.
Ok, it’s my fault for not checking earlier!
So, I shall try the whole thing again and see if it the works as expected.
I find it amazing that the system was bootable given that the iso was a bad download.My apologies for reporting an apparently fictitious fault.
Thanks again to all who contributed in this forum.
Btw, Dave, that quote by the unknown author is very funny!
Brian Masinick
By request, this was asked by sleekmason to be moved to the second slot in the topic about making your own kernel.
I moved it to a different conversation so it can be easily seen.
Here are a list of some of the changes I have made over the course of time that may be interesting to others. Having a starting point for change may be useful to some.
Most everything I looked up online as well to see if there was relevance to my personal computer usage. Many items
here are simply not necessary for a laptop computer that is being used for common tasks, web surfing, email, usb, bluetooth, etc.
–
The smaller the kernel size, the faster the reads.
–
–
No way is this even close to everything. For instance, networking and drivers are machine dependent, while security, crypto, and the like are personal. There are over 4,300 options in the config file.
–
I don’t go over schedulers and such. There is a tutorial on changing to BFQ here: https://www.antixforum.com/forums/topic/how-to-use-the-bfq-io-scheduler/
–
–
After opening make menuconfig:
–
Under General Setup:
1. () Local version – append to kernel release – – – Add a 1 to this to get started;)
2. POSIX Message Queues – – – Disable unless using solaris.
3. uselib syscall – – – Disable – Glibc doesn’t use this.
4. Memory placement aware NUMA scheduler – – – Disable – soon deprecated.
5. Configure standard kernel features (expert). – – – Enable, then INSIDE:
Enable ELF core dumps – – – Disable
Enable PC-Speaker support – – – Disable – -unless you like beeps-
Load all symbols for debugging/ksymoops – – – Disable – debugging.
6. Enable SLUB debugging support – – – Disable – debugging.
7. SLUB per cpu partial cache. – – – EITHER – performance (N) on mine.
8. Profiling support – – – Disable – used by oprofile.
—
—
Enable loadable module support —>
1. Forced module loading – – – Disable – Really shouldn’t need this.
2. Forced module unloading – – – Disable – Really shouldn’t need this.
3. Module versioning support – – – Disable – for using modules from other kernels/systems.
—
—
Enable the block layer —>
1. Zoned block device support – – – Disable – Unless you have a ZAC or ZBC Storage device.
2. Block layer debugging information in debugfs – – – Disable – Debugging.
3. For interfacing with Opal enabled SEDs – – – Disable – Unless you know what this is.
4. Under Partition Types —>
Advanced partition selection – – – Disable – Unless using hard disks from another system.
—
—
Processor type and features —>
1. Enable MPS table. – – – If 64 bit, Disable, if not, read.
2. Linux guest support – – – Disable – Unless running under Hypervisor
3. Processor family (Generic-x86-64) – – – Change to yours! – cat /proc/cpuinfo to find out.
4. Supported processor vendors – – – Enable – and remove unused vendors.
5. Old AMD GART IOMMU support – – – Disable – Unless AMD Athlon64, Opteron, turion, etc. Then maybe.
6. IBM Calgary IOMMU support – – – Disable – Unless using IBM.
7. Maximum number of CPUs – – – Change to 4 or 8 Each adds 8 kb (256 x 8 = 2048).
8. CPU core priorities scheduler support – – – Enable – If using Intel – New support in latest kernel possible.
9. Reroute for broken boot IRQs – – – Disable – unless affected – read.
10. Enable support for 16-bit segments – – – Disable – Unless running Wine.
11. Numa Memory Allocation and Scheduler Support – – – READ – I disabled on mine.
12. Contiguous Memory Allocator – – – READ – I disabled on mine.
13. x86 architectural random number generator – – – Disable – How many do you need?
14. Supervisor Mode Access Prevention – – – Disable – Read – Security feature in newer intel.
15. EFI runtime service support – – – Disable – unless you have EFI support.
16. Timer frequency – – – Change to 1000HZ.
17. kexec system call – – – Disable – If you need this, you will know what it is:)
18. Build a relocatable kernel – – – Disable.
—
—
Power management and ACPI options —>
1. Enable workqueue power-efficient mode by default. – – Disable – Read.
—
—
Bus options (PCI etc.) —> Your on your own:)
—
—
Executable file formats / Emulations —> On your own:)
—
—
Networking support —>
1. Amateur Radio support – – – Disable – unless using amateur radio.
2. CAN bus subsystem support – – – Disable – Medical equipment type stuff.
3. Bluetooth subsystem support – – – Disable – Unless using Bluetooth.
—
—
Device Drivers —> On your own:)
—
—
Firmware Drivers —> On your own:)
—
—
File systems —>
1. Reiserfs support – – – Disable – Unless you formatted with Reiser.
2. JFS filesystem support. – – – Disable – Unless formatted with.
3. XFS filesystem support. – – – Disable – Unless formatted with.
4. GFS2 file system support. – – – Disable – Unless using a cluster.
5. OCFS2 file system support. – – – Disable – Unless using.
6. Btrfs assert support – – – Disable – Just this. Keep the file system.
7. NILFS2 file system support. – – – Disable – unless used.
8. F2FS filesystem support. – – – Disable – Read.
9. Direct Access (DAX) support. – – – Disable – unless needed.
10. Quota support – – – Disable – unless setting user limits.
11. Kernel automounter version 4 support│ – – – Disable – Distributed network stuff.
12. Overlay filesystem support. – – – Disable – Unless you know what this is.
13. Caches —>
Gather statistical information on local caching – – Disable – Debugging.
Gather latency information on local caching – – – Disable – Debugging.
Filesystem caching on files – – – Disable – READ FIRST.
—
—
Kernel hacking —>
1. printk and dmesg options —>
Show timing information on printks – – – Disable – unneeded for common tasks.
2. Compile-time checks and compiler options —>
Enable unused/obsolete exported symbols – – – Disable – unused.
3. Magic SysRq key – – – Disable – READ I don’t need this.
4. Kernel debugging – – – Disable – Debugging.
5. Tracers – – – Disable – unneeded.
6. (go back 2) Stack backtrace support – – – Disable – unneeded.
7. Runtime Testing – – – Disable – self tests.
8. Early printk via the EFI framebuffer – – – Disable – Debugging.
9. TOM Punit debug driver – – – Disable – Debugging.
—
—
Security options —> On your own:)
Cryptographic API —> On your own;)
Virtualization —> On your own:)
Library routines —> On your own:)Good luck! This is just a starting point, but should show noticeable improvements. Does for me anyway.
--
Brian Masinick
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
