ú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