Sending discover loop
-
Images showing the boot process.
-
cdc_etherandwwan0point to a USB mobile broadband network device. Please disconnect this and try again! -
@Sebastian-Roth Thanks! I turned off the Wireless WAN in BIOS and the client works. But this was never a problem before. I do not need this Wireless WAN device, but what if the scenario is different, users have to use the device? Should I then have to turn off/on this device each time I want to deploy the client?
-
From what I could find out on the internet this has nothing to do with wireless!! As Tom already said: WAN means ‘wide area network’ - nothing about wireless! We don’t have any wireless drivers in the kernel (I just checked again). Searching the web about Thinkpad T500 and wwan0 I only see people using USB mobile broadband adapters but nothing about wireless.
Can you please take a picture of the BIOS setting you changed?
-
Just found this: https://bugzilla.kernel.org/show_bug.cgi?id=13544
the laptop (a thinkpad t500) has an integrated mobile modem. i think it is some kind of ericsson f3507g.
Seams like this is found by the cdc_ether driver. First I thought that some FOG users use the driver with USB network cards. But searching the forum (cdc_ether mentioned only once!) and reading other things like http://www.linux-usb.org/usbnet/ I really wonder if we need this in the kernel. @Tom-Elliott what do you think?
-
@pmonstad Please try updating and running the installer, I’ve updated the kernels to remove the usbnet problem @Sebastian-Roth is describing.
Hopefully this is corrected for now.
-
@Tom-Elliott I ran the installer and rebooted my client. Same problem i.e. it shows same messages during the boot process.
-
@pmonstad The problematic device is shown as wwan0 during client boot, and the device still shows after doing the upgrade to svn 5485.
-
@Tom-Elliott I don’t see the kernel config in SVN being updated (http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/kernel/TomElliott.config.64). Am I missing something here??
-
I updated the kernel as a test, I have not pushed the config up because I wanted to know that status first.
-
@pmonstad Are you sure you have the latest kernel/init?? To make sure we should compare MD5 hashes. Please run
md5sum /var/www/html/fog/service/ipxe/bzImage /var/www/html/fog/service/ipxe/init.xzChecksums should be:
b6aae1e7fa985e48cc60cda106152cf7 bzImage fea93a2b7ea97d7a972c40018f1152af init.xz -
@Sebastian-Roth I will check this at work tomorrow. Thanks!
-
@Tom-Elliott I just ran the svn command to get the latest svn downloaded. Then I ran the ./install.sh script. Should I do something else to test this new kernel?
-
@pmonstad Checksums are correct:
b6aae1e7fa985e48cc60cda106152cf7 /var/www/html/fog/service/ipxe/bzImage
fea93a2b7ea97d7a972c40018f1152af /var/www/html/fog/service/ipxe/init.xzDuring the boot it first turns on eth0, correct, but some seconds later it turns on wwan0
Now running svn 5499
-
@pmonstad can you update and try an image task? I updated the kernels again and hope that I got it right this time. I even updated the Config file in svn as I’m so hopeful this can then be solved.
-
Config looks good from my point of view. Keeping my fingers crossed…
-
@Tom-Elliott Thanks! I will try this at work tomorrow and give you a feedback then!
-
@pmonstad Now it works! Thanks a lot for sorting this out!
-
Thanks for reporting back! Great that we could solve this. I really hope we never see anyone actually needing this cdc_ether module!!
