- This topic has 53 replies, 6 voices, and was last updated Jul 1-7:04 am by Klaas Vaak.
-
Posts
-
Klaas Vaak
I tried to replace AntiX with Linux Mint 19, but a normal boot from a live USB is not possible: some text and numbers appear on a black screen, which then starts to flash incessantly and I have to force a shutdown.
A boot in “compatibility mode” is possible, but when I try to install LM, and I get to the “installation type” screen, but not as it should be with 3 options, incl. erase entire disk, Something else. Instead, there was a white empty box with some tabs headed Device, type, Mount point, etc. The tabs are passive, i.e. unclickable.
Below that there are 3 buttons: +, -, and Change.
Below that the “Device for boot loader installation”, showing /dev/sda
Below that 3 buttons: Quit, Back, Install.
Whether I click on the Change button or the Install button, I get a pop-up message box saying the installer has crashed !!!!I tried several times, and each time the result was the same. I get the impression that AntiX is baked into the hard drive forever and cannot be removed anymore. I cannot believe that that is the case, but this odd behaviour is not what I expected from AntiX.
- This topic was modified 3 years, 11 months ago by rokytnji.
- This topic was modified 3 years, 11 months ago by rokytnji.
dolphin_oracle
I think there is something wrong with your mint download…mostly because you can’t boot the way you expect from the live-usb, which would have nothing to do with antiX.
I’ve got 2 machines that use emmc devices, and I cannot replicate this behavior. I haven’t installed mint, but I have installed ubuntu and peppermint on those devices, after an antiX install.
Xecure
I tried to replace AntiX with Linux Mint 19, but a normal boot from a live USB is not possible: some text and numbers appear on a black screen, which then starts to flash incessantly and I have to force a shutdown.
…
I get the impression that AntiX is baked into the hard drive forever and cannot be removed anymore. I cannot believe that that is the case, but this odd behaviour is not what I expected from AntiX.
Dear user, I have installed antiX many times in my emmC drive inside my cheap chinese tablet, and also an Ubuntu based linux distribution. I would always wipe out the disk first.
Try ANY of these different steps:
a) Try to unmount the antiX partitions using Gparted and see what options the Linux Mint installed offers, to see if something has changed.
b) If you are sure you no longer want antiX, use Gparted to unmount and delete the partitions antiX created in your system.
c) If you know exactly what new partitions you want your Linux Mint system to use, delete all unwanted partitions and create and format the new ones (also using the Gparted application).I will download Linux Mint 19 64 bits and test to see what options you are talking about, but you will have to wait some hours as I need to download it first.
Try to see if you can unmount the antiX partitions in the Linux Mint Live environment and then try to install again. In a few hours I will get back to you.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.@Xecure: many thanks for your reply. I considered using GParted but had this thought: if I download GParted with AntiX, is it possible to delete the AntiX partition considering that GP itself will be located on it?
As for wiping the partition 1st, during the installation process LM offers the choice of wiping the disk entirely or installing alongside the existing OS. Would it not be simpler to let LM do the wiping while being installed?
Sorry to ask such basic questions, but I am a Linux newbie and nervous about messing with an OS.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
Xecure
@xecure: many thanks for your reply. I considered using GParted but had this thought: if I download GParted with AntiX, is it possible to delete the AntiX partition considering that GP itself will be located on it?
Only format from a live environment, not from the installed system (and Gparted is included in, at least, the antiX base flavor). The Linux Mint live environment should also have Gparted application included, so it should also be easy to do it from there.
As for wiping the partition 1st, during the installation process LM offers the choice of wiping the disk entirely or installing alongside the existing OS. Would it not be simpler to let LM do the wiping while being installed?
Yes, that is also an option.
I have downloaded Linux Mint 19.1 XFCE 64 bits. Once I have it on a usb device, I will try to see what happens.
- This reply was modified 3 years, 11 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Only format from a live environment, not from the installed system (and Gparted is included in, at least, the antiX base flavor). The Linux Mint live environment should also have Gparted application included, so it should also be easy to do it from there.
I tried from the live environment, but GP only detects the stick it is on, it does not detect the eMMC drive.
I have downloaded Linux Mint 19.1 XFCE 64 bits. Once I have it on a usb device, I will try to see what happens.
I might not answer immediately.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
Xecure
I tried from the live environment, but GP only detects the stick it is on, it does not detect the eMMC drive.
It is amazing to me to see that Linux Mint cannot detect the eMMC drive in a computer with a UEFI firmware. But it seems to be true!
I have experienced a similar thing to you. I booted Linux Mint 19.1 Xfce in the same conditions I did with antiX and Xubuntu, and the first option in the menu did not boot. I waited for over 15 minutes, and the only thing it did was display the Linux Mint logo and a four dot animation. I restarted and selected the compatibility mode, as you did.
Once booted, I tried Gparted to see what drives were detected, and to my surprise, only the USB device was detected! I proceeded to the install program to confirm that it wasn’t only Gparted, but the installation media could not detect the eMMC device. I made a google search and someone else shared the same experience.I was going to proceed to test if I could make it all work changing the options in the “BIOS utility”, but I thought it is not worth it. antiX can boot perfectly on UEFI, why cant this too? This only proves the superiority of antiX to me.
I recommend you try Xubuntu instead, as I have already installed a flavor of Xubuntu on this device in the past.
I can only congratulate the antiX team for creating a so easy to boot and install system. Linux Mint can go crying away with their thousands in donations, as they have an inferior product in comparison to what the antiX team has achieved.
- This reply was modified 3 years, 11 months ago by Xecure.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
rokytnji
Without some blkid and fdisk -l and parted -l commands. Kinda hard to tell you what and what not to delete when it comes to these newer laptops .
As I learned when I did this on my wifes broke windows touchscreen laptop.
https://forum.mxlinux.org/viewtopic.php?f=107&t=50525
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsXecure
MX will probably have no problems at all, but as the OP didn’t consider it and was asking for an Ubuntu derivative, I recomended Xubuntu instead.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.I have experienced a similar thing to you. I booted Linux Mint 19.1 Xfce in the same conditions I did with antiX and Xubuntu, and the first option in the menu did not boot. I waited for over 15 minutes, and the only thing it did was display the Linux Mint logo and a four dot animation. I restarted and selected the compatibility mode, as you did.
Once booted, I tried Gparted to see what drives were detected, and to my surprise, only the USB device was detected! I proceeded to the install program to confirm that it wasn’t only Gparted, but the installation media could not detect the eMMC device. I made a google search and someone else shared the same experience.
,/blockquote>Thanks for confirming that others had the same problem with Mint and an eMMC. I agree that that is a serious shortcoming.
I recommend you try Xubuntu instead, as I have already installed a flavor of Xubuntu on this device in the past.
OK, my story is a bit longer. After failing to install Mint I tried to install Xubuntu (this was before I contacted this forum), but I got the same flashing black screen with some text and numbers at the start, so I did not pursue it.
I can only congratulate the antiX team for creating a so easy to boot and install system. Linux Mint can go crying away with their thousands in donations, as they have an inferior product in comparison to what the antiX team has achieved.
I will reserve my judgment on that till I get this sorted out, because not being able, it seems, to remove AntiX does not ring right either.
Sorry for a not-quite-right formatting of this reply.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
MX will probably have no problems at all, but as the OP didn’t consider it and was asking for an Ubuntu derivative, I recomended Xubuntu instead.
OK, here is the full story. I was happy with AntiX, having used it 1st in a VM on a Windows host, I installed it on my little hybrid. The only thing that annoys me is a scrolling issue, that I have not been able to resolve, despite advice from various people on this forum.
So, having got fed up, I decided to ditch AntiX and install another distro. After the failed installs of Mint and Xubuntu I considered MX, since I know that one too and it is one of the most popular distros, with Mint BTW. The only concern I have is that since it is based on AntiX, would I not be confronted with that scrolling issue again?
For now, my immediate problem is the AntiX “baked-in” issue and how to solve that.
Without some blkid and fdisk -l and parted -l commands. Kinda hard to tell you what and what not to delete when it comes to these newer laptops .
This is a long list:
blkid /dev/mmcblk0p1: UUID="64A5-7D5C" TYPE="vfat" PARTLABEL="ESP" PARTUUID="4373a9ca-1cf9-4b1b-8c05-494338bb4f68" /dev/mmcblk0p2: LABEL="rootantiX17.1" UUID="c3a4d07b-cdcf-4a2a-bebf-8d735153e464" TYPE="ext4" PARTLABEL="primary" PARTUUID="f2c17e23-253a-407e-809a-915704b637b9" /dev/mmcblk0p3: LABEL="antiXswap" UUID="4bfdd799-2339-409a-ade2-f6a6af5c0d72" TYPE="swap" PARTLABEL="primary" PARTUUID="621588f1-81b2-44e9-851d-29d53ef15333" fdisk -l Disk /dev/ram0: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram1: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram2: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram3: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram4: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram5: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram6: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram7: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram8: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram9: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram10: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram11: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram12: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram13: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram14: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/ram15: 16 MiB, 16777216 bytes, 32768 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mmcblk0: 29.1 GiB, 31268536320 bytes, 61071360 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: CF36C4BD-4EF2-4729-8B72-3207D90CD93A Device Start End Sectors Size Type /dev/mmcblk0p1 34 524287 524254 256M EFI System /dev/mmcblk0p2 524288 17301503 16777216 8G Linux filesystem /dev/mmcblk0p3 17301504 21495807 4194304 2G Linux filesystem Disk /dev/sda: 125 MiB, 131072000 bytes, 256000 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type /dev/sda1 * 32 255999 255968 125M 6 FAT16As for parted -l: see next page.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
- This reply was modified 3 years, 11 months ago by Klaas Vaak.
Anonymous
retry
sudo parted -lrokytnji
Like. I would not delete
Device Boot Start End Sectors Size Id Type /dev/sda1 * 32 255999 255968 125M 6 FAT16partition just for starters. Installer has a option to install grub to that partition to boot the new install of MX. As I found out when I deleted mine and tried the install grub to mbr on sda instead.
I feel like changing this topic title this morning also. This baked in crap needs a professional dish washer.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsrokytnji
Oh yeah. Mint is hybrid iso. DD command can burn a usb . No mention of md5sum check made of mint iso also in this thread, I think? Early morning here and I am not awake yet.
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problems
- You must be logged in to reply to this topic.
