<![CDATA[PINE64 - BSD on Pinebook Pro]]> https://forum.pine64.org/ Thu, 16 Apr 2026 06:38:54 +0000 MyBB <![CDATA[OpenBSD 7.6]]> https://forum.pine64.org/showthread.php?tid=19541 Tue, 03 Dec 2024 20:23:08 +0000 elitegamercody]]> https://forum.pine64.org/showthread.php?tid=19541
Anyways, interesting experience. Not something ready out of the box. Will make some adjustments and report back if I have a bootable image.]]>
Anyways, interesting experience. Not something ready out of the box. Will make some adjustments and report back if I have a bootable image.]]> <![CDATA[2nd NetBSD boot goes dark]]> https://forum.pine64.org/showthread.php?tid=18868 Wed, 15 Nov 2023 17:25:03 +0000 donn]]> https://forum.pine64.org/showthread.php?tid=18868 <![CDATA[NetBSD 1.0 runs down battery]]> https://forum.pine64.org/showthread.php?tid=18864 Tue, 14 Nov 2023 12:01:22 +0000 donn]]> https://forum.pine64.org/showthread.php?tid=18864 http://nycdn.netbsd.org/pub/arm/



(NetBSD 9.3 and NetBSD 9 daily don't run - power light comes on and eventually goes off, followed several seconds later by a blink from the the other two lights, and that's it.)



But I can run it only as long as the battery lasts, because while I'm running NetBSD, the USB-C cable apparently doesn't charge the battery.  Eventually it runs down and crashes, and Linux shows the battery at 0%.



envstat shows only voltage, all other parameters are 0;  I could presumably infer charge state from voltage - looks like when we get down to 3.5V it's time to go back to Linux, but that could stand more research.



Is there a charging method that NetBSD supports?

[ edit ] Stuck my hand down in the paper bag packaging, and lo - I have a DC charger!  And it seems to be holding a charge now under NetBSD.  That is, still isn't getting charged, but I can run off the DC charger at 3.9V.  When I pull it out, the voltage drops to 3.5V, and percent to about the 68% it was when I left Linux, and dropping.
[ /edit ]]]> http://nycdn.netbsd.org/pub/arm/



(NetBSD 9.3 and NetBSD 9 daily don't run - power light comes on and eventually goes off, followed several seconds later by a blink from the the other two lights, and that's it.)



But I can run it only as long as the battery lasts, because while I'm running NetBSD, the USB-C cable apparently doesn't charge the battery.  Eventually it runs down and crashes, and Linux shows the battery at 0%.



envstat shows only voltage, all other parameters are 0;  I could presumably infer charge state from voltage - looks like when we get down to 3.5V it's time to go back to Linux, but that could stand more research.



Is there a charging method that NetBSD supports?

[ edit ] Stuck my hand down in the paper bag packaging, and lo - I have a DC charger!  And it seems to be holding a charge now under NetBSD.  That is, still isn't getting charged, but I can run off the DC charger at 3.9V.  When I pull it out, the voltage drops to 3.5V, and percent to about the 68% it was when I left Linux, and dropping.
[ /edit ]]]> <![CDATA[verifying the serial console]]> https://forum.pine64.org/showthread.php?tid=18153 Wed, 19 Apr 2023 23:33:36 +0000 js0000]]> https://forum.pine64.org/showthread.php?tid=18153
i have been trying to install openbsd on my pinebook pro (currently running a manjaro-i3 combo) and an at the point of verifying the serial console.

when i look on my linux (debian) box, i can see the usb connector (?)
Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converter

and can see it in dmesg (ttyUSB0)

the problem is actually sending something over- i have been unable to see anything with minicom on the other end
when i run a command like this (as root on the pinebook), i get nothing on minicom:
echo "console output" > /dev/console

and it just hangs on the pine box.

also (as i got my pinebook some time ago) it came with a cable, that i read was supposedly bad ... i tried that too, but nothing happened. the cable i am using was bought from the pine store, maybe a year-ish ago ...

