Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You have an ethernet card that requires firmware to work. That's unusual; mostly it is wireless cards that create that sort of problem. The kernel is trying to load the firmware onto the card and failing.
So:
1) do you have that named file available in /lib/firmware? If not, you must copy it over from your host system.
2) Have you built your ethernet driver as a module or directly into the kernel? For cards that need to use firmware, the kernel's card driver should always be built as a module. That ensures that firmware files on the hard drive will be available when the network card is configured.
thank for answer in 1) but in 2) i don't know how to .
Quote:
Originally Posted by hazel
You have an ethernet card that requires firmware to work. That's unusual; mostly it is wireless cards that create that sort of problem. The kernel is trying to load the firmware onto the card and failing.
So:
1) do you have that named file available in /lib/firmware? If not, you must copy it over from your host system.
2) Have you built your ethernet driver as a module or directly into the kernel? For cards that need to use firmware, the kernel's card driver should always be built as a module. That ensures that firmware files on the hard drive will be available when the network card is configured.
******
thank for answer in 1) but in 2) i don't know how to built ethernet driver as a module.
Go back into your kernel source tree and make sure you have a safety copy of your .config file somewhere else (most people keep theirs in /boot as config-4.18.3). Make mrproper, then copy the configuration file back as .config.
Make menuconfig. Go to Device drivers-->Network device support and find the driver for your card. If it is built in, it will have an asterisk * beside it. Change this to M for module. You can either type M or use the space bar to cycle through the possibilities. Then build and reinstall the kernel and its modules as in the book. You did it successfully once so you can do it again.
Note: when you do "make modules_install", you will be creating a new /lib/modules/4.18.3 directory, so you must first rename the existing one to something else, for example 4.18.3.old.
Go back into your kernel source tree and make sure you have a safety copy of your .config file somewhere else (most people keep theirs in /boot as config-4.18.3). Make mrproper, then copy the configuration file back as .config.
Make menuconfig. Go to Device drivers-->Network device support and find the driver for your card. If it is built in, it will have an asterisk * beside it. Change this to M for module. You can either type M or use the space bar to cycle through the possibilities. Then build and reinstall the kernel and its modules as in the book. You did it successfully once so you can do it again.
Note: when you do "make modules_install", you will be creating a new /lib/modules/4.18.3 directory, so you must first rename the existing one to something else, for example 4.18.3.old.
What do you mean, you can't enter anything in your prompt? What prompt? And why are you suddenly showing me your grub menu? You didn't have a grub problem up until now. Do try to think logically and don't expect me to do everything for you.
Press return, let grub boot the kernel, and in due course you will get a login prompt. Enter "root" and the root password you created in chapter 6. Then, once you are logged in, you can check your ethernet connection by pinging a suitable ip address. I suggest you try your router address first. If that works, try the Google dns server at 8.8.8.8.
First of all, the missing firmware for the rtl8168 should be no problem. Having the same here, without any trouble with the card.
iirc, there are firmware packages available somewhere in the www, maybe at the debian site. But i did not yet recognize any difference in the networkdevice, regardless if the firmware is there or not.
Then i suspect, that something with your starting scripts is going wrong;
is it possible, that you mixed up instructions from the "normal" LFS and LFS-systemd during your build?
Is it solved. I once meet an issue with rtl wifi driver. The version was Linux-4.16.18. Once the issue happened, my system never responded. I couldn't type anything. I think I read similar error report on Redhat community and it has already been fixed in later kernels.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.