[beagleboard] Re: cpufreq-info only 800MHz but I need 1GHz
Dennis - Thank you very much for the suggestions and information. Maybe I will try dd to copy some of the eMMC. But it appears to be beyond my limited understanding, and low chance of success. Blair On Wednesday, June 26, 2019 at 2:07:21 PM UTC-4, Dennis Lee Bieber wrote: > > On Wed, 26 Jun 2019 05:14:11 -0700 (PDT), > activewh...@gmail.com declaimed the > following: > > >Dennis, thanks for explaining how mount won't work. No 2nd BBB. > >Can I do cat of eMMC to read the contents of some of the files? The > >important files I need are c/cpp source text files. From the mSD, how do > I > >specify the eMMC directory? > > With no partition table, there is no way to tell it where the > "directory" is located. It needs to know where the start of the partition > was to then locate the data structures telling it where the files are. > Note > that in Linux, the "directory" is just another file > > http://tldp.org/LDP/intro-linux/html/sect_03_01.html > (Lots of stuff on that page, but I'm going to quote from the end...) > """ > 3.1.3.2. The file system in reality > > > > Every partition has its own file system. By imagining all those file > systems together, we can form an idea of the tree-structure of the entire > system, but it is not as simple as that. In a file system, a file is > represented by an inode, a kind of serial number containing information > about the actual data that makes up the file: to whom this file belongs, > and where is it located on the hard disk. > > Every partition has its own set of inodes; throughout a system with > multiple partitions, files with the same inode number can exist. > > Each inode describes a data structure on the hard disk, storing the > properties of a file, including the physical location of the file data. > > > > > The only information not included in an inode, is the file name and > directory. These are stored in the special directory files. By comparing > file names and inode numbers, the system can make up a tree-structure that > the user understands. Users can display inode numbers using the -i option > to ls. The inodes have their own separate space on the disk. > """ > > Information for one of my BBB (but I have no idea if it varies any > from > reflash to reflash -- or based upon who provided the eMMC, mine is old > enough to have Micron chips for eMMC and SDRAM) -- use fixed width font > > debian@beaglebone:~$ sudo fdisk -l > [sudo] password for debian: > Disk /dev/mmcblk1: 3.7 GiB, 3925868544 bytes, 7667712 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disklabel type: dos > Disk identifier: 0xc57622dd > > Device Boot Start End Sectors Size Id Type > /dev/mmcblk1p1 * 8192 7667711 7659520 3.7G 83 Linux > > > > > Disk /dev/mmcblk1boot1: 1 MiB, 1048576 bytes, 2048 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > > > Disk /dev/mmcblk1boot0: 1 MiB, 1048576 bytes, 2048 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > debian@beaglebone:~$ > > debian@beaglebone:~$ sudo parted -l > Error: /dev/mmcblk1boot0: unrecognised disk label > Model: Generic SD/MMC Storage Card (sd/mmc) > Disk /dev/mmcblk1boot0: 1049kB > Sector size (logical/physical): 512B/512B > Partition Table: unknown > Disk Flags: > > Model: MMC MMC04G (sd/mmc) > Disk /dev/mmcblk1: 3926MB > Sector size (logical/physical): 512B/512B > Partition Table: msdos > Disk Flags: > > Number Start End SizeType File system Flags > 1 4194kB 3926MB 3922MB primary ext4 boot > > > Error: /dev/mmcblk1rpmb: unrecognised disk label > Warning: Error fsyncing/closing /dev/mmcblk1rpmb: Input/output error > Retry/Ignore? i > Model: Generic SD/MMC Storage Card (sd/mmc) > Disk /dev/mmcblk1rpmb: 131kB > Sector size (logical/physical): 512B/512B > Partition Table: unknown > Disk Flags: > > Error: /dev/mmcblk1boot1: unrecognised disk label > Model: Generic SD/MMC Storage Card (sd/mmc) > Disk /dev/mmcblk1boot1: 1049kB > Sector size (logical/physical): 512B/512B > Partition Table: unknown > Disk Flags: > > debian@beaglebone:~$ sudo lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > mmcblk1 179:00 3.7G 0 disk > +-mmcblk1p1 179:10 3.7G 0 part / > mmcblk1boot0 179:801M 1 disk > mmcblk1boot1 179:16 01M 1 disk > mmcblk1rpmb 179:24 0 128K 0 disk > debian@beaglebone:~$ > > debian@beaglebone:~$ sudo blkid > /dev/mmcblk1p1: LABEL="rootfs" UUID="0983c07a-71fe-435f-b97f-f7a36e2fc3d3" > TYPE="ext4" PARTUUID="c57622dd-01" > /dev/mmcblk1: PTUUID="c57622dd" PTTYPE="dos" >
[beagleboard] Re: cpufreq-info only 800MHz but I need 1GHz
Dennis, thanks for explaining how mount won't work. No 2nd BBB. Can I do cat of eMMC to read the contents of some of the files? The important files I need are c/cpp source text files. From the mSD, how do I specify the eMMC directory? Or somehow copy a block of the eMMC. Then search it to extract the text content. Blair On Tuesday, June 25, 2019 at 12:49:41 PM UTC-4, Dennis Lee Bieber wrote: > > On Mon, 24 Jun 2019 19:23:54 -0700 (PDT), > activewh...@gmail.com declaimed the > following: > > >Dennis, thanks for explaining an option. I have the original image on > mSD. > >Can that be used to recreate (copy or build) the proper partition table > on > >the eMMC? How is that done? Maybe the data will not be overwritten. If it > >does not work, I will lose all data anyway when reflash all. > > > > I don't know enough about what gets done when running the normal > flasher (eg: does it create partitions or rely on the eMMC already having > a > partition table; if it creates a partition table then only running that > part without formatting the partitions might give access). > > Copying the start of the SD card likely won't work either as a > true SD > card has a reserved section (for the "secure" functions that nobody > actually uses), so is likely in a different layout. > > >Based on the above dd command (I ran by mistake), maybe from mSD run: > >sudo mount /dev/mmcblk1 > > > >Then remove mSD and reboot. > > > > Won't work -- part of the reboot sequence is to dismount "disk" > file > systems. > > > >But I don't know if I have all the correct parameters such as block size > or > >count or destination. Thanks for any help. > > > > If you had a second BBB maybe a dd command to copy the start from > ITs > eMMC, put that (as a file) on the SD card, and dd command to write that > file to the bad system eMMC > > > I suspect short of being able to manually examine everything on > the > eMMC there may not be any way to recover. > > > -- > Wulfraed Dennis Lee Bieber AF6VN > wlf...@ix.netcom.com > http://wlfraed.microdiversity.freeddns.org/ > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/d9acdfc3-9e36-4727-9f27-7af1ef888760%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: cpufreq-info only 800MHz but I need 1GHz
Dennis, thanks for explaining an option. I have the original image on mSD. Can that be used to recreate (copy or build) the proper partition table on the eMMC? How is that done? Maybe the data will not be overwritten. If it does not work, I will lose all data anyway when reflash all. Based on the above dd command (I ran by mistake), maybe from mSD run: sudo mount /dev/mmcblk1 Then remove mSD and reboot. But I don't know if I have all the correct parameters such as block size or count or destination. Thanks for any help. Blair On Monday, June 24, 2019 at 1:12:04 PM UTC-4, Dennis Lee Bieber wrote: > > On Sun, 23 Jun 2019 14:25:53 -0700 (PDT), > activewh...@gmail.com declaimed the > following: > > >It looks bad, but I want to be sure. Is there any way I can access the > data > >files on the eMMC? And to avoid rebuilding the entire BBB setup? Such as > >install U-Boot? Or is all BBB data lost? > > If you knew what the partition table had been, it might be > possible to > reflash the first part of the card restoring a partition table. BUT if the > data partition starts anywhere in the 100MB region, you've lost any data > blocks that had been stored there... And likely will spend hours in fsck > rebuilding whatever is still good, followed by copying everything off and > then reflashing the eMMC with a complete system which I believe will > restore a modern u-boot too (if it didn't, there'd be no way to update old > BBBs from kernel device tree loading to u-boot device tree loading). > > > > -- > Wulfraed Dennis Lee Bieber AF6VN > wlf...@ix.netcom.com > http://wlfraed.microdiversity.freeddns.org/ > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/179cadaf-f7bb-4611-893b-76e7ec64c81d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
