- This topic has 29 replies, 5 voices, and was last updated Jun 13-12:58 pm by Xecure.
June 4, 2021 at 10:41 am #60936Memberanon
Installed antiX on the dev/sda1 ext3 partition. When enabled in the menu, GRUB tried the first and second items, but in both cases a black screen was displayed. When I pressed the computer shutdown button, for a short moment the screen with the console for entering the login, and then the computer turned off.June 4, 2021 at 11:13 am #60937MemberRobin
Try to change splasht entry in boot parameter line to
or remove the word splash completely from the line while starting.June 4, 2021 at 11:38 am #60938Memberanon
BENQ FP95G LCD Monitor
60 HzJune 4, 2021 at 12:00 pm #60939Memberanon
Where can I find this setting?June 4, 2021 at 1:17 pm #60940MemberXecure
Installed antiX on the dev/sda1 ext3 partition.
1. What version of antiX? For example “antiX 19.4 base x64 runit with 4.19 kernel”. We need to know the antiX edition you installed.
2. With installed, you mean that you already booted with Live USB/DVD before installation and it booted and worked OK? Was this installation on the same computer as the one you are trying to boot?
When enabled in the menu, GRUB tried the first and second items, but in both cases a black screen was displayed.
3. So, you arrive at Grub, which installed properly. Or is this the GRUB menu from a different distro also installed on the same system?
When I pressed the computer shutdown button, for a short moment the screen with the console for entering the login, and then the computer turned off.
4. What are the specs on your computer? This may be important. If you could post the
inxi -Fxzoutput that you see on antiX Live USB/DVD, it may help.
5. If while on the black screen you press the keys Control+Alt+F1, do you see the terminal? And if you Control+Alt+F7 can you get back to a log-i window?
I think this could be related to a graphical driver, but because we don’t know enough about the antiX version, your experience in Live and the computer hardware, it is very difficult to find a possible solution.
When you have time, please provide a bit of info, even if you cannot answer all questions, at least we can start with something more concrete.
June 4, 2021 at 2:16 pm #60945Memberanon
- This reply was modified 1 month, 2 weeks ago by Xecure. Reason: Fixed typo, where I wrote F6 instead of F7
2. yes. yes.
3. GRUB installed correctly
5. I’ll check it out nowJune 4, 2021 at 4:08 pm #60946Memberanon
5. I can’t get back to a log-i window.
I managed to see the terminal. ( Control+Alt+F1 )June 4, 2021 at 4:29 pm #60948MemberXecure
I managed to see the terminal. ( Control+Alt+F1 )
If possible, run this in the terminal (after logging in as your username):
What I am more interested is in the driver information. For example, on my system:
$ inxi -Gxxx Graphics: Device-1: Intel 3rd Gen Core processor Graphics vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0166 Device-2: NVIDIA GF108M [GeForce GT 620M/630M/635M/640M LE] vendor: Acer Incorporated ALI driver: N/A bus ID: 01:00.0 chip ID: 10de:0de9 Display: x11 server: X.Org 1.20.11 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.3.4 compat-v: 3.0 direct render: Yes
What I want is the driver information for the device and for xorg. In your system it is probably something like:
Device: NVIDIA N520 [GeForce GT 520/XXXX] vendor: MSI driver: nouveau
Display: x11 server: X.Org 1.20.11 driver: nouveau
I suspect that driver=vesa or something worse (none)
Now that you are in terminal, edit slim to set autologin just to see if the problem happens only in SLIM or even in a logged-in system:
sudo nano /etc/slim.conf
And change the lines with:
auto_login yes default_user user
where user is where you write your username (if not already there).
Control+O to save, COntrol+X to exit nano.
Then you reboot and see what happens.
June 4, 2021 at 6:12 pm #60954Memberanon
- This reply was modified 1 month, 3 weeks ago by Xecure. Reason: EDIT: change slim to autologin
I removed the sign “#”
then save file.
this did not fix the problemJune 4, 2021 at 6:14 pm #60955Memberanon
ibb.co/D44kdTcJune 4, 2021 at 6:27 pm #60956MemberXecure
Device: AMD Pitcairn XT [Radeon HD 7870 GHz Edition] driver: N/A
If you load the radeon driver
sudo modprobe radeon
See if Control+Alt+F6 or F7
starts slim. If it doesn’t, do from Terminal
If it finally boots add the radeon module to file the /etc/modules
# start radeon driver radeon
So that the radeon module loads at boot time.
It is strange it isn’t starting automatically. Does anyone have an idea why?
June 4, 2021 at 7:35 pm #60962Memberanon
- This reply was modified 1 month, 2 weeks ago by Xecure.
it turned out to run:
I write in the terminal:
sudo modprobe radeon
modprobe: ERROR: could not insert ‘radeon’: invalid argument
# start radeon driver
the problem remainedJune 4, 2021 at 7:41 pm #60966Memberanon
this did not fix the problemJune 4, 2021 at 8:02 pm #60969MemberXecure
There is either a different kernel on your system or antiX 19.3 didn’t install properly (or the ISO was corrupted).
See this, that proves that the radeon module is already there in the antiX kernel for antiX 19.3 base
I recommend you install again, this time using antiX 19.4 and maybe even the edition with kernel 4.19. Also, before installing, check what graphic driver it uses on LIVE, so we can try match it again if there is any graphical problem again on the installed system
inxi -GxxxJune 5, 2021 at 12:04 pm #61013Memberanon
I recorded version 19.4 on a flash drive and started the computer, then the download stopped at the line ” start X”,
then I restarted the system with the splash=v parameter, the result was the same: the boot stopped at the “start X” line, then ( after a couple of minutes ) the yellow dots and the “start X” line disappeared.
I write in the terminal:
the terminal writes: ibb.co/VwdmsvN
- You must be logged in to reply to this topic.