GRUB

[Member macondo]

I installed antiX 17, omitted installing GRUB (I have another distro with GRUB)
rebooted, when did “update-grub” it did not bring it over.

Formatted, installed antix 16.2 and it worked perfectly. IOW, my other distro’s GRUB found antiX 16.2.

antiX Core 64 Bit Runit IceWM

"Sometimes a man finds his destiny on the road he took to avoid it."

[Forum Admin anticapitalista]

Helpful

Up

0

::

I cannot replicate this.
I installed net version to sda1 with grub on MBR, then another net version to sda3 and this time chose not to install grub to MBR (I pressed n).
On reboot, sda1 boots, I run update-grub and reboot.
Grub menu now shows entry for sda3 and it successfully boots.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Moderator Brian Masinick]

Helpful

Up

0

::

Hi Macondo, are you installing on a system with the more recent GPT file system structure and the UEFI boot loader with GRUB EFI (see https://en.wikipedia.org/wiki/GUID_Partition_Table for details), or are you using the older disk systems with the previous PC BIOS conventions, which are supported in the previous GRUB 2 implementation?

antiX 17 ought to be able to support either of them, but it may make a difference to the other distribution in terms of which file systems and formats it recognizes.

I found, for instance, that openSUSE 42 (up to the current 42.3 Leap and openSUSE Tumblewood) know how to recognize all of the distributions I currently have installed, but if I allow PCLinuxOS or Linux Mint – which I believe I installed without explicitly enabling UEFI support – they don’t “see” all of my distributions, and in fact, openSUSE is one of the distributions neither of them seem to “see” when I update the boot loader.

Fedora also seems to “understand” and is able to manage a UEFI-based boot loader in either the secure or insecure form. I’ve found that though most distributions have some degree of UEFI and GPT recognition built in, not very many of them can configure the boot loader 100% correctly without some manual configuration using the efi configuration program.

I’m not sure if this is what is causing your other distribution not to recognize antiX 17, but it *may* be a contributing factor; it’s something I’ve recently experienced as I multi-boot between 5-10 distributions on the same disk.

This may be something worth further investigation and research.

--
Brian Masinick

[Member macondo]

Helpful

Up

0

::

Thank you both, I will burn another copy of antiX.

antiX Core 64 Bit Runit IceWM

"Sometimes a man finds his destiny on the road he took to avoid it."

[Member boombaby]

Helpful

Up

0

::

Hello, Each…

I was going to start a new post with a problem, BUT, I believe that I may be see the same problem as macondo.

Since Antix 16.2 was so good I have been hanging out for the new Antix-17. Maybe I was greedy (and wanted everything) because I downloaded the “FULL” version. [Antix is so good that I wanted to “pig-out” on it – a lot.]

My HP Pavillion laptop is 64 bit, and has a number of partitions – Windows; Swap; and several Linux distros. [Windows is not used.]

When I ran the new DVD (burnt with iso) it got to the install menu but it would not go through to a running system. Not quite correct. The only part I could use was to go into the live menu “Advanced” section and then choose “Failsafe”. Then I got to the “live” desktop and used the “Install” to complete the installation.

Using this method I installed Antix 17 into the old 16.2 partition (formatting it as I went).

On this first try I installed with Grub in an EFI boot-up.

Boot was NO GO. (That is to say, no boot into Antix17. Seemed to complete the install properly but the boot stops after selecting Antix from menu.)

Note that the old multi-boot distro menu (both Mageia and Mint) does not have Antix17 but still shows the old Antix16.2 version – which (of course) won’t boot.

So I tried installing again in 3 different ways (no Grub + EFI; Grub + EFI; Grub on root) but Antix won’t boot. Menu option still shows 16.2

[For background, before my laptop and using 32bit PC, I used Grub pretty well. UEFI and Grub 2 is a little different – and I haven’t spent any time to understand it yet.]

Any advice to complete/fix/redo install?

Regards,
boombaby

[Forum Admin anticapitalista]

Helpful

Up

0

::

If you are using 32 bit iso, UEFI grub install on hard disk won’t work. (BitJam can correct me if I am wrong).
You will have to use legacy grub in your bios or reconfigure grub on Mageia and Mint (update-grub)

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member boombaby]

Helpful

Up

0

::

No, Anticapitalista…

I am now on 64-bit laptop system, so I used the 64-bit ISO.

As far as UEFI goes I can use the laptop EFI menu to boot to either Mageia or Mint (or other distros) but after that it will “fall through” to the last used Grub Menu. In other words I typically use the Mint Menu (or the Mageia Menu or Antix Menu). In this circumstance Antix won’t start.

When you say “update-grub” do you mean I type that in Grub’s command line, or in Linux’s CLI ?

boombaby

[Forum Admin anticapitalista]

Helpful

Up

0

::

In Mint, update-grub in a root terminal should update the Mint grub and include your antiX-17. You can then use this menu to boot antiX.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member boombaby]

Helpful

Up

0

::

Anticap…

It gets complicated.

I did update-grub in Mint terminal. I saw that “Antix-17” was updated. It was only updated in that menu (which appears as “Ubuntu”, not Mint). Mageia and others aren’t updated. [That appears to be a multiboot issue – not Antix. (I think)]

So I can boot via EFI Ubuntu/Mint menu (only).

