Rc2 hangs on install -- Dell Inspiron i5759-8835SLV

[bill...@gmail.com]

Don't know what this means, but I downloaded the new 4.0 RC2, put it on a flash drive, and tried to install it on my new Dell laptop. It froze early on, with the messages:

Firmware Bug: TSC_DEADLINE disabled due to errate. Please update microcode to version 0xb2 (or later)

2.035271 Could not get size 0x800<bunch of zeros>0e

Anyway, just a data point.

I tried the "troubleshooting" option. It froze again, but I didn't write down the step. I believe it was after discovering/creating /dev/sdd

Good luck! I'll try again once the final version comes out. I'll monitor this if someone has an idea of how to get beyond this, but it's just an early hang for me.

billo

[bill...@gmail.com]

Er, that's "errata" not "errate." Sigh.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Oct 30, 2017 at 04:29:55PM -0700, bill...@gmail.com wrote:
> Don't know what this means, but I downloaded the new 4.0 RC2, put it on a flash drive, and tried to install it on my new Dell laptop. It froze early on, with the messages:
>
>
> Firmware Bug: TSC_DEADLINE disabled due to errate. Please update microcode to version 0xb2 (or later)

This is about CPU bug, fixable with newer microcode. In most cases it is
applied by BIOS early during system startup.
In short: update your BIOS.

> 2.035271 Could not get size 0x800<bunch of zeros>0e
>
> Anyway, just a data point.
>
> I tried the "troubleshooting" option. It froze again, but I didn't write down the step. I believe it was after discovering/creating /dev/sdd
>
> Good luck! I'll try again once the final version comes out. I'll monitor this if someone has an idea of how to get beyond this, but it's just an early hang for me.
>
> billo
>

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJZ9wxuAAoJENuP0xzK19csB3AH/0kSEWjZDt+zbe4It7bkHI4F
QKIkUBc/XAThel8d+VQiH67XFxYw6g7f1CquRCQ1EGIj+dl9L2pwauWFEOeDs6q1
YgZAN6CSZMQ3aBqiblHiOtuIn+9+7BsAxTydhAkD+Bf6qHyKpcf0JJuafRK3bMNn
IVByv5VOKiUV0KHOrM5wlXBkZe0JDSnJGHfISA1HOeoBBh4yOegX1pj6VVw3aLv7
xx4hMQFaUbFY6r8eqoj0k9sGuGC7RqhGx4hwL+9ZzqX2/L9jLzs09Z6Ulln+Txb5
I9wvmpRz97mFjbm0diGk0tVOusEvEZmiAXGgIf0tgXh0njNQ8ewdFDZE3S7XZQU=
=IaqP
-----END PGP SIGNATURE-----

[bill...@gmail.com]

Thanks, I'll give it a try. Now I just have to figure out how to update my BIOS. Once I look that up, I'll report back...

[bill...@gmail.com]

OK, I updated the BIOS. That got rid of the microcode error, alright. However, it still hangs.

I now get the error:

[2.040734] Couldn't get size: 0x80000<bunch of zeros> 0e
[2.527013] usb 1-1:string descriptor 0 read error-71

Just for giggles, I tried a different usb port for my flash drive. On the second port, I get just:

[2.039925] Couldn't get size: 0x80000...0e

and it hung, without the usb 1-1 error

and for the third port, it's the same, with a different first number:

[2.037575' Couldn't get size: 0x80...0e

with the "..." being a bunch of zeros

One other thing, there's a series of four lines that pops up quickly, but disappears faster than I can write them down, that something about UEFI booting or some such. Then the screen blacks out and these errors appear.

As an aside, I'm running a dual boot machine with Windows 10 and KDE neon.

billo

[awokd]

On Wed, November 1, 2017 20:26, bill...@gmail.com wrote:
> OK, I updated the BIOS. That got rid of the microcode error, alright.
> However, it still hangs.
>
> I now get the error:
>
> [2.040734] Couldn't get size: 0x80000<bunch of zeros> 0e
> [2.527013] usb 1-1:string descriptor 0 read error-71

Try a different brand flash drive? Maybe it's going bad.

[bill...@gmail.com]

Yeah, I'll do that. On the other hand, it may be a Fedora thing. Just for giggles, I downloaded F26, and it won't install, either -- it times out, though it gives a different error when it does.

I use these cheap flash drives I buy in bulk off ebay. I'll go get a pricey one and see if it makes a difference. But I gotta say, these same drives work fine for ubuntu and KDE neon.

[[799]]

Hello,

>> I use these cheap flash drives I buy in bulk
>> off ebay. I'll go get a pricey one and see if it
>> makes a difference.

I've migrated my USB drives to only one Modell:
SanDisk
https://www.amazon.com/gp/aw/d/B01NARBPI7/

It has a good performance (I have installed Qubes on of those to showcase it to friends and colleques.

[799]

[bill...@gmail.com]

On Wednesday, November 1, 2017 at 7:43:42 PM UTC-4, [799] wrote:

> I've migrated my USB drives to only one Modell:
> SanDisk
> https://www.amazon.com/gp/aw/d/B01NARBPI7/
>
> It has a good performance (I have installed Qubes on of those to showcase it to friends and colleques.
>
> [799]

Just ordered it. I'll see if it works.

[Mike Keehan]

I've been having similar 'stuck' problems on my laptop. And trying to
install Fedora 26 got stuck too.

I found that in my case it is the nouveau driver that gets stuck - the
driver can't handle the newest nvidia chips yet.

I managed to get Fedora to install by adding the option
'modprobe.blacklist=nouveau' to the kernel boot command line (at the
Fedora install boot use 'e' to edit the command line).

However I haven't yet figured out how to do that for Qubes bootup.

Mike.