technik007_cz
-
Posts
189 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by technik007_cz
-
-
I bought few Geobooks 1E and all had regardless distro same issue. Random hangups immediately or few minutes after boot finished or after few days of run or hours.
On Armbian distro after trying some other things I enabled kernel messages in sysctl.conf. And then I got something like, luckily immediately when login prompt appeared, :
rtw_8821ce 0000:01:00.0: failed to dequeue 4088 skb Tx queue 5, .... when laptop stopped responding to keyboard immediately afterwards.
After some research I found solution, plugged USB lan adapter, disabled wifi otherwise it would knocked system down a did these next steps to replace wifi driver and hopefully after reboot 4 of these laptops this driver seems to work better without hangups.
nano /etc/modprobe.d/rtw88_8821ce.conf && update-initramfs -k all -u
ADD NEXT LINES INTO OPENED FILE =>
blacklist rtw88_8821ce
options rtw88_core disable_lps_deep=y
options rtw88_pci disable_msi=y disable_aspm=yNEXT COMMANDS:
sudo apt update && sudo apt install bc module-assistant build-essential dkms git -y
cd /usr/src && git clone https://github.com/tomaspinho/rtl8821ce.git
cd rtl8821ce
sudo m-a prepare
sudo ./dkms-install.sh
sudo nano /etc/modprobe.d/rtw88_8821ce.conf
blacklist rtw88_8821cenote: it should work without "options" lines which I found elsewhere as solution to resolve this problem without driver update
-
Real cpu speeds are for dualcore up to 2.7Ghz and for quadcore about 2086Mhz.
-
I just found they are selling dual core version as-well:
https://www.ebay.co.uk/itm/166222468091?hash=item26b3a193fb:g:wf4AAOSwocdkrWqD
-
One more it consume about 0.8A during load so in theory it could work with different power adapter like 1A. And it is able to handle USB spindle hard drives or USB-C NVME SSD compare to some similar laptops but powered over 5V adapters with obviously have to fail due to high amps demand and long power cable resistance.
-
Hi, I just got 2 of these. Everything is fine but you need to order power adapter 12V 2A with 3.5mm x 1.35mm connector.
Unfortunately due to earlier version of BIOS compare to same looking GeoBook 1E but with dualcore Celeron N4020 it cannot boot from microSD card.
Speakers are rubbish but it could be good for some low powered machine projects.
And one advice. Do not change "Quick boot" option in BIOS setting or it will not boot and you will need to unplug battery to reset BIOS.
It work with both Windows 11 or Linux with no extra drivers mods needed. 5Ghz wifi and bluetooth also included.
-
Just tried latest Armbian 23.5 Jammy on 512MB version of Radxa Zero what about if it will start working (it has not worked on 512MB board yet) and unfortunately results are still same it will never pass u-boot booting process ending up restarting.
Other system images produced by Radxa work fine, both debian or ubuntu versions, even they are using older systems.Boards with 1GB and 2GB RAM which I have run fine with Armbian.
-
It should be followed with fsck.repair=yes
BTW it causes lot of problems when you have lots of boars suddenly powered off.
-
2 hours ago, Igor said:
Doesn't boot with 3A images?
If you mean Armbian Rock-3A images unfortunately these does not boot up. I tried few, downloaded from this site or compiled ones. Only green led was on and nothing on hdmi or serial terminal (except few broken letters).
Hopefully Radxa latest images are working fine but you must avoid upgrading kernel and firmware. I tested these 2: rock-3c_debian_bullseye_cli.img.xz and rock-3c_debian_bullseye_kde.img.xz
I got email explaining why firmware breaks, etc...
-
I messaged radxa developer yesterday and I got link to system images.
https://github.com/radxa-build/rock-3c/releases
-
Hi, I have got Rock-3C board recently. It is not Rockpi4 C.
Main difference compared to Rock-3A is missing pci-e connector form back of the board, soldered wifi module and only 5V input power.
There is no system available for this board.
Any ideas how to get this board working?
-
Banana Pi BPI-M1 budle
- Banana Pi BPI-M1
- black ABS case
- white ABS case
- 8gb sdcard with Armbian OS
- sata cable
- 2.5" 320gb hard drive
- wifi usb dongle
- power adapter 5V 2A with microUSB cable and UK plug
Banana Pi BPI-M2 Berry budle
- Banana pi BPI-M2
- black case
- microUSB cable
- power adapter 5V 2A with EU and UK plug
PINE A64 512MB BOARD bundle
- PINE A64 512MB
- white ABS case with custom made holes for 18650 battery
- microUSB cable
- power adapter 5V 2A with EU and UK plug
- thermistor 10kohm
- battery connector
- USB 3.0 LAN 1000/100/10 adapter
Olimex micro enclosure to fit 2.5" hdd
https://www.olimex.com/Products/OLinuXino/BOXES/BOX-MICRO-B/
- green variation + screws and rubber legs
- red variation + screws and rubber legs
Location of items is UK.
Sending worldwide.
Prefer to sell everything to one person.
-
Hi, mate in your case it would be beneficial to get output from LCD screen or serial line. For the first option you need HDMI cable and a TV or computer screen, for the second one USB to TTL serial cable.
Secondly I have run Banana Pi (the original one) and BananaPi Pro for years with Armbian distro, both Ubuntu or Debian and it is rock stable.
You may need to change verbosity of boot process. Look for "How to toggle verbose boot?" in Armbian Documentation.
-
I found root of my card not resized to maximum space available. Unfortunately when I run out of space.
Consider adding missing package btrfs-progs to minimal image or warn user when building of such system image is complete so user can resize root manually before the sd card is inserted.
-
Ou, great I found old script to download u-boot for my micro board. It does download, install and the u-boot version will be prevented (holded) from upgrades. So @Artenverho you are welcome to test this first before experimenting.
# linux-u-boot-micro-next=5.60 #
apt remove linux-u-boot-micro-current -y; \
cd /tmp && wget --no-check-certificate https://193.40.103.96/pool/main/l/linux-u-boot-micro-next/linux-u-boot-next-micro_5.60_armhf.deb \
&& dpkg -i linux-u-boot-next-micro_5.60_armhf.deb && \
for PACKAGE in linux-u-boot-micro-next; \
do apt-mark hold $PACKAGE; aptitude hold $PACKAGE; done -
In my case on my Olimex micro when I run those commands it is output like this:
aptitude search u-boot | grep micro
p linux-u-boot-micro-current - Uboot loader 2019.10
ih linux-u-boot-micro-next - Uboot loader 2018.05apt-cache policy linux-u-boot-micro-next
linux-u-boot-micro-next:
Installed: 5.60
Candidate: 5.60
Version table:
*** 5.60 100
100 /var/lib/dpkg/statusSo there is the only one version available, but you can still experiment with "current" version of kernel and u-boot or you can try "current" u-boot on "next" kernel if you want experiment. For changing kernel version it is good to do it via armbian-config tool.
-
Hi, you can display installed package via command:
aptitude search u-boot | grep micro
Then you can display version of selected package:
(ending could be -current or -dev, select one from output of previous command starting with "i" - like "installed")
apt-cache policy linux-u-boot-micro-next
Then you can test different version of u-boot via command like this:
apt-get install linux-u-boot-micro-next=5.90
You testing u-boot, so always shutdown your device completely between tests and remove power cable from it.
-
Al right, any news in this story?
-
You think Neko May was not patient enough?
-
What is voltage in any of USB ports during resizing?
Other distro eg Ubuntu Bionic works well? -
There is no reason why it should not work. H3 works like a charm.
Mostly it is bad usb cable or unsuitable power adapter. Or it could be unstable microsd card usb adapter. It is hard to say from this distance.
-
I found working u-boot for Lime2 running on Bionic, microsdcard and kernel 4.19.81
It is:https://apt.armbian.com/pool/main/l/linux-u-boot-lime2-next/linux-u-boot-next-lime2_5.38_armhf.deb
I tried to retest u-boot for emmc board and it did not work. I did it differently than last time when I had an microsd inserted and after reinstalling of u-boot was whole microsd copied to mmc.
In this test microsd was removed and booted from emmc. After few tries, reinstalls and reboots I found message from installer saying it wrote u-boot to /dev/mmclk0. Problem is this device does not exist. Emmc module is under /dev/mmcblk1.
So I need to extract binary file from *.deb package and write it manually or return back to previous method.
-
Test of Lime2
Ubuntu Bionic with Armbian Linux 4.19.81-sunxi
linux-u-boot-lime2-next=5.90 (latest) NOK
linux-u-boot-lime2-next=5.85 NOK
linux-u-boot-lime2-default=5.90 (latest) NOK
linux-u-boot-lime2-default=5.85 NOK
linux-u-boot-lime2-current=19.11.3 NOK
linux-u-boot-lime2-emmc-next=5.31 NOK
linux-u-boot-lime2-emmc-next=5.30 NOK
linux-u-boot-lime2-emmc-next=5.25 NOK
NOK - cannot finish reboot and reset of board is necessary
Interesting results, I could not find for my setup where I am using root on nfs and custom image working u-boot.
I will do more tests but with boot image on emmc and not on microsd like in this test.
Note: the first test where linux-u-boot-lime2-emmc-next=5.30 I found working for my setup is boot image placed on emmc. -
Firstly htop show 1 cpu only with linux-u-boot-micro-default versions 5.60 and 5.38. Secondly it causes the reboot problem.
Version linux-u-boot-micro-next=5.60 which is the latest now is OK and finishes reboot completely.
I will test lime2 soon...
-
I have had similar issues what somebody had on this forum but I cannot post reply because the topic is closed.
But I found solution. You need to downgrade u-boot with following commands.
For Olimex Micro:apt-get install linux-u-boot-next-micro=5.60
Tested on ARMBIAN 5.60 stable Ubuntu 18.04.3 LTS 4.19.84-sunxi
For Olimex Lime2:
apt-get install linux-u-boot-lime2-emmc-next=5.30
Tested on Ubuntu Bionic with Armbian Linux 4.19.81-sunxi
How can I change usb-disk driver "UAS" to "usb-storage" ?
in Beginners
Posted · Edited by technik007_cz
I had same problem with RTL9210 based NVME enclosure. But I could not find one of them boot.cmd or boot.scr.
So I did it old fashion way like on Raspbian OS and added usb-storage.quirks parameter into /boot/firmware/cmdline.txt and after reboot UAS driver was replaced with basic usb one.
Note: I tried to edit /boot/armbianEnv.txt but it did not work.