[SOLVED] New build,cannot boot into live-usb

horo · 2022-02-16 06:44:01

I've started in on a new project and am building a PC from parts (first time in like 20 years).
Got a new mobo, cpu, and ram. Everything seemed to go smoothly on the hardware install, powering on the machine without any form of hard drive dropped me into a fancy graphical UEFI dashboard with waaaay more options than I thought possible for controlling the pre-boot and case fans.
I dled the most current 64bit .iso and 'dd'ed it onto a usb after checking the .sig and sha256sum. Things were going per usual, system sees the USB and gives me the live boot options. I select the first choice, get the usual printout on the screen of the boot process, then the screen goes black with a single flashing underscore in the upper left hand side and just hangs like that. I can ALT+<left/right> into other TTYs, and have ''user@debian $'' for a prompt. I have very limited commands, far less than the basic install would come with.

I tried booting again, but selected the 'fail safe' option and got some more info (typed by hand from the monitor)

...
xhci_hcd 0000:00:14.0: Error while assigning device slot ID
xhci_hcd 0000:00:14.0: Max number of devices this xHCI can support is 64
usb usb1-port1: couldn't allocate usb_device
xhci_hcd 0000:00:14.0: Error while assigning device slot ID
xhci_hcd 0000:00:14.0: Max number of devices this xHCI can support is 64
usb usb1-port2: couldn't allocate usb_device

BOOT FAILED!

This Live System image failed to boot.

Please file a bug against the 'live-boot' package o email the Live Systems
mailing list at <debian-live@lists.debian.org>, making sure to note the
exact version, name and distribution of the image you were attempting to boot.

The file /boot.log contains some debugging information but booting with the debug command-line parameter will greatly increae its verbosity which is
extremely useful when diagnosing issues.

live-boot will now start a shelllll The error messagwas:

  Unable to find a medium containing a live file system

BusyBox v1.30.1 (Debian 1:1.30.1-4) built in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

-

I assume this is a software issue, but I don't know if it's on linux or if I don't have the UEFI settings right. The hardware specs are thus-

CPU - Intel i5 12400
Mobo - ASRock B660M-HDV
RAM - T-Create DDR4 16GB (2x8GB) @ 3200 MHz

I verified the live-usb is good by booting on an older system. No issues, started normal and operated as it should.

Some UEFI notes- Secure Boot is disabled and Legacy USB Support is enabled

Last edited by horo (2022-02-24 06:27:51)

unklar · 2022-02-16 08:51:35

Wasn't there something that this stick must be created in "Uefi mode" ?

horo · 2022-02-16 16:16:40

I went and re-read the section on USB creation from the install page

It makes no mention of a UEFI mode.

unklar · 2022-02-16 18:08:01

^Sorry, that's all I read:

  Unable to find a medium containing a live file system

I can't believe it with this modern hardware, but have you tried nomodest at the kernel line?

I do not understand that either:

I dled the most current 64bit .iso and 'dd'ed it onto a usb after checking the .sig and sha256sum.

Why burn and then copy ? Why don't you do it with dd?

Edit:
I'm just "faking" the Uefi, but it does it for me with no problem.

qemu-system-x86_64 -enable-kvm -k de -smp 2 -m 2048 -bios /usr/share/OVMF/OVMF_CODE.fd -cdrom /media/Distris/bunsenlabs/lithium-1-amd64.hybrid.iso -name horo -boot d

Last edited by unklar (2022-02-16 18:36:38)

AndrewSmart · 2022-02-16 18:39:18

Puzzling. You can try #debian-live IRC channel.

Maybe tweak USB UEFI firmware settings or using different ports.

I had a funny experience with a bug in that area. Something to do with it not setting things up right. Workaround was to pull out the USB and plug it back in in a one second window, each time I booted, after seeing a message pop up on that black screen. For all machines I used that USB on, was a bug in xhci stuff, back in Debian Stretch or Jessie release.

