Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Support for AMD A4-9120C ??
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
fargodwe
n00b
n00b


Joined: 17 Nov 2020
Posts: 5

PostPosted: Tue Nov 17, 2020 10:26 pm    Post subject: Support for AMD A4-9120C ?? Reply with quote

I currently run linux Mint on an Acer Chromebook 315-2ht-47wg using firmware from mychromebox. The video on the APU and the sound are not supported. When I originally ran with Chrome OS it worked fine. I have been told that Chrome OS is based off of Gentoo linux. If that is the case does gentoo support the "C" (specifically for Chromebook) version of this APU?

If not, and if Chrome OS is based off of Gentoo linux, would there be some way to bring in the source code and needed support code from Chrome OS specifically dealing with a driver for my video and a driver for my sound?

Thank you for letting a dumb guy ask a dumb question!
Back to top
View user's profile Send private message
fargodwe
n00b
n00b


Joined: 17 Nov 2020
Posts: 5

PostPosted: Wed Nov 18, 2020 1:19 am    Post subject: Reply with quote

BTW - I mean if I go to gentoo in place of linux Mint.
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23100

PostPosted: Wed Nov 18, 2020 2:39 am    Post subject: Reply with quote

As an initial bit of advice, you should not reply to your own posts. Doing so removes them from the list of unanswered posts, which may cause some people not to see the thread, and then not offer their input on your question. Instead, you should edit your opening post to add your additional remarks. In this case, since I am responding anyway, there is no point in removing your first response, since my post will also be considered an "answer" for the purpose of that search.

To your question:

Support for hardware is primarily dependent on the kernel, rather than a particular distribution (though in the case of video, you often need a userspace component too), so your question is more about whether the upstream Linux kernel, optionally extended with the few patches that Gentoo provides for the Linux kernel, can drive your hardware. Ideally, the answer would be an automatic "yes" since the support clearly exists in the ChromeOS kernel, but some distributions (particularly the more commercial ones) have a nasty habit of using custom kernels with functionality that is not available upstream. By license, they must provide to you the code used in the kernel they shipped - but they are not obligated to submit it upstream, nor to shepherd it through the ensuing review process, so it may only work with a specific, and usually badly outdated, kernel version. It may be of such poor quality or design that the upstream maintainers would refuse to merge it as-is even if it were submitted to them. (Historically, there were several critical components of Google's Android that had this problem.)

If this were my system, I would start by obtaining and posting the PCI IDs of the relevant components. Ideally, use lspci -nnk from inside ChromeOS (if you still have that installed, and if it actually has lspci installed). That will give us the IDs and the name of the kernel driver operating each piece of hardware. Knowing those driver names makes it much easier to find how to configure a custom kernel to match. (This assumes that your only problem is that the non-ChromeOS kernel(s) you used are not built with the right kernel driver. As Mint is a general purpose distribution, I would expect them to have plenty of optional hardware support, but perhaps you are lucky and they just excluded this one as too esoteric. The alternative is that they excluded it because upstream Linux has no driver for it, in which case this gets harder.) If you cannot get lspci inside ChromeOS, then run it from Mint (or Gentoo or any other open Linux you have easy access to).
Back to top
View user's profile Send private message
fargodwe
n00b
n00b


Joined: 17 Nov 2020
Posts: 5

PostPosted: Wed Nov 18, 2020 4:08 am    Post subject: Reply with quote

thank you for the reply. I'm sorry I didn't know to edit my original reply. Since I am currently running the firmware from mrchromebox the chromebook currently does not boot chromeos. I hope the following output from linux Mint terminal will be helpful.
Code:
dave@dave-Aleena:~$ lspci -nnk
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576]
   Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex [1022:1576]
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb)
   DeviceName: VGA compatible controller
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:1eb0]
   Kernel modules: amdgpu
00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15b3]
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15b3]
   Kernel driver in use: snd_hda_intel
   Kernel modules: snd_hda_intel
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge [1022:157b]
00:02.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port [1022:157c]
   Kernel driver in use: pcieport
00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port [1022:157c]
   Kernel driver in use: pcieport
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge [1022:157b]
00:08.0 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Carrizo Platform Security Processor [1022:1578]
   Subsystem: Advanced Micro Devices, Inc. [AMD] Carrizo Platform Security Processor [1022:1578]
00:09.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Carrizo Audio Dummy Host Bridge [1022:157d]
00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7914] (rev 20)
   Subsystem: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7812]
   Kernel driver in use: xhci_hcd
00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller [1022:7908] (rev 49)
   Subsystem: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller [1022:7808]
   Kernel driver in use: ehci-pci
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 4b)
   Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:780b]
   Kernel driver in use: piix4_smbus
   Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 11)
   Subsystem: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:780e]
00:14.7 SD Host controller [0805]: Advanced Micro Devices, Inc. [AMD] FCH SD Flash Controller [1022:7906] (rev 01)
   Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SD Flash Controller [1022:7806]
   Kernel driver in use: sdhci-pci
   Kernel modules: sdhci_pci
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Stoney HT Configuration [1022:15b0]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Stoney Address Maps [1022:15b1]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Stoney DRAM Configuration [1022:15b2]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Stoney Miscellaneous Configuration [1022:15b3]
   Kernel driver in use: k10temp
   Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Stoney PM Configuration [1022:15b4]
   Kernel driver in use: fam15h_power
   Kernel modules: fam15h_power
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Stoney NB Performance Monitor [1022:15b5]
01:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
   Subsystem: Lite-On Communications Inc QCA6174 802.11ac Wireless Network Adapter [11ad:0807]
   Kernel driver in use: ath10k_pci
   Kernel modules: ath10k_pci
02:00.0 SD Host controller [0805]: O2 Micro, Inc. Device [1217:8620] (rev 01)
   Subsystem: O2 Micro, Inc. Device [1217:0002]
   Kernel driver in use: sdhci-pci
   Kernel modules: sdhci_pci
dave@dave-Aleena:~$

If it comes down to needing to see the drivers in use in Chrome I could do that but it will take some work to get back to chromos to do that. It's also a bit of work to get linux back again although I *think* I have made that part simpler since I installed it to a microSD card and run from that instead of the smaller internal emmc.

Thank you!
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

PostPosted: Wed Nov 18, 2020 7:53 am    Post subject: Reply with quote

https://www.cateee.net/lkddb/web-lkddb/DRM_AMDGPU.html

As you can see your VGA device 1002:98e4 is supported since kernel version 4.4.
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
fargodwe
n00b
n00b


Joined: 17 Nov 2020
Posts: 5

PostPosted: Wed Nov 18, 2020 8:27 am    Post subject: Reply with quote

Humm.....I even went so far as to try kernel 5.9 but to no avail. It says it's using amdgpu but it doesn't appear to be working. There are no multiple resolutions and the monitor islisted as unknown. As i remember it, in the older verions of the kernel this would work because i could use/install the old radeon/fglrx driver and x. It has not worked since amdgpu became the default. The latest docs I found said that amdgpu did not uspport the gpu because it is now the wrong GCN or something like that that would be supported. The docs indicate switch of some sort can be set for amdgpu to support older versions but i don't know what that switch is or how to use it. The dmesg in Mint shows the following around amdgpu and seems to deal with both the video and the sound:
Code:
[    1.453244] kernel: (NULL device *): device acp_audio_dma.0.auto added to pm domain
[    1.453245] kernel: (NULL device *): Failed to add dev to genpd
[    1.453489] kernel: [drm:amdgpu_device_ip_init [amdgpu]] *ERROR* hw_init of IP block <acp_ip> failed -22
[    1.453513] kernel: amdgpu 0000:00:01.0: amdgpu_device_ip_init failed
[    1.453518] kernel: amdgpu 0000:00:01.0: Fatal error during GPU init
[    1.453522] kernel: [drm] amdgpu: finishing device.
[    1.453559] kernel: hub 1-1:1.0: USB hub found
[    1.455249] kernel: hub 1-1:1.0: 4 ports detected
[    1.463373] kernel: [drm:dal_irq_service_dummy_ack [amdgpu]] *ERROR* dal_irq_service_dummy_ack: called for non-implemented irq source
[    1.463516] kernel: [drm:dal_irq_service_dummy_set [amdgpu]] *ERROR* dal_irq_service_dummy_set: called for non-implemented irq source
[    1.466334] kernel: ------------[ cut here ]------------
[    1.466553] kernel: WARNING: CPU: 1 PID: 159 at drivers/gpu/drm/amd/amdgpu/amdgpu_object.c:998 amdgpu_bo_unpin.cold+0x0/0x40 [amdgpu]
[    1.466554] kernel: Modules linked in: amdgpu(+) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 aesni_intel gpu_sched cros_ec_dev i2c_algo_bit ttm crypto_simd cryptd drm_kms_helper glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops sdhci_pci drm cqhci sdhci cros_ec_lpcs cros_ec video i2c_hid hid
[    1.466572] kernel: CPU: 1 PID: 159 Comm: systemd-udevd Not tainted 5.4.0-54-generic #60-Ubuntu
[    1.466573] kernel: Hardware name: Google Aleena/Aleena, BIOS MrChromebox-4.12 06/04/2020
[    1.466699] kernel: RIP: 0010:amdgpu_bo_unpin.cold+0x0/0x40 [amdgpu]
[    1.466702] kernel: Code: e9 eb 9d d9 ff 48 c7 c7 88 be 79 c0 41 89 c4 e8 ac 0b a3 de e9 77 9f d9 ff 48 c7 c7 b8 be 79 c0 e8 9b 0b a3 de e9 92 a0 d9 ff <0f> 0b 48 8b bb b0 b0 ff ff 4c 89 e2 48 c7 c6 37 56 7d c0 e8 14 b6
[    1.466703] kernel: RSP: 0018:ffffb3ce003038b8 EFLAGS: 00010246
[    1.466705] kernel: RAX: 0000000000000000 RBX: ffff9a87a8bc4f50 RCX: 0000000000000001
[    1.466706] kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9a8799e23400
[    1.466707] kernel: RBP: ffffb3ce003038f8 R08: ffff9a87a9a1eb00 R09: ffffffffc047df00
[    1.466708] kernel: R10: ffff9a87a99ce000 R11: 0000000000000001 R12: ffff9a8799e23400
[    1.466709] kernel: R13: ffff9a87a8bc4f50 R14: ffff9a87a8bc72f0 R15: ffff9a8799e23400
[    1.466710] kernel: FS:  00007fb5f247c880(0000) GS:ffff9a87aab00000(0000) knlGS:0000000000000000
[    1.466711] kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.466712] kernel: CR2: 000055f218ec1068 CR3: 0000000119fc8000 CR4: 00000000001406e0
[    1.466714] kernel: Call Trace:
[    1.466800] kernel:  amdgpu_bo_free_kernel+0x73/0x120 [amdgpu]
[    1.466897] kernel:  amdgpu_gfx_rlc_fini+0x4b/0x70 [amdgpu]
[    1.466994] kernel:  gfx_v8_0_sw_fini+0xac/0x1a0 [amdgpu]
[    1.467117] kernel:  amdgpu_device_fini+0x26b/0x4ac [amdgpu]
[    1.467197] kernel:  amdgpu_driver_unload_kms+0x52/0xa0 [amdgpu]
[    1.467320] kernel:  amdgpu_driver_load_kms.cold+0x39/0x5c [amdgpu]
[    1.467349] kernel:  drm_dev_register+0x12f/0x170 [drm]
[    1.467429] kernel:  amdgpu_pci_probe+0xf7/0x160 [amdgpu]
[    1.467436] kernel:  ? __pm_runtime_resume+0x60/0x80
[    1.467440] kernel:  local_pci_probe+0x48/0x80
[    1.467442] kernel:  pci_device_probe+0x10f/0x1b0
[    1.467444] kernel:  really_probe+0x159/0x3e0
[    1.467446] kernel:  driver_probe_device+0xbc/0x100
[    1.467447] kernel:  device_driver_attach+0x5d/0x70
[    1.467449] kernel:  __driver_attach+0x8f/0x150
[    1.467450] kernel:  ? device_driver_attach+0x70/0x70
[    1.467453] kernel:  bus_for_each_dev+0x7e/0xc0
[    1.467454] kernel:  driver_attach+0x1e/0x20
[    1.467455] kernel:  bus_add_driver+0x152/0x1f0
[    1.467457] kernel:  driver_register+0x74/0xd0
[    1.467459] kernel:  __pci_register_driver+0x57/0x60
[    1.467552] kernel:  amdgpu_init+0x83/0x8d [amdgpu]
[    1.467554] kernel:  ? 0xffffffffc08ca000
[    1.467558] kernel:  do_one_initcall+0x4a/0x1fa
[    1.467561] kernel:  ? kfree+0x231/0x250
[    1.467564] kernel:  ? _cond_resched+0x19/0x30
[    1.467565] kernel:  ? kmem_cache_alloc_trace+0x1a5/0x240
[    1.467568] kernel:  do_init_module+0x62/0x250
[    1.467570] kernel:  load_module+0x10b8/0x1200
[    1.467573] kernel:  __do_sys_finit_module+0xbe/0x120
[    1.467575] kernel:  ? __do_sys_finit_module+0xbe/0x120
[    1.467578] kernel:  __x64_sys_finit_module+0x1a/0x20
[    1.467580] kernel:  do_syscall_64+0x57/0x190
[    1.467582] kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    1.467583] kernel: RIP: 0033:0x7fb5f23a289d
[    1.467585] kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48
[    1.467586] kernel: RSP: 002b:00007ffd7a0c49b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    1.467588] kernel: RAX: ffffffffffffffda RBX: 000055f218ea4ca0 RCX: 00007fb5f23a289d
[    1.467589] kernel: RDX: 0000000000000000 RSI: 000055f218ea0fe0 RDI: 0000000000000015
[    1.467589] kernel: RBP: 0000000000020000 R08: 0000000000000000 R09: 0000000000000000
[    1.467590] kernel: R10: 0000000000000015 R11: 0000000000000246 R12: 000055f218ea0fe0
[    1.467591] kernel: R13: 0000000000000000 R14: 000055f218e95f80 R15: 000055f218ea4ca0
[    1.467593] kernel: ---[ end trace c6c2e3667ac64cb8 ]---
[    1.467606] kernel: amdgpu 0000:00:01.0: 00000000e82c0020 unpin not necessary
[    1.467787] kernel: ------------[ cut here ]------------
[    1.467788] kernel: Memory manager not clean during takedown.
[    1.467860] kernel: WARNING: CPU: 1 PID: 159 at drivers/gpu/drm/drm_mm.c:939 drm_mm_takedown+0x23/0x30 [drm]
[    1.467861] kernel: Modules linked in: amdgpu(+) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 aesni_intel gpu_sched cros_ec_dev i2c_algo_bit ttm crypto_simd cryptd drm_kms_helper glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops sdhci_pci drm cqhci sdhci cros_ec_lpcs cros_ec video i2c_hid hid
[    1.467874] kernel: CPU: 1 PID: 159 Comm: systemd-udevd Tainted: G        W         5.4.0-54-generic #60-Ubuntu
[    1.467875] kernel: Hardware name: Google Aleena/Aleena, BIOS MrChromebox-4.12 06/04/2020
[    1.467889] kernel: RIP: 0010:drm_mm_takedown+0x23/0x30 [drm]
[    1.467891] kernel: Code: e8 d2 41 e0 de 66 90 0f 1f 44 00 00 48 8b 47 38 48 83 c7 38 48 39 c7 75 01 c3 55 48 c7 c7 d0 b4 2d c0 48 89 e5 e8 d8 44 e0 de <0f> 0b 5d c3 66 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5
[    1.467892] kernel: RSP: 0018:ffffb3ce003038b0 EFLAGS: 00010282
[    1.467893] kernel: RAX: 0000000000000000 RBX: ffff9a87a8bc50e0 RCX: 00000000000002fc
[    1.467894] kernel: RDX: 0000000000000001 RSI: 0000000000000092 RDI: 0000000000000247
[    1.467895] kernel: RBP: ffffb3ce003038b0 R08: 00000000000002fc R09: 0000000000000004
[    1.467896] kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9a87a8bc4f50
[    1.467897] kernel: R13: ffff9a87a86d32e8 R14: ffff9a87a86d3200 R15: 0000000000000170
[    1.467898] kernel: FS:  00007fb5f247c880(0000) GS:ffff9a87aab00000(0000) knlGS:0000000000000000
[    1.467899] kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.467900] kernel: CR2: 000055f218ec1068 CR3: 0000000119fc8000 CR4: 00000000001406e0
[    1.467902] kernel: Call Trace:
[    1.468052] kernel:  amdgpu_vram_mgr_fini+0x31/0xb0 [amdgpu]
[    1.468061] kernel:  ttm_bo_clean_mm+0xac/0xc0 [ttm]
[    1.468143] kernel:  amdgpu_ttm_fini+0x76/0xd0 [amdgpu]
[    1.468226] kernel:  amdgpu_bo_fini+0x12/0x40 [amdgpu]
[    1.468319] kernel:  gmc_v8_0_sw_fini+0x36/0x60 [amdgpu]
[    1.468441] kernel:  amdgpu_device_fini+0x26b/0x4ac [amdgpu]
[    1.468522] kernel:  amdgpu_driver_unload_kms+0x52/0xa0 [amdgpu]
[    1.468646] kernel:  amdgpu_driver_load_kms.cold+0x39/0x5c [amdgpu]
[    1.468667] kernel:  drm_dev_register+0x12f/0x170 [drm]
[    1.468756] kernel:  amdgpu_pci_probe+0xf7/0x160 [amdgpu]
[    1.468761] kernel:  ? __pm_runtime_resume+0x60/0x80
[    1.468764] kernel:  local_pci_probe+0x48/0x80
[    1.468766] kernel:  pci_device_probe+0x10f/0x1b0
[    1.468768] kernel:  really_probe+0x159/0x3e0
[    1.468770] kernel:  driver_probe_device+0xbc/0x100
[    1.468771] kernel:  device_driver_attach+0x5d/0x70
[    1.468773] kernel:  __driver_attach+0x8f/0x150
[    1.468774] kernel:  ? device_driver_attach+0x70/0x70
[    1.468777] kernel:  bus_for_each_dev+0x7e/0xc0
[    1.468778] kernel:  driver_attach+0x1e/0x20
[    1.468779] kernel:  bus_add_driver+0x152/0x1f0
[    1.468781] kernel:  driver_register+0x74/0xd0
[    1.468783] kernel:  __pci_register_driver+0x57/0x60
[    1.468877] kernel:  amdgpu_init+0x83/0x8d [amdgpu]
[    1.468879] kernel:  ? 0xffffffffc08ca000
[    1.468882] kernel:  do_one_initcall+0x4a/0x1fa
[    1.468884] kernel:  ? kfree+0x231/0x250
[    1.468887] kernel:  ? _cond_resched+0x19/0x30
[    1.468888] kernel:  ? kmem_cache_alloc_trace+0x1a5/0x240
[    1.468891] kernel:  do_init_module+0x62/0x250
[    1.468893] kernel:  load_module+0x10b8/0x1200
[    1.468897] kernel:  __do_sys_finit_module+0xbe/0x120
[    1.468898] kernel:  ? __do_sys_finit_module+0xbe/0x120
[    1.468901] kernel:  __x64_sys_finit_module+0x1a/0x20
[    1.468903] kernel:  do_syscall_64+0x57/0x190
[    1.468905] kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    1.468907] kernel: RIP: 0033:0x7fb5f23a289d
[    1.468908] kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48
[    1.468909] kernel: RSP: 002b:00007ffd7a0c49b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    1.468911] kernel: RAX: ffffffffffffffda RBX: 000055f218ea4ca0 RCX: 00007fb5f23a289d
[    1.468912] kernel: RDX: 0000000000000000 RSI: 000055f218ea0fe0 RDI: 0000000000000015
[    1.468913] kernel: RBP: 0000000000020000 R08: 0000000000000000 R09: 0000000000000000
[    1.468913] kernel: R10: 0000000000000015 R11: 0000000000000246 R12: 000055f218ea0fe0
[    1.468914] kernel: R13: 0000000000000000 R14: 000055f218e95f80 R15: 000055f218ea4ca0
[    1.468916] kernel: ---[ end trace c6c2e3667ac64cb9 ]---
[    1.469239] kernel: [TTM] Finalizing pool allocator
[    1.469246] kernel: [TTM] Finalizing DMA pool allocator
[    1.470191] kernel: [TTM] Zone  kernel: Used memory at exit: 50 KiB
[    1.470196] kernel: [drm] amdgpu: ttm finalized
[    1.470232] kernel: ------------[ cut here ]------------
[    1.470233] kernel: sysfs group 'fw_version' not found for kobject '0000:00:01.0'
[    1.470262] kernel: WARNING: CPU: 1 PID: 159 at fs/sysfs/group.c:279 sysfs_remove_group+0x7c/0x80
[    1.470263] kernel: Modules linked in: fjes(-) amdgpu(+) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 aesni_intel gpu_sched cros_ec_dev i2c_algo_bit ttm crypto_simd cryptd drm_kms_helper glue_helper syscopyarea sysfillrect sysimgblt i2c_piix4 fb_sys_fops sdhci_pci drm cqhci sdhci cros_ec_lpcs cros_ec video i2c_hid hid
[    1.470279] kernel: CPU: 1 PID: 159 Comm: systemd-udevd Tainted: G        W         5.4.0-54-generic #60-Ubuntu
[    1.470280] kernel: Hardware name: Google Aleena/Aleena, BIOS MrChromebox-4.12 06/04/2020
[    1.470283] kernel: RIP: 0010:sysfs_remove_group+0x7c/0x80
[    1.470285] kernel: Code: e7 e8 98 b9 ff ff 5b 41 5c 41 5d 5d c3 4c 89 e7 e8 e9 b4 ff ff eb c9 49 8b 55 00 48 8b 33 48 c7 c7 38 ed 38 a0 e8 2f 8a d1 ff <0f> 0b eb d8 0f 1f 44 00 00 48 85 f6 74 37 55 48 89 e5 41 55 41 54
[    1.470286] kernel: RSP: 0018:ffffb3ce00303940 EFLAGS: 00010286
[    1.470288] kernel: RAX: 0000000000000000 RBX: ffffffffc06fba80 RCX: 000000000000033f
[    1.470289] kernel: RDX: 0000000000000001 RSI: 0000000000000092 RDI: 0000000000000247
[    1.470290] kernel: RBP: ffffb3ce00303958 R08: 000000000000033f R09: 0000000000000004
[    1.470291] kernel: R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000000
[    1.470292] kernel: R13: ffff9a87aa0650b0 R14: ffff9a87a8bd4da8 R15: ffff9a87a88c49f0
[    1.470293] kernel: FS:  00007fb5f247c880(0000) GS:ffff9a87aab00000(0000) knlGS:0000000000000000
[    1.470295] kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    1.470295] kernel: CR2: 000055f218ec1068 CR3: 0000000119fc8000 CR4: 00000000001406e0
[    1.470297] kernel: Call Trace:
[    1.470490] kernel:  amdgpu_ucode_sysfs_fini+0x18/0x20 [amdgpu]
[    1.470628] kernel:  amdgpu_device_fini+0x47a/0x4ac [amdgpu]
[    1.470710] kernel:  amdgpu_driver_unload_kms+0x52/0xa0 [amdgpu]
[    1.470837] kernel:  amdgpu_driver_load_kms.cold+0x39/0x5c [amdgpu]
[    1.470865] kernel:  drm_dev_register+0x12f/0x170 [drm]
[    1.470945] kernel:  amdgpu_pci_probe+0xf7/0x160 [amdgpu]
[    1.470950] kernel:  ? __pm_runtime_resume+0x60/0x80
[    1.470954] kernel:  local_pci_probe+0x48/0x80
[    1.470956] kernel:  pci_device_probe+0x10f/0x1b0
[    1.470958] kernel:  really_probe+0x159/0x3e0
[    1.470960] kernel:  driver_probe_device+0xbc/0x100
[    1.470962] kernel:  device_driver_attach+0x5d/0x70
[    1.470963] kernel:  __driver_attach+0x8f/0x150
[    1.470965] kernel:  ? device_driver_attach+0x70/0x70
[    1.470967] kernel:  bus_for_each_dev+0x7e/0xc0
[    1.470968] kernel:  driver_attach+0x1e/0x20
[    1.470970] kernel:  bus_add_driver+0x152/0x1f0
[    1.470971] kernel:  driver_register+0x74/0xd0
[    1.470973] kernel:  __pci_register_driver+0x57/0x60
[    1.471068] kernel:  amdgpu_init+0x83/0x8d [amdgpu]
[    1.471070] kernel:  ? 0xffffffffc08ca000
[    1.471073] kernel:  do_one_initcall+0x4a/0x1fa
[    1.471076] kernel:  ? kfree+0x231/0x250
[    1.471079] kernel:  ? _cond_resched+0x19/0x30
[    1.471080] kernel:  ? kmem_cache_alloc_trace+0x1a5/0x240
[    1.471083] kernel:  do_init_module+0x62/0x250
[    1.471085] kernel:  load_module+0x10b8/0x1200
[    1.471088] kernel:  __do_sys_finit_module+0xbe/0x120
[    1.471090] kernel:  ? __do_sys_finit_module+0xbe/0x120
[    1.471092] kernel:  __x64_sys_finit_module+0x1a/0x20
[    1.471094] kernel:  do_syscall_64+0x57/0x190
[    1.471097] kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[    1.471098] kernel: RIP: 0033:0x7fb5f23a289d
[    1.471100] kernel: Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d c3 f5 0c 00 f7 d8 64 89 01 48
[    1.471101] kernel: RSP: 002b:00007ffd7a0c49b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
[    1.471103] kernel: RAX: ffffffffffffffda RBX: 000055f218ea4ca0 RCX: 00007fb5f23a289d
[    1.471104] kernel: RDX: 0000000000000000 RSI: 000055f218ea0fe0 RDI: 0000000000000015
[    1.471105] kernel: RBP: 0000000000020000 R08: 0000000000000000 R09: 0000000000000000
[    1.471105] kernel: R10: 0000000000000015 R11: 0000000000000246 R12: 000055f218ea0fe0
[    1.471106] kernel: R13: 0000000000000000 R14: 000055f218e95f80 R15: 000055f218ea4ca0
[    1.471109] kernel: ---[ end trace c6c2e3667ac64cba ]---
[    1.472448] kernel: amdgpu: probe of 0000:00:01.0 failed with error -22
[    1.535021] kernel: usb 3-3: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
[    1.556814] kernel: mmc0: new ultra high speed SDR104 SDXC card at address 5048
The Mint forum experts are the ones who told me this is because it's the "C" version of the processor.

I've always wondered if there is an error or non-supprted "thing" of some sort in the replacement firmware from mrchromebox. I have zero idea how to evr know that or how to have the information that might be needed for him to look into it.

As per the Mint hardware forum I added the following to grub to try to enable support. I don't know gentoo sp i have no idea if grub is a mint only thing or if it is more of linux thing.
Code:
GRUB_CMDLINE_LINUX="radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1"


i will probably try going back to the original firmware and obviously chrome os since that's what it supports and try the lspci -nnk.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 8291
Location: Saint Amant, Acadiana

PostPosted: Wed Nov 18, 2020 12:18 pm    Post subject: Reply with quote

https://wiki.gentoo.org/wiki/Radeon

Is your hardware mentioned here?
_________________
My Gentoo installation notes.
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
fargodwe
n00b
n00b


Joined: 17 Nov 2020
Posts: 5

PostPosted: Thu May 20, 2021 5:17 am    Post subject: Support for AMD A4-9120C ?? Reply with quote

I know this is many months old and I apologize for that. I am very much a novice at all of this so I've been trying to read and make sense of some things but not real successfully. As best I can tell, my particular APU's GPU isn't on the list and it doesn't appear it is supported by AMDGPU.

So, being a complete novice at all of this I thought I would try installing GENTOO to the built-in microSD on my weird configuration still keeping my Linux Mint installation "safe" since it is on a removable microSD card.

I'm afraid since I left my days of midrange mainframes, minis and finally micros due to disability in 1996, my comprehension of things has declined terribly. So I see that to "install" GENTOO I am better off booting another distro's livecd and then doing something called a chroot to build GENTOO with what I need. There was a day when something like that would be a piece of cake - today no. I realize it seems to be more of a techie distro and I magically thought that wouldn't be a problem given my past experience. Nope.

So I'm reduced to being one of those dumb people who have to come here and ask for help. Is there something somewhere that might start on the outside with GENTOO and work it's way in so I can understand better? Same for some sort of guide where an idiot as I appear to be today can install GENTOO with wireless and a X desktop of some sort? I know these are ridiculous questions, I really do and I feel embarrassed by them. I just really want to get it installed and try building in some sound modules, etc., to see if:

(1) I can get video to work as it does in ChromeOS and as it used to work when the old Radeon driver was still available until AMDGPU replaced it but dropped support for some of the older GPU's.

(2) I can get sound to work as it does in ChromeOS but not with Linux Mint (or a couple of other distro's I tested)

ANY guidance would be so greatly appreciated. I'm not looking for someone to "do it for me". I want to get this working on my own as much as possible and I just need pointers for where to look for a more novice explanation of GENTOO and it's installation and building (apparently emerge?).

Thanking you in advance.
Back to top
View user's profile Send private message
Hu
Administrator
Administrator


Joined: 06 Mar 2007
Posts: 23100

PostPosted: Thu May 20, 2021 4:36 pm    Post subject: Reply with quote

It's fine to let your thread sit for a while. Sometimes the people helping you will have lost interest by then, but there is never a guarantee someone will come back. I would suggest phrasing your apologies a bit differently next time. When I first read your most recent post, I thought you were an unrelated user resurrecting an old thread, not the OP come back to resume work. ;)

The Gentoo installation handbook is intended to be a resource you can follow. It looks like https://wiki.gentoo.org/wiki/Handbook:Main_Page is the current entry point for the handbook. If you cannot follow it, please come here, describe what part you reached, and why you cannot follow it. Do you get an error that you're not sure how to resolve? Does it ask you to make a decision for which you feel you lack the information required to choose correctly? Is it unclear what you should be doing next?

As I wrote back when the thread was new, video/audio support depends mainly on the kernel, not the distribution. While it's possible that Linux Mint, or Debian, or Fedora, or ... would be unable to drive your video/sound cards due to decisions those distributions made about how to configure their kernel, it seems more likely that if they cannot drive your card, then your card is simply unsupported, at least in the kernel version(s) you tried. That leads to a question: if you cannot make this card work in Gentoo, would you still want to use Gentoo? It's fine if the answer is no. If the answer is no, then I suggest you cut your losses and use a distribution that is less trouble for you. There's no point to forcing yourself to use Gentoo if you don't want to use it. If you want to persevere with Gentoo anyway, that's fine too. We can help you try to get it working.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
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