Search Results for 'grub4dos'

[Moderator BobC]

BTW: You can find the different Liquorix kernel packages here: https://liquorix.net/debian/pool/main/l/linux-liquorix/

And here you will find it looks like that force probe I add to mine is required for jasperlake, and the split for elkhartlake from a guy at intel
https://lists.freedesktop.org/archives/dri-devel/2020-October/281872.html

PS: I don’t know if you noticed or not, and don’t know your drive configuration, but Fredx181 confirmed the DD uses an old version of grub4DOS which cannot handle UEFI install, so if you do load DD, don’t install/use its grub if you have UEFI (which is likely if it was a Windows machine). You will probably want to use grub2 (like most distros include) to manage the hard drive boot.

PSS: You could try other distros. Or maybe the “testing” repos have newer kernels and/or code. I suppose you need to dig and try things:
https://askubuntu.com/questions/1362382/how-can-i-change-screen-resolution-with-intel-integrated-graphics-on-atom-x6413

• This reply was modified 4 months, 3 weeks ago by BobC.
• This reply was modified 4 months, 3 weeks ago by BobC.

[Member Irina060]

Using msata solved a couple of issues I had on windows 7. I would prefer to keep the msata at all cost because it is more reliable. Also copying the installer from the live cd works but the installer doesnt recognise the partitions. And gparted doesnt even recognise the ssd. Chroot now doesnt recognise anything. But super grub2 cd recognises both windows xp and 7 which still boot using that utility. Could I install grub4dos from there?
I still havent tried the live usb method with the gfx-cpio.xxx which probably wont work but Im trying everything at this point

[Anonymous]

>> can savestate be used with live CD/DVD?
^-v
quoting download.tuxfamily.org/antix/docs-antiX-19/FAQ/boot-params.html (available via link provided in antixforum headerbar):

savestate (LiveUSB Only)
Save certain “state” files across reboots even without persistence enabled. Also save certain machine-specific state files across reboots. You can control which files get saved by editing the files /live/boot-dev/antiX/state/general-state-files and /live/boot-dev/antiX/state/machine-state-files. Those files and the directory they are in will be created automatically the first time you boot the LiveUSB. This is enabled by default and it is “sticky” so once you enable it it will stay enabled until you turn it off. See below.

nosavestate (LiveUSB Only)
disable saving state files. See description above. This too is sticky so when you use it saving state will stay disabled until you re-enable it.

additional note:
savestate is implicitly ON by default; use the nosavestate boot parameter if you wish to switch it off.

p.s.
This information is also available via the forum search.
It was last parroted to someone who had neglected to read the docs by Xecure, on Dec 11, 2021, within post #72769

• This reply was modified 1 year, 2 months ago by Brian Masinick. Reason: From skidoo

[Member Robin]

ahoppin wrote:

I don’t get any of that when booting with grub4dos, just the usual Linux-booting text-blizzard.

antiX uses syslinux/extlinux/isolinux boot manager when booting from USB or CD/DVD, not grub by default. So it’s expectable you won’t see this screen designed specially for extlinux when using a different boot manager for system startup.

ahoppin wrote:

Even though I don’t have persistence set, some things are being saved behind my back. Specifically, when I entered a static IP/DNS configuration, Antix remembered it on the next live thumb drive boot – again, without persistence being set.

Yes, you are true. There is a specific mechanism storing some basic information on the boot device for convenience if possible.
You will find everything what is stored within the folder
/live/boot-dev/antiX/state
and its subfolders on your boot device. It is partly machine specific.
If I remember correctly, there is a boot parameter to supress the saving of these state info. (Try F1 and search the help docs at antiX boot screen to find the corresponding boot code)

{ EDIT: Just noticed: Xecure (many thanks!) was more precise about this already. So you won’t need to look it up on your own anymore. }

ahoppin wrote:

I also wonder what would happen if I made sdb1 and sdb2 read-only.

For sure, it wouldn’t get saved anymore. This would be equivalent to booting from CD-ROM/DVD, where these convenience information can’t be stored also.

Windows is like a submarine. Open a window and serious problems will start.

[Member olsztyn]

