-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.0 release versions seems not to be working #2
Comments
Sorry to hear you are having trouble. When virtualbox exits during the decompression of the Linux Kernel, it is usually do to PAE/NX being disabled in the virtual machine settings. Try navigating to Machine > Settings > System > Processor > Enable PAE/NX. Also ensure when creating the virtual machine, select Type: Linux > Version: Linux 2.6 / 3.x / 4.x (32-bit). I have went ahead and tested these settings for the vdi and vmdk using Windows 10, Ubuntu 18.04 LTS, and MacOS boxes. Screenshots are below with OS and VBox versions. I will have to perform additional tests for Raspberry pi this week and will follow up with any additional procedures. Thanks for reporting. Windows 10MacOSUbuntu 18.04 |
Unsure of the root issue thats causing the NAT interface to be inaccessible from the host. Try switching the network interface to bridged adapter which should work fine (No issues on my end). With VMWare, NAT works by default. |
Thank you, finally I've managed to launch it 💯 With the VDI image, using bridged adapter didn't helped, but VMDK with bridged adapter works just fine. |
Hello. Have you been able to test the project in a raspberry pi? I want to try this project, but I need to know if it works before buying the raspberries (virtualization is not an option). Also, would it work on a pi 4, or do I have to purchase a pi 2? Thanks in advance |
Hi, the current version of OpenWRT, that the project is using, is not compatible with Pi 4, but it works on Pi 2, I've managed to run it. |
@Radv1la I was trying to flash the SD card with the provided image using the Raspberry pi imager. |
I downloaded the Raspberry Pi 2 image, used balenaEtcher to write it to the SD card. Then I had tried booting it in Raspberry Pi 4 , but all I got is just a black screen, I also tried to boot it in Raspberry Pi 2, but it just hangs with the rainbow screen. Both versions were tried (sysupgrade and the other one). Later on, I have tried using another software for writing to SD – Win32DiskImager. But that didn‘t helped. To make sure that this is not related to my machine, I used other computers to write to the card, but the effect is the same.
Some additional information
• OS that I use: Windows 10
• Size of the SD cards I‘ve tried to write to: 64 GB and 16 GB
I‘ve also tried VDI image with VirtualBox (version 6.1.4 r136177). It gets to the GRUB loader, but after this, it just crashes. From what I can see from logs, It looks like that it results in critical error when trying to boot the kernel.
I’ve also downloaded VMware to check if this would work, but unfortunately this seems to be not working also. After the grub loader screen, it starts booting, but at some point (crng init done), it just hangs. I’ve waited for about 40 minutes, but nothing progressed.
The text was updated successfully, but these errors were encountered: