Should I post inxi from the working iso(19.0.2)??
Yes I can install 19.0.2
And I’ll try architect edition…
So I can never install new iso???
System:
Host: manjaro-gnome Kernel: 5.4.23-1-MANJARO x86_64 bits: 64 compiler: gcc
v: 9.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
driver=nonfree nouveau.modeset=0 i915.modeset=1 radeon.modeset=0
misobasedir=manjaro misolabel=MANJARO_GNOMEM_1902 quiet
systemd.show_status=1 apparmor=1 security=apparmor
Desktop: Gnome 3.34.4 wm: gnome-shell dm: GDM 3.34.1 Distro: Manjaro Linux
Machine:
Type: Desktop Mobo: Intel model: DH61HO v: AAG62445-102
serial: GEHO231000C2 UEFI: Intel v: HOH6110H.86A.0816.2018.1031.1524
date: 10/31/2018
CPU:
Topology: Quad Core model: Intel Core i7-3770S bits: 64 type: MT MCP
arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 20
L1 cache: 256 KiB L2 cache: 8192 KiB L3 cache: 8192 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 49511
Speed: 1597 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 1596 2: 1596
3: 1596 4: 1596 5: 1596 6: 1597 7: 1596 8: 1596
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf
mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT vulnerable
Type: meltdown mitigation: PTI
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 generic retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ZOTAC driver: nvidia
v: 440.59 bus ID: 01:00.0 chip ID: 10de:1c82
Display: server: X. org 1.20.7 driver: nvidia compositor: gnome-shell
resolution: <xdpyinfo missing>
OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 440.59
direct render: Yes
Audio:
Device-1: Intel 6 Series/C200 Series Family High Definition Audio
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20
Device-2: NVIDIA GP107GL High Definition Audio vendor: ZOTAC
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fb9
Sound Server: ALSA v: k5.4.23-1-MANJARO
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Intel driver: r8169 v: kernel port: d000 bus ID: 03:00.0
chip ID: 10ec:8168
IF: enp3s0 state: down mac:
Device-2: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB
driver: r8188eu bus ID: 1-1.1:3 chip ID: 0bda:8179 serial: 00E04C0001
IF: wlp0s26u1u1 state: down mac:
Device-3: TP-Link USB 10/100/1000 LAN type: USB driver: r8152
bus ID: 4-3:2 chip ID: 2357:0601 serial: 000001000000
IF: enp4s0u3 state: up speed: 100 Mbps duplex: full mac:
Drives:
Local Storage: total: 1.93 TiB used: 104.62 GiB (5.3%)
ID-1: /dev/sda vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
block size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s
rotation: 7200 rpm serial: Z3TCQ0VZ rev: KC45 scheme: GPT
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s
serial: 2010E2910DFF rev: 023 scheme: GPT
ID-3: /dev/sdc type: USB vendor: Seagate model: BUP Slim BK
size: 931.51 GiB block size: physical: 4096 B logical: 512 B
serial: NA9E8CVM rev: 0304 scheme: MBR
ID-4: /dev/sdd type: USB model: TO Exter nal USB 3.0 size: 111.80 GiB
block size: physical: 4096 B logical: 512 B serial: 201503310007F
rev: 0204 scheme: GPT
Partition:
ID-1: / raw size: N/A size: 11.70 GiB used: 781.7 MiB (6.5%) fs: overlay
source: ERR-102
Sensors:
System Temperatures: cpu: 45.0 C mobo: N/A gpu: nvidia temp: 35 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 48%
Info:
Processes: 248 Uptime: 2m Memory: 15.60 GiB used: 1.20 GiB (7.7%)
Init: systemd v: 242 Compilers: gcc: N/A Shell: bash (sudo) v: 5.0.16
running in: gnome-terminal inxi: 3.0.37Thank you 
But please edit it and use ``` at the beginning and at the end, so that it is readable formatted. 
What we can try is setting parameter in grub boot menu, to see what actually the problem is with the newer kernel.
Also very helpful would be a boot journal:
journalctl -b -0 > ~/current_boot.log
Without internet connection impossible, but install Manjaro 19.0.2 and don’t upgrade everything, instead install the linux56 kernel and boot it. Then create the same log as above. If you cant do anything in linux56, just reboot use the linux54 kernel. Then create the log, but like this:
journalctl -b -1 > ~/last_boot.log
it will create a log file of the previous boot.
Better use https://pastebin.com/ for the journal log, because it could be very long.
1 Like
Ya…after updating everything it is now 20.1
And I can switch to kernel 5.8.6 without any problem
Bt is there any way to directly install the latest isos with new kernels?
1 Like
Feel free to built you own manjaro distro with the preferred kernel:
1 Like
i probably wouldnt worry about manjaro…every week theres about 3gig of updates you need to install …just getting too expensive…
Hey sometimes gets stuck in the login screen…with 5.8.6 kernel
Sometimes it boots fine and sometimes…
Hello and welcome to Manjaro!
Well, Manjaro is a semi-rolling release distro based on Arch, so larger updates are completely normal.
3 gigs every week though as you claim is a bit exaggerated.
1 Like
So I can’t install new isos?
So I can’t install new isos?
That’s not a good thing!
I would say 80% have no problems with newer kernels. If your hardware is not popular at linux users, then it is needed to detect whats the problem there. It is Open Source. Feel free to detect the problem. Here are people who could help you out by troubleshooting the problem.
1 Like
I can install every iso in virtual box in windows 10
So why can’t I install them outside vbox?
It is always nice to have a newer kernel series, but with older hardware especially the older series might be as good or even better depending how much you need newer features.
Kernel 5.4 is supported until Dec 2025.
You can always check newer ISOs, maybe with kernel 5.9 or 5.10 if they start to work with your machine.
Or you (or some else with better understanding of the kernel) find out what is causing the failure and then they find a solution and patch the kernel and you will be able to use it then.
You can ask someone to create a custom ISO for you with the command:
buildiso -k linux54 -p kde -f
or
buildiso -k linux54 -p gnome -f
(-f for full profile)
If you manage to update the installation afterward you are as good as with an install from a new ISO. But there might be some problems with the update. Create a new topic if you get problems with the update and people will try to help you.
Because VirtualBox is not real hardware. It is a simplified environment, some hardware components get emulated by software there.
I think this topic is done. I will improve the title and maybe someone who knows a solution will find your topic.
But in this topic you better wait and avoid bumping it unless you have found some useful information.
1 Like
Thank you
Thank you all
I upgraed successfully from 19.0.2 to 20.1 without any problem…
And ya l’ll keep checking new isos if they work.
For now I am good😀
1 Like
Around a couple of gigs here. But if you are on a metered connection it could still be an issue. In that case you’d be better off using a point-release distro.
Agreed on that one!
Just tried Ubuntu 20.10
Everything working properly…kernel 5.8.0-18
So 5.8 is working on my system!!
I’ve found the problem…I had a pcie to usb3 card installed…that was causing the problem…removed that card, everything is working…I can now install latest isos…no problem… everything is fixed… 
1 Like