Ethernet cable shown as "cable unplugged" on start up

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Tue Sep 13, 2016 11:28 am

An annoying, continuing problem. I am dual booting 17.3 with Windows 7 using a Gigabyte GA-890GPA-UD3H motherboard which has a built-in LAN controller by means of a Realtek 8111D chip (10/100/1000 Mbit). The Ethernet cable is always shown as unplugged when I boot up. Sometimes, it connects after 15-20 seconds, sometimes after 5 minutes, sometimes a reboot is needed. When the cable is shown as unplugged, on several occasions I have looked at the network connection via the icon in the lower right tray. It has said the last time it was connected corresponded to the time I was sitting here waiting for the connection to happen; this made me think that maybe there was a connection sometime during the boot process but that it was immediately lost [the Ethernet cable icon in the tray never showed anything other than it was unplugged].

I have all the proffered updates installed. I tried reinstalling 17.3 from scratch. I have several times reinstalled all the installed network manager related files using Synaptic Package Manager. None of that made any real difference. After some recent updates, the unplugged problem seemed to abate only requiring 15-20 seconds to say the cable was plugged in. Then it became variable and longer again.

This morning after using Mint, I had to boot into Windows for something. Then back to Mint and no connection for 43 minutes so I reinstalled all the network manager files via Synaptic. After a reboot and a longish delay, the cable was finally seen as plugged in.

BTW, the cable has always been plugged in and has not been touched during these episodes.

Is anyone else having this problem?

Any suggestions would be appreciated. I have only been using Linux for about a month so my own troubleshooting abilities are poor.

User avatar
richyrich
Level 19
Level 19
Posts: 9075
Joined: Mon May 04, 2009 8:31 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by richyrich » Tue Sep 13, 2016 12:45 pm

Have you checked your Router's settings? How long is it set to keep dhcp ip addresses? Is it showing errors for duplicate mac addresses? Many things like this can be caused by your router, not the machine.

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Tue Sep 13, 2016 3:54 pm

When the system is hanging, in the terminal :

Code: Select all

dmesg | tail
or have a look at the syslog in /var/log.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Tue Sep 13, 2016 4:13 pm

I had not checked the router logs. I just did a quick read and there did not seem to be any errors/duplicates etc. After I post this, I will look at it more closely. I would love to find something there that would get rid of this annoying issue.

Since there is only one computer that is typically on I would not have thought duplicate IP addresses would have been an issue: am I wrong in this respect?

Leases are at the default of 120 minutes. I have never lost a connection once I am connected; I just have trouble having the cable being detected as being connected.

I have another desktop machine that is not dual boot but straight Mint; it has no connection issues the odd time that I use it. Likewise, a Windows laptop that I use occasionally has no connection issues. Oh and my Android phone has no connection problems. The laptop and phone are wireless, the straight Mint machine hard-wired Ethernet.

Aside from the router being a common issue, are there any other common places that I should look?

Thanks

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Tue Sep 13, 2016 4:24 pm

Supertux:

I went to see the logs since I am currently connected just fine. This is definitely the deep end of the swimming pool for me! There is a ton of detail there that means very little to me since I am only a month into running Linux.

If I were to post that section related to my last bootup, could I impose on you to see if there was anything there that looks wrong?

Thanks

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Tue Sep 13, 2016 4:52 pm

Supertux et al,

I was trying to figure out the syslog and came across this part that I thought might point to the issue. I do not understand why about 11 lines down it says the Ethernet link was down and then that the link was not ready. Just below that. do the warnings mean anything?
----------------------------------------------------------------------------------------------------

