Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been trying unsuccessfully to get Mint 19.1 Xfce running on my USB. I've tried on 3 different thumbdrives and different downloads (in case of a corruption).
It never actually boots all the way and my resulting screen is a cursor line in the upper left of my screen.
I tried to create my live drive using unetbootin (linux) and pendrive (windows).
I could run 18.1 fine.
Is this a known issue? I'm OK running 18.1, but I was looking forward to trying 19.1.
Little disconcerting to me because I downloaded several images from different sources (yeah, I should have verified first, but I've never DLed a bad image before).
I'm currently downloading a new image this time from Ecuador.
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
One thing that I do find useful in ruling out bad USB drives etc. is by booting the iso directly from hdd.
An example from my grub.cfg:
Code:
menuentry "Mint19.1-Cinnamon-ISO" {
set isofile=linuxmint-19.1-cinnamon-64bit.iso
loopback loop (hd1,gpt4)/ISO/$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/ISO/$isofile
initrd (loop)/casper/initrd.lz
}
Obviously you'll need to change the iso filename to suit yours.
Also, the iso location and path.. (hd1,gpt4) is the fourth partition on the second hard drive. The iso file is in /ISO/ here.
If you can place the iso file on a second drive, then you can boot and install to any other drive (but not to the second drive with this method).
Well, looks like my new ISO (with good sha256sum) gives me the same symptoms. Rats.
-----------------
@bodge99,
Interesting solution! Unfortunately, I do not boot to Linux from my HDD. This is live only. From what I'm reading, this solution will only work from a Linux boot partition.
Well, looks like my new ISO (with good sha256sum) gives me the same symptoms. Rats.
-----------------
@bodge99,
Interesting solution! Unfortunately, I do not boot to Linux from my HDD. This is live only. From what I'm reading, this solution will only work from a Linux boot partition.
Any other ideas?
Thanks, All!
Rats indeed. Did you create the USB with Mint's USB Image Writer or with Etcher?
How far do you get along the installation process - do you get any text on the screen at all?
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
It is possible to have grub and one or more ISO's on an external device (hdd, flashdrive, SD card etc.).
I've done this for use on UEFI systems.. It works well for my purposes but would probably be overkill for you at the moment.
The beauty of this method is that nothing needs to be "installed", just copied to a formatted device. You can have as many ISO's on the device as you wish, subject to the device capacity... Configuration is a simple text file, grub.cfg .
If you're interested then I'll look at writing something up.
Another method is: If you have a UEFI MS Windows system and your EFI partition is large enough, it is also possible to manually place the required Grub files into the EFI partition and the ISO on the NTFS partition.. You can then boot the ISO via Grub manually from your EFI shell. This method does not affect the Windows boot mechanism in any way whatsoever. Again, this is probably total overkill for you at this time.
Have you tried booting your Mint flash drive in compatibility mode ??
@hydrurga - I tried both. Etcher worked better. I can boot into the UI, but after a few minutes the UI hangs. (In compatibility mode it works better.) My usual actions after logging in are to connect to Wifi, install Windscribe (using an apt script) and then open FireFox. I'm using Ver 64.0 of FF.
@Bodge99
You suggested that I try compatibility mode. Compatibility mode seems to be working.
I'm not sure what my limitations are with Compat Mode. My understanding is that Compat Mode emulates an earlier version?
Dude, you seem to be a grub guru. I'd love to see a write-up. Because Compat Mode seems to be working, I'm thinking it's not a drive issue.
So now that we know it's working in Compat Mode, I wonder what I should do next.
Thanks for all your help!
Last edited by richdev; 12-24-2018 at 04:58 PM.
Reason: clarifications
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
Hi,
Compatibility mode disables certain "default" optimisations/assumptions about the detected hardware in your computer.
The most relevant other thing for you here is that video hardware is forced to act in a minimal fashion.. i.e. no video acceleration or other card specific "goodies". You'll probably have a restricted range of screen resolution choices at this stage.
At this point, all you need is "some sort" of useable screen. Something that is good enough to allow your installation to proceed.
After everything is installed, you can then look at installing the specific software that you'll need to get proper graphics performance and operation.
If the new installation boots to a black screen or locks up etc. then:
See https://www.linuxmint.com/rel_tessa_xfce.php
esp. the section "Solving freezes during the boot sequence". The "nomodeset" option shown here should allow the newly installed system to boot with a useable screen. You can now look at adding further graphics software/drivers etc.
Before you proceed further, update your system using the Update Manager.
Now try rebooting to see "the state of play". If you could report here, then we can give further instructions/help.
Can you also provide as much info about your computer as possible. Some computers and hardware have "known quirks".
All of this is solvable, but accurate help requires accurate information (as far as possible).
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
As requested:
Direct Linux ISO Boot From Any External Device (external hdd, flashdrive, SD card etc.).
I'll just cover 64-bit UEFI systems, although 32-bit UEFI devices (e.g. earlier Windows tablets) can also be used, with a little modification to the method.
A flashdrive boot is described here, although this method is applicable to just about anything.
It is assumed that the chosen device is accessible from the UEFI firmware at boot time. At a pinch, it's normally possible to work around this with a further slight modification to this procedure (briefly, for example, a SD Card slot that is not supported or initialised by the firmware. The workaround is to place a copy of the required kernel and initrd into the EFI partition. The initrd initialises the SD card slot. Boot control is then passed to the kernel on the SD card to allow a normal boot to complete.)
This method can be seen as an alternative to a pre-written live Linux flashdrive. The main advantage is that multiple ISOs can be kept on the device (subject to device capacity). Yes, O.K. most people will have no need for this at all. I have personally found it useful on more than one occasion.
This may look somewhat difficult to new Linux users.. It really isn't!! Just ask here if there are any queries..
OVERVIEW:
This method boots the iso file directly from a flashdrive or via the computer's UEFI shell using the Grub2 bootloader (64-bit EFI version.).
Just about any version of Linux (32 or 64-bit) can be booted and installed using this specific method.
I'll specifically cover Linux Mint here. Any other distro that uses Casper can use this method directly. Other distros will need slightly different handling. In most cases, trivial adjustments to the Grub configuration file are required to allow this method to work with just about anything.
Software Requirements for 64-bit UEFI:
Grub 64-bit EFI Binaries:
Just extract these directly from the Linux Mint iso file and place them in a temporary directory. The files Bootx64.efi and grubx64.efi can be found in: /EFI/BOOT/ within the ISO file. The utility Midnight Commander can be used to extract these files.
Install it with:
Code:
sudo apt install mc
Grub modules for 64-bit UEFI:
Download grub-efi-amd64-bin_2.02~beta3-4ubuntu7_amd64.deb
Direct Link: http://archive.ubuntu.com/ubuntu/poo...ntu7_amd64.deb
Extract everything in /usr/lib/grub/x86_64-efi and place in {temp dir}/x86_64-efi/ i.e. extract the x86_64-efi directory
and contents.
For those whose firmware doesn't have a built-in internal UEFI shell:
If you want or need to use the "Launch EFI Shell from filesystem device" in the "Save & Exit" screen (or the equivalent in other firmwares).
The filename used for the EFI shell executable is hard-coded into most firmwares that I've seen.. If you get an error message (cannot find..) when attempting to run the EFI shell then the error message may also state the required filename. In this case, simply rename the .efi file to match this requirement.
It would appear that most firmwares specifically look for the EFI shell executable named as "shell.efi" although I've seen a couple that use "shellx64.efi"
I just keep two copies of the same file. One named as "shell.efi" and the other as "shellx64.efi" in the same location.
Copy these two files to /boot/efi (the root of your EFI partition, normally sda1) on your computer.
I also keep a copy of these files on the flashdrive. I can then simply copy them to a computers EFI partition if I need to.
Other Software Requirements:
Linux Mint ISO's: One or more as required.
Create a grub.cfg with your favourite editor.. xed is perfectly fine for this.
The grub.cfg file is a plain text file. A description of the grug.cfg and some further examples can be found in a later post.
Grub Configuration:
This is suitable for Linux Mint XFCE. There are two grub entries here.
The first is for a normal boot, the second uses the nomodeset boot option for those "blank screen" times.
Sample grub.cfg
Code:
menuentry "Mint-Xfce-ISO" {
set isofile=linuxmint-19.1-xfce-64bit.iso
loopback loop (hd0,msdos1)/ISO/$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/ISO/$isofile
initrd (loop)/casper/initrd.lz
}
menuentry "Mint-Xfce-ISO Nomodeset" {
set isofile=linuxmint-19.1-xfce-64bit.iso
loopback loop (hd0,msdos1)/ISO/$isofile
linux (loop)/casper/vmlinuz nomodeset boot=casper iso-scan/filename=/ISO/$isofile
initrd (loop)/casper/initrd.lz
}
USB flashdrive:
Minimum capacity - 2GB. This is enough for one iso file as well as the boot files. An 8GB flashdrive will hold all three Linux Mint 64-bit ISOs plus the boot files.
Boot Flashdrive Preparation:
Format your flashdrive to fat32. Now create the following directories on the flashdrive:
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
Hi,
I've had a quick look online.. It seems that your GPU is not supported by AMD/ATI so you are forced to look at the open source drivers. Your chip-ID: 1002:98e4 given in your earlier post indicates that the GPU is an R5.
As I understand it, this should be directly supported by Mint "out of the box".
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
Another alternative is to keep your working installation "as is" for now and install 19.1 to an external device.
You could use an external hard drive or even a USB flashdrive.
Obviously, the flashdrive option will give lower performance but will allow you to experiment with possible solutions to your graphics problems whilst keeping a useable system.
One further thing to try is booting a Devuan live iso. This doesn't use systemd (yay!!). I find it very fast & stable. It also handles hardware in a more "traditional" manner, so you might get better results for now, until a better solution can be found for Mint 19.1 . It is essentially a fork/partial rewrite of Debian. The devuan_ascii_2.0.0_amd64_desktop-live.iso is approx. 997MB in size.
If you want to use the above flashdrive ISO boot method then here are the grub.cfg entries for the Devuan ASCII Live ISO (with & without the nomodeset option).
Code:
menuentry "Devuan ASCII Live ISO" {
set isofile=devuan_ascii_2.0.0_amd64_desktop-live.iso
loopback loop (hd0,msdos1)/ISO/$isofile
linux (loop)/live/vmlinuz boot=live config findiso=/ISO/$isofile username=devuan
initrd (loop)/live/initrd.img
}
menuentry "Devuan ASCII Live ISO nomodeset" {
set isofile=devuan_ascii_2.0.0_amd64_desktop-live.iso
loopback loop (hd0,msdos1)/ISO/$isofile
linux (loop)/live/vmlinuz boot=live config findiso=/ISO/$isofile username=devuan nomodeset
initrd (loop)/live/initrd.img
}
Bodge99
Last edited by bodge99; 12-26-2018 at 07:58 AM.
Reason: typo
I seem to be stuck on a very rudimentary step here: how to edit the grub file. On the USB, it's a read-only drive. I've tried remounting as per https://askubuntu.com/questions/1757...-as-read-write. But no success.
I used isomaster to extract and re-add the grub file, but that seems to break the "bootablility" of the ISO (when I burn it to the thumbdrive, I get a non-bootable thumbdrive).
I've flailed on a few other ways to edit this, but nothing seems to work well.
I know this doesn't seem like it should be complicated, but I'm stumped. lol
Thanks for all your help!!
Edit:
Based on your comment about compatibility issues, I wonder if this issue could be considered a bug. For what
I do, I could probably live with Compat Mode, but something degraded between 18.1 and 19.1. I'm happy to help the Mint dev team. Thoughts?
Also - I'm DLing Devuan right now. I think I've got 1 more usable USB stick lying around.
Edit2: I think I mentioned it above, but I'm only trying to run Linux Live from the USB drive, I don't want to install it on my HDD. Unfortunately, this probably precludes kernal updates and such. I'm terribly sorry if I wasn't clear about that.
Distribution: Artix, Slackware, Devuan etc. No systemd!
Posts: 368
Rep:
Hi,
I feel your pain..
As you've found out, modding an existing ISO can easily go wrong. I've found that many of the online guides were perfectly fine when they were written, but can quickly become out of date.
You can edit your Grub configuration "on the fly" if you need to. If you can see a grub menu then you can edit it (for the current boot only i.e. it's only temporary and changes are not kept.) Just ask if you want details.
It is possible to modify a live Mint flashdrive to add persistence. (any changes are kept between reboots) but I've found this to be slightly "problematic" at times. The other reason that I personally don't use this method any more is that the working system is now becoming more and more "non-standard" if you know what I mean.
I think that you have a few options on how to proceed:
Give up and stick with your existing installation for now.. At least it's working!
Switch to a different distro (once you're sure that it works properly with your hardware).
If you have the hard drive space, resize your existing installation and install Mint 19.1 as a second OS. You can then experiment on the second OS at your leisure. The new OS is now running on real hardware with the best performance possible for your system.
Install Mint 19.1 to an external flashdrive or other device. Again, you can experiment here with no risk to your existing working system.
I personally would consider a flashdrive or external drive installation if possible. This would allow you to at least perform the actual installation and update procedures etc. The "state of play" at this stage might be slightly different.
I'm asking around locally, to see if I can borrow a laptop which has the same cpu/gpu as yours. I've sure that your graphics support problem is relatively easily solvable. I'd like to see exactly what's going on.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.