LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux From Scratch (https://www.linuxquestions.org/questions/linux-from-scratch-13/)
-   -   LFS 7.3 Chapter 7.2.2 Creating Network Interface Configuration Files (https://www.linuxquestions.org/questions/linux-from-scratch-13/lfs-7-3-chapter-7-2-2-creating-network-interface-configuration-files-4175460405/)

druuna 07-03-2013 02:43 AM

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
dmesg | grep -i eth
ipconfig -a
cat /etc/sysconfig/ifconfig.eth0
cat /etc/udev/rules.d/70-persistent-net.rules


DeeGee 07-03-2013 04:23 AM

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 :)

druuna 07-03-2013 04:42 AM

Quote:

Originally Posted by DeeGee (Post 4983275)
I haven't compiled pciutils

You might want to build this one, it is a very useful tool.
Quote:

dmesg gives no output
Strange, it should spit out kernel ring-buffer information.
Quote:

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 ate attached.
ifconfig is also a valuable tool (although they are switching to the ip command).

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.

DeeGee 07-03-2013 05:17 AM

Quote:

Originally Posted by druuna (Post 4983283)
You might want to build this one, it is a very useful tool.
Strange, it should spit out kernel ring-buffer information.
ifconfig is also a valuable tool (although they are switching to the ip command).

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.

Sure will, sorry for the inconvenience :)

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?

re_nelson 07-03-2013 01:15 PM

Quote:

Originally Posted by DeeGee (Post 4983294)
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?

Before recompiling the kernel, please post the output of dmesg | tail after performing these commands:

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.

DeeGee 07-03-2013 10:31 PM

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
mosprobe e1000 gives no output

Than you:)

re_nelson 07-03-2013 10:42 PM

1 Attachment(s)
Quote:

Originally Posted by DeeGee (Post 4983858)
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.

Per your post, the e1000 driver is not modular but is part of the kernel image. My preference is to build everything as a module but that's not necessarily germane to this matter.

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:

DeeGee 07-03-2013 11:53 PM

Quote:

Originally Posted by re_nelson (Post 4983860)
Per your post, the e1000 driver is not modular but is part of the kernel image. My preference is to build everything as a module but that's not necessarily germane to this matter.

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:

Thank you so much. It was indeed a problem with the configuration. Only now did I figure out that though Virtualbox set Intel Pro/1000 MT for recognized Linux distros, it sets PCnet-PCI for unrecognized distros(LFS).

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 :)

re_nelson 07-03-2013 11:59 PM

Quote:

Originally Posted by DeeGee (Post 4983883)
Thank you so much. It was indeed a problem with the configuration. Only now did I figure out that though Virtualbox set Intel Pro/1000 MT for recognized Linux distros, it sets PCnet-PCI for unrecognized distros(LFS).

Changed the network adapter to Intel Pro/1000 MT and works fine.

Glad to be of assistance and be sure to mark the thread as [SOLVED] as a courtesy to others with similar problems.


All times are GMT -5. The time now is 04:23 AM.