On 11/09/2019 09:06, Furkan İnciroğlu wrote:
>
>
>> Hmm, and can't you install lspci in chroot? Anyway, if you see this in dmesg,
>> and the card is e1000 (you use a virtual machine?), there is something else.
>> Maybe try running as root "journalctl", and look for eth0.
>>
>> Pierre
>> --
>
>
> Hello again,
>
> Finally, I have solved my problem. Briefly, I could not see any network
> interface like eth0, when I booted my LFS. In addition, there was not any mac
> address match my driver so I even can not add network interface by myself. I
> have to say, I was booting my LFS in VirtualBox.
>
> Solution: I shutdown my LFS machine in VirtualBox. In Network settings, I
> switched Adapter Type to Intel Pro/1000 T Server from PCnet-FAST III and my
> problem solved. Clearly, the issue was PCnet-FAST III. Because, when I
> checked my network driver through this command "dmesg | grep e1000" shows me
> your driver "Intel Pro/1000".
Glad it is solved. So you did not have the right driver (for PCnet-FAST III)
in the kernel, did you? According to menuconfig, there is a PCNET interface at:
Device drivers
Network device support
Ethernet driver support
AMD devices
AMD PCnet32 PCI support
But I have not tried. The module is called pcnet32 if you compile this as a
module.
Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
