Error cannot allocate kernel buffer

I have a Dell 9570 XPS laptop with latest BIOS (1.13.0) and I am trying to do a clean install of Ubuntu 19.10 from a flash drive. It is failing from two flash drives, one USB and one USB-C, with th...

I have a Dell 9570 XPS laptop with latest BIOS (1.13.0) and I am trying to do a clean install of Ubuntu 19.10 from a flash drive. It is failing from two flash drives, one USB and one USB-C, with these steps.

  1. Reboot with flash drive inserted.
  2. Hit F12 and select flash drive as boot option (under UEFI).
  3. Grub screen loads, select any install / try option (with or without safe graphics)

Fails with:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue...

Pressing any key takes me back to the grub selection screen. I am able to load a grub command line.

I have tried all combinations of secure boot, fast boot, legacy rom mode / legacy BIOS boot I can think of. Nothing has an impact except booting the flash drive via LEGACY EXTERNAL DEVICE BOOT, which loads the grub selection screen with nice graphics, and will successfully complete the installer.

However, I cannot then boot from the hard drive and even if I could, I want to use UEFI and secure boot.

Googling «cannot allocate kernel buffer» finds nothing that seems relevant.

Update:

I also tried installing off a 19.04 USB stick, which does work. I installed 19.04, then upgraded to 19.10. However, 19.10 then fails to boot with the same error.

I also tried creating the usb install from windows with Rufus, rather than with Startup Disk Creator from Ubuntu. Same issue.

It also seems to be now flashing briefly error: file /boot/ not found, before it hits the grub installer option screen.. Actually, this seems to only occur when booting from USB-C flash drive, not from USB.

I also.. tried from a Dell XPS 7590 with BIOS 1.2.3 and the USB stick boots fine. This be specific to my hardware / BIOS config / BIOS version somehow. I guess I will wait until either a new 19.10 release comes out, or my BIOS gets a new version.

Update: 1.14.0 BIOS version made no difference.

Содержание

  1. [РЕШЕНО] grub error: you need to load kernel first
  2. [РЕШЕНО]
  3. 19.10 usb installer boot fail
  4. Unable to boot ubuntu 19.10 or newer on dell xps 9570
  5. Bug Description
  6. [РЕШЕНО] grub error: you need to load kernel first
  7. [РЕШЕНО]
  8. Cannot allocate memory #11420
  9. Comments
  10. Vagrant version
  11. Host operating system
  12. Guest operating system
  13. Vagrantfile
  14. Debug output
  15. Expected behavior
  16. Actual behavior
  17. Steps to reproduce
  18. References

[РЕШЕНО] grub error: you need to load kernel first

