Re: [LEDE-DEV] Linksys WRT54GL / image builder

2017-10-20 Thread Alberto Bursi



On 10/20/2017 02:54 PM, Mikael Bak wrote:

Hi Jo,

On 20/10/17 10:59, Jo-Philipp Wich wrote:

Hi Mikael,

try "make info", that should display the required package set per 
device.




Thanks for the info.

$ make info
[snip]
linksys-wrt54g:
    Linksys WRT54G
    Packages: kmod-b43 kmod-b43legacy
[snip]

So I did this:
$ make image PROFILE=linksys-wrt54g PACKAGES="kmod-b43 kmod-b43legacy"

And it got me a quite small, basic image without luci that fit on my 
device.


FYI: the image I can download from today's snapshot is too big to fit 
on these devices (3.7MB). The image I built is only 3.5MB.
So I'm asking how is the package list determined for a device when the 
snapshots are built?


Is there a make command in the image builder I can run to see what the 
default packages are for a given device?


Thanks again,
Mikael

If you launch a image build without any PACKAGES= set you will see what 
are the default packages in the first lines of the output, see the 
following example:


$ make image PROFILE="wt3020-8M"

Building images for ramips - Nexx WT3020 (8MB)
Packages: base-files busybox dnsmasq dropbear firewall fstools ip6tables 
iptables kernel kmod-gpio-button-hotplug kmod-leds-gpio kmod-mt76 
kmod-rt2800-pci kmod-rt2800-soc libc libgcc logd mtd netifd odhcp6c 
odhcpd opkg ppp ppp-mod-pppoe swconfig uci uclient-fetch wpad-mini


[and then it starts downloading packages]

-Alberto

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Linksys WRT54GL / image builder

2017-10-20 Thread John Norton


On 20/10/2017 10:44, Mikael Bak wrote:

Hi,

I have been using the image builder in the past to generate custom 
images with additional packages for my other TP-LINK routers, and that 
works fine.


Now I would like to use an old Linksys WRT54GL as an access point and 
would like to generate a custom image with a minimal set of packages 
(without luci and some other stuff).


My question is: How can I know what packages I must include when 
building the image with the image builder in order to get the device 
to boot and be able to login via ssh?


Something like this:
$ make image PROFILE=linksys-wrt54g PACKAGES="[what should be here?]"

Thanks for all the hard work with lede/openwrt!

TIA,
Mikael



If you run the imagebuilder without any "PACKAGES=xxx", it will generate 
an image with the default packages for that device, kernel/drivers for 
its integrated hardware, uci, ssh, firewall, ppp and ipv6 functionality 
are included.


The image generated is similar to what you get in a LEDE development 
snapshot.


The "PACKAGES=xxx" option is there for including something on top of 
that, or removing some of the default-selected packages (like the ones 
for ipv6 support/firewall/whatever, for example).


Will edit the wiki page to add this info.

-Alberto

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Linksys WRT54GL / image builder

2017-10-20 Thread Mikael Bak

Hi Jo,

On 20/10/17 10:59, Jo-Philipp Wich wrote:

Hi Mikael,

try "make info", that should display the required package set per device.



Thanks for the info.

$ make info
[snip]
linksys-wrt54g:
Linksys WRT54G
Packages: kmod-b43 kmod-b43legacy
[snip]

So I did this:
$ make image PROFILE=linksys-wrt54g PACKAGES="kmod-b43 kmod-b43legacy"

And it got me a quite small, basic image without luci that fit on my device.

FYI: the image I can download from today's snapshot is too big to fit on 
these devices (3.7MB). The image I built is only 3.5MB.
So I'm asking how is the package list determined for a device when the 
snapshots are built?


Is there a make command in the image builder I can run to see what the 
default packages are for a given device?


Thanks again,
Mikael


For reference here's the complete package list I got after building my 
own image with the above command (Image builder for LEDE 17.01.4):


b43legacy-firmware - 3.130.20.0-1
base-files - 173.1-r3560-79f57e422d
busybox - 1.25.1-4
dnsmasq - 2.78-1
dropbear - 2017.75-2
firewall - 2017-05-27-a4d98aea-1
fstools - 2017-06-30-bdcb075f-1
fwtool - 1
hostapd-common - 2016-12-19-ad02e79d-6
ip6tables - 1.4.21-2
iptables - 1.4.21-2
iw - 4.9-1
jshn - 2017-02-24-96305a3c-1
jsonfilter - 2016-07-02-dea067ad-1
kernel - 4.4.92-1-f748c7658ebe780bcfe532cde71ec481
kmod-b43 - 4.4.92+2017-01-31-3
kmod-b43legacy - 4.4.92+2017-01-31-3
kmod-cfg80211 - 4.4.92+2017-01-31-3
kmod-gpio-button-hotplug - 4.4.92-2
kmod-ip6tables - 4.4.92-1
kmod-ipt-conntrack - 4.4.92-1
kmod-ipt-core - 4.4.92-1
kmod-ipt-nat - 4.4.92-1
kmod-leds-gpio - 4.4.92-1
kmod-ledtrig-default-on - 4.4.92-1
kmod-ledtrig-netdev - 4.4.92-1
kmod-ledtrig-timer - 4.4.92-1
kmod-lib-crc-ccitt - 4.4.92-1
kmod-mac80211 - 4.4.92+2017-01-31-3
kmod-nf-conntrack - 4.4.92-1
kmod-nf-conntrack6 - 4.4.92-1
kmod-nf-ipt - 4.4.92-1
kmod-nf-ipt6 - 4.4.92-1
kmod-nf-nat - 4.4.92-1
kmod-ppp - 4.4.92-1
kmod-pppoe - 4.4.92-1
kmod-pppox - 4.4.92-1
kmod-slhc - 4.4.92-1
lede-keyring - 2017-01-20-a50b7529-1
libblobmsg-json - 2017-02-24-96305a3c-1
libc - 1.1.16-1
libgcc - 5.4.0-1
libip4tc - 1.4.21-2
libip6tc - 1.4.21-2
libjson-c - 0.12.1-1
libjson-script - 2017-02-24-96305a3c-1
libnl-tiny - 0.1-5
libpthread - 1.1.16-1
libubox - 2017-02-24-96305a3c-1
libubus - 2017-02-18-34c6e818-1
libuci - 2016-07-04-e1bf4356-1
libuclient - 2017-09-06-24d6eded-1
libxtables - 1.4.21-2
logd - 2017-03-10-16f7e161-1
mtd - 21
netifd - 2017-01-25-650758b1-1
nvram - 10
odhcp6c - 2017-01-30-c13b6a05-2
odhcpd - 2017-10-02-c6f3d5d4-2
opkg - 2017-03-23-1d0263bb-1
otrx - 1
ppp - 2.4.7-11
ppp-mod-pppoe - 2.4.7-11
procd - 2017-08-08-66be6a23-1
swconfig - 11
ubox - 2017-03-10-16f7e161-1
ubus - 2017-02-18-34c6e818-1
ubusd - 2017-02-18-34c6e818-1
uci - 2016-07-04-e1bf4356-1
uclient-fetch - 2017-09-06-24d6eded-1
usign - 2015-07-04-ef641914-1
wpad-mini - 2016-12-19-ad02e79d-6

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev


Re: [LEDE-DEV] Linksys WRT54GL / image builder

2017-10-20 Thread Jo-Philipp Wich
Hi Mikael,

try "make info", that should display the required package set per device.

~ Jo

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev