Jump to content
XPEnology Community

ressof

Rookie
  • Posts

    9
  • Joined

  • Last visited

Everything posted by ressof

  1. I finally got DSM7.0 Apollolake 918+ to work on ESXI 7. I got Red-Pill to boot on a virtual USB drive. Thank you all for your help here.
  2. Hi. Yes its active and I can boot from it. But the installation reach 99% and then nothing happens.
  3. But the installer won't continue after FAT-fs (synoboot1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
  4. Hi Im trying to install DSM 7.01 apollolake 918+ on ESXI. When running fdisk before installing PAT file I get this: Disk /dev/sda: 120 GB, 128849018880 bytes, 251658240 sectors 15665 cylinders, 255 heads, 63 sectors/track Units: sectors of 1 * 512 = 512 bytes Disk /dev/sda doesn't contain a valid partition table Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors 1008 cylinders, 5 heads, 52 sectors/track Units: sectors of 1 * 512 = 512 bytes Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type /dev/synoboot1 0,32,33 6,62,56 2048 100351 98304 48.0M 83 Linux Partition 1 has different physical/logical start (non-Linux?): phys=(0,32,33) logical=(7,4,21) Partition 1 has different physical/logical end: phys=(6,62,56) logical=(385,4,44) /dev/synoboot2 6,62,57 15,205,62 100352 253951 153600 75.0M 83 Linux Partition 2 has different physical/logical start (non-Linux?): phys=(6,62,57) logical=(385,4,45) Partition 2 has different physical/logical end: phys=(15,205,62) logical=(976,3,36) /dev/synoboot3 15,205,63 16,81,1 253952 262143 8192 4096K 83 Linux Partition 3 has different physical/logical start (non-Linux?): phys=(15,205,63) logical=(976,3,37) Partition 3 has different physical/logical end: phys=(16,81,1) logical=(1008,1,12) and the logs when trying to install the PAT file from serial console [ 183.720933] <redpill/rtc_proxy.c:37> MfgCompatTime raw data: sec=20 min=3 hr=6 wkd=5 day=10 mth=8 yr=121 [ 183.723631] <redpill/rtc_proxy.c:95> Writing BCD-based RTC [ 183.724954] RTC time set to 2021-09-10 6:03:20 (UTC) [ 186.800143] md: bind<sda1> [ 186.801637] md/raid1:md0: active with 1 out of 16 mirrors [ 186.802992] md0: detected capacity change from 0 to 2549940224 [ 189.811875] md: bind<sda2> [ 189.813208] md/raid1:md1: active with 1 out of 16 mirrors [ 189.814563] md1: detected capacity change from 0 to 2147418112 [ 190.198325] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 190.209674] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 190.240130] <redpill/rtc_proxy.c:222> Got an invalid call to rtc_proxy_set_auto_power_on [ 190.246693] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 190.257611] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 190.272865] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 190.283741] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 196.595667] ext2: synoboot2 mounted, process=updater [ 196.599505] synoboot2 unmounted, process=updater [ 196.607208] ext2: synoboot2 mounted, process=updater [ 196.609221] synoboot2 unmounted, process=updater [ 196.616749] ext2: synoboot2 mounted, process=updater [ 196.619137] synoboot2 unmounted, process=updater [ 196.625799] ext2: synoboot2 mounted, process=updater [ 198.179513] synoboot2 unmounted, process=updater [ 203.191011] ext2: synoboot2 mounted, process=updater [ 203.250955] synoboot2 unmounted, process=updater [ 203.261041] ext2: synoboot1 mounted, process=updater [ 203.265540] vfat: synoboot1 mounted, process=updater [ 203.268169] FAT-fs (synoboot1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Can this be fixed?
  5. I tried with that also but I still got this error message [ 43.137930] vmxnet3: version magic '4.4.180+ SMP preempt mod_unload ' should be '4.4.180+ SMP mod_unload ' insmod: can't insert '/lib/modules/vmxnet3.ko': invalid module format
  6. I compiled vmxnet3 driver with this kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tag/?h=v4.4.180 But when I try to insmod the driver I get this error message [59697.560776] vmxnet3: version magic '4.4.180 SMP mod_unload ' should be '4.4.180+ SMP mod_unload ' insmod: can't insert '/lib/modules/vmxnet3.ko': invalid module format
  7. Do you know what kernel version you need for compile modules for 918+ apollolake?
×
×
  • Create New...