My grandson’s Asus shows a quick list of errors on the bios screen then lags before finally booting.
Well unfortunately that doesn’t show us any errors.
This is taken directly from Mint forums:
Logfiles are kept in the directory /var/log. Usually you find a bunch with the same name, with the older ones of those having a .1, .2, .3, etc., postfixed to their name so you know that isn’t the log file to look at for your current session. Probably the older ones are gzipped as well. syslog is usually a good place to start, or syslog.1 if older. Check the timestamps at the head of the file to see if it starts before or after the problems you had.
Depending on your desktop environment, there may also be a “System Log” or “Log Viewer” application installed that you can use to browse the log files.
I can see the errors but it’s not easy typing the bug out lol, anyway lets get some info.
Screenshots are annoying to try an help when on mobile.
In a terminal run these 3 commands separately. They will produce text files in your home directory.
1st run this:
inxi -Fxz > inxi.txt
2nd run this:
sudo parted -l > parted.txt
3rd run this:
dmesg > dmesg.txt
What we’re doing here with the “command > file.txt” is outputting terminal output to a text file in the current directory
Once complete you can open and copy paste them in the replies, then you can delete them.
I got:
Warning:Unable to open /dev/sf0 read-write (Read-only file system). /dev/sr0
Error: /dev/sr0: unrecognized disk label
The first and third commands rendered nothing.
The second command was where I got the response. (You probably already knew that…).
Not sure what you did, but this is the expected output. granted this is a Virtual Machine I’m doing it from but it is Mint Cinnamon 20.3
bill@bill-VirtualBox:~$ dmesg > dmesg.txt
bill@bill-VirtualBox:~$ sudo parted -l > parted.txt
[sudo] password for bill:
bill@bill-VirtualBox:~$ inxi -Fxz > inxi.txt
bill@bill-VirtualBox:~$ ls -a *.txt
dmesg.txt inxi.txt parted.txt
bill@bill-VirtualBox:~$ cat parted.txt
Model: ATA VBOX HARDDISK (scsi)
Disk /dev/sda: 17.2GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 538MB 537MB primary fat32 boot
2 539MB 17.2GB 16.6GB extended
5 539MB 17.2GB 16.6GB logical ext4
bill@bill-VirtualBox:~$ cat inxi.txt
System: Kernel: 5.4.0-100-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.2.7
Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal
Machine: Type: Virtualbox System: innotek product: VirtualBox v: 1.2 serial:
Mobo: Oracle model: VirtualBox v: 1.2 serial: BIOS: innotek v: VirtualBox
date: 12/01/2006
Battery: ID-1: BAT0 charge: 48.0 Wh condition: 50.0/50.0 Wh (100%) model: innotek 1 status: Unknown
CPU: Topology: Single Core model: Intel Core i5-6300U bits: 64 type: MCP arch: Skylake rev: 3
L2 cache: 3072 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 4991
Speed: 2496 MHz min/max: N/A Core speed (MHz): 1: 2496
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:02.0
Display: x11 server: X.Org 1.20.13 driver: vmware unloaded: fbdev,modesetting,vesa
resolution: 1360x768~60Hz
OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 21.2.6 direct render: Yes
Audio: Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0 v: kernel
bus ID: 00:05.0
Sound Server: ALSA v: k5.4.0-100-generic
Network: Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI port: d020
bus ID: 00:03.0
IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac:
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge driver: piix4_smbus v: N/A
port: d200 bus ID: 00:07.0
Drives: Local Storage: total: 16.00 GiB used: 7.69 GiB (48.1%)
ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 16.00 GiB
Partition: ID-1: / size: 15.19 GiB used: 7.69 GiB (50.6%) fs: ext4 dev: /dev/sda5
Sensors: Message: No sensors data was found. Is sensors configured?
Info: Processes: 167 Uptime: 4m Memory: 1.94 GiB used: 724.9 MiB (36.5%) Init: systemd
runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38
dmesg output is to big for a post, you will have to attach the txt file like I did, see bottom of post here.
bill@bill-VirtualBox:~$ cat dmesg.txt
[ 0.000000] Linux version 5.4.0-100-generic (buildd@lcy02-amd64-002) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #113-Ubuntu SMP Thu Feb 3 18:43:29 UTC 2022 (Ubuntu 5.4.0-100.113-generic 5.4.166)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic root=UUID=964ef45f-676f-4c94-9df8-b4f7cab08e01 ro quiet splash
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Hygon HygonGenuine
[ 0.000000] Centaur CentaurHauls
[ 0.000000] zhaoxin Shanghai
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using ‘standard’ format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ffeffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007fff0000-0x000000007fffffff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.5 present.
[ 0.000000] DMI: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[ 0.000000] Hypervisor detected: KVM
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[ 0.000001] kvm-clock: cpu 0, msr 1a001001, primary cpu clock
[ 0.000001] kvm-clock: using sched offset of 4619144679 cycles
[ 0.000004] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
[ 0.000007] tsc: Detected 2495.986 MHz processor
[ 0.001995] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.001998] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.002003] last_pfn = 0x7fff0 max_arch_pfn = 0x400000000
[ 0.002017] MTRR default type: uncachable
[ 0.002018] MTRR variable ranges disabled:
[ 0.002020] Disabled
[ 0.002022] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[ 0.002024] CPU MTRRs all blank - virtualized system.
[ 0.002026] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC
[ 0.002100] found SMP MP-table at [mem 0x0009fff0-0x0009ffff]
[ 0.075476] check: Scanning 1 areas for low memory corruption
[ 0.075620] RAMDISK: [mem 0x2da33000-0x32d10fff]
[ 0.075627] ACPI: Early table checksum verification disabled
[ 0.075633] ACPI: RSDP 0x00000000000E0000 000024 (v02 VBOX )
[ 0.075637] ACPI: XSDT 0x000000007FFF0030 00003C (v01 VBOX VBOXXSDT 00000001 ASL 00000061)
[ 0.075643] ACPI: FACP 0x000000007FFF00F0 0000F4 (v04 VBOX VBOXFACP 00000001 ASL 00000061)
[ 0.075649] ACPI: DSDT 0x000000007FFF0470 002325 (v02 VBOX VBOXBIOS 00000002 INTL 20190509)
[ 0.075652] ACPI: FACS 0x000000007FFF0200 000040
[ 0.075655] ACPI: FACS 0x000000007FFF0200 000040
[ 0.075658] ACPI: APIC 0x000000007FFF0240 000054 (v02 VBOX VBOXAPIC 00000001 ASL 00000061)
[ 0.075661] ACPI: SSDT 0x000000007FFF02A0 0001CC (v01 VBOX VBOXCPUT 00000002 INTL 20190509)
[ 0.075664] ACPI: Reserving FACP table memory at [mem 0x7fff00f0-0x7fff01e3]
[ 0.075665] ACPI: Reserving DSDT table memory at [mem 0x7fff0470-0x7fff2794]
[ 0.075665] ACPI: Reserving FACS table memory at [mem 0x7fff0200-0x7fff023f]
[ 0.075666] ACPI: Reserving FACS table memory at [mem 0x7fff0200-0x7fff023f]
[ 0.075666] ACPI: Reserving APIC table memory at [mem 0x7fff0240-0x7fff0293]
[ 0.075667] ACPI: Reserving SSDT table memory at [mem 0x7fff02a0-0x7fff046b]
[ 0.075681] ACPI: Local APIC address 0xfee00000
[ 0.075904] No NUMA configuration found
[ 0.075905] Faking a node at [mem 0x0000000000000000-0x000000007ffeffff]
[ 0.075913] NODE_DATA(0) allocated [mem 0x7ffc5000-0x7ffeffff]
[ 0.076080] Zone ranges:…
inxi.txt (2.0 KB)
pam@pam-Q500A:~$ dmesg > dmesg.txt
pam@pam-Q500A:~$ sudo parted -l > parted.txt
[sudo] password for pam:
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0
has been opened read-only.
Error: /dev/sr0: unrecognised disk label
pam@pam-Q500A:~$
I am using Cinnamon 20.2, if that makes a difference
Curious, have you resized any partitions etc on this system?
This may be the root of the problem:
I know nothing about partitions. I looked up how to find them. There is a CD drive (?) built into this computer. I am sorry I didn’t think to tell you that in the beginning.
In case you can’t read it: Partition 1… 537 MB FAT, Partition 2…750 GB Ext 4
Size 537 —530 MB Free
Device /dev/sda1
UUID C56F-34CS
Partition Type EFI System
Contents FAT (32-bit version)–Mounted at /boot/efi
;
Definitely looks off, I do not see a Linux partition. I used Mint 20.3 iso, did the standard install and erase, granted my “disk” sizes are made out of only 20GB vs 750GB, you should have a 3rd one for a running machine. If you still have your bootable thumbdrive, I would suggest booting to it and running disks again and comparing. As you can see from my screens of “Disks” on my VM:
can you attatch the dmesg.txt file, it is locate in your home directory.
That is one long file! I’ve no idea how to send anything like this. I will go on Telegram and ask. If I get an answer before you get to this, I will send the file to you.
Also, I don’t have the original original thumb drive. If I need to, I will make another one.
Thanks for your patience.
Simply attach it just like you did the pictures/screen shots
It worked jsut fine. i looked through it and see the ACPI error messages. Some digging resulted in certain hardware producing the ACPI error messages related to power monitoring sensor. Were you the same one whose laptop was only lasting about 40mins and could not see the percentages or approximate time remaining?
In any event I found a couple bug threads related to the AE_AML_BUFFER_LIMIT and fixes.
https://support.microfocus.com/kb/doc.php?id=7010449#
Again, this seems to be hardware related and I can only suggest these fixes/work arounds.
You could try a different Ubuntu based distro or attempt those fixes as suggested in the threads by blacklisting the module it loads for power monitoring and loading a different one.
I hope this is of some help.
I also noticed at the end of your demsg txt a couple things.
First your inxi output says your running Intel HD for graphics but dmesg showed a modprobe for nvidia. When you first get booted into your desktop does Cinnamon ask you to check your video drivers? My VM does, I will scan through it to see if it too is modprobing for Nvidia.
Second, I see UFW blocking a lot of internal network 192.168.1.# (each is directly followed by it’s ipv6 counterpart). Just noticed it is all.
I am wondering about the partitions. #1 is just MB, while #2 is 750 GB. Below the bar in the photo is a settings icon. I back and clicked on it and saw options to resize, delete, add, etc… Does the fact that the first one is highlighted and the second isn’t mean anything significant? Also if I save Trevor’s school files to a thumb drive and reinstall Mint or another distortion, will they work properly after the new installation? Thanks again
‘
.
I meant distribution!
