smoojay

Transition Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

4 Neutral

About smoojay

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. very very super nice work guys! keep on, thanks for all the fish
  2. Let's try with Discord, the invitation https://discord.gg/RQ3UtY5Mfw
  3. Already seen that, we should move to discord or some plain old technology, they are already there
  4. yes, the core os is already part of the image which you will get with the the redpill-loader
  5. after successful boot, you should see something like .. :: Loading module hid ... [ OK ] :: Loading mo[ 46.880017] usbcore: registered new interface driver usbhid dule usbhid[ 46.905318] usbhid: USB HID core driver ... [ OK ] :: Loading module syno_hddmon ... [FAILED] ============ Date ============ Wed Jul 28 15:38 Wed Jul 28 15:38:09 2021 DiskStation login: then you are sure you are at the right port. sorry i don't know other ways to access the log.
  6. You can login using the serial interface, for example on proxmox qm terminal <vmid> -iface serial1 // or serial2 then login as root w/o pw and navigate to /var/log/messages
  7. This is just the boot log, see ttyS2 for the console output
  8. Current state on Virtualbox. The message with minissdpd indicates a parameter mismatch. There is no eth interface configured. .. [ 38.551818] <redpill/bios_shim.c:111> apollolake_synobios BIOS shimmed ... [ OK ] lo Link e[ 38.607768] <redpill/intercept_execve.c:87> Blocked /usr/syno/bin/syno_pstore_collect from running ncap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  9. I can confirm that too. It’s a problem with the network interface. Virtualbox doesn’t work with the builtin e1000 driver and virtio_net doesn’t seem to be correctly loaded.
  10. Tested with both, Fusion and ESXi. On ESXi i wasn't able to grab the console output due to the limitation with the free edition. So, im not sure if it is the same with ESXi.
  11. confirmed with latest code, seems to be a problem on vmware platforms .. doesn't occur on virtualbox or proxmox
  12. there are various problems with v4, the one i saw are with 'set_memory_rw/ro' which are not exported in v4 anymore. you have to find them via 'kallsyms_lookup_name'. in addition i had to revert the last two commits 'Add virtual PCI subsystem & preliminary PCI shim' and 'Implement kernel cmdline sanitization' to get it compiled with a v4 kernel. tests pending ..