Solved Intel msi z590 motherboard Lan

rpowell47

Active Member

Reaction score: 15
Messages: 189

I have purchased a new MSI Z590 PRO WIFI Motherboad. With the fabulous help from other BSDer's, I was finally successful in getting the Nvidia graphics card to load. After purchasing an ethernet card to be able to gain access to the internet, I want to change over to the on board LAN Ethernet connection. I loaded in /boot/loader.conf the intel LAN drivers listed in the FreeBSD 13.0-RELEASE Hardware notes. Non of those listed worked. Thus, my question is how do I find the the controller chip Number that is on my MSI motherboad? My assumption is that non of the current BSD drivers are able to support the MSI chip. As always, I appreciate you acumen in helping others learn, and if possible, solve particular issues. Oh, here is the syntax I use for loading the BSD drivers in loader.conf - if_em_load="YES"
 

T-Daemon

Daemon

Reaction score: 829
Messages: 1,697

According to the specifications of the motherboard it has an Intel® I225-V 2.5Gbps LAN (please check with pciconf -vl | grep -B3 network).

At the moment the I225-V is not supported on 13.0-RELEASE, but you could build the driver from source for 13.0-RELEASE (as dizzy suggested, besides installing 13.0-STABLE).
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

According to the specifications of the motherboard it has an Intel® I225-V 2.5Gbps LAN (please check with pciconf -vl | grep -B3 network).

At the moment the I225-V is not supported on 13.0-RELEASE, but you could build the driver from source for 13.0-RELEASE (as dizzy suggested, besides installing 13.0-STABLE).
[root@randy /etc]# pciconf -vl | grep -B3 network
none5@pci0:3:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x1462 subdevice=0x7d09
vendor = 'Intel Corporation'
device = 'Ethernet Controller I225-V'
class = network
--
re0@pci0:4:0:0: class=0x020000 rev=0x06 hdr=0x00 vendor=0x10ec device=0x8168 subvendor=0x10ec subdevice=0x8168
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
class = network

Here is the data form pciconf -vl | grep -B3 network

In addition, I'm not experienced nor knowledgeable enough if I install BSD 13.0-STABLE I will still be running the RELEASE version when I reboot. Sorry for my lack of experience and knowledge.

Also, do I need to install or locate and the iflib framework for this new igc driver to work with 13.0-RELEASE?
Where do I locate the igc driver so as to build it from source?
 

T-Daemon

Daemon

Reaction score: 829
Messages: 1,697

Here is the data form pciconf -vl | grep -B3 network
Thanks, that confirms the I225.
Sorry for my lack of experience and knowledge.
No need to apologize. We don't expect here from forum members seeking help to be experts.
Also, do I need to install or locate and the iflib framework for this new igc driver to work with 13.0-RELEASE?
No, you don't need to worry about it.
Where do I locate the igc driver so as to build it from source?
I can offer you two options. The first one is I can guide you to build the driver from source. It's not complicated, and you may learn a little bit about the system.

The second option is I can attach the driver to a posting. You have just to copy it on the system.
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Thanks, that confirms the I225.

No need to apologize. We don't expect here from forum members seeking help to be experts.

No, you don't need to worry about it.

I can offer you two options. The first one is I can guide you to build the driver from source. It's not complicated, and you may learn a little bit about the system.

The second option is I can attach the driver to a posting. You have just to copy it on the system.
I would really like to have your expertise in the process of building the driver from source and loading it into the system.
Here was my thoughts when you mentioned "build from source option:"
cd /sys/dev and then ee a new file nameed igc that was built from source and add the code. Is that anywhere close? Anyway thanks for our time and support!!



I searched the BSD ports and any man pages for igc - non found. So, I'm assuming that I will just have to wait. I do want to thank all BSDer's who volunteer their time and expertise in taking the time to research, develop, and add their hard work to FreeBSD so we average lovers and users of FreeBSD can enjoy BSD!
 

T-Daemon

Daemon

Reaction score: 829
Messages: 1,697

cd /sys/dev and then ee a new file nameed igc that was built from source and add the code. Is that anywhere close?
Not quite. The code is added by other means.
I searched the BSD ports ...
There is no igc(4) driver port.
... and any man pages for igc - non found.
For now the manual can be found in 13.0-STABLE and 14.0-CURRENT only. If you backport the source code for the driver to 13.0-RELEASE it contains also the code for the manual and can be compiled and installed if desired. It can be read also from source code directly.

To build the driver you need to fetch the source tree of the FreeBSD system. First install the tool to get the source tree:
Code:
# pkg install git-lite
Then make sure /usr/src/ is empty, afterwards execute
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
Please post output of the last command.
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Not quite. The code is added by other means.

There is no igc(4) driver port.

For now the manual can be found in 13.0-STABLE and 14.0-CURRENT only. If you backport the source code for the driver to 13.0-RELEASE it contains also the code for the manual and can be compiled and installed if desired. It can be read also from source code directly.

To build the driver you need to fetch the source tree of the FreeBSD system. First install the tool to get the source tree:
Code:
# pkg install git-lite
Then make sure /usr/src/ is empty, afterwards execute
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
Please post output of the last command.
Code:
Proceed with this action? [y/N]: y
[1/1] Fetching git-lite-2.32.0_1.txz: 100%    5 MiB   1.2MB/s    00:04    
Checking integrity... done (0 conflicting)
[1/1] Installing git-lite-2.32.0_1...
===> Creating groups.
Creating group 'git_daemon' with gid '964'.
===> Creating users
Creating user 'git_daemon' with uid '964'.
[1/1] Extracting git-lite-2.32.0_1: 100%
=====
Message from git-lite-2.32.0_1:

--
If you installed the GITWEB option please follow these instructions:

In the directory /usr/local/share/examples/git/gitweb you can find all files to
make gitweb work as a public repository on the web.

All you have to do to make gitweb work is:
1) Please be sure you're able to execute CGI scripts in
   /usr/local/share/examples/git/gitweb.
2) Set the GITWEB_CONFIG variable in your webserver's config to
   /usr/local/etc/git/gitweb.conf. This variable is passed to gitweb.cgi.
3) Restart server.


If you installed the CONTRIB option please note that the scripts are
installed in /usr/local/share/git-core/contrib. Some of them require
other ports to be installed (perl, python, etc), which you may need to
install manually.
[root@randy ~]# cd /usr/src
[root@randy /usr/src]# git clone [URL]https://git.freebsd.org/src.git[/URL] /usr/src
fatal: destination path '/usr/src' already exists and is not an empty directory.
[root@randy /usr/src]# git branch -r
fatal: not a git repository (or any parent up to mount point /usr)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[root@randy /usr/src]#
 
Last edited by a moderator:
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Proceed with this action? [y/N]: y
[1/1] Fetching git-lite-2.32.0_1.txz: 100% 5 MiB 1.2MB/s 00:04
Checking integrity... done (0 conflicting)
[1/1] Installing git-lite-2.32.0_1...
===> Creating groups.
Creating group 'git_daemon' with gid '964'.
===> Creating users
Creating user 'git_daemon' with uid '964'.
[1/1] Extracting git-lite-2.32.0_1: 100%
=====
Message from git-lite-2.32.0_1:

--
If you installed the GITWEB option please follow these instructions:

In the directory /usr/local/share/examples/git/gitweb you can find all files to
make gitweb work as a public repository on the web.

All you have to do to make gitweb work is:
1) Please be sure you're able to execute CGI scripts in
/usr/local/share/examples/git/gitweb.
2) Set the GITWEB_CONFIG variable in your webserver's config to
/usr/local/etc/git/gitweb.conf. This variable is passed to gitweb.cgi.
3) Restart server.


If you installed the CONTRIB option please note that the scripts are
installed in /usr/local/share/git-core/contrib. Some of them require
other ports to be installed (perl, python, etc), which you may need to
install manually.
[root@randy ~]# cd /usr/src
[root@randy /usr/src]# git clone https://git.freebsd.org/src.git /usr/src
fatal: destination path '/usr/src' already exists and is not an empty directory.
[root@randy /usr/src]# git branch -r
fatal: not a git repository (or any parent up to mount point /usr)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
[root@randy /usr/src]#
This is in the /usr/src directory now:
Code:
root@randy /usr/src]# ls
arcconfig        COPYRIGHT        ObsoleteFiles.inc    contrib            libexec            sys
.arclint        LOCKS            README            crypto            release            targets
.cirrus.yml        MAINTAINERS        README.md        etc            rescue            tests
.clang-format        Makefile        RELNOTES        gnu            sbin            tools
.gitattributes        Makefile.inc1        UPDATING        include            secure            usr.bin
.github            Makefile.libcompat    bin            kerberos5        share            usr.sbin
.gitignore        Makefile.sys.inc    cddl            lib            stand
[root@randy /usr/src]#
 
Last edited by a moderator:
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Thanks T-Diamond, but my Freebsd box is not set up as a server. Darn. I only use it as a very nice desktop box.
Should I remove the git-lite: 2.32.0_1 pkg?
How is the quickest way to remove all files and directories in the /usr/src directory?
Or have I simply misunderstood some of the directions!

I'm sorry to have to be talked to as if I'm a third grader, but I truly believe that is about my level of understanding. When I first cd /usr/src and ls - there was nothing showing. So I loaded the pkg gt-lite:2/32/0_1 and then I entered the following lines individually and hit enter after I added each line.
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
And now, I believe, I'm back in the first grade.
 

T-Daemon

Daemon

Reaction score: 829
Messages: 1,697

When I first cd /usr/src and ls - there was nothing showing. So I loaded the pkg gt-lite:2/32/0_1 and then I entered the following lines individually and hit enter after I added each line.
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
And now, I believe, I'm back in the first grade.
Are you saying, after you made sure /usr/src/ is empty, and executed commands
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# git branch -r
those return with errors shown in post #9 ?
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Are you saying, after you made sure /usr/src/ is empty, and executed commands
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# git branch -r
those return with errors shown in post #9 ?
yes
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 12,038
Messages: 38,487

