Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #186301 > unrolled thread

Install on hp-pavilion-g6-2100 stops at 98%

Back to article view | Back to linux.debian.user

Contents

  Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-02 18:30 +0200
    Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-02 19:10 +0200
      Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-02 19:30 +0200
        Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-02 20:00 +0200
          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-02 21:10 +0200
          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 00:10 +0200
            Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-03 01:20 +0200
              Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 02:30 +0200
                Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-03 13:40 +0200
                  Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 14:00 +0200
                    Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-03 14:20 +0200
              Re: Install on hp-pavilion-g6-2100 stops at 98% Curt <curty@free.fr> - 2017-09-03 13:50 +0200
                Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-03 14:30 +0200
            Re: Install on hp-pavilion-g6-2100 stops at 98% Dominique Dumont <dod38fr@gmail.com> - 2017-09-03 10:30 +0200
              Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 11:10 +0200
                Re: Install on hp-pavilion-g6-2100 stops at 98% Dominique Dumont <dod38fr@gmail.com> - 2017-09-03 11:40 +0200
                Re: Install on hp-pavilion-g6-2100 stops at 98% Ben Caradoc-Davies <ben@transient.nz> - 2017-09-03 23:50 +0200
                  Re: Install on hp-pavilion-g6-2100 stops at 98% (SOLVED) Luis Speciale <lspeciale@gmail.com> - 2017-09-04 13:50 +0200
              Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-03 12:00 +0200
                Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 12:30 +0200
                  Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-03 13:20 +0200
                    Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 13:30 +0200
            Re: Install on hp-pavilion-g6-2100 stops at 98% Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-03 12:50 +0200
              Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 13:00 +0200
                Re: Install on hp-pavilion-g6-2100 stops at 98% Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-03 13:30 +0200
                  Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 13:40 +0200
                    Re: Install on hp-pavilion-g6-2100 stops at 98% Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-03 14:10 +0200
                      Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 14:30 +0200
                        Re: Install on hp-pavilion-g6-2100 stops at 98% Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-03 14:50 +0200
                          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 15:10 +0200
                        Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-03 15:20 +0200
                          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 15:30 +0200
                            Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-03 15:40 +0200
                              Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 18:50 +0200
                                Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-03 19:50 +0200
                                  Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-04 13:30 +0200
                                    Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-04 14:10 +0200
                                      Re: Install on hp-pavilion-g6-2100 stops at 98% Cindy-Sue Causey <butterflybytes@gmail.com> - 2017-09-04 18:00 +0200
                                        Re: Install on hp-pavilion-g6-2100 stops at 98% Gene Heskett <gheskett@shentel.net> - 2017-09-04 18:20 +0200
                                        Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-04 18:30 +0200
                                          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-04 19:10 +0200
                                      Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-04 19:00 +0200
                                        Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-04 20:00 +0200
                                          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-04 20:20 +0200
                                            Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-04 20:50 +0200
                                            Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-04 21:10 +0200
                                              Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-04 21:30 +0200
                                                Re: Install on hp-pavilion-g6-2100 stops at 98% Brian <ad44@cityscape.co.uk> - 2017-09-04 22:00 +0200
                                                  Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-04 22:30 +0200
                                          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-04 23:10 +0200
                          Re: Install on hp-pavilion-g6-2100 stops at 98% Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-09-03 15:40 +0200
                  Re: Install on hp-pavilion-g6-2100 stops at 98% "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-03 13:40 +0200
        Re: Install on hp-pavilion-g6-2100 stops at 98% Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-09-02 21:00 +0200
          Re: Install on hp-pavilion-g6-2100 stops at 98% Luis Speciale <lspeciale@gmail.com> - 2017-09-03 10:30 +0200

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

#186357

Hi,

Luis Speciale wrote:
> Consider that what I wrote here it's a transcription and maybe there's some
> bad typing

It will improve the probability of getting help from experts if you
give them the exact strings to search for.

E.g. an amd64 9.1 ISO contains file
  /boot/grub/x86_64-efi/normal.mod
So it would be very significant to know whether the problem message says
indeed:
  /boot/grub/x86_g4-efi/normal.mod


