On Wed 16 May 2018 at 00:35:33 (+0200), Pascal Hambourg wrote:
> Le 15/05/2018 à 03:23, David Wright a écrit :
> >
> >In this particular instance (the Lenovo), its PDF says:
> (...)
> > The default boot mode for your computer is UEFI mode. If you need to
> > install a legacy operating syste
Hi,
Mike Kupfer wrote:
> there seems to be something odd going on with the live image ISOs.
> [...]
> alto$ sudo dd if=debian-live-9.4.0-amd64-xfce.iso of=/dev/sdb bs=32K
> [...]
> 1951465472 bytes (2.0 GB, 1.8 GiB) copied, 455.702 s, 4.3 MB/s
> alto$ sudo isosize -x /dev/sdb
> sector co
Thomas Schmitt wrote:
> Mike Kupfer wrote:
> > I used sha256sum instead of sha512sum, but I otherwise followed
> > the above instructions. The checksum from the dd pipeline does not
> > match the checksum of the original .iso file.
>
> That's not good.
> Especially we do not have to show up at g
Le 15/05/2018 à 03:23, David Wright a écrit :
In this particular instance (the Lenovo), its PDF says:
(...)
The default boot mode for your computer is UEFI mode. If you need to
install a legacy operating system, such as Windows (that is, any operating
system before Windows 8)
Hi,
Mike Kupfer wrote:
> I used sha256sum instead of sha512sum, but I otherwise followed
> the above instructions. The checksum from the dd pipeline does not
> match the checksum of the original .iso file.
That's not good.
Especially we do not have to show up at grub-devel as long as the test
US
On Mon 14 May 2018 at 23:29:43 (+0200), Pascal Hambourg wrote:
> Le 14/05/2018 à 02:02, David Wright a écrit :
> >On Sun 13 May 2018 at 19:08:48 (+0200), Pascal Hambourg wrote:
> >>
> >>Most of my early experience with UEFI boot comes from a rather old
> >>Intel motherboard. Beside crippled UEFI su
On Mon 14 May 2018 at 11:56:11 (-0400), Stefan Monnier wrote:
> > Yes, documentation of firmware is almost unknown in my experience
> > (since probably 30 years ago). That's why I took the least invasive
>
> It's documented to the extent that it says "implements UEFI" and that
> UEFI is documented
Chris Ramsden wrote:
> On 2018-05-14 01:21, songbird wrote:
>> Pascal Hambourg wrote:
>> ...
>>> I agree with the author. If you want to keep the existing EFI Windows
>>> installation and have a convenient dual boot with GRUB, you'll have to
>>> set up your favourite distribution to boot in EFI m
Mike Kupfer wrote:
> Since the OP's problems were with 9.4, I haven't tried a more recent
> ISO, but I'll download an image and test it. (If this turns out to be
> fixed in 9.4, I will be very embarrassed and will happily buy y'all
> a meal if you're ever in the Bay Area.)
I just tried 9.4, usin
Thomas Schmitt wrote:
> Mike Kupfer wrote:
> > If I plug the stick into the laptop when it's running, the stick is
> > mounted okay. [...] didn't notice anything odd, but then I'm not familiar
> > with the contents of a hybrid image ISO.
>
> They have about the best verification support you can w
Le 14/05/2018 à 02:02, David Wright a écrit :
On Sun 13 May 2018 at 19:08:48 (+0200), Pascal Hambourg wrote:
Most of my early experience with UEFI boot comes from a rather old
Intel motherboard. Beside crippled UEFI support (no UEFI boot from
USB or SATA in AHCI mode), it had a couple of annoyi
Thomas Schmitt wrote:
> Does the live image always succeed and the netinst image always fail ?
> Is always the same USB stick affected ? (Or do you have one for each ISO ?)
> How do you actually "select" between installer and live ?
I made some changes between the initial attempts and what I'm do
Hi,
David Wright wrote:
> I read it as meaning that the USB stick works as a live system
> (first boot), but not as an installer (second boot).
Hm ... re-reading Mike's mails ...
Mike Kupfer wrote in his first mail:
> > > using a netinst image and a live image.
and today:
> > If I select the in
On Mon 14 May 2018 at 18:13:08 (+0200), Thomas Schmitt wrote:
> Hi,
>
> Mike Kupfer wrote:
> > I'm booting using EFI.
>
> So this could be a problem with GRUB about how it leaves the USB stick
> after having loaded kernel and initrd from it.
>
> The volatility of success and failure still gives
Hi,
Mike Kupfer wrote:
> I'm booting using EFI.
So this could be a problem with GRUB about how it leaves the USB stick
after having loaded kernel and initrd from it.
The volatility of success and failure still gives me riddles. But if you
can reproduce failure within a bearable number of tries,
> Yes, documentation of firmware is almost unknown in my experience
> (since probably 30 years ago). That's why I took the least invasive
It's documented to the extent that it says "implements UEFI" and that
UEFI is documented.
>> Same here (basically for the same reason: the behavior of the firm
On 2018-05-14 14:55, David Wright wrote:
> Would I be correct in thinking that the BIOS POST boot screen is
> what you get when you hit F12 sufficiently quickly after switch-on?
> So are you choosing between UEFI and Legacy (compatibility) mode.
> (I would like to know how Dell handles what I've be
Thomas Schmitt wrote:
> Hi,
>
> Just to make it clear:
> Was this kernel loaded from the very same USB stick which it then cannot
> inquire properly and in some cases cannot read from ?
Yes.
Oh, and I tried it again this morning, after the laptop had been off all
night, and this time it worked
On Mon 14 May 2018 at 09:14:23 (-0400), Stefan Monnier wrote:
> > That said, there are other statements that are odd:
>
> Not sure what you find odd about them:
>
> > "I really can’t recommend strongly enough that you do not attempt
> > to mix UEFI-native and BIOS-compatible booting of
>
On Mon 14 May 2018 at 13:28:56 (+0100), Chris Ramsden wrote:
> On 2018-05-14 01:21, songbird wrote:
> > Pascal Hambourg wrote:
> > ...
> >> I agree with the author. If you want to keep the existing EFI Windows
> >> installation and have a convenient dual boot with GRUB, you'll have to
> >> set up
> That said, there are other statements that are odd:
Not sure what you find odd about them:
> "I really can’t recommend strongly enough that you do not attempt
> to mix UEFI-native and BIOS-compatible booting of
> permanently-installed operating systems on the same computer, and
>
On 2018-05-14 01:21, songbird wrote:
> Pascal Hambourg wrote:
> ...
>> I agree with the author. If you want to keep the existing EFI Windows
>> installation and have a convenient dual boot with GRUB, you'll have to
>> set up your favourite distribution to boot in EFI mode. If you want to
>> go
Hi,
i wrote:
> > [6.997775] usb 1-2: New USB device found, idVendor=abcd,
> > idProduct=1234
> > They are missing in the good log. Other kernel version ?
> The good and bad logs are both
> for the same kernel--they're different attempts to boot the same ISO
> using the same USB stick.
Er.
Pascal Hambourg wrote:
...
> I agree with the author. If you want to keep the existing EFI Windows
> installation and have a convenient dual boot with GRUB, you'll have to
> set up your favourite distribution to boot in EFI mode. If you want to
> go back to legacy boot, including for Windows, yo
On Sun 13 May 2018 at 19:08:48 (+0200), Pascal Hambourg wrote:
> Le 13/05/2018 à 17:18, David Wright a écrit :
> >On Fri 11 May 2018 at 15:13:04 (-0500), Kent West wrote:
> >>
> >>That's good to know. I guess my source material (
> >>https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-
Thomas Schmitt wrote:
> The bad log has two suspicious lines before that range:
> [6.997775] usb 1-2: New USB device found, idVendor=abcd, idProduct=1234
> [7.000181] usb 1-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> Looks much like phony default values.
> They are
Hi,
Mike Kupfer wrote:
> (full files sent off-list)
Received.
> Hmm. The bad log has
>
> [7.015708] usbcore: registered new interface driver uas
> [ 25.552030] random: crng init done
It is quite sparse from that point on:
[ 29.034207] usb 1-2: reset high-speed USB device number 2
Le 13/05/2018 à 17:18, David Wright a écrit :
On Fri 11 May 2018 at 15:13:04 (-0500), Kent West wrote:
That's good to know. I guess my source material (
https://www.happyassassin.net/2014/01/25/uefi-boot-how-does-that-actually-work-then/)
is wrong. Or I misunderstood it.
While a lot of the de
Thomas Schmitt wrote:
> Mike Kupfer wrote:
> > I have a copy of kern.log from the first (successful) boot, and I have
> > the dmesg output from the second (failed) boot. If anyone wants to look
> > at them, let me know.
>
> I am interested. Especially whether there are messages from the ISO 966
On Fri 11 May 2018 at 15:13:04 (-0500), Kent West wrote:
> On Fri, May 11, 2018 at 2:59 PM, Pascal Hambourg
> wrote:
>
> > Le 11/05/2018 à 20:33, Kent West a écrit :
> >
> >>
> >> I learned that EFI boot drives need to have a GPT partition table. On a
> >>
> >
> > This is not correct. The UEFI sp
Hi,
i wrote:
> > The messages quoted by Kent could well indicate that the "CD-ROM" was
> > found
Curt wrote:
> I was laboring under another erroneous impression for some reason, but
> looking back at the OP he did say that the installer complained about
> not being able to "read" the cdrom (not t
On 2018-05-13, Thomas Schmitt wrote:
>
> Curt wrote:
>> I've mounted usb sticks that spontaneously 'umounted' themselves while
>> producing similar I/O reset errors.
>> Which might conceivably explain why the installer would begin asking for
>> the cdrom;
>
> The messages quoted by Kent could wel
Hi,
Mike Kupfer wrote:
> usb 1-2: device descriptor read/64, error -110
If we assume that 110 is a Linux errno, then this would be
ETIMEDOUT 110 /* Connection timed out */
> usb 1-2: reset high-speed USB device number 2 using xhci_hcd
That's what my USB attached DVD drives somet
On 2018-05-13, Mike Kupfer wrote:
>
> usb 1-2: device descriptor read/64, error -110
> ...
> usb 1-2: reset high-speed USB device number 2 using xhci_hcd
>
> I tried booting from a different USB port; that worked once, but on a
> subsequent attempt it failed with the same issue.
>
I've moun
Le 12/05/2018 à 21:38, Thomas Schmitt a écrit :
Pascal Hambourg wrote:
Why then does parted complain about a block size discrepancy ?
Because the Apple Partition Map announces to count blocks with size 2048
whereas the Linux device file announces 512 (via ioctl(BLKSSZGET) ?)).
I already kno
Kent West wrote:
> I have a Dell Latitude E7250 laptop. I'm trying to install Debian to it using
> a USB stick.
[...]
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read
> the CD-ROM.
Yes, I ran into the s
Hi,
Pascal Hambourg wrote:
> Why then does parted complain about a block size discrepancy ?
Because the Apple Partition Map announces to count blocks with size 2048
whereas the Linux device file announces 512 (via ioctl(BLKSSZGET) ?)).
It is quite a poor choice of parted to hop on the Apple Part
Le 11/05/2018 à 22:38, Thomas Schmitt a écrit :
Pascal Hambourg wrote:
It also has Apple and GPT partition tables, but they are bogus
The GPT is not valid because there is a non-"protective" MBR partition
table. The APM is valid, but should be of no interest for any firmware
that does not exp
Le 12/05/2018 à 01:04, Rick Thomas a écrit :
After doing the cp or dd to write the .iso to the USB, do you do a “sync”
before you eject it?
I don't, because I don't feel the need to.
According to its man page description, sync "flush file system buffers",
but the destination is a raw device,
On Fri 11 May 2018 at 15:49:59 -0500, Kent West wrote:
> I no longer have a failing setup, but this Ubuntu user was seeing the exact
> same thing I was seeing, except in Debian words/colors:
>
>
> https://askubuntu.com/questions/127398/usb-drive-install-of-ubuntu-12-04-server-fails-cant-find-com
I was burned once by this sort of Foolishness. (Some USB Drives even have
"Blinky Lights", to tell when Activity occurs). I do the File Copy, it
comes back to a prompt right away. But then, when I say "sync", it shows
how slow Access is, to writing to some of these USB Drives.
Never pull out a
Hi Kent,
After doing the cp or dd to write the .iso to the USB, do you do a “sync”
before you eject it? Writing to a USB stick can seem to go quite fast, but
that’s because of buffering. Often it takes quite a while (a minute or more
for a very big write on a machine with plenty of RAM) to c
Hi,
Kent West wrote:
> Warning: The driver descriptor says the physical block size is 2048 bytes,
> but Linux says it is 512 bytes.
The Apple Partition Map block size is 2048 indeed. Else it could not
coexist with the GPT.
> Disk /dev/sdc: 62.7GB
> Sector size (logical/physical): 2048B/512B
> Pa
On Fri, May 11, 2018 at 3:38 PM, Thomas Schmitt wrote:
> Hi,
>
> Kent West wrote:
> > > I learned that EFI boot drives need to have a GPT partition table.
>
> No. They do not. An MBR partition of type 0xEF is well ok, too.
>
>
> > > discovered that the flash drive had a "mac" partition table.
> >
Hi,
Kent West wrote:
> > I learned that EFI boot drives need to have a GPT partition table.
No. They do not. An MBR partition of type 0xEF is well ok, too.
> > discovered that the flash drive had a "mac" partition table.
> > Wha-a-ah-h-h??
It has an MBR partition table with partition 2 having
On Fri, May 11, 2018 at 2:59 PM, Pascal Hambourg
wrote:
> Le 11/05/2018 à 20:33, Kent West a écrit :
>
>>
>> I learned that EFI boot drives need to have a GPT partition table. On a
>>
>
> This is not correct. The UEFI specification supports boot from a drive
> with an MSDOS partition table. Other
Le 11/05/2018 à 20:33, Kent West a écrit :
I learned that EFI boot drives need to have a GPT partition table. On a
This is not correct. The UEFI specification supports boot from a drive
with an MSDOS partition table. Otherwise why would there be an "EFI
system partition" type identifier (0xe
On Fri, May 11, 2018 at 1:33 PM, Kent West wrote:
>
>
> On Fri, May 11, 2018 at 12:45 PM, songbird wrote:
>
>> Kent West wrote:
>> > --b378b9056bf066d4
>> > Content-Type: text/plain; charset="UTF-8"
>> >
>> > I have a Dell Latitude E7250 laptop. I'm trying to install Debian to it
>>
On Fri, May 11, 2018 at 11:56 AM, Curt wrote:
> On 2018-05-11, Kent West wrote:
> >
> > The real problem is that after going through the first three or four
> > screens, the install halts, complaining about not being able to read the
> > CD-ROM.
>
> I would guess that in the installer's parlance
On Fri, May 11, 2018 at 12:45 PM, songbird wrote:
> Kent West wrote:
> > --b378b9056bf066d4
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I have a Dell Latitude E7250 laptop. I'm trying to install Debian to it
> > using a USB stick.
> >
> > I've tried both of these .ISOs:
> >
Kent West wrote:
> --b378b9056bf066d4
> Content-Type: text/plain; charset="UTF-8"
>
> I have a Dell Latitude E7250 laptop. I'm trying to install Debian to it
> using a USB stick.
>
> I've tried both of these .ISOs:
>
> debian-9.4.0-amd64-xfce-CD-1.iso
> debian-buster-DI-alpha2-amd64-xfc
On 2018-05-11, Kent West wrote:
>
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read the
> CD-ROM.
I would guess that in the installer's parlance it's referring to your usb stick.
Have you tried another st
Hi,
Kent West wrote:
> The real problem is that after going through the first three or four
> screens, the install halts, complaining about not being able to read the
> CD-ROM.
Report this to debian...@lists.debian.org and add the original messages
of the complaing software.
I'd say that if the
Hi Kent,
It's much easier to write the image to the USB stick using the dd command
instead:
# dd if=debian-9.4.0-amd64-xfce-CD-1.iso of=/dev/sdc bs=1M
This should give you a working install stick.
--Robert
On Fri, May 11, 2018, 12:12 Kent West wrote:
> I have a Dell Latitude E7250 laptop. I
54 matches
Mail list logo
