Acpi error aborting method sb pci0

During boot get these ACPI errors especially AE NOT found.

During boot get these ACPI errors especially AE NOT found.

So I have 2 ssd and 2 hdd, one ssd is transcend and has windows install and 2 partitions.
The other ssd has linux mint and is crucial, uses ext4 and bios for grub.

The error seem to be related to the transcend ssd no error throws up for other disks in the journal. It feels like some grub or boot mbr issue though have tried reinstalling grub but still get the message.

is it a bad error to have.
during boot these errors show up

Code: Select all

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

ACPI Error: Aborting method _SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

ACPI Error: Aborting method _SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

ACPI Error: Aborting method _SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)

in journalctl found these warnings as well

Code: Select all

Run /init as init process
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (PMIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (GPIO) (20190816/ut>
May 19 19:00:19 mintpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
May 19 19:00:19 mintpc kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
May 19 19:00:19 mintpc kernel: i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
May 19 19:00:19 mintpc kernel: r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
May 19 19:00:19 mintpc kernel: ahci 0000:00:1f.2: version 3.0
May 19 19:00:19 mintpc kernel: r8169 0000:03:00.0 eth0: RTL8106e, 00:e0:0d:00:17:3c, XID 449, IRQ 26

Code: Select all

[    1.204246] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204273] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204296] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204321] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.204814] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.204829] fbcon: Taking over console
[    1.204833] No Local Variables are initialized for Method [_GTF]
[    1.204834] No Arguments are initialized for method [_GTF]
[    1.204835] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.204891] Console: switching to colour frame buffer device 80x30
[    1.205093] ata6.00: ATA-9: ST1000DM010-2DM162, CC46, max UDMA/133
[    1.205095] ata6.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[    1.205146] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205152] No Local Variables are initialized for Method [_GTF]
[    1.205153] No Arguments are initialized for method [_GTF]
[    1.205155] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205216] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205222] No Local Variables are initialized for Method [_GTF]
[    1.205223] No Arguments are initialized for method [_GTF]
[    1.205224] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205309] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205315] No Local Variables are initialized for Method [_GTF]
[    1.205316] No Arguments are initialized for method [_GTF]
[    1.205317] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205327] ata1.00: ATA-9: TS256GSSD370S, O0919A, max UDMA/133
[    1.205328] ata1.00: 500118192 sectors, multi 2: LBA48 NCQ (depth 32), AA
[    1.205397] ata5.00: ATA-8: ST3500418AS, CC38, max UDMA/133
[    1.205398] ata5.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32)
[    1.205595] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205601] No Local Variables are initialized for Method [_GTF]
[    1.205603] No Arguments are initialized for method [_GTF]
[    1.205605] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205694] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205700] No Local Variables are initialized for Method [_GTF]
[    1.205701] No Arguments are initialized for method [_GTF]
[    1.205702] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.205844] ata6.00: configured for UDMA/133
[    1.205938] ata1.00: configured for UDMA/133
[    1.206098] scsi 0:0:0:0: Direct-Access     ATA      TS256GSSD370S    9A   PQ: 0 ANSI: 5
[    1.206261] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.206353] sd 0:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB)
[    1.206366] sd 0:0:0:0: [sda] Write Protect is off
[    1.206367] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.206385] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.206425] ata2.00: ATA-10: CT240BX500SSD1, M6CR054, max UDMA/133
[    1.206426] ata2.00: 468862128 sectors, multi 1: LBA48 NCQ (depth 32), AA
[    1.206553] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.206559] No Local Variables are initialized for Method [_GTF]
[    1.206560] No Arguments are initialized for method [_GTF]
[    1.206561] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.206733] ata5.00: configured for UDMA/133
[    1.210618] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.210624] No Local Variables are initialized for Method [_GTF]
[    1.210625] No Arguments are initialized for method [_GTF]
[    1.210627] ACPI Error: Aborting method _SB.PCI0.SAT0.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[    1.213211] ata2.00: configured for UDMA/133
[    1.213336] scsi 1:0:0:0: Direct-Access     ATA      CT240BX500SSD1   054  PQ: 0 ANSI: 5
[    1.213560] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    1.213636] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB)
[    1.213643] sd 1:0:0:0: [sdb] Write Protect is off
[    1.213644] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.213654] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.213707] scsi 4:0:0:0: Direct-Access     ATA      ST3500418AS      CC38 PQ: 0 ANSI: 5
[    1.213854] sd 4:0:0:0: Attached scsi generic sg2 type 0
[    1.213906] sd 4:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[    1.213930] sd 4:0:0:0: [sdc] Write Protect is off
[    1.213931] sd 4:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[    1.213962] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.214021] scsi 5:0:0:0: Direct-Access     ATA      ST1000DM010-2DM1 CC46 PQ: 0 ANSI: 5
[    1.214175] sd 5:0:0:0: [sdd] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    1.214176] sd 5:0:0:0: [sdd] 4096-byte physical blocks
[    1.214179] sd 5:0:0:0: Attached scsi generic sg3 type 0
[    1.214182] sd 5:0:0:0: [sdd] Write Protect is off
[    1.214183] sd 5:0:0:0: [sdd] Mode Sense: 00 3a 00 00
[    1.214192] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.277092]  sda: sda1 sda2 sda3
[    1.277257]  sdb: sdb1 sdb2 < sdb5 >
[    1.296439]  sdd: sdd1 sdd2 sdd3
[    1.305000] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.308597] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.320612] sd 5:0:0:0: [sdd] Attached SCSI disk
[    1.376533] usb 1-1.4: new low-speed USB device number 3 using ehci-pci
[    1.386543]  sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 >
[    1.396518] usb 2-1.2: new full-speed USB device number 3 using ehci-pci
[    1.405008] sd 4:0:0:0: [sdc] Attached SCSI disk
[    1.425213] random: fast init done

Sudo parted -l

Code: Select all

