maemo.org - Talk
Page 3 of 14 12 3 4513 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)
-   -   The N9/N950 Kernel Upstreaming Force (https://talk.maemo.org/showthread.php?t=95966)

filip.pz 2015-09-20 10:25
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by wicket (Post 1483061)
It looks like switch_root is being called with incompatible arguments, probably due to the previous mount errors.

Make sure you have CONFIG_BLK_DEV_LOOP enabled. That should hopefully fix the /dev/loop0 errors.
CONFIG_BLK_DEV_LOOP is set to y.

Here's boot with 4.3.0-rc1: http://pastie.org/pastes/10433203
Seems that mmc driver is having some DMA trouble:
omap_hsmmc 480b4000.mmc: unable to obtain RX DMA engine channel 3230369304

I'm guessing that needs to be taken care of first of all.

filip.pz 2015-09-20 11:19
Re: The N9/N950 Kernel Upstreaming Force
 
OK, mmc issue sorted out by adding
CONFIG_DMADEVICES=y
CONFIG_DMA_OMAP=y

This time Nemo does get started, but dies soon after (http://pastie.org/10433263). I guess watchdog shuts it off before DSME is able to start and prevent that.

Anyway - I now have a working serial console cable, and we have kernel that kinda boots. I hope to make some more progress in the following days (time permitting).

marmistrz 2015-09-20 13:55
Re: The N9/N950 Kernel Upstreaming Force
 
The first error I noticed was

Code:
mount: mounting /dev/mmcblk0p1 on /mnt/base failed: No such file or directory
It seems as though the kernel didn't find the right partition.
Would it be possible to dump the partition table before booting? I can't really do it myself now, but you may post a question on unix.stackexchange.com

filip.pz 2015-09-20 16:42
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by marmistrz (Post 1483092)
The first error I noticed was

Code:
mount: mounting /dev/mmcblk0p1 on /mnt/base failed: No such file or directory
It seems as though the kernel didn't find the right partition.
That problem has been solved, as described in my last post:

Quote:
Originally Posted by filip.pz (Post 1483081)
OK, mmc issue sorted out by adding
CONFIG_DMADEVICES=y
CONFIG_DMA_OMAP=y
Seems that MMC driver works only with DMA enabled.

I've also captured boot of 3.5.3 kernel for reference (http://pastie.org/10433952).

I think that this is the one to solve next:
Code:
watchdog watchdog0: watchdog did not stop!

nieldk 2015-09-20 16:52
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by filip.pz (Post 1483106)
I think that this is the one to solve next:
Code:
watchdog watchdog0: watchdog did not stop!
This is just a warning, that some service didn't stop within a given timeout. You will find that even in normal log iam sure.

filip.pz 2015-09-20 16:55
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by nieldk (Post 1483107)
This is just a warning, that some service didn't stop within a given timeout. You will find that even in normal log iam sure.
It's not present when booting 3.5.3. I'd expect for kernel to kick the watchdog just before init, so it doesn't time out. Seems to me that's just the case here.

nieldk 2015-09-20 17:08
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by filip.pz (Post 1483108)
It's not present when booting 3.5.3. I'd expect for kernel to kick the watchdog just before init, so it doesn't time out. Seems to me that just the case here.
Possibly its related to the systemd errors. While annoying, I don't think its a stopper.

But, what about the unknown partition table listed?

Code:
213  2.520324  mmcblk0boot1: unknown partition table

filip.pz 2015-09-20 17:20
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by nieldk (Post 1483109)
Possibly its related to the systemd errors. While annoying, I don't think its a stopper.
This seems to be related:
https://github.com/filippz/kernel-ad...030_wdt.c#L235
I'll try to implement this into new kernel and see

wicket 2015-09-20 19:05
Re: The N9/N950 Kernel Upstreaming Force
 
The N900 which also uses twl4030_wdt, doesn't need that hack. Check that you are not doing anything differently. Here's the latest N900 config file which you might find useful for reference given the hardware similarities:

https://github.com/pali/linux-n900/b...rx51_defconfig

filip.pz 2015-09-20 19:13
Re: The N9/N950 Kernel Upstreaming Force
 
Quote:
Originally Posted by wicket (Post 1483122)
The N900 which also uses twl4030_wdt, doesn't need that hack. Check that you are not doing anything differently.
In fact N9 uses TWL5031, but the driver is the same. Both 2.6 and 3.5 had some kind of WD hacks:
https://github.com/filippz/kernel-ad...030_wdt_hack.c
https://github.com/filippz/kernel-ad...514acf4db038b0

The one from 3.5.3 seem to help a bit, ie boots a bit further.

Quote:
Originally Posted by wicket (Post 1483122)
Here's the latest N900 config file which you might find useful for reference given the hardware similarities:

https://github.com/pali/linux-n900/b...rx51_defconfig
Only difference I see is that CONFIG_OMAP_WATCHDOG and CONFIG_TWL4030_WATCHDOG are set to m whereas I used y. I'll retest with that, but not until tomorrow.


All times are GMT. The time now is 20:24.
Page 3 of 14 12 3 4513 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8