[SOLVED] Display Not Properly Detected

Kernels & Hardware, configuring network, installing services

[SOLVED] Display Not Properly Detected

Postby John Guy » 2018-11-24 17:22

What's wrong: My display has a resolution of 1366 x 768 (16:9), but I'm only getting 800 x 600 (4:3). The full display is being used, but everything is much larger and fuzzier than it should be. Under GNOME Settings, it calls the display "Unknown" and gives 800 x 600 as the only option. I also have Windows 10 on my computer, and the display works flawlessly when running that.

What I have: An HP Pavilion laptop with an AMD Ryzen 3 2300U and Radeon Vega 6 graphics. I have Windows 10 on the internal drive, and I run Debian 9.5 Stable from an external one. Here's what I got from xrandr and lspci:
Code: Select all
xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 800 x 600, maximum 800 x 600
default connected primary 800x600+0+0 0mm x 0mm
   800x600       75.00*

Code: Select all
lspci | grep VGA
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 15dd (rev cc)
04:00.7 Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Device 15e6


What I've done: I installed Debian onto an external drive with nonfree wifi firmware to have the wifi work. That was a success, but the screen resolution was low and could not be changed. I first tried a fix from this article: https://mike42.me/blog/2018-01-how-to-use-a-radeon-graphics-card-on-debian-9, but it didn't work. That solution failed because lspci | grep Radeon returned nothing for me. I then tried a solution on the Debian Wiki: https://wiki.debian.org/AtiHowTo, but that didn't work either.

Does anyone know how to fix this?
Last edited by John Guy on 2018-11-30 01:29, edited 1 time in total.
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Re: Display Not Properly Detected

Postby Head_on_a_Stick » 2018-11-24 17:26

You will probably need a newer kernel[1] for Ryzen, perhaps backported amdgpu drivers and firmware as well, maybe even the Mesa stack for full support.

Check
Code: Select all
lspci -k

to see if any kernel drivers have been loaded for your card.

[1] viewtopic.php?f=16&t=139003
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8324
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Display Not Properly Detected

Postby stevepusser » 2018-11-24 17:31

Let me know if you use my OBS repo, which should be a little easier than using backports, and if it worked. Thanks!

I'm considering putting the new Sid 4.8.20 kernel backport into it, but all I can find in the changelog is STIBP being enabled for 4.18.19, which causes performance loss on many machines, and I don't see anything about it being reverted like the latest Liquorix kernel did.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, 4.19.5 kernel, wine-staging 4.0~rc1, Pale Moon 28.2.2, Mesa 18.2.6, Midori 7.0
User avatar
stevepusser
 
Posts: 10281
Joined: 2009-10-06 05:53

Re: Display Not Properly Detected

Postby John Guy » 2018-11-24 17:58

My response to Head_on_a_Stick:
lspci -k showed that no kernel drivers were running for the "VGA compatible controller" or the "Non-VGA unclassified device. I then looked at AMD graphics firmware backports for Stretch, but the closest match in the list of contents for one of the packages was for the Vega 10: https://packages.debian.org/stretch-backports/firmware-amd-graphics

My response to stevepusser:
How would I access your OBS repository?
What is STIBP?
And is Liquorix a version of Linux, or a replacement?
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Re: Display Not Properly Detected

Postby Head_on_a_Stick » 2018-11-24 18:03

John Guy wrote:lspci -k showed that

Please post verbatim output rather than vague descriptions, it is clearer for us and less effort for you.
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8324
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Display Not Properly Detected

Postby John Guy » 2018-11-24 19:07

Here's the nice long list of output:

Code: Select all
lspci -k
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15d0
   Subsystem: Hewlett-Packard Company Device 84e7
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 15d1
   Subsystem: Hewlett-Packard Company Device 84e7
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3
   Kernel driver in use: pcieport
   Kernel modules: shpchp
00:01.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3
   Kernel driver in use: pcieport
   Kernel modules: shpchp
00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15d3
   Kernel driver in use: pcieport
   Kernel modules: shpchp
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1452
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15db
   Kernel driver in use: pcieport
   Kernel modules: shpchp
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 15dc
   Kernel driver in use: pcieport
   Kernel modules: shpchp
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
   Subsystem: Hewlett-Packard Company FCH SMBus Controller
   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 51)
   Subsystem: Hewlett-Packard Company FCH LPC Bridge
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e8
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15e9
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ea
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15eb
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ec
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ed
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ee
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 15ef
01:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0113 (rev 01)
   Subsystem: Toshiba America Info Systems Device 0001
   Kernel driver in use: nvme
   Kernel modules: nvme
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Kernel driver in use: iwlwifi
   Kernel modules: iwlwifi
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
   Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   Kernel driver in use: r8169
   Kernel modules: r8169
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 15dd (rev cc)
   Subsystem: Hewlett-Packard Company Device 84e7
04:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device 15de
   Subsystem: Hewlett-Packard Company Device 84e7
   Kernel driver in use: snd_hda_intel
   Kernel modules: snd_hda_intel
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 15df
   Subsystem: Hewlett-Packard Company Device 84e7
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15e0
   Subsystem: Hewlett-Packard Company Device 84e7
   Kernel driver in use: xhci_hcd
   Kernel modules: xhci_pci
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15e1
   Subsystem: Hewlett-Packard Company Device 84e7
   Kernel driver in use: xhci_hcd
   Kernel modules: xhci_pci
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Device 15e3
   Subsystem: Hewlett-Packard Company Device 84e7
   Kernel driver in use: snd_hda_intel
   Kernel modules: snd_hda_intel
04:00.7 Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Device 15e6
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 15e4
05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 61)
   Subsystem: Hewlett-Packard Company FCH SATA Controller [AHCI mode]
   Kernel driver in use: ahci
   Kernel modules: ahci


The VGA parts:

Code: Select all
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 15dd (rev cc)
   Subsystem: Hewlett-Packard Company Device 84e7
04:00.7 Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Device 15e6
   Subsystem: Advanced Micro Devices, Inc. [AMD] Device 15e4
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Re: Display Not Properly Detected

Postby Head_on_a_Stick » 2018-11-24 20:49

^ There is no kernel driver loaded, are you running the backported kernel yet?
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8324
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Display Not Properly Detected

Postby stevepusser » 2018-11-24 21:39

My response to stevepusser:
How would I access your OBS repository?
What is STIBP?
And is Liquorix a version of Linux, or a replacement?


The answer to the first question is in that first thread that HOAS linked to.

STIBP is something added to the latest Linux kernel releases to mitigate some security issue that had the unintended effect of severe performance hits for some operations on some hardware, and will be reverted soon. It's in the 4.8.20 Debian kernel for sure, so if I upload it, users would have to boot with "nospectre_v2" in the kernel command line to turn it off if desired.

The Liquorix kernel is an alternative to the Debian kernel, and has some major differences, such as being low-latency yet still allowing the Nvidia drivers to build on it, unlike the Debian realtime kernel. I also maintain a repository on the OBS that has backported Liquorix kernels for Jessie, Stretch, and Ubuntu 14.04.

Yes, there is no backported xserver-xorg-video-amdgpu driver in stretch-backports, but there is in my OBS repo, as well as an updated "radeon" driver for AMD hardware not supported by amdgpu.
Last edited by stevepusser on 2018-11-24 22:54, edited 1 time in total.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, 4.19.5 kernel, wine-staging 4.0~rc1, Pale Moon 28.2.2, Mesa 18.2.6, Midori 7.0
User avatar
stevepusser
 
Posts: 10281
Joined: 2009-10-06 05:53

Re: Display Not Properly Detected

Postby John Guy » 2018-11-24 22:49

Oh, I never saw Head_on_a_Stick's link. I followed the steps on that thread: http://forums.debian.net/viewtopic.php?f=16&t=139003, but they didn't work. After loading Debian with the Linux 4.18.0-0.bpo.1-amd64 kernel and putting in my LUKS password, it froze. I tried it a few times, but it still didn't work.
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Re: Display Not Properly Detected

Postby stevepusser » 2018-11-24 23:05

Can you please be more specific about what you put into the terminal and what packages you upgraded? There is also
a history of packages handled by the apt system in /var/log/apt/history.log you can check.
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, 4.19.5 kernel, wine-staging 4.0~rc1, Pale Moon 28.2.2, Mesa 18.2.6, Midori 7.0
User avatar
stevepusser
 
Posts: 10281
Joined: 2009-10-06 05:53

Re: Display Not Properly Detected

Postby John Guy » 2018-11-24 23:59

Here's my apt log for today:
Code: Select all
Start-Date: 2018-11-24  10:56:06
Commandline: apt-get install firmware-linux-free firmware-linux-nonfree
Install: intel-microcode:amd64 (3.20180807a.1~deb9u1, automatic), iucode-tool:amd64 (2.1.1-1, automatic), firmware-amd-graphics:amd64 (20161130-4, automatic), amd64-microcode:amd64 (3.20160316.3, automatic), firmware-linux-nonfree:amd64 (20161130-4), firmware-misc-nonfree:amd64 (20161130-4, automatic)
End-Date: 2018-11-24  10:56:18

Start-Date: 2018-11-24  16:01:41
Commandline: packagekit role='install-packages'
Requested-By: john (1000)
Install: libc-ares2:amd64 (1.12.0-1+deb9u1, automatic), bzflag-data:amd64 (2.4.8-1, automatic), bzflag-client:amd64 (2.4.8-1)
End-Date: 2018-11-24  16:01:43

Start-Date: 2018-11-24  16:08:25
Commandline: packagekit role='install-packages'
Requested-By: john (1000)
Install: libupnp6:amd64 (1:1.6.19+git20160116-1.2, automatic), openclonk:amd64 (7.0-4), openclonk-data:amd64 (7.0-4, automatic), libtinyxml2.6.2v5:amd64 (2.6.2-4, automatic), libalut0:amd64 (1.1.0-5+b2, automatic)
End-Date: 2018-11-24  16:08:29

Start-Date: 2018-11-24  16:15:34
Commandline: packagekit role='install-packages'
Requested-By: john (1000)
Install: substance-flamingo:amd64 (7.3+dfsg3-2, automatic), libflamingo-java:amd64 (7.3+dfsg3-2, automatic), liblaf-plugin-java:amd64 (7.3+dfsg3-2, automatic), substance:amd64 (7.3+dfsg3-2, automatic), libtrident-java:amd64 (7.3+dfsg3-2, automatic), triplea:amd64 (1.8.0.9+dfsg-1), libcommons-httpclient-java:amd64 (3.1-12, automatic), libupnp-java:amd64 (1.0.4+triplea-1, automatic), liblaf-widget-java:amd64 (7.3+dfsg3-2, automatic)
End-Date: 2018-11-24  16:15:52

Start-Date: 2018-11-24  16:18:23
Commandline: packagekit role='remove-packages'
Requested-By: john (1000)
Remove: triplea:amd64 (1.8.0.9+dfsg-1)
End-Date: 2018-11-24  16:18:24

Start-Date: 2018-11-24  18:07:56
Commandline: apt install -t stretch-backports linux-image-amd64
Install: linux-image-4.18.0-0.bpo.1-amd64:amd64 (4.18.6-1~bpo9+1, automatic), libapparmor-perl:amd64 (2.11.0-3+deb9u2, automatic), apparmor:amd64 (2.11.0-3+deb9u2, automatic)
Upgrade: linux-image-amd64:amd64 (4.9+80+deb9u6, 4.18+98~bpo9+1)
End-Date: 2018-11-24  18:08:19

All of the middle entries were me downloading games from the GNOME Software app.

So far with packages, I have the firmware-linux-free and firmware-linux-nonfree ones, along with the backported Linux image (4.18), apparmor, and a library that came along with it. The new image doesn't work, so I'm using Linux 4.9.0-8 to run Debian.

As for what I put into the terminal right before trying the new 4.18, I did exactly what HOAS wrote in his thread: http://forums.debian.net/viewtopic.php?f=16&t=139003. I don't have a log of my terminal, so I can't show you what I put in.
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Re: Display Not Properly Detected

Postby Head_on_a_Stick » 2018-11-25 12:09

John Guy wrote:I have the firmware-linux-free and firmware-linux-nonfree ones, along with the backported Linux image (4.18)

Does the firmware match the kernel? Are they all from backports?

This may clarify things:
Code: Select all
# apt install apt-show-versions
apt-show-versions | grep backports
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8324
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Display Not Properly Detected

Postby John Guy » 2018-11-25 12:55

Here's what happened when I ran that code:
Code: Select all
# apt install apt-show-versions
Reading package lists... Done
Building dependency tree       
Reading state information... Done
apt-show-versions is already the newest version (0.22.7).
The following packages were automatically installed and are no longer required:
  libcommons-httpclient-java libflamingo-java liblaf-plugin-java
  liblaf-widget-java libtrident-java libupnp-java linux-image-4.9.0-7-amd64
  substance substance-flamingo
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
# apt-show-versions | grep backports
linux-image-4.18.0-0.bpo.1-amd64:amd64/stretch-backports 4.18.6-1~bpo9+1 uptodate
linux-image-amd64:amd64/stretch-backports 4.18+98~bpo9+1 uptodate

And some extra:
Code: Select all
# apt-show-versions | grep firmware-linux
firmware-linux:all/stretch 20161130-4 uptodate
firmware-linux-free:all/stretch 3.4 uptodate
firmware-linux-nonfree:all/stretch 20161130-4 uptodate

They were not all from backports. I tried getting a backport of firmware-linux, but this is what happened:
Code: Select all
# apt install firmware-linux=20180825+dfsg-1~bpo9+1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 firmware-linux : Depends: firmware-linux-nonfree (= 20180825+dfsg-1~bpo9+1) but 20161130-4 is to be installed
E: Unable to correct problems, you have held broken packages.