sudo parted -l
[sudo] password for rams:         
Model: ATA TS256GSSD370S (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End    Size   Type     File system  Flags
 1      1049kB  128GB  128GB  primary  ntfs         boot
 2      128GB   129GB  866MB  primary  ntfs         msftres
 3      129GB   256GB  127GB  primary  ntfs


Model: ATA CT240BX500SSD1 (scsi)
Disk /dev/sdb: 240GB
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   240GB  240GB  extended
 5      539MB   240GB  240GB  logical   ext4


Model: ATA ST3500418AS (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      32.3kB  12.6GB  12.6GB  primary   ntfs            boot
 2      12.6GB  500GB   488GB   extended                  lba
 5      12.6GB  24.0GB  11.4GB  logical   ntfs
 6      24.0GB  25.6GB  1620MB  logical   linux-swap(v1)
 7      25.6GB  86.0GB  60.4GB  logical   ntfs
 8      86.0GB  193GB   107GB   logical   ntfs
 9      193GB   301GB   107GB   logical   ntfs
10      301GB   408GB   107GB   logical   ntfs
11      409GB   437GB   28.9GB  logical   ntfs
12      437GB   500GB   62.7GB  logical   ntfs


Model: ATA ST1000DM010-2DM1 (scsi)
Disk /dev/sdd: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 1      1049kB  266GB   266GB  primary  ntfs
 2      266GB   581GB   315GB  primary  ntfs
 3      581GB   1000GB  419GB  primary  ntfs

Inxi

Code: Select all

nxi -Fzxxx
System:
  Kernel: 5.4.0-110-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: INTEL model: H61 serial: <filter> 
  BIOS: American Megatrends v: 4.6.5 date: 12/30/2020 
CPU:
  Topology: Quad Core model: Intel Xeon E31230 bits: 64 type: MT MCP 
  arch: Sandy Bridge rev: 7 L2 cache: 8192 KiB 
  flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 51085 
  Speed: 1596 MHz min/max: 1600/3600 MHz Core speeds (MHz): 1: 1596 2: 1596 
  3: 1594 4: 1596 5: 1596 6: 1596 7: 1596 8: 1596 
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1060 6GB] driver: nvidia v: 510.73.05 
  bus ID: 01:00.0 chip ID: 10de:1b83 
  Display: x11 server: X.Org 1.20.13 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 
  v: 4.6.0 NVIDIA 510.73.05 direct render: Yes 
Audio:
  Device-1: Intel 6 Series/C200 Series Family High Definition Audio 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1c20 
  Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:10f0 
  Device-3: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo 
  bus ID: 2-1.4:5 chip ID: 046d:0825 serial: <filter> 
  Sound Server: ALSA v: k5.4.0-110-generic 
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 
  v: kernel port: d000 bus ID: 03:00.0 chip ID: 10ec:8136 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.82 TiB used: 21.96 GiB (1.2%) 
  ID-1: /dev/sda vendor: Transcend model: TS256GSSD370S size: 238.47 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 9A temp: 33 C scheme: MBR 
  ID-2: /dev/sdb vendor: Crucial model: CT240BX500SSD1 size: 223.57 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 054 temp: 42 C scheme: MBR 
  ID-3: /dev/sdc vendor: Seagate model: ST3500418AS size: 465.76 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC38 temp: 47 C 
  scheme: MBR 
  ID-4: /dev/sdd vendor: Seagate model: ST1000DM010-2DM162 size: 931.51 GiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC46 temp: 45 C 
  scheme: MBR 
Partition:
  ID-1: / size: 218.57 GiB used: 21.96 GiB (10.0%) fs: ext4 dev: /dev/sdb5 
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: nvidia temp: 42 C 
  Fan Speeds (RPM): N/A gpu: nvidia fan: 33% 
Info:
  Processes: 276 Uptime: 23m Memory: 7.73 GiB used: 1.89 GiB (24.4%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.

Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.

Содержание

  1. Шо, опять? Ядро 5.6 и ACPI.
  2. Linux Mint Forums
  3. [Solved] ACPI errors during boot
  4. [Solved] ACPI errors during boot
  5. Re: ACPI errors during boot
  6. Re: ACPI errors during boot
  7. Re: ACPI errors during boot
  8. Re: ACPI errors during boot
  9. Re: ACPI errors during boot
  10. Re: ACPI errors during boot
  11. Re: [Solved] ACPI errors during boot
  12. Re: [Solved] ACPI errors during boot
  13. Linux Mint Forums
  14. [SOLVED] ACPI errors and graphics card drivers issues
  15. [SOLVED] ACPI errors and graphics card drivers issues
  16. Re: ACPI errors and graphics card drivers issues
  17. Re: ACPI errors and graphics card drivers issues
  18. Re: ACPI errors and graphics card drivers issues
  19. Re: ACPI errors and graphics card drivers issues
  20. Re: ACPI errors and graphics card drivers issues
  21. Re: ACPI errors and graphics card drivers issues
  22. Re: ACPI errors and graphics card drivers issues
  23. Re: ACPI errors and graphics card drivers issues
  24. Re: ACPI errors and graphics card drivers issues
  25. Re: ACPI errors and graphics card drivers issues
  26. Re: ACPI errors and graphics card drivers issues
  27. Re: ACPI errors and graphics card drivers issues
  28. Re: ACPI errors and graphics card drivers issues
  29. Re: ACPI errors and graphics card drivers issues
  30. Re: ACPI errors and graphics card drivers issues
  31. Re: ACPI errors and graphics card drivers issues

Шо, опять? Ядро 5.6 и ACPI.

При переходе на 5.6 после выхода из саспенда dmesg спамит, и много чего перестаёт работать:

На 5.5 такого не было.

Куда деваться то со своим «старым» (P8Z68) железом?

Куда деваться то со своим «старым» (P8Z68) железом?

На свалку. У меня на лаптопе еще не такое происходить стало со временем, и всем пофиг на мои баг-репорты. Так что либо придумывай собственные костыли, либо меняй железку.

Как? i7-2600K на свалку?

Разбить? Пол-литру!? Вдребезги? Да я тебя!

не знаю про i7, но на i5 2400 даже сайты уже притормаживают, а на всяком дне типа i5 2410m не стесняясь тормозят в полную силу.

Зачем ты суспендишь десктоп?

ryzen 5 2600/b450 aorus elite

это появилось на 5 ядре, на 4.xx (точно не помню на каком именно), такого не было

У 2600K райзены первого поколения по синглкору посасывают, тащемт.

Я даже растерялся… А почему бы мне его не суспендить?

Каждый день пользуюсь. Наверное, чтоб просто клацнуть кнопкой и сразу начать пользоваться?

Если его не суспендить тоже можно просто сразу пользоваться, лол.

Предлагаешь не выключать?

Ну а сколько он там жрёт? В простое частота падает до 800мгц или сколько там.

Нет, конечно. Это пока «нытик-тред».

оставайся на 4.19

Могут сказать точно, что жрёт 80+ Ватт, так он ещё и не бесшумный.

а есть вообще разумный довод использовать максимально свежее ядро ?

А лучше обновится до Darwin Kernel Version 19.4.0

а есть вообще разумный довод использовать максимально свежее ядро ?

Вообще, конечно, нет.

_GTF — acpi функция переводящая (s)ata порт в состояние по умолчанию (или просто — инициализация).

DSSP — это какой-то флаг, на который ссылается эта функция, и который не установлен. Баг acpi/bios.

Скорее всего, в предыдущих версиях ядра из-за жалоб на эту ошибку, эта функция не вызывалась, а ядро само инициализировало sata-порты (сделали заглушку для конкретной материнки). После очередной чистки кода от старья эту заглушку выкинули и честно дергают acpi-функцию

Если нет проблем с дисками, то эту ошибку можно игнорировать.

Если нет проблем с дисками, то эту ошибку можно игнорировать.

Смотря что считать за проблему с дисками, точно есть проблемы с кедами, последний раз начали крашится ksshaskpass и system settings и может ещё что, обратил внимание только на это, ну и общая отзывчивость системы падает — в этом плане проблемы с дисками несомненно есть.

Ты привел только одну ошибку. И эта acpi-функция в основном простая заглушка, которая ничего не делает, максимум установит еще какой-нибудь флаг, ничего не значащий для работающей системы, чисто внутренняя для acpi, что типа порт инициализирован.

Думаю, у тебя скорее всего поломалось где-то в другом месте. Иначе у тебя при нормальном старте (не пробуждении из suspend) так же глючила система из-за дисков.

Думаю, у тебя скорее всего поломалось где-то в другом месте.

Всё может быть. Но мне кажется, что это всё-таки в ядре дело. На 5.5 не глючит так после выхода из сна.

Куда деваться то со своим «старым» (P8Z68) железом?

Ладно со старым, у меня с новым за последний год дважды спящий режим ломали.

глючит так после выхода из сна.

Это нормальное состояние вплоть до того, что при смене минорной версии (версиии патча) могут поломать засыпание. Потому что это неважная часть линукса, могут глобально перелопатить логику засыпания между патчами с соответствующими последствиями.

Конечно, всё бывает в первый раз. Но не припомню такие проблемы, системнику 8-10 лет.

Но не припомню такие проблемы, системнику 8-10 лет.

Купи себе модный (китайский) ноутбук/нетбук/планшет — будет что припомнить, что забывать не будешь успевать 🙂

Кто-то еще выключает компьютеры, кроме тех, кто собирает шумные ящики?

  1. скорее не связанные вещи, вот у меня с 5.3

ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20190703/psargs-330)

  1. саспенды всегда работали, работают, будут работать с линуксами через одно место. Проще не использовать, тем более, еcли у тебя корабасный десктоп. Выключай на ночь и нормально.

Так было и так будет всегда: кривые, не соответствующие стандартам прошивки на платах Asus. Поэтому в ядре фиксить это никогда не будут.

Впрочем, они почти везде кривые в потребительском железе. Из того, что можно купить за разумные деньги «для дома, для семьи» – только с Supermicro не бывает проблем. Ну, или смотрите списки сертифицированного оборудования, например, redhat.

Как я понимаю ты позорище опенсорса имеешь ввиду сайты как браузер, а не как сервер?

Как сервер www, ppp, ftp, samba, dns, router, и ррочая и прочая даже первый пень до сих пор работоспособным будет.
(и особенно первый, второй и третий пни, так как у них биос в съёмном ПЗУ, а не на флеше, их сейчас как золото беззондовое хранить нужно)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[Solved] ACPI errors during boot

[Solved] ACPI errors during boot

Post by zenmaker » Fri May 20, 2022 10:48 am

During boot get these ACPI errors especially AE NOT found.

So I have 2 ssd and 2 hdd, one ssd is transcend and has windows install and 2 partitions.
The other ssd has linux mint and is crucial, uses ext4 and bios for grub.

The error seem to be related to the transcend ssd no error throws up for other disks in the journal. It feels like some grub or boot mbr issue though have tried reinstalling grub but still get the message.

is it a bad error to have.
during boot these errors show up

Re: ACPI errors during boot

Post by rene » Fri May 20, 2022 10:57 am

Re: ACPI errors during boot

Post by zenmaker » Sat May 21, 2022 6:43 am

The thing was i didnt have this error before, when i was using ubuntu 21.10, hated 22.04 due to snap and stuff and was distro hopping, from debian to fedora to pop but settled on mint.

Its just annoying to see that, im sure its some issue with boot managers on how they are reading the windows disk.

Re: ACPI errors during boot

Post by rene » Sat May 21, 2022 8:34 am

It’s definitely not — but Mint 20.x is on a Ubuntu 20.04 base, i.e., significantly older than 21.10 and.or 22.04, and you are explicitly using the standard 5.4 kernel series.

If you’re sure that 21.10 and/or 22.04 did not show you the ACPI messages you may try upgrading to the 5.13 series: Upgrade Manager -> View -> Linux kernels; pick the newest 5.13 series kernel and reboot into it. Although it doesn’t tend to happen, as a matter of the in the linked tutorial post described BIOS kernel interaction a kernel-sides update may have also fixed (or more likely, simply silenced) this on your system after all.

If not you’d «need» to follow the advise given there as to replacing quiet with loglevel=3 — which for all I know might in fact be something newer Ubuntu releases do OOTB at the moment, although I doubt it.

Re: ACPI errors during boot

Post by zenmaker » Mon May 23, 2022 6:31 am

Hi thanks for the help, so i tested out ubuntu 21.10 impish and jammy on live usb to make sure, funnily impish is the only version it doesnt appear i think its cause of their splash logo probably has the fix you mentioned, while in jammy the errors throw up before logo shows up.

So ended up using loglevel=3 on mint and is now nice and quiet boot, and i can show off to my windows friends how superior linux is without all those errors throwing up on boot

Again thanks for the help and your time much appreciate it.

Re: ACPI errors during boot

Post by Reddog1 » Mon May 23, 2022 8:21 pm

The kernel developers, in their great wisdom, decided to print lower log-level errors on the boot screen, and this has led to a heap of questions about why the acpi errors are occurring. Some other distributions have set the log level=3 out-of-the-box in order to avoid this nuisance.

Please set the topic as [solved]

Re: ACPI errors during boot

Post by rene » Tue May 24, 2022 7:07 am

Re: [Solved] ACPI errors during boot

Post by Reddog1 » Tue May 24, 2022 10:23 pm

Yes, you are right, it is a decision made by the distribution (and those with the distribution that make determinations about the kernel). Anytime errors are shown at boot, it is definitely going to cause consternation, especially among new users. As I mentioned, some distributions have specifically set the /etc/default/grub to not print that log-level of messages.

Here is the stock grub line from an arch-based distro:

GRUB_CMDLINE_LINUX_DEFAULT=»quiet loglevel=3 nowatchdog nvme_load=YES»

Re: [Solved] ACPI errors during boot

Post by rene » Wed May 25, 2022 6:14 am

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] ACPI errors and graphics card drivers issues