How is the quickest way to remove all files and directories in the /usr/src directory?
rm -rf /usr/src/.[^.]* /usr/src/* # You need that .[^.]* to remove the so-called 'hidden' files.

Assuming you have a ZFS system you can't do rm -rf /usr/src because ZFS is going to prevent you from removing the dataset. If it's UFS then rm -rf /usr/src will work just fine.
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

rm -rf /usr/src/.[^.]* /usr/src/* # You need that .[^.]* to remove the so-called 'hidden' files.

Assuming you have a ZFS system you can't do rm -rf /usr/src because ZFS is going to prevent you from removing the dataset. If it's UFS then rm -rf /usr/src will work just fine.
Thank you Sir Dice! I'm using ZFS and carried out the first example. # /usr/src is now empty!
 

T-Daemon

Daemon

Reaction score: 829
Messages: 1,697

/usr/src is now empty!
To make sure please execute ls -a /usr/src to check if the hidden dot files and directories are also removed. If the directory returns empty execute again
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
post output of git branch -r .
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

To make sure please execute ls -a /usr/src to check if the hidden dot files and directories are also removed. If the directory returns empty execute again
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
post output of git branch -r .
There are these two different visible dot patterns . .. in the /usr/src directory
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

There are these two different visible dot patterns . .. in the /usr/src directory
Code:
.    ..
[root@randy /usr/src]# pkg install git-lite
Updating FreeBSD repository catalogue...
Fetching packagesite.txz: 100%    6 MiB   1.3MB/s    00:05    
Processing entries: 100%
FreeBSD repository update completed. 30742 packages processed.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed
[root@randy /usr/src]# ls
[root@randy /usr/src]#  ls -a /usr/src
.    ..
[root@randy /usr/src]#  rm -rf /usr/src/.[^.]* /usr/src/* 
[root@randy /usr/src]#  ls -a /usr/src
.    ..
[root@randy /usr/src]#
Here is what shows now.
 

T-Daemon

Daemon

Reaction score: 829
Messages: 1,697

Very good. Now please execute
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
post output of git branch-r .
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Very good. Now please execute
Code:
# git clone https://git.freebsd.org/src.git /usr/src
# cd /usr/src
# git branch -r
post output of git branch-r .
Okay, I've excuted those three commands. Should I reboot now?
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Okay, I've excuted those three commands. Should I reboot now?
Code:
origin/HEAD -> origin/main
  origin/main
  origin/releng/1
  origin/releng/10.0
  origin/releng/10.1
  origin/releng/10.2
  origin/releng/10.3
  origin/releng/10.4
  origin/releng/11.0
  origin/releng/11.1
  origin/releng/11.2
  origin/releng/11.3
  origin/releng/11.4
  origin/releng/12.0
  origin/releng/12.1
  origin/releng/12.2
  origin/releng/13.0
  origin/releng/2.0
  origin/releng/2.0.5
  origin/releng/4.10
  origin/releng/4.11
  origin/releng/4.3
  origin/releng/4.4
  origin/releng/4.5
  origin/releng/4.6
  origin/releng/4.7
  origin/releng/4.8
  origin/releng/4.9
  origin/releng/5.0
  origin/releng/5.1
  origin/releng/5.2
  origin/releng/5.3
  origin/releng/5.4
  origin/releng/5.5
  origin/releng/6.0
  origin/releng/6.1
  origin/releng/6.2
  origin/releng/6.3
  origin/releng/6.4
[root@randy /usr/src]#
 

tankist02

Well-Known Member

Reaction score: 47
Messages: 326

I also have the same Intel network card on my new motherboard. I verified that 13-Stable works fine with the card. But some other things important to me (like darktable) do not work. I'm wondering when 13.1-Release will be made?
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

No, no need to. Execute in /usr/src/
Code:
# git checkout releng/13.0
Code:
root@randy:~ # git checkout releng/13.0
fatal: not a git repository (or any of the parent directories): .git
root@randy:~ # cd /usr/src git checkout releng/13.0
cd: Too many arguments.
r
 
OP
R

rpowell47

Active Member

Reaction score: 15
Messages: 189

Code:
root@randy:~ # git checkout releng/13.0
fatal: not a git repository (or any of the parent directories): .git
root@randy:~ # cd /usr/src git checkout releng/13.0
cd: Too many arguments.
Sorry this is what just happened. I believe I messed up the syntax before.
Code:
root@randy:~ # cd /usr/src
root@randy:/usr/src # git checkout releng/13.0
Updating files: 100% (21611/21611), done.
Branch 'releng/13.0' set up to track remote branch 'releng/13.0' from 'origin'.
Switched to a new branch 'releng/13.0'
root@randy:/usr/src #
 
Top