From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: 2.6.28-git forcedeth dead interface and nvidia problems
Date: Thu, 01 Jan 2009 04:55:28 +0000 [thread overview]
Message-ID: <495C4CC0.1040006@blueyonder.co.uk> (raw)
2.6.28 works fine. 2.6.28-git1/3 only eth0 nVidia Corporation MCP55
Ethernet (rev a2) connected, using forcedeth driver, no light from the
card/switch. Checking ifconfig and route -n says the network is
correctly configured. In order to get the network back, I have to power
off/on and boot up 2.6.28. It seems to leave a permanent condition, so a
reboot to 2.6.28 does not get it working again.
Except for the additional config changes/options presented in
2.6.28-git, the kernels are configured the same, no network config
changes made.
Using openSUSE 11.2 Alpha0 x86_64 dual-core 6000+.
JUST FOR INFORMATION, but I'd be surprised if the two problems aren't
linked in some way.
=====================
The NVidia driver 180.18 works fine with 2.6.28, but fails with
2.6.28-git. The module builds and installs fine, Xorg.0.log says:-
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): Setting mode "1280x1024"
(EE) NVIDIA(0): Failed to allocate video memory
(EE) NVIDIA(0): *** Aborting ***
Fatal server error:
AddScreen/ScreenInit failed for driver 0
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
next reply other threads:[~2009-01-01 5:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 4:55 Sid Boyce [this message]
2009-01-02 4:32 ` 2.6.28-git forcedeth dead interface and nvidia problems Valdis.Kletnieks
2009-01-03 0:07 ` Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=495C4CC0.1040006@blueyonder.co.uk \
--to=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.