<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Debian Image with 6.1 kernel]]></title><description><![CDATA[<p dir="auto">Re: <a href="/topic/6478/coremp135-debian-image">CoreMP135 Debian image</a> New to this. I am failing at getting a debian image to boot so that i can access the CoreMP135 via the USB connection.  I followed the instructions at <a href="https://docs.m5stack.com/en/guide/linux/coremp135/buildroot" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/guide/linux/coremp135/buildroot</a>, and used the config corresponding to the newer kernel as suggested there. I can boot from the buildroot image sdcard.img, (chime, successful connection over USB-serial etc.) and uname -srm convinces me that the correct kernel is being used (6.1.28).  Then using the script in CoreMP135_buildroot-external-st/tools I was able to eventually create a debian image file.</p>
<p dir="auto">The CoreMP135 turns on, splash screen appears, but there is no chime, and the usb-serial does not work. However according to my router the CoreMP135 has an IP address, and I could theoretically ssh into it ; but, as others have pointed out ssh into root isn't allowed - so i have bit of a catch 22 in trying to figure out whats wrong.</p>
<p dir="auto">I have mounted and  inspected the image, compared the files in the buildroot image and the debian image looking for modules not loaded etc. I am not sure what I am missing. Has anyone else built a debian image with the newer kernel ? Like I said, I am new to this.  thanks!</p>
]]></description><link>https://community.m5stack.com/topic/7437/debian-image-with-6-1-kernel</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Mar 2026 13:26:50 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/7437.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 25 Mar 2025 22:37:06 GMT</pubDate><ttl>60</ttl></channel></rss>