**** BEGIN LOGGING AT Thu Mar 30 03:00:02 2017 Mar 30 03:16:40 and maemo6 doesn't use any initrd Mar 30 03:16:56 maemo5 Mar 30 03:17:00 fremantle Mar 30 03:17:26 it still has a initrd partition on NAND which is dead legacy Mar 30 03:17:43 alas too small for a decent ubifs or whatever Mar 30 04:22:08 what is the correct way to clean syslog? I just realized that it has grown to 21mb Mar 30 04:48:09 if you dont need it, you can simply stop syslog, delete file and restart syslog Mar 30 04:48:22 or you can setup logrotate to move/compress it Mar 30 04:48:41 which is preferred way if you arent short on space Mar 30 05:40:12 Wizzup: parazyd: ok Mar 30 07:07:29 bencoh Maxdamantus Thank you. And sorry for the late reply - I had to go to bed. Mar 30 07:16:02 KotCzarny: thx. I suddenly realized what my problem was. I tried stop syslogd isntead os stop sysklogd Mar 30 07:17:38 sos syslog done, ev-1.db (or something) dealt with. Are there any other files which bloat and should be taken care of? Mar 30 07:18:18 you shouldnt really run syslog on device Mar 30 07:20:11 oh? Mar 30 07:20:53 unless you are debugging something, its just unnecessary writes/wakeups Mar 30 07:22:57 im just keeping if incase of hicups :D Mar 30 07:23:17 not that i would understand what it logs... Mar 30 07:23:53 but i can always drop line or two here to get clarification Mar 30 07:31:03 TTF: 1278 minutes TTE: 65535 minutes Mar 30 07:31:03 Fun. Mar 30 07:31:19 is charging? Mar 30 07:31:21 only 21 hours left till it's charged. Mar 30 07:32:13 no internet at home, so going through N900 over WiFi. Mar 30 07:32:53 might get drained faster than charging Mar 30 07:32:58 for some reason g_ether hasn't been working while there's an internet connection over the cellular network. Mar 30 07:34:17 It seems to charging at least on a dedicated power source. Mar 30 07:34:34 # cat /sys/class/power_supply/bq24150a-0/current_limit Mar 30 07:34:34 1800 Mar 30 07:34:54 wouldn't charge off my computer's USB port as usual, don't really want to force it to 2A. Mar 30 07:37:15 maybe try bt instead of wifi? Mar 30 07:38:50 cbf figuring that out. Mar 30 07:39:11 Is there a reason it would use less power? Mar 30 07:39:23 no beacons? Mar 30 07:39:34 It's not in AP mode. Mar 30 07:40:19 oh Mar 30 07:40:49 Maybe wpa_supplicant does something that uses more power than usual, dunno. Mar 30 07:41:13 Meh, doubt it. Mar 30 07:41:14 bt was designed to be slow and low power Mar 30 07:42:01 {C 10. Bluetooth vs. WiFi - Power Consumption: Able to works at longer distances and loaded with high quality security protocols makes Wi-Fi a more power consuming protocol than Bluetooth. Mar 30 07:42:02 I suspect if I combined the typical power drain using a cellular internet connection and a WiFi connection it would probably be similar to what it's using atm Mar 30 07:42:20 maemo just doesn't normally let you do that afai Mar 30 07:42:21 k Mar 30 07:43:39 Yeah, the encryption could be significant. Mar 30 07:43:54 I don't really mind. It's at least not draining overall. Mar 30 07:44:10 * Maxdamantus will disconnect it overnight. Mar 30 07:44:20 as long your powerbrick isbr overheating it should be ok Mar 30 07:44:29 *isn't Mar 30 07:44:43 Well, the N900 won't draw more than 2A from the powerbrick. Mar 30 07:45:02 and the powerbrick thing is meant to provide "100 W" Mar 30 07:45:16 (though not through USB) Mar 30 07:45:36 hehe, then it should be fine. thought you use some phone charger Mar 30 07:50:41 http://www.clearevo.com/ecodroidlink/bluetooth_vs_wifi_on_android_battery_consumption/ Mar 30 07:50:50 and that's while playing the vid Mar 30 07:57:48 so actual savings might be much higher Mar 30 08:00:56 Well, I'd like to look into why g_ether stops working when there's a cellular internet connection sometime. Mar 30 08:01:05 That would probably be the most power-efficient. Mar 30 08:01:40 does the interface go down/deconfigure? Mar 30 08:01:44 No. Mar 30 08:01:54 not pingable? Mar 30 08:02:00 Right. Mar 30 08:02:05 o.O Mar 30 08:02:25 that's definitely weird Mar 30 08:03:15 I'm pretty sure I've used g_ether and gprs0 at the same time before. Mar 30 08:03:27 hmm Mar 30 08:09:28 maybe you have used g_nokia? Mar 30 08:10:05 Have never tried ethernet over g_nokia. Mar 30 08:10:39 Maxdamantus: are you sure it stops working? how do you check it stil/no longer works? Mar 30 08:10:45 * Maxdamantus has had g_ether load instead on boot for at least a year and a half. Mar 30 08:11:08 bencoh: well, I can run ping continuously on either side. Mar 30 08:11:10 and I suppose I should definitely move to g_ether as well, because I suspect there is a bug in g_nokia Mar 30 08:11:52 Maxdamantus: try something else then, because the gprs-related scripts disable icmp answers when enabling the gprs0 interface :) Mar 30 08:11:55 it stops as soon as gprs0 connects, and continues again once it's disconnected. Mar 30 09:49:03 Kind of annoying that it seems to set wlan0 down when connecting gprs0. Mar 30 09:49:08 s/connecting/reconnecting/ Mar 30 09:49:09 Maxdamantus meant: Kind of annoying that it seems to set wlan0 down when reconnecting gprs0. Mar 30 09:50:06 oh, and with the ICMP thing .. I can still ping over wifi when gprs0 is up. Mar 30 09:51:53 er, nvm, the N900 doesn't respond to pings. Mar 30 09:52:18 but when experimenting with g_ether/gprs0 I would've done it both ways. Mar 30 09:52:45 that's why i hate all those network-manager-like thingies Mar 30 09:53:01 they dont count for some weird configs Mar 30 09:54:11 *account Mar 30 09:54:18 maemo keeps the wifi link up when connecting to gprs0 Mar 30 09:54:26 it's just that when gprs0 is connected, it drops wlan0 Mar 30 09:54:39 if you don't manage to connect to gprs0, wlan0 is never brought down Mar 30 10:00:02 hehe Mar 30 10:25:34 Maxdamantus: wpa_supplicant? Mar 30 10:29:04 KotCzarny: i wonder about those results .. sure they aren't also just pushing their product? :) Mar 30 10:29:35 Sicelo: who knows, wanna do a n900 specific benchmark? ;) Mar 30 10:30:08 :) Mar 30 10:32:28 Hello, tonight I got suggestions about the kind of file system which is expected by the flasher to upload an initrd (I am considering a scenario like the one at play with Rescue OS, where one uploads kernel and initrd by the flasher and then boots them). Mar 30 10:32:48 if for some reason someone is forced to use wpa_supplicant on N900, iwconfig wlan0 power on helps to keep battery consumption at normal levels Mar 30 10:33:09 Somebody suggested it should be a ubifs instead of ext3. Mar 30 10:33:15 May anybody confirm this? Mar 30 10:33:45 for initrd it doesnt matter Mar 30 10:34:29 if you plan to make a rootfs that will get flashed on nand, ubifs is strongly recommended Mar 30 10:34:52 Well, I debootstrapped a debian file system and put it on a disk image formatted ext3. Then tried to upload by flasher-3.5 -n -l. It doesn't work. Mar 30 10:35:27 dont remember what -n does Mar 30 10:35:48 Specifies an initrd. According to the help, right? Mar 30 10:35:56 also, make sure fs you use is compiled in the kernel, not as a module Mar 30 10:36:09 i think ext3 is loaded as a module in initrd on maemo Mar 30 10:37:15 But how does rescue OS work? There is a zImage, uploaded by flasher-3.5 -k zImage -l, and an initrd, uploaded by flasher-3.5 -n initrd -l. Mar 30 10:37:34 The former is the kernel, the latter the initrd, right? Mar 30 10:37:44 um Mar 30 10:38:01 last time i checked the line was different? Mar 30 10:38:28 you do all in one line Mar 30 10:38:30 It is flasher-3.5 -k zImage -n initrd -l -b"parameters". Mar 30 10:38:39 yes, but in one line Mar 30 10:38:53 also, rescueos uses its own kernel, not the maemo one Mar 30 10:39:01 But this does not work either with the initrd I prepared for Debian. Mar 30 10:39:01 which kernel are you using? Mar 30 10:39:35 I am using a Linux kernel from the mainline. There is one for the N900. But the problem is not the kernel, it's the flasher, which is unable to recognise the format of the initrd. Mar 30 10:39:48 (I think.) Mar 30 10:39:53 and keep in mind there might be feature incompatibilities, 2.6.28 and ext2/3 in it might be too old for the initrd you prepare in debian Mar 30 10:40:01 Sorry, lunch ready. Will be back. Mar 30 10:57:27 23:32:48 < Sicelo> if for some reason someone is forced to use wpa_supplicant on N900, iwconfig wlan0 power on helps to keep battery consumption at normal levels Mar 30 10:57:46 I'm using wpa_supplicant because the normal network manager doesn't let you connect both gprs0 and wlan0 at the same time. Mar 30 10:58:20 So I'll just connect gprs0 the normal way (through the GUI) then run wpa_supplicant myself. Mar 30 10:59:09 then I can just route traffic from my normal computer through the N900 by adding a default route referring to its wlan0 address. Mar 30 10:59:31 (having enabled ipv4 forwarding and NAT from wlan0 to gprs0) Mar 30 11:06:16 Where is the wpa_supplicant functionality in maemo btw? is it directly inside icd2? Mar 30 11:07:01 * Maxdamantus wonders if it just has a copy of a portion of the wpa_supplicant code in it. Mar 30 11:30:59 23:33:11 < Enrico_Menotti_> Somebody suggested it should be a ubifs instead of ext3. Mar 30 11:31:23 The ubifs is for the root filesystem if you're putting it on NAND (which is what flasher does) Mar 30 11:32:47 tbh, don't bother trying to put Debian on NAND. Mar 30 11:33:05 just put it on a normal filesystem on eMMC or an SD card. Mar 30 11:33:36 NAND is only 256 MiB. The smallness is the reason for maemo's optification stuff. Mar 30 11:34:56 Enrico_Menotti_: don't bother thinking about "flashing" Debian. Mar 30 11:35:35 Enrico_Menotti_: just flash u-boot and have u-boot load your Debian kernel and initrd and set the commandline. Mar 30 11:38:01 I was trying to test the whole thing without flashing anything. The flasher is also able to upload and boot kernel and initrd. This is how Rescue OS works. But I don't understand which format it expects for the initrd. Mar 30 11:38:32 Maxdamantus: Sorry for the "somebody". I did not remember who said that, if you or somebody else... Mar 30 11:38:36 But you're not going to put an entire Debian installation in an initrd. Mar 30 11:39:13 Isn't that possible just for testing? Mar 30 11:39:28 It's not really practical due to the likely size. Mar 30 11:39:53 But so what should I put in the initrd? And with what format? Mar 30 11:40:53 The modules required by the kernel you're using to mount the root filesystem. Mar 30 11:41:29 and some scripts/programs to actually do that mount then pivot_root/switch_root and chroot into it. Mar 30 11:42:13 I think that's pretty much what Debian provides for you when you tell it to build an initrd. Mar 30 11:43:09 you still need to have the actual root filesystem somewhere (preferably not on NAND, again because of size limitations), and the command line passed to the kernel from the bootloader should point to that. Mar 30 11:43:39 (the Debian initrd will probably parse the contents of /proc/commandline to figure out what to mount) Mar 30 11:44:15 Ok, I understand, but still don't understand the format for the initrd image, in order to upload it with the flasher. Mar 30 11:44:28 Personally, I pretty much just do all the stuff the initrd would normally do just from NAND. Mar 30 11:44:59 so my NAND has modules for a bunch of kernels and some scripts that can continue booting into maemo or debian. Mar 30 11:45:39 (both maemo's and debian's roots are just directories in a single partition on the eMMC) Mar 30 11:47:15 The initrd image should probably be the output of something like `cpio -o -H newc | gzip -9` or whatever it is. Mar 30 11:48:03 It could be an ext3 image if you know the kernel has ext3 support built-in. Mar 30 11:48:15 nah, thats initramfs Mar 30 11:48:28 initrd is actual dump of fs Mar 30 11:48:39 They're passed in the same way. Mar 30 11:48:46 but they are different Mar 30 11:48:55 Sure, but it's up to Linux to determine that. Mar 30 11:49:13 and i think initramfs only works if you glue it to the kernel Mar 30 11:49:22 glue? Mar 30 11:49:34 You pass in an initramfs in the exact same way you pass in an initrd. Mar 30 11:49:54 last time i've tried it failed, might be some missing uboot wrapping though Mar 30 11:49:54 eg, if you're using grub, you'd use the "initrd" command. Mar 30 11:50:10 or maybe missing -H newc Mar 30 11:51:08 the `-H newc` part is important afaik. I don't think Linux understands the default format produced by cpio. Mar 30 11:51:26 * DocScrutinizer05 runs syslog all the time Mar 30 11:51:44 Maxdamantus: So it is not sufficient to create a disk image with the right formatting and put the file system folders there, right? Mar 30 11:51:44 Vajb: ^^^ Mar 30 11:52:06 he just gave you the command line Mar 30 11:52:10 Vajb: it usually gets logrotated during next reboot Mar 30 11:52:51 Enrico_Menotti_: if you can fit everything in there, it could be sufficient. Mar 30 11:53:01 but actually I maybe should change the log location, move it to uSD to not wear my NAND Mar 30 11:53:28 Maxdamantus: I think I fit everything, but the flasher does not understand the format. Mar 30 11:53:37 Enrico_Menotti_: how big is it? Mar 30 11:54:09 ... don't remember exactly, but I think I created a disk image of about 512 Mb. Mar 30 11:54:14 lol Mar 30 11:54:27 you know it has to be loaded into 256MB of ram? Mar 30 11:54:28 Enrico_Menotti_: that's obviously not going to work since the N900 only has 256 MiB of RAM. Mar 30 11:54:39 and actually half of that Mar 30 11:54:49 because you need ram to run software too? Mar 30 11:54:56 Enrico_Menotti_: and the ramdisks in Linux are even further restricted. Mar 30 11:56:39 Sorry for the noise - did a WHOIS by mistake. Mar 30 11:57:19 Maxdamantus: I quote you: NAND is only 256 MiB. The smallness is the reason for maemo's optification stuff. Mar 30 11:57:32 So the 256 Mb is for the NAND or for the whole RAM? Mar 30 11:57:45 first, dont use 'b' Mar 30 11:57:48 its for bits Mar 30 11:57:52 for bytes use B Mar 30 11:58:28 KotCzarny: Sorry, you're right. My mistake. Mar 30 11:58:31 N900 has 256 MiB of NAND and 256 MiB of RAM. Mar 30 11:58:40 next, ramdisk uses ram and stays in ram unless you move onto different device with pivot_root and unload the ramdisk Mar 30 11:59:07 Enrico_Menotti_: maemo5 doesn't use any initrd Mar 30 12:00:05 KotCzarny: Could you also explain why the "i" in MiB? Sorry... Mar 30 12:00:12 its 1024 vs 1000 Mar 30 12:00:39 MiB = 1048576 B Mar 30 12:00:43 MB = 1000000 B Mar 30 12:00:46 historically megabyte was 1024*1024, for many years though marketing advertised megabyte as 1000*1000 Mar 30 12:00:49 etc Mar 30 12:01:04 MiB should probably be pronounced "mebibyte" Mar 30 12:01:23 MB is "megabyte", since M- is the SI prefix "mega", meaning 1000000 Mar 30 12:01:24 and bootloader will not use it even when you flash an initrd to the NAND partition Mar 30 12:01:28 Ah, I always thought of MB as 1024*1024. Mar 30 12:01:47 Well, various things refer to 1024*1024 as MB Mar 30 12:02:02 but if you're trying to avoid ambiguity, it's probably better to use MiB. Mar 30 12:02:07 Ok. Mar 30 12:02:47 So at this point I think I will put the file system on the sd card. Mar 30 12:02:52 actually initrd is a means to allow platform agnostic kernels to boot and init the system Mar 30 12:03:19 DocScrutinizer05: Ok, I'd just like to understand how Rescue OS works. Mar 30 12:03:38 Enrico_Menotti_: you can practice it easily on pc Mar 30 12:03:45 I only use initrds (well, initramfs if you want to make that distinction) to boot into multi-device btrfs roots. Mar 30 12:03:46 rescueos loads a rootfs and kernel to RAM and then starts it there Mar 30 12:03:47 whole boot linux with initrd Mar 30 12:04:07 much faster and less wear to the device Mar 30 12:04:21 and once you learn the basics you can try on n900 Mar 30 12:05:01 ~rescueos Mar 30 12:05:01 rumour has it, rescueos is http://n900.quitesimple.org/rescueOS/ Mar 30 12:05:44 no initrd involved in rescueOS either, afaik Mar 30 12:05:50 DocScrutinizer05: Yes, but the rootfs is specified to the flasher-3.5 by -n initrd. So what format is it? Mar 30 12:05:53 There is an initrd in rescueOS Mar 30 12:06:01 the entire thing is intended to be loaded as an initrd. Mar 30 12:06:05 no idea Mar 30 12:06:08 ../maemo_flasher-3.5_2.5.2.2/flasher-3.5 -k 2.6.37 -n initrd.img -l -b"rootdelay root=/dev/ram0" Mar 30 12:06:32 Yes, exactly. Mar 30 12:06:34 That's my commandline for loading rescueOS. Mar 30 12:06:47 see http://n900.quitesimple.org/rescueOS/ Mar 30 12:06:49 So what is exactly initrd.img? What kind of image? Mar 30 12:07:18 I guess it's a RAM image Mar 30 12:07:33 Created with that cpio? Mar 30 12:07:34 rescue/initrd.img: Linux Compressed ROM File System data, little endian size 5701632 version #2 sorted_dirs CRC 0x8d9cb614, edition 0, 3083 blocks, 759 files Mar 30 12:08:15 ooh wait, yes, maybe rescueOS actually uses initrd format to let flasher (and bootloader) load the image into RAM Mar 30 12:08:37 Maxdamantus: Thanks. Now how to actually create it? Mar 30 12:09:01 see http://n900.quitesimple.org/rescueOS/ Mar 30 12:09:15 isn't it created there too? Mar 30 12:09:55 Don't know. I can't look right now, since I am at work and our network does not allow opening that page. :( Mar 30 12:10:01 honestly why do you want an initrd image? Mar 30 12:10:25 'no idea but i must talk' Mar 30 12:10:26 I just thought I could try a different OS by using the same method Rescue OS uses. Mar 30 12:10:50 KotCzarny: ? Mar 30 12:10:53 get a kernel with the needed filesystems built monolithic, and forget about initrd Mar 30 12:11:23 Enrico_Menotti_: wasnt for you. but i suggest you to just google some 'linux ramdisk howto or tutorial' Mar 30 12:11:29 I'd really suggest you "try a different OS by using" the uSD Mar 30 12:11:39 and uBoot to boot it Mar 30 12:12:26 you don't want to load your image of the OS to test via flasher on each boot Mar 30 12:12:51 DocScrutinizer05: You think it may ruin the device? Mar 30 12:13:06 https://github.com/NIN101/N900_RescueOS/blob/master/howtocreate https://github.com/NIN101/N900_RescueOS/blob/master/HACKING Mar 30 12:13:14 and creating the thing on uSD is a few magnitudes simpler than packing it into a (size limited) ramdisk Mar 30 12:13:17 NIN101: Welcome! Mar 30 12:13:22 hi Mar 30 12:14:09 Enrico_Menotti_: no, I think you're suffering an XY problem Mar 30 12:14:14 ~xy Mar 30 12:14:15 from memory, xy is The XY problem: You want to do X, but don't know how. You think you can solve it using Y, but don't know how to do that, either. You ask about Y, which is a strange thing to want to do. Just ask about X. http://www.catb.org/~esr/faqs/smart-questions.html#goal Mar 30 12:15:02 :) Mar 30 12:15:22 The fact is that I don't want to extract the sd card continuously from the device and insert it into my computer. Mar 30 12:15:43 I fear to phisically ruin the computer, which would be much worse than ruining the device! Mar 30 12:15:45 why would you? Mar 30 12:16:13 DocScrutinizer05: What, extracting the sd card or ruining the slot in the computer? Mar 30 12:16:15 you can write to uSD in N900, e.g. via scp/sftp Mar 30 12:16:45 Ah, you mean booting maemo and use ssh? Mar 30 12:16:52 yes Mar 30 12:17:03 Ok, yes, didn't think of. Mar 30 12:18:41 let me put it this way: why remove uSD from one PC to insert it into another PC Mar 30 12:20:23 and if you're afraid of ruining your computer, I strongly suggest you use a USB cardreader instead Mar 30 12:22:52 DocScrutinizer05: Yes, I understood. I didn't think about this way to transfer files from my computer to the sd card. (I mean, with ssh.) Mar 30 12:24:29 NIN101: Ok, the kinks you provided are exactly what I was looking for. Many thanks. I will read the howto instructions carefully. Mar 30 12:24:33 *links Mar 30 12:25:19 please understand that rescueOS & initrd are loaded to RAM by flasher and bootloader Mar 30 12:25:30 the will vanish on next power cycle Mar 30 12:26:32 DocScrutinizer05: Yes that's clear to me. Mar 30 12:26:42 you can't flash a initrd to persistent storage Mar 30 12:27:03 No problem - it's just for testing purposes. Mar 30 12:27:06 on N900, without *massive* modifications to bootloader Mar 30 12:28:22 also please understand that RAM size is limiting the size of any such initrd/ramdisk, obviously Mar 30 12:28:53 and the ramdisk in turn is reducing the size of RAM available to the system Mar 30 12:31:02 so e.g. you can only have a 64MB ramdisk if you want to have a 192MB RAM for the system in that ramdisk Mar 30 12:31:40 it's not like N900 has RAM in abundance Mar 30 12:32:26 on uSD otoh your rootfs size is virtually unlimited Mar 30 12:33:10 and you can use ext3 Mar 30 12:33:26 uBoot knows ext3 booting afaik Mar 30 12:33:41 powerkernel too Mar 30 12:46:19 just install uBoot under maemo, and add config files pointing to your stuff on uSD, so on next boot you choose in uBoot menu which of maemo or your own system on uSD you want to boot to Mar 30 12:48:34 depending on cmdline and kernel 'pointer' in uBoot you could even boot maemo's powerkernel from NAND and still have rootfs pointing to uSD Mar 30 13:11:13 win 64 Mar 30 13:11:15 oops. Mar 30 16:25:34 https://duckduckgo.com/country.json maybe useful for anyone requiring geolocation for a maemo application Mar 30 16:26:13 I wonder if they plan to offer more stuff like that Mar 30 17:30:30 Seems my sd card is dead. It is not mounted, neither recognised, from both my Mac and my N900. Does anybody have an idea for checking whether the card is physically dead or it is just a software problem? Mar 30 17:30:49 dmesg Mar 30 17:31:22 I tried it on the Mac. It shows a lot of things - is there anything particular I should look for? Mar 30 17:31:25 if it's inserted and kernel announces it's capacity and reads anything Mar 30 17:31:50 Ok, I will try again. Mar 30 17:32:06 if you nuked partition table it would behave as unformatted with no usable space Mar 30 17:32:49 does n900 have 'initalize/format sdcard' somewhere in settings? Mar 30 17:36:37 Right now the card is in my Mac and I've run dmesg. What if I upload the log on some website, so you may have a look at it? - But I don't want to disturb you too much. Just if you wish to. Mar 30 17:45:19 As far as I can see, nothing in the output references my sd card. Maybe better buy another one. Mar 30 17:45:47 go for samsung evo + or pro Mar 30 17:46:05 avoid nonames/fakes/kingston etc Mar 30 17:46:48 Well, I have here at hand a Mediaworld store. I will take what they have - this one is a SanDisk. Mar 30 17:47:19 Wait, wait, suddendly something happened! I estracted the card and the Mac complains I didn't eject it! Mar 30 17:47:26 Let me try again. Mar 30 17:50:22 I really don't know what happened. Now the card's alive again. I found in my thrash many files, among them the zImage of Rescue OS kernel, and the related initrd.img, and another file I put on the card a few weeks ago. But also many other files. Mar 30 17:50:59 They seem to be other versions of the same files. God knows how they got to the thrash on my Mac. Mar 30 17:51:02 corrupted fs that got fscked? Mar 30 17:51:52 Sorry, what's fscked? Mar 30 17:52:10 fsck == filesystem check util Mar 30 17:52:20 Ok. Mar 30 17:52:42 The strange thing is that now on the card I still find the files I put on it a few weeks ago. Mar 30 17:53:05 But I'm happy it's alive again. I will put it back on the N900 and see what happens. Mar 30 18:16:38 Ok, I had to try a few things. Among them I downloaded a card formatter from sdcard.org, on my Mac. This successfully reformatted the card (my Mac wasn't able to do that with high-level utilities). Now the card's back in the N900 and it seems to work. Mar 30 18:39:08 ohai. got redirected here from #maemo-ssu .. even though it's about installing cssu Mar 30 18:39:25 ~cssu Mar 30 18:39:26 cssu is, like, http://wiki.maemo.org/Community_SSU, or (Community Seamless Software Update) Mar 30 18:40:31 I'm getting a whole bunch of dependency problems on trying to install the cssu update. mostly busybox and modest-'..' localization stuff (and whole bunch of others). not sure how I can install any of these atm. how should I proceed? Mar 30 18:40:57 did you follow steps outlined on the wiki or skipped some of them? Mar 30 18:41:04 I followed the steps Mar 30 18:41:14 from: https://wiki.maemo.org/Community_SSU#Installation Mar 30 18:41:28 sometimes it helps to uninstall offending packages and reinstall them after upgrade Mar 30 18:41:40 really helps saving sanity and time Mar 30 18:42:01 I'm starting from a clean device Mar 30 18:42:14 that is on 21.2011.38-1 Mar 30 18:42:22 with latest power kernel Mar 30 18:42:55 Ok, I am trying to format the sd card on the N900 as ext3. I have rootsh installed. Also openSSH server. I ssh'd to the N900 as root. I think I have a root shell. I tried to issue "mkfs", but it is not found. If I try "sudo mkfs" I get "root is not in sudoers file". I had a look over maemo.org and found something about sudser, but the download from Maemo's application manager does not work. Mar 30 18:43:42 So first: is mkfs a standard tool in Maemo? Mar 30 18:44:00 Enrico_Menotti: type mkfs then press tab two times Mar 30 18:44:10 Ok. Mar 30 18:44:35 Ah, sorry. Mar 30 18:45:18 I was following some instructions over the Internet which probably are not for this version of the OS. Mar 30 18:45:37 Maybe it's time for dinner. Better I think. :) Mar 30 18:45:55 dreamer: try pastebin with your error Mar 30 18:46:09 KotCzarny: eh. how do I do that from the device? Mar 30 18:46:43 this is in the Problems tab in HAM Mar 30 18:46:46 copypaste into file, then curl --upload-file somefile http://transfer.sh Mar 30 18:46:55 you can't select any text in HAM Mar 30 18:47:10 no 'save log' button? Mar 30 18:47:21 no Mar 30 18:47:37 'Application packages missing:' and then a shitload of stuff Mar 30 18:48:08 maybe you need old nokia mirrors, what are the missing packages? name few of them Mar 30 18:49:19 KotCzarny: I added those mirrors already Mar 30 18:49:20 or make a screenshot, i think it was shift-fn-s or something Mar 30 18:49:46 ctrl-shift-p Mar 30 18:50:02 ok Mar 30 18:50:04 I'll try :) Mar 30 18:51:01 it gets saved in mydocs/.images/screenshots (or n900/images/screenshots in file browser) Mar 30 18:51:03 among the packages: busybox, modest-* stuff, osso-* stuff, upstart, system-services, and some other random things Mar 30 18:52:49 btw. you didnt enable extras-testing or extras-devel, did you? Mar 30 18:56:22 KotCzarny: http://imgur.com/a/JvKhE Mar 30 18:56:26 KotCzarny: nope Mar 30 18:56:48 just the nokia mirrors Mar 30 19:01:30 weird Mar 30 19:02:10 as a workaround, try installing plain cssu first? Mar 30 19:02:27 how do you mean? Mar 30 19:02:40 because you are trying to install cssu-thumb Mar 30 19:02:49 install cssu-stable Mar 30 19:03:03 I think that's the default now. I just clicked on the stable link from the maemo browser: https://wiki.maemo.org/Community_SSU Mar 30 19:03:09 "Stable_one-click-install" Mar 30 19:03:20 http://i.imgur.com/aA4esju.png Mar 30 19:03:28 clearly states you are installing cssu-thumb Mar 30 19:03:38 sure, but I clearly just pressed this one button Mar 30 19:03:45 like I said: maybe this is the default now? Mar 30 19:04:06 I have no idea. I didn't specify the thumb version anywhere Mar 30 19:04:31 huh Mar 30 19:04:52 like I said, I just pressed the 'Stable_one-click-install' link. nothing else Mar 30 19:04:57 http://repository.maemo.org/community/community-fremantle.install this says plain cssu Mar 30 19:05:10 unless someone messed something Mar 30 19:05:52 but as i've said, package manager says you are installing cssu-thumb )which isnt bad idea in itself) Mar 30 19:05:53 I have no idea man Mar 30 19:06:03 maybe I should start from scratch >_< Mar 30 19:06:24 (although seriously. this is a completely scratch installation from today) Mar 30 19:06:25 what does apt-cache policy community-ssu-enabler Mar 30 19:06:27 say? Mar 30 19:07:25 looks like 0.7-5-thumb0 is selected (with *** in front) Mar 30 19:07:39 but what repo it points to Mar 30 19:07:42 that's the one that is installed Mar 30 19:07:51 maemo.merlin1991.at Mar 30 19:12:00 since you are not far in the install, i would suggest you reflashing and repeating. because it really looks like something misconfigured Mar 30 19:12:22 and cssu enabler in stable repo isnt changed since june 2016 Mar 30 19:13:21 though.. Mar 30 19:14:47 and that busybox dependency is solved in cssu-testing Mar 30 19:14:55 so are you sure you didnt click them all? Mar 30 19:42:19 KotCzarny: all? no sure it was just testing Mar 30 19:42:22 but yeah I'll reflash :/ Mar 30 19:42:32 you can also just reclick the banner Mar 30 19:42:45 for a quick test (cssu-stable one) Mar 30 19:42:56 no, that didn't work, because it's already installed Mar 30 19:43:13 and it's no longer in the app-menu either Mar 30 19:43:16 its not, you have cssu-thumb enabler installed Mar 30 19:43:31 well I'm telling you it didn't work Mar 30 19:43:35 it said it was already installed Mar 30 19:43:36 mkay Mar 30 19:44:02 you might also wait for cssu guys to show up too Mar 30 19:44:12 if you dont want to reflash Mar 30 19:45:22 already reflashing :P Mar 30 19:45:53 although now I'm not sure which one to use. I have 2 .bin files: RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin and AE98ED9D_RX-51_2009SE_10.2010.13-2.CENTRAL-EUROPE_PR_EMMC_MR0_ARM.bin Mar 30 19:46:26 ~flashing Mar 30 19:46:26 maemo-flashing is probably http://wiki.maemo.org/Updating_the_tablet_firmware, or - on linux PC - download&extract http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz, cd into it, do sudo ./flash-it-all.sh; or see ~flashing-cmdline, or see ~lazyflashing Mar 30 19:47:14 those links are pretty useless Mar 30 19:47:18 see the tgz+sudo line Mar 30 19:47:33 http://maemo.cloud-7.de/maemo5/patches_n_tools/maemo-my-private-workdir.tgz Mar 30 19:47:39 download it and unpack Mar 30 19:47:44 then run the script inside Mar 30 19:47:55 it will download and run what it needs Mar 30 19:48:13 I'm using 0xFFFF Mar 30 19:49:06 then see the script inside to see which files to download and in which order to flash Mar 30 19:49:28 I have the same 'combined' image mentioned in that script Mar 30 19:51:20 ok, flashed Mar 30 19:51:40 will go through installing the nokia mirrors again Mar 30 19:52:31 try writing somewhere what exactly you do Mar 30 19:52:33 in steps Mar 30 19:52:39 in some .txt file Mar 30 19:52:53 :) Mar 30 19:59:35 oh, I now see bunch of updates in HAM. weren't there before Mar 30 19:59:57 will run those first before moving to cssu Mar 30 20:00:05 yes Mar 30 20:00:21 oh. bunch of conflicts there Mar 30 20:00:50 libqt4 stuff Mar 30 20:01:31 what needs it? Mar 30 20:01:52 everything conflicting with everything Mar 30 20:02:10 what did you do before that? Mar 30 20:02:42 install the stable cssu Mar 30 20:02:48 just the repos and enabler package Mar 30 20:03:36 trying the cssu install again Mar 30 20:03:44 doesn't give the same b0rk as before though Mar 30 20:03:56 maybe I used that other .bin I had to flash it Mar 30 20:05:10 ok it's installing cssu Mar 30 20:05:20 maybe those qt dependencies are coming from there Mar 30 20:06:37 ham in stock is slow, so it might be that you didnt wait for updates to show up Mar 30 20:07:06 no I think they where there Mar 30 20:07:18 my dependency issues where with busybox and other stuff right Mar 30 20:07:21 nothing libqt Mar 30 20:08:12 as i've said, it looked like you've clicked on cssu-thumb before Mar 30 20:08:27 there is no cssu-thumb on that page Mar 30 20:08:32 STABLE was the one I clicked on Mar 30 20:08:43 there is only 'stable' or 'testing' Mar 30 20:08:46 no 'thumb' Mar 30 20:08:50 ok, it rebooted Mar 30 20:08:54 *fingers crossed* Mar 30 20:09:55 ok, no updates now. so cssu must've taken care of the qt stuff Mar 30 20:10:07 ok. I think it's good now. will proceed with power kernel and my backup Mar 30 20:10:16 i still recommend you to install cssu-thumb Mar 30 20:10:36 it frees few megs of ram in the system Mar 30 20:10:36 it's supposed to be smaller/faster/better/stronger right? Mar 30 20:10:46 smaller, yes Mar 30 20:10:54 and faster becuase of less swapping Mar 30 20:11:26 ah, but it's based on testing Mar 30 20:11:43 and patches the kernel. should I wait installing the powerkernel? or it comes with its own power-kernel? Mar 30 20:11:57 I vaguely remember the thumb install not giving that many improvements Mar 30 20:12:01 in my experience Mar 30 20:12:11 I can always move to thumb later right? Mar 30 20:12:16 yup Mar 30 20:12:43 yeah atm I just need this thing functional :) Mar 30 20:33:09 KotCzarny: ok just ran updates. and now it wants to install cssu thumb .. Mar 30 20:33:23 and all that qt stuff again Mar 30 20:33:49 hmmm. I'm not guessing something: that my backup contains these packages in the list Mar 30 20:33:54 so it wants to install them from there Mar 30 20:33:55 derp Mar 30 20:34:04 ok how to curate this list .. Mar 30 20:35:17 and more importantly: how to get rid of this stuff Mar 30 20:43:16 i also never really saw much improvement with thumb on my device, but i'm happy with it nonetheless Mar 30 20:43:29 Ehm... sorry, I'd need some more help. I'm trying to copy the Debian system image over the sd card, but I get errors about cp being unable to create symlinks. Mar 30 20:48:49 heuhm. unable to install catorize. no clue why .. Mar 30 21:29:22 ah, needed package liblocale-gettext-perl Mar 30 21:30:54 ok only thing missing now is a battery monitor. no idea which one I was using before hehe Mar 30 21:32:43 bme not good enough? Mar 30 21:35:58 what's a bme? Mar 30 21:37:15 thing is I don't remember what I was using before :) Mar 30 21:37:34 ah I think it was advanced power Mar 30 23:51:14 46MB el-v1.db and going. Unfortunately, at times it doesn't save events, like calls or SMS or IM. Could probably be a race condition somewhere, especially if large size of database means that the time to save it upon adding an Event is long enough to prevent writing of another Event to the same database. Don't know how it works. Mar 30 23:53:00 Or it could be a race between messaging-ui and call-ui, if there are two processes competing for the database. **** ENDING LOGGING AT Fri Mar 31 03:00:01 2017