[SOLVED] no network at startup, but network after restart
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The system does not recognize the network card at the first boot after shutdown.
Once the system is restarted, in the session after restart, network card is recognized; networkmangaer starts and brings the network connection up.
Idea similar to what here happens.. http://www.linuxquestions.org/questi...ve-4175534057/
a) after boot, print the "lsmod" and "dmesg" output
b) after reboot, print the "lsmod" and "dmesg" output
Find out the differences between the files in a) and b).
Identify which driver of b) is loaded for the net card (it should not be blacklisted).
Perhaps a driver is loaded wrongly during a coldboot for your lan card and should be blacklisted.
I'd look at your system log and determine if there's an issue with the network service. See if there are differences between cold boot and warm boot. It would seem to me that some initialization is performed during the cold boot, but it's insufficient or not timely so that when it attempts to raise the network connection, it fails. Meanwhile if you either wait, as suggested, and restart networking, or perform the warm boot, the hardware is now OK and that attempt works. Once you figure out the key initialization, you can then work to ensure this initialization occurs prior to raising the network connection.
What network connection is this? I'm assuming its ethernet. What card do you have? At the very least do lspci before and after reboot to see if the card is detected. It's really a configuration issue, I think, and can be sorted easily.
Right, but they're running Mint. Granted that's Ubuntu, but probably different packages than what they identified. One would also think that Mint 17 would have reparations in it considering that this was reported in 2013.
Analysis was that there is something different between cold boot and warm boot, something in that card is not initialized fully, but the second time (warm boot) it works because it was primed by the cold boot initialization, however not fully made ready.
Recommendation was to look at your system logs fully and see differences with respect to that card and your network between the cold and warm boot.
Also check to see if that particular driver has any separate logs of it's own and check those out.
Perhaps a solution might be to completely unload the driver and reload it. Not the best solution, but an initialization thing here sometimes can only be fixed by re-writing the driver to have initialization be fully done the first time.
I repeat, too...
a) after boot, print the "lsmod" and "dmesg" output.
lsmod > lsmod_cold.txt
dmesg > dmesg_cold.txt
b) after reboot, print the "lsmod" and "dmesg" output
lsmod > lsmod_hot.txt
dmesg > dmesg_hot.txt
Analyze line by line the differences
between the files lsmod_cold.txt and lsmod_hot.txt
between the files dmesg_cold.txt and dmesg_hot.txt
and indicate here what are the differences.
1. Differences between lsmod-cold-boot and lsmod-hot-boot not found in contents.
But the sequencing of items are diferent.
2. Differences between demesg-cold-boot and dmesg-hot-boot.
Differences found only in last some lines, as follows.
[ 17.341335] init: avahi-cups-reload main process (853) terminated with status 1
[ 18.389169] init: smbd main process (744) killed by HUP signal
[ 18.389177] init: smbd main process ended, respawning
[ 18.705049] init: samba-ad-dc main process (926) terminated with status 1
[ 20.334808] init: plymouth-upstart-bridge main process ended, respawning
[ 20.339707] init: plymouth-upstart-bridge main process (1517) terminated with status 1
[ 20.339722] init: plymouth-upstart-bridge main process ended, respawning
[ 20.466108] init: plymouth-stop pre-start process (1550) terminated with status 1
[ 20.708523] nvidia 0000:01:00.0: irq 45 for MSI/MSI-X
[ 16.090838] init: cups main process (812) killed by HUP signal
[ 16.090846] init: cups main process ended, respawning
[ 16.414244] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
[ 16.518216] e1000e 0000:00:19.0: irq 44 for MSI/MSI-X
[ 16.518319] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 16.518494] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.982531] init: samba-ad-dc main process (917) terminated with status 1
[ 18.117014] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None
[ 18.117017] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
[ 18.117049] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.499427] init: plymouth-upstart-bridge main process ended, respawning
[ 19.502056] init: plymouth-upstart-bridge main process (1454) terminated with status 1
[ 19.502072] init: plymouth-upstart-bridge main process ended, respawning
[ 19.726552] init: plymouth-stop pre-start process (1518) terminated with status 1
[ 19.917857] nvidia 0000:01:00.0: irq 46 for MSI/MSI-X
Ofcourse the last lines are same. But I just left them as they are.
Last edited by arindamsingh; 04-24-2015 at 01:33 AM.