Search Results for 'swap'

[Moderator Brian Masinick]

The point I am making is that when you have enough memory, swapping activity does not take place because software remains in memory once loaded.

If memory is insufficient to load all programs and keep them in memory, that is when other I/O activity takes place. Perhaps toram performs more than simply loading resources completely into memory. From my perspective it is most important when available memory is less than the resources needed by the system programs and the applications being used. That may be overly simplistic from a highly technical point of view, but from a practical standpoint reducing I/O activity is the most noticeable activity when resources are limited. The toram feature cannot load all images into memory when memory is constrained; that’s when RAM images are written to pre-defined locations once available resoources are exhausted.

--
Brian Masinick

[Anonymous]

PPC, swapping a magnifying glass icon in place of “search/ filter” is a good idea.
FYI, the per-item “name” and “description” strings are read from lines within each .desktop file (translations provided by the upstream maintainers).

BobC, I hear ya and agree ~~ get it shipped in antiX 19; save the ideas for additional features for later followup.

[Anonymous]

lxterminal

I drafted that with the expectation that Dave would swap in an alternative handler. Althought roxterm is technically the the better choice of default handler here, the default roxterm font/colorscehme (pink and cyan prompt on white background) is non-ideal IMO.

could start typing right away to search

Okay, restored that “immediately focus searchentry” behavior.
This results in absence of “Type to filter…” default being text displayed at startup
(but that was a misleading anyhow, b/c typing had no effect until searchentry received focus)

People with vision problems will have a hard time with smaller icons

FWIW, the reason I had chosen a smaller size (past tense, now changed in the copy at gitlab) ~~ many of the specified icon images are smaller than 48px and look quite pixelated when stretched to fill that larger size.

[Member Klaas Vaak]

This issue has spiralled out of control – I hope the experts here allow me to use this terminology.
I could not get the computer to read any live USBs decently. Even GParted on a live USB stick could not be launched.
But, with the antiX live USB GParted recognised the current antiX partitions, so I proceeded to delete them. That seemed to have gone well, but ….

I tried to reinstall antiX (BIOS settings: secure boot – off, Legacy booting on), and marked it for Auto-install, it threw up a message that /sda1 in still in use. So Iset it to custom install, and set the root to the eMMC drive, boot in root, /home in root, swap separate. It asked if everything was allowed to be overwritten, which I confirmed.
The installation completed and at the end asked me if I wanted to reboot (if so, take out the installation medium). Having confirmed that, it rebooted but then got stuck on a black screen with some text, and the message that no bootable device was detected, and to please insert the disc? Huh?

I am completely confused now, don’t understand what I did wrong, and am frustrated with all this. I probably did some things wrong, so I accept my stupidity for that, but is there anything to correct this and get the computer to boot correctly into antiX, hopefully without my earlier issues of trackpad/scrollbar sensitivity.

[Anonymous]

Hmmm … what did I miss?

You have 2 (two) computers — one older and weaker w/o CD and another newer and better, w/ CD.

Why not swap the HDD, install OS and swap the HDD again?

If you’re already disassembling …

I’ve no choice, I MUST disassemble my laptop now because, I have 3 SSD’s inside it and, if I try to install the Windows on one of them, then it’ll install the Windows on one SSD and the Recovery on the other — which is what I don’t want. It can install all on one HD only, if there is only one single physical HD inside, other ways, it’ll always try to install itself on both (which is safer == better option) or not at all — YES, Windows will either install where and how the Windows wants to install itself or it’ll simply not install at all, as long as it doesn’t get it, exactly the way it wants it.

I tried every trick, even formated two SSD’s as XFS — it would simply inform you — NO FREE SPACE! On the empty SSD’s! 😉

But hey, you’re lucky, you’re on Linux! It doesn’t care where did you install it — just swap the HDD and you’re done.

P.S.
The worst thing that could happen is, you might need to reset Network Interfaces manually.

[Anonymous]

Thanks oops,

It says vulnerable alot too. I haven’t noticed any odd problems so it might be giving false
because the celeron-m cpu might be too old since it doesn’t even have PAE.
spectra-meltdown-checker ……

