Announcement

Collapse
No announcement yet.

Program to create UEFI flash drive to load a UEFI OS onto it

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

    Program to create UEFI flash drive to load a UEFI OS onto it

    Hi sll,

    I hsve been around and around with this issue. I have flash drive. I have a laptop with kubuntu KDE installed. I also have a desktop PC with kubuntu KDE loaded onto it. What I am looking for a is a GUI program that will allow me to create a true UEFI flash drive with a UEFI OS loaded on it.

    Also I just moved into my new place. IT will be a while for internet to be setup. Currently I am running my dektop PC with my phone as a wifi hotspot so a hard wired connection for the laptop will not work

    Any help would be appreciated

    #2
    Others here will chime in with their preferences for a GUI to do this. (I'm skeptical that any of them will actually always work.) In the meantime, I'll drop this--and it sounds like maybe you already heard of it--a method using the command called dd, at a terminal (like Kubuntu's Konsole):

    Building a Kubuntu live USB flash drive installer using dd
    https://www.kubuntuforums.net/showth...712#post378712

    IMO, as far as what I know and have heard, the method using dd is sure-fire, foolproof--unless there is a flaw in the iso file one uses.

    Btw, I'm assuming you mean a live Kubuntu (installer) flash drive.
    An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

    Comment


      #3
      TBH I am afraid I must go back to another OS that works well with the laptop and allows wifi to work. The laptop currently has kubuntu 17. It will not connect to wifi. I do not have internet at the moment and so a hard wired connection is not possible.
      So I must revert to a UEFI OS and install that one to get wifi running... Unless you know a work around to get Ubuntu to recognize wlan0

      Comment


        #4
        If you check the boot log using dmesg you will find that "wlan0" is always renamed to something else. Are you trying to get a wifi device working that doesn't exist?
        On my KDE Neon:
        Code:
        dmesg | grep wlan0
        [   15.034877] ath9k 0000:0d:00.0 wlp13s0: renamed from wlan0
        To use my wifi I must reference wlp13s0, not wlan0.

        Code:
        ~$[B] ifconfig -a[/B]
        enp14s0   Link encap:Ethernet  HWaddr 4c:72:b9:2d:8d:99  
                  BROADCAST MULTICAST  MTU:1500  Metric:1
                  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000 
                  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
        
        he-ipv6   Link encap:IPv6-in-IPv4  
                  inet6 addr: 2001:470:7b:56f::2/64 Scope:Global
                  inet6 addr: fe80::c0a8:b64/64 Scope:Link
                  UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
                  RX packets:244885 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:139252 errors:308 dropped:0 overruns:0 carrier:308
                  collisions:0 txqueuelen:1 
                  RX bytes:296792447 (296.7 MB)  TX bytes:13404673 (13.4 MB)
        
        lo        Link encap:Local Loopback  
                  inet addr:127.0.0.1  Mask:255.0.0.0
                  inet6 addr: ::1/128 Scope:Host
                  UP LOOPBACK RUNNING  MTU:65536  Metric:1
                  RX packets:18319 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:18319 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1 
                  RX bytes:1949903 (1.9 MB)  TX bytes:1949903 (1.9 MB)
        
        sit0      Link encap:IPv6-in-IPv4  
                  NOARP  MTU:1480  Metric:1
                  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1 
                  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
        
        wlp13s0   Link encap:Ethernet  HWaddr 44:6d:57:d6:48:88  
                  inet addr:192.168.11.100  Bcast:192.168.11.255  Mask:255.255.255.0
                  inet6 addr: fe80::3de0:ea66:ba62:daa7/64 Scope:Link
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:644701 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:352656 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000 
                  RX bytes:789626196 (789.6 MB)  TX bytes:57809677 (57.8 MB)
        "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
        – John F. Kennedy, February 26, 1962.

        Comment


          #5
          Originally posted by GreyGeek View Post
          If you check the boot log using dmesg you will find that "wlan0" is always renamed to something else. Are you trying to get a wifi device working that doesn't exist?
          On my KDE Neon:
          Code:
          dmesg | grep wlan0
          [   15.034877] ath9k 0000:0d:00.0 wlp13s0: renamed from wlan0
          To use my wifi I must reference wlp13s0, not wlan0.

          Code:
          ~$[B] ifconfig -a[/B]
          enp14s0   Link encap:Ethernet  HWaddr 4c:72:b9:2d:8d:99  
                   BROADCAST MULTICAST  MTU:1500  Metric:1
                   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                   collisions:0 txqueuelen:1000 
                   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          
          he-ipv6   Link encap:IPv6-in-IPv4  
                   inet6 addr: 2001:470:7b:56f::2/64 Scope:Global
                   inet6 addr: fe80::c0a8:b64/64 Scope:Link
                   UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
                   RX packets:244885 errors:0 dropped:0 overruns:0 frame:0
                   TX packets:139252 errors:308 dropped:0 overruns:0 carrier:308
                   collisions:0 txqueuelen:1 
                   RX bytes:296792447 (296.7 MB)  TX bytes:13404673 (13.4 MB)
          
          lo        Link encap:Local Loopback  
                   inet addr:127.0.0.1  Mask:255.0.0.0
                   inet6 addr: ::1/128 Scope:Host
                   UP LOOPBACK RUNNING  MTU:65536  Metric:1
                   RX packets:18319 errors:0 dropped:0 overruns:0 frame:0
                   TX packets:18319 errors:0 dropped:0 overruns:0 carrier:0
                   collisions:0 txqueuelen:1 
                   RX bytes:1949903 (1.9 MB)  TX bytes:1949903 (1.9 MB)
          
          sit0      Link encap:IPv6-in-IPv4  
                   NOARP  MTU:1480  Metric:1
                   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
                   collisions:0 txqueuelen:1 
                   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          
          wlp13s0   Link encap:Ethernet  HWaddr 44:6d:57:d6:48:88  
                   inet addr:192.168.11.100  Bcast:192.168.11.255  Mask:255.255.255.0
                   inet6 addr: fe80::3de0:ea66:ba62:daa7/64 Scope:Link
                   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                   RX packets:644701 errors:0 dropped:0 overruns:0 frame:0
                   TX packets:352656 errors:0 dropped:0 overruns:0 carrier:0
                   collisions:0 txqueuelen:1000 
                   RX bytes:789626196 (789.6 MB)  TX bytes:57809677 (57.8 MB)
          When I run the above dmesg command I get no response

          Comment


            #6
            Originally posted by Detroit_Bad_Boy View Post
            TBH I am afraid I must go back to another OS that works well with the laptop and allows wifi to work. The laptop currently has kubuntu 17. It will not connect to wifi. I do not have internet at the moment and so a hard wired connection is not possible.
            So I must revert to a UEFI OS and install that one to get wifi running... Unless you know a work around to get Ubuntu to recognize wlan0
            what wireless chip do you have ?

            Code:
            lspci | grep Network
            may tell .

            VINNY
            i7 4core HT 8MB L3 2.9GHz
            16GB RAM
            Nvidia GTX 860M 4GB RAM 1152 cuda cores

            Comment


              #7
              Originally posted by Detroit_Bad_Boy View Post
              When I run the above dmesg command I get no response
              If “dmesg | grep wlan0” (that’s a zero, not an oh) doesn’t show a rename line then your chip is referenced by another name. What is the output of
              ifconfig -a
              ?
              "A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
              – John F. Kennedy, February 26, 1962.

              Comment

              Working...
              X