Search results

So, Siemon used the "QSFP28-4" product code because it's 28AWG, 4 meters. That's kinda dumb...

The 500W should work. It's also possible one of the PSUs from other 7050 models might work. Double check the physical connectors. If they're physically compatible, they should work. I wouldn't recommend trying to use anything 3rd-party, if it even exists.

I have a 7050QX-32S. Your plan might work, but they get hot fast, even at idle. Power usage should be similar with one PSU or two - it just depends how many DACs/transceivers you plug in. It will complain if the fans aren't installed, but it won't shut down unless it reaches critical temps...

I've been using Hyper-V on S2D at home off and on for a few years now and I love it. Admittedly I'm using eight dirt cheap 120GB SSDs, so my space is very limited after the redundancy, but even after a few years it still feels like black magic watching a VM live migrate in just a few seconds

Due to the legal gray areas involved, it's not really safe to hand out the keys to the castle, but here are a few tips: 1. Locate, download, and unpack a MLNX_OS image (Preferably the x86 variant) 2. Locate the genlicense and dumplicense executables in the unpacked image. 3. Play around with...

Several of us are trying to figure that out.

After getting past the tty boot loop with the trick above, I'm sitting at 'Step 3: Creating the file systems on the switch and extracting the distro' I immediately ran into an issue. The commands mount -t proc none /proc mount -t sysfs none /sys both fail. I'm not really sure why, and I also...

Did you have to do anything special aside from following mpogr's guide?

Thanks a bunch. It looks like the exact same environment as mine: Diff Checker The only difference seems to be that addtty has been run once addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate} which just expands the bootargs variable and adds the console configuration to the end...

The command I've been using, 'run flash_jffs2' is already identical to that, just with a different name: flash_jffs2=run jffs2_args boot_common_args;bootm ${kernel_addr} - ${fdt_addr} I tried the following: envreset setenv mlxlinux 'run jffs2_args boot_common_args;bootm ${kernel_addr} -...

That's exactly what I've been doing. I even tried 'nand erase clean' one of the times without specifying addresses so it wiped the entire nand (but I did NOT do a 'nand scrub' because I read that it can cause major problems) I think part of the the problem is that before I first started this...

Ok, I started completely over, substituting in that jffs2 image, and it seems to be doing the exact same thing: And it will just reboot and go into a loop For reference here is my printenv output

I'm having this exact same issue.