Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in

  FAQ | Search | Memberlist | Usergroups | Statistics | Profile | Log in to check your private messages | Log in | Register

Can't do a first boot
 View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Sun Aug 29, 2021 11:55 pm    Post subject: Can't do a first boot Reply with quote
Hi,
After successfully installing Gentoo from SystemRescueCD I tried to reboot.
The boot up process started but then stopped and all I see on the screen is:

Code:

fb0: switching to amdgpudrmfb from EFI VGA


This is a link to my kernel configuration.

What am I missing?

Thank you.

P.S. Apologies for making anew thread about it - the old one became polluted.

[Moderator note: the "old one" referenced above seems to be Weird results on install. -Hu]
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Mon Aug 30, 2021 9:03 am    Post subject: Reply with quote
ONEEYEMAN,

You are missing the amdgpu firmware built into the kernel.
There is a big list of things to go in
Code:
CONFIG_EXTRA_FIRMWARE=""


You also need to install linux-firmware, so you have the firmware to build into your kernel.
_________________
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
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Mon Aug 30, 2021 2:47 pm    Post subject: Reply with quote
NeddySeagoon,

Code:

[root@sysrescue /mnt/gentoo/lib/firmware]# lspci | grep -i vga
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev c8)
[root@sysrescue /mnt/gentoo/lib/firmware]#



I checked - there is no firmware for the "Wani" card.

What do I do?

Thank you.
Back to top
View user's profile Send private message
chrissl1983
n00b
n00b


Joined: 27 Oct 2020
Posts: 5
Location: Vienna, Austria
PostPosted: Mon Aug 30, 2021 4:11 pm    Post subject: Re: Can't do a first boot Reply with quote
Hey ONEEYEMAN!

Code:

fb0: switching to amdgpudrmfb from EFI VGA


This message means, that your framebuffer console is being switched over to the amdgpu drm driver. Most likely there is some problem loading the (missing) firmware within the amdgpu module therefore you don't see any more output after that message.

Your current kernel config has CONFIG_DRM_AMDGPU=y so amdgpu is built into the kernel. If a driver is built in the kernel and needs to load firmware for the device to function, the firmware has to be integrated into the kernel (putting it in the initramfs in NOT enough).


Try this:

1) Make sure you have emerged the linux-firmware:
Code:
emerge --ask sys-kernel/linux-firmware


2) (Re-)Build your kernel with the amdgpu driver as a module (set CONFIG_DRM_AMDGPU=m):

Code:
Location:
    -> Device Drivers
        -> Graphics support
            ->  AMD GPU (DRM_AMDGPU [=m])


3) Reboot your system (make sure you don't remove EFI framebuffer support!).


If you are happy with the module kicking in a little later (after the initframfs and other modules are loaded), you can stop here. If you want to have the amdgpudrm-framebuffer active early on, continue with this:


4) To find out which firmware blobs are the right ones for your GPU, do a:
Code:
dmesg | grep firmware


You should see something like:

Code:
[    2.990443] Loading firmware: amdgpu/carizzo_ce.bin
[    2.992556] Loading firmware: amdgpu/carizzo_mec.bin
[    2.992747] Loading firmware: amdgpu/carizzo_pfp.bin
....


NOTE: I am just assuming you might have a carizzo GPU, adapt according to the output you found in dmesg.


5) Find out the firmware blobs available for your GPU:

Code:

cd /lib/firmware; ls amdgpu/carrizo*


Output:

Code:

amdgpu/carrizo_ce.bin  amdgpu/carrizo_mec.bin   amdgpu/carrizo_pfp.bin  amdgpu/carrizo_sdma.bin   amdgpu/carrizo_uvd.bin
amdgpu/carrizo_me.bin  amdgpu/carrizo_mec2.bin  amdgpu/carrizo_rlc.bin  amdgpu/carrizo_sdma1.bin  amdgpu/carrizo_vce.bin


This is the list of firmware blobs you will have to build into the kernel.

6) Add this list to the EXTRA_FIRMWARE kernel configuration:

Code:

Location:
-> Device Drivers
    -> Generic Driver Options
        -> Firmware loader
        -> Firmware loading facility (FW_LOADER [=y])
            ->  Build named firmware blobs into the kernel binary (EXTRA_FIRMWARE [=amdgpu/carrizo_ce.bin  amdgpu/carrizo_mec.bin ...]
            -> Firmware blobs root directory (EXTRA_FIRMWARE_DIR=[/lib/firmware])


7) Rebuild the kernel and the initramfs again

8) Reboot and enjoy...


HTH :)

You probably want to play with the video kernel parameter when going this route, as in: video=1920x1080-32 :wink:
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Mon Aug 30, 2021 4:38 pm    Post subject: Reply with quote
ONEEYEMAN,

We need the Vendor and Device IDs of the video card.
Post the output of
Code:
lspci -nnk
for the video card please.

Ahhh. Its Can't find files for AMDGPU WANI in linux-firmware and chrissl1983 is spot on.
_________________
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
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Mon Aug 30, 2021 5:23 pm    Post subject: Re: Can't do a first boot Reply with quote
Hi,
chrissl1983 wrote:

Hey ONEEYEMAN!

Code:

fb0: switching to amdgpudrmfb from EFI VGA


This message means, that your framebuffer console is being switched over to the amdgpu drm driver. Most likely there is some problem loading the (missing) firmware within the amdgpu module therefore you don't see any more output after that message.

Your current kernel config has CONFIG_DRM_AMDGPU=y so amdgpu is built into the kernel. If a driver is built in the kernel and needs to load firmware for the device to function, the firmware has to be integrated into the kernel (putting it in the initramfs in NOT enough).


Try this:

1) Make sure you have emerged the linux-firmware:
Code:
emerge --ask sys-kernel/linux-firmware


2) (Re-)Build your kernel with the amdgpu driver as a module (set CONFIG_DRM_AMDGPU=m):

Code:
Location:
    -> Device Drivers
        -> Graphics support
            ->  AMD GPU (DRM_AMDGPU [=m])



I presume I will need to add the module inside the /etc/modules-load.d/amdgpu.conf, right?
Or that would be /etc/modules-load.d/video.conf?

chrissl1983 wrote:

3) Reboot your system (make sure you don't remove EFI framebuffer support!).


If you are happy with the module kicking in a little later (after the initframfs and other modules are loaded), you can stop here. If you want to have the amdgpudrm-framebuffer active early on, continue with this:


I will probably stop there.
Then I will just set the VIDEO_CARD parameter and install GNOME + Wayland.

Thank you.

chrissl1983 wrote:

4) To find out which firmware blobs are the right ones for your GPU, do a:
Code:
dmesg | grep firmware


You should see something like:

Code:
[    2.990443] Loading firmware: amdgpu/carizzo_ce.bin
[    2.992556] Loading firmware: amdgpu/carizzo_mec.bin
[    2.992747] Loading firmware: amdgpu/carizzo_pfp.bin
....


NOTE: I am just assuming you might have a carizzo GPU, adapt according to the output you found in dmesg.


5) Find out the firmware blobs available for your GPU:

Code:

cd /lib/firmware; ls amdgpu/carrizo*


Output:

Code:

amdgpu/carrizo_ce.bin  amdgpu/carrizo_mec.bin   amdgpu/carrizo_pfp.bin  amdgpu/carrizo_sdma.bin   amdgpu/carrizo_uvd.bin
amdgpu/carrizo_me.bin  amdgpu/carrizo_mec2.bin  amdgpu/carrizo_rlc.bin  amdgpu/carrizo_sdma1.bin  amdgpu/carrizo_vce.bin


This is the list of firmware blobs you will have to build into the kernel.

6) Add this list to the EXTRA_FIRMWARE kernel configuration:

Code:

Location:
-> Device Drivers
    -> Generic Driver Options
        -> Firmware loader
        -> Firmware loading facility (FW_LOADER [=y])
            ->  Build named firmware blobs into the kernel binary (EXTRA_FIRMWARE [=amdgpu/carrizo_ce.bin  amdgpu/carrizo_mec.bin ...]
            -> Firmware blobs root directory (EXTRA_FIRMWARE_DIR=[/lib/firmware])


7) Rebuild the kernel and the initramfs again

