Fenvi FV-N700 dual-band wifi adapter not seen by Lucid Puppy

Message

Mercedes350se · #1 Post by **Mercedes350se** » Wed 24 Jul 2019, 07:57

I have a fenvi FV-N700 dual band wifi adapter. It uses the 3572 chip but the 2800 driver works - refer to my 7.0.0a1 test.

It is not even seen in 5.2.8 frugal install network wizard.

Code: Select all

dmesg 
phy1 -> rt2800_init_eeprom: Error - Invalid RT chipset detected.
phy1 -> rt2x00lib_probe_dev: Error - Failed to allocate device.

As a test tried in 6.0. The adapter works but only 2.4Ghz wifi is found.

A further test in 7.0.0a1. The adapter works i.e. 5Ghz wifi is the band I want.

I have done a lsmod and in each version the modules loaded seem to be the same in all three versions.

Given that I do not want to change from 5.2.8 my questions are:

1. Why isn't the adapter even seen in 5.2.8?

2. What does the dmesg output mean and how to rectify?

3. As part of my learning curve what determines the bands to be scanned?

bigpup · #2 Post by **bigpup** » Wed 24 Jul 2019, 08:55

It is not even seen in 5.2.8 frugal install network wizard

I assume 5.2.8 is some Puppy Linux version.
What is the exact complete name?

In the Puppy version that has everything working.
menu>System>Pup-Sysinfo>Devices>Network

Post the information it shows.

Mercedes350se · #3 Post by **Mercedes350se** » Thu 25 Jul 2019, 02:35

bigpup wrote:I assume 5.2.8 is some Puppy Linux version.
What is the exact complete name?

5.2.8 = Lucid

bigpup wrote:In the Puppy version that has everything working.
menu>System>Pup-Sysinfo>Devices>Network

Post the information it shows.

This is with the adapter plugged into 7.0.0a1:

Code: Select all

====> Network Devices <====

Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)
+ Kernel Driver: r8169
+ Memory Used: 60.94 KB
+ Path: /lib/modules/4.1.38/kernel/drivers/net/ethernet/realtek/r8169.ko
+ Driver Version: 2.3LK-NAPI
+ Description: RealTek RTL-8169 Gigabit Ethernet driver
--
USB network adapter : 802.11 n WLAN

With the adapter plugged into 5.2.8 I get:

Code: Select all

sh-4.1# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0001
Bus 004 Device 001: ID 1d6b:0001
Bus 005 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 007 Device 001: ID 1d6b:0001
Bus 008 Device 001: ID 1d6b:0001
Bus 001 Device 002: ID 05dc:a768
Bus 002 Device 002: ID 148f:3572  < This is the adapter.
Bus 002 Device 003: ID 13fe:4100
Bus 005 Device 002: ID 03f0:0024
Bus 005 Device 003: ID 15d9:0a33

Code: Select all

sh-4.1# lsmod
Module                  Size  Used by
<snip>
rt2800usb               8347  0 
rt2800lib              17097  1 rt2800usb
rt2x00usb               5331  2 rt2800usb,rt2800lib
rt2x00lib              18100  2 rt2800lib,rt2x00usb
led_class               1733  1 rt2x00lib
mac80211               99898  2 rt2x00usb,rt2x00lib
cfg80211               90319  2 rt2x00lib,mac80211
crc_ccitt               1011  1 rt2800usb
<snip>
usbcore                91279  7 rtl8187,rt2800usb,rt2x00usb,usbhid,usb_storage,uhci_hcd,ehci_hcd

bigpup · #4 Post by **bigpup** » Thu 25 Jul 2019, 09:53

Code: Select all

====> Network Devices <====

Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)
+ Kernel Driver: r8169
+ Memory Used: 60.94 KB
+ Path: /lib/modules/4.1.38/kernel/drivers/net/ethernet/realtek/r8169.ko
+ Driver Version: 2.3LK-NAPI
+ Description: RealTek RTL-8169 Gigabit Ethernet driver
--

This is the Ethernet controller info.
We need the WIFI adapter info from the working Puppy version.

Mercedes350se · #5 Post by **Mercedes350se** » Fri 26 Jul 2019, 01:23

bigpup wrote:We need the WIFI adapter info from the working Puppy version.

It is only the one line at the bottom of my post above i.e.

Code: Select all

USB network adapter : 802.11 n WLAN

EDIT: "One small step for (this) man".

Extensive reading lead me to believe that the driver being loaded was not actually correct for the adapter - so:

Load on the fly:

kernel_src_L4-2.6.33.2-patched.sfs, and
lupu_devx_528-4.sfs

Downloaded DPO_RT5572_LinuxSTA_2.6.1.3_SparkLAN.tar.gz to /opt/3572
Unzipped and go to DPO_RT5572_LinuxSTA_2.6.1.3_SparkLAN

Amended the Make file as outlined in the README_STA_usb file.

Confirmed /os/linux/config.mk had the WPA lines were "=y"

Back out to the DPO_RT5572_LinuxSTA_2.6.1.3_SparkLAN directory

make

which took surprising little time.

Then in /etc/udev/rules.d created a file

geany network_drivers.rules

In this file:

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="148f", ATTR{idProduct}=="3572", RUN+="/sbin/modprobe -qba rt3572sta"

Then in /etc/modprobe.d created a file

geany network_drivers.conf

In this file:

install rt3572sta /sbin/modprobe --ignore-install rt3572sta $CMDLINE_OPTS; /bin/echo "148f 3572" > /sys/bus/usb/drivers/rt3572/new_id

Shut down and rebooted.

The Network Wizard now has a ra0 entry. Configure it and am posting this with the adapter.

How much of the latter part of the above is actually required I do not know.

There is the same problem as in puppy 6.0 in that it only finds 2.4GHZ wifi.

EDIT 2:

Euphoria was short lived. It dis not survive a cold boot. I have blacklisted the rt2800usb module but no difference.

Mercedes350se · #6 Post by **Mercedes350se** » Fri 26 Jul 2019, 07:39

Code: Select all

sh-4.1# modprobe -v rt3572sta
install /sbin/modprobe --ignore-install rt3572sta ; /bin/echo "148f 3572" > /sys/bus/usb/drivers/rt3572/new_id
FATAL: Module rt3572sta not found.
sh: /sys/bus/usb/drivers/rt3572/new_id: No such file or directory
FATAL: Error running install command for rt3572sta

Obviously I need to attend Compiling 101.

The question is, "What do I need to do to correctly compile the driver?"

bigpup · #7 Post by **bigpup** » Fri 26 Jul 2019, 09:46

You found the driver package I was going to suggest or a similar one. Anyway, it seems to have the needed driver and firmware.

You said it worked.
So compiling seems to not be the problem.

Euphoria was short lived. It dis not survive a cold boot.

Lucid 528 is a frugal install and a frugal install uses a save file or folder to store any changes, additions, etc.......

So, the question is why it did not get into the save?
When you shutdown Lucid 528, the save should be getting updated.

In Pup-Sysinfo>Sys-files>PupState

Post the info at the top that shows pupmode.
Example:
This is my setup.

Code: Select all

▶—— /etc/rc.d/PUPSTATE ——◀

 • PUPMODE=13
 • PDEV1='sda1'
 • DEV1FS='ext3'
 • PUPSFS='sda1,ext3,/bionicpup6480uefi/puppy_bionicpup64_8.0.sfs'
 • PUPSAVE='sda1,ext3,/bionicpup6480uefi/bionicpup64save'
 • PMEDIA='usbflash'

This will show a lot of info on how you have Lucid 528 installed and how the save should be used.

Mercedes350se · #8 Post by **Mercedes350se** » Sat 27 Jul 2019, 03:01

bigpup wrote: In Pup-Sysinfo>Sys-files>PupState

Post the info at the top that shows pupmode.

5.2.8 does not have that menu.

I am not concerned with the save file - it seems to save through the session. Well has in the past anyway!

I have managed to break something so I have to start again. Replacing the save file with a "pristine" one is a huge advantage of a frugal install!!!!!!!!

My problem is with the driver - compile it properly and place it in the correct location, etc.

Thanks for hanging in there ...

Mercedes350se · #9 Post by **Mercedes350se** » Tue 30 Jul 2019, 01:26

Mercedes350se wrote:My problem is with the driver - compile it properly and place it in the correct location, etc.

I have found another source of the 3572 driver - might just as well have the driver for the chipset in the adapter - and it seems to compile.

However when I do a modprobe rt3572sta - even when I am in the directory containing the module - I get a module not found message.

Hmm.

perdido · #10 Post by **perdido** » Tue 30 Jul 2019, 19:01

Hi Mercedes350se,

You might try the drivers at the backports project
https://backports.wiki.kernel.org/index.php/Main_Page

Download page for compatible up to the 3.10 kernel
https://backports.wiki.kernel.org/index.php/Releases
These are not huge downloads, the one I checked was under 10MB
There are 5 seperate archives representing 5 different periods of developement for the drivers.
The archives have a variety of source code representing multiple wifi cards and manufacturers.

There are 5 downloads representing different progressive updates of the drivers. You may end up checking all 5 archives and still not get 5G but won't know until you try. The RT drivers are closed source
and were not supported by the manufacturer in Linux. These are the open source drivers and may or may not work depending on developement. All 5 archives may support your card though I only looked
at the contents of the first archive (backports-5.1-rc2-1.tar.xz) and it indicated the 3572 was experimental in that package, the other later archives will be further developed.

The driver you would be interested in is the rt2x00 package. That is the same driver as the working 2800 driver in your 7.0.0a1 test.

It should compile similar to packages you have already compiled/tested.

After downloading and extracting the archive the driver package should be located in
/drivers/net/wireless/ --->rt2x00

Good luck!

EDIT: If none of those archives suffice you can look at older backport archives here that cover 2013 to 2019
https://cdn.kernel.org/pub/linux/kernel ... ts/stable/

.

perdido · #11 Post by **perdido** » Tue 30 Jul 2019, 19:11