However, it seems that – since I originally used the DVD “failsafe” boot to a “live” desktop (as described) and installed from there – THAT’S EXACTLY what I have actually installed on HD – a failsafe desktop system (with “install” icon etc).

Also, the User that I added at installation time isn’t recognized now at reboot, and won’t log in. Root logs in OK.

Basic desktop looks like “live” on DVD. No real functionality. Examples: basic fluxbox desktop; “Shutdown” command in terminal wasn’t recognized command – until I used the /sbin reference to it. Etc.)

Rather than fixing this, I am prepared to (and would rather) clean re-install Antix-17 if possible. Why won’t the DVD boot to live NORMAL desktop on my laptop?

Thanks,
boombaby

• This reply was modified 5 years, 6 months ago by boombaby.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Check the md5sum of the iso. Check the integrity of the disk.(You can do this at the live boot menu – F4 – checkmd5)

Also post the inxi -Fxz output so we know about your hardware.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member boombaby]

Helpful

Up

0

::

Will check integrity shortly. Here is inxi detail…

System: Host: mylaptop Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.1)
Distro: Linux Mint 18.1 Serena
Machine: System: Hewlett-Packard (portable) product: HP Pavilion Notebook v: Type1ProductConfigId
Mobo: Hewlett-Packard model: 8093 v: 89.11
Bios: Insyde v: F.03 date: 03/31/2015
CPU: Dual core Intel Core i5-5200U (-HT-MCP-) cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 8779
clock speeds: max: 2700 MHz 1: 2223 MHz 2: 2177 MHz 3: 2084 MHz
4: 2247 MHz
Graphics: Card: Intel Broadwell-U Integrated Graphics bus-ID: 00:02.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1920×1080@60.01hz
GLX Renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2)
GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Audio: Card-1 Intel Wildcat Point-LP High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Card-2 Intel Broadwell-U Audio Controller
driver: snd_hda_intel bus-ID: 00:03.0
Sound: Advanced Linux Sound Architecture v: k4.4.0-53-generic
Network: Card-1: Intel Wireless 3160 driver: iwlwifi bus-ID: 08:00.0
IF: wlo1 state: down mac: <filter>
Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 09:00.0
IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 1000.2GB (4.1% used)
ID-1: /dev/sda model: ST1000LM024_HN size: 1000.2GB
Partition: ID-1: / size: 48G used: 37G (82%) fs: ext3 dev: /dev/sda9
ID-2: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 40.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 195 Uptime: 40 min Memory: 976.9/7905.7MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35

EDITED IN…

At DVD boot menu F4 does not function.

Here is what happens with attempts to use Menu to get to live desktop off DVD (for installing)

After selecting menu option 1 (“Full”)
System seems to be loading itself. [Can see text indicating loading.]
System seems to be setting/resetting resolution. [Resolution going through different settings.]
Get mouse cursor in middle of screen – and is movable.
Then goes to blanked screen with fixed underline cursor at top left corner.
Hung. [Hard stop needs OFF button 4secs]

• This reply was modified 5 years, 6 months ago by boombaby.
• This reply was modified 5 years, 6 months ago by boombaby.

[Forum Admin anticapitalista]

Helpful

Up

0

::

Since F4 doesn’t do anything, it suggests a bad burn.

You boot menu should look something like this.

• This reply was modified 5 years, 6 months ago by anticapitalista.

Attachments:

1. 

   Default_live_boot_menu.png
   

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member boombaby]

Helpful

Up

0

::

Aaa-huhhh!!!

Everything under “Memory Test” is missing.

Now I would have thought the disk could not work at all after that (ie ‘…a bad burn…’). Makes me wonder about tonnes of other distros that did not work for one reason or another.

Thank you, Master!

boombaby.

[Member boombaby]

Helpful

Up

0

::

Hello, Anticapitalista…

Hmmm.

Using k3b and the same ISO I burnt another Antix17. md5 checked OK first.

On boot, same thing. “Live” desktop is complete (stars and all) but below “Memory Test” option all the buttons/options and textbox are non-existent.

So I downloaded another ISO. MD5 checked OK. Burnt another DVD. Booted. SAME OUTCOME. Everything below the Mem Test option aren’t there.

EDIT Just tried Brasero – with same failure.

What now?

Regards,
boombaby

• This reply was modified 5 years, 6 months ago by boombaby.

[Forum Admin BitJam]

Helpful

Up

0

::

@boombaby, the bootloader screen you are describing sounds like it may be our live UEFI bootloader or maybe our installed bootloader. I’ve attached a screenshot of what the live UEFI bootloader looks like. We use Grub for the live UEFI bootloader and the installed bootloader. It doesn’t have the function key menu at the bottom.

Also, your problems with getting the system started seem to be mainly a problem with the graphics driver. We do copy over whatever you did on the live system to the installed system since doing anything else tends to cause extra problems when booting the installed system that didn’t happen on the live system. If you got to X on the live system then by copying that over, you should be able to also get to X on the installed system. Anyway, when you get that blank screen with the blinking cursor, you should be able to get to a virtual console where you can log in with .

Also, have you tried making a live-usb? If you can boot the live-dvd to the command line (see above) then the live-usb-maker program can clone the live system you are running to a usb stick without needing the iso file. It should be very easy.

Attachments:

1. 

   uefi-live-boot.png
   

Context is worth 80 IQ points -- Alan Kay

[Author]

Posts