# Debian: Getting Started with the PandaBoard

**URL:** <https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839>\
**Category:** Linux Guides\
**Created:** [March 18, 2021, 8:46pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839 "2021-03-18T20:46:33Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [March 18, 2021, 8:46pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/1 "2021-03-18T20:46:33Z")

</div>

This is a page about TI’s Cortex-A9 based; PandaBoard and PandaBoard ES.

# Availability

Boards:

- [PandaBoard](https://www.digikey.com/en/products/detail/circuitco-electronics-llc/UEVM4430G-01-00-00/2349866) at DigiKey
- [PandaBoard ES](https://www.digikey.com/en/products/detail/svtronics-inc/UEVM4460G-02-02-00/4037645) at DigiKey

# Basic Requirements

- Running a recent supported release of Debian, Fedora or Ubuntu on a x86 64bit based PC; without OS Virtualization Software.
- Many of the listed commands assume /bin/bash as the default shell.
- ARM Cross Compiler – Linaro: [https://www.linaro.org](https://www.linaro.org)
  - Linaro Toolchain Binaries: [https://www.linaro.org/downloads/](https://www.linaro.org/downloads/)

- Bootloader
  - Das U-Boot – the Universal Boot Loader: [http://www.denx.de/wiki/U-Boot](http://www.denx.de/wiki/U-Boot)
  - Source: [https://github.com/u-boot/u-boot/](https://github.com/u-boot/u-boot/)

- Linux Kernel
  - Linus’s Mainline tree: [https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)

- ARM based rootfs
  - Debian: [https://www.debian.org](https://www.debian.org)

# ARM Cross Compiler: GCC

This is a pre-built (64bit) version of GCC that runs on generic linux, sorry (32bit) x86 users, it’s time to upgrade…  
Download/Extract:

```bash
#user@localhost:~$
wget -c https://releases.linaro.org/components/toolchain/binaries/6.5-2018.12/arm-linux-gnueabihf/gcc-linaro-6.5.0-2018.12-x86_64_arm-linux-gnueabihf.tar.xz
tar xf gcc-linaro-6.5.0-2018.12-x86_64_arm-linux-gnueabihf.tar.xz
export CC=`pwd`/gcc-linaro-6.5.0-2018.12-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-

```

Test Cross Compiler:

```bash
#user@localhost:~$
${CC}gcc --version

```

```bash
#Test Output:
arm-linux-gnueabihf-gcc (Linaro GCC 6.5-2018.12) 6.5.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

```

# Bootloader: U-Boot

Das U-Boot – the Universal Boot Loader: [http://www.denx.de/wiki/U-Boot](http://www.denx.de/wiki/U-Boot)  
Depending on your Linux Distrubution, you will also need a host gcc and other tools, so with Debian/Ubuntu start with installing the build-essential meta package.  
[eewiki.net](http://eewiki.net) patch archive: [https://github.com/eewiki/u-boot-patches](https://github.com/eewiki/u-boot-patches)  
Download:

```bash
#user@localhost:~$
git clone -b v2019.04 https://github.com/u-boot/u-boot --depth=1
cd u-boot/

```

Patches:

```bash
#user@localhost:~/u-boot$
wget -c https://github.com/eewiki/u-boot-patches/raw/master/v2019.04/0001-omap4_common-uEnv.txt-bootz-n-fixes.patch
 
patch -p1 < 0001-omap4_common-uEnv.txt-bootz-n-fixes.patch

```

Configure and Build:

```bash
#user@localhost:~/u-boot$
make ARCH=arm CROSS_COMPILE=${CC} distclean
make ARCH=arm CROSS_COMPILE=${CC} omap4_panda_defconfig
make ARCH=arm CROSS_COMPILE=${CC}

```

# Linux Kernel

This script will build the kernel, modules, device tree binaries and copy them to the deploy directory.  
Download:

```bash
#user@localhost:~$
git clone https://github.com/RobertCNelson/armv7-multiplatform ./kernelbuildscripts
cd kernelbuildscripts/

```

For v5.4.x (Longterm 5.4.x):

```bash
#user@localhost:~/kernelbuildscripts$
git checkout origin/v5.4.x -b tmp

```

For v5.4.x-rt (Longterm 5.4.x + Real-Time Linux):

```bash
#user@localhost:~/kernelbuildscripts$
git checkout origin/v5.4.x-rt -b tmp

```

For v5.10.x (Longterm 5.10.x):

```bash
#user@localhost:~/kernelbuildscripts$
git checkout origin/v5.10.x -b tmp

```

For v5.10.x-rt (Longterm 5.10.x + Real-Time Linux):

```bash
#user@localhost:~/kernelbuildscripts$
git checkout origin/v5.10.x-rt -b tmp

```

For v5.15.x (Longterm 5.15.x):

```bash
#user@localhost:~/kernelbuildscripts$
git checkout origin/v5.15.x -b tmp

```

For v5.15.x-rt (Longterm 5.15.x + Real-Time Linux):

```bash
#user@localhost:~/kernelbuildscripts$
git checkout origin/v5.15.x-rt -b tmp

```

Build:

```bash
#user@localhost:~/kernelbuildscripts$
./build_kernel.sh

```

# Root File System

### Debian 11

| User | Password |
| --- | --- |
| debian | temppwd |
| root | root |

Download:

```bash
#user@localhost:~$
wget -c https://rcn-ee.com/rootfs/eewiki/minfs/debian-11.3-minimal-armhf-2022-04-15.tar.xz

```

Verify:

```bash
#user@localhost:~$
sha256sum debian-11.3-minimal-armhf-2022-04-15.tar.xz

```

```bash
#sha256sum output:
575738843651de2962f251447f4742d4f33313d6f7f5edf282a401207f5e6646 debian-11.3-minimal-armhf-2022-04-15.tar.xz

```

Extract:

```bash
#user@localhost:~$
tar xf debian-11.3-minimal-armhf-2022-04-15.tar.xz

```

# Setup microSD card

We need to access the External Drive to be utilized by the target device. Run lsblk to help figure out what linux device has been reserved for your External Drive.

```bash
#Example: for DISK=/dev/sdX
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part / <- Development Machine Root Partition
sdb 8:16 1 962M 0 disk <- microSD/USB Storage Device
└─sdb1 8:17 1 961M 0 part <- microSD/USB Storage Partition

```

```bash
#Thus you would use:
export DISK=/dev/sdb

```

```bash
#Example: for DISK=/dev/mmcblkX
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part / <- Development Machine Root Partition
mmcblk0 179:0 0 962M 0 disk <- microSD/USB Storage Device
└─mmcblk0p1 179:1 0 961M 0 part <- microSD/USB Storage Partition

```

```bash
#Thus you would use:
export DISK=/dev/mmcblk0

```

Erase partition table/labels on microSD card:

```bash
sudo dd if=/dev/zero of=${DISK} bs=1M count=10

```

Install Bootloader:

```bash
#user@localhost:~$
sudo dd if=./u-boot/MLO of=${DISK} count=1 seek=1 bs=128k
sudo dd if=./u-boot/u-boot.img of=${DISK} count=2 seek=1 bs=384k

```

Create Partition Layout:  
With util-linux v2.26, sfdisk was rewritten and is now based on libfdisk.

```bash
#Check the version of sfdisk installed on your pc is atleast 2.26.x or newer.
sudo sfdisk --version

```

```bash
#Example Output
sfdisk from util-linux 2.27.1

```

```bash
#sfdisk >= 2.26.x
sudo sfdisk ${DISK} <<- __EOF__
4M,,L,*
__EOF__

```

Format Partition:

```auto
for: DISK=/dev/mmcblkX
sudo mkfs.ext4 -L rootfs ${DISK}p1
 
for: DISK=/dev/sdX
sudo mkfs.ext4 -L rootfs ${DISK}1

```

Mount Partition:  
**On most systems these partitions may be auto-mounted…**

```bash
sudo mkdir -p /media/rootfs/
 
for: DISK=/dev/mmcblkX
sudo mount ${DISK}p1 /media/rootfs/
 
for: DISK=/dev/sdX
sudo mount ${DISK}1 /media/rootfs/

```

# Install Kernel and Root File System

To help new users, since the kernel version can change on a daily basis. The kernel building scripts listed on this page will now give you a hint of what kernel version was built.

```bash
-----------------------------
Script Complete
eewiki.net: [user@localhost:~$ export kernel_version=5.X.Y-Z]
-----------------------------

```

Copy and paste that “export kernel\_version=5.X.Y-Z” exactly as shown in your own build/desktop environment and hit enter to create an environment variable to be used later.

```bash
export kernel_version=5.X.Y-Z

```

### Copy Root File System

```bash
#user@localhost:~$
sudo tar xfvp ./*-*-*-armhf-*/armhf-rootfs-*.tar -C /media/rootfs/
sync

```

### Set uname\_r in /boot/uEnv.txt

```bash
#user@localhost:~$
sudo sh -c "echo 'uname_r=${kernel_version}' >> /media/rootfs/boot/uEnv.txt"

```

### Device Tree Binary

```bash
#~/
PandaBoard EA1->A3
sudo sh -c "echo 'dtb=omap4-panda.dtb' >> /media/rootfs/boot/uEnv.txt"
 
PandaBoard A4->+ (non ES)
sudo sh -c "echo 'dtb=omap4-panda-a4.dtb' >> /media/rootfs/boot/uEnv.txt"
 
PandaBoard ES
sudo sh -c "echo 'dtb=omap4-panda-es.dtb' >> /media/rootfs/boot/uEnv.txt"
 
PandaBoard ES Rev B3
sudo sh -c "echo 'dtb=omap4-panda-es-b3.dtb' >> /media/rootfs/boot/uEnv.txt"

```

### Copy Kernel Image

Kernel Image:

```bash
#user@localhost:~$
sudo cp -v ./kernelbuildscripts/deploy/${kernel_version}.zImage /media/rootfs/boot/vmlinuz-${kernel_version}

```

### Copy Kernel Device Tree Binaries

```bash
#user@localhost:~$
sudo mkdir -p /media/rootfs/boot/dtbs/${kernel_version}/
sudo tar xfv ./kernelbuildscripts/deploy/${kernel_version}-dtbs.tar.gz -C /media/rootfs/boot/dtbs/${kernel_version}/

```

### Copy Kernel Modules

```bash
#user@localhost:~$
sudo tar xfv ./kernelbuildscripts/deploy/${kernel_version}-modules.tar.gz -C /media/rootfs/

```

### File Systems Table (/etc/fstab)

```bash
#user@localhost:~/$
sudo sh -c "echo '/dev/mmcblk0p1 / auto errors=remount-ro 0 1' >> /media/rootfs/etc/fstab"

```

### WiFI

Install Firmware:

```bash
#~/
git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git --depth=1
 
sudo mkdir -p /media/rootfs/lib/firmware/ti-connectivity
sudo cp -v ./linux-firmware/ti-connectivity/* /media/rootfs/lib/firmware/ti-connectivity

```

### Remove microSD/SD card

```bash
sync
sudo umount /media/rootfs

```

# FAQ

### PandaBoard ES Rev B3: New Memory Timings

Note: the U-Boot patch on this wiki has this fix already applied…  
Error:

```bash
#~/
U-Boot SPL 2013.04-00015-gfe81c6a (Apr 24 2013 - 14:35:14)
OMAP4460 ES1.1
SDRAM: identified size not same as expected size identified: 0
expected: 40000000

```

Fix:  
Comment out:

> **[include/configs/omap4\_common.h · v2013.07-rc3 · U-Boot / U-Boot · GitLab](https://source.denx.de/u-boot/u-boot/blob/v2013.07-rc3/include/configs/omap4_common.h)**
>
> "Das U-Boot" Source Tree

```bash
#~/
/* Disable for PandaBoard ES Rev B3 #define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS */

```

### PandaBoard A4 (with “M” Micron memory)

Note: the U-Boot patch on this wiki has this fix already applied…

```bash
#~/
U-Boot SPL 2014.04-dirty (Apr 18 2014 - 13:51:58)
OMAP4430 ES2.3
SDRAM: identified size not same as expected size identified: 1000 expected: 40000000
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img

```

Fix: v2014.04:

> **[include/configs/ti\_omap4\_common.h · v2014.04 · U-Boot / U-Boot · GitLab](https://source.denx.de/u-boot/u-boot/blob/v2014.04/include/configs/ti_omap4_common.h)**
>
> "Das U-Boot" Source Tree

```bash
#~/
/* #define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS */
#define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS

```

# Comments

Any questions or comments please go to our TechForum: [TechForum](https://forum.digikey.com/c/support/linux-discussions/5)

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 2, 2024, 9:14pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/2 "2024-08-02T21:14:45Z")

</div>

Hello. I tested the howto with PandaBoard A3. The image build process went smoothly, however, I get no HDMI output after booting the generated image. Any guess what might be wrong? The ethernet+wifi seems to work. The kernel version is 5.15.148-armv7-x42.

Thank you.

---

<div class="post-metadata">

**Author:** ![Klint\_12443](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/klint_12443/32/56741_2.png) [@Klint\_12443](https://forum.digikey.com/u/Klint_12443)\
**Post date:** [August 2, 2024, 10:05pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/3 "2024-08-02T22:05:27Z")

</div>

Hello tavvva,

We will take a look at what you have and see if we can troubleshoot, someone should get back to you.

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [August 5, 2024, 6:40pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/4 "2024-08-05T18:40:44Z")

</div>

Which of the two hdmi connectors are you trying to use? For me, one was always iffy (hotplug)…

Regards,

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 6:32pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/5 "2024-08-06T18:32:44Z")

</div>

Hello Robert. I tried both and no difference. The old Ubuntu 12.04 kernel boots with the one closer to the USB ports. The same for old Fedora 18, but I think I’ve seen some of the Fedoras running only from the other one, that’s why I always test both. However the second one somehow draws power from the HDMI cable and the board has one of the LEDs still on even when the power jack is disconnected and therefore I’d love to see the first one working. Moreover the images working with the first one refuse to boot when the cable is plugged to the second one.  
Just thinking whether the issue I reported could be somehow related to the fact the native resolution of the monitor is 720p only (even when it can do 1080p). Maybe the driver became buggy at some point and refuses to work with some resolutions since then? Have you tried your image on a real hardware? If so, what revision of the board? Mine is A3. Thank you.

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [August 6, 2024, 7:15pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/6 "2024-08-06T19:15:02Z")

</div>

Oh, it’s been a while since i ran a CI farm of Panda’s… Found an A4, but no serial adapter… so let’s see if at-least hdmi comes up…

Regards,

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 7:15pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/7 "2024-08-06T19:15:56Z")

</div>

Tested with second monitor and still the same - no signal. The old 3.x kernels were the last ones I’ve ever seen working.

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 7:19pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/8 "2024-08-06T19:19:56Z")

</div>

It seems I’ll have to look at the old kernel sources and search for differences. It might be that a small detail was forgotten somewhere.

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 7:21pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/9 "2024-08-06T19:21:04Z")

</div>

You don’t need a serial cable as the ethernet works quite reliably and if you give it an address from DHCP, it’s possible to SSH to the image …

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [August 6, 2024, 7:22pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/10 "2024-08-06T19:22:05Z")

</div>

I’m just wondering if it’ll even bootup, u-boot comes in handy for that, as it’s been sitting for years, in a static bag…

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 7:23pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/11 "2024-08-06T19:23:41Z")

</div>

It does boot :] Actually the image generated with your howto works pretty well … just the video output suckzzzz 😃

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 7:26pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/12 "2024-08-06T19:26:45Z")

</div>

Btw. the oldest 5.x kernel from the howto fails to build … the 5.10 and 5.15 works …

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [August 6, 2024, 7:30pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/13 "2024-08-06T19:30:00Z")

</div>

Newer and Newer versions of GCC for HOSTCC like to break things. For really old builds, I’ve just do it in an old Docker container now…

Regards,

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 7:31pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/14 "2024-08-06T19:31:40Z")

</div>

Yeah … I’m crossbuilding 2.x kernels for ATARI in a virtual machine with old Debian 3 (woody) … the build takes just a couple of seconds …

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [August 6, 2024, 7:47pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/15 "2024-08-06T19:47:00Z")

</div>

Yeap, no video…

```auto
debian@arm:~$ uname -r ; dmesg | grep dss
5.15.148-armv7-x42
[3.973785] platform 58000000.dss: Fixing up cyclic dependency with encoder0
[3.981597] omapdss_dss 58000000.dss: supply vdda_video not found, using dummy regulator
[4.301635] omapdss_dss 58000000.dss: supply vdda_video not found, using dummy regulator
[4.320373] OF: graph: no port node found in /ocp/target-module@58000000/dss@0/target-module@5000/encoder@0
[4.330413] OF: graph: no port node found in /ocp/target-module@58000000/dss@0/target-module@5000/encoder@0

```

Let’s have a little fun… i still build for Debian 11.x: [https://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/](https://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/)

```auto
sudo apt update
sudo apt-get install linux-image-6.11.0-rc2-omap2plus-r1

```

Yeap… video works… (CONN B)… now trying HDMI-1080, which also works, but buggy on startup (had to cycle)…

 ![image](https://global.discourse-cdn.com/digikey/original/3X/e/9/e9abef0314481a2279b00918d764a279d94de2ca.jpeg)

Let’s try something more stable, i only build LTS’s for omap3/omap4/omap5 generation…

```auto
sudo apt update
sudo apt-get install bbb.io-kernel-6.6-armv7

```

and `6.6.36-armv7-x15` is broken… We probably just a deconfig tweak…

Fingers crossed i still have this in the repo…

```auto
sudo apt update
sudo apt-get install linux-image-6.6.0-omap2plus-r0

```

Yeap, video works with 6.6.0-omap2plus-r0, so now to start testing config changes to fix 6.6.36-armv7-x15

Regards,

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 8:23pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/16 "2024-08-06T20:23:54Z")

</div>

Woohoo! I can confirm 6.6.0-omap2plus-r0 works for me …

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 8:28pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/17 "2024-08-06T20:28:29Z")

</div>

Are these vanilla or patched? Is there a source for them available so that I could rebuild them with a different configuration?

---

<div class="post-metadata">

**Author:** ![RobertCNelson](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/robertcnelson/32/12_2.png) [@RobertCNelson](https://forum.digikey.com/u/RobertCNelson)\
**Post date:** [August 6, 2024, 8:30pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/18 "2024-08-06T20:30:48Z")

</div>

So 6.6.0-omap2plus-r0 is v6.6.x branch of: [GitHub - RobertCNelson/omap2plus-mainline-linux](https://github.com/RobertCNelson/omap2plus-mainline-linux) (main focus is to just build upstream omap2plus\_defconfig for testing like what we just did)

and 6.6.36-armv7-x15 is the v6.6.x branch of: [GitHub - RobertCNelson/armv7-multiplatform](https://github.com/RobertCNelson/armv7-multiplatform)

Right now i’ve copied the omap2plus defconfig into my v6.6.x branch and build testing…

Regards,

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 9:40pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/19 "2024-08-06T21:40:05Z")

</div>

Well … the problem with HDMI seems to be solved … but … the wifi disappeared 😃

---

<div class="post-metadata">

**Author:** ![tavvva](https://sea2.discourse-cdn.com/digikey/user_avatar/forum.digikey.com/tavvva/32/49177_2.png) [@tavvva](https://forum.digikey.com/u/tavvva)\
**Post date:** [August 6, 2024, 9:43pm UTC](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839/20 "2024-08-06T21:43:07Z")

</div>

I just tried to load the modules by hand, but nothing happened … no output in dmesg and the interface simply is not there

[Next page](https://forum.digikey.com/t/debian-getting-started-with-the-pandaboard/12839.md?page=2)