Mac Mini with T2 chip
-
@TaTa Ok now that both pick up IP addresses, can you image using the built in nic now as you can with the older hardware?
On the case of why… I can’t think of a reason why the linux kernel would report a different mac address than the OS. That simply shouldn’t happen. I know windows has a “feature” for wifi that it can/will create a random IP address for security reasons, but that feature is a bit dumb for me.
I’m speaking out of ignorance here, but does the hardware have some kind of firmware (bios) setup where you can see the mac address the firmware is reporting. I’m thinking the equivalent to the Dell bios screens. Since its apple with a locked ecosystem it might not.
-
@george1421 built-in nic can upload/download image just fine. I’m not sure of how to get MAC address from firmware bios on a Mac.
-
 @Tom-Elliott  Fog（Ver:1.5.8）,mac pro(2019) use USB net boot, But it say " attempting to register host…no viable macs to use
/tmp/hinfo.txt：line1：Invalid : command not found"
-
@banbuduo-2020 we need information. This might also work better as it’s own post, as this posting is quite old.
From what I can see of the pics you provided, you’re using a USB stick?
What version of FOG is your server running?
What instructions did you use for the USB?
-
@Tom-Elliott Yes，I am using a USB stick,the version of FOG is 1.5.8 in the server of Centos 7, I set the USB stick refer to the URL(https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image/22?page=2), And download bzImageT2 from the url(https://github.com/FOGProject/fogproject/releases/download/1.5.9-RC1/bzImageT2), rename bzImage on the usb flash drive and then copy the bzImageT2 to the flash drive as bzImage, do I need upgrade the version of fog to 1.5.9-RC2.11 ? or I need the version of bzImageT2 for my fog version 1.5.8
-
@banbuduo-2020 said in Mac Mini with T2 chip:
bzImage on the usb flash drive and then copy the bzImageT2 to the flash drive as bzImage, do I need upgrade the version of fog to 1.5.9-RC2.11 ? or I need the version of bzImageT2 for my fog version 1.5.8
There are a few things we need feedback on.
-
On the FOG server change to /var/www/html/fog/service/ipxe directory then key in
file bzImageand tell us the version of what was the bzImageT2 file. It will be 4.19.x or 5.x.x -
The error about hinfo.txt is strange (in deleted post) since you are getting an IP address. The target computer should be reaching the FOG server to generate this file.
-
The kernel dump in the second picture doesn’t tell the entire story. What were you doing (imaging, registering, something else) when the kernel blew up?
I know this kernel works because it has solve other FOG Admins issues. So there is something different with your system (which is possible if its a newer model) that disagrees with this kernel.
-
-
@george1421 hello，I am very happy because of your help, the version of what was the bzImageT2 file is 4.19.101,you can see the picture ,it happen the the second picture when i am doing registering… Maybe I need upgrade the version of fog to 1.5.9-RC2.11 if it is not difficulty
-
@banbuduo-2020 OK that kernel image is not one that I created. “jenkins” is on one of the FOG Developers servers. Here is the one from my one-off server: https://drive.google.com/file/d/10j8fZ3i3Y_uICxcMgX5lpiuQ2ci9bCJG/view?usp=sharing You should see a cartoon character name in the kernel definitions.
What I would do is download that as bzImageT2 and move it as is to the /var/www/html/fog/service/ipxe directory. Don’t change the name. Then in the host definiton for this apple, there is a field I think its just called kernel name enter
bzImageT2for that host and save it. Watch your case because linux is case sensitive. Then only the T2 image will be called when you pxe boot that computer. The risk of renaming bzImageT2 to bzImage is that every time you upgrade fog that T2 image will be overwritten with the latest FOG version of bzImage.Don’t confuse FOS Linux’s kernel bzImage in the ipxe directory with the FOG server’s HOST os kernel. They are different.
-
This post is deleted! -
You can also redown load it from the github site and then run the files command on that file right away. You should also see what I discussed in my last post.
