ACPI Error

English Install/Boot/Login
1

Hi,
hit another wall when trying to install current Tumbleweed on Acer Travelmate 8204WLMi /Intel Core Duo T2500/ATI Mobility Radeon X1600

Installation works, when restart I can see
“Welcome to Grub” then the three entry choice menu. When (auto) opening openSuse Tumbleweed I get there:

0.148470]    T1] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - 2008 (20211217/dspkginit-438)

repeats three more times then all is stopped.
What can I do? I read up, but BIOS update - I cannot figure out.
Can I choose Advanced options and modify the script?

Thank you.

2

ILL your CPU does not support x86-64. Try to install TW 32-bit.
But your laptop is too old even for web browsing. It is better to replace it.

3

The current TW installation system is probably using the 5.18.15 kernel that isn’t working well with a lot of AMD GPUs. You could try appending spectre_v2=off to the installation’s bootloader linu line. If that doesn’t help, try failsafe mode boot option, or appending textmode=1 to the linu line to run the installation in plain text mode. Also you could try waiting for the next iso, which hopefully will have a fixed kernel, to try again.

ACPI errors are usually red herrings.

I have a bunch of PCs running TW on Core2Duos. They aren’t obsolete yet. The X1600 ultimately might need some special cmdline option(s) for optimal X performance, but should at least be bootable. 9 days ago I upgraded a Core2Duo with X1300 and had no issues I recall, except for 2 displays not working on the modesetting DIX display driver, but OK on the radeon DDX.

4

amdgpu worked fine here. Trouble started with kernel 5.18.15:

**erlangen:~ #** journalctl -b -3 -p3 -g amdgpu 
Aug 07 13:30:44 erlangen kernel: **[drm:[/b]**amdgpu****_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!**
Aug 07 13:30:44 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered**
Aug 07 13:30:54 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x00004401 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0A900000**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E044001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 177209344, read from 'TC1' (0x54433100) (68)**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x00004801 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0A900001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E004001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 177209345, read from 'TC3' (0x54433300) (4)**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x00004801 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0A900000**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E048001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 177209344, read from 'TC0' (0x54433000) (72)**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x03180401 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0A911EDC**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E048001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 177282780, read from 'TC0' (0x54433000) (72)**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x00000801 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0C419B2A**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E008001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 205626154, read from 'TC2' (0x54433200) (8)**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x00204801 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x0A91FAC9**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E008001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 177339081, read from 'TC2' (0x54433200) (8)**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: GPU fault detected: 147 0x08f84801 for process plasmashell pid 5723 thread plasmashel:cs0 pid 5801**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x00000000**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E008001**
Aug 07 13:30:54 erlangen kernel: **amdgpu**** 0000:2b:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32772) at page 0, read from 'TC2' (0x54433200) (8)**
Aug 07 13:31:05 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered**
Aug 07 13:31:15 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered**
**erlangen:~ #**

**erlangen:~ #** journalctl -b -1 -p3 -g amdgpu  
Aug 09 09:15:00 erlangen kernel: **[drm:[/b]**amdgpu******_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!**
Aug 09 09:15:00 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=4194879, emitted seq=4194882**
Aug 09 09:15:00 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* Process information: process Xorg.bin pid 1036 thread Xorg.bin:cs0 pid 1117**
Aug 09 09:15:01 erlangen kernel: **amdgpu****: cp is busy, skip halt cp**
Aug 09 09:15:01 erlangen kernel: **amdgpu****: rlc is busy, skip halt rlc**
Aug 09 09:15:02 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:02 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:02 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:02 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:02 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:34 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:44 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=4194884, emitted seq=4194885**
Aug 09 09:15:44 erlangen kernel: **[drm:[/b]**amdgpu******_job_timedout [amdgpu]] *ERROR* Process information: process firefox pid 29507 thread firefox:cs0 pid 29585**
Aug 09 09:15:44 erlangen kernel: **amdgpu****: cp is busy, skip halt cp**
Aug 09 09:15:45 erlangen kernel: **amdgpu****: rlc is busy, skip halt rlc**
Aug 09 09:15:59 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:59 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:59 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:15:59 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:41:32 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:41:32 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
Aug 09 09:41:32 erlangen kernel: **[drm:[/b]**amdgpu******_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!**
**erlangen:**

**

5

Whenever I’ve tried to boot 64bit on a 32bit CPU, I get a warning right away it can’t be done, and why.

6

And you know the current TW installer isn’t using 5.18.15?

7

I appreciate your participation, but here are some data:

Intel 64 (Intel’s x86-64 implementation) is not supported by Yonah. However, Intel 64 support is integrated in Yonah’s successor, the mobile version of Core 2, code-named Merom.

List of Intel Core processors

8

Man, you’re trolling poor guys?
Amdgpu is too new for ATI Mobility Radeon X1600 = RV530 die.
Mesa 3D used R500 driver for it, now it deprecates R500 and uses R600 driver with unknown level of acceleration.
But it is OpenGL 2.0 (2.1) with limitations, glitches with KDE, no support for KDE’s live buttons, no acceleration with Firefox (and maybe with Chromiums).
2 GiB of RAM means troubles with BTRFS, so user needs ext4/XFS, but with TW it is better to use BTRFS.
But it is DDR2 RAM, so it is upgradable to 2*2 = 4 GiB.
WiFi Intel PRO/Wireless 3945ABG supports 802.11a/b/g only.

I hope HDD is SATA, not IDE.

Core Duo is predecessor for Core2 Duo.
CPU maybe upgradable to Core2 with BIOS update, but IDK.

9

I saw nothing in OP to suggest OP was attempting to use a 64bit TW version. His laptop differs modestly from one PC here, mine just a bit older RV5xx ATI GPU, with single core Intel Pentium Prescott:

# inxi -GSaz --vs
inxi 3.3.20-00 (2022-07-27)
System:
  Kernel: 5.18.12-1-default arch: i686 bits: 32 compiler: gcc v: 12.1.1
    parameters: root=LABEL=<filter> ipv6.disable=1 net.ifnames=0 noresume
  Desktop: KDE Plasma v: 5.25.3 tk: Qt v: 5.15.5 wm: kwin_x11 vt: 7 dm:
    1: KDM 2: XDM Distro: openSUSE Tumbleweed 20220731
Graphics:
  Device-1: AMD RV516 [Radeon X1300/X1550 Series] vendor: Dell driver: radeon
    v: kernel alternate: amdgpu arch: Rage-7 code: R200 process: TSMC 150nm
    built: 2001-06 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 ports:
    active: DVI-I-1,VGA-1 empty: SVIDEO-1 bus-ID: 01:00.0 chip-ID: 1002:7183
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 compositor: kwin_x11 driver: X:
    loaded: radeon unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 761x253mm (29.96x9.96")
    s-diag: 802mm (31.57")
  Monitor-1: DVI-I-1 mapped: DVI-0 pos: primary,left model: NEC EA243WM
    serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
    size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
    max: 1920x1200 min: 640x480
  Monitor-2: VGA-1 mapped: VGA-0 pos: right model: Lenovo L2251x Wide
    serial: <filter> built: 2011 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
    size: 474x296mm (18.66x11.65") diag: 559mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  OpenGL: renderer: ATI RV515 v: 2.1 Mesa 22.1.3 direct render: Yes
10

Thank you all for your time (@mrmazda, @Svyatko, @karlmistelberger) and your input.
I was trying to install 32-bit TW, 64-bit gave immediate error message, as you mentioned before.

I tried the suggestions, but no success. I am unsure if
adding “spectre_v2=off to the installation’s bootloader linu line”
is the same as adding “spectre_v2=off” to the first line of the GNU GRUB version 2.06 script
I also tried “textmode=1”

  • I did not do a bios upgrade, as I cannot find a specific one on the Acer home page. My model does not seem to exist within their selection.
  • I will wait for a new ISO update and try installation again
  • I did not trash the hardware yet :wink: but will do as final option

Best,

11

https://en.opensuse.org/SDB:Debugging_boot_hangThere were problems with Retbleed mitigations in kernel.

Maybe kernel tries to use wrong video driver:

ATI Mobility Radeon X1600 = RV530 die.
Mesa 3D used R500 driver for it, now it deprecates R500 and uses R600 driver with unknown level of acceleration.

12

I’m not sure whether the installation media’s bootloader is Grub, Syslinux, or something else, which is the reason I didn’t use the word Grub there. The portion of your post I highlighted in bold is ambiguous. Grub scripts I’m familiar with have many lines. Grub provides multiple scripts. If you mean the linu lines in boot stanzas in /boot/grub2/grub.cfg, then yes, it’s the same as “the installation’s bootloader linu line”. My thought is that spectre_v2=off most likely is only needed with considerably newer GPUs than your X1600.

The bug that caused spectre_v2=off to be required for some GPUs was fixed in kernels newer than 5.15.15, so with kernel 5.19 in current TW, those who needed it no longer do. 5.19 provided many other changes, so it’s probably time to try installation again. If it fails again, try appending to the bootloader’s linu line radeon.agpmode=-1.

13

Support for AGP was removed from kernel?

14

AFAIK all radeon.agpmode=-1 is supposed to do is ensure use of PCI mode with buggy GPUs. Last AGP Radeon model was 2.5 years after X1600, as OP has. IIRC, I’ve found it necessary in some configurations since AGP support was “removed” from kernel around 2 years ago (5.7?, 5.8?), but not which. It could have been AGP 7xxx, 9xxx or X1950, or PCIe X600, X1300 or HD2xxx.