**** BEGIN LOGGING AT Wed Jul 26 03:00:03 2017 Jul 26 04:33:44 http://git.savannah.gnu.org/gitweb/?p=bison.git;a=blob;f=ChangeLog-2012;h=abc1adb6df63a7f01edbbf63b0976a3dc4749510;hb=HEAD#l24505 Jul 26 04:33:52 Unepitaize `return' invocations. Jul 26 04:33:58 DocScrutinizer05: ^ what's that word? Jul 26 04:47:34 bfc Jul 26 04:47:39 nfc Jul 26 04:48:10 and I guess I need a kbd with doublesize keys Jul 26 04:49:03 nfc : no f* clue. NFC : Near-Field Communications. Jul 26 04:50:38 ~spell Unepitaize Jul 26 04:50:40 possible spellings for Unepitaize: Unitize Unities Unitas Initiates Inept Units Unitas's Enmities Entities Entice Appetizer Unit's Anita's Initiate's Unity's Jul 26 07:51:30 access denied. https://twitter.com/christopherneal/status/889503345043427329/photo/1 :-) Jul 26 09:01:28 So I managed to get Kali to boot after following this guide http://talk.maemo.org/showthread.php?t=96573. How do I type a number into the terminal? I tried all the normal maemo functions Jul 26 09:08:07 can you pull up an on screen keyboard? Jul 26 09:08:37 in the worst case might be worth running generic xvkbd or similar Jul 26 09:10:02 sixwheeledbeast^ nope Jul 26 09:10:08 Cant even boot to the graphical interface Jul 26 09:11:25 brb Jul 26 09:21:52 back Jul 26 22:01:21 re - random reboots on my N900 - traced it to cvm/phoneme (or a misbehaving j2me application) .. possibly thumb problems (but a wil guess) Jul 26 22:02:53 incidentally, i'd used cvm for months before on thumb with no problem whatsoever. however, recently when i reinstalled it and run a JAR file, within 5 minutes the device had restarted. since removing it permanently, no reboot for 3 days now Jul 26 22:03:17 unfortunate, but at least mystery solved Jul 27 00:32:30 sicelo: how about a project for your term? populate 3rd blade in server Jul 27 00:33:46 needed: CPU, RAM, drives Jul 27 00:34:25 I hope the managed switch would still have a two spare ethernet jacks Jul 27 00:35:26 afaik there should be sufficient funds in maemo eV's kitty Jul 27 00:39:21 http://wiki.maemo.org/Maemo.org_Infrastructure Jul 27 00:41:28 http://www.supermicro.nl/products/motherboard/Xeon/C600/X9DRT-HF.cfm Jul 27 00:47:09 May I hijack this channel to ask a question about a Jolla here? Hopefully some people in #maemo do have Jollas as well, and I have got no answer in #jollamobile in 4 hours, looks a bit dead there Jul 27 00:51:43 Kabouik_: probably many guys here have a Jolla.. but i have no idea how many are available now.. Jul 27 00:52:22 And I wonder how many would know how to get internet access from a Jolla C in recovery shell using Linux computer as a router. :P Jul 27 00:53:05 I've gone through all the steps to do that with a Jolla 1, and since the guide was considered valid on TJC, I guess it just works. But on Jolla C, I get no errors, but no connection either (https://together.jolla.com/question/22079/howto-all-computer-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/?answer=45710#post-id-45710) Jul 27 01:00:17 * Oksana has SeaMonkey nightly-too-buggy-to-open-clicked-links and link-recognition-capturing-brackets-into-the-link Jul 27 01:00:29 http://www.servermonkey.com/2-0-ghz-eight-core-intel-xeon-processor-with-20mb-cache-e5-2640-v2.html https://www.amazon.com/Intel-E5-2620-Six-Core-Processor-BX80635E52620V2/dp/B00F29C61K || http://www.crucial.de/deu/de/upgrade-kompatibel-mit/Supermicro/2027tr-htrf e.g 4 to 8 pcs http://www.crucial.de/deu/de/2027tr-htrf/CT4224505 Jul 27 01:00:46 plus 2 drives server grade Jul 27 01:01:33 Kabouik : which step is it? https://jolla.zendesk.com/hc/en-us/articles/204709607#24 Jul 27 01:02:45 Oksana, it's not in this guide. This one is just for getting to recovery mode, or backing up data. Jul 27 01:03:13 What I'm trying to do is using my computer as a route so that the Jolla in recovery mode gets internet access, and so I can use zypper in recovery mode Jul 27 01:03:43 This is the link I mentioned above, and I did everything as described, no issue, but no Internet access. Jul 27 01:09:00 we have like 20-40 spare servers at the uni that we want to throw out. Jul 27 01:11:28 oops sorry, rather the 1V35 instead of 1V5: http://www.crucial.de/deu/de/2027tr-htrf/CT5789373 Jul 27 01:29:44 Jolla shows up as eth2 (or something) device, telnet works fine, recovery tool, then you go into shell, want to use zypper, zypper needs Internet... Jul 27 01:29:56 * Oksana was distracted, will read the page further Jul 27 01:33:01 Kabouik_ : after you did route add default gw 10.42.66.67 , can you ping 10.42.66.67 ? Jul 27 01:33:21 No, pinging it is not allowed, I've tried Jul 27 01:33:33 And I can't devel-su from chroot to try with root rights Jul 27 01:34:11 Ouch... Jul 27 01:34:22 Okay, can your computer ping your phone? Jul 27 01:35:08 How is it that zypper runs and ping doesn't? Don't they both need root rights? Jul 27 01:35:09 Yes, it can Jul 27 01:35:35 I'm not sure, you don't really need to be root to use pkcon or zypper from Sailfish terminal I think Jul 27 01:36:20 Okay... What does route say? Jul 27 01:36:37 bash-3.2# route Jul 27 01:36:37 Kernel IP routing table Jul 27 01:36:37 Destination Gateway Genmask Flags Metric Ref Use Iface Jul 27 01:36:37 default 10.42.66.67 0.0.0.0 UG 0 0 0 rndis0 Jul 27 01:36:37 default 192.168.2.15 0.0.0.0 UG 0 0 0 rndis0 Jul 27 01:36:37 10.42.66.64 * 255.255.255.248 U 0 0 0 rndis0 Jul 27 01:36:39 192.168.2.0 * 255.255.255.0 U 0 0 0 rndis0 Jul 27 01:36:45 Woops, should have put it on hastebin, sorry Jul 27 01:37:20 I would have deleted everything except for 10.42.66.67 Jul 27 01:37:32 I'm not sure why I have 4 entries here. Pretty sure 192.168.2.15 is something I tried after 10.42.66.67 did not work, and I didn't know how to delete it Jul 27 01:38:11 Feel free to delete everything and then re-add the one you need Jul 27 01:40:02 I could delete default 192.168.2.15, but not sure how to delete 10.42.66.64 and 1092.168.2.0 Jul 27 01:40:14 * Oksana hasn't wrestled with route in a while... Did have USB networking a few times, very similar, only N900 instead of Jolla Jul 27 01:40:49 try 'route del 10.42.66.64' or 'route delete 10.42.66.64' Jul 27 01:41:13 Nope, it says SIOCDELRT: no such process Jul 27 01:41:33 https://linux.die.net/man/8/route Jul 27 01:41:44 ugh again sorry, the 1V35 are 1600, we should get 1866 though and those are 1V5 only it seems. Anyway all just suggestions to get verified with an expert before ordering Jul 27 01:42:08 Feel free to run just 'route' again to see what it looks like Jul 27 01:42:45 The same as before just without the 192.168.2.15 line Jul 27 01:42:51 Also, run zypper or something to see if it works (since you now have one default gw instead of two?) Jul 27 01:43:06 Still no ping or zypper no :( Jul 27 01:43:18 anyway you need 2 CPU 2600 v2, 4 or 8 240pin DDR3, idealy registered or buffered or even LRDDR3, and 2 drives SATA6 server grade Jul 27 01:43:25 Okay, then let's remove the other two lines Jul 27 01:44:05 But I can't find how, just route del 192.168.2.0 throws this error. It worked for the other line because it was called 'default 192.168.2.15' I think Jul 27 01:45:00 Use -net Jul 27 01:45:09 route del -net 192.168.2.0 Jul 27 01:45:23 https://serverfault.com/questions/181094/how-do-i-delete-a-route-from-linux-routing-table#735257 Since man is lacking Jul 27 01:45:40 Invalid argument :< Jul 27 01:48:54 Does man route run on phone, by any chance?.. Jul 27 01:49:35 route --help maybe? Jul 27 01:50:46 No man, but route --help yes. Unfortunately I can only see one mention of del (delete) but not how to delete these two lines that have IPs in the Destinatioin column of the route output Jul 27 01:51:29 svetlana recommends asking ##linux about route del Jul 27 01:51:48 I'll try, thanks Jul 27 01:52:26 Good luck Jul 27 01:52:27 you'd have to register your nick first, '/msg nickserv register PASS E@MAIL' and check your email, takes just a min Jul 27 01:53:13 Or login, if already registered with NickServ ;-) Jul 27 01:53:40 /msg NickServ Identify Nick Pass or something Jul 27 01:53:49 yes Jul 27 01:57:58 [2017-07-27 Thu 03:57:42] [Notice] -NickServ- Information on Kabouik (account Kabouik): Jul 27 01:57:59 [2017-07-27 Thu 03:57:42] [Notice] -NickServ- Registered : Jun 19 10:59:14 2017 (5w 2d 14h ago) Jul 27 01:58:38 Whois] Kabouik_ is ~kabouik@32.232.202.84.customer.cdi.no (Konsieur) [Notice] -NickServ- Last addr : ~kabouik@32.232.202.84.customer.cdi.no Jul 27 01:59:26 err [Notice] -NickServ- User seen : now Jul 27 01:59:54 route del -net 10.42.66.64 gw 0.0.0.0 netmask 255.255.255.248 dev rndis0 <- this seems to have worked for deleting Jul 27 02:00:20 now I only have one line in route Jul 27 02:00:37 But still no ping on www.google.com :( Jul 27 02:01:20 to start with, ping an IP, e.g. 8.8.8.8 Jul 27 02:01:46 please pastebin your route table Jul 27 02:01:55 I just typed pint 8.8.8.8. I guess that's what I'd need now. Jul 27 02:01:58 A pint. Jul 27 02:02:15 :-) Jul 27 02:02:43 bash-3.2# route Jul 27 02:02:43 Kernel IP routing table Jul 27 02:02:43 Destination Gateway Genmask Flags Metric Ref Use Iface Jul 27 02:02:43 default 10.42.66.67 0.0.0.0 UG 0 0 0 rndis0 Jul 27 02:02:47 Oh god sorry Jul 27 02:03:00 that's all? Jul 27 02:03:06 I hastebined it but did not update the clipboard :P Jul 27 02:03:14 Yeah after cleaning the extra lines I got before Jul 27 02:03:22 shit happens Jul 27 02:03:39 Ping 8.8.8.8 returns permission denied, and I can't devel-su from recovery I think Jul 27 02:03:47 Or I don't know what is the default password at least. Jul 27 02:04:42 no idea, sorrxy Jul 27 02:05:26 your route lacks a network for gateway Jul 27 02:06:06 compare arbitrary other unix system Jul 27 02:06:27 Destination Gateway Genmask Flags Metric Ref Use Iface Jul 27 02:06:29 default 172.31.1.1 0.0.0.0 UG 0 0 0 eth0 Jul 27 02:06:30 172.31.1.0 * 255.255.255.0 U 0 0 0 eth0 Jul 27 02:06:31 The guide on TJC just says "route add default gw 10.42.66.67" Jul 27 02:09:13 default 192.168.4.1 0.0.0.0 UG 0 0 0 eth0 Jul 27 02:09:14 192.168.4.0 * 255.255.255.0 U 1 0 0 eth0 Jul 27 02:09:35 route -n returns that though: https://hastebin.com/qejopusaxu Jul 27 02:10:10 as I saud, missing one line Jul 27 02:10:44 Thhttps://hastebin.com/usugobomud probably one of these I guess? Jul 27 02:11:42 yes, the third line is cruft, line 1 and 2 look correct Jul 27 02:12:38 Of course using the same command I used to delete, only with add instead of del, doesn't work. :P Jul 27 02:14:00 cehck ifconfig for own IP (should be in 10.42.66.64/30(?) network), and ping 10.42.66.67 Jul 27 02:14:32 You mean from the computer, or from the recovery shell of the Jolla? Jul 27 02:14:54 from the device where you run that route command, I assume that's jolla, no? Jul 27 02:15:26 Yes. It's IP is 10.42.66.66, but I can't really ping anything from it (I can ping it from the computer though) Jul 27 02:15:30 and 10.42.66.67 the IP of the USB(?) NIC on your PC Jul 27 02:16:21 10.42.66.66 is the IP I used with telnet to reach the phone from the computer, and it's the phone rndis0 ip. 10.42.66.67 is the corresponding network interface of the computer Jul 27 02:16:28 you can ping it from PC. Fine. Can you ssh in to device? Jul 27 02:16:39 or telnet Jul 27 02:16:45 I am in telnet Jul 27 02:16:58 so your connection to PC is already established Jul 27 02:17:11 ssh, I doubt it, it's bricked and only on through the recovery shell Jul 27 02:17:36 your problem is most likely forwarding on PC then Jul 27 02:17:41 But the phone can't access the internet using the computer as router, and I need it to check package issues with zypper Jul 27 02:17:59 aka the PC doesn't work as router Jul 27 02:18:02 (I haven't added that missing line in route though, couldn't figure out how to do so yet) Jul 27 02:18:28 What does iptables on computer say? Jul 27 02:18:41 I've ran sudo sysctl net.ipv4.ip_forward=1 and sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE, on the computer Jul 27 02:19:06 yeah, that's prolly the right thing to do Jul 27 02:19:32 iptables needs a command. -L for list? Jul 27 02:19:37 Yes Jul 27 02:19:40 An argument I meant Jul 27 02:19:46 so which commands creating traffic do you have? Jul 27 02:19:47 Well then it's empty yes Jul 27 02:20:22 https://hastebin.com/zabumubohe Jul 27 02:20:46 * Oksana thinks that 'iptables -L' should not be empty after 'iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE' Jul 27 02:21:12 yep Jul 27 02:21:25 So maybe I should investigate on the irc channel for my distro Jul 27 02:21:41 that's not distro specific Jul 27 02:21:56 ##netwoking Jul 27 02:22:02 Also, does your computer use eth0 or wlan0 for Internet, and does it matter for iptables?.. Jul 27 02:22:02 But I would have fewer remorse asking them :P Jul 27 02:22:15 wlan0, I'm on a laptop at the moment Jul 27 02:22:51 By the way, https://hastebin.com/zabumubohe looks exactly like values on my N900, and it is not set up as a router Jul 27 02:23:25 first of all make sure that plugging in the phone doesn't drop your PC's regular internet connection. Network Manager is notorious for doing that sort of shit Jul 27 02:24:03 I'm talking to you using that computer, internet access is still here Jul 27 02:24:04 Well, Kabouik's computer seems to have good Internet all the while Jolla is plugged in, right?.. Jul 27 02:24:56 please do iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE Jul 27 02:25:08 On computer ^ Jul 27 02:25:19 please do iptables -t nat -A POSTROUTING -o wlan0 -j MASQUERADE even, I'd guess Jul 27 02:25:29 * Oksana suggests replacing eth0 with wlan0 , but that's first time I see iptables Jul 27 02:25:53 ...not sysctl Jul 27 02:25:54 Done, but iptables -L still empty Jul 27 02:26:05 that's very odd Jul 27 02:26:11 damn rawcam doesn't want to take photos of bright objects Jul 27 02:26:22 I tried with wlan0 even before coming here actually, did not work (but I did not check iptables -L) Jul 27 02:26:24 i guess it's time Jul 27 02:26:39 where do i get a known good firmware for n900? Jul 27 02:26:46 and iptables doesn't throw error? Jul 27 02:26:54 No Jul 27 02:26:58 Just silent Jul 27 02:27:00 weeeird Jul 27 02:27:19 Let's see if there is a -v argument for iptables Jul 27 02:27:37 MASQUERADE all opt -- in * out wlan0 0.0.0.0/0 -> 0.0.0.0/0 Jul 27 02:27:41 This is what I get. Jul 27 02:27:44 * DocScrutinizer05 blames systemd ;-P Jul 27 02:28:28 please pastebin full ifconfig on your PC Jul 27 02:29:13 https://hastebin.com/nuxajalemu Jul 27 02:29:33 arrrgh Jul 27 02:29:41 Oh yeah maybe I should try with wlp2s0? Jul 27 02:29:42 s/wlan0/wlp2s0/ to start with Jul 27 02:31:05 iptables sucks big time, not throwing error on wrong IF Jul 27 02:31:28 I still get the same verbose with wlp2s0 in the iptables command Jul 27 02:31:35 :-S Jul 27 02:31:42 And empty iptables -L Jul 27 02:32:08 By the way, am I messing with the computer here? Will everything reset to original state after reboot or? Jul 27 02:33:01 Oh, I notice I missed the "sudo iptables" in your quote above, only seen the "sysctl" Jul 27 02:33:28 yes Jul 27 02:33:40 except sysctl maybe Jul 27 02:34:13 Ok, but sysctl will be easy to revert Jul 27 02:34:32 please check a "HowTo share internet access" for your distro Jul 27 02:34:39 yep Jul 27 02:35:24 Couldn't find one when I tried DocScrutinizer05, but I may ask on the irc channel tomorrow, they are fairly active Jul 27 02:35:36 *I* had to stop network manager to make internet sharing work Jul 27 02:35:55 YMMV Jul 27 02:36:31 Let's try Jul 27 02:36:38 ~usb-networking Jul 27 02:36:39 methinks usb-networking is http://wiki.maemo.org/USB_networking, or http://wiki.maemo.org/N900_USB_networking, or http://wiki.maemo.org/User:Joerg_rw/usb-networking, or http://wiki.maemo.org/N900_USB_router Jul 27 02:37:42 http://wiki.maemo.org/USB_networking#Linux Jul 27 02:37:42 Now before going to bed I'd like at least to readd that missing line in the route of the Jolla Jul 27 02:38:31 that missing line *might* get added automatically Jul 27 02:39:15 the problem is when you tear down the default route, your telnet access will break anyway Jul 27 02:39:29 I still have telnet access here Jul 27 02:39:47 But I will exit and reboot into recovery again, to see if the line is back Jul 27 02:39:50 hmm, right, inbound Jul 27 02:39:57 reboot is a big word since the phone is unbootable :P Jul 27 02:40:01 yep, good plan Jul 27 02:40:22 it boots, juist not to the regular system Jul 27 02:41:43 Well now it tells me that /proc/net/route: not such file or directoryINET (IPV4) not configured in this system. :D Jul 27 02:41:44 basically your problem is probably around DNS IP for the device, since you don't run a DHCP server on your PC to tell the device which DNS to use Jul 27 02:42:29 so start with using IPs instead URLs Jul 27 02:42:51 or add a default DNS like 8.8.8.8 Jul 27 02:44:01 I did that DocScrutinizer05, it's in the guide I'm trying to use Jul 27 02:44:02 https://together.jolla.com/question/22079/howto-all-computer-users-recover-or-reset-a-device-that-is-stuck-in-boot-loop/?answer=45710#post-id-45710 Jul 27 02:44:03 try connecting from device to IP of your PC. If that works, the rest is just about default route and your PC config. And DNS Jul 27 02:46:18 I don't get why now route throws this /proc/net/route error. I had it before, and then it finally returned the route I detailed to you before, and now it's back to the error Jul 27 02:46:29 I have no idea what I have done to get rid of that error earlier Jul 27 02:48:23 which error? Jul 27 02:48:37 Well now it tells me that /proc/net/route: not such file or directoryINET (IPV4) not configured in this system. :D Jul 27 02:49:18 on which command? Jul 27 02:49:34 route or route -n Jul 27 02:49:44 From the telnet shell Jul 27 02:49:48 did you do chroot? Jul 27 02:49:51 Yes Jul 27 02:50:21 you prolly must not be in a chroot Jul 27 02:50:47 I had this before actually, but then when we discussed it here it finally was working without anything special that I remember Jul 27 02:50:55 unless the chroot also bindmounted the true /proc to the chroot dir Jul 27 02:51:00 I am, just did chroot /mnt/rootfs Jul 27 02:51:15 Oh right! THat's what I did earlier! I mounted /proc Jul 27 02:51:54 So yeah, now that it's mounted, route is back Jul 27 02:52:12 And the missing line is back as well (and 192.168.2.0 too by the way, weird) Jul 27 02:52:18 you can't mount /proc, that's bogus in a chroot. You need to bindmount it into your chroot-dir/proc *before* you chroot into that dir Jul 27 02:53:06 Does that apply to any device? I could just 'mount /proc' from the chroot here and it did solve the route output issue Jul 27 02:54:16 yes, that's basic chroot 101, unless there's sth *very* special about sailfish Jul 27 02:54:18 So basically I should exit chroot, mkdir chrootdir/proc, mount /proc chrootdir/proc, and then chroot? Jul 27 02:54:52 the whole purpose of a chroot is to hide true /proc and /sys etc from the chroot user Jul 27 02:55:07 yes Jul 27 02:55:17 mount -o bind Jul 27 02:55:17 Well actually it seems that I don't even need to chroot with the Jolla C Jul 27 02:55:32 Straight in the shell, without doing anything, I can run route and see the output Jul 27 02:55:43 yes Jul 27 02:56:15 but you can't install stuff to your sailfish rootfs with zypper that way Jul 27 02:56:22 Maybe I should try to use the guide WITHOUT the chroot bits? The guide was made for the Jolla 1, in which rootfs is not already mounted, while it seems to be the case for the Jolla C Jul 27 02:56:26 Oh Jul 27 02:57:52 actually if your rescueos has zypper, you can try it in there without chroot, and when it works, you bindmount proc into /mnt/rootfs/proc and do chroot /mnt/rootfs, then you can run zypper against sailfish rootfs Jul 27 02:58:54 I don't know about rootfs already mounted in kolla C Jul 27 02:58:55 Trying to see if I can get internet sharing without chrooting also Jul 27 02:59:30 Kabouik_: in recovery you have /rootfs already mounted. jolla c is using lvm, so there is /dev/sailfish subvolumes Jul 27 02:59:41 you should already have /rootfs mounted Jul 27 02:59:57 oooh **** ENDING LOGGING AT Thu Jul 27 03:00:01 2017