I try to get into the initramfs shell on my pi400 but hdmi-monitor always keeps black after showing some boot messages. Any ideas?
My config.txt:
camera_auto_detect=1
display_auto_detect=1
dtoverlay=vc4-kms-v3d
max_framebuffers=2
arm_64bit=1
disable_overscan=1
[cm4]
otg_mode=1
[all]
[pi4]
arm_boost=1
[all]
initramfs initramfs.gz followkernel
Why I am doing that? I am following to one of the many almost identical tutorials [1] for full encryption of my sd-card with LUKS but without success.
p. ex. https://rr-developer.github.io/LUKS-on-Raspberry-Pi/
Not to enable DRM VC4 V3D driver was the solution. So I comment those lines in config.txt:
#dtoverlay=vc4-kms-v3d
#max_framebuffers=2
Does anyone have a working UBoot config for accessing an NVME drive from UBoot running on a Raspberry Pi CM4?
I've compiled everything and UBoot is detecting my NVME correctly:
pci_bind_bus_devices: bus 1/pci_0:0.0: found device 0, function 0: find ret=-19
pci_find_and_bind_driver: Searching for driver: vendor=2646, device=2263
pci_find_and_bind_driver: Match found: nvme
pci_auto_config_devices: start
pci_auto_config_devices: device nvme#0
PCI Autoconfig: BAR 0, Mem, size=0x4000, address=0xc0000000 bus_lower=0xc0004000
pci_auto_config_devices: done
but it doesnt call nvme_uclass_post_probe() and therefore it doesnt create any block device.
Running the command "nvme scan" from the UBoot command line i'am getting a timeout in nvme_submit_sync_cmd(). -> ETIMEDOUT.
I'am using a Kingston A2000 SDD with the latest firmware "S5Z42109".
Does anyone have an idea?
Thanks.
I followed this tutorial to compile a MongoDB on a raspberry pi. I ended up with the content of the tarball which is on the same repo.
The unpacked archive has the following structure:
mongo-embedded-sdk-4.0.4
include lib share
mongo-embedded-sdk-4.0.4/include:
libbson-1.0 libmongoc-1.0 mongo_embedded mongoc_embedded
mongo-embedded-sdk-4.0.4/include/libbson-1.0:
bson bson.h
mongo-embedded-sdk-4.0.4/include/libbson-1.0/bson:
bcon.h bson-context.h bson-json.h bson-oid.h bson-value.h
bson-atomic.h bson-decimal128.h bson-keys.h bson-reader.h bson-version-functions.h
bson-clock.h bson-endian.h bson-macros.h bson-string.h bson-version.h
bson-compat.h bson-error.h bson-md5.h bson-types.h bson-writer.h
bson-config.h bson-iter.h bson-memory.h bson-utf8.h bson.h
mongo-embedded-sdk-4.0.4/include/libmongoc-1.0:
mongoc mongoc.h
mongo-embedded-sdk-4.0.4/include/libmongoc-1.0/mongoc:
mongoc-apm.h mongoc-error.h mongoc-init.h mongoc-socket.h mongoc-topology-description.h
mongoc-bulk-operation.h mongoc-find-and-modify.h mongoc-iovec.h mongoc-ssl.h mongoc-uri.h
mongoc-change-stream.h mongoc-flags.h mongoc-log.h mongoc-stream-buffered.h mongoc-version-functions.h
mongoc-client-pool.h mongoc-gridfs-file-list.h mongoc-macros.h mongoc-stream-file.h mongoc-version.h
mongoc-client-session.h mongoc-gridfs-file-page.h mongoc-matcher.h mongoc-stream-gridfs.h mongoc-write-concern.h
mongoc-client.h mongoc-gridfs-file.h mongoc-opcode.h mongoc-stream-socket.h mongoc.h
mongoc-collection.h mongoc-gridfs.h mongoc-rand.h mongoc-stream-tls-libressl.h
mongoc-config.h mongoc-handshake.h mongoc-read-concern.h mongoc-stream-tls-openssl.h
mongoc-cursor.h mongoc-host-list.h mongoc-read-prefs.h mongoc-stream-tls.h
mongoc-database.h mongoc-index.h mongoc-server-description.h mongoc-stream.h
mongo-embedded-sdk-4.0.4/include/mongo_embedded:
v1
mongo-embedded-sdk-4.0.4/include/mongo_embedded/v1:
mongo_embedded
mongo-embedded-sdk-4.0.4/include/mongo_embedded/v1/mongo_embedded:
mongo_embedded.h
mongo-embedded-sdk-4.0.4/include/mongoc_embedded:
v1
mongo-embedded-sdk-4.0.4/include/mongoc_embedded/v1:
mongoc_embedded
mongo-embedded-sdk-4.0.4/include/mongoc_embedded/v1/mongoc_embedded:
mongoc_embedded.h
mongo-embedded-sdk-4.0.4/lib:
cmake libbson-1.0.so.0 libmongo_embedded.so libmongoc-1.0.so.0 libmongoc_embedded.so
libbson-1.0.so libbson-1.0.so.0.0.0 libmongoc-1.0.so libmongoc-1.0.so.0.0.0 pkgconfig
mongo-embedded-sdk-4.0.4/lib/cmake:
libbson-1.0 libmongoc-1.0
mongo-embedded-sdk-4.0.4/lib/cmake/libbson-1.0:
libbson-1.0-config-version.cmake libbson-1.0-config.cmake
mongo-embedded-sdk-4.0.4/lib/cmake/libmongoc-1.0:
libmongoc-1.0-config-version.cmake libmongoc-1.0-config.cmake
mongo-embedded-sdk-4.0.4/lib/pkgconfig:
libbson-1.0.pc libmongoc-1.0.pc
mongo-embedded-sdk-4.0.4/share:
doc mongo-c-driver
mongo-embedded-sdk-4.0.4/share/doc:
mongo_embedded mongoc_embedded
mongo-embedded-sdk-4.0.4/share/doc/mongo_embedded:
LICENSE-Community.txt LICENSE-Embedded.txt THIRD-PARTY-NOTICES
mongo-embedded-sdk-4.0.4/share/doc/mongoc_embedded:
LICENSE-Community.txt LICENSE-Embedded.txt
mongo-embedded-sdk-4.0.4/share/mongo-c-driver:
uninstall.sh
When I installed it from a package I just had to run
dbPath="/home/pi/app/mongodb_data"
mongod --dbpath "$dbPath" &
Question:
How can I launch the MongoDB to listen on a port?
The tutorial you have followed is for building MongoDB as a library to embed in your application (aka MongoDB Mobile). This embedded build does not provide a standalone server daemon (mongod); you have to link this library directly into your application. The output of the embedded SDK build is the required development header files (include/*.h) and compiled library files (lib/*.so).
For more context, see the original blog post related to the repo you found: Embedded MongoDB 4.0 on Raspberry Pi.
How can I launch the MongoDB to listen on a port?
This requires a build of the normal MongoDB community server. You could try to follow the server build instructions on Build MongoDB from source or look for a precompiled binary for your O/S distro.
Note that Raspberry Pi isn't a generally supported target for the server so you will likely encounter some challenges (particularly on 32-bit O/S). The standard MongoDB server is designed to run on 64-bit hardware with more resources than are typical on a Pi.
I'm recompiling my project (https://github.com/warpme/minimyth2) to rpi3 (aarch64).
I have all components compiled and now I'm trying to boot it on rpi3.
I'm using u-boot script from arm archlinux with replaced kernel image (Image.gz) and rootfs from my compilation
kernel boots.
Also I see also on console, kernel mounts OK 2nd partition (my rootfs content is here).
but later kernel log says:
Starting init: /sbin/init exists but couldn’t execute it (error -13)
Starting init: /sbin/sh exists but couldn’t execute it (error -13)
Accordingly to https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/include/uapi/asm-generic/errno-base.h?h=v4.16.14 "error -13" means EACCES 13 /* Permission denied */.
I double checked: both files are root:root and 755 (their dependencies as well). What else can cause EACCES here?
u-boot script is following:
# Set root partition to the second partition of boot device
part uuid ${devtype} ${devnum}:2 uuid
setenv bootargs console=ttyS1,115200 console=tty0 root=PARTUUID=${uuid} rw rootwait debug loglevel=7 smsc95xx.macaddr="${usbethaddr}"
if load ${devtype} ${devnum}:${bootpart} ${kernel_addr_r} /Image; then
if load ${devtype} ${devnum}:${bootpart} ${fdt_addr_r} /dtbs/${fdtfile}; then
if load ${devtype} ${devnum}:${bootpart} ${ramdisk_addr_r} /initramfs-linux.img; then
booti ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r};
else
booti ${kernel_addr_r} - ${fdt_addr_r};
fi;
fi;
fi
so I think rootfs is mounted as rw
If anybody wants to look on my files, here are boot and rootfs partitions content:
hxxp://warped.inet2.org/boot.tar.bz2
hxxp://warped.inet2.org/root.tar.bz2
So summarising:
1\at rootfs mounting phase kernel says
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
2\ kernel is able to find init (and fallback to sh due failed init execution) as kernel says
Starting init: /sbin/init exists but couldn't execute it (error -13)
Starting init: /sbin/sh exists but couldn’t execute it (error -13)
3\adding "rootflags=exec" to kernel command line cause mount of root fails.
For me it seems my kernel config is somehow broken as it is able to mount but can't execute on it.
Attaching my kernel cfg http://warped.inet2.org/kernel-config.tar.bz2) (pls look at linux-4.16.13-arm64-armv8.config)
Can somebody can look on it and verify is such config enough to mount rootfs without any initrd? (to confirm: I want mount SD card ext4 rootfs straight from kernel image).
Alternatively: can somebody provide me minimal aarch64 kernel config enough to U-boot rpi3 with generic 4.16 kernel with rootfs on SD ext4 partition and without any initrd?
(PS: My kernel config is based on archlinux aarch64 multiplatform kernel and is 99.9% equal to archlinux arm)
(below is screenshot form kernel log)
boot screenshot
It looks like issue was in glibc.
I build with 2.17 and despite it is marketed as "first glibc supporting aarch64" - it not works for me.
Upgrading glibc to 2.27 solves issue :-)
Thx everybody why tried help me with this!
I am using neo4j enterprise 3.0.3 version for windows. Following the operations manual 3.0, I have installed the neo4j service with bin\neo4j install-service. But I can't start it with bin\neo4j start. It said
Invoke-Neo4j : Failed to start service 'Neo4j Graph Database - neo4j (neo4j)'.
And I can't start the neo4j service in windows serice either. Maybe anyone have encountered this case before?
I had the same problem: I am using neo4j community 3.1.2 for windows and installed the service with the neo4j.bat file without any problems.Then i wanted to start the service with neo4j.bat and got the same error as you
I found a solution that worked for me. My neo4j files were in a folder, where the path to the folder contained spaces (C:\Program Files\Neo4j) Then i moved the folder one level up (C:\Neo4j).
After that i could start the service without problems.
Maybe this solution helps.
I am running neo4j on windows and in my case the crux of the issue was that there was an incompatibility between the installed versions of Java (32-bit) v/s OS version. The biggest clue that led me to this is the following set of lines in neo4j-service.2018-08-03 log file
[2018-08-03 14:55:42] [info] [ 1432] Starting service...
[2018-08-03 14:55:42] [error] [ 1432] %1 is not a valid Win32 application.
[2018-08-03 14:55:42] [error] [ 1432] Failed creating java C:\JavaNew\bin\server\jvm.dll
[2018-08-03 14:55:42] [error] [ 1432] %1 is not a valid Win32 application.
[2018-08-03 14:55:42] [error] [ 1432] ServiceStart returned 1
There are a fair number of potential issues, and I have made an attempt to compile all the issues with this,
Windows services cannot deal with service names in folders that have spaces; especially if there is another folder with the same name as the one with spaces.
For example - C:\Program Files... will have issues if C:\Program\Something...
To work around this, I put Neo4j in root folder c:\Neo4j
Get-Java.ps1 (under ..\bin\Neo4j-Management folder)looks in the path variable for 'JAVA_HOME' (usually found in *nix environments). If it does not find it here, it keeps looking in registry, and finally throws up its hand!
To deal with this, I simply put in a path variable. For a good measure, I uninstalled Java and re-installed Java in the root folder under C:\JavaNew
In retrospect, this step is probably not on part of the problem, and hence can be ignored. But I am leaving it here for completeness sake.
Invoke-Neo4j.ps1 (also under ..\bin\Neo4j-Management folder) has code that determines if the OS is 32-bit (or 64-bit). Based on this it determines if it should run prunsrv-i386.exe (32-bit) or prunsrv-amd64.exe (64-bit).
This has to match the Java version installed.
Upon running java -XshowSettings:all, and inspecting the sun.arch.data.model value (32, in my case), I realized that my OS is 64 bit and the Java version is 32-bit.
To deal with this, I put in code (very klugey!). I am sure there are much better ways to get to the same outcome, but this is what I used.
switch ( (Get-WMIObject -Class Win32_Processor | Select-Object -First 1).Addresswidth ) {
32 { $PrunSrvName = 'prunsrv-i386.exe' } # 4 Bytes = 32bit
#64 { $PrunSrvName = 'prunsrv-amd64.exe' } # 8 Bytes = 64bit COMMENTED as a workaround!!!
64 { $PrunSrvName = 'prunsrv-i386.exe' } # 8 Bytes = 64bit
Now, uninstall the neo4j service, install it, and start the service.
Hope this works for you.
neo4j console
Posting for latest versions > 4.x
I had the same issue using neo4j start, Neo4j console is the right command I was looking for. It is a web-based graph that acts as an interactive tutorial.
i had the same problem , after the neo4j worked for few weeks it stoop working (without any change that i made)
i have set java_home uninstall and install and now it works
neo4j-enterprise-3.3.4
I was also having weired issue as there was no error but neo4J service did not start.
[xx#ss1 bin]$ ./neo4j console
[xx#ss1 bin]$ .
The problem was with the permission on Java directory and I tried
chmod -R 777 jdk_directory
and problem got solved.
#neo4j #neo4jnotstarting