(I assume normal.mod in the /boot tree of the ISO is not the copy
 wanted by grub-update when GNU/Linux is already installed on disk and
 GRUB shall be enabled to boot that disk installation. The wanted file
 would rather have to come from a GRUB package installed on disk.

 But before looking into that, one needs to find out which program
 is actually at endless work.)


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#186358

Le 03/09/2017 à 13:10, Thomas Schmitt a écrit :

>> Consider that what I wrote here it's a transcription and maybe there's some
>> bad typing
> 
> It will improve the probability of getting help from experts if you
> give them the exact strings to search for.
> So it would be very significant to know whether the problem message says
> indeed:
>    /boot/grub/x86_g4-efi/normal.mod

No, it's x86_64-efi. As I said, was a type error.


> (I assume normal.mod in the /boot tree of the ISO is not the copy
>   wanted by grub-update when GNU/Linux is already installed on disk and
>   GRUB shall be enabled to boot that disk installation. The wanted file
>   would rather have to come from a GRUB package installed on disk.
> 
>   But before looking into that, one needs to find out which program
>   is actually at endless work.)
> 
> 
> Have a nice day :)

Yes! You too and thaks for the answer

Luis

[toc] | [prev] | [next] | [standalone]

#186353

Le 03/09/2017 à 00:07, Luis Speciale a écrit :
> 
> sudo dd if=./debian-9.1.0-amd64-netinst.iso of=/dev/disk1 bs=1m

Looks good.

> Then I did the install, but now I have this at startup
> 
> error: file `/boot/grub/x86_g4-efi/normal.mod`not found
> Entering rescue mode...

"x86_g4-efi", really ? Should be "x86_64-efi".

[toc] | [prev] | [next] | [standalone]

#186356

Le 03/09/2017 à 12:43, Pascal Hambourg a écrit :

>> sudo dd if=./debian-9.1.0-amd64-netinst.iso of=/dev/disk1 bs=1m
> 
> Looks good.

Good.

>> error: file `/boot/grub/x86_g4-efi/normal.mod`not found
>> Entering rescue mode...
> 
> "x86_g4-efi", really ? Should be "x86_64-efi".

My bad it's x86_64-efi

Now I think that it's linux.mod my problem, I can't see where it is

When prompted at
grub rescue>