* CPU microcode is the latest known available version:  YES  (latest version is 0x7 dated 2004/11/09 according to builtin MCExtractor DB v111 - 2019/05/18)
* CPU vulnerability to the speculative execution attack variants
  * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass):  YES 
  * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection):  YES 
  * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load):  YES 
  * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read):  YES 
  * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass):  YES 
  * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault):  NO 
  * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault):  YES 
  * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault):  YES 
  * Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)):  YES 
  * Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)):  YES 
  * Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)):  YES 
  * Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)):  YES

and …… the end result: lots of KO

> SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:KO CVE-2018-3640:KO CVE-2018-3639:KO CVE-2018-3615:OK CVE-2018-3620:KO CVE-2018-3646:OK CVE-2018-12126:KO CVE-2018-12130:KO CVE-2018-12127:KO CVE-2019-11091:KO

$ inxi -F
System:    Host: antix19b1 Kernel: 5.1.11-antix.1-486-smp i686 bits: 32 Desktop: IceWM 1.5.5+git20190610 
           Distro: antiX-19.b1_386-full Marielle Franco 12 June 2019 
Machine:   Type: Laptop System: Hewlett-Packard product: Presario 2200 (PM045UA#ABA) v: Rev 1 serial: <root required> 
           Mobo: Quanta model: 3084 v: 41.09 serial: <root required> BIOS: Hewlett-Packard v: F.10 date: 08/18/2004 
Battery:   ID-1: BAT0 charge: 35.0 Wh condition: 35.0/88.8 Wh (39%) 
CPU:       Topology: Single Core model: Intel Celeron M bits: 32 type: MCP L2 cache: 512 KiB 
           Speed: 1397 MHz min/max: N/A Core speed (MHz): 1: 1397 
Graphics:  Device-1: Intel 82852/855GM Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz 
           OpenGL: renderer: Mesa DRI Intel 852GM/855GM x86/MMX/SSE2 v: 1.3 Mesa 18.3.6 
Audio:     Device-1: Intel 82801DB/DBL/DBM AC97 Audio driver: snd_intel8x0 
           Sound Server: ALSA v: k5.1.11-antix.1-486-smp 
Network:   Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too 
           IF: eth0 state: down mac: 00:c0:9f:56:05:96 
           Device-2: Broadcom Limited BCM4306 802.11b/g Wireless LAN driver: b43-pci-bridge 
           IF-ID-1: wlan0 state: up mac: 00:90:4b:97:13:08 
Drives:    Local Storage: total: 55.89 GiB used: 10.43 GiB (18.7%) 
           ID-1: /dev/sda vendor: Hitachi model: IC25N060ATMR04-0 size: 55.89 GiB 
Partition: ID-1: / size: 54.46 GiB used: 10.43 GiB (19.1%) fs: xfs dev: /dev/sda1 
           ID-2: swap-1 size: 1.40 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Info:      Processes: 93 Uptime: 22m Memory: 460.6 MiB used: 191.2 MiB (41.5%) Shell: bash inxi: 3.0.33

[Member mattkingusa]

Hey sorry, I didn’t get any kind of notification about your response. The model is a G700ST. The ram vendor said that model doesn’t exist. But the BIOS says it’s a G700ST so does the boot splash and neofetch as well. But, it has an “A” and “B” ram slot that literally won’t work if I swap the ram sticks into the other slot. “A” stick has to be in “A” slot and the same with “B” stick. Not sure what to think about this system. But it’s working very well with antiX.

[Forum Admin BitJam]

Anonymous wrote:

but had missed the fact that mk_swap_file would be optional. (Instead, I worried it would be the new forced default.)

Well, I was thinking of offering to make a swap file after we’ve made at least one persistence file and a swap file does not already exist.

AK-47 made a good point that using swap partitions from a host machine that is not ours is a possible security risk. So having a swap file on the live-usb is safer. Also, if the live-usb is encrypted then the swap file will be encrypted too. In addition, we now automatically disable adding/using swap partitions on encrypted live-usbs. You can bypass this with “live_swap=force”. We still use the swap file though since it is already encrypted. You can disable this with “live_swap=all-off”. If you just want to disable using swap partitions use “live_swap=off”.

OTOH, using an untrusted machine is inherently unsafe since there may be a key logger, etc. I imagine this is be a far greater risk than using some swap. If I were the black hat then I would use a keylogger and I wouldn’t bother with dissecting the swap partition.

Context is worth 80 IQ points -- Alan Kay

[Anonymous]

Thanks for explaining. I’ve caught bits-n-pieces of the new stuff from looking at commit logs, but had missed the fact that mk_swap_file would be optional. (Instead, I worried it would be the new forced default.)

for fbcondecor, “f” makes sense to me (“s” does not, b/c it is not among the characters in f-b-c-o-n-d-e-c-o-r)

[Forum Admin BitJam]

Anonymous wrote:

splasht=va
The modes seem to be working as intended… as “feedback” I’m just letting you know that on a fast system the boot process proceeds so quickly that I barely have time to notice and/or read the hint text at bottom-left and bottom-right

Those navigation hints are intended for the case when X doesn’t start. It might help cut down on people confusing “X doesn’t start” with “does not boot”. A number of people see the blank screen when X doesn’t start and think our OS isn’t working at all. In the next iteration I plan to have an option to only show those nav hints on tty7 when we say “starting X”. If X starts fast they should fly by but if X doesn’t start then we have left instructions for the user on what they should/can do next. IMO it is better to have them than not to have them but we would value your input. This was one of the reasons we let you control what is shown with the splasht= parameter. IIRC:

“b” adds a border
“v” adds more text about what is happening
“n” adds navigation hints on all splash screens
“w” will add navigation hints only on tty7 but this is not in beta-1.
“a” adds everything above
[fs] enables late fbcondecor (background images on the consoles)

Uppercase characters turn things off so “splasht=Af” will turn off as much as possible but still enable late fbcondecor. As you have noticed we don’t throw any error message for characters we don’t understand which IIRC is traditional for splash boot parameters. Perhaps having “f” and “s” do the same thing is confusing and we should pick just one. I was tempted to have “v” enable late fbcondecor but it seemed more appropriate for controlling verbose progress.

We had wanted the boot parameter to be “tsplash” (for text splash) but fbcondecor sees this as “splash” and thinks we are talking to it so we moved the “t” from the front to the end.

PS if you want to see the splash screen hang around a little longer then try using “toram” or try the new boot parameter “mk_swap_file=” for example “mk_swap_file=1G” will create a 1 GiB swap file on your live-usb. This can take a while since swap_files aren’t allowed to be sparse.

Context is worth 80 IQ points -- Alan Kay

[Anonymous]

1000 times more elegant and more sophisticated, better implemented and probably

gotta swap muh boots for hip waders ~~ the level of hyperbole is really gettin’ deep in here.

[Member Klaas Vaak]

Anonymous wrote:

retry
sudo parted -l

Here is is:

sudo] password for Marie-Claire: 
Model: USB NAND FLASH DISK (scsi)
Disk /dev/sdb: 131MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      16.4kB  131MB  131MB  primary  fat16        boot

