Tesla USB - Why does the Imager not create Boot directory on SD card? #951
Replies: 11 comments 9 replies
-
|
After writing the image to the SD card there should be two partitions on the SD card. One containing a fat32 filesystem labeled "boot" or "bootfs", and the other containing an ext4 filesystem which Windows won't recognize and tell you to format. Needless to say, do not format it. It's possible you need to remove and reinsert the SD card before the new partitions/filesystems are recognized. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for that. I am building the SD card and waiting for the Pi Zero to arrive. I am sure I will have more questions when it arrives. Never played with a Raspberry Pi before. Thanks for your assistance. David in Adelaide South Australia.. |
Beta Was this translation helpful? Give feedback.
-
|
Pi Zero has arrived, having great difficulty making it work. I edit the teslausb_setup_variables.conf file and when I load it the LED flashes etc and when I elect the SD card and look at it in Windows this file has vanished. I can't even get it to connect to my WiFi network? Any assistance would be appreciated. By the way, I have never had anything to do with a Raspberry Pi before. |
Beta Was this translation helpful? Give feedback.
-
|
When it is powered up, green LED on solid, should I be able to see a WiFi signal from it? |
Beta Was this translation helpful? Give feedback.
-
The setup process moves the file to a different location during setup, so that's normal. If the Pi is not connecting to your wifi, then you probably made a mistake entering the wifi info. |
Beta Was this translation helpful? Give feedback.
-
|
Having trouble, got the wifi working, but when I ssh into it asks for password, but none work.
Have attached some config files i used.
Where to from here?
David
On 25/04/2025 1:07:37, marcone ***@***.***> wrote:
I edit the teslausb_setup_variables.conf file and when I load it the LED flashes etc and when I elect the SD card and look at it in Windows this file has vanished. The setup process moves the file to
DuckDuckGo removed one tracker. More [https://duckduckgo.com/-dOkU_M-1R3r84fRoIHKNxah6Wr7zozxx0b2F6hXjetaM_UTdE3-_NUxtqWZU-NaUVYtAUTKbAAMdU5SNzhYeIzEJeuHX6aGYDNBBewsOINJMWXg6-mnfBWBPAP_3VFjFIUWCADCVjXBNeDDGtJn4sB4JYErr5JkFXYe3bKhpdZhTzFjk51jpLFW75tltiUP9lsZeDUKxU35Msn1P1FDd-DH4hxHABEvQzkRoaMU23KV27zWNAD7VEAwkVzMHg9bfa0BZH6GA_U9vI27prU6hU-7kmghY8EWG4PjyKJ8AW-01JjjEoynQ2k2B8UQBrhpJ79McgnL5I3bZjPgtAUawIvCEYSMZiEml-h-uH_f7oGySNfBY7438A7KQ7vSipxKp3PjxiMK2QOX6nmPvJn77xZxpLDYbZD6br-5qmUfPWNf78e7ZFyWa870SFrFMTPWMsU6OpguLvvvSseGzNs3ApseBsGLePvDkR_f7A8H5VpavqPHmGTKgnu9OcmdgbxCZMrAA]
Report Spam [https://duckduckgo.com/-dOkU_M-1R3r84fRoIHKNxah6Wr7zozxx0b2F6hXjetaM_UTdE3-_NUxtqWZU-NaUVYtAUTKbAAMdU5SNzhYeIzEJeuHX6aGYDNBBewsOINJMWXg6-mnfBWBPAP_3VFjFIUWCADCVjXBNeDDGtJn4sB4JYErr5JkFXYe3bKhpdZhTzFjk51jpLFW75tltiUP9lsZeDUKxU35Msn1P1FDd-DH4hxHABEvQzkRoaMU23KV27zWNAD7VEAwkVzMHg9bfa0BZH6GA_U9vI27prU6hU-7kmghY8EWG4PjyKJ8AW-01JjjEoynQ2k2B8UQBrhpJ79McgnL5I3bZjPgtAUawIvCEYSMZiEml-h-uH_f7oGySNfBY7438A7KQ7vSipxKp3PjxiMK2QOX6nmPvJn77xZxpLDYbZD6br-5qmUfPWNf78e7ZFyWa870SFrFMTPWMsU6OpguLvvvSseGzNs3ApseBsGLePvDkR_f7A8H5VpavqPHmGTKgnu9OcmdgbxCZMrAA]
I edit the teslausb_setup_variables.conf file and when I load it the LED flashes etc and when I elect the SD card and look at it in Windows this file has vanished.
The setup process moves the file to a different location during setup, so that's normal. If the Pi is not connecting to your wifi, then you probably made a mistake entering the wifi info.
—
Reply to this email directly, view it on GitHub [#951 (reply in thread)], or unsubscribe [https://github.com/notifications/unsubscribe-auth/BRTXWSW4NWXJTF47TZV3MST23EAL7AVCNFSM6AAAAAB3MK4M36VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJTG4YTIMQ].
You are receiving this because you authored the thread.Message ID: ***@***.***>
[c2ddf809-5d9e-40a5-94f7-ab9d43fefb4a]
dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=PARTUUID=8b3aede6-02 rootfstype=ext4 fsck.repair=yes rootwait modules-load=dwc2,g_ether quiet cfg80211.ieee80211_regdom=AU fsck.mode=auto noswap ro
# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
dtoverlay=dwc2
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
#dtoverlay=vc4-fkms-v3d
Raspberry Pi reference 2021-11-06
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, a8596e0d894315396d62d3546ce96cd1e7ceaf75, stage_teslausb
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US
network={
ssid="TEMPSSID"
psk="TEMPPASS"
key_mgmt=WPA-PSK
# Uncomment the following line, if you are trying
# to connect to a network with a _hidden_ SSID
#scan_ssid=1
}
|
Beta Was this translation helpful? Give feedback.
-
|
What user/password did you use? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
What you've set in the .conf file is for WiFi not SSH. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Make the changes in |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
The command needs to be run on the Pi itself, not on your PC. So ssh into your Pi, then follow the instructions that it prints when you log in. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
The default username is "pi" and the default password is "raspberry". If you changed it to something else, I can't help you, but either way that message means you typed the wrong username/password combination. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Sentry clips are archived into a separate folder called 'SentryClips'. Double check your .conf file and be sure the following line is commented out with a '#' at the front like so: Note: won't work if you set it to true. Turns on by commenting the line out. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
All working now, the reason not getting the Sentry Clips downloaded because the Pi is loading the Recent Clips to my WiFi, the Recent Clips are over one hour of Video, so, taking forever to load over WiFi to my PC network. In the .conf file I have this setting:- |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Tesla USB - Why does the Imager not create Boot directory on SD card? Ran imager_1.8.5,exe on a 64 gig SD card in a windows 11 PC using teslausb-20211106-2.zip ?
Beta Was this translation helpful? Give feedback.
All reactions