You are not logged in.
The r8168 package in the repositories is for the linux package in the repositories only not linux-ck. repo-ck does not provide a r8168-ck package.
Why would mkinitcpio result in loading the r8168 module for linux and but not linux-ck-k10?
BTW: This morning (2017-12-06) it again failed to load r8168 for upgrading linux-ck-k10 (4.14.3-1 -> 4.14.4-1).
When linux-ck-k10 (4.14.2-2 -> 4.14.3-1) on 2017-12-01 r8168 was loaded.
Then on 2017-12-03 r8168 was upgraded (8.045.08-5 -> 8.045.08-10) and there was a mkinitcpio run for linux, but there was for not one for linux-ck-k10, and the internet connection was lost.
Subsequently I ran mkinitcpio run for linux-ck-k10 4.14.4-1. and r8168 was not loaded.
Now we have today's (2017-12-06) run for upgrading linux-ck-k10 (4.14.3-1 -> 4.14.4-1) and r8168 module again not loaded.
I would like to understand what is going on, please.
From journalctl for linux boot:
[root@KISE-066 ~]# journalctl -b | grep r8168
Dec 06 08:26:56 KISE-066 kernel: r8168: loading out-of-tree module taints kernel.
Dec 06 08:26:56 KISE-066 kernel: r8168 Gigabit Ethernet driver 8.045.08-NAPI loaded
Dec 06 08:26:56 KISE-066 kernel: r8168 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
Dec 06 08:26:56 KISE-066 kernel: r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
Dec 06 08:26:56 KISE-066 kernel: r8168 Copyright (C) 2017 Realtek NIC software team <nicfae@realtek.com>
Dec 06 08:26:56 KISE-066 kernel: r8168 0000:03:00.0 enp3s0: renamed from eth0
Dec 06 08:26:58 KISE-066 kernel: r8168: enp3s0: link up
[root@KISE-066 ~]#
From journalctl for linux-ck-k10 boot:
[root@KISE-066 ~]# journalctl -b -1 | grep r8168
[root@KISE-066 ~]#
[root@KISE-066 ~]# journalctl -b -1 | grep 8168
Dec 06 08:26:01 KISE-066 kernel: pci 0000:03:00.0: [10ec:8168] type 00 class 0x020000
[root@KISE-066 ~]#
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
loqs wrote:The r8168 package in the repositories is for the linux package in the repositories only not linux-ck. repo-ck does not provide a r8168-ck package.
Why would mkinitcpio result in loading the r8168 module for linux and but not linux-ck-k10?
Modules are kernel specific an mkinitcpio building a kernel for the for linux package would only find modules for the linux kernel not linux-ck
Even if mkinitcpio included the module it would not be loaded.
modprobe -v foobar
modprobe: FATAL: Module foobar not found in directory /lib/modules/4.14.4-1-ARCH
It does not search /lib/modules/4.14.4-1-ck. There is a symlink from /lib/modules/4.14.4-1-ARCH to extramodules-4.14-ARCH which is where the package r8168 places its kernel module.
Even if modprobe did attempt to load the module r8168 built for linux into linux-ck it would detect the "version magic" is not the same and refuse to load it.
Offline
Modules are kernel specific an mkinitcpio building a kernel for the for linux package would only find modules for the linux kernel not linux-ck
Even if mkinitcpio included the module it would not be loaded.modprobe -v foobar modprobe: FATAL: Module foobar not found in directory /lib/modules/4.14.4-1-ARCH
It does not search /lib/modules/4.14.4-1-ck. There is a symlink from /lib/modules/4.14.4-1-ARCH to extramodules-4.14-ARCH which is where the package r8168 places its kernel module.
Even if modprobe did attempt to load the module r8168 built for linux into linux-ck it would detect the "version magic" is not the same and refuse to load it.
Got it & thanks... .. .
/lib/modules/extramodules-4.14-ck-k10/ does not contain a 'r8168.ko.gz' linked from /lib/modules/4.14.4-1-ck-k10,
and /lib/modules/4.14.3-1-ARCH/ does.
But why has this mainboard NIC worked for a very long time apparently using the r8168 module with the linux-ck kernel and abruptly stop? ...after r8168 was upgraded (8.045.08-5 -> 8.045.08-10)
[SOLVED] In any case I have removed the blacklist for the r8169 module, and now both linux and linux-ck-k10 kernels boot successfully using r8169.
Hopefully the problems that were occurring in earlier kernels and r8169 module with the Realtek NICs will now not occur.
loqs: thanks for your patience and assistance.
Last edited by keepitsimpleengineer (2017-12-06 21:18:35)
Al Einstein: "Man soll die Dinge so einfach machen wie möglich ~ aber nicht einfacher." (Things should be as simple as possible ~ but not too simple.) ~ Al (Einstein) war ein Cousin von Albert, "Al" ist die Abkürzung für Aloysius
Offline
Have a look in the journal from those older boots under linux-ck and check if the module r8168 was loaded.
Offline
Is anyone experiencing a network hang when using this kernel? With linux-ck-core2 and an Nvidia MCP51 ethernet controller the cabled network works fine just after boot, then after some minutes it hangs. I cannot connect to web sites nor to local network machines like my router. Restarting the network service does not help, only a reboot fixes the problem but just for some minutes. Other devices connected to the same router (e.g. android phones) do not experience any problem. The issue is not present with the stock arch kernel. Any hint or suggestion? Thanks.
Offline
i had this very same r8169 problem to make matters worse i have a gigabyte mobo i have to run amd_iommu=on iommu=pt for my usb3.0 to work and for my network to work without crashing as well. i seem to remember there being 2 versions of r8169 or perhaps it was r8168 when i first encountered this several years ago, anyway they both had same name but one crashed every 20 minutes
to above poster: do you have a gigabyte motherboard? mine is ga-970a-d3p, you may need the iommu solution
Last edited by pr0dukter (2017-12-11 04:20:18)
Offline
the linux-ck-bulldozer modesetting flag to enalbe hdmi audio amdgpu.dc=1 gives me the following error:
amdgpu: unknown parameter 'dc' ignored
this should work with the DC/DAL merge, no?
Offline
@pr0dukter: I have an Asus P5N-E SLI motherboard, not a Gigabyte. I'll try the iommu workaround as soon as I can (the pc is my parent's one, not mine), thanks for the hint.
Offline
@snack what network driver is being used under linux-ck and what driver under linux?
Offline
@snack what network driver is being used under linux-ck and what driver under linux?
I don't know. I suppose both kernels use the same in-tree driver since I installed no out-of-tree driver. How can I check it? I won't have access to the machine for the next 10 days or so, so I will check as soon as I can.
Offline
Getting:
error: linux-ck-ivybridge: missing required signature
error: linux-ck-ivybridge-headers: missing required signature
error: failed to commit transaction (invalid or corrupted package)
Tried to import graysky keys again but it didn't help.
Offline
@Tharbad - Sorry about that... fixed now.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Online
Running into the same issue with linux-ck-sandybridge (though ck-haswell and ck-broadwell updated fine earlier today):
linux-ck-sandybridge-4.14.6-2-x86_64 59.8 MiB 4.16M/s 00:14 [##################################################################################] 88%
linux-ck-sandybridge-headers-4.14.6-2-x86_64 67.6 MiB 4.16M/s 00:16 [##################################################################################] 100%
(10/10) checking keys in keyring [##################################################################################] 100%
(10/10) checking package integrity [##################################################################################] 100%
error: linux-ck-sandybridge: missing required signature
error: linux-ck-sandybridge-headers: missing required signature
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
4X Intel(R) Xeon(R) CPU E7-8870 @ 2.40GHz; 256GiB; 11TB EXT4; SL6.8
2X Intel(R) Xeon(R) CPU E5-2680 @ 2.70GHz; 256GiB; 3.4TB EXT4; SL6.8
Thinkpad X250; Broadwell-ULT Core i5; 8GiB, 525GB Crucial_CT525MX3; Arch
Thinkpad T440S; Haswell-ULT Core i7; 12GiB, 512GB SanDisk X210; Arch
Offline
(2/2) checking keys in keyring [---------------------------------------------] 100%
(2/2) checking package integrity [---------------------------------------------] 100%
error: linux-ck-skylake: missing required signature
error: linux-ck-skylake-headers: missing required signature
error: failed to commit transaction (package missing required signature)
Errors occurred, no packages were upgraded.
Same issue here, still persist.
Offline
...
:: Proceed with installation? [Y/n]
(12/12) checking keys in keyring [######################] 100%
(12/12) checking package integrity [######################] 100%
error: linux-ck-skylake: missing required signature
error: linux-ck-skylake-headers: missing required signature
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
Same problem.
Offline
Please try now.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Online
Please try now.
It works now. Thanks.
Offline
Please try now.
It's already fixed, thanks.
Offline
Issue fixed
Offline
The last I saw of this was back in 2012, but it just occured to me that it might be worth asking again. https://bbs.archlinux.org/viewtopic.php … 3#p1097443
Is there a chance that delta updates could be used for Repo-ck in the future?
ArchLinux | x86_64 | linux-ck-ivybridge
ThinkPad X230 | 12.5" | i5-3320M (2.5GHz) | HD 4000 | 16GB (1600MHz) | 256GB mSATA SSD | 2TB HDD
ThinkPad T430 | 14.1" | i7-3520M (2.9GHz) | GF108M (NVS 5400M) | 16GB (1600MHz) | 256GB mSATA SSD | 1TB HDD | 500GB HDD
Offline
Looks like there's a pkgver mismatch for nvidia-340xx-ck packages on AUR (340.104.4.10) and repo-ck (340.104.9), causing pacman to throw a warning when one builds from AUR. Just a FYI.
Offline
@glitsj16 - Fixed thanks for the report.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Online
are the amd dc merges not going to be used in linux-ck until 4.15?
Offline
Does ck has the faulty kernel option that cause ubuntu 17.10 to be pulled back from the mirrors?
(Something about an intel driver in kernel 4.13 that allows the kernel to write to the BIOS/UEFI memory space)
Offline
Does ck has the faulty kernel option that cause ubuntu 17.10 to be pulled back from the mirrors?
(Something about an intel driver in kernel 4.13 that allows the kernel to write to the BIOS/UEFI memory space)
Did you research https://bugs.launchpad.net/ubuntu/+sour … ug/1734147 / https://cateee.net/lkddb/web-lkddb/SPI_ … TFORM.html?
@pr0dukter you want CK to release a 4.14 linux-ck+the AMD DC changeset backported to 4.14? You can test the 4.15-rc's for bugs that would help for when 4.15 is released.
Offline