Model: MMC BGND3R (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name     Flags
 1      17.4kB  268MB   268MB   fat32           ESP      boot, esp
 2      268MB   8858MB  8590MB  ext4            primary
 3      8858MB  11.0GB  2147MB  linux-swap(v1)  primary

Error: /dev/mmcblk0boot0: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)                               
Disk /dev/mmcblk0boot0: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 

Error: /dev/mmcblk0boot1: unrecognised disk label
Model: Generic SD/MMC Storage Card (sd/mmc)                               
Disk /dev/mmcblk0boot1: 4194kB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:

[Forum Admin dolphin_oracle]

rokytnji wrote:

Like. I would not delete

Device     Boot Start    End Sectors  Size Id Type
/dev/sda1  *       32 255999  255968  125M  6 FAT16

partition just for starters. Installer has a option to install grub to that partition to boot the new install of MX. As I found out when I deleted mine and tried the install grub to mbr on sda instead.

I feel like changing this topic title this morning also. This baked in crap needs a professional dish washer.

/dev/sda1 is the ESP on the live-USB I think.

blkid
/dev/mmcblk0p1: UUID=”64A5-7D5C” TYPE=”vfat” PARTLABEL=”ESP” PARTUUID=”4373a9ca-1cf9-4b1b-8c05-494338bb4f68″
/dev/mmcblk0p2: LABEL=”rootantiX17.1″ UUID=”c3a4d07b-cdcf-4a2a-bebf-8d735153e464″ TYPE=”ext4″ PARTLABEL=”primary” PARTUUID=”f2c17e23-253a-407e-809a-915704b637b9″
/dev/mmcblk0p3: LABEL=”antiXswap” UUID=”4bfdd799-2339-409a-ade2-f6a6af5c0d72″ TYPE=”swap” PARTLABEL=”primary” PARTUUID=”621588f1-81b2-44e9-851d-29d53ef15333″

