maemo.org Bugzilla – Bug 7972
Kernel in PR1.1 build-depends on fiasco-gen which is nowhere to be found
Last modified: 2010-02-16 14:09:55 UTC
You need to
before you can comment on or make changes to this bug.
EXACT STEPS LEADING TO PROBLEM:
Attempting to dpkg-buildpackage kernel in PR1.1 SDK
Ability to do so without issue.
Non-existent build dependancy, fiasco-gen.
EXTRA SOFTWARE INSTALLED:
Since there was a statement in
fiasco-gen would be released as a binary would it be possible to put out
fiasco-gen into non-free SDK tools (ideally)?
It is a bit awkward to have an open device and that we can't build the
unmodified kernel package due to this dependancy, so this is a good opportunity
to release the tool as it is needed for building kernels now.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52)
Gecko/20091020 Ubuntu/9.10 (karmic) Firefox/3.5.3
CC'ing Marcell as he's the new owner of Fremantle SDK
I am taking this.
Any progress? I would like to build kernel package with mouse and joystick
support, but without fiasco-gen it is impossible.
There's movement on this bug last I heard, but not sure of when it will be
It is not impossible, just you need to edit the source package to not call
fiasco-gen and things should be fine.
I would like to have a package with fiasco image, that flashes the kernel after
installation on the device.
Are you sure that commenting-out the fiasco-gen call will create such a
(In reply to comment #5)
> I would like to have a package with fiasco image, that flashes the kernel after
> installation on the device.
> Are you sure that commenting-out the fiasco-gen call will create such a
Right, I would have assumed a modules package would be enough for that, and no,
it probably won't.
It's planned to be shipped in the next SDK update.
Would it be possible get the package (or even the sources) already before the
afaik we are still testing the package for external use. It will be released as
The easiest is to release it together with the next SDK update. It shouldn't
take that long. The community has been waiting several years for this little
package to go out, I guess we can afford now just a bit more time to release it
(In reply to comment #9)
> The community has been waiting several years for this little
> package to go out, I guess we can afford now just a bit more time to release it
Well, it's a bit different than a month ago though. With PR1.0 we were able to
build .debs and install them via repos and they would flash the kernel.
Starting with PR1.1 fiasco-gen was required as part of the kernel build
Basically we could build good kernel .debs before and now we can't.
I thought things like this would be *urgently* fixed. It's very disappointing
to see how casually it is all done.
Previously I was building many kernel .debs, including one that wound up
solving why so many Nokia customers were getting bricks. These kernels were
also used by others to do such things as NAT. I was also trying various
patches, using it under Mer to help with development there, etc.
This was 100% halted when I went to build the PR1.1 kernel. I figured it would
be a simple update of the kernel source. But you changed how the kernel image
is packaged as well, and added the fiasco-gen as a build dependency. So now
Now we're told to be patient because we've already waited a long time?
See this gem of a thread were the whole thing sounds like it is about to be
That's from 2008....
Anyway, since PR1.1 I haven't made any kernels for maemo. Yay!
Created an attachment (id=2214) [details]
fiasco-gen binary package
Here is a preview of the fiasco-gen package that will be part of the next SDK
* I built and installed new kernel .debs with the fiasco-gen attached to this
* I was able to do the build fine.
* The install via `apt-get upgrade` *appeared* to work and flash the kernel.
* The kernel boots up.
* It gets to showing the "dots" for awhile, then goes black, then powers off.
I think it's actually not flashing *my* kernel but still booting up the old
one, however. Mine was compiled with framebuffer console, but the kernel that
boots up doesn't show the console.
So there *may* be a problem that it is not flashing the kernel on the device
correctly. I still need to prod further, but I thought I would let you know...
Here is my live kernel scratchbox, fwiw:
thank you Marcell!
I was able to successfully build and flash a custom kernel.
It works flawlessly so far.
I believe I have problems with my .postinst files, so take comment #13 as a
half VERIFY (e.g. you can build with it).
Ok, postinst sorted out, so I can VERIFY that the fiasco-gen attached here
works. I was able to `apt-get upgrade` and install my new kernel fine.
Now where's the ticket to free this critical piece of software? :)
(In reply to comment #16)
> Now where's the ticket to free this critical piece of software? :)
Now you have the binary (thanks Marcell for taking the shortcut), enjoy it!
Carsten is sort of maintaining a list of priorities for opening components. Do
you mind coming back to this topic, say, in few months if you still think it's
Why a few months? Not now?
I wonder how releasing fiasco-gen as binary can be compatible with the GPL
license of the kernel. After all, the GPL requires that whenever you ship a
binary blob of any kind that is a derivative work of a GPL'd source, you need
to provide recipients everything (including build tools) to create that very
same binary blob. Exempt from this are only tools that are "normally
distributed [...] with the major components [...] of the operating system".
fiasco-gen obviously does not fall under this exemption.
Fiasco-gen was published in PR1.1.1 SDK, now in non-free in SDK. Proposing to
Setting to Fixed