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 3 of 3 — ← Prev page 1 2 [3]

#186446

Le 04/09/2017 à 18:27, Thomas Schmitt a écrit :
> 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.

That's what I think too. That's maybe also the reason why I had the 
message "The disk you inserted was not readable by this computer." at 
the end of the cp command. My iMac did not understood the animal


> 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]

#186445

Le 04/09/2017 à 14:05, Thomas Schmitt a écrit :

I don't understand some things you wrote, so I'll mark this items by a 
question mark…

>> 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.

Good!

>> 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.

My bad. I forgot that before the cp command I unmonted de disk. The 
system saw it after that the command ends and asks what to do with the 
stranger

> 
>> 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 ?

I don't know what to say. I believe that it must be a myriad of firmwares

> 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.

I forgot to tell that I omited this jessie part. I only did
apt-get update
apt-get install firmware-realtek
apt-get install firmware-linux-nonfree

> 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 ?

Sure thing. I spend all my weekend in a fierce battle with this monster 
and I was near (a couple of times) of giving up.

> Whatever: Welcome, fellow Debian user.

Yes, you can call me that now!

Thanks for your answers

Luis

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

#186447

Hi,

i wrote:
> > This would be a preparation for a method that works by unpacking.

Luis Speciale wrote:
> ?

There are two ways to bring a bootable ISO onto a USB stick:

- The old way is to create a partition with a filesystem (FAT32 is not
  the best choice because it has so poor filenames),
  to copy the files out of the ISO into the created filesystem,
  and to install a boot loader which starts the same programs as the boot
  loader in the ISO would do if the ISO gets booted from a DVD.
  This needs knowlege about how the software in the ISO works. So you
  normally find instructions for a particular GNU/Linux distro like
  Debian, Ubuntu, Fedora, OpenSuSE, Arch, Gentoo, ...

- The new way needs a hybrid ISO image with a Master Boot Record and a
  partition table with EFI system partition. These two structures get used
  by PC BIOS or EFI, respectively, when they encounter the ISO on a hard
  disk or USB stick.
  To become recognizable by the firmware, the MBR has to sit at block 0
  of the disk or USB stick. It also hosts the partition table or the
  indication that there is a GUID partition table (GPT). So both firmwares
  demand that the ISO image copy begins at block 0.
  Thus the ISO needs to be copied onto the overall disk device file,
  not onto a disk partition device file, and especially not into the
  directory where some filesystem of the USB stick is mounted.
  No filesystem of the USB stick should be mounted when it gets overwritten,
  because afterwards its old data are likely to be gone.


> > 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.

> ??

