[opensuse-arm] Raspberry Pi: might we go to kernel 3.6.x?
Hi all, after Andreas' and Guillaume's great HOWTO, I finally pulled out my raspi over the weekend and played with it. It works pretty well. However, the system is pretty unstable with the 3.1 kernel. I noticed when trying to build ffmpeg from source. Lots of strange errors, from ext4 complaining about delayed allocation to spurios "ENOPERM" when closing temporary files during compilation etc. Also, the raspberrypi-gfx demo/test tools did not work, erroring with messages about "vcihq not connected" in dmesg. Additionally, my 512MB Raspi only had 256MB available, no matter what amount of gpu_mem I put into config.txt. Then I simply grabbed the binary kernel and modules from https://github.com/raspberrypi/linux and new firmware from https://github.com/raspberrypi/firmware and voila -- the little box was running stable. So I took the kernel from devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 and updated the patch set to yesterdays git and changed the configuration to be pretty similar to what is in the "upstream" git. I also updated the firmware package. Both together run very fine for me. I have all RAM available, the test tools work, etc.pp. So maybe it would make sense to use the 3.6.11 kernel as "upstream" Raspberry Pi also does? I created SRs 198076 (raspberrypi-firmware) and 198080 (kernel-raspberrypi) and maybe we should use devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 as the default raspi kernel? Best regards, Stefan -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, ----- Stefan Seyfried <stefan.seyfried@googlemail.com> a écrit :
Hi all,
after Andreas' and Guillaume's great HOWTO, I finally pulled out my raspi over the weekend and played with it.
It works pretty well. However, the system is pretty unstable with the 3.1 kernel. I noticed when trying to build ffmpeg from source. Lots of strange errors, from ext4 complaining about delayed allocation to spurios "ENOPERM" when closing temporary files during compilation etc. Also, the raspberrypi-gfx demo/test tools did not work, erroring with messages about "vcihq not connected" in dmesg.
Additionally, my 512MB Raspi only had 256MB available, no matter what amount of gpu_mem I put into config.txt.
Then I simply grabbed the binary kernel and modules from https://github.com/raspberrypi/linux and new firmware from https://github.com/raspberrypi/firmware and voila -- the little box was running stable.
So I took the kernel from devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 and updated the patch set to yesterdays git and changed the configuration to be pretty similar to what is in the "upstream" git.
Sounds good. :)
I also updated the firmware package.
Both together run very fine for me. I have all RAM available, the test tools work, etc.pp.
So maybe it would make sense to use the 3.6.11 kernel as "upstream" Raspberry Pi also does?
Make sense to me.
I created SRs 198076 (raspberrypi-firmware) and 198080 (kernel-raspberrypi) and maybe we should use devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 as the default raspi kernel?
I accepted your firmware patch but I have not the rigths to accept kernel SR. Thanks for your help. Guillaume
Best regards,
Stefan -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 09.09.2013 21:33, schrieb guillaume.gardet@free.fr:
Hi,
----- Stefan Seyfried <stefan.seyfried@googlemail.com> a écrit :
Hi all,
after Andreas' and Guillaume's great HOWTO, I finally pulled out my raspi over the weekend and played with it.
It works pretty well. However, the system is pretty unstable with the 3.1 kernel. I noticed when trying to build ffmpeg from source. Lots of strange errors, from ext4 complaining about delayed allocation to spurios "ENOPERM" when closing temporary files during compilation etc. Also, the raspberrypi-gfx demo/test tools did not work, erroring with messages about "vcihq not connected" in dmesg.
Additionally, my 512MB Raspi only had 256MB available, no matter what amount of gpu_mem I put into config.txt.
Then I simply grabbed the binary kernel and modules from https://github.com/raspberrypi/linux and new firmware from https://github.com/raspberrypi/firmware and voila -- the little box was running stable.
So I took the kernel from devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 and updated the patch set to yesterdays git and changed the configuration to be pretty similar to what is in the "upstream" git.
Sounds good. :)
I also updated the firmware package.
Both together run very fine for me. I have all RAM available, the test tools work, etc.pp.
So maybe it would make sense to use the 3.6.11 kernel as "upstream" Raspberry Pi also does?
Make sense to me.
I created SRs 198076 (raspberrypi-firmware) and 198080 (kernel-raspberrypi) and maybe we should use devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 as the default raspi kernel?
I accepted your firmware patch but I have not the rigths to accept kernel SR.
Well, if nobody objects, I could just SR it to Contrib:Raspi (without :kernel-3.6 subproject), but I'd wait for comments before doing so :-)
Thanks for your help.
Actually, I sort of promised Alex at the Chemnitz Linux Days in spring that I would try to get openSUSE on Raspi into good shape, but unfortunately got always sidetracked. So helping out now that the hard work is done is the least I can do :-) Best regards, Stefan P.S: I built the kernel in home:seife:ARM so you can take it from there for testing. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
----- Stefan Seyfried <stefan.seyfried@googlemail.com> a écrit :
Am 09.09.2013 21:33, schrieb guillaume.gardet@free.fr:
Hi,
----- Stefan Seyfried <stefan.seyfried@googlemail.com> a écrit :
Hi all,
after Andreas' and Guillaume's great HOWTO, I finally pulled out my raspi over the weekend and played with it.
It works pretty well. However, the system is pretty unstable with the 3.1 kernel. I noticed when trying to build ffmpeg from source. Lots of strange errors, from ext4 complaining about delayed allocation to spurios "ENOPERM" when closing temporary files during compilation etc. Also, the raspberrypi-gfx demo/test tools did not work, erroring with messages about "vcihq not connected" in dmesg.
Additionally, my 512MB Raspi only had 256MB available, no matter what amount of gpu_mem I put into config.txt.
Then I simply grabbed the binary kernel and modules from https://github.com/raspberrypi/linux and new firmware from https://github.com/raspberrypi/firmware and voila -- the little box was running stable.
So I took the kernel from devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 and updated the patch set to yesterdays git and changed the configuration to be pretty similar to what is in the "upstream" git.
Sounds good. :)
I also updated the firmware package.
Both together run very fine for me. I have all RAM available, the test tools work, etc.pp.
So maybe it would make sense to use the 3.6.11 kernel as "upstream" Raspberry Pi also does?
Make sense to me.
I created SRs 198076 (raspberrypi-firmware) and 198080 (kernel-raspberrypi) and maybe we should use devel:ARM:Factory:Contrib:RaspberryPi:kernel-3.6 as the default raspi kernel?
I accepted your firmware patch but I have not the rigths to accept kernel SR.
Well, if nobody objects, I could just SR it to Contrib:Raspi (without :kernel-3.6 subproject), but I'd wait for comments before doing so :-)
If it is accepted to Contrib:RPi, then we could remove :kernel-3.6 subproject
Thanks for your help.
Actually, I sort of promised Alex at the Chemnitz Linux Days in spring that I would try to get openSUSE on Raspi into good shape, but unfortunately got always sidetracked. So helping out now that the hard work is done is the least I can do :-)
Alex, thanks for the recruitment! ;)
Best regards,
Stefan
P.S: I built the kernel in home:seife:ARM so you can take it from there for testing.
Will try it tomorow. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Mon, 9 Sep 2013, guillaume.gardet@free.fr wrote:
I accepted your firmware patch but I have not the rigths to accept kernel SR.
Well, if nobody objects, I could just SR it to Contrib:Raspi (without :kernel-3.6 subproject), but I'd wait for comments before doing so :-)
If it is accepted to Contrib:RPi, then we could remove :kernel-3.6 subproject
Id vote for it. Everything which targets a working installation image is appreciated by me. As the current state does not work yet, you can't really break anything. :-) All these sub-project only make understanding harder. Ciao -- http://www.dstoecker.eu/ (PGP key available) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 09/09/2013 22:16, Dirk Stöcker a écrit :
On Mon, 9 Sep 2013, guillaume.gardet@free.fr wrote:
I accepted your firmware patch but I have not the rigths to accept kernel SR.
Well, if nobody objects, I could just SR it to Contrib:Raspi (without :kernel-3.6 subproject), but I'd wait for comments before doing so :-)
If it is accepted to Contrib:RPi, then we could remove :kernel-3.6 subproject
Id vote for it. Everything which targets a working installation image is appreciated by me. As the current state does not work yet, you can't really break anything. :-)
I just tested it now and it seems to works better indeed. :) Please SR to Contrib:Raspi.
All these sub-project only make understanding harder.
Alex, Dirk, are you ok to remove :kernel-3.6 subproject since all people want to go for 3.6 kernel in Contrib:RPi repo because it fixes lots of bugs? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 10.09.2013 10:40, schrieb Guillaume Gardet:
Hi,
Le 09/09/2013 22:16, Dirk Stöcker a écrit :
On Mon, 9 Sep 2013, guillaume.gardet@free.fr wrote:
I accepted your firmware patch but I have not the rigths to accept kernel SR.
Well, if nobody objects, I could just SR it to Contrib:Raspi (without :kernel-3.6 subproject), but I'd wait for comments before doing so :-)
If it is accepted to Contrib:RPi, then we could remove :kernel-3.6 subproject
Id vote for it. Everything which targets a working installation image is appreciated by me. As the current state does not work yet, you can't really break anything. :-)
I just tested it now and it seems to works better indeed. :)
Please SR to Contrib:Raspi.
Done, request 198207 ...now working on u-boot ;-) -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Dirk Stöcker -
Guillaume Gardet -
guillaume.gardet＠free.fr
-
Stefan Seyfried