E: The repository 'http://repo.mobian-project.org bullseye Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

meybe change system to nevest?

firmware-ufi001c.zip

讯优D623刷机之后虽然有设备，但是连接不上192.168.68.1

你好，
我使用uz801_v2.1，在Android切卡完成，插入sim卡后，只能adb shell进入系统，而且内部所有功能几乎不可用
dmesg输出如下：




这是因为modem不可用的原因吗？

hi our stick (not sure what model number it is, we're blind, we can't check) comes up as Qualcomm HS-USB QDLoader 9008 (COM3), does anyone have stock images and instructions on how to restore this thing?

Is it possible to run the device from a regular AC to USB power adapter? When I try this, LEDs indicate connectivity for a while but the device is unreachable over a previously configured wifi (through which it is reachable when connected to a PC)

如同标题(

It seems the repository is gone pushing for a move to bookworm.
I am not sure what is the best way to deal with this issue.

I'm interested in using the modem to make/receive calls, remotely over SIP.

I understand the modem should expose an audio device - currently none are detected.

Seems that currently although the dts includes msm8916-modem.dtsi which defines the qcom,msm8916-qdsp6-sndcard compatible node, the corresponding drivers aren't included in the released kernel.

Suggestions?

如题？

anyone know how to change the imei on this modem? my LTE network won’t connect cause the IMEI is not registered in my country, need to change the imei to fix that. using “fastboot oem writeimei ” I don’t have any result. anyone can help?

Is it possible to use OpenStick enabled device as a display receiver/streamer?

See https://wiki.postmarketos.org/wiki/DIAL#OpenStick

hello,i finished the flash,and installed the octoprint,but found no ch340 driver at the debian system.try to download and make the driver,but a lot of errors. can anyone help about this

1. AdoptOpenJDK已更名为Adoptium，需要:

sudo mkdir /etc/apt/keyrings/
rm /etc/apt/sources.list.d/AdoptOpenJDK.list
wget -O - https://packages.adoptium.net/artifactory/api/gpg/key/public | sudo tee /etc/apt/keyrings/adoptium.asc
echo "deb [signed-by=/etc/apt/keyrings/adoptium.asc] https://mirrors.tuna.tsinghua.edu.cn/Adoptium/deb $(awk -F= '/^VERSION_CODENAME/{print$2}' /etc/os-release) main" | sudo tee /etc/apt/sources.list.d/adoptium.list

2. mobian 更新密钥

wget -qO - http://repo.mobian-project.org/mobian.gpg | sudo apt-key add -
wget -qO - http://repo.mobian-project.org/mobian.gpg.key | sudo apt-key add -

3. 建议把security的源也改成镜像源以提速

参考
https://www.joshuawise.com/horndis
https://github.com/jwise/HoRNDIS
https://github.com/TomHeaven/HoRNDIS
测试因特尔处理器，macOS Mojave 10.14.1 可以正常配置登录，
测试M1 pro处理器，macOS Monterey 12.4 没有配置成功

说起来怎么实现通话，以及能不能作为SIP网关使用

We haven't been able to get LTE working at all with this device running Debian. Does anyone have instructions and images to restore this device to stock? Thanks

mmcli -m 0 power state off, so cannot access 4G network

求教如何使WiFi棒子像树莓派一样通过WiFi连接在 局域网内用ssh访问（局域网内访问）。尝试连接WiFi但是一旦让棒子离开电脑USB口，就无法通过ssh访问，请问是不是要在nmtui界面设置？感谢！

I have created this issue to serve as an instruction on how to get Debian working properly on UZ801 V3.0 boards.

I have recently acquired a couple of these from Aliexpress. One is left in stock condition, other is flashed with Debian.
This model appears to be pretty recent, the firmware build in it is dated February 2023. A quick google search shows someone has already made DTS files to support this model.
The rootfs from debian.zip file mostly works fine but requires some tweaks:

1. For modem to work, you will need to dump modem firmware files from stock ROMs modem partition and copy them to /lib/firmware
   You need the following files: modem.* mba.mbn and likely also mcfg_sw.mbn (located in image/modem_pr, region specific).
   I would also suggest dumping and copying the WiFi firmware files (wcnss.*) as well.
   I'm not absolutely sure if these are also board specific but they do work fine in AP mode. I didn't test AP mode with the original files.
   With firmware files installed, LTE modem works fine.

2. For WiFi to work in AP mode, you need to dump the NVRAM file /persist/WCNSS_qcom_wlan_nv.bin from the stock ROM and copy it to /lib/firmware/wlan/prima/. NVRAM file provided in the image only works in client mode without crashing.

3. LEDs in the platform driver are not mapped correctly and do not work. You can manually toggle LEDs by exporting GPIO pins 6, 7 and 8 (offset is 390) as output and toggling their values. Proper integration requires a kernel rebuild.
   Restart button is GPIO pin 23 active low.

Other than the LEDs, everything works fine. The OS appears to be stable so far.
I will recompile the kernel with fixed LEDs (and probably also the reset button) and upload it here later.
If anyone needs files from the stock ROM for Modem and WiFi, I can also upload them here.

Information source:
https://lore.kernel.org/lkml/[email protected]/T/

在《解决debian rndis与wifi热点共存的问题》中，第三行的注意事项是建议提前连好网，但实际上并不需要如此操作，即使操作错误也可以较为轻松恢复，文中不知道这么操作是有什么考量？

只要利用adb工具就好——系统安装后默认就有adb

同时建议该配网过程直接使用 adb 来进行。

首先将网卡插入电脑 USB 插口，然后在控制台执行adb shell ，如报 adb命令不存在 等问题，直接找到 adb.exe 所在路径执行 ./adb.exe shell （有点废话但是还是提一下）

之后操作和原教程一致，可忽略中途检测步骤，全部操作完再检查也行，就算配烂了也不会失去控制。

我使用的USB网卡型号在lsusb里查看为
Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter

百度谷歌都翻了，没有一篇有用的文章（ < linux小白 ）

如何关闭4G,USB设定成主机,甚至是CPU降频来节能。
这样可以配置成打印机服务器或者插到其他设备上当无线服务器。

想做短信转发
ModemManager会自动打开4G数据
qmicli --help-all
mmcli --help-all
/usr/sbin/ModemManager -h
查了一下午没研究明白, 辛苦大家帮我看看

/lib/systemd/system/ModemManager.service

Hi, thanks for the awesome work!
I seem to have corrupted my stick after it already worked - now I am able to boot into EDL mode, but I'm not sure what I should flash.
Could you advise me how I could recover my stick?

Thank you so much!!

板子是ufi003，改了内核设备树切卡IO解决了不认卡的问题，覆盖了firmware解决了能读卡但状态不是disable就是enabling的问题，现在已经是connected.

但是依然无法ping通公网地址

ifconfig中，wwan只有两个inet6地址，没有inet4地址

还有个问题，按照我第一段的说法改完后，现在每次开机后基带都会崩溃一次

[ 8.439336] wcn36xx: firmware API 1.5.1.2, 41 stations, 2 bssids

Debian GNU/Linux 11 openstick ttyMSM0

openstick login: [ 24.115031] qcom-q6v5-mss 4080000.remoteproc: fatal error received: sys_m.c:603:THIS IS INTENTIONAL RESET, NO RAMDUMP EXPECTED, smp2p write ret =
[ 24.115091] remoteproc remoteproc0: crash detected in 4080000.remoteproc: type fatal error
[ 24.127186] remoteproc remoteproc0: handling crash #1 in 4080000.remoteproc
[ 24.135353] remoteproc remoteproc0: recovering 4080000.remoteproc
[ 25.915463] qcom-wcnss-pil a204000.remoteproc: unexpected response to sysmon event
[ 25.915505] remoteproc remoteproc0: stopped remote processor 4080000.remoteproc
[ 25.922909] qcom-wcnss-pil a204000.remoteproc: unexpected response to sysmon event
[ 25.975040] qcom-q6v5-mss 4080000.remoteproc: MBA booted without debug policy, loading mpss
[ 26.562359] remoteproc remoteproc0: remote processor 4080000.remoteproc is now up
[ 26.646387] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:3
[ 26.647029] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:4
[ 26.654954] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:7
[ 26.664138] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:8
[ 26.673383] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:9
[ 26.682407] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:a
[ 26.691611] qcom,apr remoteproc0:smd-edge.apr_audio_svc.-1.-1: Adding APR dev: aprsvc:apr-service:4:b
[ 27.189879] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 0
[ 27.189986] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 1
[ 27.195797] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 2
[ 27.202511] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 3
[ 27.209273] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 4
[ 27.216041] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 5
[ 27.222818] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 6
[ 27.229577] bam-dmux 4080000.remoteproc:bam-dmux: Channel already open: 7

登陆进去后mmcli会查不到modem设备，尝试使用systemctl restart ModemManager重启服务，等一下就可以找到modem设备了，之后lte就自动连接上了。不知道这个崩溃和重启的操作是不是导致没有ip的原因？这张卡是没问题的我手机在用的。

Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter

in Debian, using ModemManager, the modem is forever "disabled" or "enabling". Syslog is flooded with errors indicating the modem reboots on an endless loop. any way to fix?

有没有办法可以自己移植到其他的发行版，比如Alpine Linux。Debian默认的资源占用相对还是比较高的（该死的systemd），所以想刷Alpine到棒子上，但是一直没有搜索到相关的教程资源。

此外能提供一个纯粹的服务器模式内核吗？就是完全屏蔽modem相关设备，并且把为其保留的内存也节省出来。

Hi! I see that you've ported the msm8916-mainline Linux kernel to OpenStick, nice job! Would it be possible for you to upstream your commits to msm8916-mainline's Linux kernel to make it easier for distributions shipping that kernel to support OpenStick?

刷机过程一切正常，使用nmtui也可以正常连接路由器，ifconfig显示连接信息也正常，但ping不通任何地址，包括路由器地址，并且路由器下的其它设备也ping不通OpenStick，可以帮助一下么，万分感谢
（这里是OpenStick ping 路由器的输出）
From 192.168.71.137 icmp_seq=2 Destination Host Unreachable

自带的4G容量太少了，一下子就满了。虽然有焊接内存颗粒扩容的办法，但是对手残党来说又太困难。
找到了一个可用的USB拓展坞，可以插入U盘。
请问怎么把外置U盘设定为默认的系统盘，安装程序时都自动安装到外部空间。（有点linux小白的问题，希望能得到大大们的解答）

如何修改系统默认设置，wifi及其密码等等？

I was super excited to see this awesome hack (thank you for all the notes, they are awesome!) and found a promising stick that I purchased from alibaba; the primary chip checks out – MSM8916 and going by the markings on the hynix chip next to it, it seems to be a 512MB RAM, 4GB eMMC chip, so I was feeling lucky.

But the challenge is, I’m not able to get an adb connection to it. The device is pingable and UI is accessible on 192.168.100.1, now here’s something new – there is no “upgrade” function in the UI either and after a bit of tinkering, found it is running a Eclipse Jetty webserver, rather than I what I can guess the others are running – an android app.

I also tried doing a port scan, but that didnt yield any other open port than port 80 (for UI) and port 53 (for DNS).

Starting Nmap 7.80 ( https://nmap.org ) at 2022-08-25 14:17 +08
Nmap scan report for 192.168.100.1
Host is up (0.0096s latency).
Not shown: 65533 closed ports
PORT   STATE SERVICE VERSION
53/tcp open  domain  dnsmasq 2.51
| dns-nsid: 
|_  bind.version: dnsmasq-2.51
80/tcp open  http    Jetty 8.y.z-SNAPSHOT
|_http-server-header: Jetty(8.y.z-SNAPSHOT)
|_http-title: 4G Modem

On connecting to USB, it lists as a RNDIS device, disconnects and reconnects again in a few seconds (this doesnt seem to be power related as I have tried it with a few different computers, and also, the reconnect is pretty fast ~0.25s - so it may be some mode switching internally i think)

[Aug20 15:04] usb 3-8.1.4: new high-speed USB device number 41 using xhci_hcd
[ +0.101530] usb 3-8.1.4: New USB device found, idVendor=05c6, idProduct=f00e, bcdDevice=ff.ff
[ +0.000010] usb 3-8.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ +0.000003] usb 3-8.1.4: Product: Android
[ +0.000002] usb 3-8.1.4: Manufacturer: Android
[ +0.000002] usb 3-8.1.4: SerialNumber: 0123456789ABCDEF
[ +0.006808] rndis_host 3-8.1.4:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-8.1.4, RNDIS device, ce:12:d8:cd:30:e0
[ +8.630068] usb 3-8.1.4: USB disconnect, device number 41
[ +0.000192] rndis_host 3-8.1.4:1.0 usb0: unregister ‘rndis_host’ usb-0000:00:14.0-8.1.4, RNDIS device
[ +0.257230] usb 3-8.1.4: new high-speed USB device number 42 using xhci_hcd
[ +0.100923] usb 3-8.1.4: New USB device found, idVendor=05c6, idProduct=f00e, bcdDevice=ff.ff
[ +0.000009] usb 3-8.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ +0.000004] usb 3-8.1.4: Product: Android
[ +0.000002] usb 3-8.1.4: Manufacturer: Android
[ +0.000002] usb 3-8.1.4: SerialNumber: 0123456789ABCDEF
[ +0.004680] rndis_host 3-8.1.4:1.0 usb0: register ‘rndis_host’ at usb-0000:00:14.0-8.1.4, RNDIS device, 3e:d1:02:cf:1d:75

