Cannot boot Elive 3.7.14 (alpha) 64 bit

I downloaded the 64 bit edition and burned it to a DVDR disk using xfburn. When trying to boot from said disk it fails at first hurdle.
My system specs are:
System: Host: mx Kernel: 4.15.0-1-amd64 x86_64 bits: 64 compiler: gcc v: 6.3.0 Desktop: Xfce 4.12.3 Distro: MX-18.1_x64 Continuum March 14 2018 base: Debian GNU/Linux 9 (stretch) Machine: Type: Laptop System: Dell product: Latitude E5520 v: 01 serial: <filter> Mobo: Dell model: 03PH4G v: A01 serial: <filter> BIOS: Dell v: A01 date: 04/20/2011 Battery: ID-1: BAT0 charge: 34.5 Wh condition: 66.3/99.9 Wh (66%) model: Samsung SDI DELL 5DN1K3C status: Charging CPU: Topology: Dual Core model: Intel Core i3-2310M bits: 64 type: MT MCP arch: Sandy Bridge rev: 7 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 16763 Speed: 803 MHz min/max: 800/2100 MHz Core speeds (MHz): 1: 828 2: 814 3: 798 4: 798 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.6 direct render: Yes Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k4.15.0-1-amd64 Network: Device-1: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: 7040 bus ID: 02:00.0 IF: wlan0 state: down mac: <filter> Device-2: Broadcom Limited NetXtreme BCM5761 Gigabit Ethernet PCIe vendor: Dell driver: tg3 v: 3.137 port: 7040 bus ID: 0a:00.0 IF: eth0 state: down mac: <filter> IF-ID-1: usb0 state: unknown speed: N/A duplex: N/A mac: <filter> Drives: Local Storage: total: 261.53 GiB used: 5.04 GiB (1.9%) ID-1: /dev/sda vendor: Western Digital model: WD2500LPLX-00ZNTT0 size: 232.89 GiB ID-2: /dev/sdb type: USB vendor: SanDisk model: Ultra size: 28.64 GiB Partition: ID-1: / size: 6.10 GiB used: 7.1 MiB (0.1%) fs: overlay source: ERR-102 ID-2: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 57.0 C mobo: 36.0 C sodimm: 47.0 C Fan Speeds (RPM): cpu: 0 Info: Processes: 212 Uptime: 3m Memory: 7.69 GiB used: 475.4 MiB (6.0%) Init: SysVinit runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.29
I noticed that the iso file had the word hybrid. Does this mean that the image needed to be burned a special way?

Hi @NickStone and welcome to the forum :slight_smile:

First, please verify that the MD5 of your downloaded ISO matches correctly (you have it in the moment of download), this will ensure that the integrity of your download is correct

As you said, the image is "hybrid", this means that it can be used in a DVD or in a USB, the USB is suggested because of speed and reliability

Now, apart of the previously noted:

You can try to select the boot option "debug and verbose" to see if shows any useful information about why it didn't booted, but in any case I suggest to record it in an USB too (instructions are in the download page too)

Where do you get the MD5 sum from? I never received the MD5 sum when downloading the ISO.

its on the download page, when you download the ISO

for the 64bit, 3.7.14 ISO image: f540059dd74fdabdbaeadef0479033b2
for the 64bit, 3.7.16 ISO image: ab9f17ebe6ab4f2d3bab11f469411e16

Thank you for quoting the MD5 sum.

I've checked the sum of the ISO against the ones you quoted and it was completely different.

I won't be downloading the ISO file again due to its size and also your distro has systemd which is something I do not want.

I wish you well in future development of your distro.

A trick from the "old days" of lesser net speed:

You always have the option to use "rsync" and only download the differences between the local and remote copy. That way it isn't a too heavy bandwidth grabber. :smiley14:

That's not an Elive fault but it is how Debian manages the boot system now

I would like to include the support of sysvinit but actually is not yet possible, it is too deeply integrated on Debian Buster @NickStone, you can in fact use sysvinit instead of system, by simply installing later the sysvinit package:

api sysvinit-core

but you will see that is going to remove some needed packages, like:

  • cairo-dock (the included & well-featured dock)
  • network-manager
  • udisks2 / policykit (required for manage mount disks in different applications)
  • dbus, brasero, gksu, gnome-disks, filesystems for the file-manager, etc...

leading to an unusable system

but if you know how to make "a debian buster" system not using systemd, we will be happy to include it :slight_smile:

1 Like