menu
Status #Pine64X
[Welcome to the Pine64 IRC channel. Discussion regarding the Pine A64 (LTS/SOPine), H64 and Pinebook goes here. To discuss the Rock64 or RockPro64 development boards join #Rock64. For off topic discussion join #OffTopic More infomration about the channel available here: https://forum.pine64.org/showthread.p]
[11:25] == idanskira [52508218@pine64-64B3C906.onlinehome-server.info] has joined #Pine64
[11:25] <idanskira> i really dont know but now i have on the sd card, debian os, opencv and a lot of files i want to re use
[11:27] <@pfeerick> if you find the cause of the problem first, we can work around it, and then you can go back to your project. I'd suggest get a empty microSD, install the stretch-mate image on it, do sudo apt update && sudo apt upgrade, reboot, and repeat update/upgrade until no more updates, and then reboot again. If it works fine, it _may_ not be update related.
[11:30] <idanskira> ok i'll try this... thanks
[11:31] <idanskira> you mean that maybe upgrade and update command will fix this problem?
[11:32] <@pfeerick> it will hopefully identify if it's a kernel update that is the problem, or if there is something else going on. Once you do get it 'up to date' I'd still turn updates off, so that a future update doesn't much things up (until you are ready to update).
[11:32] == nOOb [nOOb@81B46727.BB795E4D.42490761.IP] has quit [Ping timeout: 180 seconds]
[11:35] <idanskira> what is the command for turn of the updating?
[11:35] <@pfeerick> Otherwise, you will need to look at the opencv stuff, and any other changes being made to the system. If it is file system corruption, you'll need to check the microSD card for issues, and then consider how much is being written to disk. You may want to mount the root filesystem read-only, and have data written to a USB stick instead. Hard to say until the actual problem is identified
[11:36] == gameprograma [akinwale@DEE55B0.846C2866.35FBC769.IP] has joined #Pine64
[11:38] <@pfeerick> since you're on mate (desktop environment), you can do it through something like System -> Administration -> Software Sources -> change the automatically check for updates to never
[11:38] <@pfeerick> I don't have mate in front of me just this minute, so it's mostly guesswork ;)
[11:39] <idanskira> thanks a lot
[11:40] <@pfeerick> No problem... just hope you manage to get it how you want it... it's frustrating when you get it close and then something stuffs it all up for you... :(
[11:41] == gameprograma [akinwale@DEE55B0.846C2866.35FBC769.IP] has quit [Ping timeout: 180 seconds]
[11:43] <idanskira> yes exactly, after i installed open cv (6 hours) and more softwares and stuff it collapse
[11:43] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has joined #Pine64
[11:47] == nOOb [nOOb@pine64-5F9FCA2C.hsd1.mi.comcast.net] has joined #Pine64
[11:48] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has quit [Read error]
[12:09] == Lukasz [Lukasz@pine64-24DAB6DA.dynamic.gprs.plus.pl] has joined #Pine64
[12:13] == tkaiser [53abb9ba@pine64-64B3C906.onlinehome-server.info] has quit [Ping timeout: 180 seconds]
[12:22] == Erol [zmajcek@pine64-4DDB20FC.dynamic.telemach.ba] has quit [Ping timeout: 180 seconds]
[12:28] <ryan> Hey guys, does anyone know if the RockPro64 will have mainline support or if it will be BSP to start with?
[12:29] <Lukasz> ryan, it already has mainline support
[12:30] <ryan> Awesome - I'm keen to get hold of one to make a armbian build
[12:31] <ryan> Are we able to pre-order now?
[12:32] <@pfeerick> Yup, pre-order started 12th June ;)
[12:32] <Lukasz> Yes
[12:32] <Lukasz> hi pfeerick :)
[12:33] <@pfeerick> Hey Lukasz :)
[12:33] <ryan> Awesome! I love the specs of this - it's a viable challenger to the snapdragon boards available :)
[12:34] <ryan> At a much nicer pric epoint
[12:34] <ryan> s/pric epoint/price point
[12:36] <Lukasz> yes, and the PCIe + other fast IO = endless possibilities
[12:36] <Lukasz> also, do join the Rock64 channel for more chat re RPro64
[12:37] <ryan> Yeah, I probably should - i have a rock64 too :)
[12:37] <@pfeerick> It's corrections like that that ^^ that makes me think I should put Debbie online... people seemed to like her helping them correct typos!  xD
[12:37] <@pfeerick> * online again...
[12:37] <Lukasz> do :)
[12:38] <ryan> 1 x A64, 1 x Rock64 and 2* SoPine + Baseboard
[12:38] <ryan> Not a bad little collection
[12:38] <ryan> Best not mention the odroid and up! collection xD
[12:38] <@pfeerick> lol... and it was certainly interesting when she mis-spoke due to a wildcard recipe gone wrong... pine64-server will be back online soon once she'll run amock again ;)
[12:39] <@pfeerick> no, don't... we'll have to banish you to OffTopic :-P
[12:39] <ryan> Don't do that I need to be here in case I need to pick brains whilst writing my mainline mipi-dsi driver for the A64 :D
[12:40] <@pfeerick> lol... don't worry... no danger of that happening... unless you start talking about the RPi collection :P Yeah, I have to say I really do like the rock64... and the sopines are nice.
[12:41] <ryan> Ugh RPi actually suck comparatively.
[12:41] <@pfeerick> Even nicer will be the clusterboard once PXE boot via SPI flash works :-/
[12:41] <ryan> It annoys me that they keep the mipi interface data proprietary
[12:42] <ryan> PXE boot sounds like fun
[12:42] <@pfeerick> Agreed! Not a patch on the rock64 performance wise. And whaaaa? I thought they made sure everything was open sourced, blah blah blah... shame on them!
[12:44] <@pfeerick> Yeah... Seven sopines on a single baseboard, individual NICs, onboard network switch, single power connection... They can all boot fine via their SD cards, but the first one has a eMMC slot and I want to either PXE boot them from the first sopine, or use a spare pine64 as a master for the lot... but PXE on the clusterboard doesn't co-operate, but I do think it does work on the baseboard - don't have one so can't check myself.
[12:45] <ryan> It might be due to contention
[12:45] <ryan> u-boot doesn't handle errors overly well
[12:45] <ryan> Maybe add a random delay to each board before trying to PXE boot
[12:47] <@pfeerick> I think uboot either either doesn't pick up the NICs or tx/rx settings are stuffed. Something seems different enough to send uboot over the edge... and yes... a fly fart is all that is needed to skittle uboot! :O
[12:49] <ryan> pfeerick, if I have one I would take a look.. 3 years u-boot experience should solve it but I've overspent my budget so it won't be this month aha
[12:49] <ryan> s/have/had
[12:51] <@pfeerick> lol... well, you're no help then! :-P Yeah, that would probably do the trick... I'm sure some guys got it working with some mainline version of uboot... but there was something else not quite working and we never quite got there...
[12:53] <ryan> You come to love and hate u-boot all at the same time, eventually
[12:53] <ryan> Mainline u-boot is much better now though
[12:53] <ryan> Compared to the releases from 2 to 3 years ago
[12:54] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has joined #Pine64
[12:55] <@pfeerick> well, until recently, it just kept out of the way for me and I was completely oblivious to it... so the guys working on it must have gotten something wrong. Serves me right for getting more 'bleeding edge' boards...
[12:56] <@pfeerick> s/wrong/right
[13:00] == nOOb [nOOb@pine64-5F9FCA2C.hsd1.mi.comcast.net] has quit [Ping timeout: 180 seconds]
[13:06] <ryan> Nothing wrong with bleeding edge.. just don't put bleeding edge into a consumer product xD
[13:07] <ryan> Or there may be blood in the water...
[13:07] <ryan> #tumbleweed
[13:09] <@pfeerick> xD Or literal blood in my case... like the bloody CPU cooler I put in my desktop the other day... it drew blood, the nasty thing... those fins were *sharp* :-O
[13:13] <ryan> xD xD... all our designs are fanless so I just have tonnes of thermalpaste and cooling tubes xD
[13:13] == jaimehrubiks [jaime@EE79A28E.11E8B94E.1D1A5CD0.IP] has quit [Read error]
[13:13] == jaimehrubiks [jaime@EE79A28E.11E8B94E.1D1A5CD0.IP] has joined #Pine64
[13:14] == nOOb [nOOb@5B910F3F.BB795E4D.42490761.IP] has joined #Pine64
[13:22] == enki [enki@pine64-2F347E8C.adsl.eunet.rs] has quit [Ping timeout: 180 seconds]
[13:23] == enki [enki@pine64-2F347E8C.adsl.eunet.rs] has joined #Pine64
[13:31] == RockyBoulder [pi@pine64-46FD3C38.hsi13.unitymediagroup.de] has joined #Pine64
[14:19] == snuffy-home [kvirc@pine64-62FF3830.nbn.mel.aussiebb.net] has quit [Ping timeout: 180 seconds]
[14:19] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has quit [Ping timeout: 180 seconds]
[14:20] == snuffy-home [kvirc@pine64-62FF3830.nbn.mel.aussiebb.net] has joined #Pine64
[14:21] == gameprograma [akinwale@965FEC4D.A5EC86AC.D07B831E.IP] has joined #Pine64
[14:26] == gameprograma [akinwale@965FEC4D.A5EC86AC.D07B831E.IP] has quit [Ping timeout: 180 seconds]
[14:33] == gameprograma [akinwale@965FEC4D.A5EC86AC.D07B831E.IP] has joined #Pine64
[14:34] == pfeerick [pfeerick@pine64-EBF82327.static.exetel.com.au] has quit [Quit: Running away terribly fast...]
[15:08] == tomboy64 [Dingbat@1A884A05.C7592105.C8F08D92.IP] has quit [Ping timeout: 180 seconds]
[15:16] == tomboy64 [Dingbat@1A884A05.C7592105.C8F08D92.IP] has joined #Pine64
[15:19] == tomboy64 [Dingbat@1A884A05.C7592105.C8F08D92.IP] has quit [Ping timeout: 180 seconds]
[15:21] == tomboy64 [Dingbat@1A884A05.C7592105.C8F08D92.IP] has joined #Pine64
[15:35] == viku [d90c31b6@pine64-64B3C906.onlinehome-server.info] has joined #Pine64
[15:35] <%InfoBotV2> Welcome viku, it looks like you're new here!
[15:35] <%InfoBotV2> Make yourself at home, and feel free to ask any questions you have and join in with our random discussions!
[15:35] <%InfoBotV2> This channel is recorded, you may find the answer to your question at our searchable archive http://irc.pine64.uk
[15:35] <%InfoBotV2> For sales and shipping enquiries please email: support@pine64.org or submit a ticket at http://support.pine64.org
[15:45] == viku [d90c31b6@pine64-64B3C906.onlinehome-server.info] has quit [Quit: Page closed]
[15:55] == gameprograma [akinwale@965FEC4D.A5EC86AC.D07B831E.IP] has quit [Ping timeout: 180 seconds]
[15:57] <idanskira> sudo dmesg | grep sdc6 [173067.321896]  sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 [173067.704273] FAT-fs (sdc6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [173260.064229]  sdc: sdc1 sdc2 sdc3 sdc4 sdc5 sdc6 sdc7 [173261.391034] FAT-fs (sdc6): error, fat_get_cluster: invalid cluster chain (i_pos 6425) [173261.391037] FAT-fs (sdc6): Filesystem has been set read-only [173261.391041] FAT-fs (sdc6): error, fat_get_cluster: invalid cluste
[15:57] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has joined #Pine64
[15:58] <Lukasz> idanskira ?
[15:58] <idanskira> sorry, by mistake
[15:59] <idanskira> when i write sudo dmesg | grep sdc6 it shown the above errors
[15:59] <Lukasz> :)
[16:00] == Lukasz [Lukasz@pine64-24DAB6DA.dynamic.gprs.plus.pl]
[16:00] ==  realname : realname
[16:00] ==  channels : #Rock64 #Pine64
[16:00] ==  server   : irc.pine64.xyz [Pine64 Irc Server]
[16:00] == End of WHOIS
[16:00] <idanskira> does anyone have idea? i'm about to lose my mind
[16:01] <idanskira> i shut down the r64 and now it wont come up again.
[16:04] <r3boot> idanskira: did you try to run fsck.vfat /dev/sdc ?
[16:05] <idanskira> yes
[16:05] <r3boot> and still getting these errors?
[16:05] <idanskira> fsck.fat 3.0.28 (2015-05-16) 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. 1) Remove dirty bit 2) No action ?
[16:05] <idanskira> tat what shown
[16:06] <r3boot> ah, okay, so that's fsck asking you what it should do
[16:06] <idanskira> ok so what to choose 1 or 2?
[16:07] <r3boot> the 'dirty bit' tells the OS if the filesystem is mounted and/or it has been written to. In the case of a crash, that bit does not get cleared automagically, and during boot, mount will check the dirty bit. If it's set, it will assume an unsafe shutdown and give you the error above (but the fat fs looks corrupt tho)
[16:07] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has quit [Read error]
[16:07] <r3boot> if you are sure that the fs is not mounted (mount|grep sdc), you can safely remove the dirty bit and run fsck (which you will need to do to hopefully recover the FS)
[16:07] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has joined #Pine64
[16:08] <r3boot> Was this caused by an unclean shutdown btw? (or could you be facing the possibility that the flash is corrupted?)
[16:08] <idanskira>  mount|grep sdc /dev/sdc6 on /media/idanskira/boot1 type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2) /dev/sdc7 on /media/idanskira/linux-root1 type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2)
[16:08] <r3boot> okay, unmount that one first before fsck'in
[16:08] <ryan> okay you need to "umount /dev/sdc"
[16:08] <idanskira> i shut it down properly
[16:09] <ryan> Maybe bad flash r3boot..
[16:09] <ryan> idanskira have you made any dtb changes at all?
[16:09] <idanskira> it says : umount: /dev/sdc: not mounted
[16:09] <r3boot> s/sdc/sdc6/
[16:09] <ryan> and sdc7
[16:09] <r3boot> all of them iig
[16:09] <r3boot> mount | grep sdc should not return anything
[16:10] <r3boot> once you're there, you can run fsck
[16:10] <ryan> or you could plug into a reader and fix from another system
[16:10] <ryan> which imho is easier
[16:10] <idanskira> now im with reader on linux computer
[16:11] <r3boot> to each his own ofc. Basic skillset in filesystem recovery isnt that different from system to system
[16:11] <ryan> okay idanskira do this:
[16:11] <ryan> umount /dev/sdc6
[16:11] <r3boot> And personally, I'd only switch to a different reader if I'd suspect the reader to be broken
[16:11] <idanskira> what is the fsck command?
[16:11] <ryan> umount /dev/sdc7
[16:11] <evilbunny> ryan: sudo :)
[16:11] <r3boot> idanskira: fsck == FileSystem ChecK
[16:11] <ryan> I assumed he was root already
[16:11] <idanskira> it says: umount: /dev/sdc6: not mounted
[16:12] <r3boot> but does sdc6 still show up in mount | grep sdc ?
[16:12] <ryan> whats output of mount | grep sdc
[16:12] <idanskira> no i ment what command should ill write to fsck?
[16:12] <r3boot> idanskira: you first need to verify that you have not mounted any filesystems which are on sdc
[16:12] <r3boot> eg, mount | grep sdc
[16:13] <idanskira> mount | grep sdc dont show anything
[16:13] <r3boot> that'll return a bunch of sdc<number> devices
[16:13] <r3boot> okay, then it's unmounted :)
[16:13] <ryan> fsck.vfat /dev/sdc -a
[16:13] <ryan> fsck
[16:13] <idanskira> fsck.fat 3.0.28 (2015-05-16) Logical sector size is zero.
[16:13] <ryan> gotta love it
[16:13] <evilbunny> won't that screw up the device
[16:13] <r3boot> idanskira: for each partition on the device, you will need to run fsck
[16:13] <r3boot> eg, check the partitions with fdisk -l
[16:14] <r3boot> That'll return a bunch of sdc<number> devices
[16:14] <r3boot> for each device you find like that, do this:
[16:14] <idanskira> sudo fsck.vfat /dev/sdc6 -a fsck.fat 3.0.28 (2015-05-16) 0x25: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.  Automatically removing dirty bit. Performing changes. /dev/sdc6: 6 files, 10410/51091 clusters
[16:14] <r3boot> fsck.vfat /dev/sdc<number>
[16:14] <r3boot> fix any issues, remove the dirty bit, and you should be fine
[16:15] <ryan> idanskira thats sdc6 sorted
[16:15] <idanskira> yes, do the same to all other partitions? or other command?
[16:16] <ryan> show us output of fsck -l
[16:16] <ryan> and we can give you full commands
[16:16] <idanskira> sudo fsck -l fsck from util-linux 2.27.1 e2fsck 1.42.13 (17-May-2015) /dev/sda4 is mounted. e2fsck: Cannot continue, aborting.
[16:16] <r3boot> ~ Teach a man how to fish ;)
[16:16] <idanskira> hahaha
[16:16] <ryan> fsck -l /dev/sdc
[16:17] <r3boot> no, seriously. What you're trying to do idanskira, is basic UNIX skills
[16:17] <r3boot> so either we can spoonfeed you into what you need to do, or you/we take the time to learn about whats going on under the hood
[16:18] <r3boot> In this case, you'll need to learn about partitions, and how you can use them together with UNIX (linux, in this case)
[16:19] <idanskira> i'm with this issue for two weeks and until now no one solved this problm
[16:19] <ryan> idanskira, after we have fixed this
[16:19] <ryan> we will find you some reading
[16:19] <idanskira> sudo fsck -l /dev/sdc fsck from util-linux 2.27.1 e2fsck 1.42.13 (17-May-2015) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdc  The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem.  If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the s
[16:19] <ryan> so you can help yourself better next time
[16:20] <idanskira> thanks
[16:20] <r3boot> sdc is the underlying disk onto which you create partitions
[16:20] <idanskira> ok
[16:20] <r3boot> unless you have a FS the size of the underlying disk (which rarely happens), you will have partitions on there, which implies that you will almost always need a number behind /dev/sdc
[16:21] <r3boot> sdc == full disk; sdc1 == first partiton on disk, sdc2 == 2nd partition on disk, etcetc
[16:21] <idanskira> yes, i have 7 partitons, 1 to 5 is empty
[16:21] <ryan> sorry i typed wrong command
[16:21] <ryan> sudo fdisk -l /dev/sdc
[16:22] <idanskira> partition 6 is boot and 7 is linux-root
[16:22] <ryan> need that output :)
[16:22] <idanskira> sudo fdisk -l /dev/sdc GPT PMBR size mismatch (31116287 != 124735487) will be corrected by w(rite). Disk /dev/sdc: 59.5 GiB, 63864569856 bytes, 124735488 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: gpt Disk identifier: 1C7D4C86-35A6-4E6A-B3E3-2A6BEB44FDD0  Device      Start      End  Sectors  Size Type /dev/sdc1      64     8063     8000  3.9M Li
[16:22] <ryan> and we can check each fs on it
[16:22] <r3boot> Also, there are quite some filesystems for linux; ext4, xfs and vfat are common ones. Each filesystem has it's own fsck tool, usually named fsck.<name of the filesystem>. There is a convenience wrapper around that called 'fsck', which determines the filesystem on a partition, and it will call the correct fsck.<name> tool
[16:23] <ryan> sudo parted -l
[16:23] <r3boot> So, if you *know* that something is vfat (for instance), you can directly call fsck.vfat. But if you're not 100% sure, call fsck itself, and it should figure things out by itself
[16:23] <idanskira> sudo parted -l Model: ATA HFS256G39TND-N21 (scsi) Disk /dev/sda: 256GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags:   Number  Start   End    Size    File system     Name  Flags  1      1049kB  538MB  537MB   ntfs                  msftdata  2      538MB   539MB  1049kB                        bios_grub  4      539MB   248GB  247GB   ext4  3      248GB   256GB  8457MB  linux-swap(v1)   Warning: Not all of the space available to /dev/sdc a
[16:24] <idanskira> Warning: Not all of the space available to /dev/sdc appears to be used, you can fix the GPT to use all of the space (an extra 93619200 blocks) or continue with the current setting?  Fix/Ignore?
[16:24] <ryan> fix
[16:24] <ryan> it should sort out the PMBR
[16:25] <ryan> Does seem like a bad flash however
[16:25] <idanskira> Model: USB 2.0 SD/MMC Reader (scsi) Disk /dev/sdc: 63.9GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags:
[16:25] <r3boot> eh, it's a GPT disk, no MBR involved
[16:25] <idanskira>  Number  Start   End     Size    File system  Name       Flags  1      32.8kB  4129kB  4096kB               loader1  2      4129kB  4194kB  65.5kB               reserved1  3      4194kB  8389kB  4194kB               reserved2  4      8389kB  12.6MB  4194kB               loader2  5      12.6MB  16.8MB  4194kB               atf  6      16.8MB  134MB   117MB   fat16        boot       legacy_boot, msftdata  7      134MB   15.9GB  15.8GB  ext4         root
[16:26] <Lukasz> gentle prompt to use pastebin :)
[16:27] <ryan> r3boot, GPT and PMBR were mismatched
[16:27] <ryan> in other words the GPT headers were corrupt
[16:28] == Erol [zmajcek@pine64-8E6A9FBF.dynamic.telemach.ba] has joined #Pine64
[16:28] <idanskira> ok so what should i do?
[16:28] <ryan> Did you do fix?
[16:28] <ryan> Can you pastebin the output please
[16:28] <idanskira> yes
[16:28] <ryan> can't read it easily
[16:29] <idanskira> Number  Start   End     Size    File system  Name       Flags
[16:30] <ryan> https://pastebin.com/
[16:31] <idanskira> https://pastebin.com/x3zGYhCC
[16:32] <ryan> we need the end of line 7 please
[16:32] <ryan> Filesystem type
[16:34] <idanskira> https://pastebin.com/AxgaxetS
[16:34] <idanskira> ext4
[16:34] <idanskira> name root
[16:37] <ryan> ok so "sudo fsck /dev/sdc7 -f"
[16:37] <ryan> So what we are doing here is allowing fsck to detect the filesystem
[16:38] <idanskira> linux-root: 173041/966656 files (0.2% non-contiguous), 1489492/3856763 blocks
[16:38] <ryan> and saying -f is forcing a full check in case it reports clean but isn't
[16:38] <idanskira> before this line it was pass1 etc.
[16:38] <ryan> okay now you can plug back in to your device - taking care not to touch the flash chip
[16:38] <ryan> you should be earther when handing this
[16:38] <ryan> due to ESD
[16:39] == valentind [valentind@pine64-AC573953.customer.lyse.net] has quit [Ping timeout: 180 seconds]
[16:39] <ryan> but if you dont have ESD protection equipment (armban with ground plug)
[16:39] == valentind [valentind@pine64-AC573953.customer.lyse.net] has joined #Pine64
[16:39] <ryan> armband*
[16:39] <ryan> then just hold the edges of it and dont touch any metal
[16:39] <idanskira> ok
[16:39] <ryan> ESD is electrostatic discharge
[16:39] <ryan> builds up walking around with shoes on carpet etc
[16:40] <ryan> klike rubbing a baloon on your head or jumper
[16:40] <ryan> like* balloon*
[16:40] <ryan> and discharges through the device causing issues such as data corruption or completely killing it
[16:40] <ryan> (causes stuck transistor gates etc)
[16:41] <idanskira> again nothing happend... now it says tty_port_close_start: tty->count =1 port count = 2.
[16:41] <ryan> have you not reinstalled this?
[16:42] == gameprograma [akinwale@C89646E0.C7C95A21.30375EAE.IP] has quit [Ping timeout: 180 seconds]
[16:42] <ryan> I seem to remember you saying this 2 days ago
[16:42] <idanskira> reinstalled wha
[16:42] <idanskira> what
[16:42] <ryan> Did you not flash a new image?
[16:43] <ryan> you was going to copy the files you wanted from /dev/sdc7
[16:43] <ryan> and flash a new image with etcher
[16:43] <ryan> or similar
[16:43] <idanskira> you mean now? i need to create an image?
[16:43] <idanskira> after we run all the commands before?
[16:44] <ryan> we tried to rescue it
[16:44] <ryan> but if you've got a corrupted flash
[16:44] <ryan> we can't rescue the loader
[16:44] <ryan> (easily)
[16:45] <ryan> so it's easier to flash a new image after backing up files you need from /dev/sdc7
[16:45] <ryan> Have you been handling the flash by hand before it died?
[16:46] <idanskira> ok so now the sd card is on the reader, you want me to create an image with dd command?
[16:46] <ryan> not create an image
[16:46] <ryan> we need to write a new image to the card
[16:47] <ryan> which board do you have?
[16:48] <ryan> also idanskira what brand of SD is this?
[16:48] <idanskira> sandisk
[16:48] <ryan> ok. which board do you have?
[16:48] <idanskira> asus computer
[16:49] == cnxsoft [Thunderbir@pine64-BADE01D2.pool-118-172.dynamic.totbb.net] has quit [Quit: cnxsoft]
[16:49] <ryan> pine64 board..?
[16:49] <idanskira> im checking
[16:52] <idanskira> you want the motherboard model?
[16:53] <ryan> What are you trying to boot with the SD card?
[16:53] <idanskira> debian os
[16:54] <ryan> Is it a PineA64, PineA64+, sopine, rock64?
[16:54] <idanskira> rock 64
[16:55] <ryan> okay do you have etcher installed
[16:55] <ryan> download http://files.pine64.org/os/ROCK64/debian/stretch-mate-rock64-0.5.15-136-20171222-arm64.img.xz
[16:55] <idanskira> yes
[16:55] <ryan> and use etcher to put it onto the SD card
[16:56] <ryan> default username and password is rock64
[16:56] <idanskira> so i need first to format the sd card no?
[16:56] <ryan> not necessary
[16:56] <idanskira> ok
[16:56] <ryan> its good practice
[16:56] <ryan> but its not that important
[16:57] <ryan> because we are essentially formatiingit using etcher
[16:57] <idanskira> ho ok so after i burn the image on the sd card what next?
[16:57] <ryan> put it in your rock64
[16:57] <ryan> power up and wait
[16:57] <ryan> It should turn on and resize he partition
[16:57] <idanskira> ok
[16:58] <idanskira> thanks a lot
@fire219
@longsleep
%CuddlyTeddy
%InfoBotV2
%Prophesi
[ade]
_CRImier_
_william_
a1
adeel
anarsoul
andoma
ayaka
ayufan
ayufan4
barnitopine
BaronKrause
bibor
blark
bshah
caveat
CRImier
cstrahan
cwesterfield-away
cynosure
DarkUranium
det3
dex1983
DigiDaz
dol-sen
draget
enki
Erol
evilbunny
fullstop
fysa
gman
gnarface
h31
harms
idanskira
jaimehrubiks
jbr
jeremail
KC2NDA_
kjstouffer
kremlin
krux
Kwiboo
kybr
lanodan
lopsided
Lukasz
macros
malfunction_gk
manu
maya
meklu
mhoney
mnrmnaugh
MoeIcenowy
msimpson
NiteHawk
njalk
nOOb
nuclearsandwich
old_dev_guy
Omegamoon
Pc-Talk
Pepe
Perdu
phessler
phinxy
pinebreaker_
PL
pumphaus
r3boot
Ransu
ric96
RockyBoulder
rogerthn
Roguetek_
romangg
RonWhoCares
rookieone
ryan
scuzz
shadeslayer
Siltaar
snuffy
snuffy-home
spbecker
spm_draget
subzero79
sup
techy2
tekrantz
tobias
tomboy64
underdog
valentind
yang
yann
z83iiabnormal
zombielinux