ethernet on MSI K8N under 5.3-RELEASE amd64
I just got an MSI K8N Neo2 Platinum motherboard with an AMD Athlon 64 3000+ CPU to replace the burned out board in an older system. This board has two onboard LAN controllers. Before installing FreeBSD I wanted to get my old files off a drive running Red Hat 7.3; that drive booted, but the system was not finding the network. So I installed FreeBSD 5.3-RELEASE amd64 on the other hard drive in the system, and it still does not find the network. During installation I had an ethernet cable plugged in to one of the system's two LAN jacks, and the steps for configuring the ethernet and ethernet-over-firewire seemed to work. But I cannot see the network from that system or that system from others on my network. When the cable is plugged into that jack, ifconfig says re0: [blah, blah] status: active and when it's plugged into the other the status line is "no carrier". The fact that the interface wasn't working under Red Hat Linux 7.3 or under FreeBSD 5.3 makes me wonder if this is simply a hardware setup problem, but everything else seems to be working correctly, and while I was admittedly unsure about some of the vast array of cables, there wasn't even anything to connect for onboard ethernet (was there?). Suggestions on what I might be doing wrong either in hardware setup or with the OS are appreciated. dmesg includes the following: re0: port 0x9400-0x94ff mem 0xfb00-0xfbff irq 5 at device 10.0 on pci2 miibus0: on re0 rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto re0: Ethernet address: 00:11:09:c9:bd:3f ... stray irq7 strayirq7 arp: 192.168.23.254 is on fwe0 but got reply from 00:00:00:94:c6:e5:16 on re0 arp: 192.168.23.254 is on fwe0 but got reply from 00:00:00:94:c6:e5:16 on re0 stray irq7 too many stray irq 7's: not logging anymore ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Wine 20041201 on FreeBSD 5.3-RELEASE
(I apologize for replying to jason henson rather than the list; either his reply-to was set individually, gmail doesn't correctly respect reply-to (though it seems to in other cases), or I made an error.) Some of my response to jason and his later reply are included. > > (I didn't think that was so clear from the page.) I applied the > > patch, rebuilt, and installed my kernel, and I continue to get the > > same error. [snip] > > # patch > and got normal-looking messages about discarding junk headers and > > footers and applying patches in two spots. I checked the source file > > /usr/src/sys/vm/vm_mmap.c and found the appropriate sections updated. > > I had also edited a custom kernel config file in preparation for > > building a custom kernel anyway, and I did > > # cd /usr/src > > # make buildkernel KERNCONF=MYKERNELNAME > > # make installkernel KERNCONF=MYKERNELNAME > > (substituting the appropriate name, of course). > > The commands finished successfully, and I rebooted and got a > > functioning system without a hitch. > Looks like you did the right patch command. [snip] > Ok, first Kris responded to the thread with "It also clearly states (in > the followup) that the kernel patch is no longer needed." > > Sounds like what Kris was saying was you just needed to cvsup your > ports system and not do the patch anymore. > > "The wine-mmap.patch is no longer needed since that code has been > #ifdef'd=20 out in the wine CVS." > > So you could just rm vm_mmap.c and cvsup your source then update your > system and kernel. Depending on hold old your release is you should > read UPDATING very carefully. As I said in my original post, my ports tree was updated the day before I tried all that (which is well after the bug is listed as being closed). Since I have apparently the latest port of wine and have tried both with and without the kernel patch, I'm at a loss. I thought this may be an issue with common enough components that somebody on this list might have encountered and solved the same problem. I figured that maybe I had misunderstood about the kernel patch no longer being needed; maybe it was merged into CURRENT, but I'd have to do it myself with my 5.3-RELEASE system. Incidentally, if I should *undo* this patch (I'm not a kernel hacker; it intuitively seems that messing with the virtual memory manager, esp. w/ code marked "this is messy; somebody who knows what he's doing should fix it", could be a bad idea), I'd appreciate somebody's letting me know. > Try emailing [EMAIL PROTECTED], he's the port maintainer for wine. I will also email gerald directly. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Wine 20041201 on FreeBSD 5.3-RELEASE
I am running FreeBSD 5.3-RELEASE, Xorg 6.8.1 (portupgraded today), and KDE 3.3.3 (portupgraded today). My ports tree was updated yesterday. I am trying to run Wine, and I have the 20041201 port. The release notes say that it now runs under FreeBSD 5.3. While Wine's doc suggests that a kernel patch may be necessary, the discussion on this at http://www.freebsd.org/cgi/query-pr.cgi?pr=73092 suggests that that is not the case and that Wine itself has been patched. Incidentally, I am only bothering with all this in order to run the Party Poker client, which is listed on winehq as running (http://appdb.winehq.org/appview.php?appId=1567;whq_appdb=acc45b9fbc40a720bb99098126f77753) I successfully did # make and # make install on the wine port, and I have set up a link to a directory that functions as "c:", the subdirectories within it, and the ~/.wine/config file as suggested in the documentation. wineserver runs, but my Windows application crashes, as follows: -> wine PartyPokerSetup.exe fixme:file:get_default_drive_device auto detection of DOS devices not supported on this platform fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not available fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not available === [EMAIL PROTECTED] (/dev/ttyp3) ~/.wine/wine-c/Program Files 70 -> err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 err:msvcrt:split_oflags :unsupported oflags 0x8121 fixme:ntdll:NtQueryVolumeInformationFile device info not properly supported on this platform err:heap:HEAP_CreateSystemHeap system heap base address 0x8000 not available ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