By using the second way, you overwrote the MBR and partition table of the
USB stick. So now it bears the MBR and partition table of the ISO.
The partition table of the ISO contains this

  $ /sbin/fdisk -l firmware-9.1.0-amd64-netinst.iso
  
  Disk firmware-9.1.0-amd64-netinst.iso: 325 MiB, 340787200 bytes, 665600 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7db1c45b

  Device                            Boot Start    End Sectors  Size Id Type
  firmware-9.1.0-amd64-netinst.iso1 *        0 665599  665600  325M  0 Empty
  firmware-9.1.0-amd64-netinst.iso2       3984   4815     832  416K ef EFI (FAT-12

Partition 1 can be used to mount the ISO. Its type 0 = "Empty" is
a necessity of our crammed hybrid ISO. We need to please EFI firmware.

As you can see, partition 2 is a FAT12 of type 0xef = "EFI". Let's have a
look into it:

  $ sudo mount -o loop firmware-9.1.0-amd64-netinst.iso /mnt/iso
  mount: /dev/loop0 is write-protected, mounting read-only

Being involved expert, i know that /boot/grub/efi.img is the ISO filename
of the data file which is marked by partition 2:

  $ sudo mount -o loop /mnt/iso/boot/grub/efi.img /mnt/fat

(There are ways to find out the name or to mount it by its partition info.)

Now i can list the files in the FAT filesystem

  $ find /mnt/fat
  /mnt/fat
  /mnt/fat/efi
  /mnt/fat/efi/boot
  /mnt/fat/efi/boot/bootx64.efi

So the FAT12 filesystem contains just the single data file which EFI will
look for on a amd64 machine, normally known by its DOS name:
  \EFI\BOOT\BOOTX64.EFI

This file was made by program grub-mkimage. Its only purpose is to find
the device on which the ISO is presented and to load and start the GRUB2
configuration in the ISO directory /boot. At its end one can see these
GRUB2 configuration commands as human readable text:
  search --file --set=root /.disk/info
  set prefix=($root)/boot/grub
  source $prefix/x86_64-efi/grub.cfg
  (memdisk)/boot/grub
The existence of file /.disk/info is considered a unique property of the
Debian ISO (Steve: Is this really good enough ?). So the first filesystem
with that file gets used as source of further GRUB brain.
The starting point of that brain is file
  /mnt/iso/boot/grub/x86_64-efi/grub.cfg
which loads
  /mnt/iso/boot/grub/grub.cfg
In there you will find texts which you also can see in the first menu
of the booting Debian ISO:
  menuentry --hotkey=g 'Graphical install' {
  menuentry --hotkey=i 'Install' {
  submenu --hotkey=a 'Advanced options ...' {
  menuentry --hotkey=s 'Install with speech synthesis' {

Let's revoke "sudo mount" before we go on:

  $ sudo umount /mnt/fat
  $ sudo umount /mnt/iso


> I forgot to tell that I omited this jessie part. I only did
> apt-get update
> apt-get install firmware-realtek
> apt-get install firmware-linux-nonfree

First:
Very very good you skipped the reference to the old-stable system.
Obviously the non-free-firmware ISO already is prepared to use the
non-free repository of Debian 9.

Second:
I understand you got no good graphics but were able to enter shell
commands like apt-get.
Right ?
(Your previous reports stated that installation hung at some late stage.)


> I was near (a couple of times) of giving up.

That's a good sign. If it does not offer resistence then it s not worth.

As software developer i am always mistrusting if a new feature does not
show buggy behavior on the first test. Then it hides something evil ...


Have a nice day :)

Thomas

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

#186448

Le 04/09/2017 à 19:56, Thomas Schmitt a écrit :
> Hi,
> 
> i wrote:
>>> This would be a preparation for a method that works by unpacking.
> 
> Luis Speciale wrote:
>> ?
> 
> There are two ways to bring a bootable ISO onto a USB stick:
> 
> - The old way is to create a partition with a filesystem (FAT32 is not
>    the best choice because it has so poor filenames),
>    to copy the files out of the ISO into the created filesystem,
>    and to install a boot loader which starts the same programs as the boot
>    loader in the ISO would do if the ISO gets booted from a DVD.
>    This needs knowlege about how the software in the ISO works. So you
>    normally find instructions for a particular GNU/Linux distro like
>    Debian, Ubuntu, Fedora, OpenSuSE, Arch, Gentoo, ...
> 
> - The new way needs a hybrid ISO image with a Master Boot Record and a
>    partition table with EFI system partition. These two structures get used
>    by PC BIOS or EFI, respectively, when they encounter the ISO on a hard
>    disk or USB stick.
>    To become recognizable by the firmware, the MBR has to sit at block 0
>    of the disk or USB stick. It also hosts the partition table or the
>    indication that there is a GUID partition table (GPT). So both firmwares
>    demand that the ISO image copy begins at block 0.
>    Thus the ISO needs to be copied onto the overall disk device file,
>    not onto a disk partition device file, and especially not into the
>    directory where some filesystem of the USB stick is mounted.
>    No filesystem of the USB stick should be mounted when it gets overwritten,
>    because afterwards its old data are likely to be gone.
> 
> 
>>> 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.
> 
>> ??
> 
> By using the second way, you overwrote the MBR and partition table of the
> USB stick. So now it bears the MBR and partition table of the ISO.
> The partition table of the ISO contains this
> 
>    $ /sbin/fdisk -l firmware-9.1.0-amd64-netinst.iso
>    
>    Disk firmware-9.1.0-amd64-netinst.iso: 325 MiB, 340787200 bytes, 665600 sectors
>    Units: sectors of 1 * 512 = 512 bytes
>    Sector size (logical/physical): 512 bytes / 512 bytes
>    I/O size (minimum/optimal): 512 bytes / 512 bytes
>    Disklabel type: dos
>    Disk identifier: 0x7db1c45b
> 
>    Device                            Boot Start    End Sectors  Size Id Type
>    firmware-9.1.0-amd64-netinst.iso1 *        0 665599  665600  325M  0 Empty
>    firmware-9.1.0-amd64-netinst.iso2       3984   4815     832  416K ef EFI (FAT-12
> 
> Partition 1 can be used to mount the ISO. Its type 0 = "Empty" is
> a necessity of our crammed hybrid ISO. We need to please EFI firmware.
> 
> As you can see, partition 2 is a FAT12 of type 0xef = "EFI". Let's have a
> look into it:
> 
>    $ sudo mount -o loop firmware-9.1.0-amd64-netinst.iso /mnt/iso
>    mount: /dev/loop0 is write-protected, mounting read-only
> 
> Being involved expert, i know that /boot/grub/efi.img is the ISO filename
> of the data file which is marked by partition 2:
> 
>    $ sudo mount -o loop /mnt/iso/boot/grub/efi.img /mnt/fat
> 
> (There are ways to find out the name or to mount it by its partition info.)
> 
> Now i can list the files in the FAT filesystem
> 
>    $ find /mnt/fat
>    /mnt/fat
>    /mnt/fat/efi
>    /mnt/fat/efi/boot
>    /mnt/fat/efi/boot/bootx64.efi
> 
> So the FAT12 filesystem contains just the single data file which EFI will
> look for on a amd64 machine, normally known by its DOS name:
>    \EFI\BOOT\BOOTX64.EFI
> 
> This file was made by program grub-mkimage. Its only purpose is to find
> the device on which the ISO is presented and to load and start the GRUB2
> configuration in the ISO directory /boot. At its end one can see these
> GRUB2 configuration commands as human readable text:
>    search --file --set=root /.disk/info
>    set prefix=($root)/boot/grub
>    source $prefix/x86_64-efi/grub.cfg
>    (memdisk)/boot/grub
> The existence of file /.disk/info is considered a unique property of the
> Debian ISO (Steve: Is this really good enough ?). So the first filesystem
> with that file gets used as source of further GRUB brain.
> The starting point of that brain is file
>    /mnt/iso/boot/grub/x86_64-efi/grub.cfg
> which loads
>    /mnt/iso/boot/grub/grub.cfg
> In there you will find texts which you also can see in the first menu
> of the booting Debian ISO:
>    menuentry --hotkey=g 'Graphical install' {
>    menuentry --hotkey=i 'Install' {
>    submenu --hotkey=a 'Advanced options ...' {
>    menuentry --hotkey=s 'Install with speech synthesis' {
> 
> Let's revoke "sudo mount" before we go on:
> 
>    $ sudo umount /mnt/fat
>    $ sudo umount /mnt/iso
> 
> 
>> I forgot to tell that I omited this jessie part. I only did
>> apt-get update
>> apt-get install firmware-realtek
>> apt-get install firmware-linux-nonfree
> 
> First:
> Very very good you skipped the reference to the old-stable system.
> Obviously the non-free-firmware ISO already is prepared to use the
> non-free repository of Debian 9.
> 
> Second:
> I understand you got no good graphics but were able to enter shell
> commands like apt-get.
> Right ?
> (Your previous reports stated that installation hung at some late stage.)
> 
> 
>> I was near (a couple of times) of giving up.
> 
> That's a good sign. If it does not offer resistence then it s not worth.
> 
> As software developer i am always mistrusting if a new feature does not
> show buggy behavior on the first test. Then it hides something evil ...
> 
> 
> Have a nice day :)
> 
> Thomas

I'm beginning to believe that you overestimate my skills. I'm not 
complaining, but I need some time to read all this.
Anyway, I must admit that I don't have a solid theoretical background, 
I'm mostly an stochastic guy. I mean that if it doesn't explodes, I keep 
advancing.
I insist, I can't find the words to thank you enough, all of you.

Luis

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

#186450

Hi,

> I need some time to read all this.

It took me a while to learn it. We grow with our challenges. :))

I must emphasize that one can be a great Debian expert without knowing
any of those details.
On the other hand, i am a rather mediocre admin of my Debian system.
"apt-file search" and "apt-get install" is my whole repertoire.


> I mean that if it doesn't explodes, I keep advancing.

That's the right spirit. There is always the next day to revisit a problem.


Have a nice day :)

Thomas

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

#186451

On Mon 04 Sep 2017 at 20:17:58 +0200, Luis Speciale wrote:

> I'm beginning to believe that you overestimate my skills. I'm not
> complaining, but I need some time to read all this.
> Anyway, I must admit that I don't have a solid theoretical background, I'm
> mostly an stochastic guy. I mean that if it doesn't explodes, I keep
> advancing.
> I insist, I can't find the words to thank you enough, all of you.

A stochastic guy? Your private life is your own.

Glad you got Debian installed on your machine. Don't waste it.

-- 
Brian.

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

#186452

Hi,

Brian wrote:
> A stochastic guy?

German wikipedia says it's greek: stochastikē technē = The Art of Guessing.

Some mathematician obviously thought that Ratekunst does not sound
impressive enough. Back then, greek was mandatory for getting to university.
So the word got unearthed and re-used in math.
(Still better than the fate of the word that ended up as "casemate".)


Have a nice day :)

Thomas

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

#186453

On Mon 04 Sep 2017 at 21:23:57 +0200, Thomas Schmitt wrote:

> Hi,
> 
> Brian wrote:
> > A stochastic guy?
> 
> German wikipedia says it's greek: stochastikē technē = The Art of Guessing.

Something similar with en.

> Some mathematician obviously thought that Ratekunst does not sound

Rate art?

> impressive enough. Back then, greek was mandatory for getting to university.
> So the word got unearthed and re-used in math.
> (Still better than the fate of the word that ended up as "casemate".)

I'll bite. "casemate" is to do with gun emplacements.

-- 
Brian.

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

#186454

Hi,

Brian wrote:
> Rate art?

"Raten" = to guess. "Kunst" = art. But together it's more down-home.
Guesscraft, maybe.

Lecture announcement: Guesscraft II. Room 201, monday and thursday 10:00 ct.


> "casemate" is to do with gun emplacements.

In german it sounds like the words for cheese and pad.
(Actually english language has the nearly correct greek transcript spelling
 for the correct meaning of the original term. I wonder why en.wikipedia
 mumbles about italian false houses.)


Have a nice day :)

Thomas

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

#186455

Le 04/09/2017 à 19:56, Thomas Schmitt a écrit :
> That's a good sign. If it does not offer resistence then it s not worth.

Como en el truco. Lo que cuesta, vale.

;)

Luis

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

#186379

Le 03/09/2017 à 15:12, Thomas Schmitt a écrit :
> 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 think this is because the GRUB core image installed on a drive 
includes only whatever modules are needed to access and read the 
location of /boot/grub. So the GRUB core image installed on a GPT drive 
includes only the part_gpt module and cannot read MSDOS partition tables 
until it switches to normal mode and loads the part_msdos module.

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

#186363

Hi,

(somehow my mail download is lagging behind today, so i am out of sync a bit)

Luis Speciale wrote:
> My bad it's x86_64-efi

There goes the theory of some typo in some rarely visited corner of the code.


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

Consider to boot some Live-Linux and use that for inspecting the hard
disk to which you installed nearly succeddfully.
E.g.
  https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-9.1.0-amd64-xfce.iso
or the variant with "cinnamon", "gnome", "kde", "lxde", or "mate"
instead of "xfce". (Why ain't there no "fvwm2" ? Are we old people ignored ?)

To be put on USB stick like the installation ISOs.
Use the MacOS way. What you did in MS-Windows is not known yet and
it seems to have yielded a different result.

(It may be that the GRUB installation unpacks the file from some
 archive which it has at backpack. Then you can search long and in vain.)


> thaks for the answer

You are welcome. Listen especially to Pascal's advice. My expert knowledge
ends when the firmware has found the boot loader of the ISO. From then on
i can mainly contribute bystander knowledge.


Have a nice day :)

Thomas

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

#186312

[Multipart message — attachments visible in raw view] — view raw

On 02/09/17 12:23, Luis Speciale wrote:
> Installing GRUB boot loader
> 
> 66%
> Running "update grub"…
> 
> I'm going to wait a little and see if it ends the install

When I installed Debian 9, the installer wanted to install grub on a
wrong path. I had to specify the path manually.

Try to specify the path manually to /dev/sdX (where X is one of “a”,
“b”, ... as corresponds to your disk).

-- 
Do not eat animals; respect them as you respect people.
https://duckduckgo.com/?q=how+to+(become+OR+eat)+vegan

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

#186345

Le 02/09/2017 à 20:50, Mario Castelán Castro a écrit :
> On 02/09/17 12:23, Luis Speciale wrote:
>> Installing GRUB boot loader
>>
>> 66%
>> Running "update grub"…
>>
>> I'm going to wait a little and see if it ends the install
> 
> When I installed Debian 9, the installer wanted to install grub on a
> wrong path. I had to specify the path manually.
> 
> Try to specify the path manually to /dev/sdX (where X is one of “a”,
> “b”, ... as corresponds to your disk).
> 

I am having problems with GRUB  too.

Someone suggests this when prompted by grub rescue>

set root=(hd0.gpt2)
linux vmlinuz root=/dev/sda2
initrd initrd.img
boot

But it complains about

Unknown command linux

Seems that the solution could be something like this

insmod /wherethisfileis/linux.mod

But I didn't find yet this famous file


Thanks for your answer. ¡Gracias!

Luis

[toc] | [prev] | [standalone]

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

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

csiph-web