[SOLVED] ACPI errors and graphics card drivers issues

Post by Lock3 » Sat Aug 15, 2020 5:50 pm

It’s my first post here, so hello everyone.
I’ve just installed for the first time Linux Mint 64 bits in dual-boot with Windows 10 both in legacy mode.

The dual-boot works fine and so does Mint except that I have these ACPI errors on boot :

Moreover, it is impossible to install the Nvidia drivers which are recommended in the driver manager. When I try to do it, the system doesn’t recognize my graphics card anymore and the image is only managed by the CPU. I specify that I have an RTX 2070.

Secure boot is disabled as well as fast boot on windows 10.

I browsed the forum and tried to modify GRUB without success. Is this a kernel problem?

Thank you in advance for your answers

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sat Aug 15, 2020 6:05 pm

(if you type: the letter F is a capital letter, and don’t omit the space after inxi!)

Copy/paste the output in your next message.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 3:23 am

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 4:22 am

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 5:20 am

I chose a 2015 firmware version because the version of 2018 was still in beta status.

It still doesn’t work.

When I installed Mint I chose «Something Else» in the installer option and I have created a partition in ext4 an / for mount. Do I have to create a swap partition like older version of ubuntu ? Or this is irrelevant for this subject ?

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 5:59 am

I chose a 2015 firmware version because the version of 2018 was still in beta status.

That’s indeed irrelevant.

