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

horo · 2022-02-20 18:21:04

The desktop looks like the pics from the link you provided. The terminal looks off, it doesn't have the theme applied to the window or color scheme

I searched the log files for 'error' and only had a match in term.log >

Log started: 2022-02-19  16:24:20
Selecting previously unselected package cryptsetup-bin.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 90168 files and directories currently installed.)
Preparing to unpack .../cryptsetup-bin_2.3.5-1_amd64.deb ...
Unpacking cryptsetup-bin (2:2.3.5-1) ...
Selecting previously unselected package cryptsetup.
Preparing to unpack .../cryptsetup_2.3.5-1_amd64.deb ...
Unpacking cryptsetup (2:2.3.5-1) ...
Selecting previously unselected package cryptsetup-initramfs.
Preparing to unpack .../cryptsetup-initramfs_2.3.5-1_all.deb ...
Unpacking cryptsetup-initramfs (2:2.3.5-1) ...
Setting up cryptsetup-bin (2:2.3.5-1) ...
Setting up cryptsetup (2:2.3.5-1) ...
Setting up cryptsetup-initramfs (2:2.3.5-1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for initramfs-tools (0.140) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-10-amd64
cryptsetup: ERROR: Couldn't resolve device /dev/mapper/vault--vg-root
cryptsetup: WARNING: Couldn't determine root device
cryptsetup: ERROR: Couldn't resolve device 
    UUID=88ed31c0-1fc0-4c08-bb4c-00b808646189
W: Couldn't identify type of root file system for fsck hook
W: initramfs-tools configuration sets RESUME=UUID=88ed31c0-1fc0-4c08-bb4c-00b808646189
W: but no matching swap device is available.
live-boot: core filesystems devices utils udev blockdev dns.
Log ended: 2022-02-19  16:24:40

Despite this, the encrypted drive setup seems to be working.

This is a desktop computer set up next to the router, it does not have wifi capabilities. It is not losing net access, I can browse the web and use apt-get normally.

I just ran the bl-welcome script again and it seemed to function all the way through and install the various meta packages.
Will reboot and see if the screen resolution has changed at all

Bearded_Blunder · 2022-02-20 18:48:48

Just occasionally a specific mirror will have an issue for a short while, it could have been that.
I did notice you weren't using the default deb.debian.org content delivery network but rather ftp.us.debian.org.

That would be the likely cause if the problem has gone away.
I've seen similar things with some package temporarily not found when using bytemark.co.uk as the selected mirror.

rbh · 2022-02-20 19:18:05

horo wrote:

The desktop looks like the pics from the link you provided.

Ok, so it seems most work now..

The terminal looks off, it doesn't have the theme applied to the window or color scheme

Mlterm is not BL default terminal and does not have any BL theme. Lxterminal has. Maybe you have to run command "galternatives" and set your prefered terminal? The urxvt terminal also has BL-theme,but does not have mouse-support and can be cumbersome in the begining.

I just ran the bl-welcome script again and it seemed to function all the way through and install the various meta packages.

Ok, good news.

Will reboot and see if the screen resolution has changed at all

The resolution will maybe not change by itself. Then you have to do it acording to the text in the Introduction..

horo · 2022-02-20 21:48:40

'galternatives' said the system was set to 'lxterm', but switching it to 'mlterm' then back got me to where i need to be.
Arandr does nothing. Changing settings and saving makes no changes to the display. Trying to enter new resolutions with xrandr does nothing aswell.

Edit: Live booted into a new Manjaro setup. It recognizes the monitor normally and defaults it to 1240X1024

maybe another driver issue?

Edit 2.0: Another thing i've noticed is the bl install doesn't put the monitor to sleep. After a while the screen does lock and go black, but the backlight for the monitor stays on. The Manjaro live boot does not have this issue.

Edit 3.0: Attempted to upgrade the kernel from 5.10 to 5.15.

apt-get installed linux-image-5.15.0-0.bpo.3-amd64

rebooted and selected new image form 'Advanced options' on grub menu. No noticeable changes other than uname -r spits out 5.15.0-0.bpo.3-amd64 as the kernel

Last edited by horo (2022-02-20 23:16:28)

rbh · 2022-02-21 11:44:15

horo wrote:

Arandr does nothing. Changing settings and saving makes no changes to the display. Trying to enter new resolutions with xrandr does nothing aswell.

Do you use correct syntax? Have you tried running the settings-script made by Arandr in terminal?

Edit: Live booted into a new Manjaro setup. It recognizes the monitor normally and defaults it to 1240X1024

You mean "the monitors"? You had two monitors. Is 1240X1024 also your prefered setting? If booting live Debian 11.2...iso, Can you set your prefered screen-resolution?

Edit 2.0: Another thing i've noticed is the bl install doesn't put the monitor to sleep. After a while the screen does lock and go black, but the backlight for the monitor stays on. The Manjaro live boot does not have this issue.

You have gone through your power settings?

Edit 3.0: Attempted to upgrade the kernel from 5.10 to 5.15.
apt-get installed linux-image-5.15.0-0.bpo.3-amd64
rebooted and selected new image form 'Advanced options' on grub menu. No noticeable changes other than uname -r spits out 5.15.0-0.bpo.3-amd64 as the kernel

If you installed newer backported kernel, you did not try to install... Normaly latest kernel, will appear as first choice in grub, no need to go to advanced menu.

rbh · 2022-02-21 12:02:01

After thinking a litte; In your position, I would try upgrade to Debian 12. Bookworm, Debian testing is very stable now.
Even sid is quite stable.. I have one vm running sid for 2 years now. Two yeras ago it broke and I had to reinstall...

And, next time you by new hardware you want to run on Debian stable, check with https://linux-hardware.org before. You can save you a lot of work...

horo · 2022-02-21 21:15:24

"Monitor". I have a single display for the system, but the monitor I'm using is identical to one on a separate older system. I believe I used proper syntax for xrandr, but did not use arandr through terminal. I accessed it through menu>preferences>display>arandr
I'll review and retry my attempt at using arandr.

Would it be more advisable to add the Bookworm repos and upgrade the current system or re-install from a Bookworm .iso?

rbh · 2022-02-21 23:30:04

horo wrote:

"Monitor". I have a single display for the system, but the monitor I'm using is identical to one on a separate older system.

Ah, so when you wrote:

xrandr
gives me a list of possible resolutions with a mark showing the current setting

that was about another system, with identical monitor?

And your brand new system with same monitor model, does it still:

The new set up only lists 800x600 when xrandr

I believe I used proper syntax for xrandr, but did not use arandr through terminal. I accessed it through menu>preferences>display>arandr
I'll review and retry my attempt at using arandr.

I asked you to run arandr. From the menu, gmrun or terminal, does not matter how. The important thing is to make your choise of resolution, if you can choose anything more than 800x600. Then save the setting as script ~/.screenlayout/screen.sh. Then run the script in terminal, as described in the Introduction ... Do you get any error? No change of screen resolution?

Does the other system lso run BL or can you run BL/Debian live iso and get correct screenresolution? If so, worth trying to shift monitor.

I have two monitors to my desktop. Some monts ago the left monitor got black, After having detached power to monitor and computer for some minutes, the monitor worked again, but only in 800x600, I have to force the monitor to correct screen mode with
following lines in my screen.sh:

gtf 1920 1080 60
xrandr --newmode "1920x1080_60.00"  172.80  1920 2040 2248 2576  1080 1081 1084 1118  -HSync +Vsync

xrandr --output VGA-0 --primary --mode 1920x1080_60.00 --pos 0x0 --rotate normal --output DVI-0 --mode 1920x1080 --pos 1920x0 --rotate inverted

Would it be more advisable to add the Bookworm repos and upgrade the current system or re-install from a Bookworm .iso?

I don't think you can find an Bookworm .iso with non-free firmware... If you do, it is better to install from that.

horo · 2022-02-24 06:27:28

Ok. I edited my /etc/apt/source.list to point at the bookworm repos and ran

apt-get update
apt-get upgrade
apt-get full-upgrade

Rebooted my system was greeted with default 1280x1024 resolution!
The kernel was upgraded to 5.16.0.1 and for now it seems like everything is working properly.
Xrandr spits out normal info, no error messages!

A big thank you to everyone's input on this.

#21 2022-02-20 18:21:04

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

#22 2022-02-20 18:48:48

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

#23 2022-02-20 19:18:05

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

#24 2022-02-20 21:48:40

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

#25 2022-02-21 11:44:15

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

#26 2022-02-21 12:02:01

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

#27 2022-02-21 21:15:24

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

#28 2022-02-21 23:30:04

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

#29 2022-02-24 06:27:28

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

Board footer