Its rather hard to give advise without the specifics.
From a freshly booted LFS, as root, post the output of the following commands: Code:
lspci | grep -i eth |
3 Attachment(s)
Hi,
I haven't compiled pciutils so cannot run the lspci grep. dmesg gives no output I had disabled the ipconfig option according to the LFS book, but ran a ip link show. The results of it and the other two are attached. I noticed that the results of ip link show gives only the lo and sit0 interfaces. I searched on what sit is, but my connection is a static ip4 one and I there's no need for the sit0 according to my (sketchy) understanding. This is actually my first LFS build, and I'm compiled a second build with jhalfs just as an experiment. What I want next is to port the iso image of the vm to a partition in my laptop but am unsure of the complications that may arise because of the networking issue. Thanks so much :) |
Quote:
Quote:
Quote:
I cannot determine the hardware address from the limited output posted. Are you sure your network card driver is present in your kernel config? PS: Can you post the output in the thread next time, much easier to reference then when they are separate linked images. |
Quote:
I have no means of installing pciutils etc. because there's no way to connect to the network at the moment. About kernel configurations, I recompiled my kernel by configuring Intel 82540em as the Intel(R) PRO/1000 Gigabit Ethernet support as a module. (I referred this thread http://forums.gentoo.org/viewtopic-t...8-start-0.html) to no avail. Would there be any drivers I should enable? |
Quote:
modprobe -r e1000 modprobe e1000 Also double-check that VirtualBox's network device is configured to use the Intel/PRO 1000 MT Desktop (82540EM) device. |
1 Attachment(s)
On Virtualbox : Yes, it runs fine on the other virtual machines. I'm afraid I do not know how to check for vm network configurations and any pointer would be appreciated.
I have attached the screenshot of the output. (There are a lot of lines and typing could cause an error) modprobe -r e1000 gives the output Code:
Module e1000 is builtin Than you:) |
1 Attachment(s)
Quote:
In a prior post, you mentioned that dmesg | grep eth yields no results. If indeed that's the case, check the network configuration of VirtualBox by looking at the Adapter 0 value as shown in the attached screenshot: |
Quote:
Changed the network adapter to Intel Pro/1000 MT and works fine. Alternatively, I think I'd add PCInet configurations too to the next LFS build. Thanks again to everyone who helped me through :) |
Quote:
|
All times are GMT -5. The time now is 04:23 AM. |