And lsusb to lists a single device

$ lsusb | grep 05c6
Bus 003 Device 062: ID 05c6:f00e Qualcomm, Inc.

I have tried adb wait-for-any-recovery && adb reboot bootloader to see if that helps with catching the stick during its boot up and also during the factory reset (via UI).

I’m a fairly new to adb / android rooting and perhaps I’m missing something very obvious – any insights? Perhaps this PCB, which seems to be a UZ801 clone (FY_UZ801_V2.1) has some test points which I could short to force boot into boot loader? I did try probing the test points for UART console by connecting an serial RX line to them - no luck there.

Photos for reference -
PCB:

Enclosure:

please move /var/log to memory tmpfs

Hi, i recently flash this image with no base knowledge, show i didn't dump and back up.
I got the system running, overal is good. But my plan was to use the LTE on it.
I tried read some old issue but no luck
#20
@ddscentral Currentlly i only have 1 stick with debian on it. Any idea? I try the qmiclicommand above but onloy geterror: could not power on SIM: QMI protocol error (3): 'Internal'`

在我更新设备之前它工作正常，但之后它无法检测到卡:

root@openstick:/# mmcli -m 0

General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 1ec3156c870d523e616cee0ef4dcf0676f78xxxx

Hardware | manufacturer: 1
| model: 0
| firmware revision: MPSS.DPM.2.0.2.c1-00178-M8936FAAAANUZM-1D 1 [Nov 04 2016 02:00:00]
| carrier config: ROW_Generic_3GPP
| carrier config revision: 02010801
| h/w revision: 10000
| supported: gsm-umts, lte
| cdma-evdo, lte
| lte
| cdma-evdo, gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 86176603523xxxx

System | device: qcom-soc
| drivers: qcom-q6v5-mss, bam-dmux
| plugin: qcom-soc
| primary port: wwan0qmi0
| ports: wwan0 (net), wwan0at0 (at), wwan0qmi0 (qmi), wwan1 (net),
| wwan2 (net), wwan3 (net), wwan4 (net), wwan5 (net), wwan6 (net),
| wwan7 (net)

Status | state: failed
| failed reason: sim-missing
| power state: off
| signal quality: 0% (cached)

Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 2g, 3g; preferred: 3g
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: 2g
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 2g
| current: allowed: any; preferred: none

Bands | supported: egsm, dcs, pcs, g850, utran-1, utran-5, utran-8, eutran-1,
| eutran-3, eutran-5, eutran-8, cdma-bc0

IP | supported: ipv4, ipv6, ipv4v6
root@openstick:/#

The project that you fork the kernel from also has qhypstub that would allow for u-boot, EL2, KVM, etc.

I assume that some amount of work might need to be done in u-boot?

I flashed the debian image on my stick, got ssh and wifi working, LTE keeps getting errors:

[sudo] password for didi: 
error: couldn't connect the modem: 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.DeviceNotReady: Couldn't set operating mode: QMI protocol error (52): 'DeviceNotReady''

With qmicli I'm able to get imsi, but after I do, modem manager doesn't see a modem.
It seems that I have a different model, UFI-7718, or is that just a random number for the original SSID?
Any idea what causes the device not ready issue? Looking over the logs, I didn't see anything apart from it attempting to start, and stop.

Hi all,

when I start the first flash of "base-generic" bootloader I get the following errors in the terminal window:

Erasing 'boot' OKAY [ 0.105s]
Finished. Total time: 0.118s
fastboot: error: cannot load 'aboot.bin': No such file or directory
Rebooting OKAY [ 0.009s]
Finished. Total time: 1.214s
FAILED (remote: 'Use 'fastboot oem dump on/off'')
fastboot: error: Command failed
FAILED (remote: 'Use 'fastboot oem dump on/off'')
fastboot: error: Command failed
FAILED (remote: 'Use 'fastboot oem dump on/off'')
fastboot: error: Command failed
FAILED (remote: 'Use 'fastboot oem dump on/off'')
fastboot: error: Command failed
Erasing 'boot' OKAY [ 0.106s]
Finished. Total time: 0.112s
Rebooting into bootloader OKAY [ 0.016s]
Finished. Total time: 0.771s
fastboot: error: cannot load 'gpt_both0.bin': No such file or directory
fastboot: error: cannot load 'hyp.mbn': No such file or directory
fastboot: error: cannot load 'rpm.mbn': No such file or directory
fastboot: error: cannot load 'sbl1.mbn': No such file or directory
fastboot: error: cannot load 'tz.mbn': No such file or directory
fastboot: error: cannot load 'fsc.bin': No such file or directory
fastboot: error: cannot load 'fsg.bin': No such file or directory
fastboot: error: cannot load 'modemst1.bin': No such file or directory
fastboot: error: cannot load 'modemst2.bin': No such file or directory
fastboot: error: cannot load 'aboot.bin': No such file or directory
fastboot: error: cannot load 'sbc_1.0_8016.bin': No such file or directory
Erasing 'boot' OKAY [ 0.105s]
Finished. Total time: 0.112s
Erasing 'rootfs' FAILED (remote: 'Partition table doesn't exist
')
fastboot: error: Command failed
Rebooting OKAY [ 0.004s]
Finished. Total time: 0.758s
all done please flash your os!

I already tried diffrent ports (usb 2.0) and redownloading the zip packages .. no success .. any ideas what to try to get it correctly flashed ?

Will there be kernel updates for OpenStick? I tried building Linux 6.1 (latest non alpha upstream) with the OpenStick DTBs. It appears to boot, but appears to hang before it gets into the OS :(

Also, is it possible to use fs_boot in lk2nd and do away with the separate boot and rootfs (like pmOS) to potentially make it easier to update kernel images?

Hi,

I have a board labeled like: UFI003_MB_V02

WIth basegeneric + debian (with boot-ufi001c) and with firmware-ufi001c in /lib/firmware this is my modem state:

root@openstick:/# mmcli -m 0
  -----------------------------------
  General  |                    path: /org/freedesktop/ModemManager1/Modem/0
           |               device id: d2d26e98cf83bb747f5146730fc87deed4b2668c
  -----------------------------------
  Hardware |            manufacturer: 1
           |                   model: 0
           |       firmware revision: UFI001CT 20211106  1  [Nov 04 2016 02:00:00]
           |          carrier config: ROW_Generic_3GPP
           | carrier config revision: 02010801
           |            h/w revision: 10000
           |               supported: gsm-umts, lte
           |                 current: gsm-umts, lte
           |            equipment id: 864405024697373
  -----------------------------------
  System   |                  device: qcom-soc
           |                 drivers: qcom-q6v5-mss, bam-dmux
           |                  plugin: qcom-soc
           |            primary port: wwan0qmi0
           |                   ports: wwan0 (net), wwan0at0 (at), wwan0qmi0 (qmi), wwan1 (net),
           |                          wwan2 (net), wwan3 (net), wwan4 (net), wwan5 (net), wwan6 (net),
           |                          wwan7 (net)
  -----------------------------------
  Status   |                    lock: sim-pin2
           |          unlock retries: sim-pin (1), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
           |                   state: enabled
           |             power state: on
           |          signal quality: 0% (cached)
  -----------------------------------
  Modes    |               supported: allowed: 2g; preferred: none
           |                          allowed: 3g; preferred: none
           |                          allowed: 4g; preferred: none
           |                          allowed: 2g, 3g; preferred: 3g
           |                          allowed: 2g, 3g; preferred: 2g
           |                          allowed: 2g, 4g; preferred: 4g
           |                          allowed: 2g, 4g; preferred: 2g
           |                          allowed: 3g, 4g; preferred: 4g
           |                          allowed: 3g, 4g; preferred: 3g
           |                          allowed: 2g, 3g, 4g; preferred: 4g
           |                          allowed: 2g, 3g, 4g; preferred: 3g
           |                          allowed: 2g, 3g, 4g; preferred: 2g
           |                 current: allowed: 3g, 4g; preferred: 4g
  -----------------------------------
  Bands    |               supported: egsm, dcs, pcs, g850, utran-1, utran-5, utran-8, eutran-1,
           |                          eutran-3, eutran-5, eutran-8
           |                 current: egsm, dcs, pcs, g850, utran-1, utran-5, utran-8, eutran-1,
           |                          eutran-3, eutran-5, eutran-8
  -----------------------------------
  IP       |               supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP     |                    imei: <REDACTED>
           |           enabled locks: fixed-dialing
  -----------------------------------
  3GPP EPS |    ue mode of operation: csps-1
           |      initial bearer apn: telefonica.es
           |  initial bearer ip type: ipv4
           |     initial bearer user: telefonica
           | initial bearer password: telefonica
  -----------------------------------
  SIM      |        primary sim path: /org/freedesktop/ModemManager1/SIM/0

What is the best combination of drivers for UFI003_MB_V02? Now is always in "signal quality: 0%" and I can't connect with the modem.

Thanks

当前v1版本，预留了约170MB内存给驱动，系统无法使用。

Memory: 350280K/524288K available (9664K kernel code, 1212K rwdata, 3644K rodata, 1728K init, 358K bss, 141240K reserved, 32768K cma-reserved)

如果不需要使用4G功能以及相关驱动，是否可以不预留这些内存，谢谢。

只在仓库上层目录.看到两个deb包

linux-headers-5.15.0-handsomekernel+_5.15.0-handsomekernel+-10.00.Custom_arm64.deb
linux-image-5.15.0-handsomekernel+_5.15.0-handsomekernel+-10.00.Custom_arm64.deb

搜索文件夹是没有rootfs.img,这个文件是不是刷机包里面那个?

另外求编译带cdc-acm 驱动的版本(我看最近有人PULL这个了.),
我自己编译内核就是为了装这个.但是我看了下,编译出来.好像只有cnc-acm.o文件,而不是.ko后缀的.

File

boot-uf896.zip

Instructions:

# dmesg | head -3
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd030]
[    0.000000] Linux version 5.15.0-handsomekernel+ (guo@guo-Server) (aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #17 SMP PREEMPT Sun Feb 6 22:10:37 CST 2022
[    0.000000] Machine model: Handsome Openstick
# unzip boot-uf896.zip
# ls -l boot-uf896.img
-rw-r--r-- 1 pi pi 13586432 Dec 15 19:33 boot-uf896.img
# parted /dev/mmcblk0 print
Model: MMC H4G2a (sd/mmc)
Disk /dev/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name      Flags
 1      67.1MB  67.1MB  2048B                cdt
 2      134MB   135MB   524kB                sbl1
 3      135MB   135MB   524kB                rpm
 4      135MB   136MB   1049kB               tz
 5      136MB   137MB   524kB                hyp
 6      137MB   137MB   16.4kB               sec
 7      137MB   139MB   2097kB               modemst1
 8      139MB   141MB   2097kB               modemst2
 9      141MB   141MB   1024B                fsc
10      201MB   203MB   2097kB               fsg
11      268MB   269MB   1049kB               aboot
12      269MB   337MB   67.1MB               boot
13      337MB   338MB   1049kB               devinfo
14      338MB   3909MB  3571MB  ext4         rootfs

# dd if=boot-uf896.img of=/dev/mmcblk0p12
# sync
# reboot

# dmesg | head -3
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd030]
[    0.000000] Linux version 5.15.0-handsomekernel+ (guo@guo-Server) (aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #17 SMP PREEMPT Sun Feb 6 22:10:37 CST 2022
[    0.000000] Machine model: Handsome OpenStick UF896-V1_1

LED(s)

Source code

OpenStick/linux#3

The model is uf896-v1_1. It got bricked somewhat slimier to (#9).
The After flashing debian, I upgraded the debian packages, rebooted and then left it plugged in for a couple of hours and then unplugged it.

Next time I plugged it in, it didn't boot. I couldn't get it to boot in adb, fastboot or edl modes. I tried different methoda people have described to get to edl mode(short GND and D+, short test pad 1 to test pad 6, etc), none of them worked.

I'm wondering if this is a power management issue, or if something tried to write to the qfuse regions or something.

Hi,

I have the generic-base flashed, but flashed a "bad" rootfs. Do you know how I can force this device into fasboot mode?

I have the board mentioned in this post: https://www.zianet.com/jgray/openstick/08Aug2022.html

I can't figure out how to get it into recovery fastboot mode.

Thanks for any advice.