https://forum.pine64.org/ Wed, 13 May 2026 16:59:13 +0000 MyBB https://forum.pine64.org/showthread.php?tid=20267 Fri, 08 May 2026 14:56:37 +0000 tantamount]]> https://forum.pine64.org/showthread.php?tid=20267 TL;DR: None listed in the wiki boot

Irradium 3.8, kernel 6.12: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Irradium 3.8, kernel 7.0:   
 Doesn't boot. The power light stays green forever, no HDMI signal.

DietPi Trixie: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Armbian: 
 They dropped the Star64 some time ago.

NixOS v2023.11.26: 
 This one doesn't decompress: "unexpected end of file"

NixOS 23.11.20230827: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

NuttX RTOS:  
 Doesn't boot. The power light stays green forever, no HDMI signal.

What does boot:
1. I still have an ancient copy of Armbian from when it did support the Star64, which does boot (non-graphical).
2. I see that Fishwaldo's old images from 2023 are still available here: https://pine64.my-ho.st:8443/

Thus I think the "Software releases" section should be updated to remove the entries for the distros that don't even boot.

Of Fishwaldo's 3 images (version 2.1), I get the following results:

• The minimal distro does not boot. I get the green light that never blinks blue. This is a pity because text-only could be useful.
  
• The Weston distro boots and provides a fast GUI, however it doesn't provide anything else, like a menu or a way to launch apps or settings.
  
• The Plasma distro boots and provides a fast but more laggy GUI, but it does almost fully work.
  

Just now, with the Fishwaldo Plasma distro I was able to do the following which is pretty impressive:

1. Boot up and log in as pine64 (password pine64).
   
2. Set up Wifi, which works fine.
   
3. Run Firefox, which is somewhat slow but it works.
   
4. Download a FOSS program, compile it and run it.
   
5. Su as root (password pine64) and run "apt update" but there are no new packages. (e.g. GCC is version 11 but the current version is 14).
   
6. Install ffmpeg. This runs fine, however ffplay crashes with a segmentation fault.
   
7. Mount a USB thumb drive from the command line (it wasn't seen by Dolphin file manager).
   
8. Convert an MP3 to WAV and play it with `aplay`, which sounded like there was interference.
   

Regarding Weston, when I tried to force a text-only startup (systemctl set-default multi-user), this was ignored.
I think for some people, the text-only startup option could be necessary for projects.]]> TL;DR: None listed in the wiki boot

Irradium 3.8, kernel 6.12: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Irradium 3.8, kernel 7.0:   
 Doesn't boot. The power light stays green forever, no HDMI signal.

DietPi Trixie: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

Armbian: 
 They dropped the Star64 some time ago.

NixOS v2023.11.26: 
 This one doesn't decompress: "unexpected end of file"

NixOS 23.11.20230827: 
 Doesn't boot. The power light stays green forever, no HDMI signal.

NuttX RTOS:  
 Doesn't boot. The power light stays green forever, no HDMI signal.

What does boot:
1. I still have an ancient copy of Armbian from when it did support the Star64, which does boot (non-graphical).
2. I see that Fishwaldo's old images from 2023 are still available here: https://pine64.my-ho.st:8443/

Thus I think the "Software releases" section should be updated to remove the entries for the distros that don't even boot.

Of Fishwaldo's 3 images (version 2.1), I get the following results:

• The minimal distro does not boot. I get the green light that never blinks blue. This is a pity because text-only could be useful.
  
• The Weston distro boots and provides a fast GUI, however it doesn't provide anything else, like a menu or a way to launch apps or settings.
  
• The Plasma distro boots and provides a fast but more laggy GUI, but it does almost fully work.
  

Just now, with the Fishwaldo Plasma distro I was able to do the following which is pretty impressive:

1. Boot up and log in as pine64 (password pine64).
   
2. Set up Wifi, which works fine.
   
3. Run Firefox, which is somewhat slow but it works.
   
4. Download a FOSS program, compile it and run it.
   
5. Su as root (password pine64) and run "apt update" but there are no new packages. (e.g. GCC is version 11 but the current version is 14).
   
6. Install ffmpeg. This runs fine, however ffplay crashes with a segmentation fault.
   
7. Mount a USB thumb drive from the command line (it wasn't seen by Dolphin file manager).
   
8. Convert an MP3 to WAV and play it with `aplay`, which sounded like there was interference.
   

Regarding Weston, when I tried to force a text-only startup (systemctl set-default multi-user), this was ignored.
I think for some people, the text-only startup option could be necessary for projects.]]> https://forum.pine64.org/showthread.php?tid=20266 Thu, 07 May 2026 14:51:18 +0000 tantamount]]> https://forum.pine64.org/showthread.php?tid=20266 I know there's a RAM crisis ongoing but is there ever going to be a new Pinebook Pro2 with more RAM?
Some chips are easier to get than others, for instance the 1.5GB chips are easier to get than 1/2/4 GB.
Therefore maybe a Pinebook with 6GB or 12GB RAM would be doable.
Cheers.]]> I know there's a RAM crisis ongoing but is there ever going to be a new Pinebook Pro2 with more RAM?
Some chips are easier to get than others, for instance the 1.5GB chips are easier to get than 1/2/4 GB.
Therefore maybe a Pinebook with 6GB or 12GB RAM would be doable.
Cheers.]]> https://forum.pine64.org/showthread.php?tid=20265 Thu, 07 May 2026 09:37:08 +0000 PerfectJam]]> https://forum.pine64.org/showthread.php?tid=20265
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]>
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]> https://forum.pine64.org/showthread.php?tid=20264 Thu, 07 May 2026 09:36:58 +0000 PerfectJam]]> https://forum.pine64.org/showthread.php?tid=20264
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]>
I have a PineTime purchased in March 2023. When I first used it, the touchscreen was working perfectly.

I then left the watch unused for approximately 2 years. When I powered it back on, the touchscreen was no longer responding correctly, it feels like it is miscalibrated: inputs are not registered where I tap, or swipes are not recognized reliably.

I just updated the firmware to 1.16.0 (from 1.11.0), but the issue persists.

My assumption is that this may be a hardware degradation issue (deep discharge during storage) rather than a firmware problem, but I wanted to check here before concluding.

Has anyone experienced a similar issue after long-term storage? Is there any known fix or workaround short of hardware intervention?

Thanks and cheers !]]> https://forum.pine64.org/showthread.php?tid=20262 Sat, 02 May 2026 16:49:24 +0000 shinzuka]]> https://forum.pine64.org/showthread.php?tid=20262
Volumio is back on Pine A64

Image of Volumio tested on a working Pine A64+.

Volumio-3.999-2026-05-03-pine64plus.zip

Tested OK

- USB DAC
- Headphone jack

What remains to be tested:

- i2s DAC

**********Progress************

Volumio-3.999-2026-05-12-pine64plus.zip

- Jack output correction is now working.

- i2s ES9023 and Hifiberry DAC Plus (PCM5122) are available.


]]>
Volumio is back on Pine A64

Image of Volumio tested on a working Pine A64+.

Volumio-3.999-2026-05-03-pine64plus.zip

Tested OK

- USB DAC
- Headphone jack

What remains to be tested:

- i2s DAC

**********Progress************

Volumio-3.999-2026-05-12-pine64plus.zip

- Jack output correction is now working.

