LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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!

Notices


Reply
  Search this Thread
Old 04-20-2015, 05:42 AM   #1
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Rep: Reputation: Disabled
no network at startup, but network after restart


Hi Folks,
Installed Mint-mate 17.
It gives message:You are now disconnected" after logging in.
I restart, the network connection comes.
It is not "networking restart", but system restart.

Tried five more times. The behaviour is every time the same.
After booting the system, no network connection. But from there I restart the system, then network connection is on.

Very irritating to always boot it second time to get the network connection up.

The computer is a desktop Dell Optiplex 9010.
On the same computer, Windows 7 runs without any problem.

Any idea how to fix it?

Thanks
 
Old 04-20-2015, 06:17 AM   #2
cheap freelancer
LQ Newbie
 
Registered: Jun 2007
Location: buybook.in
Distribution: redhat
Posts: 6

Rep: Reputation: 0
Is the service started at the time of book up?
 
Old 04-21-2015, 12:51 AM   #3
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
Yes.
NetWorkManager service started at boot time.

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.

Thanks
 
Old 04-21-2015, 04:07 AM   #4
veerain
Senior Member
 
Registered: Mar 2005
Location: Earth bound to Helios
Distribution: Custom
Posts: 2,524

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
Might be your network device is taking time to initialize. Wait for some time and then restart NetWorkManager service.
 
Old 04-21-2015, 01:22 PM   #5
ardvark71
LQ Veteran
 
Registered: Feb 2015
Location: Oregon, USA
Distribution: Lubuntu 14.04, Windows Vista
Posts: 5,150
Blog Entries: 3

Rep: Reputation: 691Reputation: 691Reputation: 691Reputation: 691Reputation: 691Reputation: 691
Hi...

Also, would you open a terminal and post the results of...

Code:
lspci -nnk | grep -i net -A2
Thanks!
 
1 members found this post helpful.
Old 04-21-2015, 02:37 PM   #6
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
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.
 
1 members found this post helpful.
Old 04-21-2015, 03:41 PM   #7
rtmistler
Moderator
 
Registered: Mar 2011
Location: Sutton, MA. USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu
Posts: 4,087
Blog Entries: 10

Rep: Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520
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.
 
1 members found this post helpful.
Old 04-21-2015, 08:26 PM   #8
DJ Shaji
Member
 
Registered: Dec 2004
Distribution: Fedora 22 (Twenty Two!), ArchLinux
Posts: 506
Blog Entries: 15

Rep: Reputation: 106Reputation: 106
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.
 
Old 04-22-2015, 12:02 AM   #9
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
lspci output
-----------------
After cold boot:
~ $ lspci -nnk | grep -i net -A2

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04)
Subsystem: Dell Device [1028:052c]
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)

After warm boot:
~ $ lspci -nnk | grep -i net -A2

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network Connection [8086:1502] (rev 04)
Subsystem: Dell Device [1028:052c]
Kernel driver in use: e1000e
-------------------
Thanks
 
Old 04-22-2015, 05:19 AM   #10
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
That bug? https://bugs.launchpad.net/ubuntu/+s...r/+bug/1268556 and follow the indicated countermeasures?
Found with google "boot issue 8086:1502 linux"
 
Old 04-22-2015, 07:38 AM   #11
rtmistler
Moderator
 
Registered: Mar 2011
Location: Sutton, MA. USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu
Posts: 4,087
Blog Entries: 10

Rep: Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520
Quote:
Originally Posted by floppy_stuttgart View Post
That bug? https://bugs.launchpad.net/ubuntu/+s...r/+bug/1268556 and follow the indicated countermeasures?
Found with google "boot issue 8086:1502 linux"
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.
 
Old 04-22-2015, 08:26 AM   #12
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
The link to "boot issue 8086:1502 linux" has the last mail from originator:

"I want to update the very first bug description. I wrote:

> After boot network interface is down. After unplugging and plugging back network cable, network is up and running again.

Network interface is not really down, it is up, but does not have IP4 address."

But here, the problem is not of getting IP. Network is not really up on cold boot. And it is up on warm boot.

I also waited for two minutes after cold boot, plugged out the ethernet cable, plugged in, restarted netwokmanager service. No network.

--just to report so that you may diagnose.

thanks

Last edited by arindamsingh; 04-22-2015 at 08:27 AM.
 
Old 04-22-2015, 08:32 AM   #13
rtmistler
Moderator
 
Registered: Mar 2011
Location: Sutton, MA. USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu
Posts: 4,087
Blog Entries: 10

Rep: Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520
My original analysis and recommendation stands.

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.
 
Old 04-22-2015, 01:26 PM   #14
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
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.
 
Old 04-24-2015, 02:32 AM   #15
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
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.

dmesg-cold-boot:

[ 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


dmesg-hot-boot:

[ 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 02:33 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu 11.10 Network Manager issues connecting to wireless network after restart depam Linux - Software 2 01-22-2012 09:39 PM
NETWORK transmit errors - assuming offline / NETWORK restart failed, could not find gcan Linux - Networking 3 11-13-2009 08:01 PM
Network interfaces do not bring up on network restart rajat Linux - Networking 1 06-20-2007 05:44 AM
In FC6 network interface doesn't come up if 'service network restart' command is run rajat Linux - Networking 2 05-03-2007 12:53 AM
Network not accessible after boot; OK after network restart chriswei Linux - Networking 5 09-22-2004 11:16 PM


All times are GMT -5. The time now is 06:16 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration