Dazog
-
Posts
396 -
Joined
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Dazog
-
-
Solid Release.
Next .1 update can you grab Docker 20.10.20?
It fixes multiple CVE's
TY!
-
@binhex any chance you are going to push the 3.6.1 sabnzbd to docker hub?
-
3
-
-
Ha NVidia FINALLY fixed the Mellanox 4 LX flashing bug from November in this update.
Thanx again @ich777
-
1
-
-
Any chance for a beta or nightly also?
TIA
-
2 hours ago, starbetrayer said:
@SpencerJ has interesting friends
jiiij ijiii jijij jiiji iijii ijjii jijjj iijii jiiii ijjij jiiii iiiji jiiji iijjj jiiii iijii iijii ijiij
K..
-
9 hours ago, ich777 said:
This driver does not compile currently because of this (last line from the changelog), have to contact Nvidia about that:
Updated nvidia.ko to load even if no supported NVIDIA GPUs are present when an NVIDIA NVSwitch device is detected in the system. Previously, nvidia.ko would fail to load into the kernel if no supported GPUs were present.
Also keep in mind this is a beta driver.
You have to give me a few days to solve this.
No rush, the do not speak of patch is always a few days behind drivers anyway
-
https://www.nvidia.com/Download/driverResults.aspx/184911/en-us
wow massive amount of fixes for this branch.
-
3 minutes ago, Squid said:
Wow. I'm impressed that someone even looks at it....
Fixed. (Weird markdown syntax error)
I don't ALWAYS trust what you do
-
1
-
-
Seeing this error when clicking on the release notes:
Warning: count(): Parameter must be an array or an object that implements Countable in /usr/local/emhttp/plugins/dynamix/include/Markdown.php on line 2008
-
21 hours ago, ich777 said:
Is this issue on Github related: Click
Possibly. Card works perfect. Just firmware updates broke when they updated the MFT tools.
old plugin worked, new one with new MFT is broke. So i guess mellanox borked something.
-
1
-
-
On 12/8/2021 at 1:23 AM, ich777 said:
I will try to reflash my card (Mellanox Connect X3) and will see if the same happens to me and report back.
Where you able to flash this exact card in the past or did you flashed other cards?
Do you use this command: 'mstflint -d 01:00.0 -i *.bin burn' with the asterisk or do you specify the full filename?
EDIT: Flash went fine without any error:
mstflint -d 01:00.0 -i fw-ConnectX3-rel-2_42_5000-MCX311A-XCA_Ax-FlexBoot-3.4.752.bin burn Current FW version on flash: 2.42.5000 New FW version: 2.42.5000 Note: The new FW version is the same as the current FW version on flash. Do you want to continue ? (y/n) [n] : y Burn process will not be failsafe. No checks will be performed. ALL flash, including the Invariant Sector will be overwritten. If this process fails, computer may remain in an inoperable state. Do you want to continue ? (y/n) [n] : y Burning FS2 FW image without signatures - OK Restoring signature - OKAlso removed the boot ROM after that:
mstflint -d 01:00.0 --allow_rom_change drom -I- Preparing to remove ROM ... Removing ROM image - OK Restoring signature - OK
Same errors with bin name
-W- DMA burning is not supported due to BME is unset (Bus Master Enable).
FSMST_INITIALIZE - OK
Writing Boot image component - OK
-E- Burning FS3 image failed: Unexpected state -
20 hours ago, ich777 said:
I will try to reflash my card (Mellanox Connect X3) and will see if the same happens to me and report back.
Where you able to flash this exact card in the past or did you flashed other cards?
Do you use this command: 'mstflint -d 01:00.0 -i *.bin burn' with the asterisk or do you specify the full filename?
EDIT: Flash went fine without any error:
mstflint -d 01:00.0 -i fw-ConnectX3-rel-2_42_5000-MCX311A-XCA_Ax-FlexBoot-3.4.752.bin burn Current FW version on flash: 2.42.5000 New FW version: 2.42.5000 Note: The new FW version is the same as the current FW version on flash. Do you want to continue ? (y/n) [n] : y Burn process will not be failsafe. No checks will be performed. ALL flash, including the Invariant Sector will be overwritten. If this process fails, computer may remain in an inoperable state. Do you want to continue ? (y/n) [n] : y Burning FS2 FW image without signatures - OK Restoring signature - OKAlso removed the boot ROM after that:
mstflint -d 01:00.0 --allow_rom_change drom -I- Preparing to remove ROM ... Removing ROM image - OK Restoring signature - OK
I use the asterisk
I will try using the full name.
-
1
-
-
9 hours ago, ich777 said:
Are you running unRAID with virtualization? Only asking because of the explanation here: Click
But I think you are flashing a 4th gen card (or is this a 5th gen card)?
Mellanox 4LX and I run no vm's
-
8 hours ago, ich777 said:
Can you share a little more details please, maybe the Diagnostics, also what the exact commands are you've used and what card do you want to flash?
Using the command listed in the Mellanox plugin.
Flashing a Mellanox 4LX
Worked fine until the MFT got updated in the last release.
Unsure what mellanox changed, maybe i need another flag on flash
-
Getting this error trying to update my mellanox card:
-W- DMA burning is not supported due to BME is unset (Bus Master Enable).
FSMST_INITIALIZE - OKAnyone else seen this?
-
Would be nice to have this enabled even as a beta to try out (io_uring):
-
-
https://www.nvidia.com/Download/driverResults.aspx/175539/en-us
465.31
For those lucky people running unraid on their RTX3000 series laptops
-
1 minute ago, ich777 said:
You mean the Vulkan 1.2 API where the others only have 1.0 and 1.1?
But do you really think it's usefull on Unraid?
Anyways, I will not support that branch because it's not even a "real" branch because it's nowhere listed which versions numbers these drivers with the new API are and also I don't think that game developers will use Unraid as a platform to test such things or even develop games for the new API.
The next thing is I don't have a way to read the version numbers from anywhere automated which are Vulkan DEV drivers...
Also think twice about it, the users now can choose between 3 or better speaking 2 different branches and you can also choose between 8 recent driver versions, I will not bloat the plugin page anymore especially with DEV drivers...
Oh no...
No worries, I thought I would ask.
-
1
-
-
10 hours ago, ich777 said:
Is this a new card or where did you buy it?
I came across such messages in the past and this seems like it's been a counterfeit card, can you post a picture of the card itself?
Also here is a reference from Nvidia: Click
(From the audio controller identifier it looks more like a GTX550Ti)
I'm maybe wrong about that but isn't Vulkan built into every driver from 455.50.14 upwards on Linux?
EDIT: What would be the benefit on Unraid? Also keep in mind that Nvidia defines only the Production Branch and the New Feature Branch even on their download page:
Vulkan branch has latest extensions NOT in the branches on consumer site.
It's meant for people testing upcoming Vulkan versions.
I don't use it, but some may find it useful.
-
Could you add the Vulkan dev branch for people who need it also?
https://developer.nvidia.com/vulkan-driver
Linux 455.50.14
-
Another week another new driver:
https://www.nvidia.com/download/driverResults.aspx/174582/en-us
465.27
-
5 hours ago, ich777 said:
Don't know if you have seen that:
They also don't list it on their download server so the automatic build script won't trigger and I can't build it when the download isn't available...
Ugh I have a time machine.
I will dial it back down 🙂
-
1
-
-
Unraid OS version 6.11.2 available
in Announcements
Posted
6.1 is due in Dec and is LTS, would make sense to stay on 5.19 then jump to 6.1 since 6.0 will go EOL shortly after 6.1 is out.