Leanest option for 32 bit machines?

Post#16 by **pneilson** » 04 Apr 2023, 14:04

@Ed_P

Okay, thank you for your help, I sure appreciate it. I find those same *.ko files in my system in /kernel/drivers/net/wireless/ralink/rt2x00/ and when I run them through modinfo I see the same .bin files listed but no other output. If there was a driver there, what would it look like? Would it have a particular file extension, or would it be a set of files? I'm assuming that it would be something like the iwlwifi.ko file that I ran in the first set of commands that returned all of those .ucode files.

Just to clarify, you are thinking that my system is using a wifi driver (otherwise how could it connect to the wifi network in the first place), but it's not using the Ralink driver because there is not one there. Which is probably what is causing the poor connection, it's using a driver that is not designed for the Ralink hardware. But we don't know what that driver is, or which wifi module my system is currently using. Is this correct?

If that is correct, would it be better to 1) find out the wifi module my system is currently using and update the driver in it or 2) find a Ralink driver and put it in /kernel/drivers/net/wireless/ralink? Or are both of those complete nonsense - I definitely am way past my comfortable level of understanding.

At this point I am mostly just pursuing this because I'm very much a Linux beginner (been using it for years, but always in Ubuntu flavors that did almost everything for me) and it's a chance for me to learn.

Again, many thanks.

Post#17 by **beny** » 04 Apr 2023, 15:55

hi the porteus5 32 bit kernel have all you need to connect with your device,this is a report of an user: take a look at depend list of modules you have to load all this first of this one and you have also the firmware rt2800.bin,you have to see the rfkill report on terminal maybe your wifi is blocked, the eeprom adress: /modules/5.18.8-porteus/kernel/drivers/misc/eeprom/eeprom_93cx6.ko when you have to load the kernel module in terminal: insmod path of the .ko
# lspci -k
...
24:00.0 Network controller: Ralink corp. RT3592 Wireless 802.11abgn 2T/2R PCIe
Subsystem: Hewlett-Packard Company Device 1638
Kernel driver in use: rt2800pci
Kernel modules: rt2800pci

Code: Select all

   bash-5.2# modinfo /root/Scaricati/squashfs-root/lib/modules/5.18.8-porteus/kernel/drivers/net/wireless/ralink/rt2x00/rt2800pci.ko
filename:       /root/Scaricati/squashfs-root/lib/modules/5.18.8-porteus/kernel/drivers/net/wireless/ralink/rt2x00/rt2800pci.ko
license:        GPL
firmware:       rt2860.bin
description:    Ralink RT2800 PCI & PCMCIA Wireless LAN driver.
version:        2.3.0
author:         http://rt2x00.serialmonkey.com
srcversion:     65B0FCEACCA142AECED1C40
alias:          pci:v00001814d0000539Fsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Bsv*sd*bc*sc*i*
alias:          pci:v00001814d0000539Asv*sd*bc*sc*i*
alias:          pci:v00001814d00005392sv*sd*bc*sc*i*
alias:          pci:v00001814d00005390sv*sd*bc*sc*i*
alias:          pci:v00001814d00005362sv*sd*bc*sc*i*
alias:          pci:v00001814d00005360sv*sd*bc*sc*i*
alias:          pci:v00001814d0000359Fsv*sd*bc*sc*i*
alias:          pci:v00001814d00003593sv*sd*bc*sc*i*
alias:          pci:v00001814d00003592sv*sd*bc*sc*i*
alias:          pci:v00001814d00003562sv*sd*bc*sc*i*
alias:          pci:v00001814d00003062sv*sd*bc*sc*i*
alias:          pci:v00001814d00003060sv*sd*bc*sc*i*
alias:          pci:v00001432d00007722sv*sd*bc*sc*i*
alias:          pci:v00001432d00007711sv*sd*bc*sc*i*
alias:          pci:v00001814d00003390sv*sd*bc*sc*i*
alias:          pci:v00001814d00003290sv*sd*bc*sc*i*
alias:          pci:v00001A3Bd00001059sv*sd*bc*sc*i*
alias:          pci:v00001462d0000891Asv*sd*bc*sc*i*
alias:          pci:v00001432d00007768sv*sd*bc*sc*i*
alias:          pci:v00001432d00007758sv*sd*bc*sc*i*
alias:          pci:v00001432d00007748sv*sd*bc*sc*i*
alias:          pci:v00001432d00007738sv*sd*bc*sc*i*
alias:          pci:v00001432d00007728sv*sd*bc*sc*i*
alias:          pci:v00001432d00007727sv*sd*bc*sc*i*
alias:          pci:v00001432d00007708sv*sd*bc*sc*i*
alias:          pci:v00001814d00003092sv*sd*bc*sc*i*
alias:          pci:v00001814d00003091sv*sd*bc*sc*i*
alias:          pci:v00001814d00003090sv*sd*bc*sc*i*
alias:          pci:v00001814d00000781sv*sd*bc*sc*i*
alias:          pci:v00001814d00000701sv*sd*bc*sc*i*
alias:          pci:v00001814d00000681sv*sd*bc*sc*i*
alias:          pci:v00001814d00000601sv*sd*bc*sc*i*
depends:        rt2x00lib,rt2800lib,rt2800mmio,rt2x00mmio,rt2x00pci,eeprom_93cx6
retpoline:      Y
intree:         Y
name:           rt2800pci
vermagic:       5.18.8-porteus SMP preempt mod_unload 686 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        17:F0:57:24:C1:0E:A8:C4:2D:26:B7:7E:74:6A:8C:24:15:A6:C6:8E
sig_hashalgo:   sha1
signature:      84:54:BE:F1:ED:B4:99:9A:B7:74:F1:1D:18:B2:ED:7F:CF:23:A6:33:
		75:B8:57:F6:B0:33:FC:11:0B:8A:98:62:63:F1:87:D6:A7:29:23:CE:
		40:6C:0B:31:59:31:9F:03:A7:9C:AB:EB:BB:9B:D8:B8:81:9F:94:60:
		EE:43:14:87:C0:DA:CB:53:9E:45:81:66:D7:06:57:68:2A:A0:50:99:
		15:EB:01:57:C9:E1:8E:3C:3C:09:19:87:F0:95:EB:A2:3A:00:4E:B2:
		41:7B:11:98:F6:01:1D:18:27:D3:19:E6:D4:01:52:F2:CC:D6:99:22:
		71:C9:54:BF:A2:5F:17:AF:75:DB:1A:F2:9B:89:54:DC:78:63:9E:7C:
		EF:5D:1B:34:31:27:00:03:DB:CC:BA:C6:CA:CD:DB:84:BB:59:8E:AA:
		45:4F:4B:41:D0:79:75:B2:4B:43:B4:C6:66:86:32:32:11:38:D5:85:
		C6:74:12:98:8A:F6:8E:EF:B5:F9:7C:88:41:AD:2A:6F:5D:B3:DB:DB:
		0A:6D:C3:AE:9A:FD:BD:46:5A:C7:23:93:D2:2A:D2:0B:2D:6A:56:FE:
		6A:8D:A2:D3:CA:71:CF:6D:F3:DA:D6:D2:F5:4F:90:75:86:27:91:82:
		B2:E9:C5:22:40:F3:D7:54:F8:E1:77:FF:34:9E:18:ED:D0:27:FD:AE:
		68:E3:1F:8F:7C:34:5A:05:55:02:8C:AD:11:7A:55:62:13:16:2A:B4:
		FF:D3:75:BB:6A:6A:3F:90:FB:C5:61:41:7F:28:38:60:70:2C:19:5D:
		4E:74:58:47:8F:D9:0E:D3:D1:F1:30:A6:AA:D8:77:8C:ED:60:1C:AD:
		1A:3A:E4:47:1E:7D:38:EE:80:0B:8B:47:37:60:AD:F8:20:31:82:2C:
		75:FA:6B:90:A3:8E:7F:16:CB:07:F3:51:23:D2:3F:6E:91:28:BE:56:
		15:5E:40:76:02:25:FD:0D:64:60:8B:8A:44:09:52:1E:B1:1F:84:4E:
		6D:34:B7:31:40:DF:5B:BE:1E:EC:AF:17:8C:3E:45:49:C9:CC:B5:E5:
		06:73:C2:BB:25:6D:B8:DF:60:A3:15:4C:5D:FF:40:64:27:3B:6C:B2:
		68:B5:5F:C0:8E:A9:48:BB:3E:F1:D0:82:C9:72:73:A3:0A:74:F2:C7:
		58:92:4D:FF:E6:4F:DC:31:C9:86:F3:28:0E:CF:C8:BA:45:04:11:AC:
		3F:04:5B:83:A7:CB:22:F7:4A:B1:53:2A:36:FE:1D:A5:9B:55:46:0B:
		EB:02:43:9E:5D:94:BB:11:0E:2C:CF:92:E3:6E:DB:C9:60:23:2C:5A:
		20:DB:BA:05:47:72:05:A7:2D:DC:5D:13
parm:           nohwcrypt:Disable hardware encryption. (bool)
bash-5.2#

Post#18 by **Ed_P** » 04 Apr 2023, 18:24

pneilson wrote: ↑

03 Apr 2023, 19:09

Code: Select all

root@porteus:/home/guest# dmesg | egrep 'ucode|firmware|fail|error|wifi'
[   10.105292] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   10.105311] cfg80211: failed to load regulatory.db

I wonder if this .db error is contributing to the slow speeds.

Added in 5 hours 31 minutes 57 seconds:
So beny what does pneilson have to do to get his modinfo report to match your's?

Post#19 by **pneilson** » 05 Apr 2023, 03:51

@beny

Here is the rfkill report

Code: Select all

root@porteus:/home/guest# rfkill
ID TYPE      DEVICE            SOFT      HARD
 0 wlan      hp-wifi      unblocked unblocked
 1 bluetooth hp-bluetooth unblocked unblocked
 2 wlan      phy0         unblocked unblocked
 3 bluetooth hci0         unblocked unblocked

I'm not sure I quite understood your other directions. I did find eeprom_93cx6.ko in /modules/5.18.8-porteus/kernel/drivers/misc/eeprom/ I tried to run the insmod command I think you were telling me and here is what I got:

Code: Select all

root@porteus:/home/guest# insmod /lib/modules/5.18.8-porteus/kernel/drivers/misc/eeprom/eeprom_93cx6.ko
insmod: ERROR: could not insert module /lib/modules/5.18.8-porteus/kernel/drivers/misc/eeprom/eeprom_93cx6.ko: File exists

Did I do it wrong? Thanks!

Post#20 by **pneilson** » 05 Apr 2023, 03:53

@Ed_P

Ed_P wrote: ↑
04 Apr 2023, 23:56
I wonder if this .db error is contributing to the slow speeds.

If that regulatory.db file is failing to load, does that mean it's missing? Or that it was looking for firmware and couldn't find it?

Post#21 by **Ed_P** » 05 Apr 2023, 05:23

pneilson wrote: ↑
05 Apr 2023, 03:53
If that regulatory.db file is failing to load, does that mean it's missing?

That would be my interpretation. The question is where can you get it.

This is what my system shows for rfkill.

Code: Select all

root@porteus:/home/guest# rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 bluetooth hci0   unblocked unblocked
 1 wlan      phy0   unblocked unblocked
root@porteus:/home/guest#

Post#22 by **beny** » 05 Apr 2023, 10:29

hi you have all into the modules/5.18.8-porteus/kernel/drivers/net/wireless/ralink/rt2x00 if you have the file exist that is ok the module is loaded by system you have to load the modules listed in depends line if you active the changes save mode when you reboot you have all working, if you receive a warning for a module,you can see what is missed with modinfo

Post#23 by **roadie** » 05 Apr 2023, 19:20

pneilson wrote: ↑
05 Apr 2023, 03:53
@Ed_P

Ed_P wrote: ↑
04 Apr 2023, 23:56
I wonder if this .db error is contributing to the slow speeds.
If that regulatory.db file is failing to load, does that mean it's missing? Or that it was looking for firmware and couldn't find it?

I've seen that error in every Porteus install that I've done, it has no effect on my wireless connection. I believe it has something to do with country codes, or some such. I ignore it.

I suggest checking the log files, possibly the device is dropping the connection:

Code: Select all

cat /var/log/messages | grep wlan0

You should see it associating and then associated after it connects. If it's dropping the connection, it should show that as well.

If you feel the need to update, I'd download the updates manually and move them into the appropriate Porteus install folders. It's very unlikely to help with the wireless situation though.

Post#24 by **Blaze** » 06 Apr 2023, 14:33

Hi pneilson.
How about to try to update kernel to 6.2.10 from this post Porteus Kernel Builder (Пост Blaze #93655) ?

Code: Select all

# All operations should be performed as root user!

# replace 000-kernel.xzm
# remove crippled_sources.xzm
# add 06-crippled_sources-NNN-XXbit.xzm
/path-to/porteus/base

# replace vmlinuz
/path-to/boot/syslinux

# restart porteus

Note. You can do this via terminal, for example
Code: Select all
su
toor
# run Midnight Commander
mc
# and repeat steps above

After reboot open terminal and share log of these commands:

Code: Select all

uname -r
dmesg

Thanks.