I have booted a preloaded SD card labeled “snickerdoodle SD Card r2p0” and am trying to login. These logins don’t work:
snickerdoodle/snickerdoodle
admin/admin
If I try to login as root it fails before I am prompted for a password.
Thanks,
-Jim
Hi Jim, the new unified SD card works differently. We moved away from default passwords since those are a source of inherent insecurty.
Instead you need to set your initial passwords before boot using config.txt in the MSDOS boot partition of the microSD card.
Upon boot linux will suck in those password changes or user additions and delete the plaintext passwords out of config.txt
Please see README.txt on the boot partition.
config.txt might look something like this:
macula:~ jamil$ cd /Volumes/BOOT/
macula:BOOT jamil$ ls -al
total 11032
drwxrwxrwx@ 1 jamil staff 16384 Nov 20 16:02 .
drwxr-xr-x@ 5 root wheel 170 Nov 20 16:00 ..
drwxrwxrwx 1 jamil staff 2048 Nov 20 01:28 .Spotlight-V100
-rwxrwxrwx 1 jamil staff 4096 Nov 20 16:02 ._config.txt
drwxrwxrwx 1 jamil staff 2048 Nov 20 16:00 .fseventsd
-rwxrwxrwx 1 jamil staff 2882 Oct 22 06:26 README.txt
-rwxrwxrwx 1 jamil staff 550948 Apr 25 2018 boot.bin
drwxrwxrwx 1 jamil staff 2048 Oct 23 01:48 common
-rwxrwxrwx@ 1 jamil staff 1277 Nov 20 16:04 config.txt
-rwxrwxrwx 1 jamil staff 16035 Apr 25 2018 devicetree.dtb
drwxrwxrwx 1 jamil staff 2048 Oct 23 01:48 piSmasher-snickerdoodle-black
drwxrwxrwx 1 jamil staff 2048 Oct 23 01:48 snickerdoodle
drwxrwxrwx 1 jamil staff 2048 Oct 23 01:48 snickerdoodle-black
drwxrwxrwx 1 jamil staff 2048 Oct 23 01:48 snickerdoodle-one
drwxrwxrwx 1 jamil staff 2048 Oct 23 01:48 snickerdoodle-prime
-rwxrwxrwx 1 jamil staff 408 Oct 21 04:23 uEnv.txt
-rwxrwxrwx 1 jamil staff 5031640 Apr 25 2018 uImage
-rwxrwxrwx 1 jamil staff 750 Apr 25 2018 uboot.scr
macula:BOOT jamil$ cat config.txt
#
# snickerdoodle configuration
#
# This file is used to update user and network settings during boot.
#
#### Wireless access point (AP) configuration ##################################
# Set the wireless access point SSID
ap_ssid=snickerdoodleAP
# Set the wireless access point WPA passphrase
ap_passphrase=mylongaccesspointpassword
# Set the access point IP address (also sets DHCP subnet)
ap_address=10.11.12.13
#### Wireless station configuration ############################################
# Set wireless network mode
sta_mode=wpa
# Set wireless network SSID
sta_ssid="Bat Cave WiFi"
# Set wireless network key
sta_key="1snickerdoodleAte10pis"
#### User configuration ########################################################
# Update user passwords with a comma delimited list of "user:password"
update_users=root:ilikecarrots,admin:awesomeadminpassword
#### Ethernet (if present) network configurations ##############################
# Ethernet IP configuration. Can be 'dhcp', 'static' or 'disabled'.
#eth0_mode=static
# Ethernet IP address (if mode is set to 'static').
#eth0_address=10.1.1.100
# Ethernet netmask (if not specified uses 255.255.255.0)
#eth0_netmask=255.255.255.0
#eth1_mode=static
#eth1_address=10.2.2.100
#eth1_netmask=255.255.255.0
macula:BOOT jamil$
Thanks very much - I missed that item in the config file.
Is there any more detailed documentation of this change?
I’ve copied the above and the plaintext passwords do not get deleted, the user accounts don’t work and the wifi SSID generated is not changed.
Is there any observable indication in the boot-up messages to confirm that the config.txt file has been seen and parsed correctly?
My BOOT partition has the following files only. Not directories as stated above.
glenn@Oswald:~$ cd /media/glenn/BOOT/
glenn@Oswald:/media/glenn/BOOT$ ls -alt
total 9162
drwxr-xr-x 3 glenn glenn 16384 Jan 26 21:05 .
-rw-r–r-- 1 glenn glenn 1275 Jan 26 21:05 config.txt
drwxr-x—+ 31 glenn glenn 4096 Jan 26 17:52 ..
drwxr-xr-x 4 glenn glenn 2048 Jan 26 17:50 .Trash-1001
-rw-r–r-- 1 glenn glenn 1281 Jan 26 17:50 ‘config (copy).txt’
-rw-r–r-- 1 glenn glenn 16985 Jun 18 2018 devicetree.dtb
-rw-r–r-- 1 glenn glenn 550948 Apr 25 2018 boot.bin
-rw-r–r-- 1 glenn glenn 165 Apr 25 2018 bootimage.bif
-rw-r–r-- 1 glenn glenn 346724 Apr 25 2018 fsbl.elf
-rw-r–r-- 1 glenn glenn 3395900 Apr 25 2018 u-boot.elf
-rw-r–r-- 1 glenn glenn 750 Apr 25 2018 uboot.scr
-rw-r–r-- 1 glenn glenn 326 Apr 25 2018 uEnv.txt
-rw-r–r-- 1 glenn glenn 5031640 Apr 25 2018 uImage
Starting straight from the “snickerdoodle-sdcard-r2p0.img” file then added the config.txt file.
Any other pointers to what I am doing wrong?
Generally feeling frustrated that the docs are not getting updated with changes. They seemed barely sufficient in the first place. Once I get things working I may be able to help with docs. But I am feeling pretty lost at the moment!
Thanks.
I’m having the same problem.
I’m using this image: snickerdoodle-sdcard-r2p0.img
I can get ubuntu to boot, and I can edit the config.txt file so that the snickerdoodle successfully connects to my wifi router, but I cannot get it to accept any username/password combinations that allow me to login.
Initially, I thought it was because I used special characters, so I simplified the password. Are there some ridiculous password complexity rules I’m missing? How can I tell that it accepted my changes? I don’t see any obvious message on boot.
This might be a ridiculous suggestion, but have you made sure the “update_users” line is de-commented?
So:
#### User configuration ########################################################
# Update user passwords with a comma delimited list of "user:password"
#update_users=user1:password1,user2:password2
would be, for example:
#### User configuration ########################################################
# Update user passwords with a comma delimited list of "user:password"
update_users=playerone:pwnsn00bs
-RC
I did remove the #. I was able to set the wifi connection information, see it appear in my router and then get an ssh prompt which leads me to believe I’m editing the config file correctly.
I tried recreating the SD card and then just un-commenting the example update_users line thinking that maybe something had happened to my SD card installation, but neither the user1 nor user2 worked. Earlier I had tried dead-simple combinations like
update_users=a:a
to make sure that I did not have an issue typing the password, but those did not work either.
I removed the SD card and mounted it. Neither /etc/passwd nor /etc/shadow have any username changes made to them reflecting the username/password combinations I tried. Are these the correct files I should inspect?
One other comment, after trying unsucessfully to login, when I inspect the config.txt file in BOOT, the update_users line that I edited has been cleared so that it now shows
# Update user passwords with a comma delimited list of "user:password"
#update_users=
I believe this means that the file was parsed and then cleared. It did not do this for lines that I had not uncommented, like for ethernet or the wifi access point.
I tried editing the passwd and shadow files to remove password requirements for the root and admin accounts directly on the SD Card and then rebooting. Still no dice. So apparently the account information is not stored in these files. Is it stored somewhere else?
I’m trying to replicate your issue but haven’t had any success. Just to confirm, the steps you are following are:
-
Download SD image from http://krtkl.com/resources/downloads/ (direct link: http://krtkl.com/uploads/snickerdoodle-sdcard-r2p0.zip)
-
Image SD Card (you may wish to reformat your SD card prior to this step just for good measure).
-
In the BOOT partition:
a. Copy the boot.bin and devicetree.dtb files from the appropriate board subdirectory (not sure which variant you have?) to BOOT
b. Edit config.txt to set the access point SSID (ap_ssid), access point password (ap_passphrase), access point IP address (ap_address), and username:password combinations (update_users)
It sounds like you aren’t having any issues with the AP and I gather (?) you are able to SSH into the device.
Assuming both these assumptions are accurate, can you try something quickly just to make sure you aren’t breaking any weird username/password rules?
Can you enter
admin:password
after “update_users” (with that line de-commented of course) and try that combination?
And if SSH is giving you problems, can you try connecting via the USB console? So:
screen [/dev/tty.usbmodem1234] 115200
Then enter your credentials that way and see if you have any luck.
Thank you. For reference, I have a snickerdoodle black.
I was able to get it to work using the admin username. But I had tried at the same time to add another user as well like this
update_users=admin:admin,user:user
the update to admin work, but user didn’t. Having a partly working SD card, I took another and followed your suggested work flow, using just
update_users=admin:password
and that worked as well.
After some more trying, I’m working on the hypothesis that I’m only able to set the password for the admin account. I cannot create new users via the config.txt. All of my original attempts had involved self-defined users. I need to do some more testing to verify this. Can you confirm anything like this as well?
Alright, I believe I’ve figured out what’s going on/what the issue is here…don’t worry, you’re not crazy!
It looks like the image has been structured in a way that only updates existing user/password pairs vs. updating existing AND adding new user/passowrd pairs via config.txt.
Clearly this was an oversight on our part.
The two “default” users are: ‘admin’ and ‘root’.
You should be able to update the passwords of both/either of these users, but you won’t be able to add additional users via config.txt with the current image – they would need to be added separately.
Sorry for all the hassle and frustration. We will obviously need to fix this going forward. We’re working on managing our resources to improve the overall usability of our products, but that’s proven to more challenging than anticipated.
We will do better,
Ryan
Thank you for helping. I’m sorry if I was a bit petulant. I can work with the setup now that I understand what’s going on.
There is documentation in a couple places, on the wiki, the manual in github. I’m happy to contribute, since I have contemporaneous notes about the setup. Where is the preferred location that I could do that?
I ran into the same issue with my new snickerdoodle black. I wasn’t able to create a new user via the config.txt, and furthermore, I wasn’t able to set the root password via the update_users line, only the admin user. I also had to remove some “configfs” line in the fstab file in order for Ubuntu to boot properly, not sure what that’s about.
Hi jars,
Have you attempted to login via SSH using your updated root credentials? Or only via the serial terminal?
I’m not familiar with the configfs issue/that’s the first I’ve heard of it…
-Ryan
The manual in GH is kind of defunct at this point, so I’d probably recommend against that. I’d say if you have tutorials or projects you wanted to put together, we have a Hackster page set up. But for things like notes on the setup, either the forum or Wiki would be the best bet for now.