Search results

Could you please try explaining once in a different manner than @jeanlau did the steps you took? I am not getting through his explenation :(

After a lot of effort by mastakilla, someone in close contact with asrock rack, it turns out to be AMD that does not cooperate to get ECC events to be logged by IPMI on non server boards. My stance is that asrock rack should not have marketed my x470d40 board as such in that case

I think it must have been a tmp issue as the shares show up in the gui again

But they are not in storage.cfs The syslog spaming stopped after a reboot though

root@pve-trx40:/etc# cat fstab # <file system> <mount point> <type> <options> <dump> <pass> root@pve-trx40:/etc# cat /etc/pve/storage.cfg dir: local path /var/lib/vz content backup,iso,vztmpl zfspool: local-zfs pool rpool/data content rootdir,images...

every 2 seconds a new row appears in the syslog of pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve) # start copy paste from syslog kernel: CIFS VFS: \\oldnas.lan Send error in SessSetup = -13 # end copy paste from syslog there is no share specified only the server name. The weird...

thx all for the help. finally managed to get the sound passed through. I am happy

Thanks a lot: Almost there now. One error while compiling when using your patch file contents: applying patch '../../patches/kernel/0008-amd-no-flr.patch' patching file drivers/pci/quirks.c patch: **** malformed patch at line 4: DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);

@qwerty0033 can you please paste me the contents of your 0008 patch file?

I am getting closer, I just got confused, and have the patch file on my system. can you please paste me what you ended up with after the changes you mention? I can double check manufacuter and device id's later. This is what I have now in /usr/src/pve-kernel/patches/kernel/0008-amd-no-flr.patch...

finally I found the inner strength to try and then :( kernel root@pve:/usr/src/pve-kernel/patches# ls kernel root@pve:/usr/src/pve-kernel/patches# cd kernal -bash: cd: kernal: No such file or directory root@pve:/usr/src/pve-kernel/patches# cd kernel root@pve:/usr/src/pve-kernel/patches/kernel#...

wow thank you sooo much for holding my hand. Please allow some time in order for me to try it. I will for sure to get back to this.

@seji, or anyone? perhaps there is a guide for the uninitiated on how to patch the kernel? all i find are guides that assume prior knowledge

I needed to patch the kernel because of pci flr issues when passing through onboard sound on amd64, ryzen zen2 system. did not work out.

thanks for the info @seji however this results in no more netowrking and a boot time that takes ages. a start job is running for udev wait for complete device initialization a start job is running for helper to synchronize boot up for ifupdown originally all went smooth with: root@pve:~#...

Ok I went in head first and dpkg -i .deb files. Luckily that created a restor point because I got stuck and now am back again. I am relieved. Is there anyway to create such restore points before making quite drastic changes?

When doing an update using the GUI I noticed that when I reboot the host I get presented an option at early boot to select the boot environment. (e.g. use the current updated kernel or use the kernel from before the update) is there any way to create such a restore point without actually...

@seji once again thanks for your contribution. I am going in with your .deb files and have already downloaded them. can you please share a total noob guide for how to actually 'install' those .deb files? I found some guides that assume some prior knowledge that I don't have yet.

@EricD Welcome back. Thanks for sharing. Earlier in this thread I also had success with the l8st kernel. It's great that it is now part of pve 6.2

I liked your solution even though not fully understanding it yet ;) I figured that it seems to work otherwise there would have been questions already. I am going to dive in and see how far I get. I think a procedure like this should be a standard feature as it is sooooo convenient.