horo · 2022-02-17 01:54:19

unklar wrote:

I do not understand that either:
I dled the most current 64bit .iso and 'dd'ed it onto a usb after checking the .sig and sha256sum.
Why burn and then copy ? Why don't you do it with dd?

Sorry if I wasn't clear. I re-downloaded the .iso and used dd to write it to my USB.

Edit:
I'm just "faking" the Uefi, but it does it for me with no problem. lol
qemu-system-x86_64 -enable-kvm -k de -smp 2 -m 2048 -bios /usr/share/OVMF/OVMF_CODE.fd -cdrom /media/Distris/bunsenlabs/lithium-1-amd64.hybrid.iso -name horo -boot d

can you please explain more what is going on here? and where would I enter this command at? Would this issued from the pre-boot shell?

I made a live-boot from the latest Arch .iso and it seems to be working normally. I didn't want to install Arch since it's more of a project I don't want to tackle right now, but would it hold some clues as to why it functions when bunsen won't?

unklar · 2022-02-17 07:51:17

^

ubuntu-wiki wrote:

nomodeset
Returns the video mode to the XServer.
As of kernel 2.6.28, the video mode of the graphics cards has been moved from the XServer to the kernel. This made it possible for a high-resolution "boot splash" (see Plymouth (section "Disable") to be displayed flicker-free. On some cards, this "boot splash" hangs or ends in a black screen.

After pressing e you get to this screen, bring the cusor to the kernel line and type at the end:
<spacebar>nomodeset<spacebar>.
then immediately Ctrl+x or F10 start the computer.

horo · 2022-02-17 19:21:26

I have tried to boot with 'nomodeset' added as instructed. The problem remains

rbh · 2022-02-17 19:46:33

According to this page, https://www.phoronix.com/scan.php?page= … 2022&num=1, your mb should work with linux.
I searched "B660M-HDV site:linux-hardware.org", no catch.
You use the onboard graphic chip?

It is quite new hardware. You have tried to boot the lithium iso both live session and install?
Have you tried latest Debian firmware iso: https://cdimage.debian.org/cdimage/unof … g-firmware?

If that work, you can install debian without desktop, add BL Beryllium or Lithium repos and add bunsenlabs metapackages.

unklar · 2022-02-17 20:59:58

horo wrote:

I have tried to boot with 'nomodeset' added as instructed. The problem remains

One last one.
For siduction 2021.1.0 to 2021.3.0, under "Installation notes and known issues", there is always this note:
"With some Intel GPUs on some devices, the system may freeze shortly after booting into Live. To fix this, you must set the kernel parameter intel_iommu=igfx_off before booting again."

Maybe this applies to your (new)CPU.
So you set the kernel parameter exactly in the same place as nomodeset above.

intel_iommu=igfx_off

horo · 2022-02-17 21:46:44

I am using the on board graphics.

I took your advise and grabbed the latest Debian .iso
I do not have a hard drive for this system yet, it's still in the mail, so can not test a direct install, but Debian 11.2.0 with kernel 5.10 booted without any issues

I think that settles it that the drivers for the hardware are not present in the current lithium .iso

Is Beryllium stable enough for daily use? aside from adding the repos to apt-source, would i need to do anything beside 'update' and 'upgrade' to get a default BL system?

horo · 2022-02-17 21:54:56

@unklar

I tried

intel_iommu=igfx_off

with no luck.
I believe (though could be wrong) this has something to do with the linux kernel's control over the USB header. More recent linux builds aren't having an issue, so I believe the lithium kernel on the .iso is just to out of date.

Bearded_Blunder · 2022-02-17 23:16:53

horo wrote:

I think that settles it that the drivers for the hardware are not present in the current lithium .iso
Is Beryllium stable enough for daily use? aside from adding the repos to apt-source, would i need to do anything beside 'update' and 'upgrade' to get a default BL system?

Seems very likely that's the root, given your processor is newer than the iso image, 12th gen (or even 10th) hadn't even been released by intel. Frankly I'm surprised you didn't have issues with Bullseye & have to bump right the way to Bookworm.

Just follow the guide in Development & Suggestions to install Beryllium, I've seen no real issues using it, see no real reasoon it would cause any day-to-day issues.

unklar · 2022-02-18 09:46:35

horo wrote:

@unklar
I tried
intel_iommu=igfx_off
with no luck.
I believe (though could be wrong) this has something to do with the linux kernel's control over the USB header. More recent linux builds aren't having an issue, so I believe the lithium kernel on the .iso is just to out of date.

@horo,
you are not the only one who has gained new knowledge.

Is Beryllium stable enough for daily use? aside from adding the repos to apt-source, would i need to do anything beside 'update' and 'upgrade' to get a default BL system?

Please read: https://forums.bunsenlabs.org/viewtopic … 35#p120635

rbh · 2022-02-18 12:19:24

horo wrote:

I do not have a hard drive for this system yet, it's still in the mail, so can not test a direct install,

With "You have tried to boot the lithium iso both live session and install?", I meant booted to Live and Install. If you can boot text install, you know that you can continue installing... If problem booting graphical desktop, add boot-parameter "3", to boot to comandline. Then possible to fix drivers.

but Debian 11.2.0 with kernel 5.10 booted without any issues

So, easiest is to wait 1-2 weeks until New Beryllium BL is ready to test.

Is Beryllium stable enough for daily use? aside from adding the repos to apt-source, would i need to do anything beside 'update' and 'upgrade' to get a default BL system?

I have migrated my 3 most used boxes some months ago. No problems detected.
If you want it installed now, follow the recommendations in post HOW-TO set up an experimental BL Beryllium system on Bullseye.
Then when Beryllium is released, you can switch repo to official adress: pkg.bunsenlabs.org.

horo · 2022-02-19 21:37:30

rbh wrote:

I have migrated my 3 most used boxes some months ago. No problems detected.
If you want it installed now, follow the recommendations in post HOW-TO set up an experimental BL Beryllium system on Bullseye.
Then when Beryllium is released, you can switch repo to official adress: pkg.bunsenlabs.org.

is that the correct link? It's taking me to an old post about mpv builds.

Bearded_Blunder · 2022-02-19 21:49:54

horo wrote:

is that the correct link? It's taking me to an old post about mpv builds.

For the sake of a quick reply, & even though the question isn't addressed to me, no it's not, it should be:
HOW-TO set up an experimental BL Beryllium system on Bullseye.
Seems it somehow ended up looking at the wrong post.
https://forums.bunsenlabs.org/viewtopic … 7356#p7356
instead of
https://forums.bunsenlabs.org/viewtopic.php?id=7356

Possibly the forum software butchered it in the posting process, so I've left it in plain as well as with a title.. if the one with the title ends up broken when I hit post.. use the one under "insted of"

rbh · 2022-02-19 22:58:03

horo wrote:

rbh wrote:
post HOW-TO set up an experimental BL Beryllium system on Bullseye.
is that the correct link? It's taking me to an old post about mpv builds.

Sorry, pasted "7356" in link "Post", instead of link "Topic". Forgot to test the link before hitting send.

horo · 2022-02-20 01:02:30

Thank you. I used Debian-standard-11.2 as a base install and followed the HOW-TO to get the bunsen-meta-all package installed.

Rebooted and logged in. Looks a little funny, the Welcome! script popped up in a terminal that looked straight out of Windows 3.4 (mlterm) and the icon in tint2 isn't very BL esque.
Set multiple things to install from the script, but they failed with error message-

E: Failed to fetch http://ftp.us.debian.org/debian/pool/main/r/re2/libre2-9_20210201%2bdfsg-1_amd64.deb Error reading from server - read (104: Connection reset by peer) [IP: 208.80.154.139 80]
E: Unable tp fetch some archives, maybe run apt-get update or try with --fix-missing?

none of the packages form the Welcome! script installed.

I opened another terminal and tryed to install a random package, mpv in this case, and had no issue

Edit: The screen resolution seems to be stuck at 800x600 @75hz. I have two monitors that are exactly the same, one is on an older machine that has been set up for a while and running

xrandr

gives me a list of possible resolutions with a mark showing the current setting
The new set up only lists 800x600 when xrandr is run. Another driver issue?

Last edited by horo (2022-02-20 02:56:03)

rbh · 2022-02-20 07:38:24

horo wrote:

Thank you. I used Debian-standard-11.2 as a base install and followed the HOW-TO to get the bunsen-meta-all package installed.
Rebooted and logged in. Looks a little funny, the Welcome! script popped up in a terminal that looked straight out of Windows 3.4 (mlterm) and the icon in tint2 isn't very BL esque.

So, after installation of BL metapackages, the look of your desktop differ from screenshot in Introduction to the Bunsenlabs Lithium Desktop?
No error in installog: /var/log/apt/history.log and /var/log/apt/term.log?
Can you post a screenshot? (After screenshot, reboot on debian 11.2 live iso.).

Set multiple things to install from the script, but they failed with error message-

So, after installing BL metapackages, you lost network. Have you tried both cable and wifi?

Edit: The screen resolution seems to be stuck at 800x600 @75hz. I have two monitors that are exactly the same, one is on an older machine that has been set up for a while and running
xrandr
gives me a list of possible resolutions with a mark showing the current setting
The new set up only lists 800x600 when xrandr is run. Another driver issue?

Can you in Debian 11,2 live session set screenresolution for both monitors?
If so, test to export script for screenresolution and add it to your BL-session startup.

#1 2022-02-16 06:44:01

[SOLVED] New build,cannot boot into live-usb

#2 2022-02-16 08:51:35

Re: [SOLVED] New build,cannot boot into live-usb

#3 2022-02-16 16:16:40

Re: [SOLVED] New build,cannot boot into live-usb

#4 2022-02-16 18:08:01

Re: [SOLVED] New build,cannot boot into live-usb

#5 2022-02-16 18:39:18

Re: [SOLVED] New build,cannot boot into live-usb

#6 2022-02-17 01:54:19

Re: [SOLVED] New build,cannot boot into live-usb

#7 2022-02-17 07:51:17

Re: [SOLVED] New build,cannot boot into live-usb

#8 2022-02-17 19:21:26

Re: [SOLVED] New build,cannot boot into live-usb

#9 2022-02-17 19:46:33

Re: [SOLVED] New build,cannot boot into live-usb

#10 2022-02-17 20:59:58

Re: [SOLVED] New build,cannot boot into live-usb

#11 2022-02-17 21:46:44

Re: [SOLVED] New build,cannot boot into live-usb

#12 2022-02-17 21:54:56

Re: [SOLVED] New build,cannot boot into live-usb

#13 2022-02-17 23:16:53

Re: [SOLVED] New build,cannot boot into live-usb

#14 2022-02-18 09:46:35

Re: [SOLVED] New build,cannot boot into live-usb

#15 2022-02-18 12:19:24

Re: [SOLVED] New build,cannot boot into live-usb

#16 2022-02-19 21:37:30

Re: [SOLVED] New build,cannot boot into live-usb

#17 2022-02-19 21:49:54

Re: [SOLVED] New build,cannot boot into live-usb

#18 2022-02-19 22:58:03

Re: [SOLVED] New build,cannot boot into live-usb

#19 2022-02-20 01:02:30

Re: [SOLVED] New build,cannot boot into live-usb

#20 2022-02-20 07:38:24

Re: [SOLVED] New build,cannot boot into live-usb

Board footer