OpenBSD 7.6 boots from SD (install.img) but hangs on "` booting sd0a:/bsd: 30587334+... ]=0x13f15e0" and makes the screen jiggle a lot, like the scan rates are changing and everything is taking one character jog left every few seconds.

Anyways, interesting experience. Not something ready out of the box. Will make some adjustments and report back if I have a bootable image.

I am wondering about buying one for xmas lol. I'm seeing very mixed opinions on here many problems. Is it even worth it to buy?

Hi, everyone--

For the first time, I've got two cellular phone lines and am able to play more with the PinePhone Pro.

I called the PPP running Mobian, and it woke properly from sleep, and the modem also woke properly, but it wakes so slowly that the incoming call has gone to voicemail without ever ringing. It does say "Missed call" on the lock screen afterward.

If the PPP is already awake, it rings and receives the call just fine, so all I need to figure out is how to get the modem to wake fast enough to receive the call.

Any tips are appreciated. I plan on updating Mobian to the latest package versions tomorrow. It's been many months since I last powered on the PPP, so whatever it is running now is old.

I also will apply any modem firmware updates if there are any newer ones.

If updating is a bad idea, please let me know.

Thanks!

Hi, I have been using my PineTab2 for around a year now and have been very satisfied with it. I used the factory image of Arch Linux ARM and really liked it (I use Arch as my main OS on PC for over 4 years). Yesterday, I once more checked the UBports Ubuntu Touch website for the PineTab2 to check for any changes or improvements. I decided to finally make the switch and see what the OS is like. From the pictures, I really liked the UI and the apps from the OpenStore.

I followed the documentation and downloaded the latest .raw file (https://ci.ubports.com/job/focal-hybris-...m64.raw.xz), extracted it, opened BalenaEtcher and flashed it to my SD card. Then I put it in the tablet, connected the UART, switched the maskrom switch to the ON position, and powered it on. After a few seconds, switch the maskrom switch back off so it can see the internal eMMC. I copied the .raw file to my USB flash drive and connected it to the tablet. Then I erased the internal storage (emmc) but left the /dev/mmcblk0boot0/1 alone and flashed the .raw from the usb drive to the internal storage. Powered off the tablet, disconnected UART and Sd card and boot up again. It boots into ubuntu touch. I complete the initial config, and it all works fine.

Then I power it off again (or reboot) and when I try to turn it on again, it does not do anything. Not even any output from the UART to minicom. Based on what I have read, I don't think it is even getting to the u-boot so that's why the screen is black. I tried reinstalling it, renaming the file from .raw to .img (as seguested by forum post) but nothing helped. I also noticed that I can't even boot the sd card for the second time after a reboot/shutdown.

The .raw/.img also has really weird partition structure when printed using fdisk (like the first 16MB partition that I think based on binwalk is just a binary file of the u-boot). But maybe that is normal and intended.

Hello all, 

I recently aquired a Pinephone Pro with Sailfish OS preinstalled. After playing with it for a while I decided I didn't really care for it, so I installed Towboot on it and flashed Manjaro with Plasma to the emmc. I really liked this one, so I got a T-moble sim card through tracfone. I was able to quickly activate the card without any issues at all, and phone calls and sms messages worked right off the bat. The modem would dissconnect periodically but would be back up in seconds. So over all a seamless experence. I then installed waydroid so I could run android apps, this also worked very well with no issues at all. I used the phone for about 3 days with no problems. Then last night after receving a text, things begain to act up. I kept “receving” the same text over and over again. As there was no sign of this stopping I restarted the phone and turned on airplane mode. The next day the phone would not send or recive calls or messages, it said the apn needed to be configured in order to inable moble data. I thought this was odd because I had already done this but I went to the settings and played around with the settings. I found out that the modem was disabled so I clicked the button to force modem restart, however this did nothing. After some searching around online I ran this command: “sudo mmcli -m any -e” this gave the following error: “ error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'” I then tried turning off and restarting the phone, at some point I ran the command again and this time it worked, and it inabled the modem. However, it still did not allow me to turn on moble data, or change the apn settings. After a minute or so the modem once again said it was disabled. So I tried the command again, and it reinabled it, then a little later it was disabled again. The same thing keeps happening except half the time it throws the error. I also noticed that the waydroid container stopped having internet access even when conected to wifi. I don't know if this is related at all but it happend around the same time as everything else. I cannot figure out how to fix either of these problems and I am new to moble linux, so any help would be very much appreciated. Thanks in advance.

I just received my PineTime Pine64 yesterday.

Upon arrival, the battery was at 0%, 3.10V.
I charged it yesterday, and the battery indicator went from 0% to 18% after 50 minutes, then to 54% and stuck.

Today, it dropped back to 0% this morning and won’t charge.
What are my options to get a working watch?
Thank you.

Two questions...
Firstly - I would like reports of people running Trixie unstable in late 2024 onward, is it ready for daily driving, how is phone audio, system stability, and phone call quality?  Is the camera working?

Secondly - the Mobian wiki does not give up-to-date instructions

https://wiki.debian.org/Mobian/FAQ#How_d...nstable.3F

here is what https://repo.mobian-project.org/  looks like now,

Hi everyone, I'm new to the forum and just got my hands on a ROCKPro64. I came across the suggestion about using an NVMe disk as rootfs, but I'm a bit confused about the process. Could someone provide a step-by-step guide on how to set this up? Specifically, I'm interested in any prerequisites and potential pitfalls to watch out for. Thanks in advance!

When I leave the uboot cmdline or grub cmdline open for a while, system or at least the keyboard becomes unresponsive.
It does not happen after Linux has started.
Happens on 2 different Uboot builds, the one from Towboot and the one from Fedora.
The type of bootloader does not matter, it happens in grub/syslinux too.

Can you help me investigate? Is this a known thing?

Hi, I've had my pinebook pro for a few years now and for the most part it did a pretty good job
sadly a few days ago i spilled coffee over the keyboard, and since then i cant get it to boot anymore.
after the spill i shut it down and tried to clean it off as good as i could, without opening up the case.

I started to do some troubleshooting, and hope someone here can help me with that, so that i can fix it, or at least order the proper replacement parts.

I have since opened it up, and noted some coffee stains in the lower shell, but luckily i could not find any on both the boards.
the battery seems to be in order as well, and removing it, closing the jumper and powering from socket produces equivalent results.

the only life sign i can see from the board is a blinking of the orange status light for a while after i (re)connect the flat-band cable to the keyboard
this only happens with the emmc module connected, and the switch enabled. An sd card with an linux image on it alone doesnt allow for blinking, the emmc seems to be necessary for it to occur.

My current theory is that some coffee must have come into the key nipples, shorting them and thus rendering the output unviable, i removed the keyboard from the upper case and tried to wash it as good as possible, it should be dry by know but it didnt help. sadly the keyboard uses a single nipple glued to each key, instead of a silicon mat like most full scale keyboards, so i cant be sure i cleaned it properly.

before ordering a replacement keyboard id like to make sure the mainboard is actually fine, but as the power button is part of the keyboard i dont know how i would be able to test that, is there some other way to power on the board that ive missed?