Topics created by Sebastian Roth

@sebastian-roth I found the error was only in regards to the checkbox. It worked the “first” login entry you make, but the modal window wasn’t closing. So you would press the delete button again, causing the invalid login (as it was at that point invalid as no credentials were being passed anymore).

I’ve been working on the on and off over the last weeks. This is what I just sent to iPXE dev Michael Brown:

Tried looking at the NIC registers as suggested by NiKiZe in the forums a while back. Added ethtool code to dump registers to iPXE but from my tests it looks like many registers are different on every reboot and I have no idea which registers mean what. For now I don’t think this is getting us anywhere. But I am open to suggestions.
Digging through the tg3*.c code I figured that there might be some auto negotiation issue on the iMac model I have. Curtis did not seem to have that and got that sort of fixed. Now I am seeing the same thing as Curtis, interface comes up and it tries to send packets to wire but fails so. As far as I know Curtis has been onto this together with you on a IRC chat.
On the other lane I have tested the Linux code a fair bit. Tested 4.13.4, early 3.9 and the very first commit that added 57766 NIC support to the Linux kernel. I did test those early versions as I hoped to clarify if the later added binary firmware blob is playing a role or if any commit in the kernel code did fix an issue with Macs. Turns out it’s not from my tests. They all worked like a charm on the iMac that cannot send packets within iPXE.

Hope we’ll find some time to give me some hints on where to dig next.

@Seb-B As well if you have ideas and suggestions on how to diff the tg3 code of iPXE and the Linux kernel to figure out what’s up. I have started to but there seem to be too many minor differences making it really hard to diff. Though I have the feeling that we should be able to solve this soon as Linux kernel is working great.

I can’t tell you what version I’m running at home. But I am able to use FF on Zorin (ubuntu based). That is my primary browser I use for the fog forums. I can confirm when I get home. As for right now I’m using FF 47.0 on my windows computer and it is fine.

@Sebastian-Roth said in Uploading image breaks source machine, XP:

Possibly marking things unread as a dev makes it show up for everyone again?!?

Well that’s not very nice to everyone else… I’m going to test… you guys will know if this is the case or not.

sorry I dont think this is an issue anymore. We dont seem to be getting it aver we updated to the latest svn. Sorry again for the non response.

@Sebastian-Roth Sure. Marking this un-read so I can come back later.

This is untested… But well, what can go wrong?! What do you think about adding the same thing to the registration script if things fail?

@Sebastian-Roth I think I did - but that was a long time ago and it looked hard lol.

Keep in mind I’m learning stuff all the time. Looking at it now, that is going to be a piece of cake.

@Tom-Elliott said:

The canned responses that are available or more of a simple press and send kind of system which might help, but still can leave most of our common questions unanswered.

So what are our common questions that will still be unanswered you think? I guess it’s just a matter of putting all those into the canned responses “template”. I don’t think every user will fill in all the details and we still need to ask questions. But on the other hand a lot of people will happily provide as much information as they can straight from the start if they’d knew what we need to know. So the better questions we have in the “template” the better it will be. Please start adding questions to th OP!

@Wayne-Workman Thanks heaps for keeping in contact with Julian on this!

@Louis-CSUSA I forked your posts to here: https://forums.fogproject.org/topic/7561/network-booting-a-mac

Please post in there.

Fixed in latest. Have to know what Pages with objects there are, and I forgot that part. Added and all is working as expected.

I’m marking this solved. Please feel free to open this again if we run into the issue again.

@Sebastian-Roth This should be fixed now. Since moving to a less initialization status, I forgot that the last item called is the item that will be referenced. So flipped the logic on the cancellation and all started working for me.

Ok, together with Jbob I seem to have figured out a working set of libraries (SharpPcap and PacketDotNet) and C# code to send and receive the packets we want. Hopefully we’ll have the first alpha version of a tool ready soon!

I’ve solved this thread for a couple reasons. First, this isn’t really a “bug” in the truest sense. While it did print unwanted data, it had literally 0 impact on the operation of things. That said, the second reason is these “suggestions?” have been achieved. First, I added the rootfsext=ext4 as suggested. Second, we are not starting udevd at boot any more. The findings (as far as we’re aware of) that udev did “special” was it linked the stdin, stdout, and stderr to their respective proc resource element. We were able to do this on our own without needing to start this udev script at boot. This means you should not see the epoll message at all anymore.

@Jbob Thanks for your detailed answer. I agree that string filtering the MACs on the client is not wise! Shouldn’t do that. Detecting physical devices only sounds like a way better approach. See what you can do if you find the time and let me know if I can give you a hand.

Thanks! Well, then marking this solved straight away. Please let us know if you see an issue with this.

I was able to confirm the issue of the sub directories not being created and after making the proposed suggestions the installer did indeed create the pxelinux.cfg and i386-efi folders. This issue was present on both Ubuntu and Fedora.

I’m marking this as solved.

@Sebastian-Roth
https://wiki.fogproject.org/wiki/index.php?title=CentOS_7
😉

@Sebastian-Roth Pushed as suggested.