I googled rpi config.txt read only and no one has made it writable it seems, very odd. same with getting admin to change the file attributes.
thing is I had this running at 2200MHz by adding
over_voltage=8
arm_freq=2200
force_turbo=1
so I must have edited config.txt at some time.??

  Quote  

stan,
at a command prompt
sudo nano /boot/firmware/config.txt


I was able to edit and save the file without any issues

Did you try?

  TassyJim said  

  Quote  

stan,
at a command prompt
sudo nano /boot/firmware/config.txt


I was able to edit and save the file without any issues

Did you try?

Dunno what happened but that worked
edited and saved...scratch head as tried before it was read only??
over_voltage=8
arm_freq=2200
force_turbo=1

vcgencmd measure_clock arm says 2200 so happy days :) but weird

  dddns said  

  stanleyella said  

I haven't got admin access yet on rpi. seems a secret and why is config.txt now read only... stop people overclocking?

I almost can't believe that overclocking is configured in this text file. I'm interested, please post the content

In Trixie OS find arm_boost=1 and comment out then add 3 lines
# Run as fast as firmware / board allows
#arm_boost=1
over_voltage=8
arm_freq=2200
force_turbo=1

Thanks Stan, I'm looking forward to buy one. You really triggered me :)

@dddns- I do not know if you use mmedit to write code and load to pico but if you get a rpi 400 and install mmedit you will need this line in terminal
sudo usermod -aG dialout $(rpi user name)
This will make it connect usb to pico.
I just installed Trixie on another ssd and set it as before and it is working fine at 2200 overclock. youtube playback good.

  stanleyella said  

I haven't got admin access yet on rpi. seems a secret

You can do anything (including overwriting the whole system!) using sudo

If you want to do several things as root you can typically use
sudo bash

and you have a root shell.  You can get out of it using
exit
(or end of file, usually Ctrl-D)

But remember it is easy to ruin your system!!
(which is why they've made root a bit harder to use)

John
Edited 2026-03-05 08:24 by JohnS

Dear Jim,

I've got a RPi 4 on 64bit trixie and installed your mmedit5_rpi.
MMedit seems to work, but I've problems with MMCC, it doesn't accept <Return> and <Ctrl>-<C> and hangs quiet often.
Perhaps I missed something.

Greetings from the upside of our beautiful planet,
Martin

Martin,
I have been doing some work on the <CR> key problem in the various versions of Linux.
It does depend on which Enter key is pressed.

I wasn't aware of any ^C problem.
If you are using full menus, there is a ^C button. Does that work?
I will have a look.
I use a VNC for my RPis and that could make it difficult to see keyboard problems.

I have other things happening preventing me from doing much work on MMEdit at the moment.

Jim

Hi Jim,

There’s no difference between <Return> and <Enter> (i.e. between the alphanumeric and numeric keypads), and it doesn’t matter whether I access the RPi locally or via TigerVNC (which I usually use).
So I use <ESC>, <^C> and <Send+CR> via the menu; that works.
(Yes, ESC is one of the ‘naughty’ keys too)

The great thing is:
Data transfer from MMedit via MMCC to the Pico is working well – that’s the most important thing.
(Unfortunately, it’s not currently working between MMedit on Windows and my CMM2, but that’s probably a different matter)


Best regards,
Martin