problem getting ports from crux.nu
Hello, I am installing CRUX 3.5 on a new computer. I started with the ISO on a USB stick, and installed onto a SSD drive. The grub2 installation didn't work for some reason, but I managed to boot Linux on the SSD drive using the grub command line. Now I am trying to bring my ports structure up to date. When I type "ports -u", it says "Updating file list from crux.nu::ports/crux-3.5/core/", and hangs there for several minutes. It fails with the following messages: rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110)rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]Error: Running rsync failed ()Updating failed It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue. Any help would be appreciated. Thank you, Dave
what do you get when you run: mount On Tue, Jun 30, 2020 at 9:22 PM david mccooey <dmccooey@att.net> wrote:
Hello,
I am installing CRUX 3.5 on a new computer.
I started with the ISO on a USB stick, and installed onto a SSD drive.
The grub2 installation didn't work for some reason, but I managed to boot Linux on the SSD drive using the grub command line.
Now I am trying to bring my ports structure up to date.
When I type "ports -u", it says "Updating file list from crux.nu::ports/crux-3.5/core/", and hangs there for several minutes.
It fails with the following messages:
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote: On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote: Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote: On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
What's the output of 'lsmod | grep iw'? On 20/07/03 06:04PM, david mccooey wrote:
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote:
Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote:
On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Just to be sure: did do `make modules_install' after `make all' when compiling the kernel? On 20/07/04 09:08PM, Hans Bezemer wrote:
What's the output of 'lsmod | grep iw'?
On 20/07/03 06:04PM, david mccooey wrote:
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote:
Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote:
On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Yes On Saturday, July 4, 2020, 02:22:04 PM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote: Just to be sure: did do `make modules_install' after `make all' when compiling the kernel? On 20/07/04 09:08PM, Hans Bezemer wrote:
What's the output of 'lsmod | grep iw'?
On 20/07/03 06:04PM, david mccooey wrote:
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote: Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote: On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Hi David. Are you sure you have all the necessary firmware drivers? Intel: https://www.intel.com/content/www/us/en/support/articles/000005511/network-a... https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi E.g. interface connector - M.2; PCIE; USB Is the kernel modular or monolithic? Regards Milan so 4. 7. 2020 v 22:23 odesílatel david mccooey <dmccooey@att.net> napsal:
Yes
On Saturday, July 4, 2020, 02:22:04 PM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote:
Just to be sure: did do `make modules_install' after `make all' when compiling the kernel?
On 20/07/04 09:08PM, Hans Bezemer wrote:
What's the output of 'lsmod | grep iw'?
On 20/07/03 06:04PM, david mccooey wrote:
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote:
Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote:
On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Remember, no question is too stupid and no problem too small -- We've all been beginners
Hi Milan, I have the following file on my system: /lib/firmware/iwlwifi-cc-a0-46.ucode I verified this is the same file (contents and name) as the file contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site. I noticed Intel's site says this driver is for kernels 5.1+. I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem. Do you know if others have gotten this driver to work? If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup? The M.2 PCIE driver is installed, because that's where my root file system is. Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to match /usr/src/linux-4.19.48/.config. Also attached are the outputs from "lsmod" and "lspci -v". Before I can answer the question about monolithic or modular kernel, I need to know the terminology: Is a kernel monolithic until the first module is installed? Or does the distinction have something to do with how the kernel is originally built? Best regards,Dave On Sunday, July 5, 2020, 01:07:28 PM CDT, Milan Buška <milan.buska@gmail.com> wrote: Hi David. Are you sure you have all the necessary firmware drivers? Intel: https://www.intel.com/content/www/us/en/support/articles/000005511/network-a... https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi E.g. interface connector - M.2; PCIE; USB Is the kernel modular or monolithic? Regards Milan so 4. 7. 2020 v 22:23 odesílatel david mccooey <dmccooey@att.net> napsal:
Yes
On Saturday, July 4, 2020, 02:22:04 PM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote:
Just to be sure: did do `make modules_install' after `make all' when compiling the kernel?
On 20/07/04 09:08PM, Hans Bezemer wrote:
What's the output of 'lsmod | grep iw'?
On 20/07/03 06:04PM, david mccooey wrote:
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote:
Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote:
On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
-- Remember, no question is too stupid and no problem too small -- We've all been beginners
On Sun, 2020-07-05 at 21:54 +0000, david mccooey wrote:
I noticed Intel's site says this driver is for kernels 5.1+. I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem. Do you know if others have gotten this driver to work? If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
Installing a newer kernel shouldn't cause issues with CRUX. I've personally run the latest longterm release (5.4.x) on my CRUX system for a long time, and I haven't run into any issues (no guarantees that you won't run into bugs with 5.4.x tho). -- Joacim Olsen Tangen <hi@joac.im>
ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version. After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages Excuse me. I do not speak English well. Best regards -- Remember, no question is too stupid and no problem too small -- We've all been beginners
po 6. 7. 2020 v 7:42 odesílatel Milan Buška <milan.buska@gmail.com> napsal:
ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version.
After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages
Excuse me. I do not speak English well.
Good starting point. https://crux.ninja/updated-iso/crux-3.5-updated.iso -- Remember, no question is too stupid and no problem too small -- We've all been beginners
Hi Milan, I moved the computer to a new location to get around the firewall. I was able to get all packages from core, opt, xorg, contrib, and compat-32. The WiFi is not a roadblock now, but I would like to get it working eventually. I see a package called "iw" under contrib, which may be helpful. Regarding a ramdisk, I am not using one. I ran modinfo on iwlwifi, iwldvm, and iwlmvm. It shows information about each one, with no errors or warnings. In the output for iwlwifi, there are 31 lines starting with "firmware:", all with the following format: firmware: iwlwifi-*.ucode where '*' is some identifier, like "100-5" or "600g2b-6". The file for my particular device (iwlwifi-cc-a0-46.ucode) is not in this output. This may be due to my kernel 4.19.48 < 5.1. After I install iwlfifi, the following two lines are added to dmesg's output: [ 78.703559] Intel(R) Wireless WiFi driver for Linux[ 78.703560] Copyright(c) 2003- 2015 Intel Corporation I think I need to update my kernel to 5.1+ to get this driver working, but it seems odd that the 4.19.48 kernel gives no errors or warnings about it. Thank you for your suggestions. Best regards,Dave On Monday, July 6, 2020, 12:43:24 AM CDT, Milan Buška <milan.buska@gmail.com> wrote: ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version. After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages Excuse me. I do not speak English well. Best regards -- Remember, no question is too stupid and no problem too small -- We've all been beginners
út 7. 7. 2020 v 5:34 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I moved the computer to a new location to get around the firewall.
I was able to get all packages from core, opt, xorg, contrib, and compat-32.
The WiFi is not a roadblock now, but I would like to get it working eventually.
I see a package called "iw" under contrib, which may be helpful.
Regarding a ramdisk, I am not using one.
I ran modinfo on iwlwifi, iwldvm, and iwlmvm.
It shows information about each one, with no errors or warnings.
In the output for iwlwifi, there are 31 lines starting with "firmware:", all with the following format:
firmware: iwlwifi-*.ucode
where '*' is some identifier, like "100-5" or "600g2b-6".
The file for my particular device (iwlwifi-cc-a0-46.ucode) is not in this output.
This may be due to my kernel 4.19.48 < 5.1.
After I install iwlfifi, the following two lines are added to dmesg's output:
[ 78.703559] Intel(R) Wireless WiFi driver for Linux [ 78.703560] Copyright(c) 2003- 2015 Intel Corporation
I think I need to update my kernel to 5.1+ to get this driver working, but it
after updating the kernel, be sure to update the linux-firmware package
seems odd that the 4.19.48 kernel gives no errors or warnings about it.
I don't know the answer to that (this is already a question for kernel developers ???)
Thank you for your suggestions.
Best regards, Dave
On Monday, July 6, 2020, 12:43:24 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version.
After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages
Excuse me. I do not speak English well.
Best regards -- Remember, no question is too stupid and no problem too small -- We've all been beginners
Hi Milan, I upgraded my installation using the updated-iso image. This gives me the 5.4.49 kernel, and I updated the linux-firmware package as you suggested, although it appeared to be up-to-date already (20200619-1). Using the 5.4 kernel solves my WiFi driver problem, but now I have a new problem: The Nvidia video driver has compilation problems with the 5.4 kernel. The following error message occurs 308 times while running the Nvidia installer: "NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef] This same installer worked ok with the 4.19.48 kernel. Other people have encountered this same error with kernel 5.4, but nobody has posted a solution. The gcc compiler changed from 8.3.0 to 8.4.0 with this upgrade, so maybe that's the cause. In any event, my plan is to start by trying an older kernel, like 5.3. Are there any published instructions on how to do this? Maybe there is a previous updated-iso image with the 5.3 kernel? Best regards, Dave On Tuesday, July 7, 2020, 02:42:13 AM CDT, Milan Buška <milan.buska@gmail.com> wrote: út 7. 7. 2020 v 5:34 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I moved the computer to a new location to get around the firewall.
I was able to get all packages from core, opt, xorg, contrib, and compat-32.
The WiFi is not a roadblock now, but I would like to get it working eventually.
I see a package called "iw" under contrib, which may be helpful.
Regarding a ramdisk, I am not using one.
I ran modinfo on iwlwifi, iwldvm, and iwlmvm.
It shows information about each one, with no errors or warnings.
In the output for iwlwifi, there are 31 lines starting with "firmware:", all with the following format:
firmware: iwlwifi-*.ucode
where '*' is some identifier, like "100-5" or "600g2b-6".
The file for my particular device (iwlwifi-cc-a0-46.ucode) is not in this output.
This may be due to my kernel 4.19.48 < 5.1.
After I install iwlfifi, the following two lines are added to dmesg's output:
[ 78.703559] Intel(R) Wireless WiFi driver for Linux [ 78.703560] Copyright(c) 2003- 2015 Intel Corporation
I think I need to update my kernel to 5.1+ to get this driver working, but it
after updating the kernel, be sure to update the linux-firmware package
seems odd that the 4.19.48 kernel gives no errors or warnings about it.
I don't know the answer to that (this is already a question for kernel developers ???)
Thank you for your suggestions.
Best regards, Dave
On Monday, July 6, 2020, 12:43:24 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version.
After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages
Excuse me. I do not speak English well.
Best regards -- Remember, no question is too stupid and no problem too small -- We've all been beginners
ne 12. 7. 2020 v 23:59 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I upgraded my installation using the updated-iso image.
This gives me the 5.4.49 kernel, and I updated the linux-firmware package
as you suggested, although it appeared to be up-to-date already (20200619-1).
Using the 5.4 kernel solves my WiFi driver problem, but now I have a new problem:
The Nvidia video driver has compilation problems with the 5.4 kernel.
The following error message occurs 308 times while running the Nvidia installer:
"NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef]
I don't know much about the Nvidia driver, but you may need to reinstall the glibc package. It is probably compiled with 4.19 kernel header files ... E.g. Pkgfile glibc # Description: The C library used in the GNU system # URL: http://www.gnu.org/software/libc/ # Maintainer: CRUX System Team, core-ports at crux dot nu name = glibc version = 2.28 release = 2 source = (http://ftp.gnu.org/gnu/glibc/glibc-$version.tar.xz \ http://www.kernel.org/pub/linux/kernel/v5.x/linux-5.4.49.tar.xz \ glibc-2.28-1.patch \ hosts resolv.conf nsswitch.conf host.conf ld.so.conf) build () { # install kernel headers cd linux-5.4.49 ......... .........
This same installer worked ok with the 4.19.48 kernel
.Because glibc is compiled with kernel 4.19 ... Nvidia shouts that the kernel is 5.4 but the kernel headers are from the kernel 4.19
Other people have encountered this same error with kernel 5.4, but nobody has posted a solution.
The gcc compiler changed from 8.3.0 to 8.4.0 with this upgrade, so maybe that's the cause.
In any event, my plan is to start by trying an older kernel, like 5.3.
Are there any published instructions on how to do this?
Maybe there is a previous updated-iso image with the 5.3 kernel?
Best regards,
Dave
On Tuesday, July 7, 2020, 02:42:13 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
út 7. 7. 2020 v 5:34 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I moved the computer to a new location to get around the firewall.
I was able to get all packages from core, opt, xorg, contrib, and compat-32.
The WiFi is not a roadblock now, but I would like to get it working eventually.
I see a package called "iw" under contrib, which may be helpful.
Regarding a ramdisk, I am not using one.
I ran modinfo on iwlwifi, iwldvm, and iwlmvm.
It shows information about each one, with no errors or warnings.
In the output for iwlwifi, there are 31 lines starting with "firmware:", all with the following format:
firmware: iwlwifi-*.ucode
where '*' is some identifier, like "100-5" or "600g2b-6".
The file for my particular device (iwlwifi-cc-a0-46.ucode) is not in this output.
This may be due to my kernel 4.19.48 < 5.1.
After I install iwlfifi, the following two lines are added to dmesg's output:
[ 78.703559] Intel(R) Wireless WiFi driver for Linux [ 78.703560] Copyright(c) 2003- 2015 Intel Corporation
I think I need to update my kernel to 5.1+ to get this driver working, but it
after updating the kernel, be sure to update the linux-firmware package
seems odd that the 4.19.48 kernel gives no errors or warnings about it.
I don't know the answer to that (this is already a question for kernel developers ???)
Thank you for your suggestions.
Best regards, Dave
On Monday, July 6, 2020, 12:43:24 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version.
After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages
Excuse me. I do not speak English well.
Best regards
--
Remember, no question is too stupid and no problem too small -- We've all been beginners
-- Remember, no question is too stupid and no problem too small -- We've all been beginners
Hi Milan, I did the following: # pkginfo -i | grep glibc glibc 2.28-2 glibc-32 2.28-2 # cd /usr/ports/core/glibc # pkgmk -d -u This took several minutes. One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz. This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files. How do I make it use the 5.4.49 kernel header files? The version "4.29.24" comes from the "source" line in the Pkginfo file. Should I edit that line? Best regards, Dave On Monday, July 13, 2020, 12:25:36 AM CDT, Milan Buška <milan.buska@gmail.com> wrote: ne 12. 7. 2020 v 23:59 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I upgraded my installation using the updated-iso image.
This gives me the 5.4.49 kernel, and I updated the linux-firmware package
as you suggested, although it appeared to be up-to-date already (20200619-1).
Using the 5.4 kernel solves my WiFi driver problem, but now I have a new problem:
The Nvidia video driver has compilation problems with the 5.4 kernel.
The following error message occurs 308 times while running the Nvidia installer:
"NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef]
I don't know much about the Nvidia driver, but you may need to reinstall the glibc package. It is probably compiled with 4.19 kernel header files ... E.g. Pkgfile glibc # Description: The C library used in the GNU system # URL: http://www.gnu.org/software/libc/ # Maintainer: CRUX System Team, core-ports at crux dot nu name = glibc version = 2.28 release = 2 source = (http://ftp.gnu.org/gnu/glibc/glibc-$version.tar.xz \ http://www.kernel.org/pub/linux/kernel/v5.x/linux-5.4.49.tar.xz \ glibc-2.28-1.patch \ hosts resolv.conf nsswitch.conf host.conf ld.so.conf) build () { # install kernel headers cd linux-5.4.49 ......... .........
This same installer worked ok with the 4.19.48 kernel
.Because glibc is compiled with kernel 4.19 ... Nvidia shouts that the kernel is 5.4 but the kernel headers are from the kernel 4.19
Other people have encountered this same error with kernel 5.4, but nobody has posted a solution.
The gcc compiler changed from 8.3.0 to 8.4.0 with this upgrade, so maybe that's the cause.
In any event, my plan is to start by trying an older kernel, like 5.3.
Are there any published instructions on how to do this?
Maybe there is a previous updated-iso image with the 5.3 kernel?
Best regards,
Dave
On Tuesday, July 7, 2020, 02:42:13 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
út 7. 7. 2020 v 5:34 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I moved the computer to a new location to get around the firewall.
I was able to get all packages from core, opt, xorg, contrib, and compat-32.
The WiFi is not a roadblock now, but I would like to get it working eventually.
I see a package called "iw" under contrib, which may be helpful.
Regarding a ramdisk, I am not using one.
I ran modinfo on iwlwifi, iwldvm, and iwlmvm.
It shows information about each one, with no errors or warnings.
In the output for iwlwifi, there are 31 lines starting with "firmware:", all with the following format:
firmware: iwlwifi-*.ucode
where '*' is some identifier, like "100-5" or "600g2b-6".
The file for my particular device (iwlwifi-cc-a0-46.ucode) is not in this output.
This may be due to my kernel 4.19.48 < 5.1.
After I install iwlfifi, the following two lines are added to dmesg's output:
[ 78.703559] Intel(R) Wireless WiFi driver for Linux [ 78.703560] Copyright(c) 2003- 2015 Intel Corporation
I think I need to update my kernel to 5.1+ to get this driver working, but it
after updating the kernel, be sure to update the linux-firmware package
seems odd that the 4.19.48 kernel gives no errors or warnings about it.
I don't know the answer to that (this is already a question for kernel developers ???)
Thank you for your suggestions.
Best regards, Dave
On Monday, July 6, 2020, 12:43:24 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
ne 5. 7. 2020 v 23:55 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
I have the following file on my system:
/lib/firmware/iwlwifi-cc-a0-46.ucode
I verified this is the same file (contents and name) as the file
contained within the tar file "iwlwifi-cc-46.3cfab8da.0.tgz" on Intel's site.
I noticed Intel's site says this driver is for kernels 5.1+.
I am using the default CRUX kernel, 4.19.48, so this looks like the cause of the problem.
Do you know if others have gotten this driver to work?
If I installed a 5.1+ kernel, would it cause other incompatibilities in my CRUX setup?
The M.2 PCIE driver is installed, because that's where my root file system is.
Attached is the kernel's config file (extracted from /proc/config.gz) and confirmed to
match /usr/src/linux-4.19.48/.config.
Also attached are the outputs from "lsmod" and "lspci -v".
Before I can answer the question about monolithic or modular kernel,
I am sorry. Wrong wording of the question. I was wondering if you're using a ramdisk (initramfs ...., initrd ....)
I need to know the terminology:
Is a kernel monolithic until the first module is installed?
Or does the distinction have something to do with how the kernel is originally built?
The modinfo command also says a lot about modules which you need and what firmware version.
After loading the modules, check the dmesg output. This also sometimes shows a lot of error and warning messages
Excuse me. I do not speak English well.
Best regards
--
Remember, no question is too stupid and no problem too small -- We've all been beginners
-- Remember, no question is too stupid and no problem too small -- We've all been beginners
On 2020-07-13 21:06, david mccooey wrote:
One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz.
This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files.
How do I make it use the 5.4.49 kernel header files?
The version "4.29.24" comes from the "source" line in the Pkginfo file.
Should I edit that line?
Dave, You should not do this. You should leave the glibc package alone unless you REALLY want to recompile everything on your system. The kernel headers against which glibc is compiled do NOT need to match your running kernel at all. If you DO change glibc, though, you should recompile everything else installed to match, otherwise you're inviting instability. I would not recommend this level of effort at all. The only real link between your kernel and glibc in this case is the line which reads '--enable-kernel=4.9'. This configures glibc to be able to work with a 4.9 *or higher* version kernel. You do not need to change this or update the headers in the glibc port to use a newer kernel. Regards, Matt
Hi Matt, Dave út 14. 7. 2020 v 8:18 odesílatel Matt Housh <jaeger@crux.ninja> napsal:
On 2020-07-13 21:06, david mccooey wrote:
One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz.
This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files.
How do I make it use the 5.4.49 kernel header files?
The version "4.29.24" comes from the "source" line in the Pkginfo file.
Should I edit that line?
Dave,
You should not do this. You should leave the glibc package alone unless you REALLY want to recompile everything on your system. The kernel headers against which glibc is compiled do NOT need to match your running kernel at all. If you DO change glibc, though, you should recompile everything else installed to match, otherwise you're inviting instability. I would not recommend this level of effort at all.
The only real link between your kernel and glibc in this case is the line which reads '--enable-kernel=4.9'. This configures glibc to be able to work with a 4.9 *or higher* version kernel. You do not need to change this or update the headers in the glibc port to use a newer kernel.
Regards, Matt _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I apologize for what I wrote. By no means did I want to confuse anyone. Milan -- Remember, no question is too stupid and no problem too small -- We've all been beginners
Hi Milan, It's no problem. All is good. I'm making progress. Best regards, Dave On Tuesday, July 14, 2020, 01:49:14 AM CDT, Milan Buška <milan.buska@gmail.com> wrote: Hi Matt, Dave út 14. 7. 2020 v 8:18 odesílatel Matt Housh <jaeger@crux.ninja> napsal:
On 2020-07-13 21:06, david mccooey wrote:
One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz.
This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files.
How do I make it use the 5.4.49 kernel header files?
The version "4.29.24" comes from the "source" line in the Pkginfo file.
Should I edit that line?
Dave,
You should not do this. You should leave the glibc package alone unless you REALLY want to recompile everything on your system. The kernel headers against which glibc is compiled do NOT need to match your running kernel at all. If you DO change glibc, though, you should recompile everything else installed to match, otherwise you're inviting instability. I would not recommend this level of effort at all.
The only real link between your kernel and glibc in this case is the line which reads '--enable-kernel=4.9'. This configures glibc to be able to work with a 4.9 *or higher* version kernel. You do not need to change this or update the headers in the glibc port to use a newer kernel.
Regards, Matt _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I apologize for what I wrote. By no means did I want to confuse anyone. Milan -- Remember, no question is too stupid and no problem too small -- We've all been beginners _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
st 15. 7. 2020 v 8:36 odesílatel david mccooey <dmccooey@att.net> napsal:
Hi Milan,
It's no problem.
All is good. I'm making progress.
Best regards,
Dave
On Tuesday, July 14, 2020, 01:49:14 AM CDT, Milan Buška <milan.buska@gmail.com> wrote:
Hi Matt, Dave
út 14. 7. 2020 v 8:18 odesílatel Matt Housh <jaeger@crux.ninja> napsal:
On 2020-07-13 21:06, david mccooey wrote:
One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz.
This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files.
How do I make it use the 5.4.49 kernel header files?
The version "4.29.24" comes from the "source" line in the Pkginfo file.
Should I edit that line?
Dave,
You should not do this. You should leave the glibc package alone unless you REALLY want to recompile everything on your system. The kernel headers against which glibc is compiled do NOT need to match your running kernel at all. If you DO change glibc, though, you should recompile everything else installed to match, otherwise you're inviting instability. I would not recommend this level of effort at all.
The only real link between your kernel and glibc in this case is the line which reads '--enable-kernel=4.9'. This configures glibc to be able to work with a 4.9 *or higher* version kernel. You do not need to change this or update the headers in the glibc port to use a newer kernel.
Regards, Matt _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I apologize for what I wrote. By no means did I want to confuse anyone.
That's great. Enjoy Crux Linux -- Remember, no question is too stupid and no problem too small -- We've all been beginners
Hi Matt, I started from scratch (mkfs.ext4 on my file systems) and installed using the updated-iso, which gives me the 5.4.49 kernel. I named the kernel /boot/vmlinuz-5.4.49, and grub works now. Thanks for the help with that. To install the nvidia driver, I did the following: # cd /usr/ports/opt/nvidia # pkgmk -d -i It succeeded, and I am able to start X, but the display resolution is like it was last time, probably 1024x768. When I used Nvidia's installer on the 4.19.48 kernel, maybe it ran nvidia-xconfig or nvidia-settings, which set the display resolution. Best regards, Dave On Tuesday, July 14, 2020, 01:18:54 AM CDT, Matt Housh <jaeger@crux.ninja> wrote: On 2020-07-13 21:06, david mccooey wrote:
One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz.
This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files.
How do I make it use the 5.4.49 kernel header files?
The version "4.29.24" comes from the "source" line in the Pkginfo file.
Should I edit that line?
Dave, You should not do this. You should leave the glibc package alone unless you REALLY want to recompile everything on your system. The kernel headers against which glibc is compiled do NOT need to match your running kernel at all. If you DO change glibc, though, you should recompile everything else installed to match, otherwise you're inviting instability. I would not recommend this level of effort at all. The only real link between your kernel and glibc in this case is the line which reads '--enable-kernel=4.9'. This configures glibc to be able to work with a 4.9 *or higher* version kernel. You do not need to change this or update the headers in the glibc port to use a newer kernel. Regards, Matt _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I solved the problem with setting the display resolution in X. Thanks for the help Matt. Everything is working well now, except I noticed a problem in grub: When the grub menu comes up during boot, the keyboard is unresponsive. I am using an Acer model KU-0833 USB keyboard. It's very cheap and I imagine very common. I noticed previously, when grub would always go to command mode, that grub was probably reading the keyboard in polled mode, because the characters echoed on the screen would often get out of sync with the keys being typed. My remedy was to unplug/replug the keyboard before typing the very first character. If grub command mode is indeed reading the keyboard in polled mode, maybe the grub menu reads it that way too. However, I would expect at least some response after hitting lots of keys, like up-arrow, down-arrow, and 'c' multiple times. This problem happens when booting from power-off, or when rebooting (shutdown -r). My computer has USB 3.2 Gen 1 and USB 3.2 Gen 2 ports. The problem happens with either type of port. Any suggestions would be appreciated. Best regards, Dave On Wednesday, July 15, 2020, 01:00:35 AM CDT, david mccooey <dmccooey@att.net> wrote: Hi Matt, I started from scratch (mkfs.ext4 on my file systems) and installed using the updated-iso, which gives me the 5.4.49 kernel. I named the kernel /boot/vmlinuz-5.4.49, and grub works now. Thanks for the help with that. To install the nvidia driver, I did the following: # cd /usr/ports/opt/nvidia # pkgmk -d -i It succeeded, and I am able to start X, but the display resolution is like it was last time, probably 1024x768. When I used Nvidia's installer on the 4.19.48 kernel, maybe it ran nvidia-xconfig or nvidia-settings, which set the display resolution. Best regards, Dave On Tuesday, July 14, 2020, 01:18:54 AM CDT, Matt Housh <jaeger@crux.ninja> wrote: On 2020-07-13 21:06, david mccooey wrote:
One of the files downloaded was /usr/ports/core/glibc/linux-4.19.24.tar.gz.
This "pkgmk" appears to have compiled glibc with the 4.19.24 kernel header files.
How do I make it use the 5.4.49 kernel header files?
The version "4.29.24" comes from the "source" line in the Pkginfo file.
Should I edit that line?
Dave, You should not do this. You should leave the glibc package alone unless you REALLY want to recompile everything on your system. The kernel headers against which glibc is compiled do NOT need to match your running kernel at all. If you DO change glibc, though, you should recompile everything else installed to match, otherwise you're inviting instability. I would not recommend this level of effort at all. The only real link between your kernel and glibc in this case is the line which reads '--enable-kernel=4.9'. This configures glibc to be able to work with a 4.9 *or higher* version kernel. You do not need to change this or update the headers in the glibc port to use a newer kernel. Regards, Matt _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Here's the sequence of commands.This time, I used depmod and modprobe, but the results are the same as with insmod. # find /lib -name "*.ko" | grep iw /lib/modules/4.19.48/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko /lib/modules/4.19.48/kernel/drivers/net/wireless/intel/iwlwifi/dvm/iwldvm.ko /lib/modules/4.19.48/kernel/drivers/net/wireless/intel/iwlwifi/mvm/iwlmvm.ko # depmod -a # modprobe iwlwifi # modprobe iwldvm # modprobe iwlmvm # lsmod | grep iw iwlmvm 286720 0 iwldvm 147456 0 iwlwifi 217088 2 iwldvm,iwlmvm led_class 16384 3 iwldvm,input_leds,iwlmvm # lspci -v | grep -i iw <nothing returned> # dmesg | tail -3 [ 9.567663] random: 7 urandom warning(s) missed due to ratelimiting [ 211.991313] Intel(R) Wireless WiFi driver for Linux [ 211.991313] Copyright(c) 2003- 2015 Intel Corporation Best regards,Dave On Saturday, July 4, 2020, 02:08:45 PM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote: What's the output of 'lsmod | grep iw'? On 20/07/03 06:04PM, david mccooey wrote:
I configured the kernel with iwlwifi, iwldvm, and iwlmvm as modules,and installed them using insmod. However, "lspci -v" does not show these lines: Kernel driver in use: iwlwifiKernel modules: iwlwifi It's as if the modules aren't really installed. Based on various online sources, I think I need a utility called "iw" to get thesemodules to be used by the kernel. I have other computers here (MacOS) that can use the WiFi network, butthere is no "prt-get" there, so how would I retrieve the "iw" package?If I can get it on the Mac, then I can load it onto a USB drive, and thenread that USB drive from CRUX. Best regards,Dave On Wednesday, July 1, 2020, 9:53:38 PM CDT, david mccooey <dmccooey@att.net> wrote: Thank you. I am doing this installation on a computer at work, and there is a firewall. The WiFi network does not have a firewall, so I am configuring a kernelwith the appropriate driver -- for the Intel Wi-Fi 6 AX200. Best regards,Dave On Wednesday, July 1, 2020, 02:03:44 AM CDT, Fredrik <fredrik@rinnestam.se> wrote: On 2020-07-01 04:22, david mccooey wrote:
Hello,
rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3] Error: Running rsync failed () Updating failed
It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue.
Yes it is. I'd bet your firewall doesn't allow rsync traffic
Any help would be appreciated.
Thank you,
Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
On 20/07/01 02:22AM, david mccooey wrote:
Hello, I am installing CRUX 3.5 on a new computer. I started with the ISO on a USB stick, and installed onto a SSD drive. The grub2 installation didn't work for some reason, but I managed to boot Linux on the SSD drive using the grub command line. I had the same problem for a uefi boot (assuming that you have a uefi boot also). When using: grub-install --target=x86_64-efi --efi-directory=<path/to/efi/dir> --bootloader-id=GRUB followed by: grub-mkconfig -o /boot/grub/grub.cfg It worked.
Regards, Hans
Now I am trying to bring my ports structure up to date. When I type "ports -u", it says "Updating file list from crux.nu::ports/crux-3.5/core/", and hangs there for several minutes. It fails with the following messages: rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110)rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]Error: Running rsync failed ()Updating failed It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue. Any help would be appreciated. Thank you, Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I originally tried UEFI boot.The grub-install didn't work there either, and I was not able to boot from command mode,so I switched from UEFI/GPT to BIOS/MBR.The grub-install still doesn't work, but at least I am able to boot from command mode. For the grub-install, I wasn't using the --bootloader-id option, so I will give that a try. Best regards,Dave On Wednesday, July 1, 2020, 07:45:13 AM CDT, Hans Bezemer <hbezemer@kliksafe.nl> wrote: On 20/07/01 02:22AM, david mccooey wrote:
Hello, I am installing CRUX 3.5 on a new computer. I started with the ISO on a USB stick, and installed onto a SSD drive. The grub2 installation didn't work for some reason, but I managed to boot Linux on the SSD drive using the grub command line. I had the same problem for a uefi boot (assuming that you have a uefi boot also). When using: grub-install --target=x86_64-efi --efi-directory=<path/to/efi/dir> --bootloader-id=GRUB followed by: grub-mkconfig -o /boot/grub/grub.cfg It worked.
Regards, Hans
Now I am trying to bring my ports structure up to date. When I type "ports -u", it says "Updating file list from crux.nu::ports/crux-3.5/core/", and hangs there for several minutes. It fails with the following messages: rsync: failed to connect to crux.nu (213.132.101.140): Connection timed out (110)rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]Error: Running rsync failed ()Updating failed It then tries to get "opt" and "xorg", but they time out as well with the same messages.
From the bash prompt, I can ping 213.132.101.140 or crux.nu without any problem, so it does not appear to be a network issue. Any help would be appreciated. Thank you, Dave
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
_______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
I'm late to this thread, obviously, but a few things: Regarding the wireless issues, usually all you need for iwlwifi cards is the iwlwifi module and linux-firmware package. If you're missing firmware, you can see what it's looking for with 'dmesg | grep firmw'. The other modules are not necessary to load manually. Regarding grub, usually you only need to do 2 things for a standard install: 1. For UEFI: grub-install /boot/efi (or wherever you mounted your ESP) For MBR: grub-install /dev/sda (or whichever disk you intend to boot) 2. grub-mkconfig -o /boot/grub/grub.cfg Specifying bootloader ids or other things is generally not required. Regarding nvidia, are you using the port 'opt/nvidia' or the upstream installer? I'd recommend using the port as it's already tailored for CRUX. It also seems to work just fine with 5.4.x kernels. At least for my systems with kernel 5.4.44/5.4.49 and nvidia 450.57. Regards, Matt
Hi Matt, Thank you for the input. The iwlfifi driver gets installed with the 5.4.49 kernel: # lspci -v | grep iw Kernel driver in use: iwlfifi Kernel modules: iwlwifi With the 4.19.48 kernel, lspci -v didn't print those two lines. # dmesg | grep firmw [ 4.433796] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 4.761899] iwlwifi 0000:45:00.0: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 4.775457] iwlwifi 0000:45:00.0: Allocated 0x00400000 bytes for firmware monitor. I think the first message with error -2 is not related to iwlwifi. The iwlwifi module is getting loaded automatically. I am not using insmod or modprobe manually (like I was doing with the 4.19.48 kernel). ifconfig shows a "wlo1" interface (which was not shown with the 4.19.48 kernel). This interface does not show an "inet addr", so I have more work to do, but I will figure that out later after I resolve the Nvidia driver problem. For grub, the computer always boots up in grub command mode. This indicates "grub-install" is working, I suppose. The problem appears to be with grub-mkconfig: grub-mkconfig -o /boot/grub/grub.cfg The grub.cfg file is attached. Here's what I type to boot from command mode: grub> set root=(hd0,1) grub> linux /boot/vmlinuz root=/dev/nvme0n1p1 grub> boot The SSD disk is partitioned with MBR: The first partition is the Linux root partition. The second partition is not used currently. The third partition is mounted on /home. For the nvidia driver, I was using the installer from Nvidia's web site. I didn't realize there was a port, so I tried it now: # cd /usr/ports/opt/nvidia # pkgmk -d -u This built everything, but failed in the end because nothing was previously installed. # pkgmk -d -i This failed because some files existed already, and it suggested the -f option. # pkgmk -d -f -i This built everything again, but failed in the end, and suggested the -f option again. # pkgmk -d -f This built everything again, and succeeded. At this point, I can start X, but the screen resolution is wrong. I am using a 4K monitor, but X appears to be using 1024x768. Previously, with the 4.19.48 kernel and Nvidia's installer, the resolution was detected properly. Maybe the fact that I ran Nvidia's installer previously (on the 5.4.49 kernel too) messed things up? Best regards, Dave On Monday, July 13, 2020, 12:15:23 PM CDT, Matt Housh <jaeger@crux.ninja> wrote: I'm late to this thread, obviously, but a few things: Regarding the wireless issues, usually all you need for iwlwifi cards is the iwlwifi module and linux-firmware package. If you're missing firmware, you can see what it's looking for with 'dmesg | grep firmw'. The other modules are not necessary to load manually. Regarding grub, usually you only need to do 2 things for a standard install: 1. For UEFI: grub-install /boot/efi (or wherever you mounted your ESP) For MBR: grub-install /dev/sda (or whichever disk you intend to boot) 2. grub-mkconfig -o /boot/grub/grub.cfg Specifying bootloader ids or other things is generally not required. Regarding nvidia, are you using the port 'opt/nvidia' or the upstream installer? I'd recommend using the port as it's already tailored for CRUX. It also seems to work just fine with 5.4.x kernels. At least for my systems with kernel 5.4.44/5.4.49 and nvidia 450.57. Regards, Matt _______________________________________________ CRUX mailing list CRUX@lists.crux.nu https://lists.crux.nu/mailman/listinfo/crux
Hi, Dave, Regarding iwlwifi and for future reference, this driver is part of the kernel, not something external, which means that the version of the driver is tied to the version of the kernel to some extent. I have a system, for example, running 4.19.x and using iwlwifi without issue: $ lsmod | grep iwl iwlmvm 290816 0 led_class 16384 2 input_leds,iwlmvm mac80211 446464 1 iwlmvm iwlwifi 225280 1 iwlmvm cfg80211 339968 3 iwlmvm,iwlwifi,mac80211 $ ip l show dev wlan0 | head -1 4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 $ uname -r 4.19.132 $ dmesg | grep firmw | grep iwl [ 1.582232] iwlwifi 0000:07:00.0: loaded firmware version 38.755cfdd8.0 op_mode iwlmvm It's possible that your hardware is so new that the 4.19.x kernel doesn't support it, I suppose. Just providing some reference. Regarding grub, your grub config file has no menuentry for a linux kernel, which is probably because it's not named in a way that grub-mkcofnig expects. grub-mkconfig looks for these patterns: '/boot/vmlinuz-*', '/vmlinuz-*', '/boot/kernel-*'. If you named the file simply 'vmlinuz' or 'kernel' it wouldn't work, but 'vmlinuz-5.4.49' would. If you write your own config you can call it whatever you like, but this is what grub-mkconfig expects. You can find these patterns in /etc/grub.d/10_linux if you want to verify. The 'grub-install' command only installs the bootloader into your MBR or UEFI but doesn't create a config file, hence the need for 'grub-mkconfig'. If you get a grub menu like you said, that means grub is installed and booting, just doesn't have a correct (or fully populated) config file. Regards, Matt
participants (7)
-
david mccooey -
Fredrik -
Hans Bezemer -
Joacim Olsen Tangen -
Matt Housh -
Milan Buška -
Steve Volumetric