Search Results for 'swap'

[Moderator BobC]

https://unix.stackexchange.com/questions/434177/why-cant-a-file-as-swap-be-used-for-hibernation-in-linux

https://askubuntu.com/questions/6769/hibernate-and-resume-from-a-swap-file

In the ubuntu one, look under the heading “Hibernate with Swap file using uswusp” and note that at the end they rebuild the initramfs, then test it by running s2disk

sudo update-initramfs -u

sudo s2disk

[Member wb8tyw]

I installed the uswsusp package on the desktop system.

I got save to swapfile working by following the instructions for setting up the swapfile at the https://wiki.archlinux.org/index.php/Uswsusp#Standalone

I am using /swapfile instead of a swap partition.

Running sudo dpkg-reconfigure uswsusp and answering the questions got the /etc/uswsusp.conf created.

The sudo s2both saves to disk.

But something is still missing. Pulling the power cord on the desktop in that suspended state still results in a cold boot when power is re-applied.

I do not know how to check how the initramfs built was built.

The filenames in the archlinux.org link do not work on anti-x linux.

It appears that there needs to be something in the initramfs that can restore the image saved in the swapfile.

[Anonymous]

Do the affected systems have sufficient swap space available?

uswsusp
might be useful (offhand I’m unsure whether it is pre-installed) (ummmm, provided by “pm-utils” package)
https://wiki.archlinux.org/index.php/Uswsusp#Standalone

[Moderator BobC]

Hibernation won’t work with all PC’s and it can be tricky to get it all configured correctly even on machines that it works on. If you aren’t a Linux guru, the best bet is to install a power manager. XFCE Power Manager would be my first choice. I hope you created a swap partition at least 1.5 times the size of memory. If not, you either need to reinstall or add one, or use a swap file. I have added one before, but its a lot of work. I have one machine I’ve never been able to get it to work on. I can get it to hibernate, but never can get it to come back up.

Don’t try any systemd related methods on antiX. That will fail for sure.

There is also a manual way to do it. Obviously you need to be careful testing this… Try this from a terminal, suspend first, and see if you can get it to come back up. Then try hibernate. I have never had much luck with the hybrid one.

sudo /usr/bin/pm-suspend

sudo /usr/bin/pm-hibernate

PS: on this machine I was able to suspend and resume, but if the battery dies, it will be lost. I was not able to hibernate. It started trying to save the image but hung up while trying to save it. I’ve found some machines need a different kernel, or programs. It hit or miss, and there are places that explain how to diagnose it, but sometimes I just haven’t been able to get it to work. To survive a power down situation, you need to hibernate the system before the power is gone. The hybrid solution creates the hibernation data, but then suspends. If the power dies, then you resume from the hibernated drive, and if not, you wake up from the suspended system. Many times things like Wifi and graphics have problems.

• This reply was modified 2 years, 4 months ago by BobC.

Hello!

I’ve been using antiX since the release of 19.3, mainly to power an old Asus EEEpc 1015bx netbook, anno 2012. Swapped out the HDD with a SSD and its better than new. I was impressed by how efficient antiX is as an OS and now use it on my main desktop as well, tripple-booted with Win10 (only used with a few specialty programs required for work) and Mint xfce (my gateway to Linux back in 2014). Since installing antiX I rarely boot into Mint.

Anyways, just wanted to pay tribute to the devs! Great work! Keep it up!

[Anonymous]

discrepancy(ies):

https://linuxinsider.com/story/antix-linux-not-pretty-but-highly-functional-86942.html
You need at least 256 MB RAM, and the installer needs a minimum 2.7 GB hard disk size.

vs

http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/index.html#_system_requirements

So what are the minimum and suggested requirements to run antiX?
antiX should run on most computers, ranging from 192MB old PII systems with pre-configured 128MB swap to the latest powerful boxes.
antiX-core and antiX-net will run with 128MB RAM plus swap, but don’t expect miracles!
192MB RAM is the recommended minimum for antiX. 256MB RAM and above is preferred especially for antiX-full.
antiX-full needs a 5GB minimum hard disk size. antiX-base needs 3GB and antiX-core needs 1GB. antiX-net needs 0.7GB.