- i2s ES9023 and Hifiberry DAC Plus (PCM5122) are available.


]]> https://forum.pine64.org/showthread.php?tid=20256 Mon, 27 Apr 2026 10:06:11 +0000 Korfou]]> https://forum.pine64.org/showthread.php?tid=20256
I have a PinePhone 64. I’m desperately trying to figure out which Mobian image to use for the PinePhone.
I can’t find the image for the PinePhone on the Mobian website. And I don’t want to make a mistake.
Thank you for your help.]]>
I have a PinePhone 64. I’m desperately trying to figure out which Mobian image to use for the PinePhone.
I can’t find the image for the PinePhone on the Mobian website. And I don’t want to make a mistake.
Thank you for your help.]]> https://forum.pine64.org/showthread.php?tid=20254 Sat, 18 Apr 2026 16:08:52 +0000 chris.burmajster]]> https://forum.pine64.org/showthread.php?tid=20254
My Pine time is dead. It won't charge from its cradle. Is there anything I can do to make it work?

Chris]]>
My Pine time is dead. It won't charge from its cradle. Is there anything I can do to make it work?

Chris]]> https://forum.pine64.org/showthread.php?tid=20253 Fri, 17 Apr 2026 12:28:17 +0000 jagrav]]> https://forum.pine64.org/showthread.php?tid=20253 If I connect to a power supply, the display only shows calibrating, and not work. If I push the + switch under connecting the power,
it shows PD debug State 3 No Vbus. After push the - switch, only shows calibrating...
Under firmware update there are handshake errors. So I cannot step through the "calibrating" word.
The display orientation is changes, as I turn the pinecil handle to other direction....
How do I reset the unit to a working state?]]> If I connect to a power supply, the display only shows calibrating, and not work. If I push the + switch under connecting the power,
it shows PD debug State 3 No Vbus. After push the - switch, only shows calibrating...
Under firmware update there are handshake errors. So I cannot step through the "calibrating" word.
The display orientation is changes, as I turn the pinecil handle to other direction....
How do I reset the unit to a working state?]]> https://forum.pine64.org/showthread.php?tid=20251 Mon, 06 Apr 2026 14:44:41 +0000 Andrey_voce]]> https://forum.pine64.org/showthread.php?tid=20251 https://forum.pine64.org/showthread.php?tid=20244 Sat, 04 Apr 2026 14:00:51 +0000 qingss0]]> https://forum.pine64.org/showthread.php?tid=20244         I bought a crashed second-hand Pinebook Pro for a rock-bottom price.After some thinking and several attempts, I finally managed to get Kali Linux up and running properly on my Pinebook Pro.

What worked for me:

• Switched to USTC (University of Science and Technology of China) mirrors
  
• Used a command to bypass the command-not-found hook error.
  

        Feels great to see  apt-update  complete without segmentation faults or decompression errors. The Pinebook Pro is finally usable with Kali!]]>         I bought a crashed second-hand Pinebook Pro for a rock-bottom price.After some thinking and several attempts, I finally managed to get Kali Linux up and running properly on my Pinebook Pro.

What worked for me:

• Switched to USTC (University of Science and Technology of China) mirrors
  
• Used a command to bypass the command-not-found hook error.
  

        Feels great to see  apt-update  complete without segmentation faults or decompression errors. The Pinebook Pro is finally usable with Kali!]]> https://forum.pine64.org/showthread.php?tid=20243 Sat, 04 Apr 2026 13:30:31 +0000 RicTor]]> https://forum.pine64.org/showthread.php?tid=20243
I have been investigating and think I have found what  is happening - hence how to trigger charging. But I don't know why! 

Anyone else have the problem?

Are there any experts here who know the power / charging system? I can use help understanding the  schematic...]]>
I have been investigating and think I have found what  is happening - hence how to trigger charging. But I don't know why! 

Anyone else have the problem?

Are there any experts here who know the power / charging system? I can use help understanding the  schematic...]]> https://forum.pine64.org/showthread.php?tid=20237 Thu, 02 Apr 2026 23:16:51 +0000 bills2002]]> https://forum.pine64.org/showthread.php?tid=20237
Anyway with the latest update...Im finding it very useable.
- Liferea for RSS feeds.  Read the news, 3 pane window landscape...very functional.  Cant remember how I imported them but have 100s of feeds.  Update all takes about 5 minutes and then there is more articles than I can consume.
- KOreader with OPDS / Project Gutenberg gets me tons of reading material.
- Xournal++ for notes and drawings

Set the screen mode to BW:1 (or dither) and turn off automatic screen updates.  No flashing, smooth scrolling, clear as day.

Still wish:
- X11 was available for more panel options.
- faster writing response in Xournal++
- Some form of Libby / overdrive for checking out books from libraries.

Just wanted to say that it is beoming a daily need now.

Fingers crossed for a PineNote 2 with more cores, more mem, expandable storage.

Bill]]>
Anyway with the latest update...Im finding it very useable.
- Liferea for RSS feeds.  Read the news, 3 pane window landscape...very functional.  Cant remember how I imported them but have 100s of feeds.  Update all takes about 5 minutes and then there is more articles than I can consume.
- KOreader with OPDS / Project Gutenberg gets me tons of reading material.
- Xournal++ for notes and drawings

Set the screen mode to BW:1 (or dither) and turn off automatic screen updates.  No flashing, smooth scrolling, clear as day.

Still wish:
- X11 was available for more panel options.
- faster writing response in Xournal++
- Some form of Libby / overdrive for checking out books from libraries.

Just wanted to say that it is beoming a daily need now.

Fingers crossed for a PineNote 2 with more cores, more mem, expandable storage.

Bill]]> https://forum.pine64.org/showthread.php?tid=20234 Mon, 30 Mar 2026 23:07:35 +0000 cheepeero]]> https://forum.pine64.org/showthread.php?tid=20234
I have decided to try out Voidlinux on my Pinetab2, replacing the factory Archlinux I had installed until now. When I finished, I found that the same Plasma 6 desktop is much more responsive, with a significantly lower memory footprint. Maybe this is due to musl vs glibc, but it also might be that I have missed some memory-intensive services. Also note that I am using my old Archlinux home folder on the new Voidlinux system, and everything works.


So, here is my experience with this migration. I hope it will help others that want to migrate or try Voidlinux, so you can avoid bricking the Pinetab2 in the process, like I did.


First, I followed the installation instructions on the Pinetab2 releases page, which wrongly state that the Voidlinux image there is suitable both for the SD card and for the eMMC. The SD card worked, but flashing the eMMC bricked the device, so I had to revive it using the UART debugger. Do not do that!

The resources I needed are as follows:

• Pinetab2 Software Installation instructions: https://pine64.org/documentation/PineTab...tructions/
  
• Pinetab2 Software Releases: https://pine64.org/documentation/PineTab.../Releases/
  
• Voidlinux-pinetab2 readme: https://github.com/sini6a/voidlinux-pinetab2
  
• Voidlinux handbook: https://docs.voidlinux.org/about/index.html
  

If you follow my steps, and skip step 2, you won't need this, but it was handy for me:

• Pinetab2 Tutorials and FAQ: https://pine64.org/documentation/PineTab...s_and_FAQ/  (mistakes)
  

Below are the steps I took. If you follow this, SKIP STEP 2!

0. On the Pinetab2 I had the danctnix preinstalled factory image, which I used productively since I first received the device. At this step, I backed up my files using dd, and migrated my LVM home onto a separate HDD via USB.
1. I flashed Voidlinux as instructed in the Pinetab Software Releases page onto an SD card, and it booted just fine. I did not require the UART device.
2. DO NOT DO THIS STEP! It is here for informative purposes only: I flashed the same Voidlinux SD card image onto eMMC, as instructed by the Wiki page, which bricked the pinetab. So, again, DO NOT DO THIS.
    - I recovered with the UART (https://pine64.org/documentation/PineTab...s_and_FAQ/ - Recovery from non-booting device) and installed a fresh danctnix Archlinux factory image.
    - Note to maintainers: please remove the faulty instruction from the Wiki page, or, alternatively, clarify how to flash Voidlinux to the eMMC.
3. After the blunder above, I rebooted into the Voidlinux SD card install, and I left the eMMC mmcblk0p1 unchanged (the boot partition, with danctnix u-boot and the kernel), but recreated and formatted the root partition, mmcblk0p2, with an empty ext4 filesystem.
4. From the SD card I followed the instructions on chroot install from Voidlinux handbook (https://docs.voidlinux.org/installation/...hroot.html), with the following notes:
    - mounted /dev/mmcblk0p2 as /mnt, next /dev/mmcblk0p1 as /mnt/boot. There is no need for an EFI partition.
    - I used `ARCH=aarch64-musl` and the repo URL `REPO=https://repo-default.voidlinux.org/current/aarch64/`
    - after copying the xbps keys and running the chroot install, remember to skip the rootfs tarball method, but continue with generating fstab and setting a root password
    - also skip stuff related to GRUB and EFI
    - as a side note, the section about Pinebook Pro does not apply at all to Pinetab2
5. I jumped to the Voidlinux-pinetab2 readme on github, and installed all the packages mentioned there. I did not have the files downloaded on SD card, so had to configure the network at this step, but one can prepare the files beforehand, after flashing the Voidlinux SD card.
    - the imageramfs step did not work - out of disk space on boot partition, but the system boots and works fine without it
    - the u-boot boot.scr needed to be regenerated. The xbps-install output provides necessary instructions on-screen
6. Unmounted /mnt/boot and /mnt, sync and next poweroff, remove SD card, power on from button, and Voidlinux booted from eMMC successfully into the text console.
7. As root, started following the Voidlinux handbook guide on how to configure the system (lvm, sddm, wayland, xdg portals, cron etc). Finally, I configured my non-root user, after installing and testing SDDM and KDE, I moved back the LVM home volume from the external HDD, and all worked out well. (Note that I still had the dd backup of the LVM volume, just in case)

At this stage I still have Voidlinux-related stuff to fix, but the base system and KDE/Plasma works.]]>
I have decided to try out Voidlinux on my Pinetab2, replacing the factory Archlinux I had installed until now. When I finished, I found that the same Plasma 6 desktop is much more responsive, with a significantly lower memory footprint. Maybe this is due to musl vs glibc, but it also might be that I have missed some memory-intensive services. Also note that I am using my old Archlinux home folder on the new Voidlinux system, and everything works.


So, here is my experience with this migration. I hope it will help others that want to migrate or try Voidlinux, so you can avoid bricking the Pinetab2 in the process, like I did.


First, I followed the installation instructions on the Pinetab2 releases page, which wrongly state that the Voidlinux image there is suitable both for the SD card and for the eMMC. The SD card worked, but flashing the eMMC bricked the device, so I had to revive it using the UART debugger. Do not do that!

The resources I needed are as follows:

• Pinetab2 Software Installation instructions: https://pine64.org/documentation/PineTab...tructions/
  
• Pinetab2 Software Releases: https://pine64.org/documentation/PineTab.../Releases/
  
• Voidlinux-pinetab2 readme: https://github.com/sini6a/voidlinux-pinetab2
  
• Voidlinux handbook: https://docs.voidlinux.org/about/index.html
  

If you follow my steps, and skip step 2, you won't need this, but it was handy for me:

• Pinetab2 Tutorials and FAQ: https://pine64.org/documentation/PineTab...s_and_FAQ/  (mistakes)
  

Below are the steps I took. If you follow this, SKIP STEP 2!

0. On the Pinetab2 I had the danctnix preinstalled factory image, which I used productively since I first received the device. At this step, I backed up my files using dd, and migrated my LVM home onto a separate HDD via USB.
1. I flashed Voidlinux as instructed in the Pinetab Software Releases page onto an SD card, and it booted just fine. I did not require the UART device.
2. DO NOT DO THIS STEP! It is here for informative purposes only: I flashed the same Voidlinux SD card image onto eMMC, as instructed by the Wiki page, which bricked the pinetab. So, again, DO NOT DO THIS.
    - I recovered with the UART (https://pine64.org/documentation/PineTab...s_and_FAQ/ - Recovery from non-booting device) and installed a fresh danctnix Archlinux factory image.
    - Note to maintainers: please remove the faulty instruction from the Wiki page, or, alternatively, clarify how to flash Voidlinux to the eMMC.
3. After the blunder above, I rebooted into the Voidlinux SD card install, and I left the eMMC mmcblk0p1 unchanged (the boot partition, with danctnix u-boot and the kernel), but recreated and formatted the root partition, mmcblk0p2, with an empty ext4 filesystem.
4. From the SD card I followed the instructions on chroot install from Voidlinux handbook (https://docs.voidlinux.org/installation/...hroot.html), with the following notes:
    - mounted /dev/mmcblk0p2 as /mnt, next /dev/mmcblk0p1 as /mnt/boot. There is no need for an EFI partition.
    - I used `ARCH=aarch64-musl` and the repo URL `REPO=https://repo-default.voidlinux.org/current/aarch64/`
    - after copying the xbps keys and running the chroot install, remember to skip the rootfs tarball method, but continue with generating fstab and setting a root password
    - also skip stuff related to GRUB and EFI
    - as a side note, the section about Pinebook Pro does not apply at all to Pinetab2
5. I jumped to the Voidlinux-pinetab2 readme on github, and installed all the packages mentioned there. I did not have the files downloaded on SD card, so had to configure the network at this step, but one can prepare the files beforehand, after flashing the Voidlinux SD card.
    - the imageramfs step did not work - out of disk space on boot partition, but the system boots and works fine without it
    - the u-boot boot.scr needed to be regenerated. The xbps-install output provides necessary instructions on-screen
6. Unmounted /mnt/boot and /mnt, sync and next poweroff, remove SD card, power on from button, and Voidlinux booted from eMMC successfully into the text console.
7. As root, started following the Voidlinux handbook guide on how to configure the system (lvm, sddm, wayland, xdg portals, cron etc). Finally, I configured my non-root user, after installing and testing SDDM and KDE, I moved back the LVM home volume from the external HDD, and all worked out well. (Note that I still had the dd backup of the LVM volume, just in case)

At this stage I still have Voidlinux-related stuff to fix, but the base system and KDE/Plasma works.]]> https://forum.pine64.org/showthread.php?tid=20227 Tue, 24 Mar 2026 22:45:39 +0000 8lall0]]> https://forum.pine64.org/showthread.php?tid=20227 Hello everyone!

I have a Rock64, but i cannot get the A/V jack to output video.

Do you have any hints?

Thanks!]]> Hello everyone!

I have a Rock64, but i cannot get the A/V jack to output video.

Do you have any hints?

Thanks!]]> https://forum.pine64.org/showthread.php?tid=20226 Tue, 24 Mar 2026 20:25:41 +0000 Zebulon Walton]]> https://forum.pine64.org/showthread.php?tid=20226
I do have a spare USB board but before doing surgery on the phone I sprayed some DeoxIT contact cleaner into the port and plugged/unplugged a USB cable several times. After doing this the port is working fine! Even directly wiggling the connector doesn't break the connection.

The Pinephone's USB port is open to dirt and debris and over the years apparently enough got in there to affect the connection. So if you're having problems with your USB connection this is something to try before swapping out the board.

*** EDIT *** Oops, I meant to post this in the regular Pinephone board, not the Pro board! Though I expect this info applies to both models.]]>
I do have a spare USB board but before doing surgery on the phone I sprayed some DeoxIT contact cleaner into the port and plugged/unplugged a USB cable several times. After doing this the port is working fine! Even directly wiggling the connector doesn't break the connection.

The Pinephone's USB port is open to dirt and debris and over the years apparently enough got in there to affect the connection. So if you're having problems with your USB connection this is something to try before swapping out the board.

*** EDIT *** Oops, I meant to post this in the regular Pinephone board, not the Pro board! Though I expect this info applies to both models.]]>