Kernel Upgrade Breaks Network Connection

My server uses:
[15:48] (tunix@kulupler ~)$ pacman -Qs kernel
local/kernel26 2.6.19.1-1
The Linux Kernel and modules
local/kernel-headers 2.6.19.1-1
Kernel headers sanitized for use in userspace
for kernel. The latest kernel upgrade (2.6.19.2-1) breaks network connection after ~5 minutes from the boot. When the network connections fails, kernel says:
Jan 12 15:10:44 kulupler ADDRCONF(NETDEV_UP): eth0: link is not ready
The connection never comes either after a network service restart, nor ifconfig eth0 up/down etc... The only solution is to restart, but after ~5 min. it fails again.
So, as a solution, I just downgraded the kernel to 2.6.19.1-1 again.

The AirPort Extreme base station (AEBS) is putting your PowerBook on a separate subnet. To solve the problem, configure the AEBS so that it does not distribute IP addresses.

Similar Messages

Software upgrade breaks network connection

After upgrading the software for the Airport base station I have lost connection between my desktop unit and PB.
Prevously this worked without any problems.
The configuration is:
Cable modem connected to ASANTE 3004.
Desktop connected to ASANTE
AEB Connected via the WAN to ASANTE
PB using Airport to connect to ASANTE
eMac Connected to the ASANTE, this is seen by the desktop.
The PB sees the internet.
The Desktop sees the internet
But the PB using Airport doesn't see either of the Desktop units and vice versa.
If I connect the PB to the ASANTE with a direct ethernet cable both units see each other.
This seems to have been brought on by the upgrade to the base units software.
Can anyone suggest what might have changed as a result of the upgrade or what could be the source of the problem?
Richard Bullen
G4 MDD Mac OS X (10.4.3)
G4 MDD Mac OS X (10.4.3)

The AirPort Extreme base station (AEBS) is putting your PowerBook on a separate subnet. To solve the problem, configure the AEBS so that it does not distribute IP addresses.

Downloading iTunes Plus song upgrades problem - network connection msg

I recently upgraded to iTunes 10.1. I also purchased the iTunes plus song upgrades for most of my library. When I try to download these upgrades, I get the same message, which is something like "iTunes Network Connection Time Out". However, I have purchased new songs since and been able to download without issue. I have tried all of the following fixes with no avail.
-Uninstall and Reinstall
-disabled firewall completely
-Flushed DNS Cache
None of the above have had any impact on the problem. If I cannot fix this, I will contest the charge for the upgrade with my bank since no one at Apple has been able to help.

I am having the exact same problem. I tried contacting Apple support - I explained my problem and provided the info from running Diagnostics. What I got in return was a cut-and-paste answer about being sure to log in and check my cables, as well as " please note that the iTunes Store cannot investigate every user's connection issue". So what's the point of sending an email in the first place? I'm very frustrated - my iTunes plus upgrade was over $400, and it was billed to my credit card weeks ago while I've been trying to get this solved. I am about to call my bank as well.

Mountain Upgrade + Missing Network Connections

I just did the recent Mountain upgrade to 10.8.5 and all my printer network connections and my home network connection (which I paid to have set-up) are now missing. Please tell me there is an easy fix to this problem.
Thanks in advance.

