Known Issues

• Functional Issues
• Hardware Issues
• Connectivity Issues
• Audio Issues

👤 Functional Issues

Unable to close tabs

• To close tabs, you'll need a middle mouse button (M3).
• We are aware that some laptops have touchpads which lack an M3.

Workarounds

1. Use a dedicated mouse with BCLD.

💻 Hardware Issues

Unable to boot into BCLD

• Boot issues are often related to incompatible Secure Boot settings.
• Sometimes it can be caused by a corrupted image.
• Images can easily corrupt during the flashing of a USB, it happens all the time.
• In rare cases, a machine can be too 'new' for BCLD.

Workaround

1. Try to re-flash the BCLD-USB, maybe use a different tool.
2. Always use the latest version of BCLD.
3. Disable Secure Boot in the BIOS settings of your device.
4. Enable Legacy booting or a Compatibility Support Module (CSM).
5. Update the BIOS/UEFI firmare of the device.

Blank screen

• If your screen remains black or BCLD does not seem able to boot, it is possible your graphics card is not supported.

Workarounds

1. Use the nomodeset BCLD parameter.
2. It may also work to try nouveau.modeset=0
3. Another option would be to try acpi=off

This will unfortunately affect rendering as it disables the proprietary drivers.

BCLD hangs when trying to launch

• Some systems may have trouble running BCLD with updated microcode.

Workaround

• To try and boot BCLD with available microcode, use the dis_ucode_ldr KERNEL PARAMETER

🌐 Connectivity Issues

It takes long to connect

• BCLD tries to make a connection 3 times through LAN with priority over Wi-Fi.
• The default timeout is 20 seconds.

Workarounds

1. Disable unused adapters in the BIOS of your system, this may skip a few checks.

No connection with Secure Boot systems due to unsigned Realtek drivers.

• If Wi-Fi doesn't work with BCLD, it's probably related to Secure Boot.
• This is because the Realtek RTL8821CE Wireless Adapter and RTL8111/8168/8411 Ethernet Controller DKMS packages are not signed for Secure Boot.
• These drivers are never signed, as support for hardware stabilizes and merges with regular kernel updates.

Workarounds

1. Disable Secure Boot or enable legacy boot through the BIOS settings.
2. Use the pci=noaer kernel parameter.
3. Use another type of connection (LAN/Wi-Fi).
4. Wait for a new release with a kernel update.

Issues using PXE (network booting)

• All files needed for booting BCLD over PXE are included on the ISO artifact.
• You will need to find the kernel (vmlinuz) and ramdisk (initrd) files.
• It's possible to recursively mount a BCLD-IMG and then the BCLD-ISO.
• This is where the files are located.
• Many PXE issues can be caused by forgetting to update these 2 files and using a newer BCLD-ISO.

Workarounds

1. Always update the kernel and ramdisk when using a new version of BCLD.

Unable to connect, no DHCP lease

• BCLD is completely stateless and will simulate a fresh install on every boot.
• This means BCLD will ask for a new DHCP lease during every startup.
• When rebooting BCLD from multiple machines, keep in mind that your local DHCP pool may be drained.

Workarounds

1. Allow your DHCP server to remember MAC addresses for BCLD devices.
2. Use a separate DHCP pool for BCLD devices.
3. Disable IPv6 with ipv6.disable=1.

Wake-On-LAN (WOL) is not working

• BCLD enables Wake-on-LAN by default.
• It is possible to disable this using the BCLD parameter: bcld.wol.disable=1
• Wake-on-LAN allows machines booting BCLD to start remotely.

Workarounds

1. Try adding ip=dhcp to the BCLD parameters in bcld.cfg.

🔉 Audio Issues

Microphone is not working

• The microphone may not work for certain devices or headsets.
• Some hardware requires proprietary detection modules that are not publicly available.
• Switching back to legacy HDaudio can fix the problem.
• It may also be possible to switch to newer SOF audio drivers.

Workaround

1. To disable digital microphone and force analog detection, use snd_hda_intel.dmic_detect=0 (DEPRECATED).
2. To disable DSP audio detection, use snd-intel-dspcfg.dsp_driver=0.
3. To enable HDaudio legacy drivers, use snd-intel-dspcfg.dsp_driver=1.
4. To enable Intel DSP, use snd-intel-dspcfg.dsp_driver=2.
5. To enable Sound Open Firmware, use snd-intel-dspcfg.dsp_driver=3.

There is no sound

• BCLD usually waits a few seconds to check current audio devices with PulseAudio.
• If this check fails, BCLD will automatically shut down.
• This check will fail if there is no sound device, or if the hardware cannot be detected.

Workarounds

1. It may be possible to get audio working with bcld.audio.restore=1.
2. Make sure the relevant audio devices are enabled in the BIOS settings of your machine.

Volume is way too loud

• If the volume is too loud, simply change it using the BCLD parameter.

Workarounds

1. Lower the volume using the bcld.audio.volume BCLD parameter.

Volume seems lower than normal

• If the volume is low, it's possible there is lack of support for the audio device.
• ALSA may not be able to properly detect the audio sink, and will relay the audio to a combined sink.

Workarounds

1. Raise the volume using the bcld.audio.volume BCLD parameter.
2. Wait for a new release with a kernel update.