1.773390 couldn't get size 0x800000000000000

system001 · 07-13-2019, 08:31 AM

when i reboot either kde neon or kubuntu and chose to go into either one i get the following "1.773390 couldn't get size 0x800000000000000". once in either os all seems fine. i'm assuming at this point that this has to do with one of the drives or an individual partition, but without more info than that i don't have the slightest idea where to look. anyone have an idea of how i go about fixing this? thanks

mrmazda · 07-13-2019, 06:55 PM

Quote:

Originally Posted by system001

anyone have an idea of how i go about fixing this?

Start by giving us some information to go on:

What does "chose to go into either one"mean?
where do you see "1.773390 couldn't get size 0x800000000000000" appear?
what is output from "inxi -b" run from Konsole in your KDE session

system001 · 07-13-2019, 10:08 PM

chose which one to boot into, just before it boots into the selected os,

Code:

System:    Host: mg2635599-desktop Kernel: 5.1.7-050107-generic x86_64 bits: 64 Desktop: KDE Plasma 5.16.3 
           Distro: Ubuntu 19.04 (Disco Dingo) 

Machine:   Type: Desktop Mobo: ASUSTeK model: 970 PRO GAMING/AURA v: Rev 1.xx serial: <root required> 
           UEFI: American Megatrends v: 1001 date: 06/07/2017 

CPU:       6-Core: AMD FX-6300 type: MCP speed: 1404 MHz min/max: 1400/3500 MHz 

Graphics:  Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] driver: nvidia v: 430.26 
           Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
           resolution: 2560x1080~60Hz 
           OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 430.26 

Network:   Device-1: Intel I211 Gigabit Network driver: igb 

Drives:    Local Storage: total: 4.20 TiB used: 2.74 TiB (65.2%) 

Info:      Processes: 294 Uptime: 4h 42m Memory: 15.56 GiB used: 4.43 GiB (28.4%) Shell: bash inxi: 3.0.34

kilgoretrout · 07-14-2019, 08:12 AM

I googled that "couldn't get size 0x800000000000000" error message and found that you're not alone. Red Hat says it's an error that can be ignored if you haven't imported any UEFI keys:

https://bugzilla.redhat.com/show_bug.cgi?id=974841

and another advised disabling secure boot:

https://medium.com/@maniac.tw/linux-...t-14a014b7ed54

From the foregoing, that error message seems to have something to do with the secure boot/key authorization system present in modern UEFI motherboards. If you're otherwise booting OK, you can ignore it.

system001 · 07-14-2019, 09:40 AM

yea i googled it as well and turned up nothing. i tend to agree with redhat cause it doesn't seem to be hurting anything. as for secure boot i've never used it, regardless of claims otherwise it was only created to limit your software sources. microsour and company were hoping it would dissuade peeps from using linux. great plan till the mobo manufactures got forced to allow peeps to disable it, and linux distros became sure boot friendly.

verndog · 07-14-2019, 09:52 AM

Every time I see those messages, my efibootmgr is messed up. Once I clear that up, the message stops.

system001 · 07-14-2019, 09:59 AM

yea that would be my guess. i'm planning on resetting the ssd today and giving the entire drive to kubuntu instead of kubuntu and neon. have a feeling a fresh boot partition will see the end of that message. thanks guys for the replies, much appreciated.