During web surf this day, all ok, Elive asking about update: Ok!
Then after update, if network manager seems ok (by usb or wifi), conky some times gives the IP, sometimes no, and browser says unreachable site, non findable DNS, DNS_PROBE_POSSILE...
At this last update, Elive proposed to update the BIOS/firmware too, where I set, normally, "NO" as can't know exactly what it update...
And on this machine, x230t, since a moment I can't figure out to boot on USB, even with all BIOS settings right for it! Even if all 3 usb ports works ok except that...
The network problems you mention are very unspecific, so can't really help there.
Just so you know: There is no big difference between BIOS and Firmware anymore, so an upgrade might be helpful but .... generally stuff like that happens when the USB drive is faulty or has a bad boot option. Try a different drive and make sure to do a cold boot.
Sometimes even an F12 during boot to check if the drive is actually seen, followed by a refreshing 'Alt,Ctrl, Delete' if it doesn't show.
@Franc -- I have no idea if this is helpful or not, but during my lengthy attempts to install Elive RetroWave, I think I had to disable UEFI mode in my BIOS before it would boot to the USB stick. I have a very old (2011?) Samsung RF711 laptop that I ripped all vestiges of Windows out of, with an internal MBR-only formatted 1TB SSD and an external USB 512GB SSD formatted GPT (so EFI). Many times, for a USB stick to be seen at boot time, I have to disable UEFI (and sometimes actually disconnect the external SSD) .
Also, IIRC, software update of your firmware will only occur when UEFI is enabled, so probably not during an installation of mine as mentioned above!
I saw something similar on another machine (I think the Helix2) but using a freshly burned USB device solved that. No idea why that happens but it's worth a try.
And .... I´d test the specific USB disk with a different form of booting.
Personally I really LOVE ventoy. It allows me to have a large disk with all different distro ISOs on it ands choose which one I want.
That choice including "supergrub boot disk" for installations that botched the grub-install (something that does happen once in a while) and allows me to re-install grub from a running OS.
Specifically Elive requires a double reboot to remove the installer and gets clunky if using 'chroot' on a first reboot.
On top, as itś a large 256Gb disk, I use it as storage for my raspberryPi for movies, pictures, etc.
Another thing that helped me quite often is resetting the BIOS manually through the little pinhole that most laptops have hidden somewhere and then rebooting.
All things considered: Booting a computer is a weird action since it requires software that isn't there yet (initrd) but has to be loaded anyway. The action 'booting' is derived from "lifting yourself up by your bootstraps" i.e actually impossible under normal circumstances .... so have some respect.
Early on, I had a corrupted elive 3.8.52 ISO file, because the downloads didn't finish. Had burned the ISO to USB without knowing this and got the message about not finding the "magic number".
Finding out that the ISO was not complete, I copied the download link and pasted it into a "wget -c [url]" command and let it run to completion. Previously, was using my Vivaldi browser's downloader and it seemed to have failed multiple times (it or the download mirror didn't properly do the pause/restart thing).
With a proper ISO file, the installer fired right up.
Hello!
Isn't a corrupted ISO may not run at all? The one I use works ok if directly (without Ventoy) burned on usb... Except this persistence problem (just on one machine? Can't test right now on an other)...
@triantares : tested on "root" GRUB and GRUB2: same behavior...
Which might be the issue indeed. I don't see how Ventoy can be trusted to get that absolutely right .... especially where it also goes bust on a dedicated USB-drive, sometimes.
Me, I'm licking my wounds after finding that my machine refused to log into any DE from lightdm or any other display-manager.
Going into TTY1, logging in and using 'startx' worked fine, just not the display-manager.
Until I created a new user and discovered that, that did work.
Ultimately, I found there was something wrong with permissions in my .ssh directory. After simply deleting that, it works again but ..... I have no idea how that came about or why DM would crash silently on that.
BTW I never since today tried to write a usb boot key with the one in Elive menu, where I find out that it only wrote a downloaded iso, when I was thinking about writing the as it actual tuned (look, softwares...) daily Elive...
Perhaps a new option to set? @Thanatermesis : Is this thinkable?
