rpi-distro / raspi-config Goto Github PK

Is the version of raspi-config tied to a specific Raspbian release ? It looks to me like it is not..

If not, then can we add a version number to the script and have that listed in the 'About raspi-config' section ?

I recently ran into an issue that involved interface settings and had no easy way to telling if the requestor was using the same version as I was.

If you can come up with a current release number then I'll add this myself and do a pull request

thanks

I want to use the non-interactive things, but I am having to trace though the bash script to figure out how it works.

Can I get some docs on how this works?
examples examples would be great.

my use case:
I want to document how to setup a pi for this class:
https://github.com/mechanicalgirl/young-coders-tutorial

like start with current raspbian, and run these raspi-config commands to set the following:

raspi-config
expand fs
boot into gui
set locale to en_US
keyboard-layout
timezone

Rasbian Version: 2017-04-10
Disabling VNC in raspi-config tool returns the message: "The VNC server is enabled"

I'm setting many (think 100+) raspberries, and I'd like to execute a bunch of raspi-config actions on all of them programmatically. Is it possible to rum raspi-config non-interactively? I'm particularly interested in expanding the file system and overclocking.

Please add no country restriction to choose from when setting country restriction for wifi. This might be relevant in a shielded laboratory setup to test certain wifi devices or in international waters, antartica or on a space station. There are perhaps more reasons to set, or go back to, no country restriction.

The option could be called default or none. Perhaps call it none and use that as default.

the SSH option (along with some others) is missing from the Advanced Options sub-menu

Hi

I've encountered a problem where I couldn't use raspi-config to switch between boot options, e.g. to turn console autologin for user pi on or off.

Having looked at the script, it looks like boot options can only change if /etc/init.d/lightdm exists - on non-graphical light installations where lightdm doesn't exist, such as Jessie Lite, that means it's impossible to change boot options using raspi-config.

How about changing-

      B1*)
--->    if [ -e /etc/init.d/lightdm ]; then                               <--- DELETE THIS LINE
          if [ $SYSTEMD -eq 1 ]; then
            systemctl set-default multi-user.target
            ln -fs /lib/systemd/system/[email protected] /etc/systemd/system/getty.target.wants/[email protected]
          else
            update-rc.d lightdm disable 2
            sed /etc/inittab -i -e "s/1:2345:respawn:\/bin\/login -f pi tty1 <\/dev\/tty1 >\/dev\/tty1 2>&1/1:2345:respawn:\/sbin\/getty --noclear 38400 tty1/"
          fi
--->    fi                                                               <--- DELETE THIS LINE
        ;;
      B2*)
--->    if [ -e /etc/init.d/lightdm ]; then                              <--- DELETE THIS LINE
          if [ $SYSTEMD -eq 1 ]; then
            systemctl set-default multi-user.target
            ln -fs /etc/systemd/system/[email protected] /etc/systemd/system/getty.target.wants/[email protected]
          else
            update-rc.d lightdm disable 2
            sed /etc/inittab -i -e "s/1:2345:respawn:\/sbin\/getty --noclear 38400 tty1/1:2345:respawn:\/bin\/login -f pi tty1 <\/dev\/tty1 >\/dev\/tty1 2>&1/"
          fi
--->    fi                                                               <--- DELETE THIS LINE
        ;;

To-

      B1*)
        if [ $SYSTEMD -eq 1 ]; then
          systemctl set-default multi-user.target
          ln -fs /lib/systemd/system/[email protected] /etc/systemd/system/getty.target.wants/[email protected]
        else
--->      [ -e /etc/init.d/lightdm ] && update-rc.d lightdm disable 2       <--- CHANGE TO THIS
          sed /etc/inittab -i -e "s/1:2345:respawn:\/bin\/login -f pi tty1 <\/dev\/tty1 >\/dev\/tty1 2>&1/1:2345:respawn:\/sbin\/getty --noclear 38400 tty1/"
        fi
        ;;
      B2*)
        if [ $SYSTEMD -eq 1 ]; then
          systemctl set-default multi-user.target
          ln -fs /etc/systemd/system/[email protected] /etc/systemd/system/getty.target.wants/[email protected]
        else
--->      [ -e /etc/init.d/lightdm ] && update-rc.d lightdm disable 2       <--- CHANGE TO THIS
          sed /etc/inittab -i -e "s/1:2345:respawn:\/sbin\/getty --noclear 38400 tty1/1:2345:respawn:\/bin\/login -f pi tty1 <\/dev\/tty1 >\/dev\/tty1 2>&1/"
        fi
        ;;

Thanks for all your hard work! Loving the Pi and about to get another soon. :)

Seasons Greetings
Julie
x

Configuration tool should allow for arbitrary default users (auto-login, etc). There are ways around this but it would be great to have this baked in. It would also assist in educating users about accounts/roles.

On line

https://github.com/RPi-Distro/raspi-config/blob/master/raspi-config#L393

please replace

  NEW_GPU_MEM=$(whiptail --inputbox "How much memory should the GPU have?  e.g. 16/32/64/128/256" \

with

  NEW_GPU_MEM=$(whiptail --inputbox "How much MB memory should the GPU have?  e.g. 16/32/64/128/256" \

Is there a way to get verbose output?

I do not have a user named "pi" on my system, and when running raspi-config as root I get:

No passwd entry for user 'pi'

If for example I try to enable an interface.

Has anyone considered adding a "Connect to WiFi" option in raspi-config? One that asks for SSID and passkey and insert the appropriate contents into wpa_supplicant.conf?

For Linux newbies, generating the network block and inserting that into the file represents a lot of hassle. I think having an easier way to do that would make the command line feel a little less formidable to beginners.

I can create a PR if maintainers have no objection 😄

When choosing

4 Wait for Network at Boot

and selecting multiple times

Fast Boot without waiting for network connection

or

Slow Wait for network connection before completing boot

results in error in raspi-config

There was an error running option 4 Wait for Network at Boot

and on command line

rm: cannot remove '/etc/systemd/system/dhcpcd.service.d/wait.conf': No such file or directory

Please fix this as these errors could be easily avoided and give the end user more peace of mind.

The new version of raspi-config for stretch is a serious improvement if you don't want to be the 'pi' user. The change to allow it to set things up for the sudo'd user is great. There are, however, some holes.

On a vanilla system, I changed my Desktop default user to me - rebooted and logged in.. Great - the default desktop user was me. However, the default underlying tty account was opened for 'pi'. The work around was to reboot as cli user with 'me' as the default user, and then reboot again as the desktop user. The extra account opened by systemd disappears.

Looks as if that when you change the default user - it needs to change both the lightdm X setup and the terminal code too.

This is not a showstopper - but I thought it could be reported. I think I put this in the wrong place initially. Hopefully this is right now.

I gather there is some support for a limited subset of the commands available on the raspi-config GUI; however it would be nice if this could be made available for all commands and functionality directly from the CLI so that the large number of people doing unattended installs can leverage this functionality to ensure these changes are applied consistently to doing the same thing via the menus...

Also it would be great if these could be documented somewhere other than the code ;)

Most functions have a check for interactive mode, however do_audio (and potentially other settings) does not.

Here is an good example where $INTERACTIVE is checked: https://github.com/RPi-Distro/raspi-config/blob/master/raspi-config#L945-L950

Please support limiting installation of related packages that are pulled in via recommends and suggests dependencies. This concerns the file /etc/apt/apt.conf and the following lines should be added for limiting the amount of packages that are pulled in.

APT::Install-Recommends "false";
APT::Install-Suggests "false";

Removing these lines will enable installation or related packages.

Implementing this will allow for a less disk usage on these systems that are aimed at minimal hardware requirements. The packages deciding on that is "recommends" and "suggests" do this with a server, desktop or laptop in mind, and not more limited device as an RPi.

What the title says. Changing any setting related to the screensaver - there's no way to do it in the GUI. Something as simple as disabling it - no way either.

This is a very, very common configuration task. It must be included in the GUI configurator. At the very least, allow a simple enable/disable toggle, with the default set to whatever you prefer.

Please note that this applies to the screensaver in both the graphical mode, and in the text (console mode). The settings are likely very different. I feel the graphical mode has a higher priority, but eventually both should be addressed.

If using the x-terminal it is easy to set the terminal to be too narrow. Function calc_wt_size() detects a terminal that is less than 60 cols and sets the width to 80. This still leaves the terminal too narrow, and menu text columns are truncated and "squash" together. While this is not strictly unusable, it can be difficult to read the options.

If the terminal is too narrow, it should do one of:
a) automatically make the terminal wider (and redraw?),
b) continue and pop up a message that the terminal should be made wider,
c) pop up / display a message that the terminal should be made wider, and quit

I don't know if (a) or (b) are possible; perhaps (b) should recheck the width

While connected using SSH (ssh -Y -p 8205 pi@) to a headless pi running latest Jessie

$ uname -a
Linux raspberrypi6 4.4.24-v7+ #1 SMP Mon Oct 10 21:48:58 UTC 2016 armv7l GNU/Linux

I decided to force audio > HDMI using raspi-config. Exited raspi-config normally but then noticed the following had been reported to REPL.

X11 connection rejected because of wrong authentication.
xcb_connection_has_error() returned true
numid=3,iface=MIXER,name='Mic Capture Volume'
  ; type=INTEGER,access=rw---R--,values=1,min=0,max=7936,step=0
  : values=2
  | dBminmax-min=0.00dB,max=31.00dB

This looks like an error was encountered with X11. To check this I ran xclock which displayed on my pc as expected. At the very least this error message could do with clarification.
I have not yet been able to confirm whether audio is forced or not but will update this if I find out more.

Currently SSH and VNC are under Interfaces,
To me they are not interfaces like the others in the menu. (all physical interfaces)
They would be better under NETWORKING as that is where they are used and so one would logically look.

Unfortunately I can see a lot of documentation consequences of moving them.

I backed up an 8GB running Jessie install according to the directions on the foundation website.
I then restored the image to a new 8GB sd card - according to the foundation directions. The new card fails to boot because there is a problem:
bad geometry: block count exceeds size of device
After MUCH time I discovered my 8GB SD cards were not all the same - of eight 8GB cards, I have:
2 - 7,906,263,040 GB
4 - 7,948,206,080 GB
2 - 8,026,849,280 GB

This can lead to much woe. (as can be seen by doing a google search)

Request For Enhancement

Add an option to the raspi-config utility to expand to the full size of the sd card less x% or xx bytes.

If I had reduced by 2% I would have been able to restore any of those cards to any other of the cards with out the error.

Thanks

I did this in sequence:
raspi-config (<-- here I can use 'Change Keyboard Layout' without problems)
apt-get update
apt-get dist-upgrade
raspi-config (<-- here I get bad messages when I select 'Change Keyboard Layout')

This is the bad message:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Reloading keymap. This may take a short while

Conclusion:
raspi-config needs to be fixed to work with latest updates.

OS: Raspbian Jessie
used hardware: Raspberry Pi 3 Model B 1GB RAM

Could command line options be added so this could be run from a script? At times I setup a bunch of these and it gets tedious going through all of the menus. Or is that not possible (or maybe better words would be "too difficult")?

Please, support setting max_usb_current (with the proper warning or info such as only use this when USB is lacking enough power).

MAX_USB_CURRENT

Configures the available current over USB; the default value is 0 for 600 mA. A value of 1 sets  it to 1.2 A.

From https://raspberrypi.stackexchange.com/questions/27708/is-setting-max-usb-current-1-to-give-more-power-to-usb-devices-a-bad-idea

See also #30

I'd like to suggest including the model and version of raspberry board.
It could be in the header or in the footer.
What do you think? If OK, I'll send the PR

See: https://www.raspberrypi.org/forums/viewtopic.php?f=44&t=142112

The GPIO UART on the Pi3 is badly broken, as in unusable. There seem to be three options, none of which is obviously best.

• As is -- bluetooth works, but the GPIO UART doesn't.

• Both bluetooth and GPIO UARTs work but the GPU core frequency is throttled back to its minimum.
  

• The GPIO UART works but there is no Bluetooth UART.
  

Setting up these options is complex and fiddly, especially the third which involves DT overlays. On the other hand it seems to be perfect for a new raspi-config option.

Please support HifiBerry Digi+ S/PDIF audio via Toslink by adding or removing the following line in /boot/config.txt

dtoverlay=hifiberry-digi

See also https://www.hifiberry.com/digiplus/

Additionally, alter values in /etc/asound.conf to set this as default audio card

pcm.!default  {
 type hw card 0
}
ctl.!default {
 type hw card 0
}

The values are probably not the default as shown above but can be querried with

aplay -l

and

aplay -L

If needed, I can provide output of those command and test raspi-config.

Implementing this enables user to use this board with minor time consuming manual configuration.

Please offer support for disabling and enabling WiFi power saving. This involves the creation of a file called /etc/modprobe.d/8192cu.conf

To disable, add the following line.

options 8192cu rtw_power_mgnt=0 rtw_enusbss=0 rtw_ips_mode=1

And fir the file /boot/cmdline.txt add before the key "elevator" the following key-value pair

cgroup_enable=memory

To enable power saving, remove the line above and the added key-value pair.

Implementing this prevents systems locking down on remote access because power saving is disabling WiFi, rendering the system unapproachable.

The GPIO Server setting should be persistant.

Could you add 'systemctl enable pigpiod.service' in case of

1. ‘Advanced Options’
2. ‘GPIO Server’
3. ‘Would you like the GPIO server to be accessible over the network?’ = ‘Yes’

so that pigpiod is also started after a reboot.

It will help a lot to have the possibility to configure the wifi in this tool so you don't need to edit the WPA file.

Plesae, support setting config_hdmi_boost (with the proper warning or info such as only use this when HDMI output is not strong enough and use the lowest level possible).

CONFIG_HDMI_BOOST

Configures the signal strength of the HDMI interface; the default value is 0 and the maximum is 7. Try 4 if you have interference issues with HDMI.

from https://www.raspberrypi.org/documentation/configuration/config-txt.md

I made a small script to permanently change the cpu governor and up threshold on the raspi by always changing it at boot with a init.d script.
Unfornately I am not experienced enough to integrate the functionality myself into this repo, although I think it would be a useful advanced option especially for high power applications like openvpn server or low power like sensors.
Repository with the standalone application code

Disabling the serial terminal via raspi-config also removes the device node /dev/ttyACM0, which is different to how this worked previously, where it remained and could be used by user-space applications.

This is on Raspbian 2016-05-27.

Not sure if this is the correct place to raise issues against raspi-config but here goes...

The regex in get_json_string_val() expects each line to end with a comma. The lines in question are:

...
# $1 = filename, $2 = key name
get_json_string_val() {
    sed -n -e "s/^[[:space:]]*\"$2\"[[:space:]]*:[[:space:]]*\"\(.*\)\"[[:space:]]*,$/\1/p" $1
}
...

This works fine for most JSON key/value pairs except when they occur on the last one of a JSON payload, for example:

{
  "flavour": "chocolate",
  "language": "en_CA.UTF-8",
  "keyboard": "US"
}

Testing this function in a plain old shell would fail to extract a value for "keyboard" since it lacks a comma before the newline.

Hi! The current gpu_mem adjustment option only seems to edit the gpu_mem = X entry on config.txt. Fair enough, but this value is overridden by the gpu_mem_256/512/1024 (depending on what pi you have) entries, as per http://elinux.org/RPiconfig#Memory

I believe these entries are not in config.txt by default (see https://www.raspberrypi.org/documentation/configuration/config-txt.md), but I think perhaps there should be a warning, if they are present?

Hi,

Enabling the OpenGL desktop acceleration support stops OpenGLES based apps from working; this is currently the expected behaviour: raspberrypi/firmware#556

As this will effect a number of OpenGL ES based applications and libraries (including the bundled VideoCore examples under /opt/vc) already in the wild, please could you add a warning on the settings page along the lines of:

"WARNING: Enabling this option disables OpenGL ES for both console only and desktop applications."

Thanks.

After installing the Jessie image from raspbian.org, I wanted to change to a German keyboard layout using sudo raspi-config > 5 Internationalization Options > 13 Change Keyboard Layout. I had a German Macintosh USB keyboard connected to the Raspberry Pi 2.0 Model B. But when choosing this option, nothing happens and I am returned to the main menu of raspi-config. After exiting the config, I see these error messages on the console:

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Reloading keymap. This may take a short while

I guess this is related to the change to systemdin Debian Jessie.

I've tried to change the Overclock option when using my new Rasperry Pi Zero. I know, that the CPU by itself is already clocked at 1000 MhZ, thus I guess this option doesn't make sense for the Pi Zero anyway, right? This isn't a bug per se, but should this option be disabled for the Pi Zero?

I select VNC Enable on Pi Configuration screen, select ok, but it defaults back to disable.
Please advise

Raspberry Pi 3 comes with Bluetooth. While it is very nice to have, it also occupies UART and causes custom applications that rely on UART to fail.

It would be nice to have a mechanism to enable/disable Bluetooth, for reasons including but not limited to above (another reason is potential security/privacy).

I'd like to suggest including network proxy configuration. Eg export http_proxy, https_proxy, ftp_proxy....

Proxy services are very common in corporate networks.

What do you think? If OK, I'll send the PR.

I would like to know why I'm not able to overclock my Raspberry Pi 3 whit this tool

When choosing

AA GL Driver    Enable/Disable experimental desktop GL driver 

and xcompmgr is not installed, an error is shown and the instruction to install that package.

Raspi-config could easily offer the user to install that package for him or her.

Fixing this will make the configuration process more easy for the end-user.

PS Pershaps rename this option so the user know he or she is using a closed or open driver, because that is what really happens, regardless that it is experimental (as much is).

Hi,

when I try to update my raspi-config I get folowing error:

There was an error running option 8 Update

When I open the Option 6 -> Overclock I get following error:

This Pi cannot be overclocked.
Then
There was an error running option 6 Overclock

When I try to activate the Boot to Desktop and activate RealVNS server, nothing happens, after reboot.

I Try:
apt-get remove --purge raspi-config && apt-get install raspi-config

But the error ist the same. I use a raspi 3 wirh the latest raspbian firmware.

Can anyone help me?

Thx! Rudi

I've noticed two small bugs in the version of raspi-config that ships with the 2017-09-07 version of Raspbian. To reproduce the first one, install a fresh copy of 2017-09-07-raspbian-stretch-lite.img on a card and boot the Pi. Launch raspi-config, and try to explicitly desactivate VNC : raspi-config replies that VNC is enabled, which is the exact opposite of what one wanted to do.

To reproduce the second bug, try to update raspi-config to the latest available version, which is a little more recent than the one included in the 2017-09-07 image, and try to desactivate VNC again : raspi-config replies that VNC is... (an empty string is displayed instead of the word "desactivated").

Hi,

Enabling spi on the new raspberry pi 3 with raspi-config will block the device from booting.

The error displayed is : "could not insert 'spi_bcm2708'.

Workaround for now: use spi_bcm2835.

Thank you.

Documentation on https://www.raspberrypi.org/documentation/configuration/raspi-config.md is outdated, and it's not clear how to enable SPI.

I have looked at several issues, here and at the 'old' site at https://github.com/asb/raspi-config. The following Issues can be fixed by the suggested changes.

asb:11 - Raspi-config is not approachable by the blind...
Changed to use the a,b,c, menu options allowing hot keys (a, b, c,); is this more suited to people with poor vision, in addition to the colour-highlighted line? I don't know how to test this

asb:28 - raspi-config: Internationalisation Options - Selection
Using an Internationalisation menu item returns to the main menu, changed to return to same menu (also on Advanced menu)

asb:39 - display "Internationalisation Options" before "Change User Password"
If following the menu sequence, the keyboard layout should be corrected before setting the passsword; moved to option b

RPi-Distro:9 - Unusable if terminal window too narrow
If the width is less than 60, a message is given to select continue or quit. If too narrow the current raspi-config does not increase the terminal size? I am not sure how to test for a blank WT_WIDTH (if [ -z "$WT_WIDTH"...)

New: - pressing Escape just quits raspi-config
The pressing of Escape is detected, leaving a sub-menu or giving a confirmation message on the main menu before quitting

New: - Texts and comments
Some texts have been changed, some short comments added

Note: a new script is attached to this post. All update functionality has been removed; instead each option shows a message. This is to assist in testing the navigation. Lines beginning "#*nnn" preceding a function show the line number (nnn) in the original script that the function can be found. Run it in a terminal window from the GUI desktop to change the width of the screen

nav_rconfig.txt

https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=127321