Hai guys!
Looky this:
Weird syntax error.
Mine just hangs with a blinking cursor. No output, no nothing.
Working here:
can you see with inxi ?
sudo pacman -S inxi
inxi -Fza
Like so?
[orca@MiniMax ~]$ inxi -Fza
System:
Kernel: 5.11.1-arch1-1 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-linux
root=UUID=dafa0344-12c2-4a0f-aadc-ecddcaed54ff rw quiet loglevel=3
nowatchdog
Desktop: MATE 1.24.1 info: mate-panel wm: marco 1.24.1 dm: LightDM 1.30.0
Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop System: Gigabyte product: B550I AORUS PRO AX v: N/A
serial: <filter>
Mobo: Gigabyte model: B550I AORUS PRO AX v: x.x serial: <filter>
UEFI: American Megatrends v: F11 date: 12/31/2020
Battery:
Device-1: hidpp_battery_0
model: Logitech Marathon Mouse/Performance Plus M705 serial: <filter>
charge: 55% (should be ignored) rechargeable: yes status: Discharging
CPU:
Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP arch: Zen 3
family: 19 (25) model-id: 21 (33) stepping: N/A microcode: A201009
L2 cache: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 88672
Speed: 4455 MHz min/max: 2200/4791 MHz boost: enabled Core speeds (MHz):
1: 4455 2: 2870 3: 2867 4: 2867 5: 3593 6: 2873 7: 2867 8: 2869 9: 3584
10: 2875 11: 3577 12: 2871
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
IBRS_FW, STIBP: always-on, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GK104 [GeForce GTX 770] vendor: ASUSTeK driver: nvidia
v: 460.56 alternate: nouveau,nvidia_drm bus ID: 08:00.0 chip ID: 10de:1184
class ID: 0300
Display: x11 server: X.Org 1.20.10 compositor: marco v: 1.24.1 driver:
loaded: modesetting failed: nvidia display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3")
s-diag: 583mm (23")
Monitor-1: HDMI-0 res: 1920x1080 hz: 60 dpi: 92
size: 531x299mm (20.9x11.8") diag: 609mm (24")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:
Device-1: NVIDIA GK104 HDMI Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 08:00.1 chip ID: 10de:0e0a class ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte
driver: snd_hda_intel v: kernel bus ID: 0a:00.4 chip ID: 1022:1487
class ID: 0403
Sound Server: ALSA v: k5.11.1-arch1-1
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
port: f000 bus ID: 06:00.0 chip ID: 10ec:8125 class ID: 0200
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel port: f000
bus ID: 07:00.0 chip ID: 8086:2723 class ID: 0280
IF: wlan0 state: down mac: <filter>
Drives:
Local Storage: total: 2.96 TiB used: 850.39 GiB (28.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Transcend model: TS256GMTE110S
size: 238.47 GiB block size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: S1111B1L temp: 40.9 C
ID-2: /dev/sda maj-min: 8:0 type: USB vendor: Toshiba
model: External USB 3.0 size: 931.51 GiB block size: physical: 512 B
logical: 512 B serial: <filter> rev: 5438
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Toshiba
model: External USB 3.0 size: 1.82 TiB block size: physical: 512 B
logical: 512 B serial: <filter> rev: 5438
Partition:
ID-1: / raw size: 238.17 GiB size: 233.38 GiB (97.99%)
used: 12.16 GiB (5.2%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw size: 300 MiB size: 299.4 MiB (99.80%)
used: 280 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Alert: No Swap data was found.
Sensors:
System Temperatures: cpu: 41.2 C mobo: N/A gpu: nvidia temp: 38 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 45%
Info:
Processes: 272 Uptime: 40m wakeups: 4 Memory: 15.64 GiB
used: 1.55 GiB (9.9%) Init: systemd v: 247 Compilers: gcc: 10.2.0
Packages: pacman: 950 lib: 274 Shell: Bash v: 5.1.4
running in: mate-terminal inxi: 3.3.00
[orca@MiniMax ~]$
The Syntaxfehler is only for Germans ?
What does free -b
return with a german language set.
you can check
sudo inxi -mxxx
something odd with Ryzen 2 3600XT i have 91070 bogomips ( you should have more )
also for boot kernels ,
see for AKM ( multi boot kernel ) and add version zen ( for Ryzen )
for boot kernels see theses options :
noapic
processor.max_cstate=5
iommu=pt
rcu_nocbs=0_11
systemd.unified_cgroup_hierarchy=true
nvme_core.default_ps_max_latency_us=0
/usr/bin/screenfetch: Zeile 1802: 2377703424-: Syntaxfehler: Operator erwartet. (Fehlerverursachendes Zeichen ist "-").
line 1802: 2377703424-: Syntax error: operator expected. (Error-causing character is “-”).`
I see what the issue is. When you run free -b
with a german language set you get this:
LANG=de_DE.UTF-8 free -b
gesamt benutzt frei gemns. Puffer/Cache verfügbar
Speicher:67344703488 14921134080 46072750080 4848996352 6350819328 46876737536
Swap: 17179865088 0 17179865088
Since Speicher runs into the first number it breaks the awk
@Orca I think that seems to be a bug with screenfetch itself.
screenfetch
+I+ wally@Netbook
+777+ OS: EndeavourOS rolling
+77777++ Kernel: x86_64 Linux 5.11.1-arch1-1
+7777777++ Uptime: 2h 8m
+7777777777++ Packages: 2589
++7777777777777++ Shell: bash 5.1.4
++777777777777777+++ Resolution: 1920x1080
++77777777777777777++++ DE: KDE 5.79.0 / Plasma 5.21.1
++7777777777777777777++++ WM: KWin
+++777777777777777777777++++ GTK Theme: Nordic [GTK2/3]
++++7777777777777777777777+++++ Icon Theme: Arc-X-P
++++77777777777777777777777+++++ Disk: 386G / 519G (79%)
+++++777777777777777777777777+++++ CPU: Intel Atom x5-Z8350 @ 4x 1.92GHz
+++++++7777777777777777++++++ GPU: Mesa DRI Intel(R) HD Graphics (CHV)
+++++++++++++++++++++++++++++ RAM: 2643MiB / 3852MiB
Works here without any issues.
No, really? LOL
Shit man, and I only wanted to make a screenfetch to bragg about my new system in an unrelated blog. And now I can’t.
Looks like there is already an open issue for it.
not enaugh RAM to brake it
use LANG=C screenfetch
Wait a few mins. I’ll post from my desktop. Approximately 12 GB RAM.
is neofetch
also throwing the same error?
I put in a PR with a simple patch.
Just use LANG=C screenfetch