LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
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 05-12-2015, 07:15 AM   #31
rtmistler
Moderator
 
Registered: Mar 2011
Location: Sutton, MA. USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu
Posts: 4,110
Blog Entries: 10

Rep: Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525

Quote:
Originally Posted by JeremyBoden View Post
Does your BIOS retain the correct date/time between cold boots?
If not, then replace the BIOS battery.
Definitely a valid point to check.
Quote:
Originally Posted by arindamsingh View Post
$ sudo modprobe e1000e
(nothing reported)
$ sudo service network-manager start
(nothing reported)
What I would do in those cases would be to check the system log and see if the driver actually loaded and if the network manager also loaded. Further the network manager must have it's own log, or maybe it solely does use the system log. But I'd have checked that log to see information, be that error or success, some information should've been added to the system log when you tried these actions. In fact that's more likely that info went to the system log versus the terminal.
 
Old 05-12-2015, 02:26 PM   #32
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
Quote:
Originally Posted by rtmistler View Post
@rtmistler, 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.
What do you think now about blacklisting the driver and load it after boot? (a bit different from removing a loaded driver). I never did it. Just a guess (except blacklisting the driver make it unloadable forever in the boot session)
 
Old 05-12-2015, 03:03 PM   #33
rtmistler
Moderator
 
Registered: Mar 2011
Location: Sutton, MA. USA
Distribution: MINT Debian, Angstrom, SUSE, Ubuntu
Posts: 4,110
Blog Entries: 10

Rep: Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525
Quote:
Originally Posted by floppy_stuttgart View Post
What do you think now about blacklisting the driver and load it after boot? (a bit different from removing a loaded driver). I never did it. Just a guess (except blacklisting the driver make it unloadable forever in the boot session)
Yeah, good idea. Ultimately if you just don't load the driver until later. However, if the problem is a two-attempt initialization for whatever reason, then it would require to be initialized the first time and then re-initialized.

Part of my thinking is less that the chip was ready but instead at power on the chip needs something, the driver load doesn't quite take care of that. And then when the warm boot is done, the chip already was hit once, so the second initialization finally does work. So it really would be an iterative process.
 
Old 05-12-2015, 06:46 PM   #34
JeremyBoden
Member
 
Registered: Nov 2011
Posts: 939

Rep: Reputation: 174Reputation: 174
Maybe it's a firmware thing in which the kernel has to prepare the chip for action, before starting the driver??
Perhaps firmware gets retained for a few seconds when you do the reboot?
(I don't really understand these things).

Does
Code:
grep firmware /var/log/syslog
give anything like
Code:
May 12 10:21:27 hector NetworkManager[2644]: <info> monitoring kernel firmware directory '/lib/firmware'.
May 12 10:21:27 hector kernel: [   15.409793] r8169 0000:02:00.0: firmware: direct-loading firmware rtl_nic/rtl8168f-1.fw
It's worth looking at https://wiki.ubuntu.com/Kernel/Firmw...rmware_Used.3F

Maybe you could try inserting a "sleep 10" at the start of your init.d/networking(spelling?) script.
I did this for a different (low priority) daemon which is dependent on networking being up and running (seems to be working).

Of course, these are really just workrounds for init.d bugs.
 
Old 05-13-2015, 02:59 PM   #35
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
My analysis of dmesg:
- first difference @ 0,004: Cold 3392.442 MHz processor vs. hot 3392.137 MHz processor (same on my board) and the timer frequency the line after
- hot at 0,68s show "tty tty54: hash matches" seems to be good (not at cold; I will further search what does it mean)
- cold show no e1000e driver loading actions = no messages immediatly after "[ 1.143564] usb 1-1: new high-speed USB device number 2 using ehci-pci"
Perhaps is the loading of that driver ehci-pci driver not correctly done and it makes an issue in loading later the driver for LAN (or it blocks the loading of the e1000e driver).
So, I would try
- boot with blacklisting ehci-pci and e1000e
- load after boot ehci-pci then after e1000e
Just a guess.

Last edited by floppy_stuttgart; 05-13-2015 at 03:13 PM.
 
Old 05-13-2015, 11:11 PM   #36
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
Thanks for the help.

There are so many ideas to experiment with.
I will do one by one.

First, I am taking floppy_stuttgart's.

How to do:
> boot with blacklisting ehci-pci and e1000e
> load after boot ehci-pci then after e1000e
?

Silly to ask probably, but I do not know how to do it.
Can you please let me know?
 
Old 05-14-2015, 03:34 AM   #37
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
Please put the outputs of lspci and lsusb at cold and hot boot (attachments): I have another Idea (to check later).
Back to your question.
http://linux.die.net/man/5/modprobe.conf blacklisting is indicated inside it.
I would first test (after a cold boot):
- rmmod ehci-pci (later, we can blacklist)
- rmmod e1000e (later we can blacklist)
- insmod ehci-pci
- insmod e1000e
After each command, we should NOT see any error. If any error, please post here.

New thoughts for later.. include a waitdev=10 or waitusb=5 bootparameter (?) in order to wait for the pci usb card to comes up before the e1000e is loaded.

Last edited by floppy_stuttgart; 05-14-2015 at 04:01 AM.
 
Old 05-16-2015, 06:22 AM   #38
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
The four files lspci, lsusb on hot and cold are attached.
Also you asked me to try rmmod, insmod of ehci-pci, e100e on cold boot, before balcklisting.
They do give arrors. These output are attached as another file.
Attached Files
File Type: txt lspci_cold.txt (1.2 KB, 9 views)
File Type: txt lspci_hot.txt (1.2 KB, 10 views)
File Type: txt lsusb_cold.txt (604 Bytes, 8 views)
File Type: txt lsusb_hot.txt (604 Bytes, 8 views)
File Type: txt rmmod-insmod-output_cold.txt (464 Bytes, 16 views)
 
Old 05-16-2015, 06:59 AM   #39
JeremyBoden
Member
 
Registered: Nov 2011
Posts: 939

Rep: Reputation: 174Reputation: 174
You need root authority - try prepending those commands with 'sudo'.

BTW A good overall list of your computers abilities etc can be gotten with
Code:
inxi -Fx
There are lots of parameters e.g.
Code:
inxi -Nxx
tells you about network devices.
 
Old 05-16-2015, 05:00 PM   #40
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
Quote:
Originally Posted by arindamsingh View Post
Hi Folks,
Installed Mint-mate 17.
On the same computer, Windows 7 runs without any problem.
Thanks
Is mint 17 tested with KVM (not installed on HDD) ?
Is Win 7 on the HDD ?
 
Old 05-17-2015, 11:16 PM   #41
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
> Is mint 17 tested with KVM (not installed on HDD) ?

No, KVM is not installed in HDD. I have not tested Mint 17 with KVM.

> Is Win 7 on the HDD ?

Yes, it is a dual boot environment.

Just for curiosity:

In another similar system DELL Optiplex 9010, Mint 17 is working fine; no network problem on cold boot. The difference between this system and the one where it is working fine is:
This system has an NVidia card and an added 2GB RAM. Perhaps that is not affecting it; I do not know.
Also, I checked the Bios battery. It is all right. It is keeping the system time OK.

Last edited by arindamsingh; 05-17-2015 at 11:33 PM.
 
Old 05-17-2015, 11:32 PM   #42
arindamsingh
LQ Newbie
 
Registered: Apr 2015
Posts: 17

Original Poster
Rep: Reputation: Disabled
inxi -Fx has same output on cold and hot boots except the following lines:

On cold boot:
Network: Card: Intel 82579LM Gigabit Network Connection port: f040 bus-ID: 00:19.0
IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A


On hot boot:
Network: Card: Intel 82579LM Gigabit Network Connection driver: e1000e ver: 3.1.0.2-NAPI port: f040 bus-ID: 00:19.0
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 90:b1:1c:a1:a5:01
 
Old 05-18-2015, 06:53 AM   #43
JeremyBoden
Member
 
Registered: Nov 2011
Posts: 939

Rep: Reputation: 174Reputation: 174
I suggested inxi only as a way of getting a quick overview of your system.
I don't think it reveals anything new.

Your driver clearly doesn't function properly on a cold boot!

I don't suppose it's possible to stick another card in - perhaps a PCI one?
They are quite cheap...
 
Old 05-18-2015, 11:36 AM   #44
floppy_stuttgart
Member
 
Registered: Nov 2010
Location: Stuttgart, Germany
Distribution: Debian like
Posts: 710
Blog Entries: 2

Rep: Reputation: 68
Quote:
Originally Posted by arindamsingh View Post
This system has an NVidia card and an added 2GB RAM. Perhaps that is not affecting it; I do not know.
The NVidia card could make a voltage drop during boot which could have side effects?.
If you have an onboard grafic chip, take the NVIDIA card away and see if it works.
 
Old 05-18-2015, 12:45 PM   #45
JeremyBoden
Member
 
Registered: Nov 2011
Posts: 939

Rep: Reputation: 174Reputation: 174
One possibility is you have an underweight PSU plus
e.g. a lot of hard disks or a greedy graphics card.

These will take a power surge on initial startup - possibly causing a voltage reduction at your motherboard.

This could be a possible reason why cold boots fail but hot ones don't.
Just guessing!
 
  


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 05:07 PM.

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