**** BEGIN LOGGING AT Sat Apr 08 03:00:02 2017 Apr 08 09:48:28 I am sure I used mainline kernel. rx51_defconfig from Pali's repository at github. Compiles, but doesn't boot. I didn't get how to use the n900.config from parazyd. Now I'll try cloning Pali's repository and using that. Maybe I'm doing something wrong in the build process. Apr 08 09:48:43 you probably are Apr 08 09:48:56 what toolchain are you using and where are you compiling? Apr 08 09:49:10 I'm compiling on Debian. Apr 08 09:49:28 I'm using the arm-linux-gnueabihf toolchain. Apr 08 09:49:47 and what's your make command? Apr 08 09:50:28 make rx51_defconfig and then make zImage (with or without the -j4 option). Apr 08 09:50:32 By the way, how to use the n900.config? Apr 08 09:50:45 you just put it in the root of the sources Apr 08 09:50:50 name it ".config" Apr 08 09:50:55 Ah, ok. Apr 08 09:51:02 So no make n900.config. Apr 08 09:51:28 just copy it to .config Apr 08 09:51:28 I will try with that. Apr 08 09:52:12 then a `make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- zImage modules omap3-n900.dtb` should do the trick Apr 08 09:52:53 when done: cat arch/arm/boot/zImage arch/arm/boot/dts/omap3-n900.dtb > zImage Apr 08 09:52:58 ^^ that's your kernel Apr 08 09:53:20 you also need to install the according kernel modules to the sd card/image you will be using Apr 08 09:54:17 which would be: make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=/path/to/n900/rootfs INSTALL_MOD_STRIP=1 modules_install Apr 08 09:54:43 What's INSTALL_MOD_STRIP? Apr 08 09:54:49 oh, and to make a uImage out of the zImage: mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n zImage -d zImage uImage Apr 08 09:55:04 Ok, I'm not using u-boot. Apr 08 09:55:07 Enrico_Menotti: it strips debugging symbols, you may or may not want that Apr 08 09:55:40 Ok. So maybe my problem is that I was missing the dtb. Apr 08 09:55:48 and after the modules_install, i also do a firmware_install in the same manner Apr 08 09:58:04 What does the firmware_install do? Apr 08 10:09:12 Ok, I was actually missing the dtb. Now signs of life. (The kernel boots and it's a bit verbose). Apr 08 10:09:25 Now I will try to boot the file system. Apr 08 10:28:12 I tried to boot the Devuan image I had already booted on Sunday. It says, as it did on Sunday, that it can't mount selinuxfs. But on Sunday after a while I got a prompt. Now it's rebooting. Maybe the kernel I compiled does not match that system image. Apr 08 10:35:22 should i buy another microsd Apr 08 10:35:33 there's pretty good ones for cheap nowadays Apr 08 11:22:22 Enrico_Menotti: did you compile and append dtb? Apr 08 11:22:49 Yes, I did. Apr 08 11:23:02 ah, just saw it in the backscroll Apr 08 11:23:20 you have to copy modules to /lib/modules as well Apr 08 11:23:32 Or install them by make? Apr 08 11:24:21 after installing with make, copy the resulting directory Apr 08 11:24:49 Ah ok. Right. Apr 08 11:25:00 or yeah, use what parazyd toldya Apr 08 11:26:17 Now my problem is: the file system I have for Devuan is ext4, so I can't mount it. I am thinking about trying with the Debian fs which I had debootstrapped some days ago. I already used dd to put it on sd card. Apr 08 11:27:11 Now I was trying to let Maemo detect the changes in the sd card partition tables without opening the back cover. I found there is a "partprobe" command, but for that I need to install "parted". Is this available for maemo? Apr 08 11:27:26 Enrico_Menotti: doesn't the PC you build on have USB ports? Apr 08 11:28:17 Yes, usb. Are you thinking about going to mass storage mode, etc.? Apr 08 11:28:33 yes Apr 08 11:28:43 Ok, that's another option. Apr 08 11:28:53 But anyway, is there parted for Maemo? Apr 08 11:29:01 no idea Apr 08 11:29:38 there is sfdisk, I think you can command it to re-read partition table Apr 08 11:29:58 Ok, let me check. Apr 08 11:38:19 sfdisk -R Apr 08 11:38:22 This works. Apr 08 11:45:15 I can't believe. I have a prompt from Debian. It's very unstable - after a while it reboots. But I am already quite happy. Apr 08 12:14:57 there are a few watchdogs to tickle Apr 08 12:16:54 others wake (silly!!), kick (ouch!) or pet them Apr 08 12:35:14 These watchdogs are in the modules, right? Apr 08 12:39:56 Hmmm Apr 08 13:36:22 modules? Apr 08 13:37:01 I think one is a software watchdog in CPU, one is in TWL4030 companion chip, and one is in modem Apr 08 13:37:21 I'm speculating here Apr 08 13:52:51 Anyway, I built and installed modules, and now the login is stable. However, I don't know username and password... I will look into the file system. :) Apr 08 14:09:49 I am unable to login. It doesn't accept "root" as a username. It accepts both "user" and "debian", but I don't know the passwords. Also, in /etc/passwd in the rootfs "root" is listed but "user" and "debian" not. ??? Apr 08 15:03:11 Enrico_Menotti: devuan? uses 'root' and 'toor' as pass Apr 08 15:16:52 Not Devuan, Debian. From the /etc/passwd file, seems only root is enabled as a user. But if I try with "root" as username, I'm not even allowed to enter a password. Apr 08 15:34:57 Enrico_Menotti: root is by default passwordless you need to change its password Apr 08 15:35:30 Wizzup: ^ Apr 08 15:35:41 even in devuan iirc Apr 08 15:41:12 it depends on the installer i think Apr 08 15:41:20 if you don't create a user, you are asked a root password Apr 08 15:48:23 yeah Apr 08 15:48:33 what if no installer? Apr 08 15:48:47 this is similar to skipping oobe in windows Apr 08 15:52:34 init=/bin/sh and passwd? Apr 08 15:52:41 hell, init=/bin/passwd Apr 08 16:03:21 interesting Apr 08 16:11:04 Out Of Body Experience? Apr 08 16:11:14 windoze can do that ? o.O Apr 08 16:14:19 :/ Apr 08 16:21:42 hayyyyy Apr 08 16:53:35 ~#devuan root Apr 08 16:53:44 ~#devuan login Apr 08 16:53:55 ~listkeys #devuan Apr 08 16:53:57 Factoid search of '#devuan' by key (13 of 18): #devuan ml ;; #devuan systemd #DEL# ;; #devuan dng ;; #devuan xy #DEL# ;; #devuan bugtracker ;; #devuan samba ;; #devuan nm ;; #devuan non-systemd versions ;; #devuan beta2 ;; #devuan systemd popularity ;; #devuan mirrors ;; #devuan qemu ;; #devuan attentionchar #DEL#. Apr 08 16:54:13 ~listkeys #devuan Apr 08 16:54:14 Factoid search of '#devuan' by key (13 of 18): #devuan systemd #DEL# ;; #devuan owner ;; #devuan attentionchar #DEL# ;; #devuan samba ;; #devuan beta2 ;; #devuan ml ;; #devuan migrate instructions ;; #devuan network manager ;; #devuan non-systemd versions ;; #devuan dng ;; #devuan raspi login ;; #devuan xy #DEL# ;; #devuan bugtracker. Apr 08 16:54:46 ~#devuan raspi login Apr 08 16:54:46 well, #devuan raspi login is pw toor https://botbot.me/freenode/devuan/2016-05-03/?msg=65351755&page=3 Apr 08 16:55:00 root, toor Apr 08 16:55:08 Enrico_Menotti: Apr 08 16:55:18 Debian, not Devuan. Apr 08 16:55:24 ooh Apr 08 16:55:28 nfc Apr 08 16:55:52 and Wizzup alread had that Apr 08 16:56:06 * DocScrutinizer05 trolls out Apr 08 16:57:42 >> hell, init=/bin/passwd<< smaaaart :-D Apr 08 16:59:01 Ok, it seems root is disabled. If I enter it as username, I get refused. Anyway, I didn't get this init=/bin/passwd. May you explain? Apr 08 16:59:51 in bootloader, replace init=$WHATEVER by init=/bin/passwd Apr 08 17:00:27 don't Apr 08 17:00:31 or by init=/bin/sh if you feel less venturous Apr 08 17:00:32 replace it with init=/bin/sh Apr 08 17:01:01 or perhaps find a thing in your bootloader that says "single user mode" Apr 08 17:01:41 which is basically the same Apr 08 17:02:10 Ok, so if I say init=/bin/sh it should go directly to the shell, right? And what if init=/bin/passwd? Apr 08 17:02:53 then you explore something new that is likely to fail Apr 08 17:03:13 Ah. Apr 08 17:03:21 and you have only one try since passwd isn't meant to accept multi line input Apr 08 17:04:05 init= just tells kernel which program to start as pid1 Apr 08 17:04:24 could be anything Apr 08 17:04:36 even fdisk ;-P Apr 08 17:05:15 though i'm not sure how you pass cmdline parameters/options to that command Apr 08 17:05:36 which might be why passwd fails Apr 08 17:05:58 well, passwd's default behaviour is to set the root password Apr 08 17:06:10 :nod: but I wasn't sure Apr 08 17:06:44 actually the default behavior is to set the $user password Apr 08 17:07:00 afaik Apr 08 17:08:05 kernel environment I'm not sure which is $USER / EUID(), but prolly should be 0/root Apr 08 17:08:53 then you of course want to make sure your root fs is mounted Apr 08 17:09:07 "sh: can't access tty: job control turned off" Apr 08 17:09:12 will prolly fail when this gets done in an initrd, eh? Apr 08 17:09:35 hmm yeah, ouch Apr 08 17:10:13 where is your image? Apr 08 17:10:28 The rootfs? Apr 08 17:10:31 yep Apr 08 17:10:40 sd card Apr 08 17:11:01 so why don't you copy over the etc/paswd from another machine? Apr 08 17:11:50 I had a look at the etc/passwd. Seems there is root, with encrypted password. But Debian doesn't allow me to enter the password. As soon as I enter the user, I get refused. Apr 08 17:11:55 well, razher use passwd command with parameter to point to the uSD etc/passwd Apr 08 17:12:59 ? Apr 08 17:14:50 -R, --root CHROOT_DIR Apr 08 17:14:52 Apply changes in the CHROOT_DIR directory and use the configuration files from the CHROOT_DIR directory. Apr 08 17:16:31 so if there's /mnt/myuSD/etc/passwd the you invoke `passwd -R /mnt/myuSD root` Apr 08 17:18:15 >> Regardless of whether shadow passwords are used, many system administrators use an asterisk (*) in the encrypted password field to make sure that this user can not authenticate him- or herself using a password. (But see NOTES below.)<< Apr 08 17:19:21 are you sure it's not asking for the root password already? *Not* for the username Apr 08 17:19:50 Well, what it says is "login"... Apr 08 17:20:02 hmm yeah, user name Apr 08 17:20:27 If I enter anything different from "root", then asks for a pass, but refuses to log in. Apr 08 17:20:34 it seems pretty weird when it doesn't accept root there Apr 08 17:20:56 I'd think root is disabled. Apr 08 17:22:43 I'd think maybe the shell set for root in passwd is blowing chunks? but also makes no sense since it first had to ask for password Apr 08 17:23:08 maybe PAM or the crypt() lib is defect Apr 08 17:24:09 could you paste the passwd file root record? Apr 08 17:24:40 Yes, but it's simple. There's just an "x" in place of the password. Apr 08 17:25:00 As far as I've been able to find, this means the password is encrypted somewhere else, right? Apr 08 17:25:39 root:x:0:0:root:/root:/bin/bash Apr 08 17:26:44 BWAHAHA Apr 08 17:27:07 yeah, might mean it's in etc/shadow Apr 08 17:27:54 password This is either the encrypted user password, an asterisk (*), or the letter 'x'. (See pwconv(8) for an explanation of 'x'.) Apr 08 17:28:57 Let me have a look at /etc/shadow. Apr 08 17:32:10 root:*:17254:0:99999:7::: Apr 08 17:32:22 Here it is. The "*" means "no login". Apr 08 17:32:53 I will delete the "x" in /etc/passwd. It should allow login without password. Apr 08 17:37:42 really? Apr 08 17:39:32 No doesn't work. I was reading here: https://www.debian.org/doc/manuals/debian-reference/ch04.en.html. There is a table saying "(empty): passwordless account", but doesn't work. I will try to set a password in clean. Apr 08 17:39:53 The pwunconv command creates passwd from passwd and shadow and then removes shadow. Apr 08 17:41:00 Ok. Apr 08 17:44:14 where did the image come from? Apr 08 17:45:43 No way. Still doesn't allow me to insert a passwd. Apr 08 17:45:56 The image has been bootstrapped by me on a Debian system. Apr 08 17:46:14 (Cross-bootstrapped.) Apr 08 17:47:57 you seem to self inflict troubles on yourself Apr 08 17:50:02 KotCzarny Well, my goal is to learn how to build kernel and system image, not just boot them... Apr 08 17:51:29 can you sudo with user? Apr 08 17:52:25 just run with init=/bin/bash and use passwd to set one Apr 08 17:52:33 or clone entry from pc Apr 08 17:52:54 seems he's already done that with no success .. (unless i misread) Apr 08 17:53:12 then he has messed pam probably Apr 08 17:53:33 hmm? Apr 08 17:54:45 or login shells Apr 08 17:58:39 accessing /var/log/messages could help Apr 08 17:59:03 Enrico_Menotti: copy a /etc/passwd and /etc/shadow from your linux PC, make sure the shell (last parameter after last : ) is actually existing in target system, and in /etc/shells Apr 08 18:01:29 I tried to change the username for root. Doesn't work. When I use this new username, it doesn't allow me to enter a password. Looks like root privileges are disabled?!? Apr 08 18:01:30 heck, first time I lost my root password, I edited etc/passwd with a disk editor inder windows (dualboot system) and changed the UID to 0. Worked ;-P Apr 08 18:02:38 root privileges disabled? what the heck are you talking about? Apr 08 18:04:12 In fact - it's just an idea. I mean, it seems whenever I try to login as user "0" of group "0" it refuses it. Apr 08 18:04:37 no, whenever you try to login, it breaks Apr 08 18:05:08 you didn't even try with anything else than UID 0 Apr 08 18:05:19 I will now. Apr 08 18:05:39 Enrico_Menotti: copy a /etc/passwd and /etc/shadow from your linux PC, make sure the shell (last parameter after last : ) is actually existing in target system, and in /etc/shells Apr 08 18:06:15 Ok, a minute. Apr 08 18:06:58 id4eally make it /bin/sh Apr 08 18:07:18 this should always be there and be allowed by etc/shells Apr 08 18:08:02 also check /etc/login.defs Apr 08 18:08:29 and man passwd Apr 08 18:10:50 man login.defs: Apr 08 18:10:53 DEFAULT_HOME (boolean) Apr 08 18:10:55 Indicate if login is allowed if we can't cd to the home directory. Default is no. Apr 08 18:43:01 Ok, copied /etc/passwd and /etc/shadow. I've been able to login as std user. Now I cannot switch to root since I don't have numbers working, and my root password is numeric... Apr 08 18:43:15 ouch Apr 08 18:43:18 what about sudo? Apr 08 18:43:44 Let's try. Apr 08 18:44:30 No, command not found. Probably it's available only to root. May it be? Apr 08 18:44:38 Enrico_Menotti: do not try to change anything related to root. Apr 08 18:44:48 it should be username root with uid 0 Apr 08 18:44:49 period Apr 08 18:45:12 Check /etc/shells, ls /bin Apr 08 18:45:37 Ok, now I'm logging in, the problem is the password for root. Apr 08 18:45:51 Change it in your linux pc then? Apr 08 18:45:53 :/ Apr 08 18:46:15 or get your layout fixed Apr 08 18:46:22 keyboard layout Apr 08 18:46:44 ...which would be the right solution. Apr 08 18:47:06 outside of the system Apr 08 18:47:11 externally* Apr 08 18:47:36 probably you should configure autologin as root Apr 08 18:48:05 So next steps: 1. Turning on the backlight (!). 2. Fix keyboard layout. 3. Allow power button to shutdown (!). Apr 08 18:49:04 for 3: enable power management/acpi/apm? Apr 08 18:50:11 yeah you can do everything without the system running Enrico_Menotti Apr 08 18:50:20 those steps Apr 08 18:51:05 Do you think I have to debootstrap again, or is it possible to modify something in the file system? Apr 08 19:17:19 I'm wondering whether I have some way to install packages to the Debian fs on sd card by connecting in mass storage mode to the Debian computer. (At present my N900, when I boot Debian on it, is isolated from the world, and I cannot even login as root.) Apr 08 19:28:06 wifi should work in debian .. Apr 08 19:35:54 How to turn it on without being root? Apr 08 19:52:11 Enrico_Menotti: Put autologin as root Apr 08 19:52:39 i am sure there's a way to extract and repackage the filesystem Apr 08 19:52:47 and/or mount directly on linux system Apr 08 19:53:38 Well, I can mount it on my Debian computer. Mass storage mode. But how to install packages there? Apr 08 19:54:30 you chroot into it Enrico_Menotti Apr 08 19:54:54 As it is done in debootstrapping, right? Apr 08 19:54:56 seriously please research a bit more or ask common things like this in ##liunx please Apr 08 19:55:00 uhm yeah i guess Apr 08 19:55:07 however it works Apr 08 19:55:52 you dont need /dev except when creating bootloader for example **** ENDING LOGGING AT Sun Apr 09 03:00:01 2017