@aus9 If you could tell me exactly what you are talking about and how to do it I'm willing to try it. It's not like it's hard to get porteus installed again in case something goes wrong.
Sure let me try again.
Some kernels such as old kernels do not have support for your dongle and so you need to download the driver
compile and install it.....and it may also need firmware in compiling which also has to be installed.
my quote box says that there is a new kernel module in more recent kernels from series v 4.2 or higher and the kernel module name has changed from what donald and myself had previously written......and the name of the module already included in v 4.2 or higher is
mt7601u
The mt is an abbreviation of mediatek which is a chipset maker that may have taken over that Ralink ?
Now I offered previously 2 choices.....either with the Porteus/Slackware you install the neko kernel or you try a download of Nemesis.
As I am on Nemesis at I type here is that location of brokenman's kernel module
Code: Select all
sudo find / -name mt7601u
[sudo] password for guest:
/mnt/live/memory/images/000-kernel.xzm/usr/lib/modules/4.3.3-porteus/kernel/drivers/net/wireless/mediatek/mt7601u
/usr/lib/modules/4.3.3-porteus/kernel/drivers/net/wireless/mediatek/mt7601u
If you were to download umm the 64 bit distro of Nemesis and reboot with dongle already inserted the module should autoload and showup in lsmod command or you can load it manually if it does not.
Now does new kernel need firmware?
I use a 64 bit distro and looking at /usr/lib/firmware I can see NO mediatek dir and no firmware at the root of that foldername
I could be wrong but I am suggesting move to 4.2 or higher kernel and your problems should dissolve because you won't need to compile anything
neko
neko has provided updated kernels for those who still prefer to stay with Porteus/Slackware
I have not tried it myself but many have and the page to read starts here
viewtopic.php?f=75&t=4788&hilit=upkernel4.3
edit 1
But I have not asked or looked at neko's config file to see if he has built that module name in the quote box into his kernel
edit 2
At first glance neko kernel has same config as Official Porteus so unlikely to have new module compiled so Nemesis might be the answer after all?
I have posted to link to confirm his config
Is that clearer?