Re: Creative DI5631 pci modem on 4.5-R?
M. Warner Losh wrote: Where 0x12345678 is obtained from pciconf -l and 0x10 is the BAR. If you don't know the BAR, try 0x10, 0x14 and 0x18. None of the BAR values worked. In case anyone cares the type value returned by pciconf -l was 0x1507148d. However, I'd bet a good dinner that your Creative Labs modem is not a 16550 device. What would you like for dinner? Double or nothing if you can tell me how to make it work. :) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Panic in 4.4/4.5-STABLE
I am getting a panic while attempting to access an smbfs mounted resource. It's part of a script that I used to execute with zero problems with my xl0 and fxp0, but it panics with my nge0. Please cc me in any replies, I am not currently subscribed to stable. panic: nge_jfree: freeing buffer of wrong size! mp_lock=0001 cpuid=0 lapic.id=0100 boot() called on cpu0 Here is my ifconfig: fxp0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 inet 10.0.0.1 netmask 0xff00 broadcast 10.0.0.255 ether 00:06:29:ee:13:48 media: Ethernet autoselect (none) status: no carrier xl0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=3rxcsum,txcsum ether 00:50:04:75:4a:37 media: Ethernet autoselect (10baseT/UTP) status: active nge0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 9000 options=3rxcsum,txcsum inet 216.203.226.2 netmask 0xff80 broadcast 216.203.226.127 ether 00:40:f4:17:73:a5 media: Ethernet autoselect (1000baseTX full-duplex) status: active lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet 127.0.0.1 netmask 0xff00 Here is my dmesg: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-STABLE #1: Wed Jan 30 13:21:03 PST 2002 [EMAIL PROTECTED]:/usr/src/sys/compile/BRITNEY Timecounter i8254 frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (499.15-MHz 686-class CPU) Origin = GenuineIntel Id = 0x673 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268423168 (262132K bytes) avail memory = 257736704 (251696K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 - irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel kernel at 0xc034e000. netsmb_dev: loaded Pentium Pro MTRR support enabled Using $PIR table, 11 entries at 0xc00f1ad0 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard IOAPIC #0 intpin 18 - irq 2 IOAPIC #0 intpin 19 - irq 9 IOAPIC #0 intpin 17 - irq 10 IOAPIC #0 intpin 16 - irq 11 pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: NVidia Riva Vanta TNT2 graphics accelerator at 0.0 irq 11 fxp0: Intel Pro 10/100B/100+ Ethernet port 0x68e0-0x68ff mem 0xf6f0-0xf6ff,0xf3ffd000-0xf3ffdfff irq 2 at device 2.0 on pci0 fxp0: Ethernet address 00:06:29:ee:13:48 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: Adaptec aic7895 Ultra SCSI adapter port 0x7000-0x70ff mem 0xf6efd000-0xf6efdfff irq 9 at device 3.0 on pci0 aic7895C: Ultra Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: Adaptec aic7895 Ultra SCSI adapter port 0x7400-0x74ff mem 0xf6efe000-0xf6efefff irq 9 at device 3.1 on pci0 aic7895C: Ultra Wide Channel B, SCSI Id=7, 32/255 SCBs isab0: Intel 82371AB PCI to ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 ATA33 controller port 0xfff0-0x at device 4.1 on pci0 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller at 4.2 irq 9 Timecounter PIIX frequency 3579545 Hz chip1: Intel 82371AB Power management controller port 0xfe00-0xfe0f at device 4.3 on pci0 bktr0: BrookTree 878 mem 0xf3ffe000-0xf3ffefff irq 10 at device 13.0 on pci0 iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only smbus0: System Management Bus on bti2c0 bktr0: Hauppauge Model 44801 C110 bktr0: Hauppauge WinCast/TV, Philips NTSC tuner. pci0: unknown card (vendor=0x109e, dev=0x0878) at 13.1 irq 10 xl0: 3Com 3c905B-TX Fast Etherlink XL port 0x6c00-0x6c7f mem 0xf6efcf80-0xf6efcfff irq 2 at device 14.0 on pci0 xl0: Ethernet address: 00:50:04:75:4a:37 miibus1: MII bus on xl0 ukphy0: Generic IEEE 802.3u media interface on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto nge0: National Semiconductor Gigabit Ethernet port 0x7800-0x78ff mem 0xf6eff000-0xf6ef irq 11 at device 16.0 on pci0 nge0: Ethernet address: 00:40:f4:17:73:a5 miibus2: MII bus on nge0 nsgphy0: DP83861 10/100/1000 media interface on miibus2 nsgphy0: 1000baseTX-FDX, 1000baseTX, 100baseTX-FDX, 100baseTX, 10baseT-FDX, 10baseT, auto orm0: Option ROMs at iomem 0xc-0xc,0xd-0xd4fff on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 pcm0: CS423x-PCI at port
Re: src upgrade 4.0-RELEASE to 4-STABLE fails on make installworld...
On Wed, Feb 20, 2002 at 01:34:03PM -0500, Daniel Frazier wrote: Ruslan Ermilov wrote: We don't support upgrading from 4.0 to earlier than yesterday's 4.5-STABLE. I was upgrading to yesterday's 4-STABLE. The second time I cvsup'd was around 1500 GMT and I used RELENG_4 in my supfile. Sorry, thought I had made that clear... We can't fix bugs in already released software like RELENG_4_1_1_RELEASE. You should cvsup to RELENG_4. Don't forget to install the new kernel before running installworld if DESTDIR=/. did that too. Here's the steps I took: 1. A while back I installed 4.0-RELEASE and sorta forgot about the box for a while. 2. yesterday I cvsup'd using RELENG_4_1_1_RELEASE 3. started a make buildworld 3. read the post 4.0-RELEASE - 4.5-STABLE now possible... 4. killed the make buildworld 5. cvsup'd using RELENG_4 6. make buildworld 7. make buildkernel KERNCONF=whatever 8. make installworld KERNCONF=whatever Hope you actually did ``make installkernel''. Have you rebooted with the new kernel after this point? 9. make installworld 10. gasped in horror as the make installworld died. Also, while attempting to recover from this I noticed that almost everything in /bin had lost it's ABI type and had to be re-brandelf'd. Dunno what was up with that... Regardless, I've decided to just nuke /usr/obj and /usr/src and have another go at it. Hopefully my userland isn't too hosed to get thru it this time. On Wed, Feb 20, 2002 at 12:07:14PM -0500, Daniel Frazier wrote: Greetz all, I finally decided to bring this old box I had sitting around up to STABLE and everything went fine up to the make buildworld step. I had just cvsup'd to RELENG_4_1_1_RELEASE but and made world with those sources but then I saw the post titled 4.0-RELEASE - 4.5-STABLE now possible... and thought what the heck, I'll give that a shot... So I cvsup'd again and got up to the make installworld stage when I recieved the following error: === bin/test install -c -s -o root -g wheel -m 555 test /bin ELF binary type not known. Use brandelf to brand it. *** Signal 6 Stop in /usr/src/bin/test. *** Error code 1 Anyone know how what happened here? I'm thinking I'll re-cvsup and try again, but the make buildworld took about 6 hours so I'd rather not go thru that again if it's something that can be fixed another way. -- -- Daniel Frazier [EMAIL PROTECTED] Tel: 302-239-5900 Ext. 231 Systems AdministratorFax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin, Historical Review of Pennsylvania, 1759. -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Kylix
On Wed, 20 Feb 2002, W. Wayne Liauh wrote: Hi, I am toying around the idea of whether I should try fbsd. Among the many questions, I am wondering whether you can run Borland's Kylix under fbsd? Thanks. I downloaded the Kylix demo and ran the test script that determines whether the target system is up to snuff for Kylix requirements. Here's what it tells me: Borland Kylix System Compatibility Test Checking loaderFAILED Checking kernel = 2.2OK Checking libc = 2.1.2OK Stat: No such file or directory Checking libjpeg = 6.2.0FAILED This system is not compatible with Borland Kylix. Please see the documents in this directory for information on how to upgrade your system. This is with linux_base-6.1, however. I'm upgrading to linux_base-7.1_1 as we speak, and will report back my findings. For the curious, the accompanying documents say the following with regard to the two failures above: -- A bug in some versions of the glibc loader can cause data corruption during the dynamic loading and unloading of shared objects. The result can be spontaneous segmentation faults in unrelated programs. Kylix is particularly sensitive to this bug, and will not install if the bug is present. The loader bug has been reported to glibc's maintainers, who have incorporated a fix in glibc 2.2. Systems which cannot upgrade to glibc 2.2 require a patched version of glibc 2.1.2 or later. -- Kylix requires libjpeg 6.2 or higher. (Some, but not all, Kylix applications also have this requirement.) An RPM package for this version is provided. I don't know what the stat error is from. Maybe I'll truss to check that out too. For the record, even if Kylix doesn't work, you should try out FreeBSD. Geoff To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: src upgrade 4.0-RELEASE to 4-STABLE fails on make installworld...
Ruslan Ermilov wrote: On Wed, Feb 20, 2002 at 01:34:03PM -0500, Daniel Frazier wrote: Ruslan Ermilov wrote: We don't support upgrading from 4.0 to earlier than yesterday's 4.5-STABLE. I was upgrading to yesterday's 4-STABLE. The second time I cvsup'd was around 1500 GMT and I used RELENG_4 in my supfile. Sorry, thought I had made that clear... We can't fix bugs in already released software like RELENG_4_1_1_RELEASE. You should cvsup to RELENG_4. Don't forget to install the new kernel before running installworld if DESTDIR=/. did that too. Here's the steps I took: 1. A while back I installed 4.0-RELEASE and sorta forgot about the box for a while. 2. yesterday I cvsup'd using RELENG_4_1_1_RELEASE 3. started a make buildworld 3. read the post 4.0-RELEASE - 4.5-STABLE now possible... 4. killed the make buildworld 5. cvsup'd using RELENG_4 6. make buildworld 7. make buildkernel KERNCONF=whatever 8. make installworld KERNCONF=whatever Hope you actually did ``make installkernel''. Have you rebooted with the new kernel after this point? that should have been make installkernel KERNCONF=whatever... no, I did not reboot or drop into single user mode. 9. make installworld 10. gasped in horror as the make installworld died. Also, while attempting to recover from this I noticed that almost everything in /bin had lost it's ABI type and had to be re-brandelf'd. Dunno what was up with that... Regardless, I've decided to just nuke /usr/obj and /usr/src and have another go at it. Hopefully my userland isn't too hosed to get thru it this time. On Wed, Feb 20, 2002 at 12:07:14PM -0500, Daniel Frazier wrote: Greetz all, I finally decided to bring this old box I had sitting around up to STABLE and everything went fine up to the make buildworld step. I had just cvsup'd to RELENG_4_1_1_RELEASE but and made world with those sources but then I saw the post titled 4.0-RELEASE - 4.5-STABLE now possible... and thought what the heck, I'll give that a shot... So I cvsup'd again and got up to the make installworld stage when I recieved the following error: === bin/test install -c -s -o root -g wheel -m 555 test /bin ELF binary type not known. Use brandelf to brand it. *** Signal 6 Stop in /usr/src/bin/test. *** Error code 1 Anyone know how what happened here? I'm thinking I'll re-cvsup and try again, but the make buildworld took about 6 hours so I'd rather not go thru that again if it's something that can be fixed another way. -- -- Daniel Frazier [EMAIL PROTECTED] Tel: 302-239-5900 Ext. 231 Systems AdministratorFax: 302-239-3909 MAGPAGE, We Power the Internet WWW: http://www.magpage.com/ They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin, Historical Review of Pennsylvania, 1759. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: syncache patch
Mike Grissom wrote: Where can I find the patch for the syncache bug that causes the systems to reboot for no reason? I see alot of posts about the patch, but no url for it. And I also see that it was supposed to be submitted to cvs a couple days ago. Thanks! It just went in: jlemon 2002/02/20 08:48:49 PST Modified files:(Branch: RELENG_4) sys/netinet tcp_syncache.c Log: MFC: r1.11, r1.12; fixes for stale tcb pointers. Revision ChangesPath 1.5.2.5 +6 -1 src/sys/netinet/tcp_syncache.c To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe cvs-all in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: 3ware 6xxx-series controllers and 6.9 firmware
OK, while trying this patch out, I have found the following: * The patch applies to RELENG_4 with some errors, but it compiles and installs just fine. * with the patch and the OLD firmware, buildworld works as expected. I can also stress the box just fine with 20 bonnies running at the same time in the background each writing to a file the size of all the RAM. * The patch will work with the previous version of the firmware I have been using, but the 3dm util complains a bit and I am now unable to download the extended error_log on the Alarms page. e.g. dmesg | grep -i twe twe0: 3ware Storage Controller port 0xe000-0xe00f irq 15 at device 10.0 on pci0 twe0: 2 ports, Firmware FE6X 1.00.43.003, BIOS BEXX 1.04.00.009 twed0: RAID0, Normal on twe0 twed0: 58819MB (120462848 sectors) e.g. when I start up the 3dmd program I see baycrest# ./3dmd Error: ioctl(3/0x800c5469 0x402/0xc) failed: Invalid argument. Error: ioctl(3/0x800c5469 0x406/0x2) failed: Invalid argument. baycrest# Error: ioctl(4/0x800c5469 0x402/0xc) failed: Invalid argument. Error: ioctl(4/0x800c5469 0x406/0x2) failed: Invalid argument. baycrest# And browsing through the daemon's web pages, it generates a series of errors/warnings as well twed0: controller error - aborted due to system command or reconfiguration (flags = 0x16) twe0: TWEIO_GET_PARAM failed for 0x402/0xc/8 twed0: controller error - aborted due to system command or reconfiguration (flags = 0x15) twe0: TWEIO_GET_PARAM failed for 0x406/0x2/16 twed0: controller error - aborted due to system command or reconfiguration (flags = 0x16) twe0: TWEIO_GET_PARAM failed for 0x402/0xc/8 twed0: controller error - aborted due to system command or reconfiguration (flags = 0x15) I am going to try the firmware upgrade now and see how it works. ---Mike At 03:35 AM 2/18/02 -0800, Michael Smith wrote: As several people have pointed out, the 6.9 firmware update from 3ware is causing problems with the 'twe' driver. I have a version of the driver working with the 6.9 firmware which folks encountering problems are encouraged to test. I've rolled most but not all of the changes from the Linux 6.9 drivers in; some will require more testing and/or may not be useful. Please try: http://people.freebsd.org/~msmith/RAID/3ware/twe.releng_4.diff http://people.freebsd.org/~msmith/RAID/3ware/twe.current.diff and let me know how you go. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
USB SM
I recently acquired a SanDisk SDDR-55 Smart Media reader. The SanDisk SDDR-31, reading CompactFlash, is obviously supported (I've been trying to learn the usb code for a week now). Backlogs on the stable list say that the SDDR-31 is supported because SanDisk actually contacted the linux USB team... however, a quick perusal of the SanDisk site says that the SDDR-55 is not umass compatible, although it works in OS X. So, seeing as the SanDisk SDDR-55 is not supported by umass, would it need its own driver or am I going to have more luck getting a smart media reader that uses ATA (and, thus, is the umass compatible), unless none exist? So I guess the question is, does SmartMedia preclude umass? If not, I'd be willing to put the time in to see getting a SmartMedia card driver for bsd to come to fruition, unless someone more qualified wants to take on the task. -Max Shron To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: USB SM
Max Shron [EMAIL PROTECTED] types: So, seeing as the SanDisk SDDR-55 is not supported by umass, would it need its own driver or am I going to have more luck getting a smart media reader that uses ATA (and, thus, is the umass compatible), unless none exist? Yes and yes and no. So I guess the question is, does SmartMedia preclude umass? The Fuji SM-R2 is a umass cmopatible smartmedia reader. There's at least one other available, but that's the one I've got. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Panic in 4.4/4.5-STABLE
Post the stacktrace, and also post the size that nge_jfree() was called with. I see this call to nge_jfree(cf0581d0,0). Is cf0581d0 a pointer to the location of the first parameter of nge_jfree() ? How do I view this value in DDB ? Here's the stacktrace: panic: nge_jfree: freeing buffer of wrong size! mp_lock = 0001; cpuid = 0; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x34: movb$0,in_Debugger.627 db trace Debugger(c0253ea) at Debugger+0x34 panic(c0272b60,c0a74000,d0d6ed04,c010735,cf0581d0) at panic+0xa4 nge_jfree(cf0581d0,0) at nge_jfree+0x2f m_free(c0a74000) at m_free+0x55 m_freem(c0a73f00,c3c1e500,d0d6ed34,c0262941,c3c1e534) at m_freem+0x12 md_done(c3c1e534,c3c1e510) at md_done+0x13 smb_rq_done(c3c1e500) at smb_rq_done+0x19 smb_t2_request_int(c3b1e980,c31e99c,c3aec24c,d0d6edd8,c023779b) at smb_t2_request_int+0x61b smb_t2_request(c3b1e980,c3b1e99c,1,c3b1e99c,c3b61200) at smb_t2_request+0x2 smbfs_smb_statfs2(c3b61200,c3aec24c,d0d6edf8,c3aec200,c3aec24c) at smbfs_smb_statfs2+0x57 smbfs_statfs(c3aec200,c3aec2c,d0d47780) at smbfs_statfs+0x6f fstatfs(d0d47780,d0d6ef80,280f66e4,3,5) at fstatfs+0x56 syscall2(2f,2f,2f,5,3) at syscall2+0x3d Xint0x80_syscall() at Xint0x80_syscall+0x2b To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: random crashes on 4.4-S - ASUS CUSL2-M mobo
At a certain time, now past, mikea spake thusly: On Thu, Jan 17, 2002 at 11:52:09PM -0500, Eric L. Howard wrote: Mike Andrews wrote: Temperature? Can you run a temperature/fan-rpm/whatnot monitor, such as healthd? Yes...if only I could compile... 8--snip I've moved everything off the server so I've got a little playing room/time. I did catch this just before the box died earlier: vm_page_remove: page not found in hash It's about one chance in 10^googolplex of _not_ being a hardware problem. Do you have a different mobo that you can slide under the CPU(s), RAM, cards, etc.? Can you put the box out on a table and to a fingertip temperature check of things during operations? Have you tried dis- and re-connecting/inserting _EVERYTHING_, on the premise that it might be an intermittent connection triggered by vibration? Can you swap in a new power supply? Got any cooling spray? If yes (a can of compressed air for cleaning things will work), try cooling down specific components, one at a time. Do the same thing with a heat gun or hair dryer. Tap the board gently to try to isolate bad solder joints. At this point, it's grab-at-straws time. And, of course, the serial console idea is a good one. Keep us posted. OK...after much tapping, shaking, stirring and straw grabbing, I wasn't able nail down the issue directly. The only other mobo was put at work in another server and no 1U power supplies at hand. At that point, I was told I didn't have anymore time to play w/ the unit. I RMA'd it and they ended up replacing mobo, RAM and power supply. Been up for days (that's a big achievement for this box) now w/o a single hiccup. Thanks to everyone for your time and suggestions. ~elh -- Eric L. Howard e l h @ o u t r e a c h n e t w o r k s . c o m www.OutreachNetworks.com313.297.9900 Advocate of the Theocratic Rule To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
PC-Card
I have been running 4.5-PRERELEASE on my little laptop until recently. This had the problem that it would only boot with the pc card routing set to ISa, and then it would not talk to any cards as it appeared not to be able to get any data from them. I just upgraded it to -STABLE and both problems have gone away. Cards work fine both with ISA routing and PCI routing. Excellent, good work Warner! -pcf. [for reference this is a Palmax PD-1100 based on that integrated Cyrix chipset thing, which causes a lot of problems] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: PC-Card
In message: [EMAIL PROTECTED] Pete French [EMAIL PROTECTED] writes: : I just upgraded it to -STABLE and both problems have gone away. Cards work : fine both with ISA routing and PCI routing. Excellent, good work Warner! You are welcome. Hope that I don't break you again with 5.0. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Is vmnet broken in 4.5?
At 11:38 AM +0300 2/19/02, Eugene Mitrofanov wrote: Hi. My vmware2 use netgraph bridge to access the network. Under 4.4 all work fine. But after upgrade to 4.5 I got some trouble. I can't see my FBSD box under vmware, but all other boxes in network work fine. I can't ping from FBSD box to vmnet1 address. It seems, vmware guest OS can't get arp address of FBSD. I do not know enough to help with the problem you are seeing, but I thought I would mention that I am running vmware2 on a freebsd-4.5 system, and it is working for me. I follow the 4-stable branch, so I have been rebuilding my system every few weeks. It may be that I had to do special steps at some point to keep vmware2 working, but I don't remember what those would have been. I do remember that at some point I had to rebuild the port. I am using netgraph bridging too. So, it is possible for vmware2 to still work under 4.5-release. It is not completely broken. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