are the eMMC blk devices. the fact is, many distributions have problems with these devices.

one of the big problems with these devices is that partition table updates don’t necessarily automatically update the blkid caches. We work around this in the antiX/mx installer but I can’t say everyone does.

I would manually repartition the disk from the live-USB, then reboot, then try the mint installer.

after that I would talk to the mint people about their installer. Because there is no “baking” in of the antiX/MX file system. Its a straight-up cp operation to put the filesystem on the devices, same as any other hard drive device.

Its also possible that the devices are failing. They are relatively cheap storage after all. But I would try the partition thing first.

[Member Klaas Vaak]

rokytnji wrote:

Without some blkid and fdisk -l and parted -l commands. Kinda hard to tell you what and what not to delete when it comes to these newer laptops .

This is a long list:

blkid
/dev/mmcblk0p1: UUID="64A5-7D5C" TYPE="vfat" PARTLABEL="ESP" PARTUUID="4373a9ca-1cf9-4b1b-8c05-494338bb4f68"
/dev/mmcblk0p2: LABEL="rootantiX17.1" UUID="c3a4d07b-cdcf-4a2a-bebf-8d735153e464" TYPE="ext4" PARTLABEL="primary" PARTUUID="f2c17e23-253a-407e-809a-915704b637b9"
/dev/mmcblk0p3: LABEL="antiXswap" UUID="4bfdd799-2339-409a-ade2-f6a6af5c0d72" TYPE="swap" PARTLABEL="primary" PARTUUID="621588f1-81b2-44e9-851d-29d53ef15333"

fdisk -l
Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mmcblk0: 29.1 GiB, 31268536320 bytes, 61071360 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CF36C4BD-4EF2-4729-8B72-3207D90CD93A

Device            Start      End  Sectors  Size Type
/dev/mmcblk0p1       34   524287   524254  256M EFI System
/dev/mmcblk0p2   524288 17301503 16777216    8G Linux filesystem
/dev/mmcblk0p3 17301504 21495807  4194304    2G Linux filesystem

Disk /dev/sda: 125 MiB, 131072000 bytes, 256000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start    End Sectors  Size Id Type
/dev/sda1  *       32 255999  255968  125M  6 FAT16

As for parted -l: see next page.

• This reply was modified 3 years, 11 months ago by Klaas Vaak.
• This reply was modified 3 years, 11 months ago by Klaas Vaak.

[Anonymous]

noClue what are we comparing here.

If I compare, then it’ll read:

46.7 (PRobOS OB) vs. 322 (OB) or 402 (XFCE) MB RAM.

Or you’re comparing the naked desktop vs. the desktop with 2 open tabs in Firefox?

Too manyroads maybe … time for a second look … or sanity check … maybe this time at 1:1.

noClue …

P.S.
Seriously:
On a 384 MB RAM machine (128 + 256 MB), PRoboOS will let you surf with Firefox; the concurrent will be swapping only to keep the naked desktop alive.
On my machines with 32, 64 and 128 GB RAM, it’ll not make any difference but, on them I’ll also not install something like transparent OB.