set root=(hd0,gpt2)
	It accepts (it doesn't complain, at least)
insmod /boot/grub/linux.mod
	error: file `/boot/grub/x86_64-efi/normal.mod`not found

Thanks for your answer

Luis

[toc] | [prev] | [next] | [standalone]

#186359

Le 03/09/2017 à 12:58, Luis Speciale a écrit :
> 
>>> error: file `/boot/grub/x86_g4-efi/normal.mod`not found
>>> Entering rescue mode...
>>
>> "x86_g4-efi", really ? Should be "x86_64-efi".
> 
> My bad it's x86_64-efi
> 
> Now I think that it's linux.mod my problem

No it's not. normal.mod comes first. Until this module is loaded, the 
grub rescue command set is very limited.

Please provide the _exact_ output of the following commands :

ls

set

 From the "set" output, I only need the "prefix" and "root" values.

[toc] | [prev] | [next] | [standalone]

#186361

Le 03/09/2017 à 13:22, Pascal Hambourg a écrit :

>> Now I think that it's linux.mod my problem
> 
> No it's not. normal.mod comes first. Until this module is loaded, the 
> grub rescue command set is very limited.
> 
> Please provide the _exact_ output of the following commands :
> 
> ls
> 
> set
> 
>  From the "set" output, I only need the "prefix" and "root" values.

ls gives me

(hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) (hd1) 
(cd0)

set gives me
cmdpath=(hd0,gpt1)/EFI/BOOT
prefix=(hd0,gpt2)/boot/grub
root=hd0,gpt2

Thanks again


Luis

[toc] | [prev] | [next] | [standalone]

#186366

Le 03/09/2017 à 13:32, Luis Speciale a écrit :
> ls gives me
> 
> (hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) (hd1) 
> (cd0)

Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
However ls should show partitions on it. I wonder if the image was 
properly copied. Can you check the partition table on the USB drive ?

> set gives me
> cmdpath=(hd0,gpt1)/EFI/BOOT
> prefix=(hd0,gpt2)/boot/grub
> root=hd0,gpt2

hd0 in these variables means that the firmware booted on the internal 
disk, not the USB drive.

In EFI mode, hd0 is not always the boot drive, unlike BIOS mode.

[toc] | [prev] | [next] | [standalone]

#186370

Le 03/09/2017 à 14:00, Pascal Hambourg a écrit :
> Le 03/09/2017 à 13:32, Luis Speciale a écrit :
>> ls gives me
>>
>> (hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) 
>> (hd1) (cd0)
> 
> Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
> However ls should show partitions on it. I wonder if the image was 
> properly copied. Can you check the partition table on the USB drive ?

I don't see how I can do this. In my Mac, I get
The disk you inserted was not readable by this computer.

[toc] | [prev] | [next] | [standalone]

#186373

Le 03/09/2017 à 14:26, Luis Speciale a écrit :
> Le 03/09/2017 à 14:00, Pascal Hambourg a écrit :
>> Le 03/09/2017 à 13:32, Luis Speciale a écrit :
>>> ls gives me
>>>
>>> (hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) 
>>> (hd1) (cd0)
>>
>> Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
>> However ls should show partitions on it. I wonder if the image was 
>> properly copied. Can you check the partition table on the USB drive ?
> 
> I don't see how I can do this. In my Mac, I get
> The disk you inserted was not readable by this computer.

Never mind. I misread what you wrote and though that you got the error 
when booting from the USB drive. Reading more carefully, I understand 
that the installation process completed without error or freezing and 
you are now rebooting from the internal drive.

cmdpath=(hd0,gpt1)/EFI/BOOT

indicates that the EFI firmware loaded GRUB from /EFI/boot, which 
contains the fallback boot loader. However it should load GRUB from 
/EFI/debian as specified in the EFI boot entry that should have been 
created during the installation of GRUB. Both locations contain the same 
GRUB executable if you replied yes to the question about installing a 
copy of GRUB in the removable device path. Otherwise, EFI/boot may 
contain an obsolete version of GRUB from a previous installation.

$prefix and $root indicate that this GRUB expects its files to be 
located on partition 2, which should be the root partition. You wrote in 
a previous message that this partition contained the system directories. 
What is the output of

ls /boot

If there is a grub directory, what is the output of

ls /boot/grub

[toc] | [prev] | [next] | [standalone]

#186374

Le 03/09/2017 à 14:48, Pascal Hambourg a écrit :
> Le 03/09/2017 à 14:26, Luis Speciale a écrit :
>> Le 03/09/2017 à 14:00, Pascal Hambourg a écrit :
>>> Le 03/09/2017 à 13:32, Luis Speciale a écrit :
>>>> ls gives me
>>>>
>>>> (hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) 
>>>> (hd1) (cd0)
>>>
>>> Obviously hd0 is the internal disk. So hd1 must be the USB drive. 
>>> However ls should show partitions on it. I wonder if the image was 
>>> properly copied. Can you check the partition table on the USB drive ?
>>
>> I don't see how I can do this. In my Mac, I get
>> The disk you inserted was not readable by this computer.
> 
> Never mind. I misread what you wrote and though that you got the error 
> when booting from the USB drive. Reading more carefully, I understand 
> that the installation process completed without error or freezing and 
> you are now rebooting from the internal drive.
> 
> cmdpath=(hd0,gpt1)/EFI/BOOT
> 
> indicates that the EFI firmware loaded GRUB from /EFI/boot, which 
> contains the fallback boot loader. However it should load GRUB from 
> /EFI/debian as specified in the EFI boot entry that should have been 
> created during the installation of GRUB. Both locations contain the same 
> GRUB executable if you replied yes to the question about installing a 
> copy of GRUB in the removable device path. Otherwise, EFI/boot may 
> contain an obsolete version of GRUB from a previous installation.
> 
> $prefix and $root indicate that this GRUB expects its files to be 
> located on partition 2, which should be the root partition. You wrote in 
> a previous message that this partition contained the system directories. 
> What is the output of
> 
> ls /boot
> 
> If there is a grub directory, what is the output of
> 
> ls /boot/grub
> 
> 

When you told me that you thought my USB wasn't maybe ok, I did another 
USB following this instructions this time
https://business.tutsplus.com/tutorials/how-to-create-a-bootable-ubuntu-usb-drive-for-mac-in-os-x--cms-21253

I'm now reinstalling the whole thing

In some minutes I could answer your question

[toc] | [prev] | [next] | [standalone]

#186376

Hi,

Luis Speciale a écrit :
> > > (hd0) (hd0,gpt6)(hd0,gpt5)(hd0,gpt4)(hd0,gpt3)(hd0,gpt2)(hd0,gpt1) (hd1)

Pascal Hambourg wrote:
> > Obviously hd0 is the internal disk. So hd1 must be the USB drive.

Indeed, hd0 has too many partitions to be the unchanged ISO.
The ISO has 2 and no "protective" MBR partition of type 0xee, which would
indicate GPT.

But hd1 has too few partitions. I'd expect GRUB2 to ignore the GPT of the ISO
and maybe the MBR partition 1 of type 0x00. But MBR partition 2 with
type 0xef should show up.

I replay by booting a grub-mkrescue CD-ROM with Debian ISO as payload disk

  qemu-system-x86_64 -enable-kvm -m 512 \
                     -boot order=d -cdrom grub-mkrescue-original.iso \
                     -hda debian-9.1.0-amd64-netinst.iso

It shows on (hd0) : 
  (hd0,apple2), (hd0,apple1), (hd0,msdos2)
I guess apple1 is the APM Block0 aka Driver Descriptor Map. Then apple2
would be the EFI system partition marked by APM partition1, the same as
is marked by msdos2.


> > I wonder if the image was properly copied. Can
> > you check the partition table on the USB drive ?

Maybe it's simply not that USB stick. (I had to lookup man qemu to find out
how to force booting from -cdrom when -hda is bootable, too.)


> I don't see how I can do this.

How many hard-disk-like storage devices does the computer have ?
Would the bootable USB stick be the second or the third "disk" ?
Is it plugged in when GRUB starts ?


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#186377

INTERLUDE (and somehow off topic)

I'm asking myself if it could be a good idea to provide a program (for 
Windows and Mac OS) which could create an USB bootable Debian install.
People who want to try Debian could download this program, insert an USB 
disk, et voilà!

I'm pretty sure that this would significantly increase the number of users!

[toc] | [prev] | [next] | [standalone]

#186378

Hi,

Luis Speciale wrote:
> https://business.tutsplus.com/tutorials/how-to-create-a-bootable-ubuntu-usb-drive-for-mac-in-os-x--cms-21253

This is an ISO unpacking method. Not what is advised by Debian CD people,
but maybe valid, nevertheless.

It depends on what Mac program "hdiutil" does to represent the boot equipment
of the ISO in the new image file, and on whether the result is still similar
enough to the mounted ISO to be usuable for the software which originally
was inside the ISO.


> In some minutes I could answer your question

Possibly it happened already and i still sit in the valley of the clueless.


New mail:
> I'm asking myself if it could be a good idea to provide a program (for
> Windows and Mac OS) which could create an USB bootable Debian install.

The ISO is bootable from USB stick. In Debian it is an achievement of
year 2011. Others were a bit quicker to adopt this feature of the ISOLINUX
boot loader. (GRUB2 can do this too, see grub-mkrescue ISOs for i386/amd64.)

For MS-Windows, the debian-cd project proposes "win32diskimager".
  https://www.debian.org/CD/faq/#write-usb
I have read reports that "Rufus" offers a plain copy mode that is like "dd".
Avoid the offer to unpack the ISO into some other filesystem.
On MacOS, use "dd".


The problem happens much later. Maybe the USB stick plays some role.
But in general i'd expect nowadays as many successful USB stick installations
of Debian as there are via CD or DVD.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#186394

Guess what?

I have a Debian installed with Cinnamon.
I'm beginning to explore it.
I'm a little tired now but I will explain (what I remember) what I did 
tomorrow.

Thank you again to all of you. Without your help I should ended giving up.

Luis

[toc] | [prev] | [next] | [standalone]

#186396

Hi,

Luis Speciale wrote:
> I have a Debian installed with Cinnamon.

Congrats.

> I will explain (what I remember) what I did tomorrow.

Don't forget it.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#186432

Le 03/09/2017 à 19:40, Thomas Schmitt a écrit
>> I will explain (what I remember) what I did tomorrow.
> 
> Don't forget it.



I formated the USB as FAT32 in my iMac

I downloaded the firmware version

firmware-9.1.0-amd64-netinst.iso

Then I did

sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1

When this command finished I had a system message:

"The disk you inserted was not readable by this computer."

and I did

diskutil unmountDisk /dev/disk1

Then all went well. But not the resolution.

So after a little Googling I found this

https://gist.github.com/ed-flanagan/929633981ea548e97f1d

and now it's working like a charm.


And thanks again to all of you


Luis

[toc] | [prev] | [next] | [standalone]

#186434

Hi,

Luis Speciale wrote:
> I formated the USB as FAT32 in my iMac

This would be a preparation for a method that works by unpacking.


> I downloaded the firmware version firmware-9.1.0-amd64-netinst.iso

This could have been the decisive trick. Laptop and the need for
non-free firmware are a known combination.


> sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1

You copy to the device file, not to the mount directory. At least on
GNU/Linux this is like "dd". On MacOS it might differ but it will not
put the ISO as file into the FAT32 fileystem and not unpack the ISO
into the FAT32 filesystem.

I expect that now your self-made FAT32 is gone from the USB stick,
because the partition table was overwritten by the ISO.
Nevertheless, there is again a FAT filesystem, which contains initial EFI
boot equipment of the ISO.


> "The disk you inserted was not readable by this computer."
> diskutil unmountDisk /dev/disk1

Looks like you slightly confused the operating system.
One should unmount the filesystem before overwriting it, not afterwards.


> Then all went well. But not the resolution.
> So after a little Googling I found this
> https://gist.github.com/ed-flanagan/929633981ea548e97f1d

Indeed a firmware issue then. But not solved by the non-free firmware ISO.
Maybe one should file a bug towards that ISO ?
https://wiki.debian.org/Firmware could need an update about Debian 9
and a hint what package is in charge of bugs.

I assume that after equipping your Debian 9 "stretch" with
/etc/apt/sources.list content for Debian 8 "jessie", you have to expect
trouble.
Better return to the original state of that file now.
(If you are in trouble already, better repeat the installation and
 take care to use that "jessie" repository only for getting the firmware,
 and only if you cannot get it from a "stretch" repository.)


I wonder, though, how you could execute apt-get when your installation
did not finish.
Is there some step missing, e.g. how to get to a shell prompt of the
incompletely installed system ?


Whatever: Welcome, fellow Debian user.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#186441

On 9/4/17, Thomas Schmitt <scdbackup@gmx.net> wrote:
> Hi,
>
> Luis Speciale wrote:
>
>> sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1
>
> You copy to the device file, not to the mount directory. At least on
> GNU/Linux this is like "dd". On MacOS it might differ but it will not
> put the ISO as file into the FAT32 fileystem and not unpack the ISO
> into the FAT32 filesystem.
>
> I expect that now your self-made FAT32 is gone from the USB stick,
> because the partition table was overwritten by the ISO.
> Nevertheless, there is again a FAT filesystem, which contains initial EFI
> boot equipment of the ISO.


I'm understanding what you're saying, but then again I might not be
understanding. Are you saying that it looks like he copied straight to
the device instead of to a mount point? That's what I'm understanding
your words to be saying.

