New Raspberry Pi 3B+

All about WTware on Raspberry. Wtware works with Raspberry Pi 3 Model B and Pi 2 Model B devices
http://www.winterminal.com
dyvyak
Posts: 4
Joined: Wed Apr 25, 2018 10:58 am

Re: New Raspberry Pi 3B+

Post by dyvyak » Wed Apr 25, 2018 11:05 am

Hi, are you able to network boot with sd card?
When i create sd card in Configurator for network boot (not programming for boot withou sd), network interface on rpi doesn't come up at all(i checking it on cisco switch). When i remove sd card, network interface is comming up. This is happening only on RPi 3B+ , Rpi 3B is working fine.
Thx

akatik
SUPPORT
SUPPORT
Posts: 279
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: New Raspberry Pi 3B+

Post by akatik » Wed Apr 25, 2018 5:29 pm

Rpi 3B+ needs no SD for network card.

dyvyak
Posts: 4
Joined: Wed Apr 25, 2018 10:58 am

Re: New Raspberry Pi 3B+

Post by dyvyak » Thu Apr 26, 2018 11:49 am

akatik wrote:
Wed Apr 25, 2018 5:29 pm
Rpi 3B+ needs no SD for network card.
OK, thanks. Looks like it's working now

theshadow

Re: New Raspberry Pi 3B+

Post by theshadow » Tue Jul 17, 2018 4:44 pm

Hello,
I'm having problems booting Rpi 3B+
When trying to boot from network with or without a sd card there is no signal on the monitor, I'm trying to boot it with wtware 5.8.22.
Did anything change in the way wtware boots rpi's in the latest versions? I have been using version 5.4.90 with rpi 3B with booting from sd card without a problem.
I have configured my dhcp server with: filename "5.8.22/wtware.pxe"; and nextserver options and it worked in version 5.4.90 with card booting.
Also I've seen that when creating sd card with version 5.8.22 there are no more .bin files in the sd card. Am i missing something?
Thank you

akatik
SUPPORT
SUPPORT
Posts: 279
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: New Raspberry Pi 3B+

Post by akatik » Tue Jul 17, 2018 5:25 pm

theshadow wrote:
Tue Jul 17, 2018 4:44 pm
I'm having problems booting Rpi 3B+
When trying to boot from network with or without a sd card
My Rpi 3B+ never boots from network WITH sd card. 3B+ boots from network only WITHOUT sd.
theshadow wrote:
Tue Jul 17, 2018 4:44 pm
Did anything change in the way wtware boots rpi's in the latest versions?
Thre are no changes in several latest versions. Not sure about changes since 5.4.90.
theshadow wrote:
Tue Jul 17, 2018 4:44 pm
I have configured my dhcp server with: filename "5.8.22/wtware.pxe"; and nextserver options and it worked in version 5.4.90 with card booting.
Rpi (from 2 to 3B+) ignores filename and boots well with "HelloWorld" in 067 DHCP.
theshadow wrote:
Tue Jul 17, 2018 4:44 pm
Also I've seen that when creating sd card with version 5.8.22 there are no more .bin files in the sd card.
Reformat sd. Try another sd. Configurator should write bootcode.bin creating "network boot sd".

theshadow

Re: New Raspberry Pi 3B+

Post by theshadow » Wed Jul 18, 2018 9:48 am

Hello,
Thank you for your quick response.
I have added option bootfile-name "Hello World"; in my isc-dhcp-server config, the raspberry behaves the same. The log for the server shows the raspberry discovers the server but after being offered the ip address the raspberry doesn't DHCPREQUEST or DHCPACK:
Jul 18 09:19:30 dhcpd: Sending config line 'host rpi {#012hardware ethernet b8:27:eb:cf:b9:b5;#012fixed-address 192.168.100.139;#012option bootfile-name "Hello World";#012}#012'
Jul 18 09:19:32 dhcpd: Sending config line 'host rpi {#012hardware ethernet b8:27:eb:cf:b9:b5;#012fixed-address 192.168.100.139;#012option bootfile-name "Hello World";#012}#012'
Jul 18 09:19:32 dhcpd: Sending config line 'host rpi {#012hardware ethernet b8:27:eb:cf:b9:b5;#012fixed-address 192.168.100.139;#012option bootfile-name "Hello World";#012}#012'
Jul 18 09:20:06 dhcpd: DHCPDISCOVER from b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:06 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:11 dhcpd: DHCPDISCOVER from b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:11 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:17 dhcpd: DHCPDISCOVER from b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:17 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:22 dhcpd: DHCPDISCOVER from b8:27:eb:cf:b9:b5 via eth0
Jul 18 09:20:22 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:cf:b9:b5 via eth0
I have also tried with a different dhcp server and the problem is the same

akatik
SUPPORT
SUPPORT
Posts: 279
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: New Raspberry Pi 3B+

Post by akatik » Wed Jul 18, 2018 11:13 am

bootfile-name is not required.
next-server is required. I don't see next-server in your log.

theshadow

Re: New Raspberry Pi 3B+

Post by theshadow » Wed Jul 18, 2018 1:20 pm

Sorry forgot to re add next server:
Jul 18 13:16:56 dhcpd: Sending config line 'host rpi {#012hardware ethernet b8:27:eb:f6:da:0f;#012fixed-address 192.168.100.139;#012next-server 192.168.100.146;#012}#012'
Jul 18 13:16:58 dhcpd: Sending config line 'host rpi {#012hardware ethernet b8:27:eb:f6:da:0f;#012fixed-address 192.168.100.139;#012next-server 192.168.100.146;#012}#012'
Jul 18 13:16:58 dhcpd: Sending config line 'host rpi {#012hardware ethernet b8:27:eb:f6:da:0f;#012fixed-address 192.168.100.139;#012next-server 192.168.100.146;#012}#012'
Jul 18 13:18:45 dhcpd: DHCPDISCOVER from b8:27:eb:f6:da:0f via eth0
Jul 18 13:18:45 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:f6:da:0f via eth0
Jul 18 13:18:50 dhcpd: DHCPDISCOVER from b8:27:eb:f6:da:0f via eth0
Jul 18 13:18:50 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:f6:da:0f via eth0
Jul 18 13:18:55 dhcpd: DHCPDISCOVER from b8:27:eb:f6:da:0f via eth0
Jul 18 13:18:55 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:f6:da:0f via eth0
Jul 18 13:19:00 dhcpd: DHCPDISCOVER from b8:27:eb:f6:da:0f via eth0
Jul 18 13:19:00 dhcpd: DHCPOFFER on 192.168.100.139 to b8:27:eb:f6:da:0f via eth0
Problem seems to be the same

akatik
SUPPORT
SUPPORT
Posts: 279
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

Re: New Raspberry Pi 3B+

Post by akatik » Tue Jul 31, 2018 4:48 pm

Which DHCP server do you use? Read DHCP server documentation about next-server option. There are two fields in DHCPOFFER about next (boot, TFTP) server address. Perhaps, your DHCP needs both to be specified.

Post Reply