Sep 13 14:47:35 1 NetworkManager[1205]: <info> Networking is enabled by state file
Sep 13 14:47:35 1 NetworkManager[1205]: <warn> failed to allocate link cache: (-12) Object not found
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): carrier is OFF
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): new Ethernet device (driver: 'r8169' ifindex: 2)
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): bringing up device.
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): preparing device.
Sep 13 14:47:35 1 NetworkManager[1205]: <info> (eth0): deactivating device (reason 'managed') [2]
Sep 13 14:47:35 1 NetworkManager[1205]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:0a.0/0000:03:00.0/net/eth0
Sep 13 14:47:35 1 kernel: [ 13.010943] r8169 0000:03:00.0 eth0: link down
Sep 13 14:47:35 1 kernel: [ 13.010964] r8169 0000:03:00.0 eth0: link down
Sep 13 14:47:35 1 kernel: [ 13.010997] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 13 14:47:35 1 NetworkManager[1205]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Sep 13 14:47:35 1 NetworkManager[1205]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
Sep 13 14:47:35 1 NetworkManager[1205]: <info> urfkill disappeared from the bus
Sep 13 14:47:35 1 NetworkManager[1205]: <info> ModemManager available in the bus
Sep 13 14:47:35 1 kernel: [ 13.271591] init: samba-ad-dc main process (1256) terminated with status 1
Sep 13 14:47:35 1 kernel: [ 13.810756] floppy0: no floppy controllers found
Sep 13 14:47:36 1 kernel: [ 14.417605] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
Sep 13 14:47:36 1 kernel: [ 14.426953] vboxdrv: Found 6 processor cores
Sep 13 14:47:36 1 kernel: [ 14.443761] vboxdrv: TSC mode is Invariant, tentative frequency 3214210653 Hz
Sep 13 14:47:36 1 kernel: [ 14.443765] vboxdrv: Successfully loaded version 5.0.2 (interface 0x00230003)
Sep 13 14:47:36 1 mdm[1507]: Starting mdm...
Sep 13 14:47:36 1 mdm[1526]: WARNING: Plymouth is running, asking it to stop...
Sep 13 14:47:36 1 kernel: [ 14.651090] VBoxNetFlt: Successfully started.
Sep 13 14:47:36 1 kernel: [ 14.654807] VBoxNetAdp: Successfully started.
Sep 13 14:47:36 1 kernel: [ 14.658657] VBoxPciLinuxInit
Sep 13 14:47:36 1 mdm[1526]: WARNING: Plymouth stopped
Sep 13 14:47:36 1 kernel: [ 14.664898] vboxpci: IOMMU not found (not registered)
Sep 13 14:47:36 1 kernel: [ 14.670579] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 14:47:36 1 kernel: [ 14.675182] init: plymouth-upstart-bridge main process (1544) terminated with status 1
Sep 13 14:47:36 1 kernel: [ 14.675193] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 14:47:37 1 kernel: [ 15.116935] init: plymouth-stop pre-start process (1598) terminated with status 1
Sep 13 14:47:37 1 ModemManager[901]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:0a.0/0000:03:00.0': not supported by any plugin
Sep 13 14:47:37 1 ag[1608]: mdm-superinit Starting...
Sep 13 14:47:37 1 ag[1609]: mdm-superinit Finished
Sep 13 14:47:37 1 mdm[1526]: GLib-CRITICAL: g_key_file_get_string: assertion 'key_file != NULL' failed
Sep 13 14:47:37 1 mdm[1526]: GLib-CRITICAL: g_key_file_free: assertion 'key_file != NULL' failed
Sep 13 14:47:37 1 dbus[888]: [system] Activating service name='org.freedesktop.ConsoleKit' (using servicehelper)
Sep 13 14:47:37 1 dbus[888]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Sep 13 14:47:38 1 dbus[888]: [system] Activating service name='org.freedesktop.RealtimeKit1' (using servicehelper)
Sep 13 14:47:38 1 dbus[888]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Sep 13 14:47:38 1 dbus[888]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully called chroot.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully dropped privileges.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully limited resources.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Running.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Canary thread running.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Watchdog thread running.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully made thread 1799 of process 1799 (n/a) owned by '1000' high priority at nice level -11.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Supervising 1 threads of 1 processes of 1 users.
Sep 13 14:47:38 1 dbus[888]: [system] Successfully activated service 'org.freedesktop.UPower'
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully made thread 1832 of process 1799 (n/a) owned by '1000' RT at priority 5.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Supervising 2 threads of 1 processes of 1 users.
Sep 13 14:47:38 1 anacron[1899]: Anacron 2.3 started on 2016-09-13
Sep 13 14:47:38 1 anacron[1899]: Normal exit (0 jobs run)
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully made thread 1901 of process 1799 (n/a) owned by '1000' RT at priority 5.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Supervising 3 threads of 1 processes of 1 users.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Successfully made thread 1911 of process 1799 (n/a) owned by '1000' RT at priority 5.
Sep 13 14:47:38 1 rtkit-daemon[1801]: Supervising 4 threads of 1 processes of 1 users.
Sep 13 14:47:38 1 dbus[888]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper)
Sep 13 14:47:38 1 dbus[888]: [system] Successfully activated service 'org.freedesktop.systemd1'
Sep 13 14:47:39 1 dbus[888]: [system] Activating service name='org.freedesktop.UDisks2' (using servicehelper)
Sep 13 14:47:39 1 udisksd[2027]: udisks daemon version 2.1.3 starting
Sep 13 14:47:39 1 dbus[888]: [system] Successfully activated service 'org.freedesktop.UDisks2'
Sep 13 14:47:39 1 udisksd[2027]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Sep 13 14:47:39 1

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Tue Sep 13, 2016 5:08 pm

To make it shorter, when the connection is hanging and you wait for, you can run from terminal :

Code: Select all

tail -n 50 /var/log/syslog > syslog1
You can increase the number of lines (50) if you need, and you can do it several times changing number of syslog1 to 2-3 etc.
You will find the files in your home folder.
If the ethernet is trying to connect, or anything else happens about, it will be reported there.

I just read the part of syslog which says your ethernet has r8169 driver, and i catched this :
https://linhaiting.wordpress.com/2015/0 ... ction-fix/

The post says is a wrong driver for your ethernet.
I don't know if this new driver will be listed in the packages manager or it will need a manual routine to uninstall, because it has own automatic routine, if it will not work.
Anyway, if it will not work, tomorrow i will do a better look about.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Thu Sep 15, 2016 1:15 pm

Thanks for the suggestion and link. I have downloaded the driver but before I install it I want to make a complete image of my installation just in case something goes wrong.

And since I only have a cursory understanding of Linux, I am going to see if I can tweak the software update components to get and install it for me. That will prevent the idiot behind the keyboard doing something wrong :lol:

I may not be able to do the manual install until the beginning of next week since I have been and will be busy for the next little while .

I will update here after I try the driver suggestion. Thanks!

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Fri Sep 16, 2016 11:13 am

Well I decided to just try the install without doing an image of my installation. The Mint Driver Manager said there were no proprietary drivers on the system and I could not figure out how to get it or Synpatics etc. to fetch and install the Realtek driver. So manual install was the only option.

I was able to run the Realtek driver package, it uninstalled the existing driver, did something else that I did not understand but ended up saying that two cleaning steps at the end of its process did not happen. I could not blacklist the old driver -- permission denied -- regardless of trying all the sudo commands shown on the link. When the existing driver was uninstalled, I was immediately disconnected. After the new driver 'installation' was 'complete' I was still disconnected so I reinstalled Network Manager etc and rebooted. I was connected again.

The Ethernet connection this morning was not immediate on boot-up but happened much more quickly than before. I will observe for a few days and see how it goes. My feeling is that the driver is indeed the issue.

Driver manager still says 'no proprietary drivers' so I have no idea what driver is now powering my Realtek LAN chip. Any idea how to find out?

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Fri Sep 16, 2016 12:23 pm

From the terminal :

Code: Select all

sudo lshw -c network
It will list peripherals and drivers.

If the new driver is not installed, the realtime DKMS will go on with the old one at the boot.

To have help, in case next time you must tell what are the eventuals errors you get.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Fri Sep 16, 2016 5:15 pm

Thanks for the help identifying the driver. Now I unfortunately know that I am still running the 8169 driver :cry:

When you mentioned "errors", I assume that you meant what I saw when I was trying to install the correct driver. If that is what you need, I will copy the information when I try again to install the driver; if it is something else, please let me know.

From memory, all it showed in Terminal was that some cleaning failed. But I will grab the specific information when I try again. The blacklisting failed, as I said, with "permission denied" -- no other detail -- and the sudo commands to say that I was running this as administrator achieved nothing. But I am stubborn and will try again!

The strangest part of this driver saga is that now the cable is shown as connected after about 10-15 seconds, much faster than before notwithstanding that it is the same wrong driver.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Fri Sep 16, 2016 5:33 pm

OK here is what I saw on Terminal when I tried to install the Realtek driver. My memory clearly needs to go in for a tuneup.

Check old driver and unload it.
rmmod r8169
Build the module and install
arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support
Makefile:669: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler
make[2]: *** No rule to make target `8168'. Stop.
make[1]: *** [clean] Error 2
make: *** [clean] Error 2

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Sat Sep 17, 2016 11:48 am

You can open as administrator /etc/modprobe.d/blacklist.conf and adding by yourself :
blacklist r8169
at the end.
I believe you can do the same editing /etc/default/grub in the line with "quiet splash" and updating Grub.

There's not the package binutils, you have to install for the compiler.
Also gcc 4.8-4.9 packages look to be not present or the stack protector not enabled :
https://lists.debian.org/debian-kernel/ ... 00033.html

Maybe the installation is recorded in /var/log/dpkg.log


Anyway if now ethernet goes up in 10-15 seconds and there's not other problems with the connection, the rule is :
if it works, does not touch.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Thu Sep 22, 2016 12:37 pm

I did some more reading and have concluded that my issue definitely is caused by Mint using the wrong [8169] driver rather than the one for 8168.

Tux, your advice to just live with the slow connects is good. But for some reason the 10-15 second connect seems to erratically change to longer times and then my very limited patience runs out so I reinstall all the network manager stuff using Synaptics.

With each reinstall, I am back to the 10-15 second connects. Annoying but something I can live with. Almost.

Since I am using 17.3 I thought that the driver problem might be solved by installing 18. I made a disk and booted from it to test that theory. The same wrong 8169 driver was used so upgrading would solve nothing.

I am a little leery of adding packages to Mint since I am so new to Linux which makes me afraid that I might, out of ignorance, mess up something. Consequently, I will leave that as a last ditch thing to try.

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Thu Sep 22, 2016 4:16 pm

Well jon i have a good idea to test if you can solve the matter, if you have a plain mbr or full UEFI machine which support Legacy or CSM mode and Mint installed in mbr or Legacy-CSM mode.
Do you ?
You need a spare large pendrive, double than your actual system or an external USB drive.
If you do match this conditions i will tell you how testing without harm the installed ssytem, but with the exact copy you have on the main drive,

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Fri Sep 23, 2016 3:52 pm

Tux, as it happens I have another desktop machine where I installed 17.3 as a clean install. Of course, the hardware is different than the desktop machine I use; for example, I do not know if it has the same Realtek LAN chip as this machine. That said, I am totally prepared to use that machine for whatever testing you propose.

My current Linux installation is about 10 GB? Is that the size of drive I will need?

BTW, thank you very much for helping me along with this annoying problem.

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Fri Sep 23, 2016 4:47 pm

I was meaning if this LAN troubled machine was UEFi or Mbr,

Anyway, i assume is Mbr or UEFI with the Mbr legacy.
If you have at least 32 GB pendrive ( probably it will take longer to make the copy and sometimes it's possible that you can receive some errors messages ) or external usb Drive ( quicker and in fact i used to make multiboot copy from several sytems in differents machines ), you can do this :

Open a terminal and install the Kendek ppa :

Code: Select all

sudo add-apt-repository ppa:nemh/systemback
sudo apt-get update
sudo apt-get install systemback
Start gparted and make the needed partitions on the Pen/HDD.
Write down how this partitions as are known from the installed system ( maybe sdb if you have only a main drive, sdb1 will be the first etc ).
Look at some tutorials about systemback to be aware of uou're doing.
Open the program and choose the "system copy" option and in the next form, you have to say where install the root "/" ( etc ) and the swap, you did write before.
Grub ( in Mbr-Legacy ) must be on the Pen/HDD whatever the letter is, maybe sdb.
It can happens sometime the progran does not install the grub, due by errors found in the system, it will tell you.
In that matter, download SGD2, enter the system and install by yourself.

After you boot the Pen/HD in the LAN troubled machine and you can do as many tests you want,
The copy behave as the normal system, little bit slower following the USB protocols.
It will be more slower on slow Pen/HDD.
You can use it to reinstall a broken system etc.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Sat Sep 24, 2016 8:31 am

OK now I understand what you are suggesting. However, I ran into a problem: my desktop cannot be set in the BIOS to boot from a pendrive. I have installed Virtual Box on Mint and I was wondering if I could use an install of Mint in Virtual Box to experiment with. Any advice in that regard?

As an alternative, I decided to try something else.

Since neither 17.3 nor 18 versions of Mint properly identify and install the driver for my onboard Realtek 8168 LAN chip, I tried a live DVD of the latest Ubuntu 16.04. Instant success -- it ran with the proper Realtek 8168 driver not the 8169 driver that Mint insists on using.

This suggests to me that there is something wrong in that part of Mint

supertuxkart
Level 4
Level 4
Posts: 374
Joined: Sat Jan 23, 2016 5:58 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by supertuxkart » Sat Sep 24, 2016 4:47 pm

Well, if Ubuntu 16.04 fits better, you can install.
In future you can choose Mint again, if the problem will be correct.

Maybe in Mint 18 there's a need to upgrade the kernel, if you like it's possible to make experiments in volatile mode, booting directly from HD.

I noticedin hundred posts from several forums, the DE'soften makes the difference.
Maybe in Ubuntu works and in Mint does not, but many times is viceversa, all through the DEs.

jonthesecond
Level 1
Level 1
Posts: 23
Joined: Thu Aug 11, 2016 6:23 pm

Re: Ethernet cable shown as "cable unplugged" on start up

Post by jonthesecond » Sat Sep 24, 2016 10:28 pm

Tux, I guess I was not clear in my last post. I tried Ubuntu disk to see if the proper driver would be installed. That's all. I very much prefer Mint and, so far, this exasperating problem with the wrong LAN driver has not caused me to look elsewhere. Frankly, the interface on Ubuntu was no where near as intuitive as the Mint interface.

The experimentation using the pen drive........could that be replaced by running a virtual machine ["VM"] in Virtual Box on my Mint machine? What I am thinking of doing is trying the various fixes that you have suggested in a newly created Mint VM in Virtual Box on my Mint computer. That way If I mess up anything, all I need to do is reboot the VM and the mess is gone and I am back to a clean version of the Mint VM.

The only thing that I have not been able to figure out by reading about VMs is whether the Mint VM would be using the driver within the VM or the underlying driver in my Mint computer. If the former, then this will be an ideal way to try fixes but, if the latter, it will be a useless waste of time. Can you offer any insight?

Thanks

Post Reply

Return to “Newbie Questions”