Solved Big Problems With Feren OS

Solved issue

lman26

New Member
Joined
Feb 7, 2026
Messages
20
Reaction score
10
Credits
178
I looked and didn't find any posts about this issue. I had Windows 11 and Feren OS on my laptop and I had problems getting Feren to boot. After I entered my PW I would get a black screen and maybe a curser but not always. I got fed up and removed Windows from my hard drive when I re-installed Feron. Everything was fine last night but today when I tried to log into Feren I got the same black screen after entering my PW. I decided to wait and I got the desktop after about 3 min but no curser so I couldn't do anything but reboot. The few times I did get a cursor the laptop would reboot on it's own and I would lose the curser and the task bar. Any idea how to fix this?
 


I looked and didn't find any posts about this issue. I had Windows 11 and Feren OS on my laptop and I had problems getting Feren to boot. After I entered my PW I would get a black screen and maybe a curser but not always. I got fed up and removed Windows from my hard drive when I re-installed Feron. Everything was fine last night but today when I tried to log into Feren I got the same black screen after entering my PW. I decided to wait and I got the desktop after about 3 min but no curser so I couldn't do anything but reboot. The few times I did get a cursor the laptop would reboot on it's own and I would lose the curser and the task bar. Any idea how to fix this?
The first thing you might have a look at are the logs to see if there is anything mentioned there which might explain the odd behaviours. A basic look for errors in the currently booted instance can be found with:
Code:
journalctl -b -p err
To see the errors on the previous booted instance:
Code:
journalctl -b -1 -p err

For a comprehensive look at extracting detail from the journal logs see here: https://www.linux.org/threads/journalctl.61899/

One needs to know what the errors are to address them.

The intermittent nature of the issues described in post #1 suggest that an investigation of the hardware might be useful, that is, check the memory, check the hard drive, all connections. It's probably worth first doing a file check with the fsck command before checking other things in case it's filesystem irregularities or corruption that's implicated.
 
Ok thanks for the info. I will check everything you mentioned.
 
This problem has been resolved by reinstalling the distro. Thanks to everyone who tried to help. SOLVED.
 


Follow Linux.org

Members online


Top