How much space did you free up for Zorin?
He has a SATA drive, 500 Gigs wiped and clear, he said.
@Aravisian, I have installed Zorin OS onto my PC(Partial Success).
That is because I need to Boot from Grub Menu of Zorin ,SUCCESSFULLY,only after I add ‘nomodeset’ at the end of Kernel line and subsequently pressing Ctrl+X.
The Desktop is UGLY with 1024x768 resolution, WHICH I CANNOT CHANGE.
How do I change it to 1920x1080 resolution??? THIS IS WHAT I NEED AS HELP!!!
natun-athiti, have you upgraded the drivers and kernel after install?
Yessss…
This is one of my snippet …
tabatiti@comparado:~$ su -
Password:
root@comparado:~# xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
root@comparado:~#
I want to get rid of the 1024x768 resolution.
Please save me…
Ok, can you open a terminal and paste in:
xrandr --newmode "1920x1080" 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync
Then do
xrandr -q
Look for your graphics card name. It may be eDP or VGA-1 or HDMI-1 depending on what monitor you have and how it is connected.
Once you have the name, try to add the mode for 1920x1080 res
For Example on My Computer it would look like
xrandr --addmode HDMI-0 1920x1080
Replace the HDMI-0 with your monitor name
Just see this:–>
root@comparado:~# xrandr --newmode “1920x1080” 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync
xrandr: Failed to get size of gamma for output default
root@comparado:~# xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
“1920x1080” (0x2e1) 172.800MHz -HSync +VSync
h: width 1920 start 2040 end 2248 total 2576 skew 0 clock 67.08KHz
v: height 1080 start 1081 end 1084 total 1118 clock 60.00Hz
root@comparado:~#
How do I proceed???
I see you are using su - above.
Do not use a root terminal to perform this operation.
After trying that, let's look to grub:
sudo nano /etc/default/grub
Can you paste the output of that here?
Again failing…
tabatiti@comparado:~$ xrandr --newmode “1920x1080” 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -HSync +Vsync
xrandr: Failed to get size of gamma for output default
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 16 (RRCreateMode)
Serial number of failed request: 19
Current serial number in output stream: 19
tabatiti@comparado:~$ xrandr -q
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected primary 1024x768+0+0 0mm x 0mm
1024x768 76.00*
“1920x1080” (0x2e1) 172.800MHz -HSync +VSync
h: width 1920 start 2040 end 2248 total 2576 skew 0 clock 67.08KHz
v: height 1080 start 1081 end 1084 total 1118 clock 60.00Hz
tabatiti@comparado:~$
Try restarting xserver
killall Xorg
Check to see if it is working.
Again, please paste output of sudo nano /etc/default/grub here
Which drivers are you using currently?
GNU nano 2.9.3 /etc/default/grub
If you change this file, run ‘update-grub’ afterwards to update
/boot/grub/grub.cfg.
For full documentation of the options in this file, see:
info -f grub -n ‘Simple configuration’
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”
GRUB_CMDLINE_LINUX=""
Uncomment to enable BadRAM filtering, modify to suit your needs
This works with Linux (no patch required) and with any kernel that obtains
the memory map information from GRUB (GNU Mach, kernel of FreeBSD …)
#GRUB_BADRAM=“0x01234567,0xfefefefe,0x89abcdef,0xefefefef”
Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
The resolution used on graphical terminal
note that you can use only modes which your graphic card supports via VBE
you can see them in real GRUB with the command `vbeinfo’
tabatiti@comparado:~$ killall Xorg
Xorg: no process found
tabatiti@comparado:~$
I was about to suggest adding the following to grub
GRUB_GFXMODE=1920x1080x32,640x480x32,auto
When I saw this pop up:
You may need to
sudo apt-get install --reinstall xorg
Then enter ttyl with ctrl+alt+F2 and remove the xauthority file from home
rm ~.XAuthority*
rm ~.XAuthority in ttyl gives this,
rm:cannot remove ‘~.XAuthority*’: No such file or directory
Rest of the above commands were successful
Reboot, then check home folder with ctrl+h and see if .XAuthority is present
(Maybe the * was not needed in the above command…)
Rebooting yields this:—>
[1167.861009]systemd-journald[442]:Failed to write entry(21 items,695bytes),ignoring: Read-only filesystem
Cursor blinks indefinitely… 
This means that data was corrupted which could not be mounted at boot- which usually… again… is caused by hardware failure. It does that to prevent further data loss.
All the symptoms above suggest hardware issues, too.
And really, given your machine specs, you should have had No Trouble installing Zorin in the first place.
I am sorry to say this- But I would strongly suggest you check all the hardware involved. It may just be a loose or bad sata drive cable. But I definitely am leaning toward Hardware Troubles of this.
I endorse your views regarding this.
But,Friend,when I am trying to install openSUSE-15.2 Leap (64-bit) version,then how come the installer is running and functioning successfully??? Without any issues whatsoever???
I understand your point. I do not have that answer; I lack enough information.
It may be that OpenSUSE is more forgiving about investigating Hardware whereas Zorin is more strict and investigative.
Or it may be that Zorin is glitching.
But for you, as the controller and user, it still may be best to check all hardware in any case, just to be sure.
Then why Windows 10 and MX-Linux are running successfully? If there is an hardware issue,these OS as a whole should have glitch somewhere along the functioning!
Isn’t that so?