mostly DNS problem（you can confirm it with ping any url）,and you may need
to share your uconsole internet connection to the rndis interface (I only tryed this with Windows 10,I will comfirmed it together)
1 Like
Checked,RNDIS fully work on linux,NAT forwarding is needed on the uConsole. as well
【Internet】<-- wlan -->【uConsole(NAT forwarding)】<-- RNDIS -->【PicoCalc】
looks like I need to write some thing about RNDIS network.
1 Like
Connecting to the Internet via USB(RNDIS)
I’ve noticed many people struggling with using apt when a Wi-Fi connection hasn’t been established. In reality, you can easily obtain a network connection through the USB-C port on the Lyra via RNDIS.
Prerequisite: A PC with internet access (Linux or Windows).
Configuration (Picocalc side)
First, you need to configure the IP address and DNS for the usb0 interface (the RNDIS interface) on the Picocalc. You can run the following script:
#!/bin/bash
# Set IP and bring up the interface
ifconfig usb0 192.168.10.2 netmask 255.255.255.0 up
# Set the PC as the default gateway
route add default gw 192.168.10.1
# Set Google DNS
echo "nameserver 8.8.8.8" > /etc/resolv.conf`
Note: In this RNDIS network,
192.168.10.2is the Picocalc and192.168.10.1is your Host PC. You can modify these values as needed.
Configuration (Windows Host)
- Connect your PC to the Picocalc Lyra using a USB data cable. Under Control Panel > Network Connections, you should see a new adapter identified as a “Remote NDIS based Internet Sharing Device.”
- Find the adapter your PC currently uses for internet (e.g., “WLAN” or “Ethernet”).
- Right-click the adapter → Properties → Sharing tab.
- Check “Allow other network users to connect through this computer’s Internet connection.”
- Select the RNDIS adapter from the dropdown menu and click OK. Windows will now automatically handle routing for this device.
- Ensure the IP of RNDIS interface on the PC is set to
192.168.10.1. When Picocalc sets its gateway to10.1, its traffic will be forwarded through your PC’s active internet connection.
Configuration (Linux Host)
Linux setup is even more straightforward. The Picocalc side remains the same. Run these commands on your Host PC (assuming your internet source is wlan0 and the Lyra is usb0; replace names if necessary):
1. Set the RNDIS IP on the Host:
sudo ifconfig usb0 192.168.10.1 netmask 255.255.255.0 up`
2. Enable Network Forwarding and NAT:
# Enable IP forwarding
sudo sysctl -w net.ipv4.ip_forward=1
# Configure iptables for masquerading
sudo iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE
sudo iptables -A FORWARD -i usb0 -o wlan0 -j ACCEPT
sudo iptables -A FORWARD -i wlan0 -o usb0 -m state --state RELATED,ESTABLISHED -j ACCEPT`
2 Likes
Simple USB DHCP Configuration (Linux Host) - Internet Connection Sharing
No need for iptables and setting sysctl ipv4 ip forwarding
1. Determine the USB Connection name used for the Luckfox Lyra:
It typically wont be Wired connection 1
nmcli connection show
example
NAME UUID TYPE DEVICE
Wired connection 100 c57d31eb-bd98-365d-94df-60c2b875d4cc ethernet –
2. Apply shared internet connection:
sudo nmcli connection down "Wired connection 100"
sudo nmcli connection modify "Wired connection 100" ipv4.method shared
sudo nmcli connection up "Wired connection 100"
3. Obtain a DHCP client IP for Luckfox Lyra
adb shell dhclient usb0
Setting LLMNR support level “yes” for “2”, but the global support level is “no”.
4. View IP Address chosen for Luckfox Lyra
arp
Address HWtype HWaddress Flags Mask Iface
10.42.0.126 ether 16:cf:d3:c6:1b:2c C enx5a85fb60f7cd
2 Likes
Now have ethernet over usb0
Ping ok, ssh ok
sudo update ok
sudo upgrade fail on 52%
make still reporting an error, not able to compile my driver…
No offense, but is there a Discord where we can spam a little more freely? 
Sure,I make a discord channel for this post,Welcome to share your experience with using the device!
1 Like
why not just use the official discord that already exists?
Requirements for Setting Up the Build Environment
Although it is a bit of a “patchwork” solution, I have uploaded my build environment to GitHub. By following the instructions in the repository, you can quickly set up a build environment identical to mine. This will allow you to easily customize your kernel configuration via ./build.sh kconfig.
Generally, compiling drivers requires the Linux headers and kernel configuration, both of which are included in this SDK.
The GitHub repository link is provided below:
2 Likes
Don’t use Discord, with its new ‘age verification’ ‘feature’ – as we know from a recent security breach at Discord, there is no reason to trust Discord to be secure. There is no way I would hand over ‘verification’ data to Discord myself.
Rather, use something like the traditional IRC.
Great, thank you for your extra effort.
Have fresh copy of your above Ubuntu…
It seems that we have some error in “prepare” script path =>
My repository only contains the essential configuration files (you can think of it as a patch for the SDK specifically for Picocalc). To set up the entire build environment, you first need to configure the SDK. Please take special note: the Luckfox SDK is designed for x86 architectures and has specific requirements for the Ubuntu version and Python version. To avoid unnecessary trouble, try to keep your environment strictly consistent with the official requirements. (Detailed tutorials on how to build the SDK can be found on the official wiki.) Once the SDK is ready, git clone my repository into the SDK directory, select my configuration file, and you can proceed with the kernel build.
Regrettably, due to the way the Linux driver mechanism works, your driver must maintain a specific “matching” relationship with the compiled kernel. In other words, you must target a specific kernel version and configuration for the compiled driver to be compatible; otherwise, you may encounter all sorts of strange issues. My current expertise is still limited, but I will try to include the kernel headers in the image in the future to enable on-device driver compilation on the Picocalc. (Though, given the Picocalc’s performance, compiling drivers locally is honestly a test of patience.)
One last thing: the RTW_88 driver set you can download is primarily targeted at x86 architectures and may not necessarily account for ARM scenarios. Therefore, relying solely on the official make or make install will likely lead to various unpredictable problems. You need to read the Makefile and understand exactly what it is doing. (Gemini is an excellent teacher—you can paste the entire Makefile directly, and after describing your background in detail, it can provide plenty of technical advice and direct guidance.)
1 Like
Thank you for your patience and detail explanation 
Decided to move on to Calculinux Alpha 7 release…
Like Ubuntu & have two notebooks on that platform, but…
For PicoCalc with Lyra, afraid that my time is limited to spent on reinventing the wheel aka wifi.
Calculinux is up and running, wifi network working like charm 
1 Like
After correcting the parts of your network-related kernel settings that differed from those in markbirss’s image and rebuilding, my network driver also worked without any issues.
I was finally able to get the DRM driver and the picocalc SD card fully working.
However, I couldn’t get audio and the keyboard working with the drivers I compiled, so I used the prebuilt files instead. It would be helpful if there were a guide about this.
The setup wasn’t easy, but it’s impressive.
Note: According to the Linux driver architecture, .ko (Kernel Object) driver modules must strictly match the specific Linux kernel version they were compiled against. The Linux kernel does not provide a stable Kernel Module Application Binary Interface (ABI); instead, driver modules depend on specific kernel symbol tables, data structure definitions, and configurations.
Therefore, there is a high probability that your previously compiled drivers will be incompatible with my modified kernel. I have updated the GitHub repository to include the source code for my keyboard and audio drivers.
If you need to recompile your own audio/keyboard drivers, please keep the following in mind:
Environment Sync: As mentioned above, you must rebuild the SDK environment with my repository. You should successfully compile the kernel first before attempting to compile the module drivers. This ensures you obtain the correct kernel symbol tables and related information, which are typically only generated after a full kernel build.
DTS Matching: Since I have also modified the DTS (Device Tree Source) files, ensure that the .compatible strings in your driver source code match those used in the DTS (specifically “picocalc,picocalc-keyboard” and “fsl,picocalc-snd-pwm”).
What a great project. I bought a simple RTL8188FTV Wi-Fi adapter for $4, and it works!!
Semi-final Improvements for Audio
Hi everyone, it’s been a while since I’ve checked in here. It’s a bit of a shame that Luckfox-related projects seem to be at a standstill lately, but I’m back with something exciting to share!
The original PWM audio driver by @hisptoop used an 8kHz @ 8-bit mono configuration. To the naked ear, the audio distortion was quite noticeable. With a bit of help from AI, I finally mapped out the full logic of the PWM audio system. After extensive experimentation, I’ve achieved what I consider the current “SOTA” (State-of-the-Art) performance for this setup:
- Hardware Foundation: This improvement is still based on the hardware PWM version. It requires a hardware modification to the Lyra board itself, but the good news is that no soldering is required on the PicoCalc motherboard anymore.
- Mono-to-Dual Output: I’ve tested driving two channels with a single pin (by soldering the L/R channel pins together on the Lyra board). It works flawlessly, and the volume is significantly boosted since you’re now utilizing two speakers.
- Finding the “Sweet Spot”: Since the hardware limit for the Lyra PWM clock is 100MHz, increasing the “sampling depth” per PWM cycle simultaneously lowers the PWM carrier frequency. It’s a balancing act. After testing depths of 8, 9, 10, and 11 bits, I found the 48kHz @ 11-bit PWM tick combination to be the most balanced. 11-bit offers the lowest noise floor—while you can still hear a faint hum with headphones if you listen closely, the quality is now comparable to an FM radio.
- ALSA Upgrade: To complement the PWM improvements, I’ve upgraded the ALSA signal fed to the PWM to 22kHz @ S16LE. Simply put: the listening experience is excellent.
- Compatibility: Since 22kHz S16LE isn’t natively supported by most applications, an additional conversion layer is needed at the ALSA level. I’ve included the configuration details for this in the repository.
The improved audio driver source files are now available on GitHub. I welcome everyone to try it out and experience the difference!
P.S. The “Ultimate” mod would be achieving true stereo sound. However, this would require occupying an additional RMIO pin and further tweaking the PWM controller. I’ll look into that when I have more time.
4 Likes
Fresh Share #2: Agentic Bot @ Picocalc
Check out this really interesting thing: Picoclaw.
It’s a Go-based “clone” of OpenClaw, and it’s incredibly lightweight—running it eats up only about 20MB of RAM, which is plenty efficient even with a GUI running in the background.
Essentially, it exposes your Picocalc’s GPIO and USB ports to LLMs like GPT, acting as a full-blown Agent with Shell execution privileges. This means it can natively run commands on your device (even with Root access) to help you debug or tweak configurations, and it can even operate in autonomous loops to get tasks done.
Thanks to this, I actually got my mlterm configured to display color emojis!! The best part? It managed to do it while keeping the memory footprint from exploding.
2 Likes
Love this! I was late to the party because it took forever for my PicoCalc and uConsole to arrive. I recently got the Lyra and installed Ubuntu (thanks to you and the rest of this communities efforts) and have it running pretty well. I have to keep it connected to my laptop in order to ssh into it, but that’s fine while I await the wifi dongle (3.3v) and the cable to connect via the lyra. If there is anything else that you can recommend I do in order to tweak or improve it please let me know! I don’t know if there is anyway to purchase a 3D printed case for the mods but if there is then I would appreciate being pointed that direction. Also I would like to get the expansion board for the 02w if there’s a way to purchase one outright. Any way’s thank you again for the work and this is an awesome project!!!