Is this normal?
-
Are you running 1.2.0 or 0.32?
-
My current production system is a clean install of 1.2.
I had been running 0.32 for the past couple of years. That one was still up on the network.
-
Was just a dirty hack anyway. So I guess we are back to the inital question of why does the kernel sit and wait for so long?? Right now I can only think of turning on kernel debugging to see where it takes so long. Open /var/www/fog/lib/fog/BootMenu.class.php, jump to line 435:
[CODE]…
$kernelArgsArray = array(
“mac=$mac”,
“ftp=$ftp”,
“storage=$storage”,
“storageip=$storageip”,
“web=$this->web”,
“osid=$osid”,
“loglevel=4”,
“consoleblank=0”,
“irqpoll”,
…[/CODE]
Change ‘loglevel=7’ and add another line just after that called ‘debug’…
[CODE]…
“loglevel=7”,
“debug”,
…[/CODE]
Schedule a task for the client and see the kernel messages scrolling past. Probably best to take a video or picture so you can check later on. -
[quote=“Uncle Frank, post: 44142, member: 28116”]Was just a dirty hack anyway. So I guess we are back to the inital question of why does the kernel sit and wait for so long?? Right now I can only think of turning on kernel debugging to see where it takes so long. Open /var/www/fog/lib/fog/BootMenu.class.php, jump to line 435:
[CODE]…
$kernelArgsArray = array(
“mac=$mac”,
“ftp=$ftp”,
“storage=$storage”,
“storageip=$storageip”,
“web=$this->web”,
“osid=$osid”,
“loglevel=4”,
“consoleblank=0”,
“irqpoll”,
…[/CODE]
Change ‘loglevel=7’ and add another line just after that called ‘debug’…
[CODE]…
“loglevel=7”,
“debug”,
…[/CODE]
Schedule a task for the client and see the kernel messages scrolling past. Probably best to take a video or picture so you can check later on.[/quote]On the DG41RQ about 10 seconds in it hangs at the message “Switched to clocksource tsc” Right before that there are several lines about the mouse and keyboard. At 60 seconds I get:
[code]"r8169 0000:03:00.0 eth0: unable to load firmware patch rtl_nic/rt18168d-1.fw (-12)
r8169 0000:03:00.0 eth0: link down
r8169 0000:03:00.0 eth0: link down[/code]
and then 3 second later:
[code]
r8169 0000:03:00.0 eth0: link up
Sending DHCP requests .
[/code]
and the it starts the imaging process.I’ll try it on the H81M-A and report back.
-
[quote=“Mark Pickard, post: 44143, member: 609”]On the DG41RQ about 10 seconds in it hangs at the message “Switched to clocksource tsc” Right before that there are several lines about the mouse and keyboard. At 60 seconds I get:
[code]"r8169 0000:03:00.0 eth0: unable to load firmware patch rtl_nic/rt18168d-1.fw (-12)
r8169 0000:03:00.0 eth0: link down
r8169 0000:03:00.0 eth0: link down[/code]
and then 3 second later:
[code]
r8169 0000:03:00.0 eth0: link up
Sending DHCP requests .
[/code]
and the it starts the imaging process.I’ll try it on the H81M-A and report back.[/quote]
Same messages at the same time for the H81M-A.
-
YAY!
Information. It is somewhat related to the nic, but not in the lack of ability, but rather a missing firmware.
-
I mean no harm with that, I just need to add the file to the compiler.
Hopefully doing that will fix the slow issue you’re seeing.
-
[quote=“Tom Elliott, post: 44146, member: 7271”]I mean no harm with that, I just need to add the file to the compiler.
Hopefully doing that will fix the slow issue you’re seeing.[/quote]
That would be great! No harm in leaving the debugging on in the mean time is there?
-
Probably not… might make you dizzy seeing all that code fly by though… and throwing up on a computer wouldn’t be good.
-
[quote=“Tom Elliott, post: 44146, member: 7271”]I mean no harm with that, I just need to add the file to the compiler.
Hopefully doing that will fix the slow issue you’re seeing.[/quote]
Sure but how many firmware files do we add to the initrd? Most are for WLAN adapters which we don’t use with FOG (so far). But there are also a couple for normal ethernet adapters… -
It’s not in the init. I build them directly in the kernel.
-
[quote=“Tom Elliott, post: 44160, member: 7271”]It’s not in the init. I build them directly in the kernel.[/quote]
Not much difference. Makes the kernel bigger and bigger. But probably better then having a lot of people waiting for a minute for no reason… -
[quote=“Uncle Frank, post: 44161, member: 28116”]Not much difference. Makes the kernel bigger and bigger. But probably better then having a lot of people waiting for a minute for no reason… ;)[/quote]
Personally, I want a kernel that will work with EVERYTHING.
UEFI & BIOS mixed environments scares the crap out of me, honestly.
-
If you’re running SVN, the kernel’s are now updated on the Sourceforge sites. All you’ll need to do is re-run the installer. The 3.19.1 kernel has been updated. Next up is to build the 3.19.2 drivers.
-
[quote=“Tom Elliott, post: 44164, member: 7271”]If you’re running SVN, the kernel’s are now updated on the Sourceforge sites. All you’ll need to do is re-run the installer. The 3.19.1 kernel has been updated. Next up is to build the 3.19.2 drivers.[/quote]
Awesome! Flies right through it now. Thank you so much for your help.