I can't tell you there is an easy fix because I don't know what's wrong. Requires troubleshooting.
Please start by doing a Safe Boot (it does some repair stuff in the process).
To do a Safe Boot, restart or turn on the computer. After hearing the gong sound, press and hold the Shift key until you see the progress indicator. Then you can release the shift key. Safe Boot will take longer - up to ten or 15 minutes. You can confirm you are in Safe mode by seeing the words Safe Boot at top of login dialog and top of Finder.
Test your internet while in Safe mode. Let us know that result.
Now, restart in normal mode by Not pressing shift.
Again check internet and tell us the result.
If still not working, go to System Preferences, Network prefs, and tell us every thing you see in that dialog box. (left side, what's listed and what color indicator dots by each, etc.)

Kernel upgrade breaks wifi

I tried a kernel upgrade from linux-3.0.7-1 to the latest 3.2 kernel but I have an odd issue. I am using wifi on my laptop which works fine but after two/three minutes just stops working. I cannot ping my gateway anymore, but the link still seems to be up.
Does anyone know what I can do to troubleshoot this? For example, where are the logs which could give me pointers? How do I figure out what "driver" my card is using?
Has anyone had this issue before? I am using an Aspire AS3810TG-734G32n
Thanks!

ajaxas wrote:Both of you should chek what wireless driver is in use: if it's ath9k, then read this thread: https://bbs.archlinux.org/viewtopic.php?id=134374
The patches for the bug are already in 3.3-rc4 and will be in 3.2.7.
Lol, yes, I've come across that post. (and several others). Unfortunately, I'm using the rt2800pci driver. I would have to know if I was to unload &reload reload my driver.
No ath9k solution works for me. ...I did try, though.
I am already using 3.2.7 and as I said, it did get better for me but is still buggy. However, my issue (as described) is clearly a bug in the code and probably not something that cannot easily be toubleshooted on the forums. I avoided raising a bug for my particular issue before 3.2.7 because driver related wifi bugs were already being dealt with and thusfare no one else has reproduced my symptoms. If it's been fully solved for ath9k in 3.2.7 but my problem persists, than I may need to. ...it may be a related but different problem.

SLM2024 port mirroring breaks network connections

Hi all, I got an SLM2024 that I want to use with my network probe app to analyze packets, I have my network probe PC plugged into the target port and uplink to firewall's trusted port to source port of 2024. Now whenever I enable port mirroring on the 2024, I lose all network connections on the 2024, I searched around here but didn't really find my answer. If anyone's seen this before, any pointers would be great.

Hi Crash, thanks for the reply, yeah it's a similar setting on that model just with a different layout on the admin page, what I meant on the trusted port part is, I have a netscreen firewall and the trusted port of the firewall goes into the source mirrored port of the slm2024, and my PC is on the target port. And I have those mirrored with a setting for both tx and rx, whenever I enable mirroring it halts traffic from the firewall, and others that are on the 2024 like server/workstns.
But network probe works and I can see traffic. We had a cisco catalyst before and that had no problems using the span feature.

[solved...sortof]kernel upgrade breaks system

Hi, I am unable to log in to arch in any way after doing a system upgrade.
The kernel was upgraded along with a couple of other things and I now cant start X, nor get to a tty.
My target was graphical at first, then I used an install disc to disable graphical and enable multi-user.target.
multi-user.target presents me with a blank black screen
graphical.target presents me with a blank blue screen (the blue from LXDM) which flashes some boots.
Im using the xf86-video-ati driver, Will try and downgrade kernel now.
Last edited by jrussell (2012-12-21 20:36:22)

ok lts kernel works
Here is my pacman log:
[2012-12-15 11:32] Running 'pacman -Syu'
[2012-12-15 11:32] synchronizing package lists
[2012-12-15 11:33] starting full system upgrade
[2012-12-15 11:52] upgraded chromium (23.0.1271.95-1 -> 23.0.1271.97-1)
[2012-12-15 11:52] upgraded cpupower (3.6-1 -> 3.7-2)
[2012-12-15 11:52] upgraded gnupg (2.0.19-2 -> 2.0.19-3)
[2012-12-15 11:52] upgraded htop (1.0.2-1 -> 1.0.2-2)
[2012-12-15 11:52] ==> The "block" hook has replaced several hooks:
[2012-12-15 11:52] fw, sata, pata, scsi, virtio, mmc, usb
[2012-12-15 11:52] Replace any and all of these in /etc/mkinitcpio.conf with a single
[2012-12-15 11:52] instance of the "block" hook
[2012-12-15 11:52] upgraded mkinitcpio (0.11.2-1 -> 0.12.0-2)
[2012-12-15 11:53] >>> Updating module dependencies. Please wait ...
[2012-12-15 11:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-12-15 11:53] ==> Building image from preset: 'default'
[2012-12-15 11:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-12-15 11:53] ==> Starting build: 3.6.10-1-ARCH
[2012-12-15 11:53] -> Running build hook: [base]
[2012-12-15 11:53] -> Running build hook: [udev]
[2012-12-15 11:53] -> Running build hook: [autodetect]
[2012-12-15 11:53] -> Running build hook: [modconf]
[2012-12-15 11:53] -> Running build hook: [block]
[2012-12-15 11:53] -> Running build hook: [filesystems]
[2012-12-15 11:53] -> Running build hook: [usbinput]
[2012-12-15 11:53] -> Running build hook: [fsck]
[2012-12-15 11:53] ==> Generating module dependencies
[2012-12-15 11:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-12-15 11:53] ==> Image generation successful
[2012-12-15 11:53] ==> Building image from preset: 'fallback'
[2012-12-15 11:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-12-15 11:53] ==> Starting build: 3.6.10-1-ARCH
[2012-12-15 11:53] -> Running build hook: [base]
[2012-12-15 11:53] -> Running build hook: [udev]
[2012-12-15 11:53] -> Running build hook: [modconf]
[2012-12-15 11:53] -> Running build hook: [block]
[2012-12-15 11:53] -> Running build hook: [filesystems]
[2012-12-15 11:53] -> Running build hook: [usbinput]
[2012-12-15 11:53] -> Running build hook: [fsck]
[2012-12-15 11:53] ==> Generating module dependencies
[2012-12-15 11:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-12-15 11:53] ==> Image generation successful
[2012-12-15 11:53] upgraded linux (3.6.9-1 -> 3.6.10-1)
[2012-12-15 11:53] upgraded pcmciautils (018-4 -> 018-5)
[2012-12-15 11:53] upgraded perl (5.16.2-1 -> 5.16.2-2)
[2012-12-15 11:53] upgraded python2 (2.7.3-2 -> 2.7.3-3)
[2012-12-15 11:53] upgraded vim-runtime (7.3.712-1 -> 7.3.754-1)
[2012-12-15 11:53] upgraded vim (7.3.712-1 -> 7.3.754-1)
[2012-12-15 11:53] Exited with code 0
[2012-12-15 12:17] Running 'pacman -S linux-lts'
[2012-12-15 12:17] Exited with code 130
[2012-12-15 12:18] Running 'pacman -S linux-lts'
[2012-12-15 12:18] Exited with code 130
[2012-12-15 12:18] Running 'pacman -S linux-lts'
[2012-12-15 12:18] Exited with code 130
[2012-12-15 12:19] Running 'pacman -S linux-lts'
[2012-12-15 12:25] >>> Updating module dependencies. Please wait ...
[2012-12-15 12:25] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-12-15 12:25] ==> Building image from preset: 'default'
[2012-12-15 12:25] -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts.img
[2012-12-15 12:25] ==> Starting build: 3.0.54-1-lts
[2012-12-15 12:25] -> Running build hook: [base]
[2012-12-15 12:25] -> Running build hook: [udev]
[2012-12-15 12:25] -> Running build hook: [autodetect]
[2012-12-15 12:25] -> Running build hook: [modconf]
[2012-12-15 12:25] -> Running build hook: [block]
[2012-12-15 12:25] -> Running build hook: [filesystems]
[2012-12-15 12:25] -> Running build hook: [usbinput]
[2012-12-15 12:25] -> Running build hook: [fsck]
[2012-12-15 12:25] ==> Generating module dependencies
[2012-12-15 12:25] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts.img
[2012-12-15 12:25] ==> Image generation successful
[2012-12-15 12:25] ==> Building image from preset: 'fallback'
[2012-12-15 12:25] -> -k /boot/vmlinuz-linux-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lts-fallback.img -S autodetect
[2012-12-15 12:25] ==> Starting build: 3.0.54-1-lts
[2012-12-15 12:25] -> Running build hook: [base]
[2012-12-15 12:25] -> Running build hook: [udev]
[2012-12-15 12:25] -> Running build hook: [modconf]
[2012-12-15 12:25] -> Running build hook: [block]
[2012-12-15 12:25] -> Running build hook: [filesystems]
[2012-12-15 12:25] -> Running build hook: [usbinput]
[2012-12-15 12:25] -> Running build hook: [fsck]
[2012-12-15 12:25] ==> Generating module dependencies
[2012-12-15 12:25] ==> Creating gzip initcpio image: /boot/initramfs-linux-lts-fallback.img
[2012-12-15 12:25] ==> Image generation successful
[2012-12-15 12:25] installed linux-lts (3.0.54-1)
[2012-12-15 12:25] Exited with code 0
*EDIT
downgrading kernel:
[2012-12-15 12:34] Running 'pacman -U /var/cache/pacman/pkg/linux-3.6.9-1-x86_64.pkg.tar.xz'
[2012-12-15 12:34] >>> Updating module dependencies. Please wait ...
[2012-12-15 12:34] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-12-15 12:34] ==> Building image from preset: 'default'
[2012-12-15 12:34] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-12-15 12:34] ==> Starting build: 3.6.9-1-ARCH
[2012-12-15 12:34] -> Running build hook: [base]
[2012-12-15 12:34] -> Running build hook: [udev]
[2012-12-15 12:34] -> Running build hook: [autodetect]
[2012-12-15 12:34] -> Running build hook: [modconf]
[2012-12-15 12:34] -> Running build hook: [block]
[2012-12-15 12:34] -> Running build hook: [filesystems]
[2012-12-15 12:34] -> Running build hook: [usbinput]
[2012-12-15 12:34] -> Running build hook: [fsck]
[2012-12-15 12:34] ==> Generating module dependencies
[2012-12-15 12:34] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-12-15 12:34] ==> Image generation successful
[2012-12-15 12:34] ==> Building image from preset: 'fallback'
[2012-12-15 12:34] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-12-15 12:34] ==> Starting build: 3.6.9-1-ARCH
[2012-12-15 12:34] -> Running build hook: [base]
[2012-12-15 12:34] -> Running build hook: [udev]
[2012-12-15 12:34] -> Running build hook: [modconf]
[2012-12-15 12:34] -> Running build hook: [block]
[2012-12-15 12:34] -> Running build hook: [filesystems]
[2012-12-15 12:34] -> Running build hook: [usbinput]
[2012-12-15 12:34] -> Running build hook: [fsck]
[2012-12-15 12:34] ==> Generating module dependencies
[2012-12-15 12:34] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-12-15 12:34] ==> Image generation successful
[2012-12-15 12:34] installed linux (3.6.9-1)
[2012-12-15 12:34] Exited with code 0
kernel 3.6.9-1 works, 3.6.10-1 does not work, I dont know which other logs I should post?
Last edited by jrussell (2012-12-15 10:38:32)