i also opened the back and flicked the switch for the serial console out of headphone jack.

i guess what i'm looking for is how to verify that the link is working
or someway to know that my pinebook does not have fried hardware of one kind or another (diagnostic commands ok)

any help would be welcome

thx]]>
i have been trying to install openbsd on my pinebook pro (currently running a manjaro-i3 combo) and an at the point of verifying the serial console.

when i look on my linux (debian) box, i can see the usb connector (?)
Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converter

and can see it in dmesg (ttyUSB0)

the problem is actually sending something over- i have been unable to see anything with minicom on the other end
when i run a command like this (as root on the pinebook), i get nothing on minicom:
echo "console output" > /dev/console

and it just hangs on the pine box.

also (as i got my pinebook some time ago) it came with a cable, that i read was supposedly bad ... i tried that too, but nothing happened. the cable i am using was bought from the pine store, maybe a year-ish ago ...

i also opened the back and flicked the switch for the serial console out of headphone jack.

i guess what i'm looking for is how to verify that the link is working
or someway to know that my pinebook does not have fried hardware of one kind or another (diagnostic commands ok)

any help would be welcome

thx]]> <![CDATA[How to install OpenBSD on the PBP?]]> https://forum.pine64.org/showthread.php?tid=17517 Wed, 26 Oct 2022 21:22:24 +0000 BenniTec]]> https://forum.pine64.org/showthread.php?tid=17517
I have tried all day to install OpenBSD 7.2, 6.9 and 6.7 on my Pinebook Pro.
When I flash the installer*.img or miniroot*.img onto my usb-stick or SD card
and apply the necessary dtb and u-boot patching described in https://ftp.openbsd.org/pub/OpenBSD/7.2/...TALL.arm64,
the PBP starts into boot(8) and no matter what I try (eg. `set tty fb0` and/or `boot /bsd.rd` and/or `machine dtb ...`)
I get a flashing screen and nothing happens.

1: Do I need to buy a serial cable to install it or am I doing something wrong?
2: Does anyone have a working installer or image that works without a serial cable?
3: Is there some other way of installing it instead, eg. over ssh with an ethernet adapter (Pinephone USB-C dongle)?]]>
I have tried all day to install OpenBSD 7.2, 6.9 and 6.7 on my Pinebook Pro.
When I flash the installer*.img or miniroot*.img onto my usb-stick or SD card
and apply the necessary dtb and u-boot patching described in https://ftp.openbsd.org/pub/OpenBSD/7.2/...TALL.arm64,
the PBP starts into boot(8) and no matter what I try (eg. `set tty fb0` and/or `boot /bsd.rd` and/or `machine dtb ...`)
I get a flashing screen and nothing happens.

1: Do I need to buy a serial cable to install it or am I doing something wrong?
2: Does anyone have a working installer or image that works without a serial cable?
3: Is there some other way of installing it instead, eg. over ssh with an ethernet adapter (Pinephone USB-C dongle)?]]> <![CDATA[Booting NetBSD]]> https://forum.pine64.org/showthread.php?tid=17197 Mon, 22 Aug 2022 08:19:19 +0000 untitled]]> https://forum.pine64.org/showthread.php?tid=17197
Now have trouble booting up the installed system. Tow-Boot on SPI complains

"Wrong image format for "source" command."
"Can't get kernel image!"

I reinstalled kernel just to be sure

Code:
install -o root -g wheel -m 555 netbsd-GENERIC64 /netbsd

and wrote u-boot into boot sector

Code:
dd if=/usr/pkg/share/u-boot/rksd_loader.img of=/dev/rld0 seek=64 conv=sync

Also copied everything in /boot of the SD card to /boot on eMMC.

Still no luck, the system won't boot.]]>
Now have trouble booting up the installed system. Tow-Boot on SPI complains

"Wrong image format for "source" command."
"Can't get kernel image!"

I reinstalled kernel just to be sure