vs

https://distrowatch.com/table.php?distribution=antix

…should run on most computers, ranging from 256 MB old PIII systems with pre-configured swap to the latest powerful boxes. 256 MB RAM is recommended minimum for antiX. The installer needs minimum 2.7 GB hard disk size.

vs

https://gitlab.com/antiX-Linux/cli-installer-antix/-/blob/master/cli-installer

echo $"Requirements for minimum installation:"
echo $"antiX-full: hard-disk 5.0GB  RAM 64MB"
echo $"antiX-base: hard-disk 3.5GB  RAM 48MB"
echo $"antiX-core: hard-disk 1.0GB  RAM 48MB"
echo $"antiX-net:  hard-disk 0.7GB  RAM 48MB"

vs

https://gitlab.com/antiX-Linux/gazelle-installer-data-antix/-/blob/master/gazelle-installer-data/installer.conf

default smallest size to search for installable partitions
MIN_ROOT_DRIVE_SIZE=4000

#Variables that affect installer help text, but may vary by iso
MIN_INSTALL_SIZE=3.5 GB
PREFERRED_MIN_INSTALL_SIZE=5 GB

[Anonymous]

sudo touch /usr/local/share/excludes/iso-snapshot-exclude.list

ouch.
OMG, no that wouldn’t lead to a happy ending…

There are things that need to be excluded from the snapshot if you want the final iso to boot on other systems.

… and, in the absence of a suitable exclusions list, the operation would never reach completion, period. Instead, endless recursion would result, attempting to read (and create squashed copies of) “virtual” files from the vfs directories, e.g. /sys/ and /proc/ …ultimately leading to “kernel panic” once the recursive process has fully exhaused all available (memory, swap) resources.

[Member rayluo]

OK, OK, I understand that you were helping. And I appreciate it! I was merely trying to find a way to make these interaction more efficient, simply because running some command line locally in our computer would take seconds per command, and then we could read the output, and fire up another command within half a minute, …, rinse and repeat. That sounds faster than each iteration would take hours of asynchronized waiting time in forum, with some iteration would even be used to rule out other possibility. (In particular, my first post contained 2 “cat” output, the “cat hello.sh” contains only one line, hinting that I did not omit anything i.e. that script contains no shebang, in contrary to the “cat /etc/fstab” which I used “…” to omit some lines.)

Anonymous wrote:

Is this a correct summary assessment?
When interacting with the Live-usb-storage mountpoint, can exec.
When interacting with the Live-usb-storage directory, pathed under /live/boot-dev mountpoint, cannot exec.

Perhaps it is not about mountpoint vs directory. Let me show you the following uncensored output, plus some “<–” comments.

demo@antix1:~ (master)$ mount | grep -i live-usb
/dev/sda7 on /root/Live-usb-storage type ext4 (rw,noatime,data=ordered)        <-- sda7 is the frugal partition, but it is not mount on /root/Live-usb-storage
/dev/sda7 on /home/demo/Live-usb-storage type ext4 (rw,noatime,data=ordered)   <-- sda7 is the frugal partition, and yes, this is its mount point
/dev/sdb1 on /media/Live-usb type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered)  <-- sdb1 is the main partition on my Live USB, turns out it is mounted as noexec
demo@antix1:~ (master)$ cp /media/Live-usb/Live-usb-storage/demo/hello.sh ~/Live-usb-storage/   <-- Again, this is that test script containing only one line "echo hello"
demo@antix1:~ (master)$ ~/Live-usb-storage/hello.sh 
hello
demo@antix1:~ (master)$ /media/Live-usb/Live-usb-storage/demo/hello.sh
-bash: /media/Live-usb/Live-usb-storage/demo/hello.sh: Permission denied

Anonymous wrote:

you said: I don’t wanna workaround.
In response (perhaps wrongly) I attempted to lead you through the output of a series of commands which would bring you to the conclusion that a remount may not be a workaround, but a necessity.

In my first post, I was saying I already know the workaround and that’s fine, but I’m trying to understand whether it was controlled by a hidden setting in somewhere. If there is no such “flip switch”, then so be it.

Anonymous wrote:

All the antiX systems I locally support and maintain have been “diskless” since back around 2019. Any internal drives, if present, are typically uncabled.

Perhaps we can spend these forum interaction on more fruitful topics, such as how you manage your diskless system. 🙂 Feel free to start a new thread to share your tips and tricks on using diskless system. Do your machines have plenty of RAM? I used to do diskless, they worked well until you reach a point that your system is out of memory, and then it would typically halt without any prior warning. So, nowadays I tend to still hook up a small hard drive, to be used as a swap, if nothing else.

[Anonymous]

Is it a Rox pinboard?

It is “xlunch”
http://xlunch.org/
https://www.youtube.com/watch?v=5-eltc1_HKU
https://github.com/Tomas-M/xlunch

recently discussed it here in antixforum when someone asked about limiting access to wm desktop menu,
toward creating a curated, kiosk-like environment for a 6yr old child
https://www.antixforum.com/forums/topic/antix-19-3-i386-base/#post-46788

usage: xlunch [options]
xlunch is a program launcher/option selector similar to dmenu or rofi.
By default it launches in full-screen mode and terminates after a selection is made,
it is also possible to close xlunch by pressing Esc or the right mouse button.
Some options changes this behaviour, the most notable being the desktop mode switch:
    -d, --desktop                      Desktop mode, always keep the launcher at
                                       background(behind other windows), and ignore ESC
                                       and right mouse click. Combined with --dontquit
                                       xlunch never exits (behaviour of --desktop from
                                       previous versions).
Functional options:
    --config [file]                    Reads configuration options from a file. The
                                       options are the same as the long options
                                       specified here. Options that take a value must
                                       have a colon (':') before it's option. It is
                                       also possible to pass the entries along with the
                                       configuration file by using "entries:"
                                       followed by a newline and the regular contents
                                       of an input file
    -v, --version                      Returns the version of xlunch
    -H, --help                         Shows this help message
    --name                             POSIX-esque way to specify the first part of
                                       WM_CLASS (default: environment variable 
                                       RESOURCE_NAME or argv[0])
    -N, --notitle                      Do not display any titles under/around icons
    -n, --noprompt                     Hides the prompt, only allowing selection
                                       by icon
    -o, --outputonly                   Do not run the selected entry, only output it
                                       to stdout
    -S, --selectonly                   Only allow an actual entry and not free-typed
                                       commands. Nice for scripting.
    -i, --input [file]                 File to read entries from, defaults to stdin
                                       if data is available otherwise it reads from
                                       $HOME/.config/xlunch/entries.dsv or
                                       /etc/xlunch/entries.dsv
    -m, --multiple                     Allow multiple instances running
    -t, --voidclickterminate           Clicking anywhere that's not an entry terminates
                                       xlunch, practical for touch screens.
    --focuslostterminate               When the window loses focus xlunch will quit,
                                       practical for menus
    -q, --dontquit                     When an option is selected, don't close xlunch.
                                       Combined with --desktop xlunch
                                       never exits (behaviour of --desktop from
                                       previous versions).
    -R, --reverse                      All entries in xlunch as reversly ordered.
    -W, --windowed                     Start in windowed mode
    --title                            Specifies the title to put on the window when
                                       running in windowed mode.
    -M, --clearmemory                  Set the memory of each entry to null before
                                       exiting. Used for passing sensitive information
                                       through xlunch.
    -U, --shortcuts [shortcuts]        Sets shortcuts for the entries, 'shortcuts' is a
                                       string of UTF-8 characters to use sequentially
                                       for the entries provided.
    -A, --button [button]              Adds a button to the window. The argument
                                        "button" is a semicolon-separated list on the
                                       form "<icon>;<highlight icon>;<x>,<y>;<command>"
                                       If x or y is negative positioning is relative
                                       to the other side of the screen.
    --noscroll                         Disable scroll in xlunch. Ignore entries
                                       that can't fit the screen.

Multi monitor setup: xlunch cannot detect your output monitors, it sees your monitors
as a big single screen. You can customize this manually by setting windowed mode and
providing the top/left coordinates and width/height of your monitor screen which
effectively positions xlunch on the desired monitor. Use the following options:
    -x, --xposition                 The x coordinate of the launcher window
                                       Use negative number to align from right
    -y, --yposition                 The y coordinate of the launcher window
                                       Use negative number to align from bottom
    -w, --width                     The width of the launcher window
    -h, --height                    The height of the launcher window

Style options:
    -p, --prompt [text]                The prompt asking for input (default: "Run: ")
    -f, --font [name]                  Font name including size after slash (default:
                                       "OpenSans-Regular/10" and  "DejaVuSans/10")
    -F, --promptfont [name]            Font to use for the prompt
                                       (default: same as --font)
    -G, --rootwindowbackground         Use root windows background image
    -g, --background [file]            Image to set as background (jpg/png). NOTE: the
                                       background color will be drawn over this image
                                       so use a fully transparent background color if
                                       the image should be drawn as-is.
    --bgfill                           Makes the background keep aspect ratio
                                       while stretching
    -L, --highlight [file]             Image set as highlighting under selected icon
                                       (jpg/png)
    -I, --iconpadding               Padding around icons (default: 10)
        --iconvpadding              Vertical padding around icons (default: same as
                                       iconpadding)
    -T, --textpadding               Padding around entry titles (default: 10)
    -c, --columns                   Number of columns to show (without this the max
                                       amount possible is used)
    -r, --rows                      Numbers of rows to show (without this the max
                                       amount possible is used)
    -b, --border                    Size of the border around the icons and prompt
                                       (default: 1/10th of screen width)
                                       This can also be set to 'auto' in order to
                                       automatically calculate a border taking into
                                       account the margin settings and the
                                       configured columns and rows. You can also specify
                                       border in terms of percentage of screen width by
                                       appending a % sign to the value
    -B, --sideborder                Size of the border on the sides, if this is used
                                       --border will be only top and bottom. Similarily
                                       this can be set to 'auto' or a percentage but
                                       then only side borders are calculated
    --borderratio                   The ratio of the border to apply above the
                                       content. 0 is no top border, only bottom. 100 is
                                       only top border, no bottom
    --sideborderratio               The ratio of the side border to apply to the
                                       left of the content. 0 is no left border, only
                                       right. 100 is only left border, no right
    -C, --center                       Center entries when there are fewer entries on a
                                       row than the maximum
    -P, --promptspacing             Distance between the prompt and the icons
                                       (default: 48)
    -s, --iconsize                  Size of the icons (default: 48)
    -a, --textafter                    Draw the title to the right of the icon instead
                                       of below, this option automatically sets
                                       --columns to 1 but this can be overridden.
    -O, --textotherside                Draw the text on the other side of the icon from
                                       where it is normally drawn.
    -u, --upsidedown                   Draw the prompt on the bottom and have icons
                                       sort from bottom to top.
    -X, --paddingswap                  Icon padding and text padding swaps order
                                       around text.
    -l, --leastmargin               Adds a margin to the calculation of
                                       application sizes.
    -V, --leastvmargin              Adds a vertical margin to the calculation of
                                       application sizes.
    -e, --hidemissing                  Hide entries with missing or broken icon images
    --tc, --textcolor           Color to use for the text on the format rrggbbaa
                                       (default: ffffffff)
    --pc, --promptcolor         Color to use for the prompt text
                                       (default: ffffffff)
    --bc, --backgroundcolor     Color to use for the background
                                       (default: 2e3440ff) NOTE: transparent background
                                       color requires a compositor
    --sc, --shadowcolor         Color to use for text shadows (default: 00000030)
    --hc, --highlightcolor      Color to use for the highlight box
                                       (default: ffffff32)
    --scrollbarcolor            Color to use for the scrollbar
                                       (default: ffffff3c)
    --scrollindicatorcolor      Color to use for the scrollbar indicator
                                       (default: ffffff70)

[Member ab4711]

Hello Xecure,
I can’t find the point where I can set the refresh rate in the Set Screen Resolution menu.
I installed the system in safe mode.
I start the system normally.

$ inxi -Fxz
System:
  Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc 
  v: 8.3.0 Desktop: IceWM 1.9.2 
  Distro: antiX-19-legacy-bet2_386-base Lazarus 29 November 2020 
  base: Debian GNU/Linux 10 (buster) 
Machine:
  Type: Desktop System: FUJITSU SIEMENS product: Amilo A1640 v: 0.01 
  serial: <filter> 
  Mobo: Uniwill model: 255KI / 259KI Series v: 0.01 serial: <filter> 
  BIOS: American Megatrends v: 080011 date: 12/14/2004 
Battery:
  ID-1: BAT0 charge: 67.9 Wh condition: 67.9/78.5 Wh (86%) model: 255/259 
  status: Full 
CPU:
  Topology: Single Core model: Mobile AMD Sempron 3000+ bits: 32 type: UP 
  arch: K8 L2 cache: 128 KiB 
  flags: nx pae sse sse2 bogomips: 3192 
  Speed: 1600 MHz min/max: 800/1800 MHz Core speed (MHz): 1: 1600 
Graphics:
  Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 
  662/761Gx PCIE VGA Display Adapter 
  vendor: Fujitsu Solutions driver: N/A bus ID: 01:00.0 
  Display: x11 server: X.Org 1.16.4 driver: vesa resolution: 1024x768~61Hz 
  OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 
  direct render: Yes 
Audio:
  Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound 
  vendor: Fujitsu Solutions driver: snd_intel8x0 v: kernel bus ID: 00:02.7 
  Sound Server: ALSA v: k4.4.240-antix.2-486-smp 
Network:
  Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet 
  vendor: Fujitsu Solutions driver: sis900 v: kernel port: d800 
  bus ID: 00:04.0 
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 111.79 GiB used: 5.14 GiB (4.6%) 
  ID-1: /dev/sda vendor: Fujitsu model: MHV2120AH size: 111.79 GiB 
Partition:
  ID-1: / size: 40.12 GiB used: 5.14 GiB (12.8%) fs: ext4 dev: /dev/sda2 
  ID-2: swap-1 size: 1.84 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 75.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 120 Uptime: 3m Memory: 876.2 MiB used: 281.0 MiB (32.1%) 
  Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 
  inxi: 3.0.36

• This reply was modified 2 years, 4 months ago by rokytnji.

Here are my notes on how to clear most of the memory buffer/cache and how to clear swap memory (run these commands as root):
Clear page memory –
sync; echo 1 > /proc/sys/vm/drop_caches

Not recommended – can cause data loss – clear dentries (data structure that represents a directory) and inodes (data structure that represents a file) –
sync; echo 2 > /proc/sys/vm/drop_caches

Clear swap –
swapoff -a && swapon -a

Anyone have any thoughts? I’ve used commands #1 and #3 for a couple years, haven’t had any trouble, and occasionally use command #2. I’d like to know if anyone has a thought on how these commands could be improved, or if you feel they are incorrect or if they are simply a waste of time for any reason.

[Member Xecure]

First make sure there is enough RAM.
If you are using standard dynamic persistence, the changes (persistence file) are being saved in RAM. If apart from that you are loading the whole OS in RAM, you may be find tha, as some point your system will be even slower because RAM is full and it is using swap.

If you are sure there is enough RAM, there are 2 different ways to add the toram option.

1. From the Live Boot screen.
A.If running in Legacy Bios, the screen will look like this:

The F4 menu will give you the toram option. Once selected, you can save the boot parameters with the F8 “Save” menu.
B. If running on UEFI systems, you need to write the boot parameter inside your Custom boot option. Move the selection to the Custom menu entry, hit the ‘e’ key and edit the line containing the boot parameters (third line). You need to add toram and menus=s
It could look similar to:
linux /antiX/vmlinuz quiet splash=v persist_root toram menus=s
When ready, hit F10 key and it will ask you if you want to save the boot changes. Select the “yes” option.

2. From inside the running antiX system.
Depending on if UEFI or Legacy Bios boot, you need to edit (with root privileges)
Legacy Bios: /live/boot-dev/boot/isolinux/isolinux.cfg and /live/boot-dev/boot/syslinux/syslinux.cfg (and add the boot parameters there)
UEFI: /live/boot-dev/boot/grub/grub.cfg (and add the boot parameters to the Custom entry)