Java update breaks network connect

The latest Java update has broken my junipe netwrok connect, anyone got any ideas?

This worked for me:
http://groups.google.com/group/macenterprise/browse_thread/thread/6368431a9c273a 53
The key is:
"This update also configures the Java web plug-in to disable the automatic
execution of Java applets. Users may re-enable automatic execution of Java
applets using the Java Preferences application. If the Java web plug-in
detects that no applets have been run for an extended period of time it will
again disable Java applets."

BT HomeHub firmware upgrade broken network connect...

whatever you guys have done with the latest firmware release on the Homehub 2 has completely messed up my dual-boot Ubuntu-Win7 installation.
Current firmware 4.7.5.1.83.3.18 (Type B)
Last Updated 21/04/11
Ever since Friday when I boot into Win7 then reboot into Ubuntu, Ubuntu cannot aquire an IP address from the router. I have to do a factory reset on the router to get an address. I've 10's of port forwarding setup and this is far from ideal.
What do I do to go back a firmware or who do I contact to get it fixed.
Its a bit pathetic TBH and I'm quite annoyed about this

I've got exactly the same (baffling) problem with my BT HomeHub 2 and Ubuntu 10.10. - worked fine last Wednesday (20th April) and won't work today (26th April). Can see the router just fine but won't connect wirelessly or wired but will connect to BT Open Zone which is enabled on my hub and a couple of other hubs nearby. The OpenZone connection is full strength (which is my hub) - none of the neighbouring connections has ever been a full strength signal. Very odd.
Checked to see if it was my Ubuntu set up by running the machine off the installation disk and got exactly the same symptoms. My HomeHub also updated its firmware some time on the 21st April so, given that nothing else has changed (my windows 7 laptop has continued to work flawlessly) I am driven to the conclusion, like other correspondents here, that the HomeHub update is the culprit.
Ubuntu is growing and it would be good to see BT do some work on this quickly.

No Network Connectivity on G4 after Tiger upgrade.

Yes, I know the machine is ancient. It's a Power Mac G4 with dual 1.25Ghz processors. Has a built in Airport card.
I did a clean install of the Mac OS the machine came with... 10.2. Airport worked fine, was able to get online.
Then, I did an upgrade to Tiger (10.4). After the upgrade ALL network connectivity is gone, cannot connect via Airport or Ethernet.
Airport card still shows up in system profiler, and the status icon is next to the time display. However, it is greyed out, and zero networks show up as being available. There are at least 5 networks available on my other Macs.
Also, Ethernet connection doesnt work either. Again, works fine when plugging the same Ethernet cable into my MacBook...works wonderfully via Ethernet. When connected directly to the Power Mac G4 however, no connectivity. No IP address at all. I've even tried doing a manual IP address, to no avail.
PLEASE HELP!!

Hi again, apply this...
The combo update for PowerPC-based Macs...
http://www.apple.com/support/downloads/macosx10411comboupdateppc.html
Does that do anything?

Slow network connection after uprade to kernel 2.6.19

Hello
Since I upgraded my kernel from 2.6.18 to 2.6.19 my connection to the net is extremely slow! Before the upgrade everything worked fine! And I haven't changed any config file.
When I ping my internal router (ping 10.0.0.1) I get sth. like the following:
64 bytes from 10.0.0.1: icmp_seq=133 ttl=127 time=391 ms
64 bytes from 10.0.0.1: icmp_seq=134 ttl=127 time=4394 ms
64 bytes from 10.0.0.1: icmp_seq=135 ttl=127 time=3383 ms
64 bytes from 10.0.0.1: icmp_seq=136 ttl=127 time=2382 ms
64 bytes from 10.0.0.1: icmp_seq=137 ttl=127 time=1381 ms
64 bytes from 10.0.0.1: icmp_seq=138 ttl=127 time=380 ms
64 bytes from 10.0.0.1: icmp_seq=139 ttl=127 time=0.280 ms
64 bytes from 10.0.0.1: icmp_seq=140 ttl=127 time=0.283 ms
64 bytes from 10.0.0.1: icmp_seq=141 ttl=127 time=0.283 ms
64 bytes from 10.0.0.1: icmp_seq=142 ttl=127 time=0.292 ms
So sometimes the rt is pretty ok and the next ping is about 100x slower.
With any other machine (gentoo, windows) I have no problems.
I checked several threads in the forum and followed every advice, but haven't found a solution!
http://bbs.archlinux.org/viewtopic.php? … nel+update
http://bbs.archlinux.org/viewtopic.php?t=27787
I have ip6 turned off and checked my /etc/hosts file. So I thought maybe it could be
a problem with the nic driver. But changing the driver (from r8169 to r1000) hasn't changed anything!
So now I really don't have a clue what the problem could be!
Any help really, really welcome!

It means you can downgrade your kernel if it's still in /var/cache/pacman/pkg.
I tried several kernels form 2.6.18 to 2.6.19.1, custom and kernel26 from repo, and still www response is horrible. It's strange, but only http protocol is broken. I have no problems with ftp, mail, torrents and others. Some websites loads normal and some of them not, especially based on mediawiki engine loads very long.
I tried many ways to solve this. I turned off iptables and almost all daemons, tested different browsers, removed browser cache and config, downgrade last upgrades, run network with dhcp and static addresses. I think it isn't dns problem, because the same reslov.conf I have on testing partition with ubuntu and it works flawlessly. My kernel doesn't have ipv6.
I'm running out of ideas now.

IPhone shuts off when I use the internet on the 3G network & I can't upgrade/restore because of network connection error. Any Help?

A few months ago, while on the 3G network, my iPhone 3GS starting turning off randomly when I was using safari or an online app and the battery was somewhere around 5-20%. When this happened the only way to get the phone back on was by fully charging it which sometimes took a few hours even. It wasn't a big deal at the time because it was infrequent and while the phone was at a low battery %. However, in the past few months, around the time I upgraded to iOS 5.1 it started happened more and more often and at higher and higher battery percentages. It is now at a point where my phone shuts off every time I connect to the 3G network regardless of what my battery life is. I have called Rogers several times to complain about this and I have been told it is because of the battery for the most part but I don’t buy it; the problem has got to be more significant than the battery alone because I can listen to music and send texts at anytime and fully use the internet when I am connected to Wi-Fi. I more recently talked to someone in tech support from Rogers who said my phone cannot support the iOS 5.1 software and that is why it is crashing. They also asked if my phone was heating up more now than in the past and it is. They said this was further evidence that my phone was couldn't handle the new software and was basically on overload. I was told to the best solution was to "Back Up" my iPhone then do a full "Restore". Here is where my next problem comes along. I cannot "Restore" my iPhone without doing an upgrade and every time I attempt to "Upgrade & Restore" an error message pops up that says "There was a problem downloading the software for the iPhone "...". The network connection timed out/was reset. -Make sure your network settings are correct and your network connection is active, or try again later". I have followed all of the protocol that is readily available online to address this problem but still no success. I disabled my firewall and anti-virus programs, I have ensured my connection is active and stable, I have upgraded to the newest iTunes, I have uninstalled iTunes and all apple programs in the correct order then reinstalled iTunes, I have disabled my DNS cache. Nothing works.
If you have any advise whatsoever please share as it would be greatly appreciated.
Thanks

I was actually able to upgrade to the newest software, iOS 5.1.1 without connecting to my computer/iTunes but rather directly through my phone when I was home on Wi-Fi. After the upgrade I plugged my phone into a different USB port at the back of my computer and was able to do a full restore. I really don't think the USB port had anything to do with it because I use the same front USB port all the time with my external hard drive and other devices wuth no problems at all; regardless of what the actual solution was, I am now able to connect to iTunes and upgrade/restore without any problems so that half of my problem is resolved.
I have yet to leave my house since doing the upgrade/restore so I am not sure if the problem with my phone crashing when I use the interent on the 3G is still an issue. I will test it today and tomorrow and give you an update.
Thanks

Cannot upgrade my ipod touch to iOS5.1 - error:"the network connection could not be established" Although I can access the itunes store.

Cannot upgrade my ipod touch to iOS5.1 - error:"the network connection could not be established" Although I can access the itunes store.
Running Mac OS 10.7.3 using itunes 10.6
unplugged other USB devices, disabled security, restarted computer. Next?

Try changing the DNS as described here:
iOS 5 update issues "Network...: Apple Support Communities

2.1 "upgrade" - lost 3G network connectivity in my apartment

hey apple are you trying to turn me against you? upgraded to 2.1 last night. now i get no signal service on the 3G network. if i turn 3G off then i get full Edge network connectivity. This is strange as there was no connectivity issue in my apartment with either network up until this "upgrade". I would love to blame AT&T but it looks like its your crap software.

Try the iPhone 3G forum. You will find more help in there.

Kernel Panics during system boot, and no kind of network connectivity

I've tried quite a lot of things here, so please read them all before you suggest something - and thanks for taking a look at my question (-:
I recently got my Mac Pro back from the AlaskaMacStore (not an actual apple retail store, and they aren't very good at that), having brought it in for loss of FW800. They sent it to Apple, and I received it back, supposedly with a new motherboard - and my FW800 working. However, it proceeded to kernel panic (complete visual system freeze, not greyscreenofdeath - oddly enough, iTunes would never stop playing during them) at least once a day after that.
Not wanting to deal with them again, I just used it like that and put up with it - but soon enough, I lost any sort of network connectivity as well. With AirPort connected to my Time Capsule's network (which worked fine on my Macbook Air and iPhone and various other devices), I was being told "...Self-Assigned IP address, and thus may not be able to connect to the internet...". Even connected directly via Ethernet to the Time Capsule, or directly via Ethernet to the cable modem, or directly via Ethernet to another Mac, or connected to another Mac's ad-hoc network, I could get absolutely no network communication going on of any sort.
This was too much for me, as all of my work requires frequent and heavy internet access, so I gave in and took it back to the local mac store equivalent - they charged me 100$, and kept it two days, just to tell me they 'couldn't reproduce the problem'. I took the Mac Pro to a friend's house, and went through the same tests - connected to his modem, with his Ethernet cords, and to his wireless and other macs. Same deal, no connection or indication of a networking being connected beyond that blasted 'self-assigned IP' in Network prefs.
Having no desire to be defrauded by the local fools again, I decided I didn't really have anything important on my internal hard drive, and decided to wipe the internals and re-install Leopard. My horrible luck continuing, I found my only Leopard disc to be cracked, prompting me to drive out and purchase a new one. Inserting this into my Mac Pro's drive, I found myself faced with yet another horrible problem.
During the boot to the Leopard DVD, the grey loading screen (with the apple logo and the spinner) simply froze with the spinner pointing left. I left it for a while, expecting this to be part of what I'd previously experienced with the slow boot-from-DVD on a Macintosh... but after 30 minutes of waiting, I got quite worried, and booted back into my normal OS by holding down Option and selecting my RAID.
Now, note this for later - it booted absolutely fine, and though I still had no network connectivity, the system had no problems. I changed the startup-disk to my RAID and then back to the Leopard DVD, naïvely thinking this would solve the problem, and ran into the same problem after restarting and booting to the Leopard DVD again.
Dismissing this as a optical drive problem (haven't had occasion to use optical media in nearly 3 years, don't really trust it in general), I booted the Mac Pro into Firewire Target Disk mode, and connected it to my Macbook Pro, and then booted the Macbook Pro from the installation DVD. Again, note carefully here - there was nothing wrong with the DVD itself, as the Macbook Pro had no trouble booting to the DVD.
I used Disk Utility to preform some planned modifications to the internal drives of my Mac Pro (erasing my previous inefficient RAID setup in favor of a new, faster (but less secure) RAID0 striped setup for my main two 1TB drives), and then proceeded to install a fresh Leopard onto the newly minted RAID. I usually cancel the 'disc checksum' that the Leopard DVD runs on itself, not really worrying about it, but in light of recent possible problems with the DVD, I went ahead and let it run - no problems, it completed and went straight into the normal install.
The install itself completed in a timely manner, and my Macbook Pro re-booted automatically, to the newly Leopard-ed RAIDed internals on the Mac Pro. It booted to the new install without a hitch, played the Leopard intro video, and continued to the setup cube. I opted to shut down (by hitting command-q and selecting the shut down option), so I could set it up on the Mac Pro instead.
Surprised was I, when I experienced the same grey loading screen freeze on the Mac Pro, booting to the newly clean install on the new RAID, that I had seen trying to boot to the Leopard disc. Worrying that my Leopard disc was, infact, corrupted in some way, I tried placing the Macbook Pro into firewire Target Disc Mode, and booting that drive over FW800 on the Mac Pro. Same freezing problem occurred.
Well, now, the only installation that HADN'T kernel panicked on boot was the old install, and that had been erased for the new RAID configuration, so I was left without a way to boot to a working install and test things from the Term. This left me with Single User Mode, which I immediately booted into.
Interestingly enough, there was no problem booting into Single User Mode - so I poked around a bit before mounting, and I had seemingly fine access to the entire filesystem of the new Leopard install, and nothing looked screwed up to my (albiet untrained) eye. After mounting and continuing the boot, it froze - but since this was verbose SUM, and not simple normal boot, I was able to see exactly where it froze: something about 'mDNSResponder starting', and then no input or output was accepted, leaving me assuming it had kernel panicked again.
To test this, I again attempted to boot from the Leopard DVD on the Mac Pro, this time in verbose startup mode, and watched it freeze up at exactly the same point. After a little googling, I found some suggestions to disable the launchd plist for mDNSResponder - I tried SUM again, and did so, then continued with the boot. This time, there was no output relating to mDNSResponder, so the launchd change had worked; however, it still froze - this time, right after three lines, first something along the lines of 'Login Window Application Starting', and then two lines printing Ethernet IDs of some sort. After those Ethernet related lines, it again froze.
What with the DNS and Ethernet bits showing up in the freezing, I was getting worried this was still tied into my NIC in some way, so I unplugged my Ethernet cords and tried the exact same boot again, and again disabled mDNSResponder. This time the only sensible thing before the freeze was the 'Login Window Application Starting' line, which seemed perfectly normal. I doubt there is/was anything wrong with that, so I'm assuming there's still some networking-related process freezing/panicking the computer, and it just doesn't happen to log in a visible way during startup.
Does anybody have any suggestion as to what such a process might be, and how I can at least pause or kill it from SUM, so I can at least finish booting the computer?
If I can't figure out a solution to this, I'll have to buy a new Mac Pro tomorrow morning... I have very, very pressing matters that can't wait for a new Mac Pro to ship, nor can they wait for me to ship this one to Apple and back (I live in Alaska, we have at least a weeks wait if nothing is seriously wrong when sending an Apple product in for repairs on our own), and nor can I wait 2 days for the local Apple store to tell me there's nothing wrong with it and then have to wait another week to, again, send it to Apple myself. I don't want to have to shell out for a new, expensive computer when there's a (most likely) perfectly good one sitting here... so any help would be MUCH appreciated.
If you've read this far, phew, you deserve a cookie. That was one... long... post.
(If you care, this post was cross-posted to my blog, at http://blog.elliottcable.name/posts/macpro_epicfail.xhtml)

Talk about bad luck.
The point at which the system "freezes" with the gray spinner (and just after the login window app starts) is right about the point the accelerated drivers should kick in for the video card.
So a couple things could be going on.
1) bad video card dragging down the bus
2) The system board is fubar - this I think is likely - issues with onboard ethernet, and whats seems to be video card related.
I would hazard to guess that the PCI-express bus has something wrong with it, ethernet and video live on the bus, SATA, and USB live in the southbridge.
So, looks like a trip to a certified apple dealer/repair center is next for your Mac Pro - probably for a new system board, again?
Something tells me that your system really didn't get to Apple for a new board.
You can verify by looking at the serial ID tag on the system board, note the rev and serial # before and after such repairs.

Kernel Upgrade Breaks Network Connection

Similar Messages

Maybe you are looking for