Is my system a broken distribution now? Should I install the backport of firmware-linux-nonfree (20180825+dfsg-1~bpo9+1), then of firmware-linux (20180825+dfsg-1~bpo9+1), and then reboot into the newer Linux kernel (4.18)?
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Re: Display Not Properly Detected

Postby Head_on_a_Stick » 2018-11-25 12:59

John Guy wrote:Should I install the backport of firmware-linux-nonfree (20180825+dfsg-1~bpo9+1), then of firmware-linux (20180825+dfsg-1~bpo9+1), and then reboot into the newer Linux kernel (4.18)?

Yes.

Try
Code: Select all
# apt install -t stretch-backports firmware-linux{,-nonfree}
dbruce wrote:Ubuntu forums try to be like a coffee shop in Seattle. Debian forums strive for the charm and ambience of a skinhead bar in Bacau. We intend to keep it that way.
User avatar
Head_on_a_Stick
 
Posts: 8324
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Display Not Properly Detected

Postby John Guy » 2018-11-25 14:08

HUUUUUURAAAAAAAAY!

That did it!

Ah, it looks so good!

Here's the code for reference:
Code: Select all
# apt install -t stretch-backports firmware-linux{,-nonfree}
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libcommons-httpclient-java libflamingo-java liblaf-plugin-java
  liblaf-widget-java libtrident-java libupnp-java linux-image-4.9.0-7-amd64
  substance substance-flamingo
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  firmware-amd-graphics firmware-misc-nonfree
The following packages will be upgraded:
  firmware-amd-graphics firmware-linux firmware-linux-nonfree
  firmware-misc-nonfree
4 upgraded, 0 newly installed, 0 to remove and 154 not upgraded.
Need to get 5,422 kB of archives.
After this operation, 9,048 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.debian.org/debian stretch-backports/non-free amd64 firmware-amd-graphics all 20180825+dfsg-1~bpo9+1 [2,329 kB]
Get:2 http://deb.debian.org/debian stretch-backports/non-free amd64 firmware-linux all 20180825+dfsg-1~bpo9+1 [17.1 kB]
Get:3 http://deb.debian.org/debian stretch-backports/non-free amd64 firmware-linux-nonfree all 20180825+dfsg-1~bpo9+1 [16.8 kB]
Get:4 http://deb.debian.org/debian stretch-backports/non-free amd64 firmware-misc-nonfree all 20180825+dfsg-1~bpo9+1 [3,059 kB]
Fetched 5,422 kB in 0s (7,385 kB/s)         
Reading changelogs... Done
(Reading database ... 157629 files and directories currently installed.)
Preparing to unpack .../firmware-amd-graphics_20180825+dfsg-1~bpo9+1_all.deb ...
Unpacking firmware-amd-graphics (20180825+dfsg-1~bpo9+1) over (20161130-4) ...
Preparing to unpack .../firmware-linux_20180825+dfsg-1~bpo9+1_all.deb ...
Unpacking firmware-linux (20180825+dfsg-1~bpo9+1) over (20161130-4) ...
Preparing to unpack .../firmware-linux-nonfree_20180825+dfsg-1~bpo9+1_all.deb ...
Unpacking firmware-linux-nonfree (20180825+dfsg-1~bpo9+1) over (20161130-4) ...
Preparing to unpack .../firmware-misc-nonfree_20180825+dfsg-1~bpo9+1_all.deb ...
Unpacking firmware-misc-nonfree (20180825+dfsg-1~bpo9+1) over (20161130-4) ...
Setting up firmware-amd-graphics (20180825+dfsg-1~bpo9+1) ...
Setting up firmware-misc-nonfree (20180825+dfsg-1~bpo9+1) ...
update-initramfs: deferring update (trigger activated)
Setting up firmware-linux-nonfree (20180825+dfsg-1~bpo9+1) ...
Setting up firmware-linux (20180825+dfsg-1~bpo9+1) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-0.bpo.1-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168h-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169
# reboot

Thanks to you both for tackling this problem.

Now just one more question: When I installed Debian on my external drive, I had the installer on a thumbdrive. I put the iwlwifi package in the /firmware folder of the installer, and I was able to install it and have working wifi. If I were to reinstall Debian on my machine, what packages should I include in that /firmware folder to prevent this screen problem, and should I use a different version of Debian besides stable?
John Guy
 
Posts: 9
Joined: 2018-11-24 15:56

Next

Return to System configuration

Who is online

Users browsing this forum: peter_irich and 5 guests

fashionable