The VideoLAN Forums

Hello,

I bought some A130M from ebay, unflashed the problem is that although the A130 works with dhcpd.conf like
the A130M don't seem to have the same vendor-class-identifier, I tried with tcpdump, but they don't send anything...

I tried also adding the "m" as in dhcpd.conf example from amino docs but still no luck Anyone have any clue how to force the dhcpd server to identify the A130M?
Also the A130 image is compatible with A130M ?
As fas as the hardware the A130M is missing the rj11 jack..

Regards
memmas

OK! after building a debug cable, I realize that was A130v2 and not A130M, but problem was that it requires upgrade from tftp boot, and not multicast dhcp server as the old one...

I only have bootstrap and mc2.mcfs files, does anyone know how to unpack mc2.mcfs or having a full archive of A130 or Ax3x to create the tftpboot directory, or how to upgrade from tftp boot with the files I already have (bootstrap, mc2.mcfs)?

Regards
memmas

OK! After a lot of testings , the debug cable help on that, I was able to install system...
After failed attempts to extract mc2.mcfs to a directory, I follow another approach...
Since the A130 wanted a tftp boot server I gave him one, place the bootstrap kernel in tftpboot directory and create an AMINET.txt with So having the multicast server running already I was able to install the mc2.mcfs through the booted bootstrap kernel...

I had to trick it thought, because sniffing with tcpdump I saw a vendor-class with "Linux 2.6.17.14_stm22_0037 sh4" so I add in
class "AmiNET130 upgrd" I hope that will help others...

Regards
memmas