4 Jan
2018
4 Jan
'18
5:18 p.m.
Dear LiMers,
I've been recently using the lime-sdk tool (actually, a fork
<https://dev.qmp.cat/projects/qmp-cooker/>) to generate images for a
number of devices
<https://dev.qmp.cat/projects/qmp-cooker/repository/revisions/master/entry/qmp.profiles.conf#L1>.
Overall it's been very successful but, with some of them, I've faced
some trouble.
Take the example of the Alfa N5 outdoor wireless CPE
(target=ar71xx/generic, profile=ALFANX), which has 8 MB of flash (enough
to fit a lot of packages). Once the additional packages are built
(./cooker -b ar71xx/generic --force-local) I cook the image (./cooker -c
ar71xx/generic --profile=ALFANX) but the process fails: the kernel built
locally is too big to fit in the device's partition scheme.
I guess the problem comes from the fact that the SDK builds packages
with some extra options (debug, symbols, etc.) compared to the
Buildroot. Have you experienced this behaviour? Do you have any idea on
how to overcome this? The lime-sdk cooker is a wonderful tool, and it
would be very nice to make it work with all the devices.
Cheers,
Roger
4 Jan
4 Jan
9:08 p.m.
New subject: lime-sdk fails to generate some images (too big kernel size)
Dear Roger,
On 04/01/18 18:18, Roger Pueyo Centelles | Guifi.net wrote:
Dear LiMers,
I've been recently using the lime-sdk tool (actually, a fork
<https://dev.qmp.cat/projects/qmp-cooker/>) to generate images for a
number of devices
<https://dev.qmp.cat/projects/qmp-cooker/repository/revisions/master/entry/qmp.profiles.conf#L1>.
Overall it's been very successful but, with some of them, I've faced
some trouble.
Take the example of the Alfa N5 outdoor wireless CPE
(target=ar71xx/generic, profile=ALFANX), which has 8 MB of flash
(enough to fit a lot of packages). Once the additional packages are
built (./cooker -b ar71xx/generic --force-local) I cook the image
(./cooker -c ar71xx/generic --profile=ALFANX) but the process fails:
the kernel built locally is too big to fit in the device's partition
scheme.
I guess the problem comes from the fact that the SDK builds packages
with some extra options (debug, symbols, etc.) compared to the
Buildroot. Have you experienced this behaviour? Do you have any idea
on how to overcome this? The lime-sdk cooker is a wonderful tool, and
it would be very nice to make it work with all the devices.
Actually the Kernel is not built but comes with the LEDE-SDK. This is in
one side a feature (because we use the same Kernel as official LEDE
release so we can use the same Kmods and stuff) but in the other side
the Kernel image cannot be modified, so there are some options for
reducing space which cannot be enabled.
Look at the libremesh flavors, what we do to reduce space is, for
instance, to change hostapd-mini for wpad-mini.
Apart from these tricks there is nothing more that you can do.
Cheers.
Cheers,
Roger
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
10:13 p.m.
New subject: lime-sdk fails to generate some images (too big kernel size)
On Thu, Jan 04, 2018 at 10:08:19PM +0100, pau wrote:
Dear Roger,
On 04/01/18 18:18, Roger Pueyo Centelles | Guifi.net wrote:
What you meant is actually the other way around:
hostapd-mini (AP-mode) + wpa_supplicant-mini (STA-mode) = wpad-mini
hence hostapd-mini < wpad-mini
Dear LiMers,
I've been recently using the lime-sdk tool (actually, a fork
<https://dev.qmp.cat/projects/qmp-cooker/>) to generate images for a
number of devices
<https://dev.qmp.cat/projects/qmp-cooker/repository/revisions/master/entry/qmp.profiles.conf#L1>.
Overall it's been very successful but, with some of them, I've faced
some trouble.
Take the example of the Alfa N5 outdoor wireless CPE
(target=ar71xx/generic, profile=ALFANX), which has 8 MB of flash
(enough to fit a lot of packages). Once the additional packages are
built (./cooker -b ar71xx/generic --force-local) I cook the image
(./cooker -c ar71xx/generic --profile=ALFANX) but the process fails:
the kernel built locally is too big to fit in the device's partition
scheme.
I guess the problem comes from the fact that the SDK builds packages
with some extra options (debug, symbols, etc.) compared to the
Buildroot. Have you experienced this behaviour? Do you have any idea
on how to overcome this? The lime-sdk cooker is a wonderful tool, and
it would be very nice to make it work with all the devices.
Actually the Kernel is not built but comes with the LEDE-SDK. This is in
one side a feature (because we use the same Kernel as official LEDE
release so we can use the same Kmods and stuff) but in the other side
the Kernel image cannot be modified, so there are some options for
reducing space which cannot be enabled.
Look at the libremesh flavors, what we do to reduce space is, for
instance, to change hostapd-mini for wpad-mini.
Apart from these tricks there is nothing more that you can do.
Cheers.
Cheers,
Roger
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
9 Jan
9 Jan
6:03 p.m.
New subject: lime-sdk fails to generate some images (too big kernel size)
On 04/01/18 23:13, Daniel Golle wrote:
On Thu, Jan 04, 2018 at 10:08:19PM +0100, pau wrote:
right.
Dear Roger,
On 04/01/18 18:18, Roger Pueyo Centelles | Guifi.net wrote:
What you meant is actually the
other way around:
hostapd-mini (AP-mode) + wpa_supplicant-mini (STA-mode) = wpad-mini
hence hostapd-mini < wpad-mini Dear LiMers,
I've been recently using the lime-sdk tool (actually, a fork
<https://dev.qmp.cat/projects/qmp-cooker/>) to generate images for a
number of devices
<https://dev.qmp.cat/projects/qmp-cooker/repository/revisions/master/entry/qmp.profiles.conf#L1>.
Overall it's been very successful but, with some of them, I've faced
some trouble.
Take the example of the Alfa N5 outdoor wireless CPE
(target=ar71xx/generic, profile=ALFANX), which has 8 MB of flash
(enough to fit a lot of packages). Once the additional packages are
built (./cooker -b ar71xx/generic --force-local) I cook the image
(./cooker -c ar71xx/generic --profile=ALFANX) but the process fails:
the kernel built locally is too big to fit in the device's partition
scheme.
I guess the problem comes from the fact that the SDK builds packages
with some extra options (debug, symbols, etc.) compared to the
Buildroot. Have you experienced this behaviour? Do you have any idea
on how to overcome this? The lime-sdk cooker is a wonderful tool, and
it would be very nice to make it work with all the devices.
Actually the Kernel is not built but comes with the LEDE-SDK. This is in
one side a feature (because we use the same Kernel as official LEDE
release so we can use the same Kmods and stuff) but in the other side
the Kernel image cannot be modified, so there are some options for
reducing space which cannot be enabled.
Look at the libremesh flavors, what we do to reduce space is, for
instance, to change hostapd-mini for wpad-mini. Apart from
these tricks there is nothing more that you can do.
Cheers.
> Cheers,
>
> Roger
>
>
>
> _______________________________________________
> lime-dev mailing list
> lime-dev(a)lists.libremesh.org
> https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
_______________________________________________
lime-dev mailing list
lime-dev(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-dev
2301
days inactive
2306
days old
3 comments
3 participants
participants (3)
-
Daniel Golle -
pau -
Roger Pueyo Centelles | Guifi.net