Re: Boot Errors

[Toni Casueps]

When you get the "invalid argument" error do you see something in the output of 
"dmesg"?
Can you try to mount it from another distro live-USB or from the Debian 
installer rescue mode?

Enviado desde Outlook Mobile


From: Michael Lee 
Sent: Thursday, March 2, 2023 4:30:47 PM
To: debian-user@lists.debian.org 
Subject: Boot Errors

While running the stable branch of 64-bit Debian, rebooted into an
alternative OS, but forgot to unmount a USB device beforhand. Shutdown
was taking too long, so forced it anyway. Now when I try to start
Linux, I get these error messages:

[1.922640] platform gpio_ich.2.auto: failed to claim resource 0:[io
0x0480-0x04ff]
[8.934607] BTRFS error (device sdc2): parent transid verify faild on
176160768 wanted 680981 found 680979
[8.934649] BTRFS error (device sdc2): failed to read block groups 1 - 5
[8.935724] BTRFS error (device sdc2): open_ctree failed
mount: mounting /dev/sdc2 on /root failed: invalid argument
failed to mount /dev/sdc2 as root file system

Then the initramfs command prompt appears. A little hard to find much
on that.

Read in the btrfs wiki that <-o ro,usebackuproot> with the mount
command could help when the "wanted" and "found" numbers were not too
far apart.

mount -t btrfs -o ro,usebackuproot /dev/sdc2
TRIED with: /sysroot
GOT: mount: mounting /dev/sdc2 on /sysroot failed: invalid argument
TRIED with: /
GOT: mount: mounting /dev/sdc2 on / failed: invalid argument
TRIED with: /root
GOT: mount: mounting /dev/sdc2 on /root failed: invalid argument

Is this a GRUB issue, a btrfs issue, or must I reinstall the operating
system, and if so where can I find out which files must be preserved in
order to maintain continuity?

RE: partial freeze when playing 3D games

[Toni Casueps]

I discarded LXDE as a problem as the same happens with KDE

De: Toni Casueps
Enviado: viernes, 23 de julio de 2021 8:39
Para: debian-user@lists.debian.org 
Asunto: partial freeze when playing 3D games


Hi all,


When running 3D games (video players or 2D games work fine), at a random moment 
the image freezes. If I Alt-Tab out of the game window, as shown in the linked 
video below, the Alt-Tab dialog works and it actually switches to the other 
applications but they can't be seen, only their window borders. I can even do 
Alt+F2, type xterm, the application opens and I can type exit and xterm is 
closed. The only thing I can do is go back to text mode with Ctrl+Alt+F1, log 
in and kill the game process, then go back to Alt-F7 and everything works fine 
with the remaining open applications.


I checked Xorg.0.log and other files in /var/log and dmesg, but there is 
nothing there related to the freeze. How can I further debug this?


System: Debian 11 + LXDE, all updates applied


Linux 5.10.0-8-amd64 SMP


VGA compatible controller: Intel Corporation TigerLake GT2 [Iris Xe Graphics] 
(rev 01)


https://drive.google.com/file/d/164KJ1zUIgI7oNwIC5V1yhigyLcG1GLA2/view?usp=sharing

RE: partial freeze when playing 3D games

[Toni Casueps]

Hi all,


When running 3D games (video players or 2D games work fine), at a random moment 
the image freezes. If I Alt-Tab out of the game window, as shown in the linked 
video below, the Alt-Tab dialog works and it actually switches to the other 
applications but they can't be seen, only their window borders. I can even do 
Alt+F2, type xterm, the application opens and I can type exit and xterm is 
closed. The only thing I can do is go back to text mode with Ctrl+Alt+F1, log 
in and kill the game process, then go back to Alt-F7 and everything works fine 
with the remaining open applications.


I checked Xorg.0.log and other files in /var/log and dmesg, but there is 
nothing there related to the freeze. How can I further debug this?


System: Debian 11 + LXDE, all updates applied


Linux 5.10.0-8-amd64 SMP


VGA compatible controller: Intel Corporation TigerLake GT2 [Iris Xe Graphics] 
(rev 01)


https://drive.google.com/file/d/164KJ1zUIgI7oNwIC5V1yhigyLcG1GLA2/view?usp=sharing

partial freeze when playing 3D games

[Toni Casueps]

Hi all,


When running 3D games (video players or 2D games work fine), at a random moment 
the image freezes. If I Alt-Tab out of the game window, as shown in the linked 
video below, the Alt-Tab dialog works and it actually switches to the other 
applications but they can't be seen, only their window borders. I can even do 
Alt+F2, type xterm, the application opens and I can type exit and xterm is 
closed. The only thing I can do is go back to text mode with Ctrl+Alt+F1, log 
in and kill the game process, then go back to Alt-F7 and everything works fine 
with the remaining open applications.


I checked Xorg.0.log and other files in /var/log and dmesg, but there is 
nothing there related to the freeze. How can I further debug this?


System: Debian 11 + LXDE, all updates applied


Linux 5.10.0-8-amd64 SMP


