Notices


Reply
Thread Tools
Community Council | Posts: 3,986 | Thanked: 9,418 times | Joined on May 2012 @ Southerrn Finland
#1341
Originally Posted by marmistrz View Post
Originally Posted by juiceme View Post
How far do you get, I assume debian starts to at least some extent?
The kernel you are using, did you compile it yourself with all the patches needed to make it work on N9?
That was installed from the repo. 4.9 should have the most needed patches
http://elinux.org/N950

The patches for display were not merged yet, though.
Ooh, I was not aware such a recent kernel has been fixed to work with N9(50)... Maybe I need to try that myself.

How's the init system in your kernel; is it expecting to use systemd or sysvinit? As I presume you are taking some arm debian disk image and integrating that with the elinux kernel?


Originally Posted by marmistrz View Post
Originally Posted by juiceme View Post
Easiest is to enable serial console and connect to N9's serial port with minicom; that is pretty much foolproof. Same way you will get kernel logs visible while the device is booting.
and without unscrewing the device? I'm a little afraid I'll break my N950.
I don't know about N950 (since I only ever was allowed once to hold @eekkelund's device in my hands for about a minute ) but in N9 the access to serial port is through the simtray, there is no need to open the device for that

Any other way to access the device requires you to have a daemon running in it, which basically means your userland needs to start.
For debugging init problems this is not the optimal strategy

[OK, yes there are other ways of course, you could build serial-emulation-for-usb in your kernel, or route kernel logging to audio port or modulate the status led with it... however you probably don't want to know about those methods]
 

The Following 2 Users Say Thank You to juiceme For This Useful Post:
Community Council | Posts: 329 | Thanked: 1,949 times | Joined on Oct 2013 @ Fin
#1342
If I am correct the serial port is accessed via 3.5mm headphone plug in N950. So there wouldn't be need to tear phone apart(maybe). But somebody needs to comfirm this.
__________________
Joined first time.. 09-08-12.
tIDE - transportable IDE - app to make apps for SFOS - winner of Maemo Coding Competition 2016-2017 "Something new" category
 

The Following 2 Users Say Thank You to eekkelund For This Useful Post:
Posts: 3,217 | Thanked: 4,064 times | Joined on May 2011 @ Poland
#1343
I have journalctl installed, so I think I have the full right to assume it's systemd.

My steps were:
1. Create a partition, setup ubiboot
2. Mount the partition from the ubiboot rescue, follow this guide:
http://blog.lazy-evaluation.net/post...bootstrap.html
3. install the kernel package linux-image-armmp

That's the normal upstream kernel, as provided by Debian.

I guess I have no serial cable...
__________________
If you want to support my work, you can donate by PayPal or Flattr

Current project:
Porting SailfishOS onto OnePlus 3

Projects no longer actively developed: here
 

The Following 2 Users Say Thank You to marmistrz For This Useful Post:
Community Council | Posts: 3,986 | Thanked: 9,418 times | Joined on May 2012 @ Southerrn Finland
#1344
What I meant; what is the debian rootfs you installed to your mmcblk0p4 partition?
When your kernel boots does it find all it needs on the rootfs?

And you still did not answer; how far does the boot go, do you see anything at all on your device screen after ubiboot hands the execution to the debian kernel?

And another thing; have you checked that the debian kernel handles the CPU L2 cache initialization correctly? (See the section 4. of ubiboot README file...)
 
Posts: 3,217 | Thanked: 4,064 times | Joined on May 2011 @ Poland
#1345
[QUOTE=juiceme;1532806]What I meant; what is the debian rootfs you installed to your mmcblk0p4 partition?
When your kernel boots does it find all it needs on the rootfs?[/code]
I created an empty ext4 partition and bootstrapped latest Debian Stretch onto it using `debootstrap`.


Originally Posted by juiceme View Post
And you still did not answer; how far does the boot go, do you see anything at all on your device screen after ubiboot hands the execution to the debian kernel?
I don't know. I have no journal logs in /var/log, even though I use persistent storage mode in journald.conf


Originally Posted by juiceme View Post
And another thing; have you checked that the debian kernel handles the CPU L2 cache initialization correctly? (See the section 4. of ubiboot README file...)
How can I check it?

Here's my kernel config, I don't really know what to look for: https://pastebin.com/1T9DBbbb

Maybe the problem is that I didn't append the device tree part manually?
__________________
If you want to support my work, you can donate by PayPal or Flattr

Current project:
Porting SailfishOS onto OnePlus 3

Projects no longer actively developed: here

Last edited by marmistrz; 2017-08-18 at 17:06.
 

The Following User Says Thank You to marmistrz For This Useful Post:
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 04:44.