**** BEGIN LOGGING AT Thu Mar 31 02:59:58 2016 **** BEGIN LOGGING AT Thu Mar 31 03:29:41 2016 Mar 31 09:13:34 Do I have to open Flopswap to make it work, or is there a daemon? Mar 31 09:16:55 just make a bigger swap partition and use it Mar 31 09:16:58 srsly Mar 31 09:20:38 The wiki says that it will not be as efficient as a swap on the SD card, and then if using SD swap, it seems flopswap is the best option Mar 31 09:21:20 This is actually impressive: https://vimeo.com/109855151. So I made 2 swaps partitions on the SD, plus the internal, and flopswaps seems to work. Just don't know if I have to manually open it. Mar 31 09:22:21 how big is your swap partition? Mar 31 09:22:28 About 800 MB Mar 31 09:23:07 yeah i'm talking like Mar 31 09:23:10 2gb Mar 31 09:23:11 or 4gb Mar 31 09:23:40 SD or internal? Mar 31 09:23:44 sd Mar 31 09:23:50 to avoid I/O starvation Mar 31 09:24:04 If I could achieve the result in the video (with flopswap and partitions ~800MB), that'd be perfect for me Mar 31 10:01:20 There's probably not actually going to be any difference if you use a swap file. Mar 31 10:01:36 just as long as it doesn't start out heavily fragmented. Mar 31 10:01:53 Hum, for some reason I can't ssh into my N900 anymore. I just unburried it two days ago so sorry for the numerous questions, it's not easy to get back to it. :) Mar 31 10:02:13 The filesystem tells Linux where the swap file lives on disk, so Linux bypasses the filesystem from there. Mar 31 10:02:46 I changed ssh password with "sudo gainroot" and "passwd user" in the N900, but then when I try to ssh to user@ip, the password is incorrect. Do I have to reboot for the password to be taken into account in ssh? Mar 31 10:03:01 Kabouik_: no. Mar 31 10:03:21 I have no idea what is wrong then. Mar 31 10:03:33 Kabouik_: what are the first two characters for the hash in /etc/shadow? Mar 31 10:03:47 About swap, my question was just whether Flopswap automatically runs in background, or if I have to manually open it Mar 31 10:03:57 Kabouik_: they should be $1 (bad, insecure) or $5 (slightly better) Mar 31 10:04:11 wait, that's not right. Mar 31 10:04:25 $1 is the slightly better one (MD5). Mar 31 10:04:28 Apparently there's no /etc/shadow on my N900 Mar 31 10:04:45 Maybe that's why it doesn't work. Mar 31 10:05:07 And on my computer, there's one but it's empty Mar 31 10:05:11 oh, right, it's just in /etc/passwd Mar 31 10:06:17 I don't see any $1 or $5 in /etc/passwd, it starts with "root:blahblah" Mar 31 10:06:31 Right, so it's probably just DES, which is the insecure one. Mar 31 10:07:01 What should I do? Mar 31 10:07:38 Have you sshed in as user before? Mar 31 10:08:03 Yeah but it was long ago, I don't remember reinstalling either Linux or Maemo since then though Mar 31 10:08:09 I feel like I might've had to change something in sshd_config to enable it .. or it might've been root. Mar 31 10:08:18 I even still have a preconfigured Filezilla connection for the N900 @user Mar 31 10:12:57 I'm off to lunch, will check that later. Weird though, using the exact same password as I typed it after "passwd user" on the N900, and I get a "permission denied" when attempting ssh to user Mar 31 10:13:47 try `mkpasswd -S ..` on some system, where `..` is the first two characters in the hash you saw in /etc/passwd Mar 31 10:13:56 see if it comes back with the same hash. Mar 31 10:40:37 < Kabouik_> Guys, I have an EasyDebian partition on a small SD card and would want to move it to a partition on a larger SD card. Is it possible, or will it fail because of different mmcblk or whatever? Is there a file Mar 31 10:40:41 I can edit to tell the N900 where is the new EasyDebian partition? Mar 31 10:40:49 Kabouik_: /home/user/.chroot Mar 31 10:42:19 flopswap .. do a dpkg -L flopswap which will show you all files that flowswap installs, then you'll know if there's a daemon or not. not using flopswap myself Mar 31 10:54:07 Sicelo thanks, but in the end I have had to change my SD card for other reasons so I reinstalled EasyDebian. Was actually about to edit /home/user/.chroot file to check the settings when I faced my ssh issue Mar 31 11:08:46 Maxdamantus: I confirm the password comes back with the same hash with mkpasswd -S Mar 31 11:11:18 If it is of any help: I'm trying to ssh through usb. usb0 ip is 192.168.2.16 on the N900 and 192.168.2.14 on the computer. Mar 31 11:11:25 They cannot ping each other. Mar 31 11:12:34 Kabouik: what the heck? Mar 31 11:12:37 I was mistakenly trying to ssh the wrong ip earlier, hence the wrong password (wrong user name in fact). Was trying to ssh from computer to computer. :< Mar 31 11:12:54 So now, with the right ip, the error is: ssh: connect to host 192.168.2.16 port 22: No route to host Mar 31 11:14:34 ~usbnetworking Mar 31 11:14:34 methinks usbnetworking is http://wiki.maemo.org/USB_networking, or http://wiki.maemo.org/N900_USB_networking Mar 31 11:17:24 ip route show Mar 31 11:30:04 I was already following the second wiki link Mar 31 11:30:13 And remembered I did so in the past Mar 31 11:31:02 My /etc/network/interfaces is properly configured for instance Mar 31 11:35:13 sorry I can't help much, USB networking is way too inconvenient, I use WLAN only Mar 31 11:36:04 Can you post the relevant output from `ifconfig` on both systems? Mar 31 11:36:06 when USB then mass storage mode Mar 31 11:36:34 * Maxdamantus always has g_eth loaded. Mar 31 11:36:37 g_ether* Mar 31 11:36:50 WLAN is not very convenient here because I'm at work on a institutional network Mar 31 11:37:17 I see, fair enough Mar 31 11:38:57 http://hastebin.com/miseyoxoco.css for computer Maxdamantus. Let me connect to IRC with N900 for pasting the output here Mar 31 11:39:54 Octets transmis:0 (0.0 B) Mar 31 11:40:05 wifi also eats more power and is less stable and latency is worse Mar 31 11:40:18 If that's after trying ping, it might mean your computer doesn't route through it. Mar 31 11:40:42 try `ip route show` Mar 31 11:40:45 usb0 Link encap:Ethernet HWaddr 2E:05:52:76:73:23 Mar 31 11:40:57 That's the N900 side Mar 31 11:41:13 you still could use adhoc WLAN Mar 31 11:41:32 Damn, the paste did not work Mar 31 11:43:03 What does `ip route` look like on the computer side? Mar 31 11:43:16 n900 side: http://pastebin.com/ePWG5vru Mar 31 11:43:28 Konsieur = Kabouik Mar 31 11:44:07 ip route Maxdamantus: http://hastebin.com/tiyerojezo.cpp Mar 31 11:45:10 this looks good Mar 31 11:45:24 After doing `ping 192.168.2.16`, does `Octets transmis` in `ifconfig` increase? Mar 31 11:45:27 as far as I can tell, with a lack of coffee Mar 31 11:46:05 From 192.168.2.14 icmp_seq=1 Destination Host Unreachable Maxdamantus Mar 31 11:46:05 And still 0 bytes transmitted Mar 31 11:47:06 I know it did work in the past, I don't know what has changed Mar 31 11:47:48 wait, what's your N900 IP? Mar 31 11:47:54 192.168.2.14 Mar 31 11:48:01 Sorry Mar 31 11:48:04 and USB IP on PC? Mar 31 11:48:06 192.168.2.16 Mar 31 11:48:11 And computer .14 Mar 31 11:48:31 I mixed it just above, right after you asked, forget this line Mar 31 11:48:46 and on computer you got a route for 16 via interface 14(USB)? Mar 31 11:49:29 I honestly don't know how to check that Mar 31 11:49:33 I think there should be a RUNNING flag. Mar 31 11:50:38 RX packets:516 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 Mar 31 11:50:49 on your N900, doesn't look too bad Mar 31 11:52:07 192.168.2.0/24 dev usb0 proto kernel scope link src 192.168.2.14 on PC also looks good Mar 31 11:52:25 again with disclaimer "afaict" Mar 31 11:53:04 though I'm not familiar with ip Mar 31 11:53:21 I'm still a ifconfig and route guy Mar 31 11:54:05 I'm mostly concerned that it doesn't list the "RUNNING" flag in ifconfig. Mar 31 11:54:16 How did you configure the interface? Mar 31 11:54:44 What kind of question is that! :< Mar 31 11:55:02 (I don't know, don't laugh. Was a long time ago. :p Probably just followed the Maemo wiki). Mar 31 11:55:05 Hm .. /etc/network/interfaces Mar 31 11:55:47 Yeah, that I followed the N900 USB networking wiki page, just change the IP for .16 instead of .15 (.15 is my Jolla) Mar 31 11:56:10 I'd probably try removing (or commenting out) anything to do with usb0 in there. Mar 31 11:56:23 then just reconnecting it and doing `ifconfig 192.168.2.14` Mar 31 11:56:32 er, `ifconfig usb0 192.168.2.14` Mar 31 11:57:22 On computer, /etc/network/interfaces is just this: Mar 31 11:57:23 auto lo Mar 31 11:57:24 iface lo inet loopback Mar 31 11:57:38 what about interfaces.d? Mar 31 11:57:50 On N900, it's as in the wiki, just with 192.168.2.16 instead of 192.168.2.15 Mar 31 11:57:59 interfaces.d empty Mar 31 12:00:38 You should only really need to run one command on the computer, the ifconfig one I said above. Mar 31 12:01:11 unless you've set up some sort of firewall software like shorewall. Mar 31 12:01:49 The wiki seems to mostly talk about modifying things in /etc Mar 31 12:08:48 Kabouik: which is your C system? Mar 31 12:08:52 PC Mar 31 12:09:18 Kabouik: and does it use network manager or sth like that? Mar 31 12:09:30 Kabouik: do you have a firewall set up? Mar 31 12:11:27 Kabouik: also I noticed several times that my PC side routing got messed up FUBAR, so only a reboot helped Mar 31 12:12:23 it _really_ got messed up, not just bad configuration but it shown garbage and didn't follow configuration commands anymore Mar 31 12:13:19 nowadays it seems systemd introduces new problems with interface and route config Mar 31 12:15:02 Sorry DocScrutinizer05, had to leave the office Mar 31 12:15:09 I'm running Mint 17.3 Mar 31 12:15:38 can't comment on mint, never touched it Mar 31 12:15:40 For some reason, I see the N900 in the network manager indeed. Noticed that just 10 min ago but had to leave before I could tell Mar 31 12:16:03 And the N900 appears toggled off. If I tried to toggle it on, it attempts connection, but eventually will revert to off Mar 31 12:16:08 network manager completely messes up all config you try to do manually Mar 31 12:16:42 yes, since network manager treats all USB IP devices as a upstream NIC Mar 31 12:17:08 and your N900 doesn't offer internet connectivity (by default) neither DHCP Mar 31 12:18:13 so network manager tries to get a new internet connection via USB and that fails, so it takes down the interface Mar 31 12:18:30 Ok, so I should not bother about the network manager I guess Mar 31 12:18:33 (long story short) Mar 31 12:18:48 you should shut off NM all together Mar 31 12:18:54 I had to do that Mar 31 12:18:57 Network management is: ifconfig usb0 192.168.2.14 Mar 31 12:19:00 Don't know how to do that :[ Mar 31 12:19:01 3 words. Mar 31 12:19:16 I did it Maxdamantus, but still can't ping N900 Mar 31 12:19:38 does ifconfig show both `UP` and`RUNNING` yet? Mar 31 12:20:11 Nope. But usb1 does. Mar 31 12:20:18 Don't know what is usb1 though, there's not ip in it Mar 31 12:20:42 if there are multiple usb devices, the highest one is probably the N900.. Mar 31 12:20:58 unless you've been plugging other ones in recently. Mar 31 12:21:11 usb1 might be my ethernet adapter (I have a thin laptop with no RJ45 port) Mar 31 12:21:32 Could that not be usb0? Mar 31 12:21:41 Ah yes you're right, usb1 seems to be the N900. Mar 31 12:21:52 So I should try ifconfig usb1 192.168.2.14? Mar 31 12:22:09 Yes, probably after ifconfig usb0 down Mar 31 12:22:44 ! Mar 31 12:22:47 Ping! Mar 31 12:22:53 pong Mar 31 12:23:13 Working ssh connection! Mar 31 12:23:22 hah! Mar 31 12:23:51 Great, thanks folks! I am sorry I mixed usb0 and usb1. I'm 100% positive N900 always was usb0 in the past, but I guess I did not use the RJ45 adapter at this time Mar 31 12:24:14 perfect explanation Mar 31 12:24:47 I should have pasted the whole output of ifconfig instead of usb0, you guys would surely have spotted the issue immediately Mar 31 12:24:57 usb device naming is a mess Mar 31 12:25:06 yes Mar 31 12:25:08 :-) Mar 31 12:27:13 Should I do ifconfig usb1 192.168.2.14 before every connection Maxdamantus, or will it be stored in a config file on my computer? Mar 31 12:27:23 for USB naming mess, see init() in http://maemo.cloud-7.de/maemo5/usr/local/bin/u1233-wip Mar 31 12:27:24 It won't be stored. Mar 31 12:27:39 You'll need to do it each time you connect the plug. Mar 31 12:28:02 No way to make it permanent? Mar 31 12:28:09 Kabouik: I use a script to do such stuff on PC Mar 31 12:28:30 Yeah, I prefer just making scripts for these sorts of things. Mar 31 12:28:43 for 'permanent' you need to mess around with udev-rules Mar 31 12:28:46 though in this case it's easy enough for me to just invoke ifconfig directly. Mar 31 12:29:01 Ok Mar 31 12:29:31 on the N900 side I just have it load g_ether and configure the interface in rcS-late Mar 31 12:29:55 (the N900 will remember its configuration until g_ether is unloaded) Mar 31 12:30:14 or g_nokia if you're using that. Mar 31 12:31:46 And I could successfully edit /home/user/.chroot to make EasyDebian work, great. I expected to have another issue with my terrible Linux skills, but it worked. :] Mar 31 12:32:18 Kabouik: linux is not *that* hard to get right :-) Mar 31 12:32:49 I can do basic things, but when you start using your big udev words, I know I'm starting to be lost. :) Mar 31 12:41:55 There's still an issue but it might be related to the image I tried. LXDE does not display the menu (start menu equivalent) and the top bar. They actually appear for a fraction of a second when launching LXDE, but then dissapear Mar 31 12:42:21 I'm using debian-m5-estel.img.ext3 image Mar 31 12:43:32 https://wiki.maemo.org/Easy_Debian#LXDE_Top_Menu_Disappears will investigate this Mar 31 12:45:06 They're actually just autohiding and very hard to show again, apparently Mar 31 12:59:10 Kabouik: there are now, debian jessie armhf images, better ... was a fiddylr hack to create but they exist =) Mar 31 13:15:09 Ah, interesting enyc! Do you have any link? Mar 31 19:01:48 HI! Can you pls help me with u-boot? With fat MyDocs it even doesn't show menu with kernels. I switched to ext3 and now it shows different kernels but I can't boot any external kernel because of "unsupported filesystem" Mar 31 19:14:25 alien2003: silly question but can you just copy those other kernels onto the ext3 filessytem so u-boot *can* read them ? Mar 31 19:15:27 enyc: They are on it. They are everywhere... in /boot, in /opt/boot, in MyDocs... Mar 31 19:15:41 I tried to copy them everywhere Mar 31 19:23:58 alien2003: so.. it then boots said kernels ok ??? but they can't then mount a root filesystem where needed? Mar 31 19:27:54 enyc: it can only boot attached kernel :( Mar 31 19:58:11 uboot checks existing kernels during post-install Mar 31 19:58:28 and whenever you call u-boot-update-bootmenu Mar 31 19:58:35 yep Mar 31 19:58:41 thanks, I forgot the name Mar 31 19:58:57 now the only name missing is the config files dir Mar 31 19:59:11 bootmenu( ? Mar 31 19:59:17 bootmenu/ ? Mar 31 19:59:34 /etc/boot Mar 31 19:59:40 :nod: Mar 31 19:59:55 alien2003: ^^^ Mar 31 20:00:30 DocScrutinizer05: I have that folder Mar 31 20:00:46 yes, and all your kernels need to be configured in there Mar 31 20:01:08 however, do note that it's not actually checked by uboot Mar 31 20:01:10 once that's accomplished, you run the script kerio said# Mar 31 20:01:18 it's only used by the script that builds the actual menu Mar 31 20:01:25 bootmenu.img.d, right? Mar 31 20:01:25 exactly Mar 31 20:01:31 also, do note that pali's uboot doesn't do extfs Mar 31 20:01:52 it'll read uboot.scr or whatever it's called from the first vfat partition on the emmc or on the sd Mar 31 20:01:59 hm? uboot has support for ext2,3,4 Mar 31 20:02:03 :o Mar 31 20:02:09 then what doesn't it support Mar 31 20:02:10 hehe Mar 31 20:02:18 there are my kerbek zInages in that folder Mar 31 20:02:31 why was i convinced that you needed a vfat partition then Mar 31 20:02:42 ugh, you need config files in that folder Mar 31 20:02:49 not zImages Mar 31 20:02:53 with vfat partition it even doesn't show a menu with kernels Mar 31 20:02:55 http://git.denx.de/?p=u-boot.git;a=blob;f=include/configs/nokia_rx51.h;h=5c4140526dc16ad60338480ce71256715da6f263;hb=HEAD#l347 Mar 31 20:03:07 first try fat, then ext2, then ext4 Mar 31 20:03:28 pali meant: "first it tries..." Mar 31 20:03:29 on which partition? Mar 31 20:03:39 partition is always first Mar 31 20:03:42 see linked code Mar 31 20:04:50 what about ext3? Mar 31 20:05:09 I never really liked the idea to use bootmenu*.d/* for configuring uBoot *.scr Mar 31 20:05:45 ext2 driver should have read support for ext3 Mar 31 20:05:54 DocScrutinizer05: can you provide me an example of config file for that folder? Mar 31 20:05:59 bootmenu.img.d Mar 31 20:06:04 Pali can Mar 31 20:06:46 bootmenu.scr is uboot boot script (with binary header!) Mar 31 20:06:46 if you missed that: he's maintainer/author of uBoot-N900 Mar 31 20:06:57 uboot can boot only files in uimage format Mar 31 20:07:10 Pali: bootmenu.scr is in MyDocs, not in bootmeny.img.d Mar 31 20:07:21 so boot files (in uimage format) are stored in bootmeny.img.d Mar 31 20:07:28 and referenced by bootmenu.scr Mar 31 20:07:38 ooh, what? Mar 31 20:07:51 uboot cannot boot directly zImage Mar 31 20:08:14 the uImage kernels are stored in /etc/* ? Mar 31 20:08:16 so there is script u-boot-update-bootmenu which take all installed zImages and convert them into uboot format Mar 31 20:08:23 or is uImage a plain ascii file? Mar 31 20:08:30 and then store them into ~/MyDocs/bootmenu.img.d Mar 31 20:08:41 uimage is uboot binary format Mar 31 20:08:58 with kernel or with menu? Mar 31 20:09:17 do not understand last question... Mar 31 20:09:35 what's the typical size of a uimage ? Mar 31 20:09:56 zImage + sizeof(binary_uboot_header) + sizeof(padding) Mar 31 20:10:12 Pali: 1,70 MB Mar 31 20:10:15 so it contains kernel zImage plus some meta info? Mar 31 20:10:19 yes Mar 31 20:10:34 hmmm Mar 31 20:11:04 Pali: I think it's a uImage in my bootmenu.img.d because it appeared there after u-boot-update-menu Mar 31 20:11:18 yes, it should be uimage Mar 31 20:11:28 so where do I place original zImage and how does script u-boot-update-bootmenu find it? Mar 31 20:11:37 ~uboot Mar 31 20:11:38 N900 uBoot is a siamese twin binary [uBoot+stockMaemoKernel] that resides in kernel NAND partition /dev/mtd3 aka "kernel". You can't uninstall it, rather you'll nuke it when you flash/install another kernel like stock maemo kernel or powerkernel. To start other than stock maemo kernel via uBoot, you have to provide the according kernel image files, or http://talk.maemo.org/showthread.php?t=81613 Mar 31 20:11:55 see section "How to create bootmenu entry for U-Boot:" Mar 31 20:12:15 kernel zImage is stored in /opt/boot (or /boot) Mar 31 20:12:38 Pali: I use custom partition sizes. My /home is 4 or 5 GB Mar 31 20:12:41 in /etc/bootmenu.d/ is specified config file for boot menu entry Mar 31 20:13:02 Maybe that's why u-boot can not boot custom kernels? Mar 31 20:13:43 and u-boot-update-bootmenu take configuration from /etc/bootmenu.d/ and generate ~/MyDocs/bootmenu.scr and ~/MyDocs/bootmenu.img.d/ Mar 31 20:14:02 alien2003: partition size does not matter Mar 31 20:14:22 Pali: so what would you recommend me to do with that 'unsupported file system'? I just want to be able to boot NITDroid and Kali Mar 31 20:14:41 you just need to have stored those bootmenu files stored in *first* eMMC parition Mar 31 20:15:04 Pali: MyDocs partition is my first partition Mar 31 20:15:09 and that *first* eMMC partition must be either fat, ext2/3 or ext4 Mar 31 20:15:20 and it's ext3 Mar 31 20:15:20 which filesystem it is? Mar 31 20:15:25 *now* we're talking :-) Mar 31 20:15:40 with vfat it doesn't even show boot menu Mar 31 20:16:04 what do you mean by that? Mar 31 20:16:10 do not show boot menu? Mar 31 20:16:24 if keyboard is open, there always must be bootmenu Mar 31 20:16:28 When I boot phone with opened keyboard slider there is no menu items for custom kernels if I use vfat Mar 31 20:16:57 with vfat there are some problems, when it is incorrectly formatted Mar 31 20:16:58 and with ext3 they appear. But still can not boot Mar 31 20:17:08 try to format it as FAT16 (that could help) Mar 31 20:17:15 My USB is broken :( Mar 31 20:17:54 maybe I should try ext4? or it's a bad idea? Mar 31 20:18:00 dude, you got cochones ;-D Mar 31 20:18:19 I do not see reason why ext3 does not work... Mar 31 20:18:46 and also I don't know how to format as fat16... is it possible to do it directly on my Nokia N900? Mar 31 20:18:51 df -h|pastebinit Mar 31 20:19:01 mkfs.vfat -F 16? Mar 31 20:19:06 cat /proc/mounts|pastebinit Mar 31 20:19:28 or try fat32 (-F 32) Mar 31 20:20:05 you're aware it's pretty risky to format /home ? Mar 31 20:20:16 not /home, but MyDocs Mar 31 20:20:24 aaah, yep Mar 31 20:20:35 http://pastebin.com/htqZEwFV Mar 31 20:21:16 http://pastebin.com/GKzJbszx Mar 31 20:21:59 looking ok: /dev/mmcblk0p1 Mar 31 20:22:43 yep, /dev/mmcblk0p1 /home/user/MyDocs ext3 rw,nosuid,noatime,nodiratime,errors=continue,data=ordered 0 0 Mar 31 20:23:12 I think this is correct Mar 31 20:23:14 ls -l ~/MyDocs/bootmenu.scr Mar 31 20:23:32 $ cat ~/MyDocs/bootmenu.scr Mar 31 20:23:32 ext partition is be better for me than fat anyway Mar 31 20:23:54 http://pastebin.com/zPuZFDfs Mar 31 20:24:19 I leave that to Pali ;-P Mar 31 20:24:36 I'm supposed to understand it but too lazy now Mar 31 20:25:30 there are just 3 entries: attached kernel, kernel-cssu and kernel-power Mar 31 20:25:37 so what is problem? Mar 31 20:25:48 they are not shown in uboot bootmenu? Mar 31 20:26:03 or what is visible in uboot bootmenu? Mar 31 20:26:13 They are shown but when I try to boot kernel-cssu or kernel-power it says "unsupported filesystem" Mar 31 20:26:32 aaaaa, there is problably bug Mar 31 20:26:36 attachboot is ok Mar 31 20:26:42 I see it "setenv mmctype fat" Mar 31 20:26:44 Pali: so any ways to fix it? :) Mar 31 20:26:58 fixing that u-boot-update-bootmenu script... Mar 31 20:27:02 going to look at it Mar 31 20:27:15 Pali: yep... I've seen it. And tried to change to ext3 but it breaks everything at all Mar 31 20:27:24 Pali: thank you Mar 31 20:27:31 ext3 does not exist Mar 31 20:27:38 uboot has just ext2 or ext4 driver Mar 31 20:28:00 I can switch to ext4 Mar 31 20:28:01 but if you change it, you need also regenerate checksum (that binary header) Mar 31 20:28:10 uh oO Mar 31 20:28:12 Should I? Mar 31 20:28:24 I mean tune2fs -j... Mar 31 20:28:37 nah Mar 31 20:28:43 of that bootmenu.scr file Mar 31 20:28:56 wait for Pali fixing it, he's fast Mar 31 20:28:58 :-) Mar 31 20:33:39 alien2003: actually thanks for bringing it up :-) Mar 31 20:36:24 however I wnder why it failed with fat fs on MyDocs for alien2003 Mar 31 20:37:03 alien2003: fix should be in my git repo: https://github.com/pali/u-boot-maemo Mar 31 20:37:12 Pali: thanks Mar 31 20:37:16 download new version of u-boot-update-bootmenu script Mar 31 20:37:20 and try to use it Mar 31 20:37:27 let me know if it works now, or not Mar 31 20:37:56 Pali: really i don't know how to ccompile or install it... Mar 31 20:37:58 Pali: you're a wizard :-) Mar 31 20:38:14 alien2003: download new version of u-boot-update-bootmenu script and try to use it Mar 31 20:38:18 oh thx Mar 31 20:38:20 it is in debian folder Mar 31 20:38:28 u-boot-update-bootmenu is shell script Mar 31 20:39:19 and post output of bootmenu.scr file Mar 31 20:39:24 (before rebooting) Mar 31 20:39:42 for a start copy it into root's ~ and invoke it like ~/u-boot-update-bootmenu Mar 31 20:40:34 Pali: thank you... 5 minutes Mar 31 20:41:22 alien2003: flashing u-boot... I have removed it before Mar 31 20:41:33 as far as I could tell the maemo et.c all sopports ext4 wiht no problems, just the included system wasn't using it by default, or so Mar 31 20:46:29 wooooow... Mar 31 20:46:33 it works! Really! Mar 31 20:46:37 Pali: Thank you very much!!! Mar 31 20:46:58 will the package in repos be updated? Mar 31 20:47:05 so replace system version of that script with new fixed version Mar 31 20:47:18 I will try to update package in extras-devel repository Mar 31 20:48:18 Pali: thank you very much Mar 31 20:48:27 Pali: such a great phone should stay alive! Mar 31 20:48:57 have fun! Mar 31 20:50:05 I have no reasons to buy Android no Mar 31 20:50:06 now* Mar 31 20:50:08 yep Mar 31 20:50:19 btw... Is it possible to run shashlik on Nokia N900? Mar 31 20:51:44 yummy Mar 31 20:51:54 now I'm hungry :p Mar 31 20:53:39 I'd say maybe, but they mention qemu (I guess they use qemu-user in their chroot) Mar 31 20:53:43 Shaslik is an QEMU-based Android emulator Mar 31 20:54:21 I doubt (arm) emulation on our omap3 would be very efficient Mar 31 20:54:35 even with userland (qemu-user) emulation only Mar 31 20:54:43 * DocScrutinizer05 is hungry too now. And shashlik looks promising Mar 31 20:54:56 (I'm not even sure that they only use qemu-user, haven't checked their code) Mar 31 20:55:44 i just went full debian on my home server Mar 31 20:56:43 alien2003: I gather it's for x86 now? Mar 31 20:57:10 Shashlik will then install the app and you’ll be able to launch it from your desktop’s applications menu. Other APKs may or may not work—if an APK has native code, it must support x86 processors and not just ARM processors, or it won’t work. Mar 31 20:57:15 http://www.pcworld.com/article/3040093/android/shashlik-brings-android-apps-to-linux-and-you-can-try-it-today.html Mar 31 20:57:18 hmm Mar 31 20:57:36 why is it that debian supports the sheevaplug but not the n900? :c Mar 31 20:57:40 now that's funny Mar 31 20:58:15 takling cpu architectures, i was wondering why maemo and debian-chroots were setup as armel and not armhf... Mar 31 20:58:32 now seemingly the debian chroot can be done as armhf instead but... wasn't origianlly this way Mar 31 20:58:53 I added post to u-boot thread about that fs problem: http://talk.maemo.org/showthread.php?p=1502566#post1502566 Mar 31 20:58:57 kerio: actually ""they"" do, you can run debian on top of mainline (and loose a few drivers that don't work yet) Mar 31 21:02:21 bencoh: yeah but Mar 31 21:02:27 linux-image-marvell Mar 31 21:02:50 (and then flash-kernel to automatically turn kernel and initrd into uImage and uInitrd) Mar 31 21:04:23 err you are aware we don't have initrd? Mar 31 21:05:06 well, you prolly can mae uBoot bring up initrd Mar 31 21:05:10 make Mar 31 21:06:23 DocScrutinizer05: he's talking about debian Mar 31 21:06:25 not maemo Mar 31 21:08:31 yes, of course Mar 31 21:08:49 I'm however talking about *booting* debian Mar 31 21:09:48 DocScrutinizer05: yeah but i'm talking about the fact that i can just blindly apt-get upgrade and get myself the latest debian kernel with an appropriate initrd, both turned into uboot images Mar 31 21:10:14 but there's no linux-image-rx51 package in debian ._. Mar 31 21:10:20 so? how do you tell NOLO to load the initrd? Mar 31 21:11:11 actually tell NOLO to tell kernel to load the initrd Mar 31 21:11:14 surely i'd just tell NOLO to load uboot Mar 31 21:11:20 no no, the kernel doesn't load initrd Mar 31 21:11:26 see? Mar 31 21:11:31 you need uBoot Mar 31 21:11:38 of course Mar 31 21:12:16 actually it MIGHT be possible to tell even NOLO about cmdline Mar 31 21:13:17 i wasn't even considering the possibility of not having uboot tbh Mar 31 21:13:27 me neither :) Mar 31 21:13:46 it just feels silly relying on NOLO only Mar 31 21:13:49 you asked why N900 isn't supported straight away in debian, right? Mar 31 21:14:13 i didn't say "supported by debian-installer" Mar 31 21:14:26