More info in:
https://antixlinuxfan.miraheze.org/wiki/AntiX_Live_System
https://antixlinuxfan.miraheze.org/wiki/Boot_Parameters

• This reply was modified 2 years, 5 months ago by Xecure. Reason: correcting EUFI keys

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member Dzhigit]

ah yes, I forgot

$ inxi -Fxz
System:    Host: DzhigitPC Kernel: 5.9.0-13.2-liquorix-amd64 x86_64 bits: 64 compiler: N/A Desktop: JWM 2.3.7 
           Distro: antiX-19.2.1-runit_x64-base Hannie Schaft 29 March 2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop Mobo: Micro-Star model: B450M BAZOOKA V2 (MS-7A38) v: 5.0 serial: <filter> UEFI: American Megatrends 
           v: P.B0 date: 06/10/2020 
CPU:       Topology: 6-Core model: AMD Ryzen 5 3600X bits: 64 type: MT MCP arch: Zen L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 91201 
           Speed: 4086 MHz min/max: 2200/3800 MHz Core speeds (MHz): 1: 4086 2: 4138 3: 4108 4: 4129 5: 4124 6: 3983 7: 4115 
           8: 4095 9: 4117 10: 4136 11: 4223 12: 4019 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480] vendor: Tul driver: amdgpu v: kernel 
           bus ID: 29:00.0 
           Display: server: X.Org 1.20.4 driver: amdgpu resolution: 1920x1080~60Hz 
           OpenGL: renderer: Radeon RX 580 Series (POLARIS10 DRM 3.39.0 5.9.0-13.2-liquorix-amd64 LLVM 7.0.1) 
           v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Tul driver: snd_hda_intel v: kernel 
           bus ID: 29:00.1 
           Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus ID: 2b:00.4 
           Device-3: C-Media type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-8:2 
           Sound Server: ALSA v: k5.9.0-13.2-liquorix-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
           port: f000 bus ID: 25:00.0 
           IF: eth0 state: down mac: <filter> 
           Device-2: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter driver: wl v: kernel port: f000 
           bus ID: 27:00.0 
           IF: wlan0 state: up mac: <filter> 
