- This topic has 27 replies, 10 voices, and was last updated Nov 23-7:40 am by BobC.
-
Posts
-
PPC
You are, in fact, using antiX 64 bits version :
Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64so that is not your problem…
Did you try booting from antiX and use the mem test tool available from the menu?
On the Discord suggestion – hummm- I never used it before – you can always wait to see what anticapitalista says about that suggestion (if he say anything).
P.
christophe
Memory: RAM: total: 1.93 GiB used: 1.25 GiB (64.7%) Array-1: capacity: 8 GiB slots: 2 EC: None max-module-size: 4 GiB note: est. Device-1: Bottom - Slot 1 type: DDR3 detail: synchronous size: 2 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64 manufacturer: Samsung part-no: M471B5673EH1-CH9 serial: <filter> Device-2: Bottom - Slot 2 type: DDR3 detail: synchronous size: 2 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64 manufacturer: Samsung part-no: M471B5673EH1-CH9 serial: <filter>confirmed antiX frugaler, since 2019
marathon
Did you try booting from antiX and use the mem test tool available from the menu?
Absolutely, mentioned this in the thread. đ
marathon
Memory:
RAM: total: 1.93 GiB used: 1.25 GiB (64.7%)
Array-1: capacity: 8 GiB slots: 2 EC: None max-module-size: 4 GiB
note: est.
Device-1: Bottom – Slot 1 type: DDR3 detail: synchronous size: 2 GiB
speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: Samsung part-no: M471B5673EH1-CH9 serial: <filter>
Device-2: Bottom – Slot 2 type: DDR3 detail: synchronous size: 2 GiB
speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64
manufacturer: Samsung part-no: M471B5673EH1-CH9 serial: <filter>OK so what’s the point? It has 4 Gb of ram, but only see’s 2Gb, Like I said originally. No one has any idea why?
christophe
Look at these. They both were solved, but in different ways:
https://www.linuxquestions.org/questions/debian-26/debian-64-bit-sees-only-2gb-ram-574338/
https://unix.stackexchange.com/questions/65980/only-two-2gb-memory-available-on-64-bit-linux-kernel
confirmed antiX frugaler, since 2019
seaken64
Hi @marathon, welcome to antiX.
No, you are not the only one to find this forum software a challenge. The subject comes up now and then and I share your opinion that it is awkward. But we soldier on and eventually we figure it out.
There is a search function that can be useful. But there is a better way to search the forum using google search. I can’t recall the technique at the moment but if you search the forum it will probably show up. Use the search box directly on the first Forum page, the page that comes up after clicking on the Forum menu on the top above. The search icon on the menu does not yield same results.
Seaken64
BobC
It’s a computer from 2010 or before based on the BIOS date. Why not try the older style kernels from the Package Installer? Install one, try 4.19.xxx first, then 4.9.xxx if that doesn’t work. After installing, Reboot, and when the grub menu comes up, go to Advanced options and select it. After it boots, see if it worked, and also make sure you can Suspend and Resume.
System: Kernel: 5.10.142-antix.2-amd64-smp arch: x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: IceWM v: 3.2.0 dm: slimski v: 1.5.0 Distro: antiX-22_x64-full Grup Yorum 18 October 2022 base: Debian GNU/Linux 11 (bullseye) Machine: Type: Laptop System: Hewlett-Packard product: HP Pavilion dv6 Notebook PC v: 049D210000241210000020000 serial: <filter> Chassis: type: 10 serial: N/A Mobo: Hewlett-Packard model: 3659 v: 32.24 serial: <filter> BIOS: Hewlett-Packard v: F.16 date: 01/22/2010 Battery: ID-1: BAT0 charge: 43.2 Wh condition: N/A/47.5 Wh volts: 9.3 min: 10.8 model: Hewlett-Packard Primary type: Li-ion serial: N/A status: N/A Memory: RAM: total: 1.93 GiB used: 1.25 GiB (64.7%) Array-1: capacity: 8 GiB slots: 2 EC: None max-module-size: 4 GiB note: est. Device-1: Bottom - Slot 1 type: DDR3 detail: synchronous size: 2 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64 manufacturer: Samsung part-no: M471B5673EH1-CH9 serial: <filter> Device-2: Bottom - Slot 2 type: DDR3 detail: synchronous size: 2 GiB speed: 1333 MT/s volts: N/A width (bits): data: 64 total: 64 manufacturer: Samsung part-no: M471B5673EH1-CH9 serial: <filter> CPU: Info: quad core model: Intel Core i7 Q 720 bits: 64 type: MT MCP smt: enabled arch: Nehalem rev: 5 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 1600 min/max: 933/1600 boost: enabled volts: 1.2 V ext-clock: 1066 MHz cores: 1: 1600 2: 1600 3: 1600 4: 1600 5: 1600 6: 1600 7: 1600 8: 1600 bogomips: 25537 Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts est flush_l1d fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pdcm pebs pge pni popcnt pse pse36 pti rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tsc vme xtopology xtprModdIt
Please stop trying to blame the operating system unless everything else works perfectly with another OS.
First ensure Hardware is OK otherwise it is a waste of time and nerves…I have only ever seen an issue like quoted when hardware or BIOS problems exist.
On a lot of computers of all types and manufacturers.Do you have latest available BIOS ?. If not please update.
If possible fit two iknown working modules and test before further work.Hopefully understandable fault finding proceedure.
Swap the known working module in to the presently non working slot.
Boot check if the module is in useTest with just the NON RECOGNIZED module fitted in presently working slot, first carefully clean the contacts.
If recognized and the system booting correctly, contact issue, rarely but not impossible timing or BIOS settings.
Fit both modules, Boot check if both modules are in use
Test with a live stick of another distro, very unlikely to help but not entirely unknown that a kernel issue is cause.
If problem still exists and possible fit both modules in another computer and test.
Sometimes such issues are very annoying/time consuming to resolve.
Ram modules age and can develop subtle defects. Ram can be listed by the OS but still be defective as a description is read
from the modules but nothing fully tested.Please stop trying to blame the operating system unless everything else works perfectly with another OS.
I suggested that Marathon should check if the RAM is correctly recognized by another OS. Since for about a week Marathon has not reported back, he either solved that problem or lost interest in it (or in antiX).
Just in case, Marathon reads this – the forum members usually are persistent, in trying to help solve problems, you just need to give the information that people ask you, in this case- test the device with other OS- some problems reported here are not antiX, or even OS specific, but hardware problems that users didn’t even knew they have – in my case, for example, a busted sound card- it happened twice to me- I assumed it was antiX just refusing to play sounds, but it was, in fact 1- the sound card, and 2- in my laptop, a weird conflict between alsa and pulseaudio that, for some reason did not mute my volume, but moved it down to zero…Lesson learned: the problem, sometimes, is in the place that we least expect it to be…
P.
marathon
Why not try the older style kernels from the Package Installer? Install one, try 4.19.xxx first, then 4.9.xxx if that doesnât work. After installing, Reboot, and when the grub menu comes up, go to Advanced options and select it. After it boots, see if it worked, and also make sure you can Suspend and Resume.
Will do. Thanks for the constructive advice. It runs fine with the 2Gb of ram, but of course it’d be nice to have all 4Gb working. đ
Damn, this forum sucks at responding to threads! One has to scroll all the way to the bottom to find the window after hitting reply. Geesus get a modern BBS FFS. I’m done with this, can’t even respond via email to the thread.
marathon
Thanks for the helpful hintâOf course the best solution would be a slack interface (if one must use a web interface). This one isn’t UI friendly.
marathon
I suggested that Marathon should check if the RAM is correctly recognized by another OS
I think it was already mentioned that yes, another OS see the entire ram, even other Linux distributions too! The ram was checked with the onboard ram tool at boot. Checked out A-OK. I even removed the ram, checked the contacts and cleaned them b4 replacing back. Yours truly is not a new Linux kernel user, either.
BTW, another possible kernel to try would be the Liquorix 6.0 one. It solved hardware interface problems for one of my laptops.
- You must be logged in to reply to this topic.