Вечер добрый, друзья. С этой ошибкой столкнулся 3 дня назад. Все эти 3 дня подряд я не могу ничего поставить/переустановить. Кругом либо сразу же пишет grub error: you need to load kernel first , либо то, что на скрине, после чего установка не продолжается, если нажать Yes . Изначально поставил себе убунту 20.04, вместо винды, и всё поставилось с первого раза и без приключений, то есть я записал образ через balenaEtcher, вставил флешку в комп и всё заработало, а через какое-то время решил поставить себе какой-нибудь другой дистрибутив и понеслось… Такое ощущение, что мне будто бы подменили компьютер. Пробовал ставить Debian, ParrotOS (home и security), Ubuntu 20.10, Mint. Даже арч пробовал по совету друга, но и там меня ждала эта беда! Делал через dd, Rufus, Unetbootin, win32diskimager, убунтовский Startup Disk Creator но всё безуспешно!( Я на 100% уверен, что дело даже не во флешке, потому что до этого я ставил себе через неё же на другой компьютер винду и ElementaryOS. Никаких проблем не было, но тут как-то всё идёт против меня. На компьютере у меня стоит VisualBIOS 2.2.17. Ниже прикреплю некоторые скриншоты из него тут

С одной стороны у тебя uefi, а с другой… Сними галочку с legacy Boot.

[РЕШЕНО]

Спасибо огромное! Снял галочку с legacy boot, перезагрузился и всё заработало!

Источник

19.10 usb installer boot fail

I have a Dell 9570 XPS laptop with latest BIOS (1.13.0) and I am trying to do a clean install of Ubuntu 19.10 from a flash drive. It is failing from two flash drives, one USB and one USB-C, with these steps.

  1. Reboot with flash drive inserted.
  2. Hit F12 and select flash drive as boot option (under UEFI).
  3. Grub screen loads, select any install / try option (with or without safe graphics)

Pressing any key takes me back to the grub selection screen. I am able to load a grub command line.

I have tried all combinations of secure boot, fast boot, legacy rom mode / legacy BIOS boot I can think of. Nothing has an impact except booting the flash drive via LEGACY EXTERNAL DEVICE BOOT , which loads the grub selection screen with nice graphics, and will successfully complete the installer.

However, I cannot then boot from the hard drive and even if I could, I want to use UEFI and secure boot.

Googling «cannot allocate kernel buffer» finds nothing that seems relevant.

I also tried installing off a 19.04 USB stick, which does work. I installed 19.04, then upgraded to 19.10. However, 19.10 then fails to boot with the same error.

I also tried creating the usb install from windows with Rufus, rather than with Startup Disk Creator from Ubuntu. Same issue.

It also seems to be now flashing briefly error: file /boot/ not found , before it hits the grub installer option screen.. Actually, this seems to only occur when booting from USB-C flash drive, not from USB.

I also.. tried from a Dell XPS 7590 with BIOS 1.2.3 and the USB stick boots fine. This be specific to my hardware / BIOS config / BIOS version somehow. I guess I will wait until either a new 19.10 release comes out, or my BIOS gets a new version.

Update: 1.14.0 BIOS version made no difference.

Источник

Unable to boot ubuntu 19.10 or newer on dell xps 9570

Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It fails with the following error quickly flashing:

error: file `/boot/` not found

Then followed by:

error: cannot allocate kernel buffer.
error: you need to load the kernel first.

press any key to continue.

This occurs when doing an update from 19.04 to 19.10 and also when just booting off a usb drive with 19.10.

When booting off the usb drive. The first error flashes quickly before displaying the usb installer options. Selecting any install / boot option results in the second error about kernel buffer.

I have tried all combinations of bios settings I can think of, such as toggling secure boot and other options. The only thing that made a difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This allows the installer to complete, but I cannot then boot off the hard drive.

I have tried the same USB drive with 19.10 on a Dell XPS 7590 with BIOS 1.2.3 and the USB stick boots fine. I have also tried many different USB drives on my 9570.

I have tried a few daily builds of 20.04 with the same result. I tested with 20.04 beta as well.

Note: 19.04 and earlier continues to work no problem.

Источник

[РЕШЕНО] grub error: you need to load kernel first

Вечер добрый, друзья. С этой ошибкой столкнулся 3 дня назад. Все эти 3 дня подряд я не могу ничего поставить/переустановить. Кругом либо сразу же пишет grub error: you need to load kernel first , либо то, что на скрине, после чего установка не продолжается, если нажать Yes . Изначально поставил себе убунту 20.04, вместо винды, и всё поставилось с первого раза и без приключений, то есть я записал образ через balenaEtcher, вставил флешку в комп и всё заработало, а через какое-то время решил поставить себе какой-нибудь другой дистрибутив и понеслось… Такое ощущение, что мне будто бы подменили компьютер. Пробовал ставить Debian, ParrotOS (home и security), Ubuntu 20.10, Mint. Даже арч пробовал по совету друга, но и там меня ждала эта беда! Делал через dd, Rufus, Unetbootin, win32diskimager, убунтовский Startup Disk Creator но всё безуспешно!( Я на 100% уверен, что дело даже не во флешке, потому что до этого я ставил себе через неё же на другой компьютер винду и ElementaryOS. Никаких проблем не было, но тут как-то всё идёт против меня. На компьютере у меня стоит VisualBIOS 2.2.17. Ниже прикреплю некоторые скриншоты из него тут

С одной стороны у тебя uefi, а с другой… Сними галочку с legacy Boot.

[РЕШЕНО]

Спасибо огромное! Снял галочку с legacy boot, перезагрузился и всё заработало!

Источник

Cannot allocate memory #11420

Vagrant version

Host operating system

Windows 10 (1809)
Virtualbox 6.1.4

Guest operating system

Vagrantfile

Debug output

Expected behavior

The public key should be successfully inserted and the vm should finish upping.

Actual behavior

An error is encountered ( C:/HashiCorp/Vagrant/embedded/gems/2.2.6/gems/net-scp-1.2.1/lib/net/scp.rb:398:in `await_response_state’: �scp: /tmp/vagrant-insert-pubkey-1572381127: Cannot allocate memory (RuntimeError) ) while inserting the public key and the vm is deleted.

Steps to reproduce

  1. using the included vagrantfile, run vagrant up

Note that it doesn’t seem to happen every time. It was happening every time I upped the included vagrantfile, but when I tried to run in debug mode it worked the first time, but then encountered the error the next time I ran it. My host machine has plenty of ram (32GB total, only using

13GB) and the error seems to occur more often the higher the memory is set (e.g. happens a lot with v.memory = 8192 , doesn’t seem to ever happen with v.memory=1024 ).

Also important to note is that this error doesn’t seem to occur when using a different oracle 7 box, e.g. generic/oracle7 . It was only after we switched to bento/oracle-7 that we started seeing this error. I’m opening this issue here because it seems to be falling on vagrant’s side, but I can open an issue with bento if it’s determined to be an issue with the way they’re creating boxes.

References

Seems to be the same error as #11166 (and the guest OS I’m running, Oracle 7, is based on the guest OS they were running, CentOS 7).

The text was updated successfully, but these errors were encountered:

Источник

  • Печать

Страницы: [1]   Вниз

Тема: Не могу загружаться через grub [Решено]  (Прочитано 795 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
pthon

Здравствуйте,не могу загрузить линукс из граб ошибка:
grub> linux /boot/vmlinuz root=/dev/sdb2
error: cannot allocate kernel buffer.

« Последнее редактирование: 19 Марта 2021, 14:34:36 от zg_nico »

Conf: i3-8100, 16gb RAM, Amd RX580 4gb


Оффлайн
Sly_tom_cat

:idiot2: мне кажется еще initrd нужно указать, однако у меня опыта в использовании груба не так что бы совсем нет, но маловато…


Оффлайн
pthon

мне кажется еще initrd нужно указать

Не-а,я не могу указать initrd пока не указал ядро

Conf: i3-8100, 16gb RAM, Amd RX580 4gb


Оффлайн
ALiEN175

модули фс загружены(insmod)? корневой раздел указан(set root)?
почему вручную?

ASUS P5K-C :: Intel Xeon E5450 @ 3.00GHz :: 8 GB DDR2 :: Radeon R7 260X :: XFCE
ACER 5750G :: Intel Core i5-2450M @ 2.50GHz :: 6 GB DDR3 :: GeForce GT 630M :: XFCE


Оффлайн
pthon

модули фс загружены(insmod)? корневой раздел указан(set root)?
почему вручную?

Нет, insmod не использовал, но zorin os грузилась без этого. Set root указан.
Потому что grub-install не может установить загрузчик самостоятельно.
У меня стоит 3 системы (win10,hackintosh,linux mint)
В кловер есть линукс, но он не грузится с него,приходится грузиться в uefi shell и оттуда запускать grub efi (граб я скопировал с установочной флешки)

Conf: i3-8100, 16gb RAM, Amd RX580 4gb


Оффлайн
andytux

граб я скопировал с установочной флешки

Что за груб. Точно скопировал все необходимые файлы. К чему этот мазохизм — ручная загрузка.
Если груб работает, то пропиши загрузку в конфиг. Проще подпраить в режиме редактирования, чем каждый раз набирать все команды по памяти вручную.
Но если-уж хочется, то вручную запускается примерно так.
Немаловажный вопрос, что за ядро ты пытаешься грузить. И последний вопрос, который должен быть первым — «secure boot» отключен?

win10,hackintosh,linux mint

А вообще, ты ошибся форумом.

« Последнее редактирование: 21 Августа 2020, 06:58:29 от andytux »


Оффлайн
pthon

Решилось все обычной перезагрузкой -_-

Conf: i3-8100, 16gb RAM, Amd RX580 4gb


  • Печать

Страницы: [1]   Вверх

0

Создано виртуальная машина Linux Mint 21.
Установка через iso-образ (DVD)

Запускается и выводит ошибку:

error: cannot allocate kernel buffer
error: you need to load the kernel first

Подскажите пожалуйста источник для исправления этой ошибки если кто то сталкивался, прочту…

введите сюда описание изображения

  • virtualbox

Улучшить вопрос

задан 12 янв в 10:54

chilli's user avatar

chillichilli

135 бронзовых знаков

2

  • whitefumes.wordpress.com/2021/06/08/…

    – Alex F

    12 янв в 11:29

  • Огромное спасибо!

    – chilli

    12 янв в 12:38

Добавить комментарий
 | 

Сортировка:

Сброс на вариант по умолчанию

Ваш ответ

Зарегистрируйтесь или войдите

Регистрация через Google

Регистрация через Facebook

Регистрация через почту

Отправить без регистрации

Имя

Почта

Необходима, но никому не показывается

Нажимая на кнопку «Отправить ответ», вы соглашаетесь с нашими пользовательским соглашением, политикой конфиденциальности и политикой о куки

Посмотрите другие вопросы с метками

  • virtualbox

или задайте свой вопрос.

Hi,

Since updating my dell xps 9570 (latest BIOS 1.15.0 and a few previous versions) from 19.04 to 19.10 I have been unable to boot ubuntu. It fails with the following error quickly flashing:

  error: file `/boot/` not found

Then followed by:

  error: cannot allocate kernel buffer.
  error: you need to load the kernel first.

  press any key to continue…

This occurs when doing an update from 19.04 to 19.10 and also when just booting off a usb drive with 19.10.

When booting off the usb drive. The first error flashes quickly before displaying the usb installer options. Selecting any install / boot option results in the second error about kernel buffer.

I have tried all combinations of bios settings I can think of, such as toggling secure boot and other options. The only thing that made a difference is booting via USB with LEGACY EXTERNAL DEVICE BOOT. This allows the installer to complete, but I cannot then boot off the hard drive.

I have tried the same USB drive with 19.10 on a Dell XPS 7590 with BIOS 1.2.3 and the USB stick boots fine. I have also tried many different USB drives on my 9570.

I have tried a few daily builds of 20.04 with the same result. I tested with 20.04 beta as well.

Note: 19.04 and earlier continues to work no problem.

I have asked for help previously:

* https://askubuntu.com/questions/1183129/19-10-usb-installer-boot-fail
* https://answers.launchpad.net/ubuntu/+question/689546/+index

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-release-upgrader-core 1:19.04.16.9
ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
Uname: Linux 5.0.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 06:55:59 2020
InstallationDate: Installed on 2019-10-24 (162 days ago)
InstallationMedia: Ubuntu 19.04 «Disco Dingo» — Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bananan 2456 F…. pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-04-13 (2 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS «Bionic Beaver» — Release amd64 (20200203.1)
MachineType: Dell Inc. XPS 15 9570
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/ubuntu—vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-46-generic N/A
 linux-backports-modules-5.3.0-46-generic N/A
 linux-firmware 1.173.17
Tags: bionic
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 07GHH0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.

@astridos2go

I installed the Tela theme for my grub2 recently, and it looked wonderful, but every time I tried to boot into Ubuntu, it would not load the kernel, and came up with a message saying that I needed to load the kernel first.

I ended up having to boot from a livedisk and reinstalling grub entirely to remove the theme. As soon as the theme was removed Ubuntu booted fine. I’m not sure why installing the theme causes Ubuntu to not load correctly.

I would love to use these themes in my grub, since I have a 4k monitor and it looks very good but I don’t want to lose access to my Ubuntu.

@bmihaila

Hi @blumn2

I ran into the same problem, the error displayed is

error: cannot allocate kernel buffer
error: you need to load the kernel first

which then brings you back to grub menu and you are stuck with not being able to boot your system. The error occurs with any of the 4k theme background images. Likely due to Grub not being able to allocate that much memory for the image and the kernel. Very weird though.

To fix such a broken boot you don’t need to reinstall grub. You need to access your root filesystem (e.g. with a LiveUSB and mount it) and replace the file /usr/share/grub/themes/<themename>/background.jpg with a non-4k image, those can be found in https://github.com/vinceliuice/grub2-themes/tree/master/backgrounds
Use the 2k images as those worked for me.

However, if using those 4k images lead to an unbootable system for everyone then it should be fixed in grub upstream and meanwhile those themes should not be offered here to prevent people shooting themselves in the foot.
I’m using grub 2.02 btw. Have not tested it with newer versions like grub 2.04. From a fast search on the net it seems that it might be related to this issue in Grub 2.02 https://bugzilla.redhat.com/show_bug.cgi?id=1572126 but not sure.

@astridos2go

I tried again with the 2k image, and it again gave me the same issue, although @bmihaila ‘s solution of deleting the background image (I didn’t replace it this time) did save me some time in getting my grub and Ubuntu back to normal.

@stuarthayhurst

Is this still an issue? Or can it be closed because it’s an upstream issue?

@larchenkov

Same. Actually ubuntu starts but gdm3 not starting up, so you should change tty. Even purging gdm3 or installing lightdm didn’t help.

@stuarthayhurst

@larchenkov Does this happen when using other GRUB themes? I’m not sure how GDM 3 could be related to the GRUB theme though.

Понравилась статья? Поделить с друзьями:
  • Error cannot access filter public class securityconfig extends websecurityconfigureradapter
  • Error candidate is
  • Error canceling statement due to conflict with recovery
  • Error canceling autovacuum task
  • Error can t start driver error 1275