maemo.org - Talk
Page 6 of 18 « First 45 6 7816 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)
-   -   2.1.1/Jämsänjoki EA (https://talk.maemo.org/showthread.php?t=99643)

deutch1976 2017-07-27 16:03
Re: 2.1.1/Jämsänjoki EA
 
Is it already possible, after a phone flash, to update directly to 2.1.1 or do we still have to update one by one? Thanks

Kabouik 2017-07-27 16:31
Re: 2.1.1/Jämsänjoki EA
 
Quote:
Originally Posted by ejjoman (Post 1531415)
Can you ping your computer from your recovery shell? Can you try to ping the IP of some public service, like the Google DNS (8.8.8.8)?
No, I get "permission denied" when trying to ping an IP, and unknown host when pinging a url. This is from chroot, but ping works better when ran out of chroot (just going into Recovery shell and using ping immediately without the mount points and the chroot), I mean I don't get permission issues, but there is still no internet access.

Here is an output of what I get when trying to follow the guide on TJC:

Code:
/ # mkdir /mnt/rootfs
 
/ # mount /dev/mapper/sailfish-root /mnt/rootfs
 
/ # chroot /mnt/rootfs
 
bash-3.2# mount /proc
 
bash-3.2# mount /sys
 
bash-3.2# mount /dev/pts
 
bash-3.2# echo "nameserver 8.8.8.8" >> /etc/resolv.conf
 
bash-3.2# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
10.42.66.64    *              255.255.255.248 U    0      0        0 rndis0
192.168.2.0    *              255.255.255.0  U    0      0        0 rndis0
 
bash-3.2# route add default gw 10.42.66.67
 
bash-3.2# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
default        10.42.66.67    0.0.0.0        UG    0      0        0 rndis0
10.42.66.64    *              255.255.255.248 U    0      0        0 rndis0
192.168.2.0    *              255.255.255.0  U    0      0        0 rndis0
 
bash-3.2# su
 
[root@(none) /]# ip -4 addr
3: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 10.42.66.66/29 brd 10.42.66.255 scope global rndis0
      valid_lft forever preferred_lft forever
    inet 192.168.2.15/24 brd 192.168.2.255 scope global rndis0:0
      valid_lft forever preferred_lft forever
 
[root@(none) /]# ip route
default via 10.42.66.67 dev rndis0
10.42.66.64/29 dev rndis0  proto kernel  scope link  src 10.42.66.66
192.168.2.0/24 dev rndis0  proto kernel  scope link  src 192.168.2.15
 
[root@(none) /]# tracepath -n 8.8.8.8
 1:  send failed
    Resume: pmtu 65535
 
[root@(none) /]# ping -c 5 google.com
ping: unknown host google.com

[root@(none) /]# exit
exit

bash-3.2# ifconfig
rndis0    Link encap:Ethernet  HWaddr B6:23:76:8C:DC:63 
          inet addr:10.42.66.66  Bcast:10.42.66.255  Mask:255.255.255.248
          inet6 addr: fe80::b423:76ff:fe8c:dc63/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1188 errors:0 dropped:0 overruns:0 frame:0
          TX packets:505 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:91017 (88.8 KiB)  TX bytes:60383 (58.9 KiB)

rndis0:0  Link encap:Ethernet  HWaddr B6:23:76:8C:DC:63 
          inet addr:192.168.2.15  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
The computer can ping the Jolla C at 10.42.66.66, and I have run this from it and it returned no error:
Code:
sudo sysctl net.ipv4.ip_forward=1
sudo iptables -t nat -A POSTROUTING -o wlp2s0 -j MASQUERADE
But somehow, something is still perventing it to share internet to the Jolla C, or the Jolla C to pick up.

[Edit] Finally reset to factory state, I love my original Jolla and I largely prefer it over my Jolla C for its form factor actually so it was nice to reuse it in the meantime. However, there is an Android application requiring 4.4.4 that I need to run, and I can't on the Jolla due to its older version of Aliendalvik. So fixing the Jolla C could not wait.

nieldk 2017-07-27 18:05
Re: 2.1.1/Jämsänjoki EA
 
Quote:
Originally Posted by Kabouik (Post 1531434)
No, I get "permission denied" when trying to ping an IP, and unknown host when pinging a url. This is from chroot, but ping works better when ran out of chroot (just going into Recovery shell and using ping immediately without the mount points and the chroot), I mean I don't get permission issues, but there is still no internet access.

Here is an output of what I get when trying to follow the guide on TJC:

Code:
/ # mkdir /mnt/rootfs
 
/ # mount /dev/mapper/sailfish-root /mnt/rootfs
 
/ # chroot /mnt/rootfs
 
bash-3.2# mount /proc
 
bash-3.2# mount /sys
 
bash-3.2# mount /dev/pts
 
bash-3.2# echo "nameserver 8.8.8.8" >> /etc/resolv.conf
 
bash-3.2# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
10.42.66.64    *              255.255.255.248 U    0      0        0 rndis0
192.168.2.0    *              255.255.255.0  U    0      0        0 rndis0
 
bash-3.2# route add default gw 10.42.66.67
 
bash-3.2# route
Kernel IP routing table
Destination    Gateway        Genmask        Flags Metric Ref    Use Iface
default        10.42.66.67    0.0.0.0        UG    0      0        0 rndis0
10.42.66.64    *              255.255.255.248 U    0      0        0 rndis0
192.168.2.0    *              255.255.255.0  U    0      0        0 rndis0
 
bash-3.2# su
 
[root@(none) /]# ip -4 addr
3: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    inet 10.42.66.66/29 brd 10.42.66.255 scope global rndis0
      valid_lft forever preferred_lft forever
    inet 192.168.2.15/24 brd 192.168.2.255 scope global rndis0:0
      valid_lft forever preferred_lft forever
 
[root@(none) /]# ip route
default via 10.42.66.67 dev rndis0
10.42.66.64/29 dev rndis0  proto kernel  scope link  src 10.42.66.66
192.168.2.0/24 dev rndis0  proto kernel  scope link  src 192.168.2.15
 
[root@(none) /]# tracepath -n 8.8.8.8
 1:  send failed
    Resume: pmtu 65535
 
[root@(none) /]# ping -c 5 google.com
ping: unknown host google.com

[root@(none) /]# exit
exit

bash-3.2# ifconfig
rndis0    Link encap:Ethernet  HWaddr B6:23:76:8C:DC:63 
          inet addr:10.42.66.66  Bcast:10.42.66.255  Mask:255.255.255.248
          inet6 addr: fe80::b423:76ff:fe8c:dc63/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1188 errors:0 dropped:0 overruns:0 frame:0
          TX packets:505 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:91017 (88.8 KiB)  TX bytes:60383 (58.9 KiB)

rndis0:0  Link encap:Ethernet  HWaddr B6:23:76:8C:DC:63 
          inet addr:192.168.2.15  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
The computer can ping the Jolla C at 10.42.66.66, and I have run this from it and it returned no error:
Code:
sudo sysctl net.ipv4.ip_forward=1
sudo iptables -t nat -A POSTROUTING -o wlp2s0 -j MASQUERADE
But somehow, something is still perventing it to share internet to the Jolla C, or the Jolla C to pick up.

[Edit] Finally reset to factory state, I love my original Jolla and I largely prefer it over my Jolla C for its form factor actually, but there is an Androdi application that requires 4.4.4 that I need to run and I can't on the Jolla due to its older version of Aliendalvik. :(
Is wlp2s0 your internet device on your computer?
Not wlan0?

mosen 2017-07-27 18:25
Re: 2.1.1/Jämsänjoki EA
 
Quote:
Originally Posted by nieldk (Post 1531439)
Is wlp2s0 your internet device on your computer?
Not wlan0?
I guess he is either using Arch or some systemd naming policy in an other distro.

aspergerguy 2017-07-27 18:52
Re: 2.1.1/Jämsänjoki EA
 
Quote:
Originally Posted by deutch1976 (Post 1531432)
Is it already possible, after a phone flash, to update directly to 2.1.1 or do we still have to update one by one? Thanks
Presumably referring to AquaFish rather than Jolla 1 otherwise you would have your work cut out: https://jolla.zendesk.com/hc/en-us/articles/201836347

Which version are you offered under "Sailfish OS Updates"?

Kabouik 2017-07-27 19:01
Re: 2.1.1/Jämsänjoki EA
 
Yes, wlp2s0 would be the equivalent of wlan0 on my distribution (Solus).

elastic 2017-07-27 20:40
Re: 2.1.1/Jämsänjoki EA
 
Grmblfx - Update bricked my Jolla1 - recovery mode, reset - currently downloading update to 1.1.2.16 - is there any shortcut or do I have to go version by version again ... - btw Sailfish 1.x hat a quite simple and intuitive user interface compared to 2.x - already forgot that ...

Kabouik 2017-07-27 21:39
Re: 2.1.1/Jämsänjoki EA
 
So after factory reset, my Jolla C is back to 2.0.2.43, and readily sees the 2.1.1.23 update (I thought there would be intermediate updates). However, it can't seem to download the update. I've tried more than 8 or 10 times now, I initiated the download with the pulley menu and wait for tens of minutes while the Jolla is busy trying to download (pulley is deactivated), but at some point the phone stopped trying and I can use the pulley menu again to download. There is no download progress visible in the update banner. I'm on wifi with a pretty good internet connexion.

Also, restoring a backup made before I bricked my device two days ago fails.

chilango 2017-07-28 04:06
Re: 2.1.1/Jämsänjoki EA
 
Quote:
Originally Posted by elastic (Post 1531449)
Sailfish 1.x hat a quite simple and intuitive user interface compared to 2.x - already forgot that ...
i completely agree with you in that

nieldk 2017-07-28 06:13
Re: 2.1.1/Jämsänjoki EA
 
Jolla1 updated without issues, remotely using SSH and Even my repo (merproject, not ooenrepos) enabled. Obviously commandline update.


All times are GMT. The time now is 21:39.
Page 6 of 18 « First 45 6 7816 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8