Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230
(For the not working Wifi chip, I use at the moment an USB-Wifi dongle, Realtek RTL8191S WLAN Adapter, which works fine). I also can't get Xorg plus twm up; it says in /var/log/Xorg.0.log at the end: .. REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270, ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS, AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS, ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI, MULLINS, KAVERI, HAWAII [ 248.442] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 248.442] (II) scfb: driver for wsdisplay framebuffer: scfb [ 248.442] (II) VESA: driver for VESA chipsets: vesa [ 248.442] (--) Using syscons driver with X support (version 2.0) [ 248.442] (--) using VT number 9 [ 248.447] (EE) open /dev/dri/card0: No such file or directory [ 248.447] (WW) Falling back to old probe method for modesetting [ 248.447] (EE) open /dev/dri/card0: No such file or directory [ 248.447] (WW) Falling back to old probe method for scfb [ 248.447] scfb trace: probe start .. The kernel modules loaded are: Id Refs AddressSize Name 1 139 0x8020 1d4f010 kernel 21 0x81f5 36c0 coretemp.ko 31 0x81f55000 9c48 if_cdce.ko 42 0x81f5f000 6138 uether.ko 51 0x81f66000 a698 cuse.ko 61 0x81f71000f7f38 ipl.ko 71 0x83c0 462be0 zfs.ko 81 0x84063000 1510b8 radeonkms.ko 92 0x841b500073da0 drm.ko 101 0x83bd7000 22a8 iic.ko 113 0x83bda000 1100 linuxkpi_gplv2.ko 124 0x83bdc000 6320 dmabuf.ko 134 0x83be3000 3080 linuxkpi_hdmi.ko 141 0x83be7000 c7b0 ttm.ko 151 0x83bf4000 3370 acpi_wmi.ko 161 0x83bf8000 5ee0 ig4.ko 171 0x84229000 3210 intpm.ko 181 0x8422d000 2178 smbus.ko 191 0x842330ad8 linux.ko 204 0x84261000 be30 linux_common.ko 211 0x8426d0002ccf8 linux64.ko 221 0x8429a000 2270 pty.ko 231 0x8429d000 3540 fdescfs.ko 241 0x842a1000 73c0 linprocfs.ko 251 0x842a9000 43e4 linsysfs.ko 261 0x842ae000 4d00 ng_ubt.ko 276 0x842b3000 bb28 netgraph.ko 282 0x842bf000 a238 ng_hci.ko 294 0x842ca000 2668 ng_bluetooth.ko 301 0x842cd000 a7e0 if_rsu.ko 311 0x842d8000 3218 iichid.ko 325 0x842dc000 32a8 hidbus.ko 331 0x842e f250 ng_l2cap.ko 341 0x842f19f08 ng_btsocket.ko 351 0x8430a000 38b8 ng_socket.ko 371 0x8432e000 21e0 hms.ko 381 0x84331000 40a8 hidmap.ko 391 0x84336000 334d hmt.ko 401 0x8433a000 22c4 hconf.ko The complete Xorg.0.log is here: http://www.unixarea.de/Xorg.0.log.txt Thanks in advance for ideas. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230
El día miércoles, marzo 27, 2024 a las 03:51:33p. m. +0100, Matthias Apitz
escribió:
> The WLAN card seems to be:
>
> none2@pci0:1:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x14c3
> device=0x7961 subvendor=0x1a3b subdevice=0x4680
> vendor = 'MEDIATEK Corp.'
> device = 'MT7921 802.11ax PCI Express Wireless Network Adapter'
> class = network
>
> Perhaps not supported until today:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264300
While grepping through /usr/src I found the driver in
/usr/src/sys/contrib/dev/mediatek/mt76/mt7921/ and a make && make
install in
# cd /usr/src/sys/modules/mt76
# make
..
# make install
===> core (install)
install -T release -o root -g wheel -m 555 mt76_core.ko /boot/modules/
kldxref /boot/modules
===> mt7915 (install)
install -T release -o root -g wheel -m 555 if_mt7915.ko /boot/modules/
kldxref /boot/modules
===> mt7921 (install)
install -T release -o root -g wheel -m 555 if_mt7921.ko /boot/modules/
kldxref /boot/modules
installs it fine. There is also a manpage in /usr/src/share/man/man4/mt7921.4
(attached)
I still have to build the firmware from ports/net/wifi-firmware-mt76-kmod.
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
MT7921(4) FreeBSD Kernel Interfaces Manual MT7921(4)
NAME
mt7921 – MediaTek IEEE 802.11ax wireless network driver
SYNOPSIS
The driver will auto-load without any user interaction using devmatch(8)
if enabled in rc.conf(5).
Only if auto-loading is explicitly disabled, place the following lines in
rc.conf(5) to manually load the driver as a module at boot time:
kld_list="${kld_list} if_mt7921"
The driver should automatically load any firmware needed for the
particular chipset.
It is discouraged to load the driver from loader(8).
DESCRIPTION
The mt7921 driver is derived from MediaTek's Linux mt76 driver and
provides support for the following chipsets:
MediaTek MT7921E (PCIe)
This driver requires firmware to be loaded before it will work. The
package wifi-firmware-mt76-kmod from the
ports/net/wifi-firmware-mt76-kmod port needs to be installed before the
driver is loaded. Otherwise no wlan(4) interface can be created using
ifconfig(8).
The driver uses the linuxkpi_wlan and linuxkpi compat framework to bridge
between the Linux and native FreeBSD driver code as well as to the native
net80211(4) wireless stack.
While mt7921 supports all 802.11 a/b/g/n/ac and ax the compatibility code
currently only supports 802.11 a/b/g modes. Support for 802.11 n/ac is
to come.
BUGS
Certainly.
SEE ALSO
wlan(4), ifconfig(8), wpa_supplicant(8)
HISTORY
The mt7921 driver first appeared in FreeBSD 14.0.
FreeBSD 14.0-CURRENTApril 18, 2023FreeBSD 14.0-CURRENT
Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230
El día miércoles, marzo 27, 2024 a las 10:37:48a. m. +0100, Matthias Apitz escribió: > > Hello, > > I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to > boot FreeBSD with boot verbose messages from an USB key and I'm able to > login. The /var/log/messages are here > http://www.unixarea.de/ASUS-VivoBook-Pro-14-messages.txt A 'gpart list nda0' is here http://www.unixarea.de/nda0.txt Actual the (Windows) partitions are: # egrep 'Name:|Mediasize:' nda0.txt 1. Name: nda0p1 Mediasize: 272629760 (260M) 2. Name: nda0p2 Mediasize: 16777216 (16M) 3. Name: nda0p3 Mediasize: 510507949568 (475G) 4. Name: nda0p4 Mediasize: 1101004800 (1.0G) 5. Name: nda0p5 Mediasize: 209715200 (200M) 1. Name: nda0 Mediasize: 512110190592 (477G) A 'pciconf -lv' is here: http://www.unixarea.de/pciconf.txt The WLAN card seems to be: none2@pci0:1:0:0: class=0x028000 rev=0x00 hdr=0x00 vendor=0x14c3 device=0x7961 subvendor=0x1a3b subdevice=0x4680 vendor = 'MEDIATEK Corp.' device = 'MT7921 802.11ax PCI Express Wireless Network Adapter' class = network Perhaps not supported until today: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=264300 An attached USB mouse is detected and works. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Re: CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230
On Wed, Mar 27, 2024 at 12:38 PM Matthias Apitz wrote: > > > Hello, > > I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to > boot FreeBSD with boot verbose messages from an USB key and I'm able to > login. The /var/log/messages are here > http://www.unixarea.de/ASUS-VivoBook-Pro-14-messages.txt `pciconf -lv` would be useful too.
CURRENT on laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230
Hello, I bought the laptop ASUS VivoBook Pro 14 90NB0VZ2-M01230 and managed to boot FreeBSD with boot verbose messages from an USB key and I'm able to login. The /var/log/messages are here http://www.unixarea.de/ASUS-VivoBook-Pro-14-messages.txt I can identify the harddisk as nda0 (correct), but don't see any mouse and WLAN card. I will also boot an Ubuntu 22.04.4 from USB, maybe this gives more hints about hardware details. Thanks for any comments. I have 30 days to return the laptop to the store. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