Just an idea, I am not saying I know for sure:
In antiX 19 the boot process had one kernel to boot. In antiX 21 there are two kernels to chose from, from which to boot – 4.9 and 5.10.
I think the default is kernel 4.9, unless 5.10 is saved as default. In the Live composition, both kernels are in antiX folder – one as vmlinuz and the other is named vmlinuz1. I understand the state remembers which kernel is saved to boot, and if there is a mismatch, then you get the message you described.
I will try to re-create similar situation using Ez2Boot, which I think is using Grub4Dos, where I will set a kernel to boot as default, run ISO-Snapshot and add the resulting ISO file to /Linux folder in Ez2Boot as one to boot.
I am just a user, so antiX tech team might be able to provide a more clear answer…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member ahoppin]

Something is clearly different about booting (or trying to) with grub / grub4dos.

When I boot from either the DVD or the thumb drive made with Antix’s official thumb-drive-maker, I get a menu that allows me to choose the kernel (old or new) and boot process (normal, safe video, failsafe).

I don’t get any of that when booting with grub4dos, just the usual Linux-booting text-blizzard.

Could it be that there’s some extra code in the DVD boot sector that’s not getting executed when grub4dos tries to boot the iso contents?

If so, would it be possible to somehow transfer that code to the thumb drive so grub4dos can execute it?

Or maybe grub4dos needs to launch some other executable on the thumb drive.

PS – I just discovered another interesting feature (?) of booting from an “official” thumb drive.

Even though I don’t have persistence set, some things are being saved behind my back. Specifically, when I entered a static IP/DNS configuration, Antix remembered it on the next live thumb drive boot – again, without persistence being set.

And stat /dev/sdb* (sdb is the thumb drive) shows for the thumb drive block dev a modification time which I think is the last shutdown.

I wonder what else is being saved without the user asking it to be.

I also wonder what would happen if I made sdb1 and sdb2 read-only.

Is there a way to boot Antix 21 live with grub4dos?

I mounted the .iso, and copied the files to /antix64_21 on a vfat thumb drive which also boots other live distros including Antix 19.3.

The relevant section of the grub4dos menu.lst:

title Antix 21.0 (antix64_21)
find –set-root –ignore-floppies –ignore-cd /antix64_21/antiX/initrd.gz
kernel /antix64_21/antiX/vmlinuz disable=lxF
initrd /antix64_21/antiX/initrd.gz

This method works with Antix 19.3, but not with Antix 21.0.

I get the following message during boot:

Non-Fatal Error
Kernel version mismatch
Kernel version 4.9.0-279-antix.1=amd64-smp
The module directory /live/linux/lib/modules/4.9.0-279-antix.1=amd64-smp is missing
c = continue
p = power off
r – reboot

Selecting c continues the boot with a note about “using Vesa driver.”

Xwin starts but isn’t usable. See attached photo.

Hardware: Thinkpad T400, non-UEFI, using integrated Intel graphics.

Thanks!

• This topic was modified 1 year, 3 months ago by anticapitalista. Reason: solved

Attachments:

1. 

   antix.jpg
   

Hi, we’re violet spark, among other names we go by on the webs. We got an old lightweight netbook recently to use as a mobile communications device, with 2 gigs of ram and a 32-bit intel atom topping out at a screaming 1.33GHz. We were browsing the ol’ distrowatch trying to find a lightweight 32-bit distro with a similar batteries-included + packages available feel of the ubuntu-derived puppy linuxes, since fossapup is 64bit only now that ubuntu dropped 32-bit. Came across antiX and gosh are we glad we did, its basically exactly what we were hoping for and more!

We decided to go for a traditional install since it’s kinda ram limited. We’ve got a fun setup with grub4dos on a FAT32 partition that’s set to either boot our real system, or the live antiX iso that’s also living on the FAT32 partition for recovery purposes. Finding the 5.10 kernel in the repos was a pleasant surprise too, since thats new enough to give us wireguard as well as the lzo-rle algorithm for zram.

Anyways, happy to be here, thanks everyone involved for creating this. It’s a perfect match for this little computer friend, and we’re using it for some VMs now too.

• This topic was modified 1 year, 6 months ago by violet_spark.

[Member Roberto]

BobC, I have antiX-19full Marielle Franco booting from a iso file in flash drive, it uses grub4dos to boot and suspends to ram normally. Also, I have Linux Mint, Debian jessie, and Porteus-4.0, all them are booted from a iso file by grub4dos and all them suspend to ram without problem. The only distro that do not suspend to ram is antiX-19.3full Manolis Glezos, so I do not believe the problem is grub4dos. I use grub4dos for a long time and never have problem to suspend to ram.

[Moderator BobC]

Do you have any other Debian based distro’s that suspend works for that are also booted from the flashdrive? I would suggest running antiX from a flashdrive made using the live usb maker included, and see if it will suspend from that. If that works then you need to investigate suspending under grub4dos and how to diagnose problems. I can’t help there, but that’s how I would go about it.

[Member Roberto]

fungalnet, I am not using swap. I am using grub4dos to boot the iso file of antiX-19.3 from a flash drive.
Here is my boot lines:

kernel /antiX/vmlinuz fromiso=/_ISO/LINUX/MNU/antiX19.3/32bits/antiX-19.3_386-full.iso desktop=space-icewm desktheme=dark hwclock=local tz=America/Argentina/Buenos_Aires kbd=br quiet splasht disable=lxF
initrd /antiX/initrd.gz

[Member seaken64]

rayluo wrote:

seaken64 wrote:

The antiX system requirements say at least 256MB RAM for the FULL version with 5GB hard disk space. On my computers this seems to be a reasonable minimum. … My installs are between 3.6GB and 4.9GB of hard disk space. That leaves no room for data. I suggest at least 512MB of RAM and a 6GB hard drive or an 8GB USB.

If hard disk space is a concern, will frugal install on hard disk help? It is said to be saving more hard disk space.

Yes, if you only have a 2GB hard drive a frugal install should fit. Both antiX and Puppy do this. I like antiX because it is easy to setup with the current grub. Puppy likes to use Grub4DOS.

If you have a surplus center then it should be pretty easy to get a 6GB or 10GB IDE drive. Pentium 4 and Athlon XP usually support booting from USB so a LiveUSB could work. Maybe a little slower than a frugal install to HD.

Seaken64

[Member liofter]

Hello and thank you for your replies!

Well, I gave Rescatux a try, as Moddit suggested, and it did work!

Here is what happened. Rescatux installed Grub and when I booted, Grub recognised Antix and Windows but not Puppy Linux. So I thought I should try and reinstall Grub4Dos (as it had been untill now) so that I could have also Puppy Linux in the boot menu. But then upon restarting the computer, the same error message appeared and I could not boot into anything. So the conflict is with Grub4Dos but I am not sure what is the cause of the problem.
Anyway, I now have grub installed and (through searching) I managed to have also Puppy in the grub entries.

So, thank you so much for the support! The forum works perfectly well!

[Member 3guesses]

CORRECTION: I am using Grub4Dos not legacy GRUB. Apologies. Otherwise, everything else I have written still applies (mutatis mutandis, as the lawyers would say).

Hi,

I recently downloaded antiX 19 x64 and performed a fresh install into a logical partition formatted to ext4. The install seemed to go fine but then it would not boot – GRUB reported the error:

Error 13: Invalid or unsupported executable format

It took a bit of detective work but eventually I came across this post:

https://web.archive.org/web/20190522142541/https://forum.antergos.com/topic/6097/grub-error-13-invalid-or-unsupported-executable-format

When I had done the antiX 19 x64 install I specified the ext4 file system for the installation partition but I skipped installing GRUB to the MBR as I already had Grub4Dos installed (and configured). The problem was that antiX x64 had formatted the partition to the 64-bit ext4 file system and Grub4Dos only supports the 32-bit ext4 file system – I was able to fix the problem by converting it back to 32-bit ext4 using the following command (from Puppy 8.0 x64):

resize2fs -s /dev/sda6

I would therefore suggest that the antiX 19 installer asks the user whether they want to use the 32-bit or 64-bit ext4 filesystem (with a brief note explaining the implications/potential problems of each) if ext4 is chosen for the installation partition. Might save others some heartache in the future.

• This topic was modified 3 years, 5 months ago by 3guesses. Reason: Added missing details