VGA compatible controller: Intel Corporation TigerLake GT2 [Iris Xe Graphics] 
(rev 01)


https://drive.google.com/file/d/164KJ1zUIgI7oNwIC5V1yhigyLcG1GLA2/view?usp=sharing

Multiple issues with LXDE/LightDM after upgrading to Debian 10

[Toni Casueps]

None of these issues happened on Debian 9, and they seem related, so I'm 
thinking that they may be caused by some single change or misconfiguration. 
Graphics drivers seem to be fine, as 2D and 3D acceleration both work perfectly:

  *   When the PC is at sleep state, after waking up, the monitor shows "no 
signal", and moving the mouse or pressing keys does not work. Only Ctrl+Alt+F1 
works, it goes to text mode where the monitor gets signal, and then Ctrl+Alt+F7 
works fine and shows the graphical session. This does not happen with normal 
boot from shutdown
  *   Sometimes (very randomly) after correctly logging in and the desktop 
shows up, after 1 second or so it goes back to the login screen, I log in again 
and then it works fine (the session is not lost in this case, programs are 
still there)
  *   If there is a TV connected to the HDMI port, after waking up from 
suspend, the session is lost, it creates a new desktop session with no 
programs, and after opening those programs they report they crashed and prompt 
the user to try to recover documents or browser tabs
  *   If the laptop display is turned off so as to only use the external one, 
then I shut down or suspend the PC, disconnect the external display and try to 
use the laptop somewhere else without an external monitor, the laptop display 
is blank for X sessions, only text mode works. I managed to turn the laptop 
display on with xrandr, but I think it should fallback to the internal display 
when it's the only one available

Are these related to Debian, LXDE, Openbox or LightDM?
Thanks

Chromium randomly crashes

[Toni Casueps]

Not sure if I should report this to Chromium or to Debian, but I guess that 
packaging a new Chromium version could fix the problem
I updated (on Debian 10) to 83.0.4103.116-1~deb10u2 and after some minutes it 
crashes giving this log. It's difficult to tell when it happens as it's really 
random, just reading a page and scrolling down, the window disappears and the 
process ends, it could be after 2, 5, 10 minutes... totally random:


Received signal 11 SEGV_MAPERR 7f018c158b47
#0 0x56027fcbe469 (/usr/lib/chromium/chromium+0x51f9468)
#1 0x56027fc1c193 (/usr/lib/chromium/chromium+0x5157192)
#2 0x56027fcbdff1 (/usr/lib/chromium/chromium+0x51f8ff0)
#3 0x7ff8b3e48730 (/usr/lib/x86_64-linux-gnu/libpthread-2.28.so+0x1272f)
#4 0x7ff8add51d48 (/usr/lib/x86_64-linux-gnu/libc-2.28.so+0x7fd47)
#5 0x7ff8add54a58 (/usr/lib/x86_64-linux-gnu/libc-2.28.so+0x82a57)
#6 0x7ff8add5656a __libc_malloc
#7 0x56027fcd5bee operator new()
#8 0x7ff8adfcb3cd std::__cxx11::basic_string<>::reserve()
#9 0x7ff8adfbf845 std::__cxx11::basic_stringbuf<>::overflow()
#10 0x7ff8adfc99cb std::basic_streambuf<>::xsputn()
#11 0x7ff8adfbab34 std::__ostream_insert<>()
#12 0x56027fcbe7b9 (/usr/lib/chromium/chromium+0x51f97b8)
#13 0x56027fcbe844 (/usr/lib/chromium/chromium+0x51f9843)
#14 0x56027fc2e9d2 (/usr/lib/chromium/chromium+0x51699d1)
#15 0x56027fc30b1e (/usr/lib/chromium/chromium+0x516bb1d)
#16 0x56027e39962a (/usr/lib/chromium/chromium+0x38d4629)
#17 0x56027e39967e (/usr/lib/chromium/chromium+0x38d467d)
#18 0x56027da3f98f (/usr/lib/chromium/chromium+0x2f7a98e)
#19 0x56027e353559 (/usr/lib/chromium/chromium+0x388e558)
#20 0x56027e35379e (/usr/lib/chromium/chromium+0x388e79d)
#21 0x56027e39ce67 (/usr/lib/chromium/chromium+0x38d7e66)
#22 0x56027e3c8ac2 (/usr/lib/chromium/chromium+0x3903ac1)
#23 0x56027e3c8d7e (/usr/lib/chromium/chromium+0x3903d7d)
#24 0x56027e39963f (/usr/lib/chromium/chromium+0x38d463e)
#25 0x56027e39967e (/usr/lib/chromium/chromium+0x38d467d)
#26 0x56027da3f98f (/usr/lib/chromium/chromium+0x2f7a98e)
#27 0x56027dcf6f53 (/usr/lib/chromium/chromium+0x3231f52)
#28 0x56027e021e22 (/usr/lib/chromium/chromium+0x355ce21)
#29 0x56027fdf1aff (/usr/lib/chromium/chromium+0x532cafe)
#30 0x56027fdf8274 (/usr/lib/chromium/chromium+0x5333273)
#31 0x56027fdf616d (/usr/lib/chromium/chromium+0x533116c)
#32 0x56027fdf4e2c (/usr/lib/chromium/chromium+0x532fe2b)
#33 0x56027fded913 (/usr/lib/chromium/chromium+0x5328912)
#34 0x56027fe0977b (/usr/lib/chromium/chromium+0x534477a)
#35 0x56027fe09a41 (/usr/lib/chromium/chromium+0x5344a40)
#36 0x56027fe09040 (/usr/lib/chromium/chromium+0x534403f)
#37 0x56027dcdfe26 (/usr/lib/chromium/chromium+0x321ae25)
#38 0x56027dcdf94c (/usr/lib/chromium/chromium+0x321a94b)
#39 0x56027dcdbd51 (/usr/lib/chromium/chromium+0x3216d50)
#40 0x56027dcd261b (/usr/lib/chromium/chromium+0x320d61a)
#41 0x56027dcc4f1b (/usr/lib/chromium/chromium+0x31fff1a)
#42 0x56027dcc4c03 (/usr/lib/chromium/chromium+0x31ffc02)
#43 0x56027dce39a6 (/usr/lib/chromium/chromium+0x321e9a5)
#44 0x56027fcdb28a (/usr/lib/chromium/chromium+0x5216289)
#45 0x7ff8b22619ba (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.6.0.2+0x229b9)
#46 0x7ff8b2262537 event_base_loop
#47 0x56027fcdb510 (/usr/lib/chromium/chromium+0x521650f)
#48 0x56027fc7ac05 (/usr/lib/chromium/chromium+0x51b5c04)
#49 0x56027fc52a1d (/usr/lib/chromium/chromium+0x518da1c)
#50 0x56027dfbdd93 (/usr/lib/chromium/chromium+0x34f8d92)
#51 0x56027fc913f7 (/usr/lib/chromium/chromium+0x51cc3f6)
#52 0x56027fcce0ce (/usr/lib/chromium/chromium+0x52090cd)
#53 0x7ff8b3e3dfa3 start_thread
#54 0x7ff8addcb4cf clone
  r8: 0041  r9: 7ff88c30 r10: 7ff88cd991a0 r11: 
