I'm trying to setup Alpine Linux on a Raspberry Pi Zero W in Sys Mode (normal Desktop mode) but it doesn't seem to be working.
I've followed all the instructions given on the Alpine website for installations.
After setting up the setup-alpine setups, I'm choosing the "Sys" mode in the mmcblk0p1 disk (SD Card). It creates a boot partition (FAT FS) then says installation is complete, please reboot. But after reboot the Alpine doesn't boot and it throws a big "Kernel Panic not Syncing" error or something like that.
I'm even having trouble installing packages as all the installations seem to be going to the RAM memory instead of ROM.
Can somebody please help me with this.
I'm not all that good with Linux systems and OS/Kernels but can learn really quick.
Related
I want to build a time consuming package (mediapipe) on my Raspberry-Pi buster image under QEMU. So far, I've gotten the image to load and run (including with network connectivity); however, I'm limited to 256MB of storage, which just isn't enough to do much - especially build a mediapipe. Can someone explain why Raspbian images running under QEMU seem to be limited to 256MB?
I've seen some posts about people running with 512MB and even one with 1GB, but they don't seem to be very successful. Can anyone explain the reason for the restriction, and a potential fix?
The problem here is that a lot of people claim to be running "raspberry pi emulation in QEMU" when they're actually just running Raspbian userspace on top of a kernel for a different machine emulation. So it's easy to be confused if you look at several different tutorials that are really describing entirely different emulation setups. Look for what machine type they pass QEMU.
The "versatilepb" machine type gets used in a lot of tutorials, especially older ones, because it has been in QEMU a long time and it is possible to get it to work with the 1176 CPU that the classic Raspberry Pi boards used. This specific machine has a 256MB maximum memory size, because the real hardware it's emulating has that restriction (it's imposed by the way the physical memory address space is designed). This machine type will never be able to support more RAM, so if you need more then you should ignore any tutorial or setup that uses it.
More recent versions of QEMU really do emulate the actual raspberry pi hardware; these are the raspi0, raspi1ap, raspi2b, raspi3ap, raspi3b machine types. These will have the same amount of RAM as the real raspi hardware they're emulating (either 512MB or 1GB). The downside of these board models is that some of the device emulation is lacking features -- so older QEMU will often not correctly boot a newer kernel, and sometimes devices you would like to use are not present. Also, because the raspi boards hang their ethernet device off the USB controller, the only way to get ethernet on these QEMU models would also be to use a USB ethernet device, eg with:
-device usb-net,netdev=eth0 -netdev user,id=eth0
This probably needs a recent QEMU version to get a working USB controller.
I don't know if there are any tutorials/recipes for running Raspbian on top of the QEMU "virt" board. If there are, this would probably be the best experience, because the virt board permits lots of memory, PCI devices, virtio devices, and is well maintained.
I have installed Raspberry Pi for Desktop on a Lenovo Laptop following these instructions. The installation ran without problems. On restart the computer hangs in a loop: Every time I am asked in the boot menu from which drive I want to boot.
Here I select the hard disk and after a short time I am asked again from which drive I want to boot...
Anyone have an idea what is going wrong?
Thanks for the help
I have a short Question related to Raspberrys but in applies in general to Linux systems.
Can I prevent someone from reading out the SD-Card of the Raspberry?
What do I mean: I can simply disable all login-posibilitys to prevent anyone from logging into the system. But if you unplug the SD-Card and mount it in another linux system, you still have full access to all files.
Is there any possibility besides glueing the SD-Card to the Pi?
I would be already greatfull for some keywords to google with ;)
some Linux distributions (e.g. Ubuntu) support full disk encryption, which you can activate during setup.
Since you have an Raspberry PI, I assume that you have already installed raspbian. Therefore you can search for raspbian home folder encryption for example.
You can also set access rights so only the Pi user can open them.
I've filled up my Intel Edison 100% and have no room for anything more. I've emptied all logs and am still at 100%. I decided I want to factory reset and reorganize next time with the SD card better. Unfortunately I cannot find out how to reinstall completely the OS.
I've tried downloding the Yocto linux image off the intel downloads page, and uploading that to the Edison. However, it still is running the same as before...
For some reason I distinctly remember (pretty sure anyway...) reading a command to 'reset' everything. I just can't find any documentation now that I need it. Does anyone know how to do this?
Found the command, it's reboot ota
This is my checklist
Install dfu-util (on Linux: sudo apt-get install dfu-util)
Download Release 3.0 Yocto* complete image and unzip it
Connect the module using both USB connectors.
Run sudo ./flashall.sh --recovery
Wait for the script to finish and then a few extra minutes for the module to boot.
I've found one USB hub that didn't work, I had to connect directly to the USB port on the computer.
I'm not sure if you need both usb connectors but at least the one for main power is needed.
flashall.sh is found in the unzipped directory.
I am trying to setup an iDs ueye camera on my raspberry pi for a project. I am supposed to run a .gz.run script file that setups everything and then run a daemon that startups the camera.Although on my laptop it works fine (64bit ubuntu) when I setup the 32bit version on the pi and then run the daemon I get the following error:
/usr/local/share/ueye/ueyeusbd/ueyeusbd: 1:
/usr/local/share/ueye/ueyeusbd/ueyeusbd: Syntax error: word unexpected
(expecting ")")
I'm suspecting that the camera is not compatible for arm processors , but I would like to find out if there's a way for it to be.
IDS has recently released an alpha driver for the Raspberry Pi in the form of an image file. Basically it is a normal Wheezy Rasbian distribution with the ueye-driver (i.e. ueye-daemon) installed. Although the official documentation is sparse (to say the least), everything seems to be in place - the complete Linux SDK should be supported.
You can get the stuff from: http://en.ids-imaging.com/embedded.html