Solved question about hardware drivers when manual install freebsd14.2 ?

fff2024g

fff2024g

Dear all:
morning. i have install freebsd 14.2 by manual . when i finished it. i don't find any driver for my devices.
the system works normal.
what is manual installation :
1. create partiton by gpart
2. tar kernal.txz and base.txz
3. reboot.

what step i need to do for install driver for all hardwares ?....
how to make sure the driver was correct ?
thanks.
 
Are drivers you need really in base? Aren't they belong to ports?

For example, if you have nvidia GPU card which is the only display device connected to monitor, you'll want x11/nvidia-driver (and graphics/nvidia-drm-kmod to install matching drm drivers if you want auto-configuration for X11 and/or Wayland to work). Your milage may vary with how many ports drivers are needed.

And even though kmod ports are available as official pkgs, too, the safest way is to build them locally, unlike usual applications. So you'll want net/gitup or devel/git[|-lite|-tiny] to pull ports tree and src tree in. And you need pkg bootstrap -f before these.

Why src? Because kmod ports (typically drivers and filesystems) require kernel sources that exactly matches with the kernel they are to be used with.
 
T-Aoki said:
Are drivers you need really in base? Aren't they belong to ports?

For example, if you have nvidia GPU card which is the only display device connected to monitor, you'll want x11/nvidia-driver (and graphics/nvidia-drm-kmod to install matching drm drivers if you want auto-configuration for X11 and/or Wayland to work). Your milage may vary with how many ports drivers are needed.

And even though kmod ports are available as official pkgs, too, the safest way is to build them locally, unlike usual applications. So you'll want net/gitup or devel/git[|-lite|-tiny] to pull ports tree and src tree in. And you need pkg bootstrap -f before these.

Why src? Because kmod ports (typically drivers and filesystems) require kernel sources that exactly matches with the kernel they are to be used with.
Click to expand...
Dear T-Aoki :
my laptop was been install freebsd14.2 by manual, system looks like working normal. but. this guy don't have any drivers about wire and wireless. so network can't work normal ..
but , when i reinstall freebsd14.2 by autoufs or autozfs , the system will find all network card, and driver it working. what step i have missed about networking ? thanks.
 
Base normally includes a generic ethernet driver.

If the ethernet chipset is too new, it would really help if you have a USB->ethernet hardware adapter. In which case, the base will see it as ue0.
 
As far as I know, many notebooks have RealTek (aka Crab) NICs both for wired and wireless. In these cases, if the chipsets are too new as noted by astyle, you'll want net/realtek-re-kmod or net/realtek-re-kmod198. The problem is that how you can download it. If you have another FreeBSD computer working, using pkg fetch <pkgname> would help, but you need to temporarily switch ABI string if the computer is running different version.
 
I was really talking about something like this:
1748189853319.png

I have a similar adapter, I use it every time I need to install FreeBSD on an AM5 board. I download net/realtek-re-kmod straight to the machine with help of that adapter. Same adapter can be used to download wifi drivers.
 
fff2024g said:
my laptop was been install freebsd14.2 by manual, system looks like working normal. but. this guy don't have any drivers about wire and wireless. so network can't work normal ..
but , when i reinstall freebsd14.2 by autoufs or autozfs , the system will find all network card, and driver it working. what step i have missed about networking ?
Click to expand...
This sounds not like a driver but a network configuration problem. Have you configured wired and wireless networks in /etc/rc.conf ? For example
Code: 
ifconfig_<wired_interface_name>="DHCP"

# or
ifconfig_DEFAULT="DHCP"
# see rc.conf(5) for ifconfig_DEFAULT

wlans_<wireless_interface_name>="wlan0"
ifconfig_wlan0="WPA DHCP"
 
astyle said:
If the ethernet chipset is too new, it would really help if you have a USB->ethernet hardware adapter.
Click to expand...
T-Aoki said:
If you have another FreeBSD computer working,
Click to expand...
A USB->ethernet hardware adapter or a second FreeBSD computer is not absolutely necessary. In today's electronic devices collection of a person, almost everyone has a smartphone with a mobile data plan.

Plug in the smartphone into the machines USB port, on phone enable "USB tethering", enable "Mobile data" connection, acquire IP on FreeBSD machine: dhclient ue0, pkg install ...

USB tethering can also be used to access a routers wifi access point over the phones wireless connection.
 
astyle said:
I was really talking about something like this:
View attachment 22731
I have a similar adapter, I use it every time I need to install FreeBSD on an AM5 board. I download net/realtek-re-kmod straight to the machine with help of that adapter. Same adapter can be used to download wifi drivers.
Click to expand...
DEar astyle :
no, my laptop was toshiba L700 c19r . this guy have a internal wifi rtl8188ce and a wire network. don't use external wifi adapter. thanks
 
fff2024g said:
DEar astyle :
no, my laptop was toshiba L700 c19r . this guy have a internal wifi rtl8188ce and a wire network. don't use external wifi adapter. thanks
Click to expand...
Well, you're in luck, Toshiba L700 series do have an ethernet port built in. And the laptop is from early 2010s, which predates the rtl8188ce by a good 5 years. So base.txz would definitely have a driver for the ethernet port.

But, you did mis-understand something. I never mentioned an external wifi adapter.

Not sure if the manual I found matches your laptop accurately, but just in case, here's a link to it. I found it by googling around.
 
And the installation (extracting) order should be base.txz at first, then kernel.txz, and others as needed.
But I could be mis-recalling.
My latest installation was the whole copy of my previous main branch environment for testing. And after putting the drive into new computer and startup,
  1. pull latest src repo,
  2. switch from main to just created brand-new stable branch,
  3. rebuild / reinstall base,
  4. pull latest ports repo,
  5. pkg bootstrap -f,
  6. rebuild/reinstalling all ports,
  7. install missing ports (ports on main branch environment are subset of my daily driver stable environment).
 
Dear all:
thanks for your help . below was my device list .
vgapci0@pci0:1:0:0: class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x0dec subvendor=0x1179 subdevice=0xfcd0
vendor = 'NVIDIA Corporation'
device = 'GF108M [GeForce GT 525M]'
class = display
subclass = VGA

rtwn0@pci0:9:0:0: class=0x028000 rev=0x01 hdr=0x00 vendor=0x10ec device=0x8176 subvendor=0x10ec subdevice=0x8181
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8188CE 802.11b/g/n WiFi Adapter'
class = network
alc0@pci0:10:0:0: class=0x020000 rev=0xc0 hdr=0x00 vendor=0x1969 device=0x1083 subvendor=0x1179 subdevice=0xfcd0
vendor = 'Qualcomm Atheros'
device = 'AR8151 v2.0 Gigabit Ethernet'
class = network
subclass = ethernet

game@dsa:~ $ xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
LVDS-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1366x768 60.00*+
HDMI-0 disconnected (normal left inverted right x axis y axis)

from the pciconf -lv command , that show me all devices has been know by freebsd14.2 . yeah, question. how to sure all devices driver correct ?

example . my graphic card was nvidia geforce GT 525m .. when i fresh install freebsd14.2 , the x11 will work normal. i don't install any driver..
from the pciconf -lv result. looks like this graphic card use the GF108M driver , right ? and i don't see any nvidia.ko load . when install nvidia-driver 390 for nvidia geforce GT525m , the nvidia.ko and nvidia-modeset.ko will be load in kernel.

maybe the pciconf -lv will show all known devices with some driver , right ? or not.. thanks
 
fff2024g said:
Dear all:
thanks for your help . below was my device list .
vgapci0@pci0:1:0:0: class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x0dec subvendor=0x1179 subdevice=0xfcd0
vendor = 'NVIDIA Corporation'
device = 'GF108M [GeForce GT 525M]'
class = display
subclass = VGA

