Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Installation issues and concerns

Message
Author
Byteria
Forum Novice
Forum  Novice
Posts: 23
Joined: Wed Jun 13, 2018 10:23 am

Re: Installation issues and concerns

#31 Post by Byteria » Wed Jun 13, 2018 2:37 pm

fehlix wrote:
Wed Jun 13, 2018 1:13 pm
Byteria wrote:
Wed Jun 13, 2018 1:04 pm
Byteria wrote:
Wed Jun 13, 2018 10:38 am
1) In Live MX Linux 17.1 (May 2018 ISO, I think) the graphical installer presented this issue, even trying all F6 options.
I have tried Live options F6: Safe video, Failsafe, nomodeset and modesetting, — some of them, more than once.
Forgive me please, I not fully undestand. Would you mind to explain the issue you had or is it now solved, after the upgrade? Not sure about bothe issue "F6 :Safe video..." and "graphical installer presented this issue".
It's a bitt confusing for me. As not clear what issue you had... :alien: :confused:
Well, I did refer this, at OP's 2nd paragraph:
whatever window or section of a window was floating over the installer window would leave an imprint of itself inside the installer
After select partitions and click "Next", Installer's window doesn't refresh any more. If any other window (e.g. screenshot) covers it, it remains for ever.

Note that I had previously formated these partitions, so it was not needed the Installer to call it at this point (I guess).

I have attached a PrintScreen showing pieces of 3 or 4 windows that remain over Installer's window.

When I said "graphical" Installer, I just meant to distinguish it from "cli-installer".

F6 Options at Boot Menu before Live session refers to #2 above:
The problem is almost certainly caused by the fact that your video card is poorly supported by the nouveau driver.
Using <F6> at the boot screen to select "Safe Video" should allow installation, after which you can install the proprietary nvidia driver using MX Tools
At #3 above:
I gave this a try. The video is certainly in a lower quality now, but sadly it did not fix the issue with the installer.
Even giving a try to all F6 options, I couldn't go after this point.

The issue has not been solved to me, event after a system upgrade in 1 (or+) of those 6 or 8 Live sessions.

What finally allowed to install, was to use "cli-installer" in a Terminal window.

Image

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1150
Joined: Wed Apr 11, 2018 5:09 pm

Re: Installation issues and concerns

#32 Post by fehlix » Wed Jun 13, 2018 3:07 pm

Thanks you for giving me a better picture of you situation.
Remaing question not yet clear to me is:

1 Would running the graphical mx-installer allow you to install having no other application-window open?
2 If you had already prepared the partions, e.g. with gparted, before
you call the mx-installer would run the installer ok, without to manually start partioning
from the installer and again without any other open window?

Thanks

Byteria
Forum Novice
Forum  Novice
Posts: 23
Joined: Wed Jun 13, 2018 10:23 am

Re: Installation issues and concerns

#33 Post by Byteria » Wed Jun 13, 2018 3:43 pm

fehlix wrote:
Wed Jun 13, 2018 3:07 pm
Thanks you for giving me a better picture of you situation.
Remaing question not yet clear to me is:

1 Would running the graphical mx-installer allow you to install having no other application-window open?
2 If you had already prepared the partions, e.g. with gparted, before
you call the mx-installer would run the installer ok, without to manually start partioning
from the installer and again without any other open window?

Thanks
fehlix,

1) I didn't try without any other app-window open, so I cannot tell about it.

2) I really did try with previously formated & labeled partitions, but when I clicke "Next" the Installer's window hangs.

Note that I tryed 6 or 8 times, so it's difficult to say exactly what I did in each o them, unless I would make a complete study.

But the same Installer worked fine in Live antiX, later, in the same day.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9066
Joined: Sun Dec 16, 2007 1:17 pm

Re: Installation issues and concerns

#34 Post by dolphin_oracle » Wed Jun 13, 2018 3:52 pm

the mx-installer was updated with things that got into the antiX installer after the may iso was released, just so everyone knows. They have both been updated now, but up through about 2 weeks ago they were not the same as the new installer got into antiX before we put it in MX repo. They looked the same in the gui, but they were not exactly the same on the backend.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1150
Joined: Wed Apr 11, 2018 5:09 pm

Re: Installation issues and concerns

#35 Post by fehlix » Wed Jun 13, 2018 4:17 pm

Byteria wrote:
Wed Jun 13, 2018 3:43 pm
2) I really did try with previously formated & labeled partitions, but when I clicke "Next" the Installer's window hangs.
Can you remember on which window you clicked "Next" and the installed hangs:
Here the window-sequence as I see it, with having already partions in place prepared.

