The “Suggested Partitioning” during install of openSuse 15.3 on a new notebook (ASUS VivoBook) with Windows 10 gives W10 almost all the SSD capacity. I want to reduce W10 and use the disk space for 15.3. But the partitioner does not, in any mode (guided or expert), offer the opportunity to resize partitions. The install docs say there should be a Resize button under the table of partitions on a drive. I have used Resize in earlier versions of openSuse but don’t see it any more.
I want to make this a dual-boot machine so I can’t (don’t know how to) keep W10 when deleting and creating partitions. Am I missing something in the version of the partitioner in 15.3?
Windows can resize itself better than anything else can. Do that and you should have plenty of freespace. If not, go back into Windows and disable the swap file and hibernation, then try again to make it resize itself before trying again openSUSE.
Be sure Windows fast boot is OFF
Also be sure Windows is not using dynamic disk or other LVM like Windows schemes
Thanks for the answers. They fixed my problem. I’m glad someone is tracking Windows now that I’ve ignored it for almost 20 years 
Spoke (wrote) too soon, before the installation had finished. Booting in grub produces the menu to choose openSuse 15.3 or Win10. Selection 15.3 boots to a “localhost login:” and not the GUI sign-in page. Is this a Lin or Win problem?
Thanks in advance.
Lin. Automatic graphics configuration isn’t working right. Please paste here output from
lspci -nnk | grep -A3 VGA
susepaste -n 40320 /var/log/Xorg.0.log
Start new thread with suitable subject. Nobody will look for graphical issues in a thread titled “cannot resize windows partition”.
...# lspci -nnk | grep -A3 VGA
03:00.0 VGA compatible controller [0300]: AMD [AMD/ATI] Lucienne [1002:164cl] (rev c1)
Subsystem: AUSTeK Computer Inc. Device [1043:18721]
03:00.1 Audio device [04031]: AMD [AMD/ATI] Device [1002:1637]
Subsystem: AMD [AMD/ATI] Device [1002:1637]
Susepaste ....
Can't read /var/log/Xorg.0.log
Couldn’t send from the same computer so the above is retyped. AMD is spelled out in the original display.
Technology about 4 years old, so well supported.
Susepaste ....
Can't read /var/log/Xorg.0.log
Couldn’t send from the same computer so the above is retyped.
Did you run susepaste from the installed system? If not, then the correct pathname depends on where the / filesystem was mounted. e.g., if the mount point was /mnt/, then it would be
susepaste -n 40320 /mnt/var/log/Xorg.0.log
If yes, it could be any of:
- X was not installed
- X was never started
- Xorg.0.log was written to ~/.local/share/xorg/ instead
Check whether Xorg..log exists in /var/log/ or ~/.local/share/xorg/ and susepaste what you find. Before doing so, try, logged in as root:
systemctl isolate graphical
startx
Also, as arvidjaar asked, do this in a new thread with an appropriate subject line to entice others to weigh in on your non-working X.
Yes, ran susepaste on the new computer.
Thanks for everyone’s help here. New thread at 556615 about GUI not starting.