rtwn0@pci0:9:0:0: class=0x028000 rev=0x01 hdr=0x00 vendor=0x10ec device=0x8176 subvendor=0x10ec subdevice=0x8181
vendor = 'Realtek Semiconductor Co., Ltd.'
device = 'RTL8188CE 802.11b/g/n WiFi Adapter'
class = network
alc0@pci0:10:0:0: class=0x020000 rev=0xc0 hdr=0x00 vendor=0x1969 device=0x1083 subvendor=0x1179 subdevice=0xfcd0
vendor = 'Qualcomm Atheros'
device = 'AR8151 v2.0 Gigabit Ethernet'
class = network
subclass = ethernet

game@dsa:~ $ xrandr
Screen 0: minimum 8 x 8, current 1366 x 768, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
LVDS-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1366x768 60.00*+
HDMI-0 disconnected (normal left inverted right x axis y axis)

from the pciconf -lv command , that show me all devices has been know by freebsd14.2 . yeah, question. how to sure all devices driver correct ?

example . my graphic card was nvidia geforce GT 525m .. when i fresh install freebsd14.2 , the x11 will work normal. i don't install any driver..
from the pciconf -lv result. looks like this graphic card use the GF108M driver , right ? and i don't see any nvidia.ko load . when install nvidia-driver 390 for nvidia geforce GT525m , the nvidia.ko and nvidia-modeset.ko will be load in kernel.

maybe the pciconf -lv will show all known devices with some driver , right ? or not.. thanks
Click to expand...
If you don't install any of x11/nvidia-driver* but xorg (fully or partially), generic driver for VESA (for legacy BIOS with sc console driver) or SCFB (for anything others) should be used.

Looking into Supported Products for each branch of FreeBSD driver listed here, assuming you're on amd64, 390.157, 340.108 and 304.137 lists GT 525m as supported.

All 3 versions are in main (aka latest) branch of ports tree as x11/nvidia-driver-390, x11/nvidia-driver-340 and x11/nvidia-driver-304 respectively.

Don't attempt to load nvidia[-modeset].ko via /boot/loader.conf.
As nvidia.ko (loaded as specified or via nvidia-modeset.ko) is a large kernel module, it could overflow on load by loader, causing undefined erroneous behaviors.
Load it via kld_list variable in /etc/rc.conf[.local] as documented in messages shown on install. This way, enough memory to load would be allocated.

Note that any of graphics/nvidia-drm-[510|515|61|66]-kmod doesn't support these "legacy" versions of x11/nvidia-driver-[470|390|340|304] because they don't have required codes in upstream tarball.
 
I've posted a reply to whom complaining delayed upgrades about x11/nvidia-driver-390 which contains current MFC (Merge From Current, aka MFL [Merge From Latest]) policy of nvidia-driver related ports to quarterly.

Beware that no MFC would be done unless the upgrade contains securty fix with CVE number. Or any breakage (except version mismatch between base and kernel modules and loading via /boot/loader.conf, of course!) are reported on Bugzilla (or patch is proposed on Phablicator) and fixes are committed to main (aka latest) branch.

This is because MFC with non-securty (nor any other "blanket" approved reson) updates requires explicit approval of portsmgr team per commit.
This could take additional long days if intensive QA is requested by portmgr and we have not enough resources. So if you choose to stay quarterly, please be patient until next quarterly is branched.

Another reason is the lack of GPUs to test legacy branches.

Yes, it's kinda resource limitation. We're volunteers and cannot purchase and keep every GPUs with our private budget. For example, I have Quadro P1000 (notebook) only.
So problems specific with other GPUs cannot be reproduced and fixes cannot be tested on hand. Reports and test by anyone affected (of course including myself) is always mandatory to proceed.
And binary-only parts can be fixed by upstream (nvidia) only. We can do nothing other than contacting them, and nvidia representative (not me, I'm not a nvidia insider) are watching Bugzilla and Phablicator.
 
You must log in or register to reply here.
Back
Top