You are not logged in.
i dont have to do this on my original arch ssd
You're running this while the new disk is attached to the system?
Please post a journal from such boot covering a suspend cycle.
Online
i dont have to do this on my original arch ssd
You're running this while the new disk is attached to the system?
Please post a journal from such boot covering a suspend cycle.
what i mean is that the kernel version on my original arch install is the same as my new one so i don't think that it's a kernel issue.
Offline
BIG NEWS: After reinstalling all my packages, i got some more messages for what happens when i resume. output of
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
Offline
i don't think that it's a kernel issue
No, I think it's a "new disk" issue since some dozen posts ago
The plan is to sleep/wake the system from the old disk and see whether - though everything seems working, the new disk acts up.
It'll likely be helpful if some partition of the new disk is mounted before sleeoing the system.
Online
i don't think that it's a kernel issue
No, I think it's a "new disk" issue since some dozen posts ago
The plan is to sleep/wake the system from the old disk and see whether - though everything seems working, the new disk acts up.
It'll likely be helpful if some partition of the new disk is mounted before sleeoing the system.
Ok just to be clear you want me to sleep my original system with a partition of the new disk mounted and then tell what happened? well the result is that it worked just fine. also there are some new things in the journal which i posted in my previous post which include the reading/poll/queues thing to be completed allowing there to be some more information such as the wifi/Bluetooth driver failing and getting stuck on getting stuck on
random: crng reseeded on system resumption
Offline
Ok just to be clear you want me to sleep my original system with a partition of the new disk mounted and then tell what happened?
Almost. Not "tell", "show" - post the journal.
We're lookng for any signs of the nvme acting up (though not critically, since it's not the root device)
Online
Ok just to be clear you want me to sleep my original system with a partition of the new disk mounted and then tell what happened?
Almost. Not "tell", "show" - post the journal.
We're lookng for any signs of the nvme acting up (though not critically, since it's not the root device)
update: seemed to be fixed by just reinstalling. but now computer just does not resume and fails to detect my laptop lid opening every 2nd time with the last message being
File systems sync
with some random message about the wifi 30 seconds after i open the lid. also every time i put it to sleep, the usb failing to suspend and the wifi failing to resume even though they work. i tried checking with hw-probe to see the firmware but it was not working.
Last edited by Omarz2012 (Yesterday 17:19:24)
Offline