You might try a kernel update from the Canonical Kernel Team PPA:
https://easylinuxtipsproject.blogspot.c . t.html#ID8
(item 8 )

That should give you the latest kernel from the 5.4 series, which hopefully contains improvements that are relevant for your problem.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 8:36 am

I did as you said and switched to the 5.4.0-44 and unfortunately it doesn’t change anything.

I experience some weird crashes too : I tried to open Rhythmbox or the firewall and it’s stop the current session and send me back to the login screen. (It happens before the kernel update)

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 12:46 pm

So I tried the tip with

I still have the ACPI errors and the graphic card still doesn’t work.

Re: ACPI errors and graphics card drivers issues

Post by Pjotr » Sun Aug 16, 2020 1:03 pm

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 1:42 pm

This beta bios was made only for spectre vulnerability on CPU wich I am already protected.

Many users had issues with this Bios and I will not take my chance with it I think.

It’s a shame beacause Mint works flawlessly on my laptop and it seems to have many issues with a dual boot on legacy mode. Perhaps should I try to convert all the os on EFI mode ? Is it possible anyway without reinstalling the two OS ?

Re: ACPI errors and graphics card drivers issues

Post by SMG » Sun Aug 16, 2020 1:43 pm

When the Nvidia driver loads properly, you will see nvidia in both the device driver and the display driver.

Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: Micro-Star MSI
driver: nvidia v: 450.57 bus ID: 01:00.0

Display: x11 server: X.Org 1.20.8 driver: fbdev,modesetting,nouveau
unloaded: vesa resolution: 640×480

I don’t see it loaded or unloaded in the display drivers, so I’m going to suggest the driver did not install properly. I don’t what method you used to install it, but Pjotr’s website has a section on NVIDIA: how to install the latest video card drivers and roblm has tips for installing on LM20 in this post (scroll to the section in big blue letters — Mint 20 Nvidia Driver Installation Update).

Hopefully information in one of those two places (or both) can help you.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 2:21 pm

I tried the first step already without success unfortunately.

I will try the second one with driver directly downloaded from nvidia website.

Thanks for answering guys.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Sun Aug 16, 2020 6:32 pm

The second one was better than the others

Driver nvidia-450 has worked flawlessly with the roblm installation technique (with the driver downloaded on nvidia website) after

, every program on Mint worked fine, no crashes. UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don’t recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don’t know

Re: ACPI errors and graphics card drivers issues

Post by SMG » Sun Aug 16, 2020 8:26 pm

UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don’t recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don’t know

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Mon Aug 17, 2020 4:59 am

Yes I removed the nomodeset.

I tried a fresh install again this morning, but again it’s like Mint can’t find the GPU nivdia-driver after or during the boot sequence.

Re: ACPI errors and graphics card drivers issues

Post by Lock3 » Mon Aug 17, 2020 5:30 am

OK I’ve got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn’t launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don’t know what.

Re: ACPI errors and graphics card drivers issues

Post by SMG » Mon Aug 17, 2020 12:09 pm

OK I’ve got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn’t launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don’t know what.

That sounds similar to what was happening to several people in this thread. Maybe reading through the thread will help. As I understand it, it is not that something is preventing the driver from starting, but rather something is not telling the driver to start at the correct time in the start-up sequence. I know there is a way to fix this (since several people in the thread were able to do it), but I don’t currently have the knowledge level to be able to guide something through the correct steps for doing it.

Perhaps someone with more knowledge than I currently have will be able to help

Источник

My Ubuntu 18.04 system has been working fine for quite some time (a few years). It suddenly threw up this error. Causes the system to auto-reboot several time. Sometimes it is able to boot into the login but even after login, it is behaving in a cranky manner. What gives?

linux kernel 5.4.0-42-generic

Error

Update:

  1. The BIOS was updated and that resolved the crazy auto-reboot issue and made the system usable.

  2. I found that this Error appears in the dmesg log of both 18.04 and 16.04. Below is a more detailed list of the ACPI error msg (I found some related ACPI msgs was issued but without the ACPI syntax). It seems the issue pertains to the method _GTF. What is that and what does it do? Also, what is a DSSP?

More details from dmesg on the error:

[    1.201570] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.201575] No Local Variables are initialized for Method [_GTF]
[    1.201576] No Arguments are initialized for method [_GTF]
[    1.201577] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.205307] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.205311] No Local Variables are initialized for Method [_GTF]
[    1.205312] No Arguments are initialized for method [_GTF]
[    1.205313] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT0._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.249944] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.249949] No Local Variables are initialized for Method [_GTF]
[    1.249950] No Arguments are initialized for method [_GTF]
[    1.249951] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)
[    1.333524] ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
[    1.333529] No Local Variables are initialized for Method [_GTF]
[    1.333530] No Arguments are initialized for method [_GTF]
[    1.333531] ACPI Error: Aborting method _SB.PCI0.SAT0.PRT1._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-531)

Try rotating through the kernel options.

Worst case scenario run it with acpi=off or noacpi but if you’re not experiencing issues I would just leave it as it it.

acpi=off OR noacpi
This parameter disables the whole ACPI system. This may prove very useful, for example, if your computer does not support ACPI or if you think the ACPI implementation might cause some problems (for instance random reboots or system lockups).

acpi=force
Activates the ACPI system even if your computer BIOS date is older than 2000. This parameter overrides acpi=off and can also be used with current hardware if the ACPI support is not activated despite apm=off.

pci=noacpi OR acpi=noirq
These parameters disable the PCI IRQ routing

pci=acpi
This parameter activates the PCI IRQ routing

acpi_irq_balance
ACPI is allowed to use PIC interrupts to minimize the common use of IRQs.

acpi_irq_nobalance
ACPI is not allowed to use PIC interrupts.

acpi=oldboot
Deactivates the ACPI system almost completely; only the components required for the boot process will be used.

acpi=ht
Deactivates the ACPI system almost completely; only the components required for hyper threading will be used.

noapic
Disable the «Advanced Programmable Interrupt Controller (APIC)».

nolapic
Disable the «local APIC».

apm=off OR noapm
Disable the Advanced Power Management.

irqpoll
Changes the way the kernel handles interrupt calls (set it to polling). Can be useful in case of hardware interrupt issues.

acpi.power_nocheck=1 OR acpi_osi=Linux
Disable the check of power state. Option two modifies the list of supported OS interface strings (changes the OS compatibility reported to the BIOS). Necessary on some broken BIOSes to make temperature/fan control work.

Full info found in https://help.ubuntu.com/community/BootOptions

fgarraud63

Posts: 7
Joined: 2022-01-16 20:35
Has thanked: 1 time

ACPI issue during boot

#1

Post

by fgarraud63 » 2022-01-16 20:44

Hello Everyone,
Thanks for this forum.
I have moved some weeks ago from Windows to Debian.
I’m almost happy with that but i still face an issue during the boot with ACPI.
I have updated the Bios with latest Dell firmware without any change.

Could anyone help me understanding the error bug message and how to fix it please ?

Here is my config :
Dell Inc. Latitude 5424 Rugged
Memory : 31.2 GiB
Processor : Intel® Core™ i7-8650U CPU @ 1.90GHz × 8
Graphics : AMD® Radeon 500 series / Mesa Intel® UHD Graphics 620 (KBL GT2)
Disk : 1.0 TB NVME

OS : Debian GNU/Linux bookworm/sid version testing
OS type : 64 bits
Gnome : 41.2

And here are the dmesg | grep error messages :

[ 0.317572] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.317623] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.317672] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.349328] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.349375] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.349419] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.401925] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.401949] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 0.401969] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.542739] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.542846] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.542945] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.571399] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.575373] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.579438] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.657970] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.VORE._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.660572] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.SKBT._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[ 1.663228] ACPI Error: Aborting method _SB.PCI0.LPCB.ECDV.WANS._STA due to previous error (AE_NOT_FOUND) (20210730/psparse-529)

Thanks in advance,



fgarraud63

Posts: 7
Joined: 2022-01-16 20:35
Has thanked: 1 time

Re: ACPI issue during boot

#3

Post

by fgarraud63 » 2022-01-17 20:14

Hello Keydaha,

Do you think i could be more lucky if i use the Debian stable version ? I think i saw somewhere on internet that this klind of ACPI issues are linked to BIOS. ..
But If yes, could you please guide me on how to move from testing to stable if possible if feasible ?

Thanks


kedaha

Posts: 3509
Joined: 2008-05-24 12:26
Has thanked: 33 times
Been thanked: 75 times

Re: ACPI issue during boot

#4

Post

by kedaha » 2022-01-17 21:23

Hi,
It’s not possible to move from testing to stable. The only way is to do a fresh install. You could always try a Debian stable live CD first to see if you get such ACPI errors.
Using development versions of Debian is like living in a house undergoing extensive renovations and eternal upgrades so I’ll just stick to bullseye myself till bookworm is finished. But, being averse to instability, I’ve always only upgraded from old stable to stable.


User avatar

NorthEast

Posts: 274
Joined: 2018-11-18 04:35
Has thanked: 5 times
Been thanked: 17 times

Re: ACPI issue during boot

#5

Post

by NorthEast » 2022-01-18 01:00

The error output looks like it’s a lot of errors, but they are all anchored to «AE_NOT_FOUND», so it looks like a single problem causing multiple errors really. My brief research suggests it’s a firmware issue. You could boot with the kernel parameter: acpi=off, which will avoid the error of course, but it may have other power management issues that you don’t wish for, but it may not.



fgarraud63

Posts: 7
Joined: 2022-01-16 20:35
Has thanked: 1 time

Re: ACPI issue during boot

#7

Post

by fgarraud63 » 2022-01-18 12:44

Hello, unfortunately no change. i have just boot with bullseye 11 live debian and same messages related to ACPI.
Maybe my laptop is not fully compatible with debian … that’s weird for a Dell laptop.

Any idea how to solve that ?



fgarraud63

Posts: 7
Joined: 2022-01-16 20:35
Has thanked: 1 time

Re: ACPI issue during boot

#9

Post

by fgarraud63 » 2022-01-18 18:06

In fact, i dont see any mulfunction apart from this error message at startup. But as it it has been threre since the begining i don’t know if some feature is missing.
But as for brightness or Fan it seems to be working fine.


kedaha

Posts: 3509
Joined: 2008-05-24 12:26
Has thanked: 33 times
Been thanked: 75 times

Re: ACPI issue during boot

#10

Post

by kedaha » 2022-01-18 18:37

In that case I don’t think there’s anything to worry about but nevertheless, you might like to report it. Meanwhile, perhaps someone here will figure it out. My ancient Acer Aspire One netbook dmesg throws up a bunch of errors but, since it works fine, I just ignore them but maybe I’ll post them some time.


Zod wrote:

Workaround: add pcie_aspm=off to kernel cmdline (add to GRUB_CMDLINE_LINUX in /etc/default/grub, and run update-grub*) – this will negatively impact power consumption

So this is just another workaround for the «Dell logo» issue mentioned earlier (Early Dell logo display in BIOS).
Unfortunately it doesn’t help with the problem I’m experiencing.

seth wrote:

Did you also set «mem_sleep_default=deep»?

Yes, I did because I don’t really care about the s2idle sleep. It drains my battery and fans spin when my laptop is in my backpack.

seth wrote:

Do the delay also happen w/o?

I couldn’t reproduce the problem without mem_sleep_default=deep

If I knew that there will be this many issues with this laptop I would have gotten the non 2-in-1 variant which is apparently a lot better on Linux, but I got this one for half price new, so I thought it will be worth it. smile I mean, it’s not that bad, many issues were solved already by the community, but the issue I’m experiencing is apparently new, because I didn’t find anyone else experiencing it. Anyway, thanks for the help I received so far.

Also, since I posted here, the issue seems a lot harder to reproduce. The freezes still happen, but less often, I guess it’s just unpredictable. Weird, because I haven’t really changed anything since in the configuration.

@EDIT
The only thing changing is the battery charge level. Maybe it influences the probability of a freeze on sleep/wake?

@EDIT

krystiancha wrote:

the issue seems a lot harder to reproduce

Yeah, so the issue is back at its full intensity. If anyone has any more ideas what I can try to solve this, please let me know.

Last edited by krystiancha (2020-10-18 20:11:54)

Error ACPI on boot related with USB

Hi!

I have a fresh installation of Ubuntu 20.04 and apparently the system works ok. But when I boot I can read some errors:

ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT1._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT2._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[…]
ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT13._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT14._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)

One error from POT1 to POT14

My hardware:

Asus ROG STRIX B450-F GAMING
AMD Ryzen 7 2700X 3.7 Ghz
2x Kingston HyperX Fury Black 16GB DDR4 3200Mhz PC-25600 CL16
NVIDIA GeForce 630 rev. 2

My dmseg says:
[…]

[ 0.421320] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 0.421321] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.421322] usb usb1: Product: xHCI Host Controller
[ 0.421323] usb usb1: Manufacturer: Linux 5.4.0-28-generic xhci-hcd
[ 0.421323] usb usb1: SerialNumber: 0000:02:00.0
[ 0.421382] hub 1-0:1.0: USB hub found
[ 0.421394] hub 1-0:1.0: 10 ports detected
[ 0.421476] No Local Variables are initialized for Method [_PLD]
[ 0.421477] No Arguments are initialized for method [_PLD]
[ 0.421478] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT5._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.421488] fbcon: Taking over console
[ 0.421529] Console: switching to colour frame buffer device 240×67
[ 0.422445] No Local Variables are initialized for Method [_PLD]
[ 0.422446] No Arguments are initialized for method [_PLD]
[ 0.422448] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT6._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422506] No Local Variables are initialized for Method [_PLD]
[ 0.422507] No Arguments are initialized for method [_PLD]
[ 0.422508] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT7._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422564] No Local Variables are initialized for Method [_PLD]
[ 0.422565] No Arguments are initialized for method [_PLD]
[ 0.422566] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT8._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422621] No Local Variables are initialized for Method [_PLD]
[ 0.422622] No Arguments are initialized for method [_PLD]
[ 0.422623] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT9._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422676] No Local Variables are initialized for Method [_PLD]
[ 0.422677] No Arguments are initialized for method [_PLD]
[ 0.422678] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.PO10._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422732] No Local Variables are initialized for Method [_PLD]
[ 0.422733] No Arguments are initialized for method [_PLD]
[ 0.422734] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.PO11._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422787] No Local Variables are initialized for Method [_PLD]
[ 0.422788] No Arguments are initialized for method [_PLD]
[ 0.422789] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.PO12._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422843] No Local Variables are initialized for Method [_PLD]
[ 0.422844] No Arguments are initialized for method [_PLD]
[ 0.422845] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.PO13._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.422899] No Local Variables are initialized for Method [_PLD]
[ 0.422900] No Arguments are initialized for method [_PLD]
[ 0.422901] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.PO14._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.423038] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 0.423040] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 0.423043] xhci_hcd 0000:02:00.0: Host supports USB 3.1 Enhanced SuperSpeed
[ 0.423097] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 0.423113] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[ 0.423114] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.423115] usb usb2: Product: xHCI Host Controller
[ 0.423116] usb usb2: Manufacturer: Linux 5.4.0-28-generic xhci-hcd
[ 0.423116] usb usb2: SerialNumber: 0000:02:00.0
[ 0.423176] hub 2-0:1.0: USB hub found
[ 0.423182] hub 2-0:1.0: 4 ports detected
[ 0.423237] No Local Variables are initialized for Method [_PLD]
[ 0.423238] No Arguments are initialized for method [_PLD]
[ 0.423239] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT1._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.423300] No Local Variables are initialized for Method [_PLD]
[ 0.423301] No Arguments are initialized for method [_PLD]
[ 0.423302] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT2._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.423360] No Local Variables are initialized for Method [_PLD]
[ 0.423361] No Arguments are initialized for method [_PLD]
[ 0.423362] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT3._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.423420] No Local Variables are initialized for Method [_PLD]
[ 0.423421] No Arguments are initialized for method [_PLD]
[ 0.423422] ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT4._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20190816/psparse-529)
[ 0.423555] xhci_hcd 0000:0b:00.3: xHCI Host Controller
[ 0.423558] xhci_hcd 0000:0b:00.3: new USB bus registered, assigned bus number 3
[ 0.423651] xhci_hcd 0000:0b:00.3: hcc params 0x0270f665 hci version 0x100 quirks 0x0000000000000410
[ 0.423906] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04
[ 0.423907] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.423908] usb usb3: Product: xHCI Host Controller
[ 0.423908] usb usb3: Manufacturer: Linux 5.4.0-28-generic xhci-hcd
[ 0.423909] usb usb3: SerialNumber: 0000:0b:00.3
[ 0.423966] hub 3-0:1.0: USB hub found
[ 0.423971] hub 3-0:1.0: 4 ports detected
[ 0.424105] xhci_hcd 0000:0b:00.3: xHCI Host Controller
[ 0.424106] xhci_hcd 0000:0b:00.3: new USB bus registered, assigned bus number 4
[ 0.424108] xhci_hcd 0000:0b:00.3: Host supports USB 3.0 SuperSpeed
[ 0.424117] usb usb4: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 0.424129] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04
[ 0.424129] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.424130] usb usb4: Product: xHCI Host Controller
[ 0.424131] usb usb4: Manufacturer: Linux 5.4.0-28-generic xhci-hcd
[ 0.424131] usb usb4: SerialNumber: 0000:0b:00.3
[ 0.424181] hub 4-0:1.0: USB hub found
[ 0.424186] hub 4-0:1.0: 4 ports detected

[…]

Any idea?

Thanks in advance


Re: Error ACPI on boot related with USB

I have the same motherboard and the same ACPI error.

Code:

ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.POT1._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200110/psparse-529)
.....
ACPI Error: Aborting method _SB.PCI0.GPP2.PTXH.RHUB.PO14._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20200110/psparse-529)

However I have not found any functionality impact.

I have W10, Fedora32 and Ubuntu 20.04 installed on this computer. On both Fedora and Ubuntu Logs give this info. I haven’t seen any info on W10.

When I google with «AE_AML_UNINITIALIZED_ELEMENT) (20200110/psparse-529» I get some info
https://bbs.archlinux.org/viewtopic.php?id=243991
https://bugzilla.redhat.com/show_bug.cgi?id=1610727
https://bbs.archlinux.org/viewtopic.php?id=223804

Probably this isn’t important and can be ignored.
Full config

Code:

p-i@pi-Asus-B450-F:~$ inxi -Fz
System:    Kernel: 5.6.7-050607-generic x86_64 bits: 64 Desktop: Gnome 3.36.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:   Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx serial: <filter> UEFI: American Megatrends 
           v: 2704 date: 08/23/2019 
CPU:       Topology: 8-Core model: AMD Ryzen 7 1700 bits: 64 type: MT MCP L2 cache: 4096 KiB 
           Speed: 1373 MHz min/max: 1550/3750 MHz Core speeds (MHz): 1: 1373 2: 1373 3: 1375 4: 1372 5: 1375 6: 1371 7: 1374 
           8: 1372 9: 1373 10: 1375 11: 1379 12: 1374 13: 1373 14: 1375 15: 1373 16: 1372 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
           v: kernel 
           Display: wayland server: X.Org 1.20.8 driver: amdgpu resolution: 2560x1440~60Hz 
           OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.36.0 5.6.7-050607-generic LLVM 9.0.1) 
           v: 4.6 Mesa 20.2.0-devel (git-d510974 2020-05-06 focal-oibaf-ppa) 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
           Sound Server: ALSA v: k5.6.7-050607-generic 
Network:   Device-1: Intel I211 Gigabit Network driver: igb 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 680.02 GiB used: 88.91 GiB (13.1%) 
           ID-1: /dev/nvme0n1 vendor: Kingston model: SA1000M8480G size: 447.13 GiB 
           ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB 
           ID-3: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
Partition: ID-1: / size: 227.74 GiB used: 61.94 GiB (27.2%) fs: ext4 dev: /dev/sda2 
Sensors:   System Temperatures: cpu: 42.0 C mobo: 36.0 C gpu: amdgpu temp: 48 C 
           Fan Speeds (RPM): cpu: 551 case-1: 890 case-2: 824 case-3: 490 gpu: amdgpu fan: 0 
Info:      Processes: 363 Uptime: 9m Memory: 15.56 GiB used: 1.44 GiB (9.3%) Shell: bash inxi: 3.0.38 
p-i@pi-Asus-B450-F:~$


Re: Error ACPI on boot related with USB

Hi P-I H,

I agree, probably can be ignored. Actually I have had no problems on ubuntu.

I want to check how ubuntu works with USB drives (in my old PC I had some USB problems with hardrives and pendrives), but it seems all OK.


View previous topic :: View next topic  
Author Message
Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sat Nov 06, 2021 3:33 pm    Post subject: [solved] ACPI error, how to fix? Reply with quote

Code:
  6.901344] ACPI BIOS Error (bug): Could not resolve symbol [_SB.ALIB], AE_NOT_FOUND (20200925/psargs-330)

[    6.901360] ACPI Error: Aborting method _SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)

[    6.901377] ACPI Error: Aborting method _SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20200925/psparse-529)



Full dmesg at http://dpaste.com/HW3FE989R

Hardware is Gigabyte F2A88X-D3HP

If tried acpi_enforce_resources=no =off =lax and no acpi command line setting at all.

Code:
~ $ uname -a

Linux Trantor 5.10.76-gentoo-r1 #1 SMP Fri Nov 5 21:40:48 CDT 2021 x86_64 AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G AuthenticAMD GNU/Linux

Problem was probably there before latest update which updated xdm and kernel. This computer is the network file and DNS server. it’s on 24/7

Video high performance is not required. No gaming and actually rarely run locally. usually I ssh in.

Last edited by Tony0945 on Sun Nov 07, 2021 1:08 am; edited 1 time in total

Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area

PostPosted: Sat Nov 06, 2021 3:49 pm    Post subject: Reply with quote

Probably an option for the video card that shouldn’t be turned on for your hardware (kernel config). In other words some hardware it doesn’t recognize.

If you just want to shut up the messages add «pcie=noaer» to the kernel cmd line.

Edit to add:

From dmesg => radeon 0000:00:01.0: [drm] fb0: radeondrmfb frame buffer device

it was the last message before acpi error, so probably related.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland


copy of my local repo

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sat Nov 06, 2021 4:41 pm    Post subject: Reply with quote

Code:
~ $ zgrep RADEON /proc/config.gz

CONFIG_DRM_RADEON=m

CONFIG_DRM_RADEON_USERPTR=y

# CONFIG_FB_RADEON is not set



I’ll try turning CONFIG_FB_RADEON on.

Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area

PostPosted: Sat Nov 06, 2021 4:59 pm    Post subject: Reply with quote

You should be using amdgpu not radeon
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland


copy of my local repo
Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sat Nov 06, 2021 5:02 pm    Post subject: Reply with quote

Anon-E-moose wrote:
You should be using amdgpu not radeon



Why?

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sat Nov 06, 2021 5:05 pm    Post subject: Reply with quote

Code:
 6.464320] fbcon: radeondrmfb (fb0) is primary device

[    6.813143] Console: switching to colour frame buffer device 240×67

[    6.823032] radeon 0000:00:01.0: [drm] fb0: radeondrmfb frame buffer device

[    6.891288] ACPI BIOS Error (bug): Could not resolve symbol [_SB.ALIB], AE_NOT_FOUND (20200925/psargs-330)

[    6.891301] ACPI Error: Aborting method _SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)

[    6.891316] ACPI Error: Aborting method _SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20200925/psparse-529)

[    6.891674] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on minor 0



FB_RADEON didn’t help.

Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area

PostPosted: Sat Nov 06, 2021 5:11 pm    Post subject: Reply with quote

Because the radeon driver is basically for the older ati/amd cards. At least that’s my understanding.

Your card is a gcn1.* so should work under amdgpu,

Code:
$ grep VIDEO /etc/portage/make.conf

VIDEO_CARDS=»amdgpu radeonsi»


_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland


copy of my local repo

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sat Nov 06, 2021 5:16 pm    Post subject: Reply with quote

Code:
~ $ grep VIDEO_CARDS /etc/portage/make.conf

#VIDEO_CARDS=»radeonsi»

VIDEO_CARDS=»amdgpu radeonsi radeon»

Been this way for a long time. Should I remove radeonsi?

Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area

PostPosted: Sat Nov 06, 2021 5:24 pm    Post subject: Reply with quote

Tony0945 wrote:
Code:
~ $ grep VIDEO_CARDS /etc/portage/make.conf

#VIDEO_CARDS=»radeonsi»

VIDEO_CARDS=»amdgpu radeonsi radeon»

Been this way for a long time. Should I remove radeonsi?

Take off radeon, leave amdgpu and radeonsi.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland


copy of my local repo

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sat Nov 06, 2021 10:21 pm    Post subject: Reply with quote

That was okay, but error is till there.

Code:
   6.454572] fbcon: radeondrmfb (fb0) is primary device

[    6.803569] Console: switching to colour frame buffer device 240×67

[    6.813393] radeon 0000:00:01.0: [drm] fb0: radeondrmfb frame buffer device

[    6.871102] ACPI BIOS Error (bug): Could not resolve symbol [_SB.ALIB], AE_NOT_FOUND (20200925/psargs-330)

[    6.871117] ACPI Error: Aborting method _SB.PCI0.VGA.ATC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)

[    6.871133] ACPI Error: Aborting method _SB.PCI0.VGA.ATCS due to previous error (AE_NOT_FOUND) (20200925/psparse-529)

[    6.871469] [drm] Initialized radeon 2.50.0 20080528 for 0000:00:01.0 on minor 0

kernel config at http://dpaste.com/354TUE8F4

CPU is AMD A8-7600. I chose this for minimum power as the system is 24/7

BTW, portage updated yesterday but I have no idea how long this has been going on.

Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area

PostPosted: Sat Nov 06, 2021 11:10 pm    Post subject: Reply with quote

Code:
CONFIG_DRM_RADEON=m

CONFIG_DRM_RADEON_USERPTR=y

# CONFIG_DRM_AMDGPU is not set

You have radeon still on and amdgpu off, they need to be reversed

Mine:

Code:
# CONFIG_DRM_RADEON is not set

CONFIG_DRM_AMDGPU=m

CONFIG_DRM_AMDGPU_USERPTR=y

And I use an rx 550, a little newer than yours but not by much.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland


copy of my local repo

Back to top

View user's profile Send private message

NeddySeagoon
Administrator
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

PostPosted: Sat Nov 06, 2021 11:35 pm    Post subject: Reply with quote

Tony0945,

You should use amdgpu with

Code:
VIDEO_CARDS=»amdgpu radeonsi»

radeonsi is for mesa.

Code:
CONFIG_DRM_RADEON=m

CONFIG_DRM_RADEON_USERPTR=y

# CONFIG_DRM_AMDGPU is not set

needs a gentle poking.

Inside the DRM_AMDGPU menu are options oy CI and SI chipset support. I’ve not checked to see if your Radeon r7 250 is one of those.

If it is, choose that option.

Firmware goes into the kernel if you make amdgpu built it, or the kernel will load it if its a module.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 1:00 am    Post subject: Reply with quote

Set kernel config to ANON-E_MOOSE settings.

Haven’t checked either experimental option for lack of knowledge.

Hoping neither is neccessary or that dmesg will give me a clue to which to use.

Picked the APU for power-saving but really wish I just had a cheap NOuveau card like on my newest system. So much simpler than these radeon thingys.

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 1:07 am    Post subject: Reply with quote

Clean dmesg! http://dpaste.com/5FRCVFVV9

I’m marking this solved. Tomorrow I will check that i actually have a screen. But I suspect it is good.

Many thanks! Gentoo forum — users helping users!

EDIT:

And system boots 20% faster!

Back to top

View user's profile Send private message

mike155
Advocate
Advocate

Joined: 17 Sep 2010
Posts: 4312
Location: Frankfurt, Germany

PostPosted: Sun Nov 07, 2021 1:34 am    Post subject: Reply with quote

Quote:
And system boots 20% faster!



Code:
$ grep «rand» Tony0945s_dmesg

[    4.174075] random: udevd: uninitialized urandom read (16 bytes read)

[    4.174434] random: udevd: uninitialized urandom read (16 bytes read)

[    4.240328] random: udevd: uninitialized urandom read (16 bytes read)

[    5.968773] urandom_read: 2 callbacks suppressed

[    5.968775] random: mktemp: uninitialized urandom read (10 bytes read)

[    5.972616] random: dd: uninitialized urandom read (512 bytes read)

[    6.654620] random: dbus-daemon: uninitialized urandom read (12 bytes read)

[    9.152256] random: crng init done

[    9.152260] random: 2 urandom warning(s) missed due to ratelimiting



crng initialization takes 9.1 seconds. Services that read from /dev/random are delayed until the crng is initialized.

You could try to speed up crng initialization with either the hardware random number generator of your CPU (RDRAND) or with a tool like haveged.

Below is the message on my machine with «CONFIG_RANDOM_TRUST_CPU=y» (no haveged)

Code:
[    0.163516] random: crng done (trusting CPU’s manufacturer)



and with «# CONFIG_RANDOM_TRUST_CPU is not set» (no haveged)

Code:
[    4.753650] random: crng init done

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 7:39 am    Post subject: Reply with quote

Code:
~ $ rc-update |grep haveged

              haveged |      default



Maybe should be boot?

Back to top

View user's profile Send private message

Anon-E-moose
Watchman
Watchman

Joined: 23 May 2008
Posts: 5861
Location: Dallas area

PostPosted: Sun Nov 07, 2021 10:41 am    Post subject: Reply with quote

I use rng-tools, and I have it set for boot not default.
_________________
PRIME x570-pro, 3700x, 5.17 zen kernel

gcc 11.2.0/12.2.0, profile 17.1 amd64-no-multilib, openrc, wayland


copy of my local repo
Back to top

View user's profile Send private message

NeddySeagoon
Administrator
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

PostPosted: Sun Nov 07, 2021 11:48 am    Post subject: Reply with quote

Tony0945,

Your console is

Code:
[    0.425731] Console: switching to colour frame buffer device 128×48

[    0.427086] fb0: EFI VGA frame buffer device

There is no radeon or amdgpu support at all from your clean dmesg.

That’s OK if you don’t want a GUI.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 3:16 pm    Post subject: Reply with quote

NeddySeagoon wrote:
There is no radeon or amdgpu support at all from your clean dmesg.

That’s OK if you don’t want a GUI.



But I do have a GUI. I had to go to the basement last night and checked. It was rather washed out looking but functional.

Still, from /etc/conf.d/modules:

Code:
modules=»r8169 ath9k radeon snd_hda_intel»

modules=»${modules} xhci_hcd ahci ohci-pci ehci-pci»

modules=»${modules} pata_atiixp k10temp fam15h_power»

modules=»${modules} it87 i2c-dev i2c-piix4″



I gather I never was supposed to launch radeon. What was I supposed to launch?

EDIT:

Code:
 # modprobe -v radeon

modprobe: FATAL: Module radeon not found in directory /lib/modules/5.10.76-gentoo-r1

Explains why the display never looked very good.

Back to top

View user's profile Send private message

NeddySeagoon
Administrator
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

PostPosted: Sun Nov 07, 2021 3:21 pm    Post subject: Reply with quote

Tony0945,

You have a working GUI for a very low value of working. :)

That may not matter to you.

Either radeon or amdgpu will work for your GPU. amdgpu is probably better supported now.

Both of those framebuffer drivers are missing from your dmesg, so neither is loaded.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 3:45 pm    Post subject: Reply with quote

Substituted amdgpu for radeon in /etc/conf.d/modules and rebooted. Logged in remote X via this computer and it looks pretty good. Of course, that might be the nouveau rendering from this computer, right?

dmesg = http://dpaste.com/FMXDCKQ96

Code:
~ # lsmod

Module                  Size  Used by

i2c_dev                16384  0

it87                   45056  0

hwmon_vid              16384  1 it87

amdgpu               3940352  0

gpu_sched              20480  1 amdgpu

ttm                    69632  1 amdgpu

drm_kms_helper        167936  1 amdgpu

syscopyarea            16384  1 drm_kms_helper

sysfillrect            16384  1 drm_kms_helper

sysimgblt              16384  1 drm_kms_helper

fb_sys_fops            16384  1 drm_kms_helper

drm                   356352  4 gpu_sched,drm_kms_helper,amdgpu,ttm

snd_hda_codec_hdmi     53248  1

snd_hda_codec_realtek   122880  1

snd_hda_codec_generic    69632  1 snd_hda_codec_realtek

ledtrig_audio          16384  1 snd_hda_codec_generic

k10temp                16384  0

i2c_piix4              20480  0

r8169                  90112  0

fam15h_power           16384  0

snd_hda_intel          32768  0

realtek                20480  1

snd_intel_dspcfg       16384  1 snd_hda_intel

mdio_devres            16384  1 r8169

snd_hda_codec          86016  4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek

snd_hwdep              16384  1 snd_hda_codec

libphy                 77824  3 r8169,mdio_devres,realtek

snd_hda_core           53248  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek

snd_pcm                90112  4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core

snd_timer              28672  1 snd_pcm

snd                    61440  8 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm

soundcore              16384  1 snd

acpi_cpufreq           16384  0

Back to top

View user's profile Send private message

NeddySeagoon
Administrator
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

PostPosted: Sun Nov 07, 2021 3:52 pm    Post subject: Reply with quote

Tony0945,

Remote X cannot use the remote hosts GPU. It sends all the screen drawing commands over the network to the local system to render.

VNC can operate in ‘screen scraper’ mode if you ask it nicely but that’s not its default.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 4:40 pm    Post subject: Reply with quote

I’ll just have to go down and look at it myself.

Continuing the urandom problem at new topic https://forums.gentoo.org/viewtopic-p-8675010.html#8675010

Please continue addressing the ACPI/video here.

Back to top

View user's profile Send private message

Tony0945
Watchman
Watchman

Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Sun Nov 07, 2021 8:38 pm    Post subject: Reply with quote

Text looks better with more contrast and sharper with amdgpu. The dune.jpg background looks the same. it looks much more colorful and sharp on this machine using Nouveau on an ancient $30 card.

But I’m glad dmesg looks clean now.

Back to top

View user's profile Send private message

NeddySeagoon
Administrator
Administrator

Joined: 05 Jul 2003
Posts: 51961
Location: 56N 3W

PostPosted: Sun Nov 07, 2021 9:01 pm    Post subject: Reply with quote

Tony0945,

Why do you think its using amdgpu?

That was not shown in your last dmesg.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-

those that do backups

those that have never had a hard drive fail.

Back to top

View user's profile Send private message

Display posts from previous:   

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Acpi bios error при установке windows 10
  • Acpi bios error при установке linux
  • Acpi bios error windows 10 при загрузке ноутбука
  • Acpi bios error supermicro
  • Acpi bios error failure creating named object ubuntu

  • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии