foxx1337
Members-
Posts
11 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
@Edgar did the replacement at a local hardware repair shop, you are the best!
-
Kernel - Internal Error Oops: 0000000096000004 [#1] PREEMPT SMP
foxx1337 replied to Abdul Badalambadad's topic in Rockchip
Thanks, I'm watching, bamboo. -
Kernel - Internal Error Oops: 0000000096000004 [#1] PREEMPT SMP
foxx1337 replied to Abdul Badalambadad's topic in Rockchip
My bet is that it's a DTB issue - so software. -
Kernel - Internal Error Oops: 0000000096000004 [#1] PREEMPT SMP
foxx1337 replied to Abdul Badalambadad's topic in Rockchip
I think it's the DTBs from Armbian. Joshua Riek's 5.10 works fine. -
Kernel - Internal Error Oops: 0000000096000004 [#1] PREEMPT SMP
foxx1337 replied to Abdul Badalambadad's topic in Rockchip
std::vector also zeroes it, also it's the 32 GB Rock 5Bs I think. -
Kernel - Internal Error Oops: 0000000096000004 [#1] PREEMPT SMP
foxx1337 replied to Abdul Badalambadad's topic in Rockchip
It's the memory. You'll notice that the machine with the Armbian kernels can't access more than 8-9 gigabytes. I have the same issue. The Ubuntu 5.10 kernels published by Joshua Riek work fine, not sure about Radxa's 6.1 yet. Type this into a file called test.cpp: #include <iostream> #include <vector> int main() { std::vector<unsigned char> test(29ull * 1024 * 1024 * 1024); std::cin.get(); return 0; } then launch htop in a session and type in a different session: g++ test.cpp ./a.out and watch the kernel die after 2-3 seconds when the vector gets to zeroing past the 8-9 gigabyte mark. 3 posts under this one - -
Thanks! I was wrong with the kernel - same panic happens also on the old 23.11.1-legacy Armbian with the vendor's 5.10.160 kernel. The one that works is Joshua Riek's Ubuntu build (still 5.10.160). Maybe DTB related?
-
I was getting kernel panics and discovered that my 32 GB Rock 5B Blue Edition just crashes when I try to malloc 8-9 gigabtes of memory. Is there a way to specify that this board has 32 GB ram? 5.10 works fine.
-
European mirrors still don't seem to offer anything on top of 23.0.2, or maybe manually editing sources around /etc/apt is the way, but then all proposed packages still appear as being testing versions. Check - it will take a while for packages to distribute through the mirrors.
-
No, they're not. On the other hand, I now think the mirror also doesn't have them, looking for linux-image-edge-meson64 in `Packages` at https://mirrors.xtom.de/armbian/dists/bullseye/main/binary-arm64/Packages shows me that the one I got installed is in fact the latest one. LE. do i need to switch my sources.list to "jammy"? LLE. I don't need "jammy". I see that a different mirror from our github (https://github.com/armbian/mirror) has newer kernels - https://mirror.albony.xyz/armbian/dists/bullseye/main/binary-arm64/Packages. That `Packages` contains 5.19 kernels for example. Today I learned to read the `Packages` files for clues . By the way, your mirror seems to have it all and updating with it worked just fine, thank you!
-
I don't understand why I can't update to 5.19. I just updated to various user-space Debian 11.5 packages, but I can't see any newer kernels. root@odo:/boot# apt policy linux-image-edge-meson64 linux-image-edge-meson64: Installed: 22.05.1 Candidate: 22.05.1 Version table: *** 22.05.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 100 /var/lib/dpkg/status 22.02.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0046 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0045 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0040 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0035 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0034 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0031 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0029 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0027 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0025 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0023 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk.0021 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.0-trunk 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.115 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.108 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.11.0-trunk.101 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages root@odo:/boot# apt policy linux-u-boot-odroidhc4-edge linux-u-boot-odroidhc4-edge: Installed: 22.05.3 Candidate: 22.05.3 Version table: *** 22.05.3 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 100 /var/lib/dpkg/status 22.05.2 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.05.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 22.02.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.8 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.6 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages 21.08.1 500 500 https://mirrors.xtom.de/armbian bullseye/main arm64 Packages I'm looking at https://mirrors.xtom.de/armbian/pool/main/l/ for example and I can see items such as https://mirrors.xtom.de/armbian/pool/main/l/linux-5.19.5-meson64/. How do I get my apt to see them?