- This topic has 10 replies, 8 voices, and was last updated Nov 21-7:53 pm by christophe.
-
Posts
-
dimz
I try both in my system …
with antix 32 start from 85 M RAM
with antix 64 start from 500 M RAM
my system is 64
i prefer use antix 32 because is faster but is this better solution or must use antix 64 ?
give me your opiniondim@antix1dim:~
$ inxi -zv7
System:
Host: antix1dim Kernel: 4.9.160-antix.2-486-smp i686 bits: 32 compiler: gcc v: 6.3.0
Desktop: IceWM 1.4.2 info: icewmtray dm: SLiM 1.3.4
Distro: antiX-17.4.1_386-full Helen Keller 28 March 2019
base: Debian GNU/Linux 9 (stretch)
Machine:
Type: Laptop System: Hewlett-Packard product: HP Compaq 6730b (GW687AV) v: F.08
serial: <filter> Chassis: type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 30DD v: KBC Version 96.18 serial: <filter>
BIOS: Hewlett-Packard v: 68PDD Ver. F.08 date: 09/18/2008
Battery:
ID-1: BAT0 charge: 45.7 Wh condition: 46.5/46.5 Wh (100%) volts: 12.5/11.1
model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Unknown
Memory:
RAM: total: 1.90 GiB used: 677.8 MiB (34.8%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: Dual Core model: Intel Core2 Duo P8400 bits: 64 type: MCP arch: Penryn
rev: 6 L2 cache: 3072 KiB bogomips: 9044
Speed: 1600 MHz min/max: 800/2267 MHz Core speeds (MHz): 1: 1600 2: 1600
Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cx16 cx8 de
ds_cpl dtes64 dtherm dts est flexpriority fpu fxsr ht lahf_lm lm mca mce mmx monitor
msr mtrr nx pae pat pbe pdcm pebs pge pni pse pse36 sep smx ss sse sse2 sse4_1 ssse3
tm tm2 tpr_shadow tsc vme vmx vnmi xtpr
Graphics:
Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Hewlett-Packard
driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2a42
Display: server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa
resolution: 1280×800~60Hz
OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express x86/MMX/SSE2 v: 2.1 Mesa 13.0.6
direct render: Yes
Audio:
Device-1: Intel 82801I HD Audio vendor: Hewlett-Packard driver: snd_hda_intel
v: kernel bus ID: 00:1b.0 chip ID: 8086:293e
Sound Server: ALSA v: k4.9.160-antix.2-486-smp
Network:
Device-1: Broadcom Limited BCM4312 802.11b/g LP-PHY vendor: Hewlett-Packard
driver: wl v: kernel port: 6000 bus ID: 02:00.0 chip ID: 14e4:4315
IF: wlan0 state: up mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> scope: link
Device-2: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCI Express
vendor: Hewlett-Packard driver: tg3 v: 3.137 port: 6000 bus ID: 85:00.0
chip ID: 14e4:1693
IF: eth0 state: down mac: <filter>
WAN IP: <filter>
Drives:
Local Storage: total: 126.33 GiB used: 6.23 GiB (4.9%)
ID-1: /dev/sda vendor: Toshiba model: MK1252GSX size: 111.79 GiB speed: 3.0 Gb/s
serial: <filter> rev: 1C scheme: MBR
ID-2: /dev/sdb type: USB vendor: Toshiba model: TransMemory size: 14.53 GiB
serial: <filter> rev: PMAP scheme: MBR
Optical-1: /dev/sr0 vendor: Optiarc model: DVD-ROM DDU820S rev: MH04
dev-links: cdrom,dvd
Features: speed: 24 multisession: yes audio: yes dvd: yes rw: none state: running
RAID:
Message: No RAID data was found.
Partition:
ID-1: / size: 17.40 GiB used: 3.64 GiB (20.9%) fs: ext4 dev: /dev/sda3
label: rootantiX17.4.1 uuid: 3820c3bb-0b7f-447b-9b6f-547a4c7e1a7d
ID-2: /home size: 20.84 GiB used: 2.54 GiB (12.2%) fs: ext4 dev: /dev/sda4
label: homeantiX uuid: f01c1ec2-fb66-49b9-b5c5-e5fddc12f018
ID-3: /media/-rw size: 11.66 GiB used: 40.0 MiB (0.3%) fs: ext4 dev: /dev/sdb5
label: -rw uuid: 3cd1ace9-6a9d-43a0-933e-a1a45fd7793d
ID-4: /media/MX-Live raw size: 1.41 GiB size: <root required> used: <root required>
fs: iso9660 dev: /dev/sdb4 label: MX-Live uuid: 2019-10-21-17-35-05-00
ID-5: /media/usbboot size: 240.2 MiB used: 7.0 MiB (2.9%) fs: vfat dev: /dev/sdb3
label: usbboot uuid: 3055-742E
ID-6: /media/usbdata size: 1.03 GiB used: 5.8 MiB (0.6%) fs: ntfs dev: /dev/sdb1
label: usbdata uuid: 0504B837002B90F5
ID-7: swap-1 size: 6.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda5 label: N/A
uuid: 40ccc468-e3a5-4544-82b8-ee84ab6df0b5
Unmounted:
ID-1: /dev/sda1 size: 1 KiB fs: <root required> label: N/A uuid: N/A
ID-2: /dev/sda2 size: 46.57 GiB fs: ext4 label: N/A
uuid: 743f0e89-2ac8-42cb-a66d-bbef565e1ecc
ID-3: /dev/sda6 size: 18.62 GiB fs: ext4 label: N/A
uuid: d478de32-5949-4f6f-b9d3-aabeaaf9bcc9
ID-4: /dev/sdb2 size: 1 KiB fs: <root required> label: N/A uuid: N/A
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Hub: 2-0:1 info: Full speed (or root) Hub ports: 6 rev: 2.0 speed: 480 Mb/s
chip ID: 1d6b:0002
Device-1: 2-5:2 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB
/ PNY Attache 4GB Stick
type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s
chip ID: 0930:6545 serial: <filter>
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Device-2: 3-1:2 info: HP Bluetooth 2.0 Interface [Broadcom BCM2045] type: Bluetooth
driver: btusb interfaces: 4 rev: 2.0 speed: 12 Mb/s chip ID: 03f0:171d
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 7-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 8-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Sensors:
System Temperatures: cpu: 50.0 C mobo: 43.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 161 Uptime: 1h 08m 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
inxi: 3.0.36
dim@antix1dim:~
$BobC
If you have 4 gb of memory or less, 64 bit is unnecessary, so use 32 bit
rokytnji
Agree with BobC.
Memory: RAM: total: 1.90 GiB used: 677.8 MiB (34.8%)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 problems
oops
If you have 4 gb of memory or less, 64 bit is unnecessary, so use 32 bit
… And if superior to 4 gb of memory, you can use a PAE Kernel with the 32 bits version.
ok thank you…
i install antix 19 64 and works fine
rayluo
If you have 4 gb of memory or less, 64 bit is unnecessary, so use 32 bit
… And if superior to 4 gb of memory, you can use a PAE Kernel with the 32 bits version.
But AntiX 19 does not (yet?) provide some 32bit PAE flavor to download, does it? Not from SourceForge Mirror.
anticapitalista
No, but it does provide plenty of pae kernels in the repos – easy to install using cli-aptiX
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
rayluo
AntiX 19 does not (yet?) provide some 32bit PAE flavor to download, does it?
No, but it does provide plenty of pae kernels in the repos – easy to install using cli-aptiX
I happen to be a LiveUSB user, exclusively. Following the hint above, I ran cli-aptiX to choose a PAE kernel. The update itself seemed smooth, but after the update, “uname -a” showed no difference. Perhaps it would (understandably) need a reboot to take effect, but does that mean I need a root persistence and later preferably a remaster? (My first root persistence attempt failed probably due to running out of thumb drive space, so I would need to try it again later.)
Also I notice there is a Live USB Kernel Updater inside the antiX menu. Is it used to somehow replace the root persistence and remaster step? But does that mean I would need to first install the new kernel to hard disk, for it to be available for “flushing” into the Live USB disk?
I don’t mind to do some trial and error here. But it would also be nice if there is already some (even high level) guidance for this.
Anonymous
The live-kernel-updater utility requires (demands) that you first perform a live-remaster operation & reboot. This prerequisite ensures that a known-good falback will be available if a newly-installed kernel misbehaves on your system.
guidance:
0) refer to “Synposis” section of https://github.com/BitJam/live-kernel-updater/blob/master/README.md
1) “install” a different kernel via synaptic
2) perform a live-remaster operation
3) reboot & then run live-kernel-updater4) After installing a new kernel and testing across XX reboot sessions to become confident that everything’s working fine, browse the liveboot media AsRoot and manually remove the fallback *.old files (a housekeeping step to reduce the amount of used space on the drive)
anticapitalista
AS skidoo says except you can run live-kernel-updater immediately after the remaster has finished and before reboot.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
christophe
The only bad thing about 32-bit, in 4 GB or less computers, IMO, is that some software is only available in 64-bit.
confirmed antiX frugaler, since 2019
- You must be logged in to reply to this topic.
