Drivers Loading During Booting Up
-
@NollipfSense said in Drivers Loading During Booting Up:
takes 2 minutes and 40 seconds to completely load.
Like : the boot process shows a line, pauses 10 seconds, and shows another line.
Or do you want to show us what line exactly takes a "lot of time" ?!
My "Atom(TM) CPU C3338R @ 1.80GHz" based Netgate (a 4100) needs ... not sure.... 30 seconds before it enters pfSense land.
-
@Gertjan said in Drivers Loading During Booting Up:
Like : the boot process shows a line, pauses 10 seconds, and shows another line.
Yes however, with the device manager, it pauses for 30 seconds, then continues, then gets to cryptographic accelerator, pauses for 2 minutes and 40 seconds until the next line appears...this is consistently over several booting up and just curious.
-
It sounds like you have the wrong console type set and are only seeing the boot messages that are sent to both consoles.
Check Adv > Admin Access > primary-console
-
@stephenw10 said in Drivers Loading During Booting Up:
It sounds like you have the wrong console type set and are only seeing the boot messages that are sent to both consoles.
Check Adv > Admin Access > primary-console
It was on serial console...just changed to video and will reboot to see whether that resolve it. No, it remained the same...
-
It just appears to stop and then carried on with the normal boot? Or do you see nothing for some time and then just see the console menu?
-
@stephenw10 said in Drivers Loading During Booting Up:
It just appears to stop and then carried on with the normal boot?
More like a pause, albeit a 2 minitues and 40 seconds, then carry on as normal until it gets to my favorite part "bootstrapping clock" where I smile wondering who came up with that term while I visualize a cartoon animation of a clock getting bootstrapped. Every time I watch the boot up process, the same animation appears upon seeing bootstrapping clock.
-
Hmm, odd. Can you show where in happens in the boot messages?
-
@stephenw10 said in Drivers Loading During Booting Up:
Hmm, odd. Can you show where in happens in the boot messages?
Stayed like this for 2 minutes and 40 seconds approximately before continuing...
-
Ah, that's using the 8950 expansion card for QAT?
If you disable QAT does it not hang there?
Try pressing CTL+t at the console whilst it's waiting at that point. See what it's waiting for.
-
@stephenw10 said in Drivers Loading During Booting Up:
Ah, that's using the 8950 expansion card for QAT?
If you disable QAT does it not hang there?
Try pressing CTL+t at the console whilst it's waiting at that point. See what it's waiting for.
If I interrupt this correctly, it seems that the system is pausing NIC driver (e1000) first so it can load...learned something new today! Maybe the difference with the private cloud box is that it's not using the e1000 driver; it's using a virtual one.
-
Hmm, no idea why it would wait for that. Loading the driver usually almost instant.
Does it actually have any em or igb NICs? That QAT card is a bit odd because IIRC it is derived from a chipset that includes e1000 NICs....
-
@stephenw10 said in Drivers Loading During Booting Up:
Hmm, no idea why it would wait for that. Loading the driver usually almost instant.
Does it actually have any em or igb NICs? That QAT card is a bit odd because IIRC it is derived from a chipset that includes e1000 NICs....
It has the Intel i350-t4, so igb...
-
If you keep hitting ctl+t does the 'r' values count up in seconds for the full delay with the same process?
-
@stephenw10 said in Drivers Loading During Booting Up:
If you keep hitting ctl+t does the 'r' values count up in seconds for the full delay with the same process?
Yes indeed; however, I didn't go to the full delay...didn't see the last part of your sentence while trying to get the camera ready. This gives the idea of the 2 minutes and 40 seconds estimation though...
-
Are you able to test removing the QAT card? I'd bet that is the odd chipset that it has in some way.
-
@stephenw10 said in Drivers Loading During Booting Up:
Are you able to test removing the QAT card? I'd bet that is the odd chipset that it has in some way.
No because it's my production box, don't want to disrupt the rest of the household...I would lose.
-
Ok I understand. Let me see if I can find anything...
-
@stephenw10 said in Drivers Loading During Booting Up:
Ok I understand. Let me see if I can find anything...
It turned out that the same e1000 affects the device manager and caused its delay also despite only 20 - 30 seconds...
-
I think you will need to schedule and outage and try booting without the QAT card to confirm that is or isn't the source of the problem here.
-
@stephenw10 said in Drivers Loading During Booting Up:
I think you will need to schedule and outage and try booting without the QAT card to confirm that is or isn't the source of the problem here.
The thing is I don't view it as a problem since the box completed the boot up and operates normally...I was just curious about the delay and learned the cause that appears to be the e1000 driver or the manner it loads. With the private cloud box, which has the same identical NIC and QAT, I know that the delay doesn't happen because it's not using the e1000 driver but instead is using the virtl0/1 paravirtualized driver.
I could schedule something on the weekend when the other household gone shopping...maybe it's unnecessary since I can compare with the private cloud box.
