Booting Live-USB, the wiki page, some thouights, RFC.

English Install/Boot/Login
1

[LEFT]Hi guys, we are at that time in the cycle when lots of keen but inexperienced users are going to be trying openSUSE for the first time, some of them new to linux altogether. Many of them will be using USB sticks, and some no doubt, will refer to this wiki:[/LEFT]
[LEFT]SDB:Live USB stick - openSUSE[/LEFT]
[LEFT]I usually use Imagewriter, but thought I would try another method this time (for no good reason, really, I have learned how to work around the “bug/feature” in imagewriter which makes USB unusable, by using dd).

Here are some thoughts on the wiki page, and some suggestions. I know I can edit wiki pages myself, but I thought best to run it past more expert members of the community first. I would welcome your comments and thoughts.

[/LEFT]
[LEFT]First, the user is sent to the download page for 12.2:
[/LEFT]
[LEFT]Index of /distribution/12.2/iso[/LEFT]
[LEFT]Or[/LEFT]
[LEFT]

 ~> aria2c -x5 http://download.opensuse.org/distribution/12.2/iso/openSUSE-12.2-KDE-LiveCD-x86_64.iso

[/LEFT]
[LEFT]Surely this should be directed to a generic download page, so he can make his choice.[/LEFT]
[LEFT]Secondly, the verification of download seems not to be very clear at all. Surely a simple instruction how-to find the SHA1 checksum, and compare it with the correct one would be preferable here?[/LEFT]

    [LEFT]Verify a download integrity:[/LEFT]
        [LEFT]~> gpg --recv-keys 9C800ACA[/LEFT]
    [LEFT]~> wget http://download.opensuse.org/distribution/12.2/iso/openSUSE-12.2-KDE-LiveCD-x86_64.iso.asc[/LEFT]
    [LEFT]~> gpg -a openSUSE-12.2-KDE-LiveCD-x86_64.iso.asc [/LEFT]


    [LEFT]In the wiki page, we are instructed to "find what device it is" and are offered the following command to do so:[/LEFT]

        [LEFT]~> su[/LEFT]
    [LEFT]# grep -Ff <(hwinfo --disk --short) <(hwinfo --usb --short)[/LEFT]
            

    [LEFT]This seems to be a rather convoluted command, and to a new user completely baffling, containing reversed redirects and parentheses . Surely a simple:[/LEFT]
[LEFT]

 ~> su -
# fdisk -l

would be a better start point?[/LEFT]
[LEFT]If the user has a multitude of USB drives attached, perhaps he should be advised at this point to unplug those not required, until he is 100% sure which he is going to overwrite.[/LEFT]
[LEFT]Next, shouldn’t there be some advice here to format the USB drive as VFAT?

[/LEFT]
[LEFT]When we come to writing our .iso image, we are advised in the text to issue:
[/LEFT]
[LEFT]# dd if=/path/to/downloaded.iso of=/dev/sdX[/LEFT]
[LEFT] But in the accompanying screenshot, the user has used dd_rescue, which could be confusing for our hypothetical noobie, especially as dd_rescue appears not to have a man. He has also, in the screenshot, used a relative path, which could also trip some people up.

[/LEFT]
[LEFT]Also on the wiki there is a suggestion to use:[/LEFT]
[LEFT]live-fat-stick and a link:
[/LEFT]
[LEFT]https://github.com/cyberorg/live-fat-stick[/LEFT]
[LEFT]Ths takes us to github, where it is not immediately clear what to do next, ie how to download the actual script. Should not the link perhaps be to the RAW page:[/LEFT]
[LEFT]https://raw.github.com/cyberorg/live-fat-stick/master/live-fat-stick[/LEFT]
[LEFT]Or better even, a wget command/link to download the script directly, and perhaps even to make it executable?[/LEFT]
[LEFT]Whilst using the live-fat-stick script, it throws a warning:[/LEFT]
[LEFT]/usr/bin/live-fat-stick: line 21: partition: command not found[/LEFT]
[LEFT] This is because of a missing # on that line.[/LEFT]
[LEFT]Also, a typo in “Requires first arguement as iso image path” This should be “argument”[/LEFT]
[LEFT]I don’t know how to do corrections to github things, could someone do those for me please?[/LEFT]

2

On 2013-10-25 15:56, wakou wrote:

There is a dedicated wiki forum here, you should have posted there, I think.

