Announcement

Collapse
No announcement yet.

DVD ISO and USB ISO Will Not Run Live OS

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    DVD ISO and USB ISO Will Not Run Live OS

    I downloaded the 20.04LTS ISO and verified the download with MD5 Hash. Burned a DVD and Bootable USB, but neither one will load the Live OS. I started by booting the system (18.04.4 LTS) with the DVD. The OS is identified on the screen, then goes to a black screen and locks up. Thinking my DVD media is just too old I burned 2 more disks and the same results. Then I burned an 18.04 LTS DVD from the same media spindle and it booted up just fine. Since no one else has posted that the ISO doesn't work, the problem must be on my end.

    Any ideas would be appreciated.
    "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

    #2
    20.04 is 64-bit. Is your CPU 32-bit?
    Windows no longer obstructs my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      How much ram on this system? You need at least 2gb for the live session to be able to load.Since 18.04 is working, I'll say you have at least that much.
      Another old trick with DVD burning is to slow the burn speed down, particularly with older burners or certain batches of disks.

      Not sure if md5sums are still a good way to test, a link to instructions on checking the sha256sums can be found at the bottom of the downloads page
      https://help.ubuntu.com/community/HowToSHA256SUM

      The sha256 sums are here
      https://kubuntu.org/alternative-downloads

      Comment


        #4
        What video card are you using? Is it Nvidia?
        Dave Kubuntu 20.04 Registered Linux User #462608

        Wireless Script: http://ubuntuforums.org/showthread.p...5#post12350385

        Comment


          #5
          You're assuming it's not booting. Could be something relating to hardware or whatever.

          One good way to check the ISO is use it to install to a Virtual Machine. If it works there - the black screen isn't related to the ISO.

          Please Read Me

          Comment


            #6
            O.K, let's start with something you can do. In you current OS, open a konsole and enter:
            Code:
            inxi -Fxxxr
            and post the results here.
            The next brick house on the left
            Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



            Comment


              #7
              Thank you all. Yes I'm hardware compatible. Here's the output from the very interesting terminal command "inxi -Fxxxr" from jglen490:

              Code:
              System:    Host: AMD-64 Kernel: 4.15.0-109-generic x86_64 bits: 64 gcc: 7.5.0
                        Desktop: KDE Plasma 5.12.9 (Qt 5.9.5) dm: sddm,sddm Distro: Ubuntu 18.04.4 LTS
              Machine:   Device: desktop Mobo: ASUSTeK model: M4N98TD EVO v: Rev 2.00 serial: N/A
                        BIOS: American Megatrends v: 1301 date: 04/14/2011
              CPU:       Dual core AMD Phenom II X2 555 (-MCP-) arch: K10 rev.3 cache: 1024 KB
                        flags: (lm nx sse sse2 sse3 sse4a svm) bmips: 12799
                        clock speeds: min/max: 800/3200 MHz 1: 2100 MHz 2: 2100 MHz
              Graphics:  Card: NVIDIA GP107 [GeForce GTX 1050 Ti] bus-ID: 04:00.0 chip-ID: 10de:1c82
                        Display Server: x11 (X.Org 1.19.6 ) drivers: nvidia (unloaded: modesetting,fbdev,vesa,nouveau)
                        Resolution: 3840x2160@60.00hz
                        OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 version: 4.6.0 NVIDIA 390.138 Direct Render: Yes
              Audio:     Card-1 NVIDIA GP107GL High Definition Audio Controller
                        driver: snd_hda_intel bus-ID: 04:00.1 chip-ID: 10de:0fb9
                        Card-2 NVIDIA MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio
                        driver: snd_hda_intel bus-ID: 00:07.0 chip-ID: 10de:0774
                        Card-3 Logitech QuickCam Pro 9000 driver: USB Audio usb-ID: 001-004 chip-ID: 046d:0990
                        Sound: Advanced Linux Sound Architecture v: k4.15.0-109-generic
              Network:   Card: NVIDIA MCP77 Ethernet driver: forcedeth port: c480 bus-ID: 00:0a.0 chip-ID: 10de:0760
                        IF: enp0s10 state: up speed: 1000 Mbps duplex: full mac: f4:6d:04:0f:47:7d
              Drives:    HDD Total Size: 628.1GB (52.9% used)
                        ID-1: /dev/sda model: ADATA_SP600 size: 128.0GB serial: 2F4920012398 temp: 28C
                        ID-2: /dev/sdb model: WDC_WD5000AADS size: 500.1GB serial: WD-WCAV93880239 temp: 28C
              Partition: ID-1: / size: 117G used: 78G (70%) fs: ext4 dev: /dev/sda1
                        ID-2: swap-1 size: 1.07GB used: 0.00GB (0%) fs: swap dev: /dev/zram0
              RAID:      System: supported: N/A
                        No RAID devices: /proc/mdstat, md_mod kernel module present
                        Unused Devices: none
              Sensors:   System Temperatures: cpu: 35.0C mobo: 30.0C gpu: 0.0:37C
                        Fan Speeds (in rpm): cpu: 3125 sys-1: 1713 sys-2: 0
              The sha256 hash of my downloaded iso matches that on the Kubuntu website. I'm going to try another burn using Claydoh's suggestion of slowing down the burn speed instead of using the auto setting. Although not listed in the print-out above, I have a new optical drive that can even burn M-Disks so it may be the issue. Of course that doesn't explain the USB flash drive having the same issue. I'll post the results of the new burn shortly.
              "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

              Comment


                #8
                Wow, what a ride! I think the issue is graphics, either the card (GeForce GFX-1020Ti) or the nVidia drivers. Anyway hitting F9 displayed the installation options for 20.04LTS. What does F9 do anyway, I thought I was pressing F8 for boot options, but as soon as I pressed F9, the screen came up and I was able to install the new OS version.

                Now, when I boot to the SSD with a new 20.04 LTS installation, it doesn't display any graphics from the OS. I get my normal boot up displays, but nothing from the OS. I did hold Shift to get to the grub menu and opened a root terminal. From there I commanded "startx" and I got a rudimentary gui low resolution graphics. From there, I determined that I do not have an internet connection and I can't find any graphics drivers. Perhaps I should have clicked on the 3-party driver installation during the OS install.

                I think I'll try to reinstall to include the 3rd-party software this time. I realize there's probably an easier way to do this, but I'm anxious to get this done so I can start configuring the new OS.
                "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                Comment


                  #9
                  IF you're already booting the machine using grub to any other OS you could just stop making coasters and boot the ISO directly using GRUB

                  Please Read Me

                  Comment


                    #10
                    Well my last "coaster" works. I have 20.04 installed and running. So what does F9 do during the optical drive boot-up? That's what displayed the live DVD screen so I could install.
                    "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                    Comment


                      #11
                      From what you described, F9 bypasses part of the install, but I've never heard of that before. Sounds like maybe if you could have interrupted the Live install process at the initial screen and added the nomodeset boot parameter, it might have helped you through the install. Yes, it sounds like a video card problem.
                      The next brick house on the left
                      Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



                      Comment

                      Working...
                      X