8) Reboot and enjoy...


HTH :)

You probably want to play with the video kernel parameter when going this route, as in: video=1920x1080-32 :wink:
Back to top
View user's profile Send private message
chrissl1983
n00b
n00b


Joined: 27 Oct 2020
Posts: 5
Location: Vienna, Austria
PostPosted: Mon Aug 30, 2021 5:26 pm    Post subject: Re: Can't do a first boot Reply with quote
ONEEYEMAN wrote:


chrissl1983 wrote:


2) (Re-)Build your kernel with the amdgpu driver as a module (set CONFIG_DRM_AMDGPU=m):

Code:
Location:
    -> Device Drivers
        -> Graphics support
            ->  AMD GPU (DRM_AMDGPU [=m])



I presume I will need to add the module inside the /etc/modules-load.d/amdgpu, right?


Ooops... I forgot that one. Good you caught it! ;-)

ONEEYEMAN wrote:


I will probably stop there.
Then I will just set the VIDEO_CARD parameter and install GNOME + Wayland.

Thank you.


NP, you're welcome! :-)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Mon Aug 30, 2021 5:31 pm    Post subject: Reply with quote
Module loading should be automatic when the hardware in detected.
_________________
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
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Mon Aug 30, 2021 5:51 pm    Post subject: Reply with quote
NeddySeagoon,
Not necessarily.
The WiFi card/network card modukes do not always loads.

Or I am missing something here?

Thank you.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Mon Aug 30, 2021 6:02 pm    Post subject: Reply with quote
ONEEYEMAN,

I thought networking was fixed a long time ago.
It does no harm to load the modules explicitly.
_________________
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
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Tue Aug 31, 2021 1:44 am    Post subject: Reply with quote
Hi, guys,
Building AMDGPU as a module made proceed further.

However, I now have a Kernel Panic!!
At least now it is something I can work off. ;-)

This is what I got:

Quote:

VFS: Cannot open root device "sda3" or inknown block(0,0): error --6
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: unable to mount root fs on unknown block(0,0)


This is my fstab:

Code:

[root@sysrescue ~]# cat /mnt/gentoo/etc/fstab
# /etc/fstab: static file system information.
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed); notail increases performance of ReiserFS (at the expense of storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#
# The root filesystem should have a pass number of either 0 or 1.
# All other filesystems should have a pass number of 0 or greater than 1.
#
# See the manpage fstab(5) for more information.
#

# <fs>         <mountpoint>   <type>      <opts>      <dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
#
# NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3
#       filesystems.  This just tells the kernel to use the ext4 driver.
#
# NOTE: You can use full paths to devices like /dev/sda3, but it is often
#       more reliable to use filesystem labels or UUIDs. See your filesystem
#       documentation for details on setting a label. To obtain the UUID, use
#       the blkid(8) command.

/dev/sda1      /boot      vfat      noauto,noatime   1 2
/dev/sda3      /      ext4      noatime      0 1
/dev/sda2      none      swap      sw      0 0
/dev/cdrom      /mnt/cdrom   auto      noauto,ro   0 0
[root@sysrescue ~]#


And I did build FS4 support in the kernel and not as a module.

What am I missing?
Is it because I have a wrong hard drive driver?

Thank you.

P.S.:

Below is a complete lspci -v output:

Code:

[root@sysrescue ~]# lspci -v
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Complex
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0

00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) I/O Memory Management Unit
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 24
   Capabilities: [40] Secure device <?>
   Capabilities: [64] MSI: Enable+ Count=1/4 Maskable- 64bit+
   Capabilities: [74] HyperTransport: MSI Mapping Enable+ Fixed+

00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] (rev c8) (prog-if 00 [VGA controller])
   DeviceName: ATI EG BROADWAY
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 52, IOMMU group 0
   Memory at e0000000 (64-bit, prefetchable) [size=256M]
   Memory at f0000000 (64-bit, prefetchable) [size=8M]
   I/O ports at 2000 [size=256]
   Memory at f0c00000 (32-bit, non-prefetchable) [size=256K]
   Expansion ROM at 000c0000 [disabled] [size=128K]
   Capabilities: [48] Vendor Specific Information: Len=08 <?>
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
   Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
   Capabilities: [270] Secondary PCI Express
   Capabilities: [2b0] Address Translation Service (ATS)
   Capabilities: [2c0] Page Request Interface (PRI)
   Capabilities: [2d0] Process Address Space ID (PASID)
   Kernel driver in use: amdgpu
   Kernel modules: amdgpu

00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 50, IOMMU group 0
   Memory at f0c60000 (64-bit, non-prefetchable) [size=16K]
   Capabilities: [48] Vendor Specific Information: Len=08 <?>
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
   Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
   Kernel driver in use: snd_hda_intel
   Kernel modules: snd_hda_intel

00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge
   Flags: fast devsel, IOMMU group 1

00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port (prog-if 00 [Normal decode])
   Flags: bus master, fast devsel, latency 0, IRQ 26, IOMMU group 1
   Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
   I/O behind bridge: [disabled]
   Memory behind bridge: f0b00000-f0bfffff [size=1M]
   Prefetchable memory behind bridge: [disabled]
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Port (Slot+), MSI 00
   Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1234
   Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
   Capabilities: [270] Secondary PCI Express
   Kernel driver in use: pcieport

00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Root Port (prog-if 00 [Normal decode])
   Flags: bus master, fast devsel, latency 0, IRQ 27, IOMMU group 1
   Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
   I/O behind bridge: [disabled]
   Memory behind bridge: f0a00000-f0afffff [size=1M]
   Prefetchable memory behind bridge: [disabled]
   Capabilities: [50] Power Management version 3
   Capabilities: [58] Express Root Port (Slot+), MSI 00
   Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [c0] Subsystem: Advanced Micro Devices, Inc. [AMD] Device 1234
   Capabilities: [c8] HyperTransport: MSI Mapping Enable+ Fixed+
   Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
   Capabilities: [270] Secondary PCI Express
   Kernel driver in use: pcieport

00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Host Bridge
   Flags: fast devsel, IOMMU group 2

00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Carrizo Platform Security Processor
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 3, IOMMU group 3
   Memory at f0c40000 (64-bit, prefetchable) [size=128K]
   Memory at f0900000 (32-bit, non-prefetchable) [size=1M]
   Memory at f0c6f000 (32-bit, non-prefetchable) [size=4K]
   Memory at f0c6a000 (32-bit, non-prefetchable) [size=8K]
   Capabilities: [50] MSI-X: Enable- Count=2 Masked-
   Capabilities: [5c] HyperTransport: MSI Mapping Enable+ Fixed+
   Capabilities: [60] Power Management version 3
   Capabilities: [a4] PCI Advanced Features

00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Carrizo Audio Dummy Host Bridge
   Flags: fast devsel, IOMMU group 4

00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Audio Controller
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 49, IOMMU group 4
   Memory at f0c64000 (32-bit, non-prefetchable) [size=16K]
   Capabilities: [60] Power Management version 3
   Capabilities: [a4] PCI Advanced Features
   Kernel driver in use: snd_hda_intel
   Kernel modules: snd_hda_intel

00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 20) (prog-if 30 [XHCI])
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 18, IOMMU group 5
   Memory at f0c68000 (64-bit, non-prefetchable) [size=8K]
   Capabilities: [50] Power Management version 3
   Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
   Capabilities: [90] MSI-X: Enable+ Count=8 Masked-
   Capabilities: [a0] Express Root Complex Integrated Endpoint, MSI 00
   Capabilities: [100] Latency Tolerance Reporting
   Kernel driver in use: xhci_hcd
   Kernel modules: xhci_pci

00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 49) (prog-if 01 [AHCI 1.0])
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 19, IOMMU group 6
   I/O ports at 2118 [size=8]
   I/O ports at 2124 [size=4]
   I/O ports at 2110 [size=8]
   I/O ports at 2120 [size=4]
   I/O ports at 2100 [size=16]
   Memory at f0c6c000 (32-bit, non-prefetchable) [size=1K]
   Capabilities: [60] Power Management version 3
   Capabilities: [70] SATA HBA v1.0
   Kernel driver in use: ahci

00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 49) (prog-if 20 [EHCI])
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 18, IOMMU group 7
   Memory at f0c6d000 (32-bit, non-prefetchable) [size=256]
   Capabilities: [c0] Power Management version 2
   Capabilities: [e4] Debug port: BAR=1 offset=00e0
   Kernel driver in use: ehci-pci

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 4a)
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: 66MHz, medium devsel, IOMMU group 8
   Kernel driver in use: piix4_smbus
   Kernel modules: i2c_piix4, sp5100_tco

00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 8

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 0
   Flags: fast devsel, IOMMU group 9

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 1
   Flags: fast devsel, IOMMU group 9

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 2
   Flags: fast devsel, IOMMU group 9

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 3
   Flags: fast devsel, IOMMU group 9
   Capabilities: [f0] Secure device <?>
   Kernel driver in use: k10temp
   Kernel modules: k10temp

00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 4
   Flags: fast devsel, IOMMU group 9
   Kernel driver in use: fam15h_power
   Kernel modules: fam15h_power

00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 60h-6fh) Processor Function 5
   Flags: fast devsel, IOMMU group 9

01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
   Subsystem: Hewlett-Packard Company Device 81aa
   Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 1
   Memory at f0b00000 (32-bit, non-prefetchable) [size=4K]
   Capabilities: [40] Power Management version 3
   Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [70] Express Endpoint, MSI 00
   Capabilities: [100] Advanced Error Reporting
   Capabilities: [140] Device Serial Number 00-00-00-01-00-4c-e0-00
   Kernel driver in use: rtsx_pci
   Kernel modules: rtsx_pci

02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)
   DeviceName: Intel WLAN Intel 7265NGWG.NVW Stone Peak 2 D0 ac 2x2 + BT 4 LE PCIe+USB NGFF 2230 WW non-vPro
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Flags: bus master, fast devsel, latency 0, IRQ 47, IOMMU group 1
   Memory at f0a00000 (64-bit, non-prefetchable) [size=8K]
   Capabilities: [c8] Power Management version 3
   Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
   Capabilities: [40] Express Endpoint, MSI 00
   Capabilities: [100] Advanced Error Reporting
   Capabilities: [140] Device Serial Number a4-02-b9-ff-ff-4a-8b-57
   Capabilities: [14c] Latency Tolerance Reporting
   Capabilities: [154] L1 PM Substates
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi

[root@sysrescue ~]#


P.P.S.: BTW, Neddy Seagoon, you were right - I didn't need to add amdgpu to loading modules.
.
Back to top
View user's profile Send private message
chrissl1983
n00b
n00b


Joined: 27 Oct 2020
Posts: 5
Location: Vienna, Austria
PostPosted: Tue Aug 31, 2021 7:04 am    Post subject: Reply with quote
Hey ONEEYEMAN!

Good that the amdgpu stuff is working. :wink: I am on the run, so I gotta be brief.

I assume you have a SATA disk, for this to work you also need SCSI disk support which is disabled in the kernel config you provided (if that one is still current?), try this:

Code:
Depends on: SCSI [=y]
Location:
    -> Device Drivers
        -> SCSI device support [=Y]



If that doesn't help please kindly provide dmesg output and your current kernel config... :)

EDIT: Are you also providing the correct kernel parameters? Are you using genkernel, dracut or something custom to generate your initramfs?
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Tue Aug 31, 2021 4:23 pm    Post subject: Reply with quote
Hi,
Silly me.
I had SCSI turned on but not SCSI hard drive. ;-)

Now the machine boots up.

However, it fails to load the iwlwifi driver.

The kernel has the debugging option for the driver itself. I turned them on, but it didn't produce anything.

I presume there are some generic network debug option that needs to be turned on in order to see the error.

THank you.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Tue Aug 31, 2021 5:17 pm    Post subject: Reply with quote
ONEEYEMAN,

Put the dmesg onto a pastebin.

iwlwifi needs firmware, so make sure its a module.

Debugging options can interfere with normal operation. They are intended for use by kernel developers.
Turn that off.
_________________
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
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Tue Aug 31, 2021 5:37 pm    Post subject: Reply with quote
NeddySeagoon,
That's the problem - dmesg doesn't have any errors in it.

Running:

Code:

dmesg | grep -i error


doesn't produce any errors.

I just thought that there should be a generic Network debugging option and/or 80211-specific ones to help with that.

Yet on the screen during the boot I clearly see the message that loading fails.
And then net.wlan0 is not active.

That driver is built as a module. And I also installed wpa_supplicant and configured it.

Laptop doesn't have a wired interface, so I will need to save the output, reboot and post it.

Will be later on today though.
Back to top
View user's profile Send private message
chrissl1983
n00b
n00b


Joined: 27 Oct 2020
Posts: 5
Location: Vienna, Austria
PostPosted: Tue Aug 31, 2021 6:21 pm    Post subject: Reply with quote
ONEEYEMAN wrote:
NeddySeagoon,
That's the problem - dmesg doesn't have any errors in it.

Running:

Code:

dmesg | grep -i error



Try following instead:

Code:
dmesg -l err


Most error messages don't have the string "error" in them so grep won't find them all, but dmesg can filter by message types like info, warn and err (see dmesg --help for all of them)
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Tue Aug 31, 2021 9:32 pm    Post subject: Reply with quote
ONEEYEMAN,

What is missing is as important as what is actually in dmesg.
We can't spot what is missing but should be there with only dmesg fragments.
Hence my request for all of it.
_________________
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
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Tue Aug 31, 2021 11:31 pm    Post subject: Reply with quote
NeddySeagoon,
Here is the dmesg requested.

Thank you.
Back to top
View user's profile Send private message
ONEEYEMAN
Advocate
Advocate


Joined: 01 Mar 2005
Posts: 3650
PostPosted: Wed Sep 01, 2021 1:24 am    Post subject: Reply with quote
NeddySeagoon et al
It looks like I did get a connection.
All I needed to do is to fix the name of the interface with the udev rule.

However there is an error in the dmesg about loading some firmware.

Could someone please look at that?

Thank you.
Back to top
View user's profile Send private message
chrissl1983
n00b
n00b


Joined: 27 Oct 2020
Posts: 5
Location: Vienna, Austria
PostPosted: Sun Sep 05, 2021 10:52 am    Post subject: Reply with quote
There are a few firmware messages in your dmesg. Some seem to be BIOS quirks - nothing unusual, nothing to worry about. Which one has you thinking it is related to your wifi problems?

ONEEYEMAN wrote:
NeddySeagoon et al
It looks like I did get a connection.
All I needed to do is to fix the name of the interface with the udev rule.

However there is an error in the dmesg about loading some firmware.

Could someone please look at that?

Thank you.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 54578
Location: 56N 3W
PostPosted: Sun Sep 05, 2021 11:28 am    Post subject: Reply with quote
ONEEYEMAN,

There are no firmware errors in dmesg that matter.

The really important message is
Code:
[    4.977364] iwlwifi 0000:02:00.0: loaded firmware version 29.4063824552.0 7265D-29.ucode op_mode iwlmvm


Code:
[   12.013025] wlan0: authenticate with 78:f2:9e:c9:38:48
[   12.018119] wlan0: send auth to 78:f2:9e:c9:38:48 (try 1/3)
[   12.020978] wlan0: authenticated
[   12.022040] wlan0: associate with 78:f2:9e:c9:38:48 (try 1/3)
[   12.025235] wlan0: RX AssocResp from 78:f2:9e:c9:38:48 (capab=0x1411 status=0 aid=3)
[   12.026342] wlan0: associated

That says that the radio link worked and the interface is named wlan0

Code:
dhcpcd wlan0
should make wlan0 work until your dhcp lease expires.

Did you deliberately prevent udev from renaming the interface or is there a problem with udev?

There is no attempt in dmesg to actually set it up for IPv4 but IPv6 has done its automatic thing.
Code:
 [   12.207762] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

_________________
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:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo 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



 Links: forums.gentoo.org | www.gentoo.org | bugs.gentoo.org | wiki.gentoo.org | forum-mods@gentoo.org

Copyright 2001-2024 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy