Jump to content
XPEnology Community

nearffxx

Member
  • Posts

    10
  • Joined

  • Last visited

Posts posted by nearffxx

  1. To extract the rd.gz you should use the script contained in the linux kernel tree then binwalk

    linux/scripts/extract-vmlinux 
    binwalk vmlinux

    So compile your fiber-channel-driver.ko and rename it to e100.ko, then pack it in rd.gz, and finally boot it with the xpenology bootloader with initrd=rd.gz.

  2. Depending on what you want to do you can either delete the rd.gz from the .config file or the one extracted from the bootloader (https://mega.nz/#!rIk2BYYI!2a5_fZzyfqH7YUvmOyUXSniQeNe9nB9TkmI4qL680H0).

    If you want to only compile kernel modules and use the original kernel then you can just delete rd.gz from the .config.

    After the kernel module has been compiled you have to create a new init ram rd.gz and then add to the iso/usb and append the following argument to the kernel

    initrd=rd.gz

    , which it seems to work as a sort of overlay.

    If you want to run your own kernel then you have to specify the path of your rd,gz in your .config file. In theory, this latter method should work, I got an error while installing the pat file. According to this post http://xpenology.com/forum/viewtopic.php?f=2&t=13076 the source code might not contain be complete.

     

    Best

    D.

  3. That's the .config taken from the latest xpenology release, dunno if that works for you.

    https://mega.nz/#!rAtz3aqA!c2iGrRtH6W5MIlhVSNGI2gXvKI0rosiT6q701pvJWvE

    BTW, you can find the .config of a running OS in /proc/config.gz.

    Only if you have a kernel compiled with specific option to export running config into /proc or, if you have compiled specific module

    I can confirm xpenology kernel is compiled with that option.

  4. Hi Trantor,

     

    Can you please patch the mcp89 controller?

    The controller is already patched in the upstream kernel but not in this the current version https://github.com/torvalds/linux/commit/cb85696d7277592ddbd2897db9a29f3ec6e9fe11.

    I tried to patch myself and it half worked, xpenology can detect my drive, but the installation failed (13).

    Here are my last build.

    http://xpenology.com/forum/viewtopic.php?f=2&t=18379

     

    Thanks

×
×
  • Create New...