12-29-2021, 07:46 AM
(This post was last modified: 12-29-2021, 08:38 AM by moodroid.)
Hi,
No probs. I'm no Linux expert either, but I think you would just need to enter those commands at the command line. So, open a shell / command / bash (or whatever it's called on your distro) window. Then after connecting jumpdrive, enter:
tail -f /var/log/syslog
And then:
tail -f /var/log/messages
Good luck, and hope there's a solution.
edit: on a couple of similar threads, people are saying that the output from the following command would be useful too:
lsblk
12-29-2021, 10:36 AM
(This post was last modified: 12-29-2021, 10:38 AM by Zebulon Walton.)
(12-29-2021, 06:21 AM)thorensjubilee Wrote: Thanks for your message. How do I go about that? I've had two strokes and my memory is terrible.
Sorry to hear that, hope things improve. (Have gone through similar problems with family members but in time they did well.)
What you want to do is boot up your PC on your Ubuntu flash drive. Then, open up a terminal to get to the command line and enter the following command:
sudo tail -f /var/log/syslog
This will give you a "live" readout of the system log file as messages are added to it. Then plug in your Pinephone running Jumpdrive and see what messages related to USB devices (if any) coincide with doing that. Normally you would see something like this - these are the messages generated on my Ubuntu system when plugging in a flash drive:
Code: Dec 29 11:23:03 ubuntu kernel: [ 4603.076243] usb 2-1.8: new high-speed USB device number 5 using ehci-pci
Dec 29 11:23:03 ubuntu kernel: [ 4603.172806] usb 2-1.8: New USB device found, idVendor=ffff, idProduct=5678
Dec 29 11:23:03 ubuntu kernel: [ 4603.172811] usb 2-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 29 11:23:03 ubuntu kernel: [ 4603.172813] usb 2-1.8: Product: Disk 2.0
Dec 29 11:23:03 ubuntu kernel: [ 4603.172815] usb 2-1.8: Manufacturer: USB
Dec 29 11:23:03 ubuntu kernel: [ 4603.172817] usb 2-1.8: SerialNumber: KT2020000000000038
Dec 29 11:23:03 ubuntu kernel: [ 4603.173200] usb-storage 2-1.8:1.0: USB Mass Storage device detected
Dec 29 11:23:03 ubuntu kernel: [ 4603.173457] scsi host16: usb-storage 2-1.8:1.0
Dec 29 11:23:03 ubuntu mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8"
Dec 29 11:23:03 ubuntu mtp-probe: bus: 2, device: 5 was not an MTP device
Dec 29 11:23:04 ubuntu kernel: [ 4604.173507] scsi 16:0:0:0: Direct-Access VendorCo ProductCode 2.00 PQ: 0 ANSI: 4
Dec 29 11:23:04 ubuntu kernel: [ 4604.174020] sd 16:0:0:0: Attached scsi generic sg16 type 0
Dec 29 11:23:04 ubuntu kernel: [ 4604.175986] sd 16:0:0:0: [sdn] 61440000 512-byte logical blocks: (31.5 GB/29.3 GiB)
Dec 29 11:23:04 ubuntu kernel: [ 4604.176601] sd 16:0:0:0: [sdn] Write Protect is off
Dec 29 11:23:04 ubuntu kernel: [ 4604.176606] sd 16:0:0:0: [sdn] Mode Sense: 03 00 00 00
Dec 29 11:23:04 ubuntu kernel: [ 4604.177269] sd 16:0:0:0: [sdn] No Caching mode page found
Dec 29 11:23:04 ubuntu kernel: [ 4604.177273] sd 16:0:0:0: [sdn] Assuming drive cache: write through
Dec 29 11:23:04 ubuntu kernel: [ 4604.182484] sdn: sdn1
Dec 29 11:23:04 ubuntu kernel: [ 4604.185106] sd 16:0:0:0: [sdn] Attached SCSI removable disk
Dec 29 11:23:04 ubuntu udisksd[2610]: Mounted /dev/sdn1 at /media/balpert/EC80-5622 on behalf of uid 1000
I know at first glance it looks like intimidating gobbledy-gook, but what's happening is the USB device is detected, identified as mass storage, a device node assigned (in this case /dev/sdn with partition /dev/sdn1), and it's mounted. If Jumpdrive is working correctly you would see something similar. Since it is not working for you it's possible you may see something in the log that can help identify the problem. (If you see nothing at all when you plug it in you know that Jumpdrive is not working at all.)
Another possibility is that there is something wrong with your Jumpdrive SD card and you could try another, or that your USB cable is bad. (Even if it works for charging it may not work for data.)
Hello,
I got the following message:
darley@darley-All-Series:~$ sudo tail -f /var/log/syslog
[sudo] password for darley:
Dec 29 17:53:00 darley-All-Series systemd[1]: systemd-timedated.service: Succeeded.
Dec 29 17:53:03 darley-All-Series systemd[1910]: Started Application launched by gsd-media-keys.
Dec 29 17:53:03 darley-All-Series dbus-daemon[1921]: [session uid=1000 pid=1921] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.91' (uid=1000 pid=3606 comm="/usr/bin/gnome-terminal.real " label="unconfined")
Dec 29 17:53:03 darley-All-Series systemd[1910]: Starting GNOME Terminal Server...
Dec 29 17:53:03 darley-All-Series dbus-daemon[1921]: [session uid=1000 pid=1921] Successfully activated service 'org.gnome.Terminal'
Dec 29 17:53:03 darley-All-Series systemd[1910]: Started GNOME Terminal Server.
Dec 29 17:53:03 darley-All-Series systemd[1910]: Started VTE child process 3617 launched by gnome-terminal-server process 3609.
Dec 29 17:53:03 darley-All-Series systemd[1910]: gnome-launched-x-terminal-emulator-3603.scope: Succeeded.
Dec 29 17:53:09 darley-All-Series geoclue[1764]: Service not used for 60 seconds. Shutting down..
Dec 29 17:53:09 darley-All-Series systemd[1]: geoclue.service: Succeeded.
Dec 29 17:53:23 darley-All-Series systemd[1910]: Started snap.canonical-livepatch.canonical-livepatch.5ec6f9ce-a33b-45c7-a7b7-e06ee1568284.scope.
Dec 29 17:53:23 darley-All-Series systemd[1910]: snap.canonical-livepatch.canonical-livepatch.5ec6f9ce-a33b-45c7-a7b7-e06ee1568284.scope: Succeeded.
Dec 29 17:53:23 darley-All-Series systemd[1910]: Started snap.canonical-livepatch.canonical-livepatch.f26a2dbb-a34f-43c0-985e-a63e5b678266.scope.
Dec 29 17:53:23 darley-All-Series systemd[1910]: snap.canonical-livepatch.canonical-livepatch.f26a2dbb-a34f-43c0-985e-a63e5b678266.scope: Succeeded.
Dec 29 17:53:23 darley-All-Series systemd[1910]: Started snap.canonical-livepatch.canonical-livepatch.e63fcb2c-aede-40d1-ba36-a3adfd6c1831.scope.
Dec 29 17:53:23 darley-All-Series systemd[1910]: snap.canonical-livepatch.canonical-livepatch.e63fcb2c-aede-40d1-ba36-a3adfd6c1831.scope: Succeeded.
Dec 29 17:53:23 darley-All-Series systemd[1910]: Started snap.canonical-livepatch.canonical-livepatch.7d778df3-12fd-4e4e-bde9-54d1b2d36a77.scope.
Dec 29 17:53:23 darley-All-Series systemd[1910]: snap.canonical-livepatch.canonical-livepatch.7d778df3-12fd-4e4e-bde9-54d1b2d36a77.scope: Succeeded.
Dec 29 17:53:59 darley-All-Series kernel: [ 124.461550] usb 3-7: new high-speed USB device number 6 using xhci_hcd
Dec 29 17:53:59 darley-All-Series kernel: [ 124.589534] usb 3-7: device descriptor read/64, error -71
Dec 29 17:54:00 darley-All-Series kernel: [ 124.825571] usb 3-7: device descriptor read/64, error -71
So the last two lines are the Jumpdrive with EMMC. What do they say?
Chris
There's an error communicating over the USB protocol and the device descriptor could not be obtained. (Well, we basically knew that but now we know the PC is at least seeing Jumpdrive but cannot communicate with it.) I tried searching for this error but could not find -71; -110 and -32 seem to be most common, but they all point to USB communication problems. Sometimes this is due to the port not delivering enough power but since the Pinephone is powered by its battery that should not be the case here.
Make sure your USB cable is inserted all the way into the phone. If you have the phone in a case remove that, with some cables the case can prevent the connector from fully seating. I'd try another USB port if you have not already done so, preferably one on your computer's motherboard. (On a tower those would be in the back.) Also try another cable, making sure it's a data cable, not for power only. Finally I'd try another SD card flashed with a copy of the latest Jumpdrive.
12-30-2021, 04:09 AM
(This post was last modified: 12-30-2021, 04:11 AM by thorensjubilee.)
Hello Zebulon,
I tried again with the only USB C connector that I have! That' s the one that came with the phone and I tried connecting it to s different USB A socket on the computer. I did the code and I got this:
Dec 30 10:05:55 darley-All-Series PackageKit: daemon quit
Dec 30 10:05:56 darley-All-Series systemd[1]: packagekit.service: Succeeded.
Dec 30 10:06:07 darley-All-Series systemd[1]: systemd-timedated.service: Succeeded.
Dec 30 10:06:25 darley-All-Series systemd[1916]: Started Application launched by gsd-media-keys.
Dec 30 10:06:25 darley-All-Series dbus-daemon[1927]: [session uid=1000 pid=1927] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.100' (uid=1000 pid=4040 comm="/usr/bin/gnome-terminal.real " label="unconfined")
Dec 30 10:06:25 darley-All-Series systemd[1916]: Starting GNOME Terminal Server...
Dec 30 10:06:25 darley-All-Series dbus-daemon[1927]: [session uid=1000 pid=1927] Successfully activated service 'org.gnome.Terminal'
Dec 30 10:06:25 darley-All-Series systemd[1916]: Started GNOME Terminal Server.
Dec 30 10:06:26 darley-All-Series systemd[1916]: Started VTE child process 4051 launched by gnome-terminal-server process 4043.
Dec 30 10:06:26 darley-All-Series systemd[1916]: gnome-launched-x-terminal-emulator-4037.scope: Succeeded.
Dec 30 10:06:50 darley-All-Series kernel: [ 389.080673] usb 3-13: new high-speed USB device number 6 using xhci_hcd
I still can't flash to it!
Chris
12-30-2021, 10:26 AM
(This post was last modified: 12-30-2021, 10:32 AM by Zebulon Walton.)
The last line in your log shows detection of the device but it's not going past that. (As you saw in my example a lot more has to happen.)
I'd try reflashing the latest Jumpdrive to your SD card. Aside from that, the only other thing I can think of trying would be another USB-C cable. I've bought those cables for $1 at Dollar Tree if you have those stores in your area, and they work for data as well as power. In fact I just hooked up my phone using one of my Dollar Tree cables and Jumpdrive works fine with it. (Protective case must be removed from the phone to plug it in since the plug on the phone end is shorter than the one on the Pine64 cable.)
Below are the resulting system log entries which show what you should see when it's working properly, notice that early on when the USB device descriptor is read the product is identified as "Pinephone", the manufacturer as "Pine64", and SerialNumber as "Jumpdrive" on lines 4-6. Further down in the log the device is identifed as "JumpDriv e eMMC" and "JumpDriv e microSD", and is assigned device node /dev/sdo:
Code: Dec 30 11:13:44 ubuntu kernel: [ 6464.971803] usb 1-1.1.4: new high-speed USB device number 5 using ehci-pci
Dec 30 11:13:44 ubuntu kernel: [ 6465.064668] usb 1-1.1.4: New USB device found, idVendor=1209, idProduct=4201
Dec 30 11:13:44 ubuntu kernel: [ 6465.064673] usb 1-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 30 11:13:44 ubuntu kernel: [ 6465.064675] usb 1-1.1.4: Product: PinePhone
Dec 30 11:13:44 ubuntu kernel: [ 6465.064677] usb 1-1.1.4: Manufacturer: Pine64
Dec 30 11:13:44 ubuntu kernel: [ 6465.064679] usb 1-1.1.4: SerialNumber: Jumpdrive
Dec 30 11:13:44 ubuntu kernel: [ 6465.065949] usb-storage 1-1.1.4:1.2: USB Mass Storage device detected
Dec 30 11:13:44 ubuntu kernel: [ 6465.066061] scsi host16: usb-storage 1-1.1.4:1.2
Dec 30 11:13:44 ubuntu mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4"
Dec 30 11:13:44 ubuntu mtp-probe: bus: 1, device: 5 was not an MTP device
Dec 30 11:13:44 ubuntu kernel: [ 6465.624106] usbcore: registered new interface driver cdc_ether
Dec 30 11:13:44 ubuntu kernel: [ 6465.624936] cfg80211: World regulatory domain updated:
Dec 30 11:13:44 ubuntu kernel: [ 6465.624939] cfg80211: DFS Master region: unset
Dec 30 11:13:44 ubuntu kernel: [ 6465.624940] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624943] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624945] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624946] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624948] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624950] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624952] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624953] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
Dec 30 11:13:44 ubuntu kernel: [ 6465.624955] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
Dec 30 11:13:44 ubuntu kernel: [ 6465.627655] rndis_host 1-1.1.4:1.0 usb0: register 'rndis_host' at usb-0000:00:1a.0-1.1.4, RNDIS device, 3a:49:a7:01:78:1a
Dec 30 11:13:44 ubuntu NetworkManager[2175]: <warn> [1640880824.6845] device (usb0): failed to find device 5 'usb0' with udev
Dec 30 11:13:44 ubuntu NetworkManager[2175]: <info> [1640880824.6854] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Dec 30 11:13:44 ubuntu kernel: [ 6465.630287] usbcore: registered new interface driver rndis_host
Dec 30 11:13:44 ubuntu kernel: [ 6465.633511] usbcore: registered new interface driver rndis_wlan
Dec 30 11:13:44 ubuntu kernel: [ 6465.636375] rndis_host 1-1.1.4:1.0 enp0s26u1u1u4: renamed from usb0
Dec 30 11:13:44 ubuntu NetworkManager[2175]: <info> [1640880824.7086] device (usb0): interface index 5 renamed iface from 'usb0' to 'enp0s26u1u1u4'
Dec 30 11:13:44 ubuntu NetworkManager[2175]: <info> [1640880824.7137] devices added (path: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/net/enp0s26u1u1u4, iface: enp0s26u1u1u4)
Dec 30 11:13:44 ubuntu NetworkManager[2175]: <info> [1640880824.7137] device added (path: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/net/enp0s26u1u1u4, iface: enp0s26u1u1u4): no ifupdown configuration found.
Dec 30 11:13:45 ubuntu kernel: [ 6466.064369] scsi 16:0:0:0: Direct-Access JumpDriv e eMMC PQ: 0 ANSI: 2
Dec 30 11:13:45 ubuntu kernel: [ 6466.064829] scsi 16:0:0:1: Direct-Access JumpDriv e microSD PQ: 0 ANSI: 2
Dec 30 11:13:45 ubuntu kernel: [ 6466.065263] sd 16:0:0:0: Attached scsi generic sg16 type 0
Dec 30 11:13:45 ubuntu kernel: [ 6466.065477] sd 16:0:0:1: Attached scsi generic sg17 type 0
Dec 30 11:13:45 ubuntu kernel: [ 6466.068915] sd 16:0:0:1: [sdo] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
Dec 30 11:13:45 ubuntu kernel: [ 6466.069534] sd 16:0:0:1: [sdo] Write Protect is off
Dec 30 11:13:45 ubuntu kernel: [ 6466.069537] sd 16:0:0:1: [sdo] Mode Sense: 0f 00 00 00
Dec 30 11:13:45 ubuntu kernel: [ 6466.070160] sd 16:0:0:1: [sdo] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 30 11:13:45 ubuntu kernel: [ 6466.070541] sd 16:0:0:0: [sdn] 61071360 512-byte logical blocks: (31.3 GB/29.1 GiB)
Dec 30 11:13:45 ubuntu kernel: [ 6466.071539] sd 16:0:0:0: [sdn] Write Protect is off
Dec 30 11:13:45 ubuntu kernel: [ 6466.071543] sd 16:0:0:0: [sdn] Mode Sense: 0f 00 00 00
Dec 30 11:13:45 ubuntu kernel: [ 6466.072851] sd 16:0:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Dec 30 11:13:45 ubuntu kernel: [ 6466.084457] sdo: sdo1
Dec 30 11:13:45 ubuntu kernel: [ 6466.091174] sdn: sdn1 sdn3
Dec 30 11:13:45 ubuntu kernel: [ 6466.094788] sd 16:0:0:1: [sdo] Attached SCSI removable disk
Hello Zebulon,
I went out and bought a USB A to USB C cable premium product. I have done another test and the following is:
ec 30 17:09:01 darley-All-Series anacron[4525]: Anacron 2.3 started on 2021-12-30
Dec 30 17:09:01 darley-All-Series anacron[4525]: Normal exit (0 jobs run)
Dec 30 17:09:01 darley-All-Series systemd[1]: anacron.service: Succeeded.
Dec 30 17:09:52 darley-All-Series systemd[1935]: Started Application launched by gsd-media-keys.
Dec 30 17:09:52 darley-All-Series dbus-daemon[1946]: [session uid=1000 pid=1946] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.102' (uid=1000 pid=4534 comm="/usr/bin/gnome-terminal.real " label="unconfined")
Dec 30 17:09:52 darley-All-Series systemd[1935]: Starting GNOME Terminal Server...
Dec 30 17:09:52 darley-All-Series dbus-daemon[1946]: [session uid=1000 pid=1946] Successfully activated service 'org.gnome.Terminal'
Dec 30 17:09:52 darley-All-Series systemd[1935]: Started GNOME Terminal Server.
Dec 30 17:09:52 darley-All-Series systemd[1935]: Started VTE child process 4546 launched by gnome-terminal-server process 4538.
Dec 30 17:09:52 darley-All-Series systemd[1935]: gnome-launched-x-terminal-emulator-4531.scope: Succeeded.
Dec 30 17:10:30 darley-All-Series kernel: [ 313.995410] usb 3-13: new high-speed USB device number 7 using xhci_hcd
Dec 30 17:10:33 darley-All-Series dbus-daemon[1072]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.78' (uid=0 pid=1101 comm="/usr/lib/snapd/snapd " label="unconfined")
Dec 30 17:10:33 darley-All-Series systemd[1]: Starting Time & Date Service...
Dec 30 17:10:33 darley-All-Series dbus-daemon[1072]: [system] Successfully activated service 'org.freedesktop.timedate1'
Dec 30 17:10:33 darley-All-Series systemd[1]: Started Time & Date Service.
Dec 30 17:10:33 darley-All-Series snapd[1101]: storehelpers.go:710: cannot refresh: snap has no updates available: "bare", "canonical-livepatch", "chromium-ffmpeg", "core", "core18", "core20", "gnome-3-28-1804", "gnome-3-34-1804", "gnome-3-38-2004", "gtk-common-themes", "opera", "snap-store", "snapd", "vlc"
Dec 30 17:10:33 darley-All-Series snapd[1101]: autorefresh.go:536: auto-refresh: all snaps are up-to-date
Dec 30 17:10:46 darley-All-Series gnome-shell[1584]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
Dec 30 17:10:46 darley-All-Series gnome-shell[1584]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
Dec 30 17:11:00 darley-All-Series PackageKit: daemon quit
Dec 30 17:11:01 darley-All-Series systemd[1]: packagekit.service: Succeeded.
Dec 30 17:11:03 darley-All-Series systemd[1]: systemd-timedated.service: Succeeded.
Has the new cable succeeded? Or has it failed? I flashed the jumpdrive to the latest version. Nowhere is the pinephone named, nor is Pine64 named as the manufacturer.
What am I to do? Is the phone bricked?
Chris
Chris
It looks like the same issue, all I'm seeing in your log is the initial detection when you plug in the cable from the phone. (Line 11 in your listing. The other entries are unrelated.) However the USB device descriptor is not read in and no further action is taken. You can see in my last log file example what you should be seeing if all is working OK. In fact in mine you can also see the network part of Jumpdrive being set up in addition to the eMMC.
If your Pinephone is able to boot up on Jumpdrive it's not totally bricked. Have you tried flashing your SD card with the Pinephone factory test image to run diagnostics?
https://wiki.pine64.org/wiki/PinePhone_S...ry_Test_OS
If you flash your SD card with a full operating system (Mobian, etc.) does the phone boot up on that and work? (Maybe your eMMC is dead but the rest of the phone is working?)
Hello Zebulon,
Thanks for your message. No, I haven't tried flashing my SD card with the pinephone factory test image. I'll try it tomorrow. The phone doesn't boot up with anything. It's dead.
Chris
I've been working under the assumption here that the phone was at least booting up the Jumpdrive image from sd card (Jumpdrive logo appears on phone screen). If not that would 'splain why you're not getting any action via the USB connection. That doesn't happen until the Jumpdrive image is booted up.
If it's the case that even the Jumpdrive sd card is not booting the factory test image would likely not run either.
|
Pinephone is dead (sort of)