Code:
install -o root -g wheel -m 555 netbsd-GENERIC64 /netbsd

and wrote u-boot into boot sector

Code:
dd if=/usr/pkg/share/u-boot/rksd_loader.img of=/dev/rld0 seek=64 conv=sync

Also copied everything in /boot of the SD card to /boot on eMMC.

Still no luck, the system won't boot.]]> <![CDATA[NetBSD on the Pinebook Pro in August 2022 - or not?]]> https://forum.pine64.org/showthread.php?tid=17180 Sat, 20 Aug 2022 00:52:36 +0000 KC9UDX]]> https://forum.pine64.org/showthread.php?tid=17180
I bought another PinebookPro.  I have a microSD card with NetBSD 9.0 on it that I used as sort of a rescue boot for my other PinebookPro (which runs NetBSD 9.1).  I know that it works because I booted the old PBP with it, to make an image of the eMMC, so that I could make the new PBP a clone of the old one.  Booting this new PBP with the microSD card works for less than 20 seconds, and then the display turns off.  I have yet to open this PBP up to use the serial console, but I don't expect that will help, because NetBSD does start to boot.  I see that the PBP image of NetBSD has been withdrawn from armbsd.org, and I expect that is due to this problem.

I suppose it may be possible to install a different Linux on a microSD card in order to re-flash the eMMC with my original PBP NetBSD image.  But I wonder if I will run into some other trouble and effectively brick the PBP.  Is Manjaro booting via SPI ROM?  I'm not very ambitious about experimenting because I don't have my other PBP running NetBSD to fall back on.
Well it seems I can answer my own question. My microSD card may have gone corrupt.

