![]() |
Re: [Announce] kernel-power stable v52 in Extras
@pali
May you consider to have another look at my (and now also akuma's) problem with kp and dsp libs (/etc/modprobe.d/bridgedriver)? http://talk.maemo.org/showthread.php...postcount=1345 I took a look in kp53 modules postinst and saw that you remove there all mentioning of shm_size, but you do not remove the phys_mem_base (introduced with kp52). On purpose? IIRC stock kernel did not start with that config (or better said without shm_mem=0x4000000). What we would have with kp53 is shm_size removed and phys_mem_pool inside (for people upgrading from kp52 to 53). Nothing to consider when only using kp, but when we need/want to u-boot stock kernel: reboot loop. |
Re: [Announce] kernel-power stable v52 in Extras
Original fille /etc/modprobe.d/bridgedriver from package omap3430-dsp-baseimage-ti_0.201007-1+0m5_armel.deb has this content:
Code:
options bridgedriver shm_size=0x400000 phys_mempool_base=0 base_img=/lib/dsp/baseimage.dof So removing any of those two params from /etc/modprobe.d/bridgedriver does not break or change any behaviour of stock kernel. |
Re: [Announce] kernel-power stable v52 in Extras
Okay, would expect that too.
But see the config of akuma (and also also my experience). With this config the stock kernel produced a reboot loop. Bringing back the 0x400000 let stock kernel boot. -- edit BUT as we are the only ones reporting I might fear that it is due to multiboot and its changed preinit? Could not see why (but that could be due to my limited knowledge :rolleyes:). If so I might understand you stop your support here! Are there any other fellows out there willing to try to test above linked config with stock kernel? -- And: it is not critical but just inconvenient (now that I know ;), so ...) |
Re: [Announce] kernel-power stable v52 in Extras
@peterleinchen: when you will be able to boot stock kernel, please run uname -a. Also please post sha1sum of that problematic kernel driver /lib/modules/2.6.28-omap1/bridgedriver.ko
|
Re: [Announce] kernel-power stable v52 in Extras
@freemangordon: can you try to look at stock dridgedriver source code too? to confirm that default shm_size param is 0x400000?
|
Re: [Announce] kernel-power stable v52 in Extras
Will do so (but probably not today).
Ah now I see what you think: bridgedriver.ko got overwritten by installing dsp debs? Okay, post later ... TIA Just remembered some info from akumo about installing cssu-thumb and jist doing the dsp lib thingy (http://talk.maemo.org/showpost.php?p...stcount=1342): Quote:
--temporary info: ~ $ sha1sum temp/kp52/modules/lib/modules/2.6.28.10-power52/bridgedriver.ko /lib/modules/2.6.28.10-power52/bridgedriver.ko f82d6ba811e76ea19783b8ce07ab37d83d0099c9 temp/kp52/modules/lib/modules/2.6.28.10-power52/bridgedriver.ko f82d6ba811e76ea19783b8ce07ab37d83d0099c9 /lib/modules/2.6.28.10-power52/bridgedriver.ko I compared directly against unpacked kp52 modules deb and they are the same. |
Re: [Announce] kernel-power stable v52 in Extras
Quote:
|
Re: [Announce] kernel-power stable v52 in Extras
Strange stranger ...
Now I booted stock kernel with following config: options bridgedriver phys_mempool_base=0 base_img=/lib/dsp/baseimage.dof and ... it booted. :confused: (of course tryinmg to boot stock kernel with 0x500000 failed, was expected) My kp52 with same config booted successful, too. So I will leave that as default. Here is requested info: f82d6ba811e76ea19783b8ce07ab37d83d0099c9 /lib/modules/2.6.28.10-power52/bridgedriver.ko and Linux delite 2.6.28-omap1 #1 PREEMPT Sun Aug 8 09:50:47 BST 2010 armv7l GNU/Linux if you still need. I have no explanation why it now works on my device? And I am sure it did not 9 months ago, as I am not interested in stealing your time. :) But why the hell akumo had the same problem then? |
Re: [Announce] kernel-power stable v52 in Extras
My idea is that multiboot can use older version of kernel...
|
Re: [Announce] kernel-power stable v52 in Extras
Quote:
Do you mean cannot handle? No, multiboot is stone-age, and was created during early times. And did its work for lots of folks using plain stock and nitdroid kernel. |
Re: [Announce] kernel-power stable v52 in Extras
PR1.3 kernel version which is in deb package kernel_2.6.28-20103103+0m5_armel.deb has string:
Code:
Linux version 2.6.28-omap1 (bifh6@) (gcc version 4.2.1) #1 PREEMPT Fri Aug 6 11:50:00 EEST 2010 and same version of zimage which is in that deb package is in PR1.3 and PR1.3.1 fiasco images (RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin and RX-51_2009SE_21.2011.38-1_PR_COMBINED_MR0_ARM.bin) So check that you have that version string in file /proc/version. If not then you not have PR1.3 kernel. With multiboot (which flashing kernel at every boot) I mean that it could use another and maybe old version of stock kernel. |
Re: [Announce] kernel-power stable v52 in Extras
Sir, yes, Sir.
You were right about kernels. Thanks. It really looks like multiboot used an older release in its deb. I never ever thought about that :cool: But both kernels differ but have about the same creation date, so it was not obvious (to me). Fetched pr1.3 kernel image, going to create uImage and test (but need to free some space on rootfs aforehand). Does not yet explain behaviour (or was pr1.2 known to not boot without 0x400000?) and especially why it now worked on my device. But who cares? Thanks, once more! btw: I use u-boot to load kernels and multiboot in second stage confirms. If I like to boot another kernel I boot it with u-boot and select it also in multiboot. This way multiboot does not flash but just uses it. Going back to default use the same procedure and kernel does not get flashed! I have fbcon enabled and can select a shell in multiboot. Quite nice and easy to flash kernel on boot (if really needed). |
Re: [Announce] kernel-power stable v52 in Extras
Hi! after long time kernel-power v53 was relesed! See new thread: http://talk.maemo.org/showthread.php?t=94287
|
All times are GMT. The time now is 07:25. |
vBulletin® Version 3.8.8