Drives:    Local Storage: total: 931.52 GiB used: 106.28 GiB (11.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB 
           ID-2: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 GiB 
Partition: ID-1: / size: 455.21 GiB used: 106.28 GiB (23.3%) fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 53.6 C mobo: 33.0 C gpu: amdgpu temp: 26 C 
           Fan Speeds (RPM): fan-1: 0 fan-2: 1086 fan-3: 1664 fan-4: 940 fan-5: 0 gpu: amdgpu fan: 1141 
           Voltages: 12v: N/A 5v: N/A 3.3v: 3.38 vbat: 3.34 
Info:      Processes: 301 Uptime: 5h 24m Memory: 15.65 GiB used: 2.62 GiB (16.7%) Init: runit runlevel: 2 Compilers: 
           gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 

I think it is space jwm because I apt-get purged rox.

I installed antiX 19.3 (full–32 bit) on my Dell Latitude D610 laptop. It appears to be working fine.
The internet works well with the ethernet cable.
However, I cannot get the wireless to work with neither Connman nor Ceni (it previously automatically worked with antiX 17).
When I do the switch to Connman, I get a message that “no WLAN entries found in etc/network/interfaces”
Connmand gui only show the wired ethernet–no wireless.
rfkill list shows “wireless LAN is hard blocked”

Below is inxi -F:

user@antix2:~
$ inxi -F
System:
Host: antix2 Kernel: 4.9.240-antix.1-486-smp i686 bits: 32
Desktop: IceWM 1.9.2
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
Machine:
Type: Portable System: Dell product: Latitude D610 v: N/A
serial: <root required>
Mobo: Dell model: 0D4571 serial: <root required> BIOS: Dell v: A06
date: 10/02/2005
Battery:
ID-1: BAT0 charge: 53.3 Wh condition: 52.5/53.3 Wh (99%)
CPU:
Topology: Single Core model: Intel Pentium M bits: 32 type: MCP
L2 cache: 2048 KiB
Speed: 800 MHz min/max: 800/1867 MHz Core speed (MHz): 1: 1067
Graphics:
Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics driver: i915
v: kernel
Display: x11 server: X.Org 1.20.4 driver: intel
unloaded: fbdev,modesetting,vesa resolution: 1024×768~60Hz
OpenGL: renderer: Mesa DRI Intel 915GM x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
Audio:
Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio driver: snd_intel8x0
Sound Server: ALSA v: k4.9.240-antix.1-486-smp
Network:
Device-1: Broadcom Limited NetXtreme BCM5751 Gigabit Ethernet PCI Express
driver: tg3
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:14:22:d8:99:f8
Device-2: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200
IF: eth1 state: down mac: 00:16:6f:46:d6:28
Drives:
Local Storage: total: 37.26 GiB used: 4.13 GiB (11.1%)
ID-1: /dev/sda vendor: Samsung model: MP0402H size: 37.26 GiB
Partition:
ID-1: / size: 34.43 GiB used: 4.13 GiB (12.0%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2387
Info:
Processes: 141 Uptime: 14m Memory: 1.96 GiB used: 315.9 MiB (15.7%)
Shell: bash inxi: 3.0.36
user@antix2:~
$

• This topic was modified 2 years, 5 months ago by greyowl.
• This topic was modified 2 years, 5 months ago by greyowl.
• This topic was modified 2 years, 5 months ago by greyowl.

Dell Latitude D620 laptop with antiX 22 (64 bit)

[Member ArchiMark]

Thanks, Xecure and caprea for your help!

Tried running roxterm after following directions, it shows up in menu, but does not open.

I tried opening it from terminal, but no go, as before…..

I did get results from running inxi command as follows:

$ inxi -Fxz | tee inxi.txt

System:
Host: marks-C1MZX Kernel: 4.9.235-antix.1-486-smp i586 bits: 32 compiler: gcc
v: 8.3.0 Desktop: IceWM 1.8.3
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)

Machine:
Type: Laptop System: Sony product: PCG-C1MZX(J) v: 01 serial: <filter>
Mobo: N/A model: N/A serial: N/A BIOS: Phoenix v: R0246E0 date: 08/07/02

CPU:
Topology: Single Core model: Transmeta Crusoe TM5800 bits: 32 type: UP arch: N/A
L2 cache: 512 KiB
flags: N/A bogomips: 1852
Speed: 533 MHz min/max: 300/933 MHz Core speed (MHz): 1: 933

Graphics:
Device-1: AMD RV100/M6 [Rage/Radeon Mobility Series] vendor: Sony driver: radeon
v: kernel bus ID: 00:0c.0
Display: x11 server: X.Org 1.20.4 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1280×600~60Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 direct render: Yes

Audio:
Device-1: ULi M5451 PCI AC-Link Audio vendor: Sony driver: snd_ali5451 v: kernel
bus ID: 00:06.0
Device-2: Fujitsu Limited. vendor: Sony driver: N/A bus ID: 00:0a.0
Sound Server: ALSA v: k4.9.235-antix.1-486-smp

Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter vendor: Sony
driver: 8139too v: 0.9.28 port: 2400 bus ID: 00:0b.0
IF: eth0 state: down mac: <filter>
Device-2: TP-Link TL WN823N RTL8192EU type: USB driver: rtl8xxxu bus ID: 2-1:2
IF: wlan0 state: up mac: <filter>

Drives:
Local Storage: total: 55.89 GiB used: 3.78 GiB (6.8%)
ID-1: /dev/sda vendor: Hitachi model: DK23EA-60 size: 55.89 GiB

Partition:
ID-1: / size: 52.76 GiB used: 3.78 GiB (7.2%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 2.7 MiB (0.1%) fs: swap dev: /dev/sda2

Sensors:
Message: No sensors data was found. Is sensors configured?

Info:
Processes: 140 Uptime: 29m Memory: 343.4 MiB used: 219.6 MiB (63.9%) Init: SysVinit
runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36