I followed the first three instructions here https://wiki.netbsd.org/ports/evbarm/ins...g_sysinst/
and then copied rk3399-pinebook-pro.dtb from /dtb/rockchip to both /dtb and / (because I don't recall which is the proper place), and now have a bootable microSD with NetBSD.

The actual first command used was
Code:
dd if=arm64.img of=/dev/mmcblk1 bs=1M conv=sync
arm64.img is from evbarm/aarch64
the Pinebook Pro U-Boot was found here https://cdn.netbsd.org/pub/pkgsrc/packag...4/9.0/All/]]>
I bought another PinebookPro.  I have a microSD card with NetBSD 9.0 on it that I used as sort of a rescue boot for my other PinebookPro (which runs NetBSD 9.1).  I know that it works because I booted the old PBP with it, to make an image of the eMMC, so that I could make the new PBP a clone of the old one.  Booting this new PBP with the microSD card works for less than 20 seconds, and then the display turns off.  I have yet to open this PBP up to use the serial console, but I don't expect that will help, because NetBSD does start to boot.  I see that the PBP image of NetBSD has been withdrawn from armbsd.org, and I expect that is due to this problem.

I suppose it may be possible to install a different Linux on a microSD card in order to re-flash the eMMC with my original PBP NetBSD image.  But I wonder if I will run into some other trouble and effectively brick the PBP.  Is Manjaro booting via SPI ROM?  I'm not very ambitious about experimenting because I don't have my other PBP running NetBSD to fall back on.
Well it seems I can answer my own question. My microSD card may have gone corrupt.

I followed the first three instructions here https://wiki.netbsd.org/ports/evbarm/ins...g_sysinst/
and then copied rk3399-pinebook-pro.dtb from /dtb/rockchip to both /dtb and / (because I don't recall which is the proper place), and now have a bootable microSD with NetBSD.

The actual first command used was
Code:
dd if=arm64.img of=/dev/mmcblk1 bs=1M conv=sync
arm64.img is from evbarm/aarch64
the Pinebook Pro U-Boot was found here https://cdn.netbsd.org/pub/pkgsrc/packag...4/9.0/All/]]> <![CDATA[FreeBSD 13 (PersonalBSD)]]> https://forum.pine64.org/showthread.php?tid=14781 Mon, 30 Aug 2021 01:00:07 +0000 evantaylor]]> https://forum.pine64.org/showthread.php?tid=14781
Go through base/installer image from PersonalBSD.org sd-card (if your u-boot supports USB it will also work that way), you can run the PersonalBSD image as your FreeBSD setup, or install it as I did using bsdinstall.

No built in wifi, so I use a rtl8188 based usb adapter which uses the rtwn driver.

just requires modifying /etc/rc.conf:

# wifi setup
wlans_rtwn0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

and adding my network to /etc/wpa_supplicant.conf

network={
    ssid="wifi_ssid_name"
    psk="wifi_password"
}

Desktop Setup/Packages

If you absolutely need packages not in the PersonalBSD repos, modify /usr/local/pkg/repos/FreeBSD.conf to enable the normal FreeBSD repo.

FreeBSD:  {
    enabled: yes
    priority: 0
}

follow step5 onward for XFCE4 desktop from this walkthrough (https://leonardcucos.com/how-to-install-...ce-4-2021/), and the command ee is your friend if you hate modifying config files with vi.

I did not enable HALD as that has not been necessary for some time, but its in all the older guides.

Caveats:

FreeBSD 13 does not understand big.LITTLE scheduling yet, so worse performance across the board.

There is no ETA on the wifi driver for the built in adapter, given how horribly it performed recently on NetBSD, it will likely be a while if it ever gets supported.

There will not nearly be as much support for FreeBSD as linux distros for the PBP, so unless you're comfortable applying patches to ports yourself this may not be the OS for you (this is above even my pay grade).

The FreeBSD Quarterly Repo has more packages than Latest, so I wouldn't bother switching to it.  Firefox is still only v87, sadly.

Package Conflicts are annoying, some things break when using multiple repos, try building things from ports.

P.S.

Had to use right-ctrl for tmux/screen window switching as the default key map differentiates them.

Edit:

Be ready to compile from ports as package repos are not completely working for all desktop apps.]]>
Go through base/installer image from PersonalBSD.org sd-card (if your u-boot supports USB it will also work that way), you can run the PersonalBSD image as your FreeBSD setup, or install it as I did using bsdinstall.

No built in wifi, so I use a rtl8188 based usb adapter which uses the rtwn driver.

just requires modifying /etc/rc.conf:

# wifi setup
wlans_rtwn0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

and adding my network to /etc/wpa_supplicant.conf

network={
    ssid="wifi_ssid_name"
    psk="wifi_password"
}

Desktop Setup/Packages

If you absolutely need packages not in the PersonalBSD repos, modify /usr/local/pkg/repos/FreeBSD.conf to enable the normal FreeBSD repo.

FreeBSD:  {
    enabled: yes
    priority: 0
}

follow step5 onward for XFCE4 desktop from this walkthrough (https://leonardcucos.com/how-to-install-...ce-4-2021/), and the command ee is your friend if you hate modifying config files with vi.

I did not enable HALD as that has not been necessary for some time, but its in all the older guides.

Caveats:

FreeBSD 13 does not understand big.LITTLE scheduling yet, so worse performance across the board.

There is no ETA on the wifi driver for the built in adapter, given how horribly it performed recently on NetBSD, it will likely be a while if it ever gets supported.

There will not nearly be as much support for FreeBSD as linux distros for the PBP, so unless you're comfortable applying patches to ports yourself this may not be the OS for you (this is above even my pay grade).

The FreeBSD Quarterly Repo has more packages than Latest, so I wouldn't bother switching to it.  Firefox is still only v87, sadly.

Package Conflicts are annoying, some things break when using multiple repos, try building things from ports.

P.S.

Had to use right-ctrl for tmux/screen window switching as the default key map differentiates them.

Edit:

Be ready to compile from ports as package repos are not completely working for all desktop apps.]]> <![CDATA[OpenBSD 6.9 install]]> https://forum.pine64.org/showthread.php?tid=13920 Mon, 17 May 2021 08:30:02 +0000 StickyPine]]> https://forum.pine64.org/showthread.php?tid=13920
I attempted to install OpenBSD 6.9 on the PineBookPro. I essentially followed those steps https://github.com/ndhwyd/roc-rk3399-pc_openbsd and changed rk3399-roc-pc.dtb with rk3399-pinebook-pro.dtb. 