0. "Terms of Use" and keyboard Settings
1a. Choose disk for installation / 1c. Custom install an existing partition
2. Choose Partition
-> Now a popo-up "OK formating partiton?"
3. Installing in progress : "Copying new system..."
4 Select Boot Method : Install GRUB for Linux ... ->MBR
-> Now PopUp "OK Install Grub bootloader on sda"
-> PopUp Please wait till grub is installed ....
5. Computer Network names
6 Localization Defaults
7 Default User Account
8 Reminders
-> Finish -> Do you want to reboot...

If you do install the next time, would you mind to start the installer from within
a terminal command line with this command:

Code: Select all

sudo -E env LANG=en_US.UTF-8 /usr/sbin/minstall
Within the terminal window you will see the actuall stepp performed.
This migth help us to identify the stepp the install stopped for you.

Below an exampel of in installation I just made:

Code: Select all

$ sudo -E env LANG=en_US.UTF-8 /usr/sbin/minstall

[sudo] Passwort für demo: 
Offer Home Encryption is  "true"
demo@mx1:~/Desktop
$ sudo -E env LANG=en_US.UTF-8 /usr/sbin/minstall
Offer Home Encryption is  "true"
yes
sda2 -     2G - swap - MXswap
Error: device /dev/sda1 is not mounted
sda2 -     2G - swap - MXswap
sfdisk: change-id is deprecated in favour of --part-type

The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
Syncing disks.
mke2fs 1.43.4 (31-Jan-2017)
/dev/sda1 contains a ext4 file system labelled 'rootMX17.1'
	last mounted on / on Mon Jun 11 01:20:57 2018
Creating filesystem with 3661823 4k blocks and 915712 inodes
Filesystem UUID: 1756c15b-0b72-43c5-b9fa-c2c808fdc2f5
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done   

mke2fs 1.43.4 (31-Jan-2017)
/dev/sda1 contains a ext4 file system labelled 'rootMX17.1'
	created on Wed Jun 13 21:59:39 2018
Creating filesystem with 3661823 4k blocks and 915712 inodes
Filesystem UUID: 0da61144-cd87-4b0a-9379-7f149ac77bf0
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done   

  make-fstab: Remove all dynamic entries from /etc/fstab
  make-fstab: Create new /etc/fstab
  make-fstab: Put 1 hard drive entry into /etc/fstab
chroot /mnt/antiX desktop-menu --write-out-global
exit code: 127
"parted -s /dev/sda set 1 boot on"
"grub-install --target=i386-pc --recheck --no-floppy --force --boot-directory=/mnt/antiX/boot /dev/sda"
Installing for i386-pc platform.
grub-install: warning: this msdos-style partition label has no post-MBR gap; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
Exit code:  0
"sed -i -r 's|^(GRUB_CMDLINE_LINUX_DEFAULT=).*|\\1\"quiet video=1600x900\"|' /mnt/antiX/etc/default/grub"
"chroot /mnt/antiX update-grub"
Generating grub configuration file ...
using custom appearance settings
Found background image: /usr/share/backgrounds/MXLinux/grub/MX-Gold1080P.png
Found linux image: /boot/vmlinuz-4.15.0-1-amd64
Found initrd image: /boot/initrd.img-4.15.0-1-amd64
Found memtest86+ image: /boot/memtest86+.bin
done
Exit code:  0
/sbin/make-fstab --install /mnt/antiX
  make-fstab: Create new /mnt/antiX/etc/fstab
  make-fstab: Put 2 hard drive entries into /mnt/antiX/etc/fstab
chroot /mnt/antiX dev2uuid_fstab
# /etc/fstab: static file system information
#
# Created by make-fstab on Wed Jun 13 22:05:19 CEST 2018

# <file system>                            <mount point>                               <type>     <options>                       <dump/pass>

