Boot errors

Forum Forums General Hardware Boot errors

  • This topic has 3 replies, 3 voices, and was last updated Dec 18-3:13 pm by dukester.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #72798
    Member
    dukester

      Saw the following in the logs:

      Dec 12 08:35:42 antixbox kernel: [ 3.351831] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20160831/utaddress-247)
      Dec 12 08:35:42 antixbox kernel: [ 3.351833] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20160831/utaddress-247)
      Dec 12 08:35:42 antixbox kernel: [ 3.351842] ACPI: If an ACPI driver is available for this device, you should use it instead of the
      native driver

      Is this fixable at my end?

      At boot-time after the initial GRUB screen, there’s a whack of boot info flying by, one of which is a screw-uo regarding UEFI.
      Can’t find it in any of the logs in /var/log. Where do I look for these msgs so that I can show you guys the problem?

      --
      dukester

      #72799
      Forum Admin
      rokytnji
        Helpful
        Up
        0
        ::

        dmesg | grep acpi

        Might have something to say. Can you give a

        harry@biker:~
        $ inxi -v8 -r
        System:
          Host: biker Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64 
          compiler: gcc v: 8.3.0 
          parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.212-antix.1-amd64-smp 
          root=UUID=fd5a926f-f3df-452b-84d5-d72ac28c3f8b ro vga=791 quiet 
          Desktop: IceWM 2.9.2 vt: 7 dm: SLiM 1.3.6 
          Distro: antiX-19.2_x64-full Hannie Schaft 27 March 2020 
          base: Debian GNU/Linux 10 (buster) 
        Machine:
          Type: Desktop System: Google product: Parrot v: 1.0 
          serial: <superuser required> Chassis: type: 3 serial: <superuser required> 
          Mobo: Google model: Parrot v: 1.0 serial: <superuser required> 
          BIOS: coreboot v: 4.0-6588-g4acd8ea-dirty date: 09/04/2014 
        Battery:
          ID-1: BATX charge: 24.5 Wh (100.0%) condition: 24.5/37.0 Wh (66.2%) 
          volts: 17.2 min: 14.8 model: SANYO AL12B32 type: Li-ion 
          serial: 00000000000026FC status: Full 
        Memory:
          RAM: total: 3.8 GiB used: 1.05 GiB (27.5%) 
          RAM Report: 
          permissions: Unable to run dmidecode. Root privileges required. 
        PCI Slots:
          Permissions: Unable to run dmidecode. Root privileges required. 
        CPU:
          Info: Dual Core model: Intel Celeron 1007U bits: 64 type: MCP 
          arch: Ivy Bridge family: 6 model-id: 3A (58) stepping: 9 microcode: 21 
          cache: L2: 2 MiB bogomips: 5986 
          Speed: 1486 MHz min/max: 800/1500 MHz Core speeds (MHz): 1: 1486 2: 1500 
          Flags: acpi aperfmperf apic arat arch_perfmon bts clflush cmov 
          constant_tsc cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept erms est 
          flexpriority flush_l1d fpu fsgsbase fxsr ht ibpb ibrs kaiser lahf_lm lm 
          mca mce md_clear mmx monitor msr mtrr nonstop_tsc nopl nx pae pat pbe pcid 
          pclmulqdq pdcm pebs pge pln pni popcnt pse pse36 pts rdtscp rep_good sep 
          smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow 
          tsc tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology 
          xtpr 
          Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages 
          Type: l1tf 
          mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled 
          Type: mds mitigation: Clear CPU buffers; SMT disabled 
          Type: meltdown mitigation: PTI 
          Type: spec_store_bypass 
          mitigation: Speculative Store Bypass disabled via prctl and seccomp 
          Type: spectre_v1 
          mitigation: usercopy/swapgs barriers and __user pointer sanitization 
          Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
          IBRS_FW, STIBP: disabled, RSB filling 
          Type: tsx_async_abort status: Not affected 
        Graphics:
          Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
          bus-ID: 00:02.0 chip-ID: 8086:0156 class-ID: 0300 
          Device-2: Chicony type: USB driver: uvcvideo bus-ID: 1-1.3:4 
          chip-ID: 04f2:b336 class-ID: 0e02 
          Display: x11 server: X.Org 1.20.4 driver: loaded: modesetting 
          unloaded: fbdev,vesa display-ID: :0.0 screens: 1 
          Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") 
          s-diag: 414mm (16.3") 
          Monitor-1: LVDS-1 res: 1366x768 hz: 60 dpi: 136 
          size: 256x144mm (10.1x5.7") diag: 294mm (11.6") 
          OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.6 
          compat-v: 3.0 direct render: Yes 
        Audio:
          Device-1: Intel 7 Series/C216 Family High Definition Audio 
          driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 
          class-ID: 0403 
          Sound Server-1: ALSA v: k4.9.212-antix.1-amd64-smp running: yes 
        Network:
          Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Foxconn 
          driver: ath9k v: kernel modules: wl port: 0400 bus-ID: 01:00.0 
          chip-ID: 168c:0034 class-ID: 0280 
          IF: wlan0 state: up mac: 3c:77:e6:26:f5:b5 
          IP v4: 192.168.254.72/24 scope: global broadcast: 192.168.254.255 
          IP v6: fe80::3e77:e6ff:fe26:f5b5/64 scope: link 
          Device-2: Broadcom Limited NetLink BCM57785 Gigabit Ethernet PCIe 
          vendor: Acer Incorporated ALI driver: tg3 v: 3.137 port: 0400 
          bus-ID: 02:00.0 chip-ID: 14e4:16b5 class-ID: 0200 
          IF: eth0 state: down mac: 20:1a:06:14:09:d9 
          WAN IP: 98.18.192.47 
        Bluetooth:
          Device-1: Foxconn / Hon Hai type: USB driver: btusb v: 0.8 bus-ID: 1-1.1:5 
          chip-ID: 0489:e04e class-ID: e001 
          Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: running 
          rfk-block: hardware: no software: yes address: 3C:77:E6:26:F5:B6 
          Info: acl-mtu: 1022:8 sco-mtu: 183:5 link-policy: rswitch hold sniff 
          link-mode: slave accept 
        Logical:
          Message: No logical block device data found. 
        RAID:
          Message: No RAID data found. 
        Drives:
          Local Storage: total: 14.91 GiB used: 7.82 GiB (52.4%) 
          SMART Message: Unable to run smartctl. Root privileges required. 
          ID-1: /dev/sda maj-min: 8:0 vendor: SanDisk model: SSD U100 16GB 
          size: 14.91 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s 
          type: SSD serial: 132149401089 rev: 6.14 scheme: GPT 
          Message: No optical or floppy data found. 
        Partition:
          ID-1: / raw-size: 14.91 GiB size: 14.62 GiB (98.01%) 
          used: 7.82 GiB (53.5%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 
          label: rootantiX19 uuid: fd5a926f-f3df-452b-84d5-d72ac28c3f8b 
        Swap:
          Alert: No swap data was found. 
        Unmounted:
          Message: No unmounted partitions found. 
        USB:
          Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 
          speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
          Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0 
          speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
          Device-1: 1-1.1:5 info: Foxconn / Hon Hai type: Bluetooth driver: btusb 
          interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 0489:e04e 
          class-ID: e001 
          Device-2: 1-1.3:4 info: Chicony type: Video driver: uvcvideo interfaces: 2 
          rev: 2.0 speed: 480 Mb/s power: 500mA chip-ID: 04f2:b336 class-ID: 0e02 
          Hub-3: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 
          speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
          Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0 
          speed: 480 Mb/s chip-ID: 8087:0024 class-ID: 0900 
        Sensors:
          System Temperatures: cpu: 57.0 C mobo: N/A 
          Fan Speeds (RPM): N/A 
        Repos:
          Packages: apt: 1679 lib: 810 
          Active apt repos in: /etc/apt/sources.list.d/antix.list 
          1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/buster buster main nonfree nosystemd
          Active apt repos in: /etc/apt/sources.list.d/buster-backports.list 
          1: deb http://deb.debian.org/debian buster-backports main contrib non-free
          Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
          1: deb http://ftp.us.debian.org/debian/ buster-updates main contrib non-free
          Active apt repos in: /etc/apt/sources.list.d/debian.list 
          1: deb http://ftp.us.debian.org/debian/ buster main contrib non-free
          2: deb http://security.debian.org/ buster/updates main contrib non-free
          Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
          1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
          No active apt repos in: /etc/apt/sources.list.d/onion.list 
          No active apt repos in: /etc/apt/sources.list.d/various.list 
        Processes:
          CPU top: 5 of 180 
          1: cpu: 61.7% command: chrome pid: 8126 mem: 167.8 MiB (4.3%) 
          2: cpu: 3.9% command: google-chrome-stable pid: 19241 
          mem: 256.4 MiB (6.5%) 
          3: cpu: 3.7% command: chrome pid: 19279 mem: 155.5 MiB (3.9%) 
          4: cpu: 0.7% command: chrome pid: 19280 mem: 133.5 MiB (3.4%) 
          5: cpu: 0.5% command: chrome pid: 19350 mem: 162.0 MiB (4.1%) 
          Memory top: 5 of 180 
          1: mem: 256.4 MiB (6.5%) command: google-chrome-stable pid: 19241 
          cpu: 3.9% 
          2: mem: 167.8 MiB (4.3%) command: chrome pid: 8126 cpu: 61.7% 
          3: mem: 162.0 MiB (4.1%) command: chrome pid: 19350 cpu: 0.5% 
          4: mem: 155.5 MiB (3.9%) command: chrome pid: 19279 cpu: 3.7% 
          5: mem: 133.5 MiB (3.4%) command: chrome pid: 19280 cpu: 0.7% 
        Info:
          Processes: 180 Uptime: 2d 16h 41m wakeups: 37849 Init: SysVinit v: 2.93 
          runlevel: 5 default: 5 tool: service Compilers: gcc: 8.3.0 alt: 8 
          Shell: Bash v: 5.0.3 running-in: roxterm inxi: 3.3.06 
        harry@biker:~
        $ 
        

        also wo we can look at your install/hardware. Above is my chromebook install.

        Sometimes I drive a crooked road to get my mind straight.
        Not all who Wander are Lost.
        I'm not outa place. I'm from outer space.

        Linux Registered User # 475019
        How to Search for AntiX solutions to your problems

        #72800
        Member
        Xecure
          Helpful
          Up
          0
          ::

          Warning: a statement or event that warns of something or that serves as a cautionary example

          Error: a message displayed on a monitor screen or printout indicating that an incorrect instruction has been given or that there is an error resulting from faulty software or hardware

          Warnings are OK. They serve as guide if you want to change how something is working. Error are real problems encountered by the operating system, and that require the users attention. I wouldn’t be too concerned about them.

          See all kernel related messages:
          sudo dmesg | less
          See only warning/errors:
          sudo dmesg | grep -i "error\|warning" | less

          I have a similar warning, but I don’t worry about it, as everything works OK with the native driver.

          antiX Live system enthusiast.
          General Live Boot Parameters for antiX.

          #73183
          Member
          dukester
            Helpful
            Up
            1
            ::

            Sorry for late reply! Chemo ….

            Also, right at the beginning of the boot process, there flashes by a fatal msg about not being able to mount UEFI something or other. Goes by so bloody fast, that I can’t cipher out the details. Looked for a GRUB boot long, but no joy! Where does all that initial good stuff get logged to? It’s not in `dmesg’, cuz I’ve checked. No /var/log/boot.log on my system.

            --
            dukester

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.