I regularly mount partitions to do debootstrap installs so I do
understand that method. That's how I am a-suming this should be done,
too.

All the times I've done that correctly, I have still.... wasted a
ridiculous amount of time... repeatedly... tracking down the... device
name to use when that's not what we use. *smacking my head (in
hindsight)*

That's an important point that I now wonder how often gets missed
versus caught when people are having problems installing to other
media. I know it never crosses my mind to consciously check off that
specific detail when people are writing about their problems. :)

That's also why people trying to help want to know the *exact* steps a
user took to try to do something. The person helping is not being
nosey. Seeing exact details might just help them catch a whoops such
as that device name standing in place of a mount point.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#186442

On Monday 04 September 2017 11:57:19 Cindy-Sue Causey wrote:

> On 9/4/17, Thomas Schmitt <scdbackup@gmx.net> wrote:
> > Hi,
> >
> > Luis Speciale wrote:
> >> sudo cp firmware-9.1.0-amd64-netinst.iso /dev/disk1
> >
> > You copy to the device file, not to the mount directory. At least on
> > GNU/Linux this is like "dd". On MacOS it might differ but it will
> > not put the ISO as file into the FAT32 fileystem and not unpack the
> > ISO into the FAT32 filesystem.
> >
> > I expect that now your self-made FAT32 is gone from the USB stick,
> > because the partition table was overwritten by the ISO.
> > Nevertheless, there is again a FAT filesystem, which contains
> > initial EFI boot equipment of the ISO.
>
> I'm understanding what you're saying, but then again I might not be
> understanding. Are you saying that it looks like he copied straight to
> the device instead of to a mount point? That's what I'm understanding
> your words to be saying.
>
This s/b correct, the iso is an image, complete with filesystem, designed 
to be written to the device starting at LSN0.  IOW, it obliterates 
whatever may have been there before.

> I regularly mount partitions to do debootstrap installs so I do
> understand that method. That's how I am a-suming this should be done,
> too.
>
> All the times I've done that correctly, I have still.... wasted a
> ridiculous amount of time... repeatedly... tracking down the... device
> name to use when that's not what we use. *smacking my head (in
> hindsight)*
>
> That's an important point that I now wonder how often gets missed
> versus caught when people are having problems installing to other
> media. I know it never crosses my mind to consciously check off that
> specific detail when people are writing about their problems. :)
>
> That's also why people trying to help want to know the *exact* steps a
> user took to try to do something. The person helping is not being
> nosey. Seeing exact details might just help them catch a whoops such
> as that device name standing in place of a mount point.
>
> Cindy :)


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#186443

Hi,

Cindy-Sue Causey wrote:
> Are you saying that it looks like he copied straight to
> the device instead of to a mount point?

Yes, i believe it is so.
I cannot be totally sure, because i have no MacOS at hand.
But /dev/disk1 is a whole disk device, according to web and other
confirmations. No Unix puts a file into the filesystem of a disk if
you copy it to the disk device file.
On GNU/Linux, "cp" does the same as "dd" in such a case. It copies the
ISO image bytes plainly onto the disk device, overwriting the partition
table and possibly establishing an own partition table.

This plain copying of the ISO to the disk device is the recommended way
to use a Debian i386 or amd64 installation ISO on a USB stick. 
Unpacking and installing to the hard disk happens by a GNU/Linux system
which gets booted out of the ISO. Either by bootloader ISOLINUX on PC BIOS
firmware, or by bootloader GRUB2 on EFI firmware. Both are ready in the ISO.

So no need to unpack the ISO before booting the USB stick.
There are old instructions around to do so. They might still have a benefit
if you want to boot more than one system from the USB stick.


> I regularly mount partitions to do debootstrap installs so I do
> understand that method.

That's an alternative way to install Debian without a bootable ISO but
rather by help of an already running operating system (must it be a
GNU/Linux ?) and access to a Debian repository.
One could possibly use a Live-CD ISO as such a running operating system.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

Page 2 of 3 — ← Prev page 1 [2] 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web