#-> /dev/sda1  label=rootMX17.1
UUID=0da61144-cd87-4b0a-9379-7f149ac77bf0  /                                           ext4       defaults                        1 1
#-> /dev/sda2  label=MXswap
UUID=450ac90d-cb25-488f-83c1-5a7a9ed7fc50  swap                                        swap       defaults                        0 0
DONE!
"chroot /mnt/antiX update-initramfs -u -t -k all"
update-initramfs: Generating /boot/initrd.img-4.15.0-1-amd64
Exit code:  0
umount /mnt/antiX/proc; umount /mnt/antiX/sys; umount /mnt/antiX/dev
hwclock --hctosys
exit code: 0
umount -R /mnt/antiX
exit code: 0
mount /dev/sda1 /mnt/antiX -o defaults,noatime
exit code: 0
sed: can't read /mnt/antiX/etc/skel/.icewm/preferences: No such file or directory
sed: can't read /mnt/antiX/etc/skel/.fluxbox/init: No such file or directory
sed: can't read /mnt/antiX/etc/skel/.jwm/tray: No such file or directory
chroot /mnt/antiX localize-repo default
exit code: 0
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully
cp -a /mnt/antiX/etc/skel /mnt/antiX/home
exit code: 0
mv -f /mnt/antiX/home/skel /mnt/antiX/home/fehlix
exit code: 0
chown -R demo:demo /mnt/antiX/home/fehlix
exit code: 0
umount: /mnt/antiX/proc: not mounted
umount: /mnt/antiX/sys: not mounted
umount: /mnt/antiX/dev/shm: mountpoint not found
umount: /mnt/antiX/dev: not mounted
demo@mx1:~/Desktop
$ 
:snail:
Thanks for your cooperations

Byteria
Forum Novice
Forum  Novice
Posts: 23
Joined: Wed Jun 13, 2018 10:23 am

Re: Installation issues and concerns

#36 Post by Byteria » Wed Jun 13, 2018 6:41 pm

dolphin_oracle wrote:
Wed Jun 13, 2018 3:52 pm
the mx-installer was updated with things that got into the antiX installer after the may iso was released, just so everyone knows. They have both been updated now, but up through about 2 weeks ago they were not the same as the new installer got into antiX before we put it in MX repo. They looked the same in the gui, but they were not exactly the same on the backend.
Thanks delphin_oracle

I will download a newer /the newest ISO and try again.

(Just for reference, antiX was antiX-17.1_x64-full from March, 17).

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9066
Joined: Sun Dec 16, 2007 1:17 pm

Re: Installation issues and concerns

#37 Post by dolphin_oracle » Wed Jun 13, 2018 6:43 pm

Just make sure to update the installer before trying an install.

Code: Select all

sudo apt update 
sudo apt install mx-installer 
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

Byteria
Forum Novice
Forum  Novice
Posts: 23
Joined: Wed Jun 13, 2018 10:23 am

Re: Installation issues and concerns

#38 Post by Byteria » Wed Jun 13, 2018 6:50 pm

fehlix wrote:
Wed Jun 13, 2018 4:17 pm
Byteria wrote:
Wed Jun 13, 2018 3:43 pm
2) I really did try with previously formated & labeled partitions, but when I clicke "Next" the Installer's window hangs.
Can you remember on which window you clicked "Next" and the installed hangs:
Here the window-sequence as I see it, with having already partions in place prepared.

0. "Terms of Use" and keyboard Settings
1a. Choose disk for installation / 1c. Custom install an existing partition
2. Choose Partition

-> Now a popo-up "OK formating partiton?"
3. Installing in progress : "Copying new system..."
4 Select Boot Method : Install GRUB for Linux ... ->MBR
-> Now PopUp "OK Install Grub bootloader on sda"
-> PopUp Please wait till grub is installed ....
5. Computer Network names
6 Localization Defaults
7 Default User Account
8 Reminders
-> Finish -> Do you want to reboot...
..................
:snail:
Thanks for your cooperations
fehlix

the last steps were these:
1c. Custom install an existing partition
2. Choose Partition
After click "Next" in (2), no more reaction and no more refresh within Installer's window.

This happened a all times, in all Live sessions I tryed, with different options.

But I will download the newest ISO and will do as you proposed, next days, and copy here the infos you said.

Note: - The cli-installer worked fine, this week, and now Plasma 5 KDE is almost fine too (Image below). Test will be made with other partitions.

Image

Byteria
Forum Novice
Forum  Novice
Posts: 23
Joined: Wed Jun 13, 2018 10:23 am

Re: Installation issues and concerns

#39 Post by Byteria » Wed Jun 13, 2018 8:37 pm

Just for understand:

here
sudo -E env LANG=en_US.UTF-8 /usr/sbin/minstall
and here
sudo apt install mx-installer
minstall and mx-installer are the same tool?

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 9066
Joined: Sun Dec 16, 2007 1:17 pm

Re: Installation issues and concerns

#40 Post by dolphin_oracle » Wed Jun 13, 2018 9:07 pm

Byteria wrote:
Wed Jun 13, 2018 8:37 pm
Just for understand:

minstall and mx-installer are the same tool?
yes
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

Post Reply

Return to “Installation”