When starting the machine, the booting process halts with the following message:

Code:
bwfm0: failed loadfirmware of file brcmfmac43456-sdio.rockchip,rk3399-evb.bin

(I have the same issue when using rk3399-roc-pc.dtb)

Has anyone experienced something similar or would know how to solve this ?]]>
I attempted to install OpenBSD 6.9 on the PineBookPro. I essentially followed those steps https://github.com/ndhwyd/roc-rk3399-pc_openbsd and changed rk3399-roc-pc.dtb with rk3399-pinebook-pro.dtb. 

When starting the machine, the booting process halts with the following message:

Code:
bwfm0: failed loadfirmware of file brcmfmac43456-sdio.rockchip,rk3399-evb.bin

(I have the same issue when using rk3399-roc-pc.dtb)

Has anyone experienced something similar or would know how to solve this ?]]> <![CDATA[PINEBOOK Pro USB-C Docking Deck on FreeBSD]]> https://forum.pine64.org/showthread.php?tid=13236 Fri, 26 Feb 2021 08:07:52 +0000 S199pWa1k9r]]> https://forum.pine64.org/showthread.php?tid=13236
Has anyone tried the PINEBOOK Pro USB-C Docking Deck under FreeBSD.
Ethernet is not detected on me.
What chipset is used in the PINEBOOK Pro USB-C Docking Deck?]]>
Has anyone tried the PINEBOOK Pro USB-C Docking Deck under FreeBSD.
Ethernet is not detected on me.
What chipset is used in the PINEBOOK Pro USB-C Docking Deck?]]> <![CDATA[Trackpad Adjustments for Xorg]]> https://forum.pine64.org/showthread.php?tid=12883 Sun, 24 Jan 2021 18:10:39 +0000 ReleaseTheGeese]]> https://forum.pine64.org/showthread.php?tid=12883
I was wondering if anyone has successfully adjusted the trackpad acceleration? The pointer moves a bit too slow for my liking.

A command exists for the synclient on Linux: https://wiki.pine64.org/wiki/Pinebook_Pr...d_settings. But that's a different driver on a different OS, of course.

A quick look at sysctl didn't bring up anything that looked to do with the trackpad.

I'd appreciate any help.

Regards,
RTG.]]>
I was wondering if anyone has successfully adjusted the trackpad acceleration? The pointer moves a bit too slow for my liking.

A command exists for the synclient on Linux: https://wiki.pine64.org/wiki/Pinebook_Pr...d_settings. But that's a different driver on a different OS, of course.

A quick look at sysctl didn't bring up anything that looked to do with the trackpad.

I'd appreciate any help.

Regards,
RTG.]]> <![CDATA[Issues Installing NetBSD on a PineBook Pro]]> https://forum.pine64.org/showthread.php?tid=12695 Sun, 03 Jan 2021 19:56:09 +0000 ReleaseTheGeese]]> https://forum.pine64.org/showthread.php?tid=12695
I've recently acquired a second-hand PBP. I'm quite impressed with the construction of this laptop, and eager to make it into a useful machine. I've also been looking for an excuse to try a BSD system. Thus, these two developments meet in some problems I've had with the PBP.

So the PineBook Pro came with the default Manjaro ARM OS. This booted without any trouble and was usable. I then went and flashed a NetBSD Current image for the PineBook Pro onto a microSD card. I used `dd` on a Void Linux desktop to do this. I was hoping to eventually flash NetBSD from the microSD onto the internal SSD.

However, when I inserted the SD card into the PineBook, it ignored the microSD card and just went ahead to boot Manjaro. This happened even after a reboot. Then I disassembled it and disabled the internal SSD using the switch. While leaving the microSD card inserted, I powered the PBP on again. However, this time the screen remained black and there was no activity from any of the power lights. I don't think I've bricked it, but I'm not sure what to do next.

I've been looking through the forums, reddit, the wiki. But I'd like clarity from anyone who has successfully installed NetBSD: Did I follow the correct procedure for installing NetBSD? Is it simply a case of flashing the microSD and then switching on the PBP, and that'll present me with a ready-installed NetBSD or an installer?

Also, I'd appreciate any troubleshooting tips. If that's more appropriately asked in the hardware section, I'll begin another thread there.

Regards,
R.T.G.]]>
I've recently acquired a second-hand PBP. I'm quite impressed with the construction of this laptop, and eager to make it into a useful machine. I've also been looking for an excuse to try a BSD system. Thus, these two developments meet in some problems I've had with the PBP.

So the PineBook Pro came with the default Manjaro ARM OS. This booted without any trouble and was usable. I then went and flashed a NetBSD Current image for the PineBook Pro onto a microSD card. I used `dd` on a Void Linux desktop to do this. I was hoping to eventually flash NetBSD from the microSD onto the internal SSD.

However, when I inserted the SD card into the PineBook, it ignored the microSD card and just went ahead to boot Manjaro. This happened even after a reboot. Then I disassembled it and disabled the internal SSD using the switch. While leaving the microSD card inserted, I powered the PBP on again. However, this time the screen remained black and there was no activity from any of the power lights. I don't think I've bricked it, but I'm not sure what to do next.

I've been looking through the forums, reddit, the wiki. But I'd like clarity from anyone who has successfully installed NetBSD: Did I follow the correct procedure for installing NetBSD? Is it simply a case of flashing the microSD and then switching on the PBP, and that'll present me with a ready-installed NetBSD or an installer?

Also, I'd appreciate any troubleshooting tips. If that's more appropriately asked in the hardware section, I'll begin another thread there.

Regards,
R.T.G.]]> <![CDATA[NetBSD -Current binaries]]> https://forum.pine64.org/showthread.php?tid=12608 Thu, 24 Dec 2020 05:06:56 +0000 BronzeBeard]]> https://forum.pine64.org/showthread.php?tid=12608 <![CDATA[NetBSD and USB "sound cards"]]> https://forum.pine64.org/showthread.php?tid=11926 Sat, 24 Oct 2020 10:04:17 +0000 KC9UDX]]> https://forum.pine64.org/showthread.php?tid=11926
I bought two devices from Newegg, hoping that one of them would work.  This turned out to be very fortuitous. The first is a StarTech ICUSBAUDIO7D.  The second is a Toshiba PA3390U-1MPM.

First off, connecting or disconnecting either of these whilst the system is booted risks locking up the PBP. I am using Audacity to record, which also occasionally locks the machine. Since I am running NetBSD-current, this is not totally unexpected.

First the StarTech:
I was able to record audio via /dev/audio1, but this does not source the audio from Line In.  It sources it from the microphone jacks, which there are two and they are mono.  The audio level is about 10db too low.  There is a periodic tschk-stck noise in the recorded audio which I cannot figure out how to avoid.  I can play back audio, also via /dev/audio1.  This routes audio to the front speaker jacks.  The output audio seems to be an adequate level, and seems to be clear and acceptable.  Despite that these are labeled as speaker jacks, they seem to be line level.

Next the Toshiba:
I was able to record audio via /dev/audio1, and this sources audio from Line In.  The audio level again is about 10db too low.  The record audio seems to be clear and sufficient, albeit a low level.  I cannot get audio to play back from the device.  There is a mute button with indicator light on the front of the device, and this indicator is always on.  I assume that I would need the Windows software that comes with the device to turn the mute function off.

So, you can see I have one device that records well and one that plays back well.  I was able to daisy-chain them; the Toshiba device has an inbuilt USB hub.  In this case, the StarTech device becomes /dev/audio2.

The low record audio may have something to do with "line level" standards changing over the years.  The only other computer I've used with this stereo system is an Amiga with a Delfina audio card, and I don't recall ever having issues with low level audio on that.  (In fact, I'm pretty certain that there was plenty of headroom in the audio level; I did a lot of recording with that).  But that was over twenty years ago.  Things may have changed in the industry since; I have no idea.

This was my first experience ever using a "USB sound card".  So perhaps there are other things I could have done better and I am not aware.  But at least this is a workable solution, and I was able to record the audio that I needed.]]>
I bought two devices from Newegg, hoping that one of them would work.  This turned out to be very fortuitous. The first is a StarTech ICUSBAUDIO7D.  The second is a Toshiba PA3390U-1MPM.

First off, connecting or disconnecting either of these whilst the system is booted risks locking up the PBP. I am using Audacity to record, which also occasionally locks the machine. Since I am running NetBSD-current, this is not totally unexpected.

First the StarTech:
I was able to record audio via /dev/audio1, but this does not source the audio from Line In.  It sources it from the microphone jacks, which there are two and they are mono.  The audio level is about 10db too low.  There is a periodic tschk-stck noise in the recorded audio which I cannot figure out how to avoid.  I can play back audio, also via /dev/audio1.  This routes audio to the front speaker jacks.  The output audio seems to be an adequate level, and seems to be clear and acceptable.  Despite that these are labeled as speaker jacks, they seem to be line level.

Next the Toshiba:
I was able to record audio via /dev/audio1, and this sources audio from Line In.  The audio level again is about 10db too low.  The record audio seems to be clear and sufficient, albeit a low level.  I cannot get audio to play back from the device.  There is a mute button with indicator light on the front of the device, and this indicator is always on.  I assume that I would need the Windows software that comes with the device to turn the mute function off.

So, you can see I have one device that records well and one that plays back well.  I was able to daisy-chain them; the Toshiba device has an inbuilt USB hub.  In this case, the StarTech device becomes /dev/audio2.

The low record audio may have something to do with "line level" standards changing over the years.  The only other computer I've used with this stereo system is an Amiga with a Delfina audio card, and I don't recall ever having issues with low level audio on that.  (In fact, I'm pretty certain that there was plenty of headroom in the audio level; I did a lot of recording with that).  But that was over twenty years ago.  Things may have changed in the industry since; I have no idea.

This was my first experience ever using a "USB sound card".  So perhaps there are other things I could have done better and I am not aware.  But at least this is a workable solution, and I was able to record the audio that I needed.]]> <![CDATA[My NetBSD on Pinebook Pro journey]]> https://forum.pine64.org/showthread.php?tid=10377 Mon, 22 Jun 2020 05:04:30 +0000 KC9UDX]]> https://forum.pine64.org/showthread.php?tid=10377
A few months ago, I dug out an old laptop to use as a portable VNC terminal to operate and administer the various computers (some "headless") that I have, which run NetBSD and Debian/Raspbian Linux. After finding out that the hard drive was quickly dying, I sought out another cheap, used laptop.  I also found out about the Pinebook which seemed more lucrative, since I wouldn't need to buy new obsolete batteries.  I then found out that it would be quicker to get a Pinebook Pro.  So I ordered one.  A few covid months went by but then one day I got a tracking number.  Two days later I had the Pinebook Pro in my hands, all the way from Hong Kong!  I can't get things that quickly from a hundred miles away.  What an amazing machine.  It seems very well engineered and built, especially considering the price.

I thought I would use the Pinebook Pro to download NetBSD.  I quickly discovered an error in my DHCP server.  The Debian that came with the Pinebook Pro would always clobber /etc/resolv.conf, even though I was using a static IP.  Oddly, I have two other machines running Debian Buster, which do not have this problem.  But I fixed the server, and was able to download a NetBSD image.  I could not boot from the SD card though.  When the SD card was inserted, the eMMC would not boot, but neither did the SD card. 

So I took the bottom off the Pinebook and switched off the eMMC, and switched it back on immediately after the SD card started to boot.  This turned out to be pretty straightforward and not as scary as I had read.  The trick is to open the lid 90°, and lay the Pinebook on its keyboard, with the display overhanging the edge of a table, for disassembly.  I carefully stood the Pinebook up on its side to operate it.  Of course, I made sure to remove the plastic standoffs first.  A speaker did fall out, but I pressed it back in.  When picking up the Pinebook to stand it on edge, I picked it up by the display half so as not to put any load on the hinges.

I tried for several days to use sysinst to install with small partitions.  There is something wrong with sysinst, going back to at least version 8, on every platform I've used it on.  The partitioning barely works and does some very bad things.  I never did get it to give me a working, bootable setup on the Pinebook Pro.  I only tried this because I like to have small partitions so that I can quickly make uncompressed images that easily fit on USB memory sticks.  So rather than try to partition and install manually, I put the installation image on the eMMC and let it grow itself.  When doing this, you can link /targetroot to / and still use sysinst to configure the system and install pkgsrc.

I initially did have some hiccups with the wifi.  I used FTP to retrieve the NetBSD image from a local server.  I had the "flood of checksum errors" problem.  But I rebooted and tried again, and did not have the issue again.  In fact, except for sysinst occasionally crashing, I'm finding NetBSD-current to be very stable.  Right now, it's compiling kde4, and has been doing this for over twelve hours.]]>
A few months ago, I dug out an old laptop to use as a portable VNC terminal to operate and administer the various computers (some "headless") that I have, which run NetBSD and Debian/Raspbian Linux. After finding out that the hard drive was quickly dying, I sought out another cheap, used laptop.  I also found out about the Pinebook which seemed more lucrative, since I wouldn't need to buy new obsolete batteries.  I then found out that it would be quicker to get a Pinebook Pro.  So I ordered one.  A few covid months went by but then one day I got a tracking number.  Two days later I had the Pinebook Pro in my hands, all the way from Hong Kong!  I can't get things that quickly from a hundred miles away.  What an amazing machine.  It seems very well engineered and built, especially considering the price.

I thought I would use the Pinebook Pro to download NetBSD.  I quickly discovered an error in my DHCP server.  The Debian that came with the Pinebook Pro would always clobber /etc/resolv.conf, even though I was using a static IP.  Oddly, I have two other machines running Debian Buster, which do not have this problem.  But I fixed the server, and was able to download a NetBSD image.  I could not boot from the SD card though.  When the SD card was inserted, the eMMC would not boot, but neither did the SD card. 

So I took the bottom off the Pinebook and switched off the eMMC, and switched it back on immediately after the SD card started to boot.  This turned out to be pretty straightforward and not as scary as I had read.  The trick is to open the lid 90°, and lay the Pinebook on its keyboard, with the display overhanging the edge of a table, for disassembly.  I carefully stood the Pinebook up on its side to operate it.  Of course, I made sure to remove the plastic standoffs first.  A speaker did fall out, but I pressed it back in.  When picking up the Pinebook to stand it on edge, I picked it up by the display half so as not to put any load on the hinges.

I tried for several days to use sysinst to install with small partitions.  There is something wrong with sysinst, going back to at least version 8, on every platform I've used it on.  The partitioning barely works and does some very bad things.  I never did get it to give me a working, bootable setup on the Pinebook Pro.  I only tried this because I like to have small partitions so that I can quickly make uncompressed images that easily fit on USB memory sticks.  So rather than try to partition and install manually, I put the installation image on the eMMC and let it grow itself.  When doing this, you can link /targetroot to / and still use sysinst to configure the system and install pkgsrc.

I initially did have some hiccups with the wifi.  I used FTP to retrieve the NetBSD image from a local server.  I had the "flood of checksum errors" problem.  But I rebooted and tried again, and did not have the issue again.  In fact, except for sysinst occasionally crashing, I'm finding NetBSD-current to be very stable.  Right now, it's compiling kde4, and has been doing this for over twelve hours.]]>