JhonScript
-
Posts
88 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JhonScript
-
-
On 9/30/2023 at 3:30 AM, scolcipitato said:
New version out: 2023.09.30
Changelog:
- Added custom events, go to the edit/ add page to get started.
- Updated EN and IT translation for the new version, @kennymc.c I've already added the new lines to the DE translation you just need to translate if you want.
- Changed the custom CSS import method (here you can find the post I talked about it, if the custom CSS is not working after the update just rename some file according and everything will work as before).
- Added custom scripts event, you can read about it in the dev guide on GH (link in the first post).
- Bringed VM tab to par with docker functionality where possible.
- Updated dev guide and templates.
Hello @scolcipitato, thank you very much for the update, regarding the execution of User-Scripts, I had not been able to write, since until today I managed to catch up with the forum posts. I tried to get the user scripts to work, and it didn't work, until I read the Javascript script code at line 1007 of the file "usr/local/emhttp/plugins/folder.view/scripts /dashboard.js", where it indicates that only the script name of the "User Script" plugin should be entered, I like it much better this way. However, when adding the script it is not clear that only the plugin script name "User Script" should be entered.
Additionally, I would like to ask you the favor of correcting the edit scripts button, since when you click it, it redirects to the last page before entering to edit the Folder
I use Google Chrome
My intuition says that the error may be on line 322 of the file usr/local/emhttp/plugins/folder.view/scripts /folder.js "config.conatiners"
Additionally I see that by correcting this error it would only work for containers, I don't know what needs to be done to make it work on virtual machines
-
4 hours ago, scolcipitato said:
Nunca lo usé, así que no sabía cómo funcionaba, así que no lo he incluido.
Puedo intentar integrar el complemento de secuencia de comandos de usuario y agregar botones en el menú contextual.
Nuevamente, no sé si así es como funcionaba antes, pero hay que esperar. Estoy trabajando en el contexto avanzado para la ventana acoplable, así que lo integraré con esa actualización.
Thank you very much, how can I help? Do you have questions about how it worked?
-
Hello, thank you very much for working on this plugin. This was the reason I didn't want to upgrade from 6.11.5 to 6.12.3.
However, I read all 8 pages on this topic and didn't see anyone mention the ability to run scripts (it seems only I used it XD).
img from sonic6
My use case is running scripts, as I currently have 4 miners working (2 trex miners, which take up my graphics cards) (2 xmr miners, which take up my processor cores).
The thing is that when I want to play with my virtual machine, I have to stop one of the trex miners and one of the xmr miners, so that it frees up resources for my virtual machine, the same thing happens when my nephew wants to play in his virtual machine.
likewise when we stop playing we turn off the virtual machines, the miners start automatically... this is a separate topic but I like to mention it so that they have the context.
All this is done by scripts from the "User Scripts" plugin.
Similarly, with the old plugin you could do all of this, including running mining related scripts. like stop the activation of the 4 miners or start it. therefore, the scripts were executed as buttons in dockers and in the virtual machine.
Thanks if you can confirm if you plan to work on this and if I can help you in any way.
I leave you the screenshots related to this topic since I am a person who understands through images.
Also, I wanted to mention that in the old plugin you could decide which buttons (Start, Stop, Pause, Force) you could activate and which ones you couldn't. For example, I only had the force and stop buttons active, since the start button was executed through the script
-
This plugin allows me to run scripts on the dashboard to stop the miners using the GPU and start my virtual machines so I can play. I hope you can work on making this new plugin usable with version 6.12.2.
I don't know if it's just me with the problem, since the plugin works fine from the Dockers and VMs page, but the most I use it is from the Dashboard page.
-
-
Hello, I made a change in the virtual machine configuration that asked me to reboot, but the operating system did not work again, therefore I had to reinstall unraid, but when I activate my license I get the following error:
the image is edited
I wrote an email to
but i received the following mail:
What is the correct way to contact support?
-
It also changed the PCIe ACS override to "Both" and generated this
Can you think of any way that when connecting a usb device, it connects to the GPUs? in order to achieve the passthrough
-
On 2/14/2023 at 4:13 PM, Skitals said:
So unfortunately no way to make use of it. Best practice is still to passthrough all sub-devices together with multifunction on (54:00.0, 54:00.1, 54:00.2, 54:00.3 on the same bus, etc). Typically they would be in the same iommu group, what do your groups look like with acs overrides disabled?
Hi this looks like this
-
The solution for me was to edit the docker and set it as follows
it worked
-
1
-
-
On 1/15/2020 at 11:22 PM, Skitals said:
It now shows USB devices attached to each controller. If a USB controller is bound to vfio, the USB devices will not be visible.
Hello, I would like to understand what this means in other words? I don't know if you can help me with my case.
I have two GPUs (TUF-GTX1660S), and in SysDevs this appears, my Motherboard is b550 Vision D
My GPU does not have any USB c or USB 3.1 port
My Motherboard does have a usb c port and usb 3.1 ports
The first question is because this text appears "This controller is linked to vfio, the connected USB devices are not seen", this means that if I managed to connect a usb, and if I have made a passthrough from the GPU to the VM, the usb will it connect directly to the VM and not be seen on the Unraid server?
The second question is, because my GPU indicates that it has a USB 3.1 and USB c controller, if it does not have any physical port, is there an adapter to convert HDMI to USB?
https://www.amazon.com/Adapter-Converter-Thunderbolt-MacBook-Microsoft/dp/B08VDT3YGK
https://www.amazon.com/ELUTENG-Thunderbolt-Compatible-Converter-Connector/dp/B07Z4G911X
-
Hello, I would like to know if anyone has managed to earn money by renting their available disk space.
I know there are several DSN (Decentralized Storage Network) solutions. I want to contribute to PermaWEB (https://arweave.medium.com/welcome-to-the-permaweb-ce0e6c73ddfb) and It is part of the ARWeave network (https://arweave.medium.com/what-is-arweave-explain-like-im-five-425362144eb5)
This is the documentation to perform the best "Mining" that they have managed to create, in ARWeave it is not a waste of energy to find a random number, since the objective is to store data forever.
It is a utopia, and I believe that an impressive network can be formed with the UNRAID community.
https://docs.arweave.org/info/mining/mining-guide
Also, I found someone who generated a docker for this miner, however it doesn't seem to be maintained and a new version of ARWeave already exists.
https://github.com/rafaelzimmermann/arweave-miner/blob/master/Dockerfile
https://github.com/ArweaveTeam/arweave/releases
-
Make sure when configuring the virtual machine the BIOS is set like this
-
Did you manage to install OSSIM on an Unraid(KVM) virtual machine?
-
Last night I updated to version 6.10.1 and I have the same problem.
I did an installation from scratch since the xmr miner was giving me a problem that it could not find the path /dev/
https://github.com/P3R-CO/openrgb-container/blob/master/README.md
-
+1
-
I tell you that during the day I did the following:
PCIe ACS override: Multi-function
I removed bluetooth.conf file from path /boot/config/modprobe.d/
I created a new virtual machine with O.O Kali Linux and just passed the WiFi device which was marked for VFIO on boot
QuoteNOTE: With the creation of a new machine we would discard all the configurations that were made within the virtual machine
Everything works within Kali.
The image is edited
QuoteThe screenshots show that the bluetooth (Intel Corp. (8087:0029)) is not found, but I already verified that I can associate it to the virtual machine without having to associate the entire IOMMU group or another different device
$ sudo iwconfiglo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11 ESSID:"MyESSID" Mode:Managed Frequency:2.437 GHz Access Point: FF:FF:FF:00:00:00 Bit Rate=52 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=70/70 Signal level=-20 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:7 Missed beacon:0$ rfkillID TYPE DEVICE SOFT HARD 0 wlan phy0 unblocked unblocked$ sudo dmesg | grep iwl[ 8.558540] iwlwifi 0000:03:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 8.558554] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 8.561580] iwlwifi 0000:03:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode [ 8.561598] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver [ 8.561614] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 8.561936] iwlwifi 0000:03:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm [ 8.561970] iwlwifi 0000:03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 8.691723] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 8.826471] iwlwifi 0000:03:00.0: Detected RF HR B3, rfid=0x10a100 [ 8.894397] iwlwifi 0000:03:00.0: base HW address: 00:00:00:FF:FF:FFQuoteWith the dmesg output message, in this installation you can see that part of the firmware 64. It should be noted that this installation is with the ISO "kali-linux-2021.4a-installer-amd64.iso", the iso of the previous tests was "kali-linux-2022-W06-installer-amd64.iso"
$ cd /lib/firmware/ $ ls
QuoteNOTE: In this installation I did not copy any file, and it is observed that there is firmware from 46 (this is the firmware of the WiFi 6 ax200 card) to firmware 63, which is the one that is shown loaded in the output messages of the "dmesg" command.
So far the solution seems to have been:
1. Changed USB port to UNRAID OS Bootable USB
2. have gone through the process of shutting down the physical machine and disconnecting it from power for 2-3 minutes
3. have booted the physical machine and run the Kali Linux virtual machine without running any other virtual machines that make use of the WiFi device
I'm guessing you also need to have Fastboot disabled in the BIOS of the physical machine. (In my case it was always disabled)
In the next few days I will rule out the need to move the UNRAID OS boot usb to another USB port.
I don't know if I missed something we did. but I think that would be the summary until I drop point number 1, God willing
.
-
7 hours ago, ghost82 said:
Devices like this have the firmware loaded in the device ram during boot, if a wrong firmware is wrongly loaded you may need to power cycle it to be able to load another firmware on it.
this makes sense, regarding the procedure of turning off and disconnecting the power supply from power.
7 hours ago, ghost82 said:If you stick with the "firmware renamed solution", remember that if you update the linux-firmware package (if you have it installed), your renamed firmware could be overwritten (replaced with the real a0-66) and your wifi won't work again, if it will be the case, just repeat the steps you did.
Got it, I'm going to work on that solution today.
I will also confirm that the VFIO process is completely necessary.
Thank you very much for everything, really.
-
after doing this.
40 minutes ago, JhonScript said:Rename file 46 to 66 and copy file "66" to /lib/firmware folder, run dmesg command and get this output
i did this again, step by step
5 hours ago, ghost82 said:That's really strange
Shutdown your pc.
Boot to your pc bios (not the vm bios), disable fast boot if it's enabled and apply changes, shutdown.
Unplug power chord and wait 2-3 minutes.
Boot unraid and run the linux vm, do not start any windows vm before.
See if you get wifi.
The image is edited, it is working correctly.
$ rfkillID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked 1 wlan phy0 unblocked unblocked$ iwconfiglo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11 ESSID:"EXAMPLE" Mode:Managed Frequency:2.437 GHz Access Point: FF:FF:FF:00:00:00 Bit Rate=26 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=70/70 Signal level=-24 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:7 Missed beacon:0sudo dmesg | grep iwl[ 3.970022] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-66.ucode [ 3.970035] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM [ 3.970036] iwlwifi 0000:04:00.0: Found debug configuration: 0 [ 3.970174] iwlwifi 0000:04:00.0: loaded firmware version 46.177b3e46.0 cc-a0-66.ucode op_mode iwlmvm [ 5.769813] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.781915] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM [ 5.782199] iwlwifi 0000:04:00.0: Allocated 0x00400000 bytes for firmware monitor. [ 5.871900] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100 [ 5.931647] iwlwifi 0000:04:00.0: base HW address: 8c:c6:81:ef:ba:a5 [ 7.062842] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM [ 7.206552] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuring [ 7.239315] iwlwifi 0000:04:00.0: Applying debug destination EXTERNAL_DRAM [ 7.384031] iwlwifi 0000:04:00.0: FW already configured (0) - re-configuringI don't understand why this happens. There must be a way to force it to look for file 46 directly and not have to do this. but well it works and I'm happy.
I thank you very much for the time you spent @ghost82, @SimonF.
I hope if someone has come across this. at least this solution will work.
-
2
-
-
Rename file 46 to 66 and copy file "66" to /lib/firmware folder, run dmesg command and get this output
[ 5.491948] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-66.ucode [ 5.491968] iwlwifi 0000:04:00.0: Found debug destination: EXTERNAL_DRAM [ 5.491969] iwlwifi 0000:04:00.0: Found debug configuration: 0 [ 5.492245] iwlwifi 0000:04:00.0: loaded firmware version 46.177b3e46.0 cc-a0-66.ucode op_mode iwlmvm [ 5.651527] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.749474] iwlwifi 0000:04:00.0: retry init count 0 [ 5.749507] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.849701] iwlwifi 0000:04:00.0: retry init count 1 [ 5.849728] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 5.936719] iwlwifi 0000:04:00.0: retry init count 2After loading the driver it keeps trying to detect the wifi card.
-
3 minutes ago, ghost82 said:
In real I think it's not an issue with the passthrough, but with the driver.
Tomorrow I will have a better look at that log and think something.
Thanks @ghost82.
@ghost82, Can you do me the favor of passing me the 66 file to do the test?
I'm curious that it starts searching from file 66 and not from file 68.
maybe the error is that firmware 66 is not really loaded.
-
2 hours ago, ghost82 said:
if the same 63 is loaded you can try to delete 66, and rename that 68 to 66 and check if it loads.
I don't know if you mean that it replaces 63, because 66 doesn't exist.
What I did was copy 68 to /lib/firmware folder and restart Kali. but the result was the same. the Kali continued looking for file 66 until file 63.
After that i renamed file 68 to 66 and got below output with dmesg command.
$ sudo dmesg | grep iwl[ 5.627642] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-66.ucode [ 5.627657] iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver [ 5.627665] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 5.627670] iwlwifi 0000:04:00.0: Driver unable to support your firmware API. Driver supports v66, firmware is v68. [ 5.628029] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-65.ucode (-2) [ 5.628033] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2 [ 5.628052] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-64.ucode (-2) [ 5.628054] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2 [ 5.642753] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-63.ucode [ 5.642786] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.642800] Modules linked in: drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) usb_common(E) virtio_ring(E) drm(E) [ 5.642862] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.662038] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-62.ucode [ 5.662076] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.662093] Modules linked in: drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) usb_common(E) virtio_ring(E) drm(E) [ 5.662156] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.662399] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-61.ucode (-2) [ 5.662404] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-61.ucode failed with error -2 [ 5.662429] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-60.ucode (-2) [ 5.662432] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-60.ucode failed with error -2 [ 5.683709] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-59.ucode [ 5.683752] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.683766] Modules linked in: sha512_generic(E+) drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) usb_common(E) [ 5.683818] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.683936] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-58.ucode (-2) [ 5.683939] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-58.ucode failed with error -2 [ 5.683955] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-57.ucode (-2) [ 5.683957] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-57.ucode failed with error -2 [ 5.684868] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-56.ucode (-2) [ 5.684873] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2 [ 5.716313] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-55.ucode [ 5.716355] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.716372] Modules linked in: sha512_ssse3(E+) sha512_generic(E) drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) [ 5.716432] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.716557] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-54.ucode (-2) [ 5.716561] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-54.ucode failed with error -2 [ 5.736923] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-53.ucode [ 5.736964] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.736981] Modules linked in: sha512_ssse3(E) sha512_generic(E) drbg(E+) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) usbcore(E) virtio(E) [ 5.737041] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.737166] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-52.ucode (-2) [ 5.737169] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-52.ucode failed with error -2 [ 5.737186] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-51.ucode (-2) [ 5.737187] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-51.ucode failed with error -2 [ 5.762891] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-50.ucode [ 5.762933] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.762949] Modules linked in: jitterentropy_rng(E+) sha512_ssse3(E) sha512_generic(E) drbg(E) ansi_cprng(E) iwlwifi(E) ecdh_generic(E+) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) [ 5.763018] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.763141] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-49.ucode (-2) [ 5.763144] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2 [ 5.786945] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-48.ucode [ 5.786984] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.787000] Modules linked in: jitterentropy_rng(E) sha512_ssse3(E) sha512_generic(E) drbg(E) ansi_cprng(E) iwlwifi(E) ecdh_generic(E) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) [ 5.787062] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.787178] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-47.ucode (-2) [ 5.787181] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2 [ 5.807576] iwlwifi 0000:04:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-46.ucode [ 5.807609] WARNING: CPU: 2 PID: 45 at drivers/net/wireless/intel/iwlwifi/iwl-drv.c:1145 iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.807624] Modules linked in: fat(E) jitterentropy_rng(E) sha512_ssse3(E) sha512_generic(E) drbg(E) ansi_cprng(E) iwlwifi(E) ecdh_generic(E) intel_rapl_msr(E) ecc(E) intel_rapl_common(E) iTCO_wdt(E) joydev(E) intel_pmc_bxt(E) pcspkr(E) sg(E) serio_raw(E) cfg80211(E) efi_pstore(E) iTCO_vendor_support(E) watchdog(E) virtio_console(E) rfkill(E) qemu_fw_cfg(E) evdev(E) fuse(E) configfs(E) sunrpc(E) efivarfs(E) ip_tables(E) x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) crc32c_generic(E) hid_generic(E) usbhid(E) sd_mod(E) t10_pi(E) hid(E) crc_t10dif(E) crct10dif_generic(E) crct10dif_pclmul(E) crct10dif_common(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) virtio_net(E) net_failover(E) failover(E) ahci(E) libahci(E) libata(E) aesni_intel(E) crypto_simd(E) qxl(E) drm_ttm_helper(E) cryptd(E) ttm(E) scsi_mod(E) xhci_pci(E) scsi_common(E) psmouse(E) i2c_i801(E) drm_kms_helper(E) i2c_smbus(E) xhci_hcd(E) lpc_ich(E) cec(E) virtio_pci(E) rc_core(E) virtio_pci_modern_dev(E) [ 5.807673] RIP: 0010:iwl_req_fw_callback+0x2193/0x2310 [iwlwifi] [ 5.807774] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-45.ucode (-2) [ 5.807777] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-45.ucode failed with error -2 [ 5.807792] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-44.ucode (-2) [ 5.807793] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-44.ucode failed with error -2 [ 5.807808] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-43.ucode (-2) [ 5.807809] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-43.ucode failed with error -2 [ 5.807822] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-42.ucode (-2) [ 5.807845] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-42.ucode failed with error -2 [ 5.807860] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-41.ucode (-2) [ 5.807861] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-41.ucode failed with error -2 [ 5.807876] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-40.ucode (-2) [ 5.807877] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-40.ucode failed with error -2 [ 5.807889] iwlwifi 0000:04:00.0: firmware: failed to load iwlwifi-cc-a0-39.ucode (-2) [ 5.807891] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-cc-a0-39.ucode failed with error -2 [ 5.807892] iwlwifi 0000:04:00.0: minimum version required: iwlwifi-cc-a0-39 [ 5.807894] iwlwifi 0000:04:00.0: maximum version supported: iwlwifi-cc-a0-66 [ 5.807895] iwlwifi 0000:04:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.gitI don't know if I should delete file 63
I'm thinking of creating a bootable USB with Kali Linux. to test without the S.O UnRaid and rule out that it really is an error when passing the wifi card.
-
1 hour ago, JhonScript said:
only this output appears. I don't know if I should do something with this
Feb 12 10:50:32 kali bluetoothd[2149]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Feb 12 10:50:32 kali bluetoothd[2149]: sap-server: Operation not permitted (1) Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc_xq_453 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc_xq_453 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc_xq_512 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc_xq_512 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink/sbc_xq_552 Feb 12 10:50:32 kali bluetoothd[2149]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource/sbc_xq_552@ghost82, @SimonF, Do you know if these messages are normal?
-
3 minutes ago, JhonScript said:
It seems that they have different weight, I will do tests.
copy the new file, restart the kali.
I don't change anything.
-
4 minutes ago, JhonScript said:
i only found this repo https://github.com/thesofproject/linux-firmware/blob/master/iwlwifi-cc-a0-46.ucode
It seems that they have different weight, I will do tests.
QuoteNOTE:
left, downloaded from intel.
right, downloaded from github
[Plugin] FolderView
in Plugin Support
Posted
Hello, it seems that the problem is that the custom action does not have the conatiners variable when the custom action is of type "Custom"