Black Screen on Surface Pro 4

[Tom Elliott]

@Psycholiquid I’ll but the 7156 efi files up on rc-3 so this shouldn’t be an issue anymore.

[Wayne Workman]

@Tom-Elliott said in Black Screen on Surface Pro 4:

@Psycholiquid I’ll but the 7156 efi files up on rc-3 so this shouldn’t be an issue anymore.

Perhaps even label them differently than just replacing all of them?

Could call the 7156 ipxe.efi file something like surfspro.efi or ipxe7156.efi ?

I want to keep the latest efi files, and these ones that work for the surface too.

If someone ( @Psycholiquid ) could post a complete packet capture of a DHCP conversation with a surface 4, I’ll see what I can do in the way of a vendor class for DHCP.

[Psycholiquid]

@Tom-Elliott It worked to switch out the files. Not sure why but it did work.

[Psycholiquid]

@Wayne-Workman said in Black Screen on Surface Pro 4:

@Tom-Elliott said in Black Screen on Surface Pro 4:

@Psycholiquid I’ll but the 7156 efi files up on rc-3 so this shouldn’t be an issue anymore.

Perhaps even label them differently than just replacing all of them?

Could call the 7156 ipxe.efi file something like surfspro.efi or ipxe7156.efi ?

I want to keep the latest efi files, and these ones that work for the surface too.

If someone ( @Psycholiquid ) could post a complete packet capture of a DHCP conversation with a surface 4, I’ll see what I can do in the way of a vendor class for DHCP.

Man would love to if I knew how…

[Psycholiquid]

@Psycholiquid said in Black Screen on Surface Pro 4:

@Wayne-Workman said in Black Screen on Surface Pro 4:

@Tom-Elliott said in Black Screen on Surface Pro 4:

@Psycholiquid I’ll but the 7156 efi files up on rc-3 so this shouldn’t be an issue anymore.

Perhaps even label them differently than just replacing all of them?

Could call the 7156 ipxe.efi file something like surfspro.efi or ipxe7156.efi ?

I want to keep the latest efi files, and these ones that work for the surface too.

If someone ( @Psycholiquid ) could post a complete packet capture of a DHCP conversation with a surface 4, I’ll see what I can do in the way of a vendor class for DHCP.

Man would love to if I knew how…

Unless you are talking about Wiresharking the packets between the surface and the fog server. If so I can give that a try today. I did back up the files before I uploaded the other ones.

[Tom Elliott]

I’ve add the 5835 svn tftp files into the mix but labeled them as 7156 (as that’s the version iPXE files they’re using).

There is some change between that commit (starting with sha hash 7156) and current iPXE code that broke the functionality in some way. I haven’t had enough time to troubleshoot or test. So I find it quite nice to be able to have both versions of the files (current, and what works) so at least it reminds me what version worked.

[Wayne Workman]

@Psycholiquid said in Black Screen on Surface Pro 4:

Unless you are talking about Wiresharking the packets between the surface and the fog server. If so I can give that a try today. I did back up the files before I uploaded the other ones.

That’s what I’m asking for. Different people have different ways of getting it done. Just a full DHCP conversation is all that is needed.

[fry_p]

@Wayne-Workman said in Black Screen on Surface Pro 4:

@Psycholiquid said in Black Screen on Surface Pro 4:

Unless you are talking about Wiresharking the packets between the surface and the fog server. If so I can give that a try today. I did back up the files before I uploaded the other ones.

That’s what I’m asking for. Different people have different ways of getting it done. Just a full DHCP conversation is all that is needed.

I have some spare time and a surface pro 4 sitting in front of me. I can get you that capture. I’m rusty on Wireshark so it may take a minute lol

[Tom Elliott]

@fry_p I don’t understand what DHCP packets are or aren’t going to prove? It’s not failing to see or download or even execute the files. It’s failing to release the file back to allow booting the bzImage/init together.

[fry_p]

@Tom-Elliott said in Black Screen on Surface Pro 4:

@fry_p I don’t understand what DHCP packets are or aren’t going to prove? It’s not failing to see or download or even execute the files. It’s failing to release the file back to allow booting the bzImage/init together.

On the other hand if this is a moot point, I won’t bother. Let me know

[Wayne Workman]

@Tom-Elliott Tom, I’m wanting the capture in hopes of creating a dhcp class to hand out the specific boot ROM that works with Surface pros, so people don’t have to switch files back and forth. What you’re talking about is a different issue.

[fry_p]

@Wayne-Workman I’m still up to doing it… If I do this, we would be able to set a class much like my UEFI/BIOS Co-existence on DHCP? I’d like this very much.

[Wayne Workman]

@fry_p Yeah, like that hopefully. I am not making promises though, but that’s the goal. It all just depends on how the surface identifies itself in the DHCP Discovery packet.

[fry_p]

@Wayne-Workman I’m about to leave for the day, But I got a capture of the surface with USB to ethernet adapter and our DHCP server. It’s not much to look at, please let me know if it is not what you are looking for.0_1469568466030_fog surface1.pcapng

[Wayne Workman]

@fry_p I looked through it, there are no DHCP packets in it. Thanks for trying though. Maybe tomorrow?

[fry_p]

@Wayne-Workman said in Black Screen on Surface Pro 4:

@fry_p I looked through it, there are no DHCP packets in it. Thanks for trying though. Maybe tomorrow?

whoops, I needed a refresher on wireshark lol. After some googling, I filtered it to host (IP OF SURFACE) and udp ports 67 or 68 between the DHCP server and the surface

0_1469569393912_fog surface1.pcapng

edit: I’m out of the office tomorrow and the pro 4 i have for testing may be deployed by Thursday

[Wayne Workman]

@fry_p We might have a winner!

Try this class, add it into ISC-DCHP config file and then restart dhcp. Be aware of putting it into the right subnet and not messing up the closing brackets for that subnet.

class "SURFACE-Pro-4" {
    match if substring(option vendor-class-identifier, 0, 32) = "PXEClient:Arch:00007:UNDI:003016";
    filename "ipxe7156.efi";
}

Notice the filename I specified. This is the file that works with the Microsoft Surface series, and is available in FOG 1.3.0 RC-3 by default.

Also, notice all that stuff in the vendor class identifier… it’s a lot. That exact identifier is probably specific to that EXACT model of surface pro 4. Meaning this probably wouldn’t work for a surface pro made 6 months from now, or 6 months before because the manufacturers change that last part all the time, for every little change they make. I think that’s how they determine what image to put on it at the factory.

If this works, I think we can make a Windows Server 2012+ equivalent as well.

I guess now, I have to ask every surface person on the forums to do a packet capture. They are like Pokemon, gotta catch em all.

That said, can you provide a sub-model number? Anything on the back of the device in tiny print? Not looking for a serial, but a sub-model.

[george1421]

@Wayne-Workman Do you know if wild cards are supported for the class matching? If so then something like “SURFACE*” would match all when the surface 5’s come out.

[Wayne Workman]

@george1421 I set the class name “surface-pro”. The matching string is how the surface 4 identified. You can name classes whatever you want, so long as it makes sense.

In that last packet capture, look at dhcp discover option 60.

[fry_p]

@Wayne-Workman I use Server 2012 as my DHCP server, so how would I incorporate this into that (no idea what or where the ISC-DHCP config file is)? Should I follow the wiki instructions? Pardon my ignorance on the subject. Also, tomorrow I can get you the sub-model, but are we talking the surface, or the dongle?