>
> First, the user is sent to the download page for 12.2:
>
>
> ‘Index of /distribution/12.2/iso’
> (http://download.opensuse.org/distribution/12.2/iso/)

Which paragraph?

The first one I see points just to


http://software.opensuse.org/

Ah, I see the paragraph you mean.

> Code:
> --------------------
> ~> aria2c -x5 http://download.opensuse.org/distribution/12.2/iso/openSUSE-12.2-KDE-LiveCD-x86_64.iso
> --------------------
>

That’s just an example. The user has to find the exact link he wants and
write it. It is also the KDE link, so what are the users that want gnome
going to do, despair? :slight_smile:

> Surely this should be directed to a generic
> download page, so he can make his choice.
>
> Secondly, the verification of download seems not to be
> very clear at all. Surely a simple instruction how-to find the SHA1
> checksum, and compare it with the correct one would be preferable
> here?

Well, those are the instructions for the GPG method, which is probably
the best one.

> In the wiki page, we are instructed to “find what device
> it is” and are offered the following command to do so:
>
> Code:
> --------------------
>
> ~> su
>
> # grep -Ff <(hwinfo --disk --short) <(hwinfo --usb --short)
>
> --------------------
>
> This seems to be a rather convoluted command, and to a new
> user completely baffling, containing reversed redirects and parentheses
> . Surely a simple:
>
>
> Code:
> --------------------
> ~> su -
> # fdisk -l
> --------------------
>
>
> would be a better start point?

Probably not.

>
> If the user has a multitude of USB drives attached,
> perhaps he should be advised at this point to unplug those not required,
> until he is 100% sure which he is going to overwrite.

Yes, that is so.

> Next, shouldn’t there be some advice here to format the
> USB drive as VFAT?

No, you do not need to format the device as anything at all.

> When we come to writing our .iso image, we are advised
> in the text to issue:
>
>
> # dd if=/path/to/downloaded.iso of=/dev/sdX
>
> But in the accompanying screenshot, the user has used
> dd_rescue, which could be confusing for our hypothetical noobie,
> especially as dd_rescue appears not to have a man. He has also, in the
> screenshot, used a relative path, which could also trip some people up.

Well, you have a jolly good sight. I have no idea what the screenshot
shows :slight_smile:

Well, a paragraph for using dd_rescue could be added.

> Also on the wiki there is a suggestion to use:
>
> live-fat-stick and a link:

…

> I don’t know how to do corrections to github things, could
> someone do those for me please?

I can’t either.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

3

Thank-you Robin/Carlos… re the screenshot, if you click on it… :slight_smile:
re the gpg thing, perhaps a brief explanation, of what the number is 99C800ACA? Is this a key to a particular source/vendor? Does it change according to which of the .iso files we are downloading? How do we apply it to the file we have downloaded?

~> gpg --recv-keys 9C800ACA
~> wget http://download.opensuse.org/distribution/12.2/iso/openSUSE-12.2-KDE-LiveCD-x86_64.iso.asc
~> gpg -a openSUSE-12.2-KDE-LiveCD-x86_64.iso.asc

Which paragraph?

Create a Live USB (console)

edit] Download and verify LiveCD ISO

Download the installation image of your choice from:

4

On 2013-10-25 17:26, wakou wrote:
>
> Thank-you Robin/Carlos… re the screenshot, if you click on it… :slight_smile:

Oh! Ah! O:-)

> re the gpg thing, perhaps a brief explanation, of what the number is
> 99C800ACA? Is this a key to a particular source/vendor? Does it change
> according to which of the .iso files we are downloading? How do we apply
> it to the file we have downloaded?

That’s the identifier of the key, and it does not change. What changes
is contained in the .asc signature. That is, you have to download the
corresponding .asc file.

There is a key, and with that same key yo can sign many different files…

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

5

Just as a FYI, I found that none of the ways above worked for me. Details here:

https://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/491135-opensuse-13-1-rc1-observations-10.html#post2593477

6

The problems you had with the live USB were due to bug 841426. If you disable secure-boot, it works on some hardware but there are others who find it won’t even boot with secure-boot disabled.

I never tried “live-fat-stick” with a DVD, since it isn’t a live system. Did that get you into the installer? And was that the 32bit DVD or the 64bit DVD? (just curiosity here).

7

Hi Nick, I tried 64 bit KDE live by dd and dd_rescue, did not boot at all, hang at “Loading operating system”
I then tried 64 bit KDE live using live-fat-stick, this boots, loads splash screen, selecting live, loads kernel OK, all very slick and quick. It then hangs after freeing kernel memory and id’ing the USB thumb-drive. It gets stuck after:
(from memory and brief notes)


Attached scsi generic sg0 sd 0.0.0.0
  "         "      "  sg1  sd 0.0.0.0

/usr/bin/klogconsole failed to find MBR identifier
reboot exception
rebooting 120 seconds

I then tried the Full DVD with live-fat-stick. It boots, loads splash, and proceeds to initiate an install. I was not ready for an install, I wanted to run a live session so I aborted that.
I then tried 12.3 KDE live using live-fat-stick. It does the same as the 13.1 and hangs at the same place.

I don’t think that the issues are due to that bug, MSWin 7 or 8 are not on this system

8

It may be apparent that I have no real clue what secure boot actually IS! AFAIK I do not have it, there is no setting in the BIOS relating to “Secure Boot” I just watched this tutorial, presented by Scooter from The Muppets, who appears to have put on a little weight
Windows 8 and Secure Boot - Demo, UEFI, PC, BIOS | TechNet

My BIOS BTW is:


 dmidecode 2.11
SMBIOS 2.4 present.
46 structures occupying 2176 bytes.
Table at 0x000F0100.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: Award Software International, Inc.
        Version: FDe
        Release Date: 05/10/2010
        Address: 0xE0000
        Runtime Size: 128 kB
        ROM Size: 1024 kB
        Characteristics:
                ISA is supported
                PCI is supported
                PNP is supported
                APM is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                5.25"/360 kB floppy services are supported (int 13h)
                5.25"/1.2 MB floppy services are supported (int 13h)
                3.5"/720 kB floppy services are supported (int 13h)
                3.5"/2.88 MB floppy services are supported (int 13h)
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                CGA/mono video services are supported (int 10h)
                ACPI is supported
                USB legacy is supported
                AGP is supported
                LS-120 boot is supported
                ATAPI Zip drive boot is supported
                BIOS boot specification is supported
                Targeted content distribution is supported
9

Sorry Nick, the Full DVD was 64 bit.

openSUSE-13.1-DVD-Build0041-x86_64.iso

10

Well, okay.

Secure-boot only applies to a newer UEFI system. That’s a new kind of firmware to replace the traditional BIOS, though people still call it a BIOS.

Your problem looked like that of bug 841426, which only applies to UEFI systems. So I assumed that you have UEFI. Apparently, I was mistaken about that, and your problem with the live USB is different from what I thought.

As for the “live-fat-stick” – my experience is that the script is confused by 64bit isos, due to the UEFI support that they contain. But maybe there’s a newer version of the script than what I have. I will have to check that.

11

I downloaded the latest version of “live-fat-stick”, and it is now working with 64bit isos.

It’s not much use with the DVD iso. It boots, but it could not find the repos that were there. Maybe there’s a way of coaxing it to find them.

12

On 2013-10-26 10:56, wakou wrote:
>
> Just as a FYI, I found that none of the ways above worked for me.
> Details here:
>
> http://tinyurl.com/lb36a98

Ok… you say there:

> I partitioned and formatted a USB
> thumb-drive to VFAT, and using the instructions in the wiki I
> ran:
>
> Code:
> --------------------
>
> dd if=/home/stephen/bin/openSUSE-13.1-KDE-Live-Build0041-x86_64.iso of=/dev/sdc1
>
>
> ------

But that is wrong.

First, do not partition nor format the stick. Just run the dd line on it

  • and not to sdc1, but plain sdc.

As it is, it can not boot.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

13

Thank you Robin. Surely the partition/format does not make any difference, if the iso overwrites the whole device, including the partition table and boot sector?

I have now successfully made a bootable USB thumbdrive, of the NET-install (and installed it) I have some observations on the whole USB process, I shall perhaps post them elsewhere. I intended this thread for a discussion specifically about the wiki page, and I feel we have strayed a little from that topic, and the forum police will be on us soon!

14

wakou,

Carlos is correct in regards to dd. There is no point to formatting a USB stick if you’re going to use dd. dd doesn’t care about partitions or formats. It simply writes to the disk, over writing partitions and data in the process. You also would not specify a partition, again, since dd doesn’t care about such things. As Carlos said, it’d be just sdc. dd only needs to be pointed to the drive, not the partition. Please see dd(1): convert/copy file - Linux man page and http://en.wikipedia.org/wiki/Dd_(Unix) I think the wikipedia page will be more understandable.

15

On 2013-10-28 06:56, wakou wrote:
>
> robin_listas;2593795 Wrote:

>
> Thank you Robin. Surely the partition/format does not make any
> difference, if the iso overwrites the whole device, including the
> partition table and boot sector?

Right, it is about a waste of time.

However, some think that partition and format works as a method to
recover the usb stick for normal usage after an install.

But doing the dd to sdc1 sure breaks things.

> I have now successfully made a bootable USB thumbdrive, of the
> NET-install (and installed it) I have some observations on the whole USB
> process, I shall perhaps post them elsewhere. I intended this thread for
> a discussion specifically about the wiki page, and I feel we have
> strayed a little from that topic, and the forum police will be on us
> soon!

If you want to talk about the wiki page, please use the wiki forum here.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

16

On 2013-11-01 19:26, Jonathan R wrote:
>
> wakou,
>
> Carlos is correct in regards to dd. There is no point to formatting a
> USB stick if you’re going to use dd. dd doesn’t care about partitions or
> formats. It simply writes to the disk, over writing partitions and data
> in the process. You also would not specify a partition, again, since dd
> doesn’t care about such things. As Carlos said, it’d be just sdc. dd
> only needs to be pointed to the drive, not the partition. Please see
> ‘dd(1): convert/copy file - Linux man page’
> (http://linux.die.net/man/1/dd) and
> http://en.wikipedia.org/wiki/Dd_(Unix) I think the wikipedia page will
> be more understandable.

As a matter of fact, if you specify a partition for the destination of
the write, dd respects the partition and only writes there. It will
destroy the existing “format”: the new format will be whatever is
contained in the source image. And if the partition is smaller, it will
refuse to write beyond it. But, the partition table is not touched when
writing to a partition.

For all those reasons, the procedure should fail to produce a working
bootable usb stick.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)