gnoboot

Members
  • Content Count

    278
  • Joined

  • Last visited

Everything posted by gnoboot

  1. I've been there too... Some people doesn't really appreciate our effort for this community. All they want is free stuff and complain.
  2. It took so long before finally releasing this iSCSI patch to the community. I'm no longer interested in maintaining/keeping this stuff. Releasing my kernel build script soon, but no support or whatever. If you want to donate or appreciate my work email me.
  3. Did you try manually reloading mpt2sas driver after booting up DSM? gnoboot> rmmod mpt2sas gnoboot> insmod /lib/modules/mpt2sas.ko && dmesg | tail -n 50 or gnoboot> insmod /lib/modules/mpt2sas.ko missing_delay=1000 && dmesg | tail -n 50 And post the result of 2nd command.
  4. I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk? Have you been able to get disks conected to the 9211-8i to start from Disk1-Disk8? Do i need to blacklist any other drivers to make sure theres no unused slots before the disks on the raid card? Also , Will flashing IT firmware instead of IR benifit in any way? You have to blacklist the boot image disk (ata_piix) using rmmod GRUB option. Put the following lines in your /boot/grub/menu_alpha.lst kernel /zImage rmmod=ata_pi
  5. https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/net/ethernet/atheros/alx?id=bc2bebe8de8ed4ba6482c9cc370b0dd72ffe8cd2
  6. Boot to debug mode by editing gnoboot-alpha boot menu, send your /.gnoboot/debug.log. Can you also provide a DSM screenshoot? kernel /zImage debug
  7. Haven't looked into it . I'm using 9211-8i and it works (IR mode) for me on ESXi+vt-d. Are you using baremetal or vt-d? Doesn't show in DSM or doesn't detect the disk? Try to blacklist r8169 using rmmod GRUB option. Did you load the drivers in /etc/rc.local? Try it again using 10.5, added more boot-up messages to trace your problem. Try to blacklist r8169 using rmmod GRUB option. Did you load the DVB drivers in /etc/rc.local?
  8. Try to insmod pata_amd or pata_acpi.
  9. Please expound custom hardware. What you're getting is the default hardware model if something weird happens.
  10. Post your `dmesg` and `lspci -vvv`. You can also try gnoboot-alpha10.5-vanila-zImage.
  11. Edit your GRUB configuration like the following: kernel /zImage sn=XXXXXXXX
  12. I've looked at your dmesg but there's no unknown messages. Did you dmesg after plugging your USB device?
  13. Great! Are you still using those boot parameters I gave you? Use pastebin or cryptobin then link it here.
  14. @FrankDeRyder, It's probably DSM app related issue, my boot image is just a kernel and initramfs. It has nothing to do with the apps. For example, synozram script is broken because vendor is using PHP to calculate memory size which is missing from default installation. @Kybla, Might be, try another backup method (e.g. rsync) or wait for beta release that will include a working iSCSI block backend.
  15. Not sure, if you 4.2 would allow you to jump directly to 5.0. Take a backup first before you do anything as it should not be "configuration lost" if you have existing DSM installation.
  16. Post your `dmesg` and `lspci -vvv` result. You have to give linuxtv.org link for your USB DVB-T2.
  17. Try booting with the following options. kernel /zImage acpi=off irqpoll debug rmmod=sg
  18. Serial console and boot to debug GRUB option, use putty to capture the text messages during boot up. Though, not sure if you MB supports serial connection.
  19. Then you either have to rmmod xhci or ehci in /etc/rc.local. Back read to know what's causing the segfaults.
  20. A quick google resulted to this. So i think this more of hardware bug/limitation.
  21. How about using a Linux livecd with your disks connected, does it work? I think this more of a hardware problem or something. It doesn't even load the GRUB and kernel. You can also try changing from AHCI to IDE mode, check if that works.
  22. Kernel driver in use: r8168 There's already workaround posted in my blog. You have to rmmod GRUB option r8169_new. Have you tried that already? kernel /zImage rmmod=r8169,r8169_new
  23. Yeah, just read it the other day. That's why I've cleanup the comments section. This also the same to using a custom pat file which is against the vendor license terms.
  24. Capture the last module loaded before it panic, then try to rmmod that module. kernel /zImage rmmod=pata_acpi,pata_amd Can you send your `dmesg` and `lspci -vvv` result?