My ASUS SK8V MB has a 3Com 3C940 gigabit LAN interface on the MB. I has seen
(someplace) that this was known not to work so I plugged in a Linksys NC100
(pciid=1317:0985) which uses the tulip driver.
The Linksys NIC works fine under FC1-i386 (in fact it supported an NFS
I am still having problems creating fc1_x86_64 cdroms so I installed
taroon-amd64 just to have something. It also seemed to have problems with an
NFS install so I copied (under fc1-i386) the iso images to the harddrive and
did a harddrive install. OK, taroon-amd64 installed. Bootup and the boot
messages indicate that networking was started. However, if you try and do
anything (e.g., ifconfig) with the interface, that function hangs (and
shutdown hangs closing out the network). There appears to be a problem with
the tulip driver in 64 bit mode.
1. Does anyone know of a NIC that does work in 64 bit mode?
2. How do we go about reporting bugs for the fc1_x86_64 preview?
Gene C. wrote:
> I assumed that some hardware such as the NIC on the MB was not going to work
> but am really surprised by the interaction with the Dell 2000FP monitor.
> Given that bad values could actually destroy a monitor (according to Mike
> Harris) does not give me warm feelings about the MB.
I guess I have had somewhat better luck with my K8V (yeah, I sprung for
the 3200+/754 pin version) with FC1. Both the std FC1 32 bit version
and Justin's 2.4.22-1.2129.nptl for the x86_64 are running here quite
well...no monitor issues with a ATI 9000 and a MAG LCD altho Anaconda
didn't recognize it so I had to feed it H and V sync ranges. Anaconda
did find the SATA controller that I had turned off as I have no SATA
drives which caused some nasty messages to show up in the log but did no
real harm...and removing sata_via from modules.conf cleaned up that
I never could get a FTP install to work (it insisted on putting in an
extra \ in the url that I never could get rid of) from the boot disk but
an NFS install worked perfectly once I had the directory tree on another
The 3c2000 driver (source, at least) on the Asus site looks to be
nothing other than the driver for the full range of SysKonnect cards
...it includes everything but the kitchen sink but it works ok here...it
was used during the NFS install so, as I remember, the driver got
installed without any further intervention by me.
Davey Jones' 2.6.0 RPM does not run here though. Seems to have memory
setup issues, perhaps from BIOS, as there are slab corruption errors as
far as the eye can see. It is trying but...I've passed info along to
experts so hopefully this issue will be looked into soon. I've heard
that it does run on a Biostar board but not sure whether it was the
K8T800 or the nForce 150 version...at any rate, those both use Award
BIOS and since the northbridge is on the CPU, memory access should be
unaffected by the chipset, so it seems that perhaps Award got things
right and AMI didn't (or at least the way the developers thought they
would be). I'd be interested in hearing if others have gotten 2.6 on an
Athlon65/Opteron to run on AMI Bios.
Based on previous messages, this is a summery of current progress:
1. the floppy is working .. I had the cable in backwards (or rather
2. The BIOS Setup etc. at power-on now visible with the Dell Monitor
connected via DVI rather than analog through the KVM switch. The ASUS/AMI
BIOS must max out the video parameters rather than doing things safely. This
must have been filtered by the KVM. I can live with this. Except when I
need to fool with the BIOS Setup, I may switch back to using the KVM since it
is more convenient. I still consider the bad video parameters an ASUS bug.
3. The Linksys NIC (tulip driver) definitely hangs Linux in 64 bit mode
although it works fine in 32 bit mode. However, the onboard 3COM 3C940
gigabit ethernet NIC also works. It completely works under 32 bit Linux and
will handle the nfs install under 64 bit linux (Fedora Core 1 for the amd64).
Unfortunately, under 64 bit linux I get an "kernel Oops" enabling the
interface. Fortunately this is not MS Windows and things went merrily along
without the interface rather than getting the blue-screen-of-death.
The 3C940 driver (sk98lin) must be manually selected rather than automatically
Overall I am getting much more happy with this box, the SK8V MB, etc.
Questions -- where should I post bug reports? In bugzilla? Assigned to whom?
Fedora Core but what version?
What in the world is the issue with every single test 2.6.0 kernel
having issues with:
> FATAL: keybdev not found.
> FATAL: mousedev not found.
Could someone please explain why they appear when the mouse and keyboard
Are properly detected and everything is working just fine. I've tried
the modprobe.conf.dist and modprobe.conf to no avail.
I saw the earlier message that it doesn't matter, but still shouldn't there
be a way to get rid of the annoying kernel boot messages?
Also in this 2.6.0-0.1.14 there seems to be a very significant delay in the
just a quick heads up. I decided to test this kernel and it produced an
oops+panic on a shutdown that was attempted by pressing cntl-alt-del
from singleuser/maintenance mode.
the message was something about unable to flush buffers or unmount
filesystems. upon hard reboot there was some mild fs corruption.
I think I had been mounting something loopback previously, but I don't
remember if it was still mounted when I hit ctrl-alt-del
If I get any additional info I will try to get a proper bug report into
bugzilla but the oops didn't make it to syslog.
With the release of autofs v4, has anyone in the fedora group
considered adding it to the package list.
It helps out greatly when in an NFS/NIS environment when home
directories are automounted. As far as I can tell the 3.x version in
the distribution right now won't/can't do this.
Academia is a little like child | Parrish M. Myers
rearing, it provides a chance at | The Wacked Jester
immortality without the stretch | parrishmyers(a)yahoo.com
marks -- (unknown source) |
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.