Main menu
You are here
rPi Blog
rPi home page
-----
(top listing is most recent)
-
------------------------------------------------------------------------
- 2024-10-19:
- KM4ACK install VARA: https://www.youtube.com/watch?v=kgdSr5SmV0I
- first... : Build-a-Pi (latest version)
https://github.com/km4ack/73Linux
He says in an earlier video that running it in 64-bit was buggy, so will prepare a 32-bit SD. - Using SD-12, which has 32-bit OS installed.
Did update/upgrade, then executed command (from github link above) to install 73Linux (new version of build-a-pi)
Instructions say it may take 3-4 hours... - Install apparently successful.
Learning new features: pat config menu, for one ...
When it comes up, it lists my gridsquare, but it's blank because I didn't enter it when I webt through the prompts during install.
Yet config.json did already contain my gridsquare, so not sure why the pat menu doesn't show it, or what the consequences of that might be ... - also, the build-a-pi created a new desktop icon ...
which is what I used to install Vara.
Have not executed/tested it yet. - 2024-10-17:
- Installed rPi-06 (rPi5) into Neo case
Installed SD-23, which contains other ham programs. - Installed Direwolf per procedure here.
No errors. - 2024-10-13:
- Booted up my rpi-4 (ID: rPi-05 4gB ram), but problem with keyboard, would not enter the "@" symbol.
websearch for using alt, typing 4digit "0064" or using alt-fn, nothing worked.
Finally did $ sudo raspi-config and re-mapped keyboard.
Did not have my keyboard listed (Logitech K410), but picked most likely options in several selection screens,
re-booted and lo, it worked. - 2024-10-11:
- Received case for my rPi-4, a Neo alum. Very Nice. Installed rPi-05 (my ID - rPi-4 4gB ram) with 64gB SD-23 with winlink programs. Worked, mostly...
- Had some errors on the screen during bootup:
- USB 1-1.4: device descriptor read/64, error -110
Web search suggests it's an insufficient power issue with some USB peripheral.
The only thing plugged in at the time was the Logitech wireless keyboard dongle.
Boot process continued to success regardless, but suggested remedy was to power down, unplug power supply,
wait 2-5 minutes (for it to cool off?), then try again.
Amazingly it worked, errors disappeared. Go figure. - Proceeded to install Direwolf, which I was told I needed.
DireWolf - 2024-10-02:
- Attempting to install winlink on rPi:
- From Add/Remove Software... search for pat client
Select pat-0.13.1-1+b4 (64-bit)
Apply - However it did not work. That is, dpkg showed it was there,
but $ pat http gave no such command error... - Back to the drawing board...
First install ardop. Searching for it in Add/Remove brings up the pat client I'd previously installed...?
In any case, will install ardop from Releases:- browse to github, download ardopcf, make executable, double-click.
Re-booted, but pat http still gives no such command.
- From Add/Remove Software... search for pat client
- ...
Add/Remove --> remove pat ??? - 2024-09-25:
- Major progress today. Got guizero loaded onto SD-12. Loaded rPiOS-64 onto SD-13.
- And the really amazing thing, the gui python programs I tested actually worked!
- 2024-09-24:
- Got USB-C to USB-micro adapter and powered up rPi's with 3A supply. Power part of it seems to be working.
- Hooked up HDMI to small monitor, and IOGear wireless keyboard.
- Tried SD-17 (new 32-bit image) in rPi-04. Lots of red and green blinking, and monitor went black at times,
but no bootup screen appeared. Waited about 5 minutes. Pulled power. - Tried SD-17 in rPi-01 and rPi-02, same results.
- Tried SD-16 in rPi-02. Monitor screen never went black. Pulled power.
- Tried SD-19 (new with Stretch-Lite). Monitor screen cycled black to blue bunches of times,
but still no boot screen. - Google says likely the rPi is booting correctly, but HDMI is not enabled.
- forum suggests:
-
put
- hdmi_force_hotplug=1
in your config.txt file.
- Or: hdmi_safe=1, which combines the hotplug setting with several others...
The config file is on the partition you can read with your PC.
check out http://elinux.org/RPi_config.txt for other options- $ sudo nano /boot/config.txt
- Another suggestion:
- "same issue after successfully formatting the Micro SD cards.
Re-formatted, with the Logical Address Adjustment settings set to yes and it did the trick." - Another tip:
- "A regularly flashing green LED on a Pi 4B means the microSD card is not being detected."
Check for debris in the SD socket.
- forum suggests:
- Bad news is, if in fact it's booting, and the problem is just in the HDMI settings,
then I've surely trashed 3 more SD cards (16, 17, & 19) by pulling power without a "proper" shutdown. - Proceeded as if SD-19 was fine in spite of improper shutdown.
Put in card reader and edited config.txt to uncomment safe mode setting.
Back into rPi-02, it tried, green blinkies, but then they stopped and I just had solid red. Pulled power. - Finally success:
- Connected small monitor to Beelink and indeed it was NFG. Connected rPi-02 with SD-03 to Vizio monitor and it booted.
Installed SD-17 and it booted as well, taking me through initial setups, indicating that perhaps it did NOT boot at all before...
SD-16 and SD-04 booted as well. - SD-19, OTOH, booted into terminal. Tried startx to get to GUI (per forum), but didn't work. Did shutdown with:
- $ shutdown now
- Connected small monitor to Beelink and indeed it was NFG. Connected rPi-02 with SD-03 to Vizio monitor and it booted.
- 2024-09-20:
- Back at it after a year doing other things
- Checked SD card inventory, attemped to boot up several of my rPi's.
rPi-01 worked initially, but failed second try after doing "improper" shutdown. - Loaded new Imager program and created two new SD cards from new, blank versions in inventory.
Waiting for new power supply and USB-C adapters to test them. - 2023-01-30:
- Struggling to get Espotek and Arduino IDE AppImages to run on the pi-400.
Unsuccessful so far... - Took a lot of messing with file owners and permissions to get the 69-Labrador.rules.d file transferred from tower to pi-400
(have lost ref to source of the file...)
In the end what worked was to do everything in CLI.
Regardless would not run. - Per tip from itsfoss, did $ sudo apt install libfuse2
That worked, but AppImage still won't run. - 2022-Oct-06:
- Cranked up the 400, going through the process of making the serial communication work so I can interface it to RS485. Progress.
- Did the same with both rPiZero's I have. Managed to get serial port configured and functioning on rPiZ-01, but rPiZ-02, which is a W version, did not work.
That is, after much pulling plugs and trying different configurations, best guess is that it has some video output problem that locks it up. Either that or it just takes more amps than I was giving it, though I did try other supplies. - 2021-Feb-28:
- Using it for email with Chrome browser due to Firefox on Dell's not being able to get into Hotmail.
- Setting Desktop Preferences with right-click works, but changes are not saved with reboot.
searching forums ... - 2019-Dec-06:
- Auto-mounts, disk is currently empty.
GP shows 2 lines, sdf1 28+gb (fat32 lba), and 4mb unallocated
selected sdf1, Partition-unmount, Partition-delete, Edit-Apply
now 29+gb unallocated
closed GP - removed card, reinserted
/dev/sdf shows up
does not auto-mount - $ sudo fdisk -l ... shows /dev/sdf
$ sudo fdisk /dev/sdf n ... enter-x4 ... w
/dev/sdf1 successfully created as type: Linux - $ sudo fdisk /dev/sdf1
"Device does not contain a recognized partition table."- not sure what I'm doing here. Instructions I have say to create a partition, sdf1p1, assuming sdf1 already exists. However I had deleted sdf1 with GP, so now I've created it again with fdisk, however it is type linux, which I'm guessing is wrong, so I'll attempt to change it...
$ sudo fdisk /dev/sdf1 ... t
"no partition defined yet"
$ sudo fdisk /dev/sdf ... t ... b ... w
no errors.
$ sudo fdisk /dev/sdf ... p
shows sdf1 type: W95 FAT32 - removed card, reinserted
did not auto-mount, but /dev/sdf1 shows up - opened GP:
single partition, 29+gb, "unknown file system" - will attempt to format sdf1
removed card, reinserted
$ sudo mkfs.vfat /dev/sdf1
paused and completed without error
removed card, reinserted
auto-mounts
GP says: fat32 (no LBA!)
appears to have been successful - $ sudo fdisk /dev/sdf1 ... n ... enter x4 ... t ... b ... w
"Failed to add partition 1 to system: Invalid argument"
However: $ sudo fdisk /dev/sdf1 ... p ... shows sdf1p1 as type: W95 FAT32
which seems correct... - closed FM, ejected 32gb volume, removed card, reinserted card, auto-mounted
did some forum searching and best guess is I can ignore the "invalid argument" message, which in fact is consistent with my previous results... - OTOH, GP still only shows sdf1, does not show the p1 partition - perhaps since I haven't formatted it yet?
- $ sudo mkfs.vfat /dev/sdf1p1
"mkfs.vfat: unable to open /dev/sdf1p1: No such file or directory"
yet fdisk /dev/sdf1 shows the p1 partition, though FM /dev does not - close FM, eject removable drive, remove card, reinsert
$ sudo fdisk /dev/sdf1 ... p ... shows p1 partition
d ... w ... "invalid argument" (suspect 'w' was not needed)
however $ sudo fdisk /dev/sdf1 ... p ... shows no partitions
$ sudo umount /dev/sdf1
successful: listing removed from drive list
$ sudo fdisk /dev/sdf1 ... n ... enter-x4 ... w
"invalid argument"
However: $ sudo fdisk /dev/sdf1 ... p ... shows sdf1p1 as type: Linux
removed drive, reinserted, auto-mounted
GP: still only one line, but this time "sdg1" ???
ejected, (realized fdisk was still open???) closed fdisk, removed card, reinserted, auto-mounted, closed FM
FM shows /dev/sdf & sdf1
$ sudo fdisk -l ... shows sdf1
$ sudo fdisk /dev/sdf1 ... p ... shows p1 format as type: Linux
t ... b ... w ... successful
GP: still only shows one line, now back to sdf1, type: fat32 - ejected, removed, reinserted, auto-mounted
$ cd /media/jay/355C-ED83
$ sudo unzip /media/jay/OS/Users/Jay/myFiles/mstrWorkingFiles/Tech/microcontrollers/rPi/distros/buster/2019-09-26-raspbian-buster-full.zip
"write error (disk full?)" Arrgghhhh - looked at functioning cards SD-08 & SD-09 with GP. Neither of them show any p1 partitions, though fdisk sdf1 does show p1
Interestingly, they both show sdf2 & sdf6 as fat32 LBA - wondering if this latest batch of clone SD cards is bad. Will go back and try to re-do SD-06, which broke along the line, though what I've learned since may allow me to fix it, and it was from original shipment.
- inserted, did not auto-mount
GP shows sdf1, "unknown file system"
Partition-delete to remove it - removed card, reinserted
$ sudo fdisk /dev/sdf ... shows no partitions
n ... enter-x4 ... w
completed without error - removed card, reinserted
$ sudo fdisk /dev/sdf ... shows /dev/sdf1 partition
t ... b ... w
completed without error - removed card, reinserted, did not auto-mount
$ sudo fdisk /dev/sdf1 ... p ... shows /dev/sdf1p1 already there ???
but it's type: Linux, so:
t ... b ... w
completed without error - removed card, reinserted, did not auto-mount
Confusions here:- I created sdf1 from a supposedly blank card, yet:
I did not format it w/ mkfs,
plus it already had sdf1p1 partition defined...Accordingly, I will back up and start over:
$ sudo fdisk /dev/sdf1 ... d ... "partition 1 has been deleted"- note I did NOT do 'w', however when re-entering fdisk then p, sdf1p1 is still there, so:
$ sudo fdisk /dev/sdf1 ... d ... w
"failed to remove ... invalid argument"
regardless going in with fdisk p shows partition was in fact removed - Proceeding:
remove card, reinsert, did not auto-mount
$ sudo mkfs.vfat /dev/sdf1
completed without error
removed card, reinserted, and now it auto-mounts- not sure, but this time I will leave it mounted...
$ sudo fdisk /dev/sdf1 ... n ... enter-4x ... w
"failed to add ... invalid argument"
yet fdisk /dev/sdf1 ... p ... shows it's there as type Linux
ejected, removed, reinserted, auto-mounted
fdisk p confirms sdf1p1 still there
$ sudo mkfs.vfat /dev/sdf1p1
"unable to open ... no such file or directory"
regardless ... - ejected, removed, reinserted, auto-mounted
$ cd /media/jay/C00E-7BE4
$ sudo unzip /media/jay/OS/Users/Jay/Documents/myFiles/mstrWorkingFiles/Tech/microcontrollers/rPi/distros/buster/2019-09-26-raspbian-buster-full.zip
"inflating: 2019-09-26-raspbian-buster-full.img" proceded about 5 min but finally gave same error:- "write error (disk full?). Continue? (y/n/^C)"
This time I did ^C and it aborted the process. - Looking back through notes, I realized that I neglected to change sdf1p1 partition type from Linux to fat.
Accordingly will back up a bit...
inserted, auto-mounted, FM deleted partial .img file downloaded, closed FM
$ sudo fdisk /dev/sdf1 ... p shows sdf1p1 ... d ... w
$ sudo fdisk /dev/sdf1 ... p shows sdf1p1 gone
n ... enter-x4 ... w
same "invalid argument" error
$ sudo fdisk /dev/sdf1 ... p shows sdf1p1 ... t ... b ... w
completed without error
ejected, removed, reinserted, auto-mounted
$ sudo mkfs.vfat /dev/sdf1p1
"unable to open ... no such file or directory"
regardless ... - closed FM, ejected, removed, reinserted, auto-mounted
$ cd /media/jay/C00E-7BE4
$ sudo unzip /media/jay/OS/Users/Jay/Documents/myFiles/mstrWorkingFiles/Tech/microcontrollers/rPi/distros/buster/2019-09-26-raspbian-buster-full.zip
same "write error" - First attempt with this card was 12/05, and orig mfr partition for sdf1 was not touched.
- However first attempt left bunches of files of incomplete NOOBS install. Deleted all in FM.
$ sudo fdisk -l ... shows:
/dev/sdf1 type: W95 FAT32 (LBA)
$ sudo fdisk /dev/sdf1 ... p shows no partitions
n ... enter-x5 ... t ... b ... w
"invalid argument"
close FM, eject, remove - reinserted, auto-mount
$ sudo fdisk /dev/sdf1 ... p confirms sdf1p1 as fat32
$ sudo mkfs.vfat /dev/sdf1p1
"unable to open"
closed FM, ejected, removed - inserted, auto-mounted
$ cd /media/jay/3439-3334
$ sudo unzip /media/jay/OS/Users/Jay/Documents/myFiles/mstrWorkingFiles/Tech/microcontrollers/rPi/distros/buster/2019-09-26-raspbian-buster-full.zip
almost immediate "write error" - Failure
- Trying again with completely fresh card:
left sdf1 intact, created new sdf1p1, changed to fat32 before 'w',
all with command line, ie. no GP
same result. - deleted truncated .img
- 2019-Dec-05:
- Still trying to get a handle on SD card formatting...
SD-14:
This is a new card (Amazon, no doubt a clone)
It auto-mounts when inserted in a card reader.
$ sudo fdisk -l ... shows it has one partition, /dev/sdf1, type "W95 FAT32 (LBA)"- (one forum post said: "Without LBA, some BIOS could not address disks bigger than 8GB.")
Instructions I have for using GParted:
- say if I only have one partition (which seems to be the case with sdf1), then I should format-to FAT32. However it appears it is already formatted to that, so perhaps I'm done and can just go ahead and download files??
- Proceeding on that assumption:
$ cd /media/jay/3839-3334
$ sudo unzip /media/jay/OS/Users/Jay/Documents/myFiles/mstrWorkingFiles/Tech/microcontrollers/rPi/distros/NOOBS_v3.2.1/NOOBS_v3_2_1.zip
Errors:- "inflating: os/LibreELEC_RPi4/release_notes.txt
inflating: os/LibreELEC_RPi4/System.tar.xz
error: cannot create os/LibreELEC_RPi4/LibreELEC_RPi4.png
Input/output error
error: cannot create os/LibreELEC_RPi4/os.json
Input/output error
checkdir error: cannot create os/Raspbian_Full
Input/output error
unable to process os/Raspbian_Full/." - OK, so maybe my distro is corrupted? Will download fresh:
- This time I will download "Raspbian Buster with desktop and recommended software"
SHA-256: 549da0fa9ed52a8d7c2d66cb06afac9fe856638b06d8f23df4e6b72e67ed4cea - "write error (disk full?)"
- Sheesh. OK, so the distro is not the problem...
- 2019-Dec-04:
- SD-10: powered up and attempted to boot.
Rainbow screen came up, then dialog box saying I needed wifi connection
to load NOOBS when I didn't have a local image on the SD card. - So indeed the download of NOOBS to the SD card failed as indicated yesterday. Back to the drawing board...
- Opened GParted. Selected SD card (sdf1). There were several partitions defined now, apparently by the NOOBS program, so I deleted all of them (had to unmount first...), then Apply. Attempted to create a new partition...
- Not being very disciplined about recording every step I've taken ...
- Removed and reinsertted SD card. Does not mount. FM shows /dev/sdf.
- Opened GParted.
- Selected /dev/sdf from drop-down in upper right corner. One line, 29.72gb, unallocated partition & file system.
- right-click "Format to" option not available.
- Partition (top menu-bar) > New
default is "primary partition"
selected "fat32" File System, then "Add" - GParted now shows:
Petition: "New Partition #1" with fat32 File System
"Format to" option is now available, but will decline this time... - Edit (top menu bar) > Apply All Operations > Apply > Close (after successful completion)
Label is gibberish - removed SD card. Re-inserted. Still nothing mounted. FM however now shows /dev/sdf & /dev/sdf1
Opened terminal. But /media/jay empty because card is not mounted. GParted shows mount option unavailable. - Back to GParted:
Partition > Format to > fat32
Edit > Apply All Operations > Apply > Close
"Label" column no longer shown
Partition > mount still unavailable. - removed and reinserted; still not mounted
GParted (top menu bar) > Refresh Devices
Partition > mount still unavailable. - $ sudo mount /dev/sdf1 /media/jay/root (root directory already created)
Successful: 32gb volume now listed in Removable drives - $ cd /media/jay/root
$ sudo unzip /media/jay/OS ... to buster zip file
Same as before. Unzip started, then quit with:- "os/Raspbian_Full/root.tar.xz: write error (disk full?). Continue? (y/n/^C)"
entered "n" to quit.
- Removable drives oddly shows two listings for 32gb volume.
perhaps auto-mount did in fact work and I just didn't wait long enough to see it before manually mounting...
clicking to eject lower one did nothing
ejecting top one worked, SD card reader light went out
mount shows sdf1 still mounted at /media/jay/root
$ sudo umount /dev/sdf1 ...
"mount: /media/jay/root: target is busy."
cd terminal to /media, same with FM, still busy...
closed all FM windows, closed and reopened terminal and now unmounted successfully. - Inserted in card reader - mounted as /dev/sdf1 on /media/jay/E01D-ADAC
- Opened GParted:
- selected /dev/sdf (top-right drop-down)
- select /dev/sdf1 line to highlight
- Partition > unmount
listing removed from Removable drives - select /dev/sdf1 line to highlight
- Partition > delete
- Edit > Apply All Operations > Apply > Close
- Partition > New > select fat32 > Add
Edit > Apply All Operations > Apply > Close
(no gibberish label this time...) - Removed card; closed GParted; reopened GParted
Inserted card; did not auto-mount
GParted > Refresh Devices - select /dev/sdf from drop-down
mount option not available, but
Partition > Format to > fat32
Edit > Apply All Operations > Apply > Close - Close GParted, remove card, wait 30sec, reinsert card,
mounted as /dev/sdf1 on /media/jay/9724-D1BB - closed and re-opened terminal
$ cd /media/jay/9724-D1BB
$ sudo unzip /media/jay/OS/Users ... [buster].zip
Same failure - disk full Arrgghhh! - Inserted in card reader - mounted as /dev/sdf1 on /media/jay/6539-3334
- Opened GParted:
- selected /dev/sdf (top-right drop-down)
- select /dev/sdf1 line to highlight
- Partition > unmount
listing removed from Removable drives - select /dev/sdf1 line to highlight
- Partition > delete
- Edit > Apply All Operations > Apply > Close
- Partition > New > select fat32 > Add
Edit > Apply All Operations > Apply > Close
(no gibberish label this time...) - Closed GParted; Removed card; reopened GParted
Inserted card; did not auto-mount
GParted > Refresh Devices - select /dev/sdf from drop-down
mount option not available, but
Partition > Format to > fat32
Edit > Apply All Operations > Apply > Close - Close GParted, remove card, wait 30sec, reinsert card,
mounted as /dev/sdf1 on /media/jay/BA3C-3320 - closed and re-opened terminal
$ cd /media/jay/BA3C-3320
$ sudo unzip /media/jay/OS/Users ... [buster].zip
Apparrent at least partial success, in that the process finished without locking up...
However I got a bunch of errors & warnings like this:- " extracting: os/LibreELEC_RPi4/LibreELEC_RPi4.png
error: cannot create os/LibreELEC_RPi4/os.json
Input/output error
checkdir error: cannot create os/Raspbian_Full
Input/output error
unable to process os/Raspbian_Full/.
checkdir error: cannot create os/Raspbian_Full
Input/output error
unable to process os/Raspbian_Full/boot.tar.xz.
checkdir error: cannot create os/Raspbian_Full
Input/output error
unable to process os/Raspbian_Full/partition_setup.sh.
checkdir error: cannot create os/Raspbian_Full
Input/output error
unable to process os/Raspbian_Full/root.tar.xz." - Closed terminal & File manager, ejected 32gb volume
- Inserted into rPi-04 and attempted to boot NOOBS.
raspberry came up, NOOBS initialized, but like before, said:
"Network access is required to use NOOBS without local images..." - Inserted into card reader; auto mounted; ejected
- Opened GParted. SD card not visible.
Opened terminal. SD card not shown with fdisk
Removed card, reinserted. Did not auto-mount, but fdisk sees it, as does GP - in GParted:
selected sdf1
Partition - delete - Apply
Partition - new - fat32 - Add - Apply
closed GParted - Removed card - reinserted - auto-mounted to /media/jay/F101-377E
but curiously, in spite of re-partitioning, files created by NOOBS are still there.
tried to deleted them in FM, but message said it was a read-only file system. - Opened GParted: closed /media file manager; selected /dev/sdf1; Partition - unmount;
Partition - delete - Apply
Partition - new - fat32 - Add - Apply
Partition - Format to - fat32 - Apply
GParted - quit - removed card; reinserted; auto-mounted; files are now gone.
- manually copied (drag & drop) files from extracted stretch distro
lots of errors...
closed terminal, ejected and removed card
inserted into rPi-02 and booted - hangs at rainbow screen - attempting to manually copy results in errors (splicing files)
deleted all files, closed FM, ejected, removed, reinserted, opened GParted - selected /dev/sdf, selected /dev/sdf1,
Partition - unmount
select, Partition - Format to - ext 4 - Apply - error, same with ext 3
tried other things, nothing worked ... - deleted partition in GParted. closed GP, removed SD, reinserted...
sudo fdisk /dev/sdf ... n ... enter-enter-enter ... t ... b ... w
but then could not mount it... bad superblock... - 2019-Dec-03:
- SD-10 continuing from yesterday...
- Inserted SD into card reader in Linux tower
In File manager, deleted all files - $ cd /media/jay/3239-3334
- $ unzip /media/jay/OS/Users/Jay ... ... to zip file
- unzip failed for:
- Opened GParted and looked at the SD card. It showed a single partition in FAT32 (as I recall, not sure...)
- closed file manager and terminal,
ejected SD card, inserted into rPi-04 ... - 2019-Dec-02:
- SD-10: Starting with a new SD card (32gb SanDisk), unformatted (except from mfr),
generally following this procedure: - in Linux tower:
- File manager opens to: /media/jay/3239-3334
- Removable drives shows: 32gb volume
- File manager shows: /dev/sdf & /sdf1
- $ mount | grep sdf ... shows: /dev/sdf1 on /media/jay/3239-3334 type vfat
- $ sudo fdisk -l ... shows (start / end / sectors / size / ID / type:
"/dev/sdf1 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)" - $ sudo fdisk /dev/sdf1 ... p ... shows:
sector size: 512; type: dos - Create partitions:
- $ sudo fdisk /dev/sdf1
- d ... no partitions defined
- n ... p ... 1 ... enter ... enter ...
Linux partition created, 29.7gb - t ... b
partition type changed from Linux to W95 FAT32 - w ... enter
same error as before ... fdisk closed - $ sudo fdisk /dev/sdf1 ... p
confirms sdf1p1 partition successfully created - closed terminal, no file manager windows open,
ejected 32gb volume, removed SD card - Inserted SD card in Linux tower:
- File manager opens to: /media/jay/3239-3334
- Removable drives shows: 32gb volume
- File manager shows: /dev/sdf & /sdf1
- $ mount | grep sdf ... shows: /dev/sdf1 on /media/jay/3239-3334 type vfat
- $ sudo fdisk -l ... shows same as above
- $ sudo fdisk /dev/sdf1 ... p ... shows (start / end / sectors / size / ID / type):
/dev/sdf1p1 2048 62325759 62323712 29.7G b W95 FAT32 - Format:
- $ sudo mkfs.vfat /dev/sdf1
"mkfs.vfat: /dev/sdf1 contains a mounted filesystem." - $ sudo fdisk /dev/sdf1 ... p ... shows same as above
- Best Guess:
the SD card comes pre-formatted and the mkfs command does nothing... - load software onto card:
- eject and reinsert SD card
- $ cd /media/jay/3238-6132 (or wherever)
$ unzip [full path/filename to zip file] - However:
after starting the unzip process, got bunches of errors similar to this:- "checkdir error: cannot create overlays
Input/output error
unable to process overlays/ilitek251x.dtbo."as well as a "disk full" error
Stopping here, will resume tomorrow... - 2019-Nov-27:
- Reviewing SD08
- Inserting into card reader in Linux tower:
file manager shows: /dev/sdf & /dev/sdf1
$ sudo fdisk /sdf1 ... shows 3 partitions, p1, p2, & p4
$ mount | grep sdf1 ... shows /dev/sdf1 on /media/jay/SD08- (recall SD08 was formatted in Windows, with 'SD08' specified as disk name)
file manager on /media/jay/SD08 ... shows
- one directory 'System Volume Information'
- Copied all files from extracted NOOBS 2.4.3 into SD08
- ejected from tower, inserted into rPi-02
booted successfully, selected Raspbian.
Works!
- Inserting into card reader in Linux tower:
- 2019-Nov-24:
- SD02:
- At start, inserting into card reader in Linux tower:
- $ mount | grep sdf shows:
sdf5 on /media/jay/SETTINGS type: ext4
sdf6 on /media/jay/boot type: vfat
sdf7 on /media/jay/root1 type: ext4 - file manager shows: /dev/sdf, sdf1, sdf2, sdf5, sdf6, & sdf7
- $ sudo fdisk -l shows:
/dev/sdf1 type: W95 FAT16
/dev/sdf2 type: extended
/dev/sdf5 type: Linux
/dev/sdf6 type: W95 FAT32
/dev/sdf7 type: Linux - $ sudo fdisk /dev/sdf1 ... p shows:
p1, p2, p3, & p4 defined
$ sudo fdisk /dev/sdf2 ... p shows:
p1 & p2 defined, however also gives error:
"Failed to read extended partition table (offset=66128): Invalid argument"
$ sudo fdisk /dev/sdf5 ... p shows no partitions defined, however gives error:
"The old ext4 signature will be removed by a write command."
$ sudo fdisk /dev/sdf6 ... p shows no partitions defined
$ sudo fdisk /dev/sdf7 ... p shows no partitions defined, however gives error:
"The old ext4 signature will be removed by a write command." - Attempting to repair:
- $ sudo fdisk /dev/sdf7 ... w, then
$ sudo fdisk /dev/sdf7 ... p shows no partitions defined, with no error. - $ sudo fdisk /dev/sdf ... d ... 7 ... w gives error for device busy
attempted to closed /media/jay/root1 file manager ... but it wasn't open???
However $ sudo fdisk /dev/sdf ... p ... no longer lists sdf7, so it apparently worked... - Closed /media/jay/boot file manager window (sdf6)
$ sudo fdisk /dev/sdf6 ... p ... confirms no partitions
$ sudo fdisk /dev/sdf ... d ... 6 ... w ...
$ sudo fdisk /dev/sdf ... p ... confirms 6 bdeleted - Closed /media/jay/SETTINGS file manager window (sdf5)
$ sudo fdisk /dev/sdf5 ... w
$ sudo fdisk /dev/sdf5 ... error has been removed
$ sudo fdisk /dev/sdf ... d ... 5 ... w
$ sudo fdisk /dev/sdf ... p ... shows 5 removed - $ sudo fdisk /dev/sdf2 no longer shows any partitions. WTF???
$ sudo fdisk /dev/sdf ... d ... 2 ... w
$ sudo fdisk /dev/sdf ... p ... confirms 2 deleted - $ sudo fdisk /dev/sdf ... d ... [default accepted without my entry] ... w
$ sudo fdisk /dev/sdf ... p ... confirms no partitions - However: Removable drives still shows:
boot, 34 MB volume, and 6.2 GB volume
and $ mount | grep sdf ... still shows sdf5, 6, & 7 still mounted
ejected boot and all 3 disappeared
$ sudo mount shows no sdf drives mounted
removed and reinserted SD card...
nothing mounted, but /dev/sdf is listed
removed SD card
Looks like everything has worked so far, all partitions successfully removed ... - Attempting to write NOOBS:
- inserted SD card w/ reader into Linux tower
nothing mounted - $ sudo fdisk -l ... shows sdf
file manager likewise shows /dev/sdf - $ sudo fdisk /dev/sdf ... n ... p ... 1 ... enter ... enter ... w
successful w/ no errors
$ sudo fdisk /dev/sdf ... t ... b ... w
successful w/ no errors - $ sudo mkfs.vfat /dev/sdf1p1
"unable to open" error - removed, reinserted
nothing mounted, however
$ sudo fdisk -l ... shows /dev/sdf1 - Instructions say I need to mount it in order to download software.
Already have an empty directory /media/jay/root
$ sudo mount /dev/sdf1 /media/jay/root
error: "mount: /media/jay/root: wrong fs type, bad option, bad superblock on /dev/sdf1, missing codepage or helper program, or other error."
Arrgghhh And here I thought things were going so well ... - $ sudo fdisk /dev/sdf ... deleted sdf1 partition
- removed, inserted into Windows tower:
initial response was to ask for me to insert a disk, though it was already inserted
opened a command window and executed:
format i:
error message:- "C:\Users\Jay>format i:
Insert new disk for drive I:
and press ENTER when ready...
The type of the file system is RAW.
The new file system is FAT.
Verifying 0.0 Bytes
The specified cluster size is too big for FAT.
Format failed." - ...
- inserted SD card w/ reader into Linux tower
- 2019-Nov-23:
- SD08 & SD07
- Inserted into tower with Windows booted.
Prompt asked if I wanted to format - clicked yes.
Entered 'SD07' & 'SD08' as drive name - formatting seemed to complete successfully
- Proceeding with SD07: Drive mounted automatically when inserted into tower with Linux booted.
- fdisk shows device name still sdf1
- Proceeding to format and install NOOBS:
- $ sudo fdisk /dev/sdf1
d shows partitions 1, 2, & 4 defined.
deleted 4, but would not allow deleting 2, didn't try #1 ... - Created new primary partition per instructions, however it called it p3, since p1 & p2 had not been deleted
- $ sudo mkfs.vfat /dev/sdf1p3
"unable to open ... no such file ..."
Regardless, proceeded, as before... - Closed file manager, ejected card, reinserted...
$ mount says it's mounted at /media/jay/SD07 - $ cd /media/jay/SD07
$ unzip [pathname to NOOBs.zip]
closed terminal & file manager, ejected card - inserted card into rPi02
booted into NOOBS, selected Raspbian,
installation & boot completed successfully. - Looks like I have a workable recovery procedure for cards with superblocks damaged.
No clue if there may be future consequences to the remaining p1 & p2 partitions on the card. - 2019-Nov-21:
- SD09:
- downloaded and installed Seq24 a Midi sequencer (with software manager)
Could not quickly figure out software, though it did recognize my Roland adapter. - Installed Muse (with software manager), another Midi sequencer
Have not tested it. - Also installed Firefox-esr browser
- $ sudo apt update
- $ sudo apt install firefox-esr
- Removed Chromium (with software manager)
- rPiZW-02
Works, works with 4-port USB hub - rPiZ-01
Works, but not with USB hub.
Will disassemble and re-assemble... - 2019-Nov-20 (continued):
- After doing all below, then update & upgrade, then installing gparted, then restarting,
then re-inserting the SD, it now comes up (with fdisk -l) as sdb, not sdf.
Removing then reinserting removed then reinstates sdb and sdb1 in /dev,
while sdf remains in /dev whether or not the SD is inserted. - 2019-Nov-20:
- As of now I have SD06, SD07, & SD08 all damaged. [earlier] notes about damaged SD cards not auto mounting were clearly not for SD06, which as I found yesterday mounts just fine. Will update status of other cards later, but for now will try to reformat SD06.
- I started the reformat procedure on this card yesterday, by deleting all the partitions. Today when I insert it, it does not mount (shown by both lsblk & mount). However /dev/sdf is indeed listed in file manager, so proceeding:
- $ sudo fdisk /dev/sdf
"Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0xca779b04." - [fdisk] p shows:
"Disklabel type: dos
Disk identifier: 0xca779b04" - Not sure how to proceed, but took a shot with:
[fdisk] w
seems to have been successful
$ lsblk now shows sdf as type disk with no mountPoint
$ mount shows nothing for sdf - Removed SD card reader and re-inserted
Auto-mounted: /SETTINGS, /root, & /boot partitions all there, along with all their files.
$ mount shows partitions SDF5 (/SETTINGS), SDF6 (/boot), and SDF7 (/root) all mounted
$ lsblk also shows sdf1 & sdf2 - $ sudo fdisk -l shows:
sdf1 as type W95 FAT16
sdf2 as type Extended
sdf5 as type Linux
sdf6 as type W95 FAT32
sdf7 as type Linux - Instructions now say to delete any existing partitions, but not sure if "sdf1 ... 7" are "partitions."
They don't have p1 or similar designations.
Plus deleting was what I did yesterday, and they all came back, however I'm not sure the 'order' in which I deleted things, and also I may have deleted sdf1, but this time I will not do that (?) ... - sudo fdisk /dev/sdf1
p returns:
"/dev/sdf1p1 2048 62325759 62323712 29.7G b W95 FAT32"
[what is returned by 'p' on a new, blank SD card ???]
which suggests indeed a partition is there, maybe primary?
OTOH address numbers and size suggest it is a single partition covering the whole card.
"Command (m for help): d
Selected partition 1
Partition 1 has been deleted."
"Command (m for help): n
enter (primary), 1, enter, enter
p returns:
"/dev/sdf1p1 2048 5007433 5005386 2.4G 83 Linux"
t, b changed to W95 FAT32
w seems to have worked (same as instructions) - $ sudo mkfs.vfat /dev/sdf1p1
returned same error as described in instructions, regardless proceeding... - ejected via 'removable drives", (/boot cleared all 3)
re-inserted, and all 3 drives and file managers opened. - Flying blind here. Am going to try to delete all the files and directories:
$ cd /media/jay
$ sudo rm -rf root
"rm: cannot remove 'root': Device or resource busy"
even though I closed file manager window ...
ejected /SETTINGS in removable drives. All 3 drives gone.
$ sudo rm -rf boot
no error message...
$ ls shows only OS & sdf - trying again... pulling and reinserting SD...
3 drives mounted, 3 file managers opened,
however this time /root & /boot have no files in them. - $ ls SETTINGS showed all files still there
$ sudo rm -rf SETTINGS
same 'busy' error, however
$ ls SETTINGS showed it did in fact clear all the files - tried a bunch of stuff in file manager, still unable to delete these 3 folders.
$ mount | grep boot shows sdf6 is mounted on it
in /media/jay, $ sudo umount sdf6
"no mount point specified"
$ cd /dev
$ sudo umount sdf6
seems to have worked.
$ ls /media/jay now shows only root & SETTINGS - ejected and reinserted...
but again all 3 are back - used fdisk to delete partitions 6 & 7
sudo mountpoint boot ... & root ... both listed as 'mountpoints' - however, after again ejecting and reinserting,
neither boot nor root are listed as mount points, and only SETTINGS is in 'removable drives' list
/media/jay only shows SETTINGS,
/dev shows sdf, sdf1, sdf2, & sdf5
feels like progress - $ cd /media/jay
$ sudo fdisk /dev/sdf1
p shows sdf1p1
$ sudo fdisk /dev/sdf2
p shows sdf2p1
$ sudo fdisk /dev/sdf5
says no partition table
p shows "Disk identifier: 0x3407135a" - $ sudo fdisk /dev/sdf
d, 5, w
p now only shows 1 & 2 - eject & reinsert...
nothing in removable drives or /media/jay
/dev has sdf, sdf1, & sdf2
$ dmesg says sdf attached
$ sudo fdisk -l shows sdf1 & sdf2
$ sudo fdisk /dev/sdf1
p shows sdf1p1
$ sudo fdisk /dev/sdf2
p now shows no partitions
$ sudo fdisk /dev/sdf
d, 2, w
p now only shows 1
d, (deleted the only partition, #1, without prompt) w
p shows no partitions
$ mount | grep sdf shows nothing mounted
/dev shows only sdf
red light is still on - pulled SD card, reinserted
nothing in removable drives or /media/jay, no file managers opened
/dev shows sdf
$ sudo fdisk /dev/sdf
n, p, 1, enter, enter
(address options were different than with blank SD...)
t, b, w
p now shows sdf1 created
$ sudo fdisk /dev/sdf1
n, p, 1, enter, enter
same results as before, appears successful
$ sudo mkfs.vfat /dev/sdf1p1
same results as before, appears successful - red light still on, nothing in removable drives,
no file managers open,
pulled SD, reinserted
but this time nothing mounted
$ sudo mkdir /media/jay/root
$ sudo mount /dev/sdf1 /media/jay/root
"bad superblock" arrgghhhh
so maybe this is just trash... - searched online and found this site:
link to: oracle.com
It recommends a module called newfs to fix the problem.
However I have not been able to find such a command. apt install doesn't work...
Bottom line at least for now is this appears to be another dead end. SD06 may be toast - 2019-Nov-19:
- At least a partial update on the last couple of days of fumbling:
- Still unsuccessful at getting a driver installed for the TFT LCD screen on the rPi.
- In the failed attempts have now generated a couple of "bad" SD cards. The driver installs failed by hanging up during boot, but when I attempted to reformat them with a SD card reader on my PC, fdisk didn't see them, ie I think they were not "mounted."
- trying different things...
- inserted SD06 into card reader. auto mounted successfully as shown by:
3 file manager windows opened, /SETTINGS, /boot, & /root, and all are shown on list of 'Removable drives'
$ sudo mount | grep sd
$ lsblk and
$ sudo fdisk -l show sdf1 (W95 FAT16), 2 (Extended), 5 (Linux, /SETTINGS), 6 (W95 FAT32, /boot), & 7 (Linux /root)
$ dmesg says "volume was not properly unmounted ... please run fsck"
(fsck == "file system consistency check") - tutorials online say to use -N option,
"only show what should be done - do not make any changes" - in order to run fsck, the partition you are checking must not be mounted.
$ sudo umount /dev/sdf[n] repeated for each partition,
after which listings disappeared from "removable drives" list. - $ sudo fsck /dev/sdf
Gave bunch of error lines, notably "Bad magic number in super-block ... Superblock invalid ..." - 2019-Nov-16:
- SD-07: boots ok in rPi-02
- $ df -h: reports 22gb avail in root, with lots of other stuff I don't understand...
- $ sudo apt-get clean: no change
$ sudo apt-get autoclean: no change
$ sudo apt-get autoremove: no change - Opened network icon from lower right and entered router pw. Connected
- Repeated Waveshare driver download that I did yesterday with SD-06,
but failed again. - SD-07:
attempted to re-format etc. per my instructions here: but things didn't work. After fumbling around, I gave up and set it aside, since inserting it didn't show anything in "removable media". - SD-08:
format etc. per my instructions here: successfully loaded stretch - Preparing to follow procedure from "Out of Stock" site:
- 2019-Nov-15:
- Damaged SD card socket on rPi-03. Still boots and works as far as tested, still will put aside and attempt to repair later.
- Created SD-06 with buster, using full tutorial.
However after downloading Waveshare driver attempting to get TFT LCD working, it won't boot, saying "Mode Not Supported".
Will re-partition and start over. - Created SD-07 with stretch, using full tutorial.
- 2019-Oct-25:
- SD03 created successfully from a blank 16gb SD card. Reformatted and partitioned card per tutorial. Tested in rPi-04. Loaded Raspbian 10 buster
- SD05 created by copying extracted files of NOOBS v2.4.3 from tower Linux to blank (msdos) 16gb SD. Did not reformat or partition. Regardless it appears to have worked and is currently booting...
- Started up rPi-02 (with same supply and cord and SD card) and it comes up just fine. Boots directly, ie no NOOBS selections offered. Did I load it previously??
$ cat /etc/os-release shows it's running Rasbian 9 Stretch
Logitech Unifying Receiver works with trackball and keyboard.
Logged into Century Link router and internet works. - 2019-Oct-23:
- rPi-03:. Boots up fine with either of the two SD cards I have that have confirmed Rasbian OS.
- wifi verified working.
- $ df -h reports 785 mB available
$ sudo apt clean
now df -h reports 1.2 gB available - rPi-02:. Wifi confirmed working.
- 2019-Oct-21:
- Starting up the rPi-04. Installing 8 gb microSD w/ full pixel desktop NOOBS from Adafruit (PID: 3259).
Connected HDMI to monitor and micro USB power. Monitor shows rainbow screen, but hangs there. Red LED on board blinks 4 longs & 4 shorts and repeats.
Forums suggest power issues, but same supply and cord powers up the touchscreen rPi just fine. At this point suspect a bad board. - 2019-Oct:
- Powered up the newark desktop box, and it initially worked, but then seemed to lock up, and wouldn't power down with the power button so pulled the power plug, but now it won't come back up.
- 2017-Sep:
- Working with various python programs. None ready to publish here yet. Main project is to write a GUI for the touchscreen, to use in the GMC. Initial programming successful so far; learning lots of code and Linux weirdness. Will document WIGATI.
- Secondary project is to figure out how to make a program run in background on bootup. Done and documented [where?]
- Have discovered that my SD card appears to be corrupted. It works, ie. boots up, but whereas earlier (before it got corrupted) I could edit and save programs and they'd still be there after a reboot, when it got corrupted it would no longer save them. It looked like it was, but apparently the edits were just saved to a buffer, and after reboot they were gone.
Got a new SD card and all is well again. Did a hardware switch to do a soft shutdown as recommended to prevent such things. Will document later... - 2017-Aug:
- Connected a 7" Touch screen and all worked. Screen touch calibration is off a bit, and the resolution is so high that the tiny little "x" and other icons like in the corner of the windows is almost impossible to hit with a finger..
- Also, it appears that I can't use the touchscreen at the same time as the HDMI output.>/li>
- 2016-Oct:
- Bought a rPi 3 model B V1.2 from Adafruit, along with a TFT screen, but did not get it running before moving to other projects.
Now I'm back at it and first thing I see is that there's no SD card. If I swap in the SD card from my B+, it boots as far as the very first multi-colored screen, but locks there and never goes further.
Adafruit has a bewildering assortment of SD cards. Sent them an email asking for help. - 2016-Jly:
- Finally cranked it up. After a bunch of learning curve, I managed to get it up and running.
- The File Manager is very Windows-like, and was easy to navigate in, easy to create directories, move files, etc.
- Used Leafpad text editor to begin editing my first Python program.
Connected a breadboard, wrote a python program to blink an LED, and it all worked! - 2015-Feb:
- Bought my first Rpi.
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
- (go to:) rPi-400:
------------------------------------------------------------------------
- SD-13:
---------------------
- SD-06:
---------------------
- SD-14:
---------------------
- SD-15:
------------------------------------------------------------------------
---------------------
------------------------------------------------------------------------
--------------------------
- SD-10 Re-try:
--------------------------
- SD-12: Attempt with un-used card, repeating SD-10 Re-Try from above...
--------------------------
- SD-10: 2nd Re-Try:
------------------------------------------------------------------------
- "os/LibreELEC_RPi4/LibreELEC_RPi4.png: write error (disk full?). Continue? (y/n/^C)"
selected 'y' and it continued with bunches of errors...
------------------------------------------------------------------------
- Screwup?
card mounted as /dev/sdg1 because I had neglected to close out the fdisk /dev/sdf1 command...
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------------------------------------------
eof
Powered by Drupal