Hi Mercedes350se,

Adding this seperate post to keep it less confusing.
There is source at github also, later source that I cannot determine if it supports your card.

Since it is later it should.
Located here
https://github.com/oja/rt2800usb

Even though your chip is not specifically listed in chips I believe it may work.
The sources were developed until Nov, 2015

EDIT: One more here
https://github.com/AlexisTM/RT-WiFi/tre ... t/wireless.

----------------------
One other way may be to try ndiswrapper with the windows driver.
ndiswrapper is used for loading windows network drivers in linux.

-----

One other thought.
The firmware may be different (newer) in the stretch 7.0.0a1 than what is in Lupu 5.2.8
The firmware for the rt28x00 driver is named rt2870.bin
Might try replacing the rt2870.bin in Lupu 5.2.8 with the firmware from stretch 7.0.0a1 when testing the rt28x00 driver.
/lib/modules/all-firmware/ or lib/modules/firmware/ should be where the firmware is located

Have fun!

.

Mercedes350se · #12 Post by **Mercedes350se** » Thu 01 Aug 2019, 03:27

I have tried a few of those links without success.

The current one returns:

Code: Select all

sh-4.1# make
make: *** No targets.  Stop.

I assume I have to add something to the Kconfig and/or the Makefile but what? The 'net is silent on the matter!

perdido · #13 Post by **perdido** » Thu 01 Aug 2019, 08:22

Mercedes350se wrote:I have tried a few of those links without success.

The current one returns:
Code: Select all
sh-4.1# make
make: *** No targets.  Stop.
I assume I have to add something to the Kconfig and/or the Makefile but what? The 'net is silent on the matter!

I just looked at those archives, the source doesn't have a configure script.
Usually you run ./configure to create the makefile
So those can't be used if the existing makefile is wrong for the compiler.

Here is a good article about the makefile and configure.
https://thoughtbot.com/blog/the-magic-b ... ke-install
--------------------------------------
This driver may work for your wifi in Lucid 5.2.8, its a small download at 300k
https://archive.org/download/Puppy_Linu ... 6.33.2.pet

The naming conventions used on the ralink wifi drivers is confusing for identifying
exactly which chips they support. At least to me.

.

Mercedes350se · #14 Post by **Mercedes350se** » Fri 02 Aug 2019, 08:42

Found another driver. At least there is a readme with it!

Code: Select all

sh-4.1# make
make -C tools
make[1]: Entering directory `/opt/3572_2/rt3572sta-master/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/opt/3572_2/rt3572sta-master/tools'
/opt/3572_2/rt3572sta-master/tools/bin2h
cp -f os/linux/Makefile.6 /opt/3572_2/rt3572sta-master/os/linux/Makefile
make -C /lib/modules/2.6.33.2/build SUBDIRS=/opt/3572_2/rt3572sta-master/os/linux modules
make[1]: Entering directory `/usr/src/linux-2.6.33.2'
make[1]: *** No rule to make target `modules'.  Stop.
make[1]: Leaving directory `/usr/src/linux-2.6.33.2'
make: *** [LINUX] Error 2

Oh dear.

Mercedes350se · #15 Post by **Mercedes350se** » Sat 03 Aug 2019, 08:25

Another day, another attempt!

Code: Select all

sh-4.1# make
make -C tools
make[1]: Entering directory `/opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/tools'
/opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/tools/bin2h
cp -f os/linux/Makefile.6 /opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/Makefile
make -C /lib/modules/2.6.33.2/build SUBDIRS=/opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux modules
make[1]: Entering directory `/usr/src/linux-2.6.33.2'
  CC [M]  /opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/../../common/rtmp_mcu.o
  LD [M]  /opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/rt3572sta.o
  Building modules, stage 2.
  MODPOST 1 modules
  LD [M]  /opt/2800/2011_0427_RT3572_Linux_STA_v2.5.0.0.DPO/os/linux/rt3572sta.ko
make[1]: Leaving directory `/usr/src/linux-2.6.33.2'
sh-4.1#

and then:

Code: Select all

sh-4.1# modprobe rt3572sta.ko
FATAL: Module rt3572sta.ko not found.
sh-4.1#

Totally confused.

bigpup · #16 Post by **bigpup** » Sat 03 Aug 2019, 11:16

Have you tried using the pet that perdido posted about?
https://archive.org/download/Puppy_Linu ... 6.33.2.pet

Mercedes350se · #17 Post by **Mercedes350se** » Mon 05 Aug 2019, 02:00

Yes. That was the easy way - unfortunately it only created the 5572 module so no go.

Mercedes350se · #18 Post by **Mercedes350se** » Thu 08 Aug 2019, 00:58

Several days and more attempts later still no working driver.

I think I will take the soft option and do a frugal install of 5.7.1 - the adapter works OOTB!

Only an hour or two customisation to make it the way I want!!!

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Fenvi FV-N700 dual-band wifi adapter not seen by Lucid Puppy

Fenvi FV-N700 dual-band wifi adapter not seen by Lucid Puppy