7ff88c80
 r12: 7ff88ce1dc20 r13: 0021 r14: 7ff88c20 r15: 
0041
  di: 7ff88c20  si: 0081  bp: 7f018c158b3f  bx: 

  dx: 0080  ax: 7f018c158b3f  cx: 7ff88cfe0770  sp: 
7ff896ff98c0
  ip: 7ff8add51d48 efl: 00010206 cgf: 002b0033 erf: 
0004
 trp: 000e msk:  cr2: 7f018c158b47
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Debian installer puts GRUB on main disk without asking

[Toni Casueps]

Hi all,

I wanted to install a Debian Linux system (with LUKS) on the remaining space 
left by a Windows 10 install (with BitLocker and Secure Boot), without messing 
with the Windows boot or the main disk (nvme0n1 below) boot sector . As I 
needed an unencrypted filesystem to put the Linux kernel+initrd and also the 
boot loader, I decided to use a 1 GB pendrive (sda below) for both things

This is how the Debian partition manager looked like (I guess that 'B' means 
boot, but I don't know if that implies that GRUB is going to be installed to 
the main disk...):

Encrypted volume (nvm0n1p4_crypt) - 104.8 GB Linux device-mapper (crypt)
#1  104.8 GBf   ext4/
/dev/nvme0n1 - 512.1 GB
1.0 MB  FREE SPACE
#1  536.9 MB   BK   ESP EFI system partition
#2  134.2 MBMicrosoft reserved partition
#3  406.6 GBBasic data partition
#4  104.9 GBK   crypto  d10root (nvme0n1p4_crypt)
335.4 KBFREE SPACE
SCSI1 (0,0,0) (sda) - 1.0 GB Mass Storage Device
#1 primary  1.0 GB BF   ext4/boot


Later at the boot loader part, it didn't ask if/where to install GRUB. There 
was some message about probing or detecting partitions and at Alt+F4 screen I 
saw something like "grub dummy" but I can't remember exactly what the command 
was. Then it started installing packages

After completing the installation and rebooting, if the pendrive is not 
inserted I see a GRUB screen, which is what I was trying to avoid, and also it 
can't boot Windows or Linux ("minimal BASH like line editing is supported" 
message). If the pendrive is inserted GRUB works fine.

Linux boots fine but Windows' BitLocker didn't like it and wouldn't boot, it 
asked for the BitLocker recovery key, then it "fixed" the boot. After that fix, 
and rebooting, both Linux and Windows boot fine.

For the next time, what would be the correct settings to install both GRUB+boot 
files on the pendrive and not touching the main disk boot at all, or as an 
alternative, install both GRUB+boot files on the main disk and not need the 
pendrive to boot? Or even not using GRUB and just using EFI boot manager?

Thanks