Re: VMWare build failure
On Thu, 2003-11-20 at 12:38, Ben Paley wrote: Hello all. I think this is a -current issue. When I started using -current I began to get weird behaviour from vmware2: eventually every time I powered on the virtual machine the screen would freeze up so I couldn't get a console, and then the whole machine - the REAL machine, I mean - would reboot. Bit rubbish, huh? [snip] -I. -I@ -I@/../include -I/usr/include -finline-limit=15000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/freebsd/driver.c /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/freebsd/driver.c: In function `cleanup_module': /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/freebsd/driver.c:284: warning: unused variable `retval' /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only/freebsd/driver.c:301:35: i386/isa/intr_machdep.h: No such file or directory *** Error code 1 Stop in /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only. *** Error code 1 Stop in /usr/ports/emulators/vmware2/work/vmware-distrib/vmmon-only. *** Error code 1 Stop in /usr/ports/emulators/vmware2/work/vmware-distrib. *** Error code 1 Stop in /usr/ports/emulators/vmware2. *** Error code 1 Stop in /usr/ports/emulators/vmware2. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall6065.18 make ** Fix the problem and try again. ** The following packages were not installed or upgraded (*:skipped / !:failed) ! emulators/vmware2 (missing header) First off if you're running -CURRENT you want emulators/vmware3, missing header would conclude you don't have the header installed that it wants. Guessing you're running -CURRENT you have the kernel source installed, so my suggestion is to run vmware3. Unless you have a specific reason to run 2? -- I think we ought to be out there doing what we do best - making large holes in other people's countries. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recovery? recent make world rendered system unusable (64 bit change)
On Tue, 2003-11-18 at 08:50, Chris Shenton wrote: I've been running 5.1-CURRENT for a while and a couple nights ago did a make world. After a couple hours building, my system was unusable. Critical binaries like rm, ls, mtree, sh failed, reporting Exec format error. I can't login, not even single user. I can no longer even boot single user. I've hosed my system and am looking for a way to recover without having to reinstall everything and overwrite critical data and system config files. Naturally, I only discovered the note in UPDATING after I trashed my system -- in fact, I read it from the OK boot prompt with its more. Doh! 20031112: The statfs structure has been updated with 64-bit fields to allow accurate reporting of multi-terabyte filesystem sizes. You should build world, then build and boot the new kernel BEFORE doing a `installworld' as the new kernel will know about binaries using the old statfs structure, but an old kernel will not know about the new system calls that support the new statfs structure. [...] Running an old kernel after a `make world' will cause programs such as `df' that do a statfs system call to fail with a bad system call. [...] DO NOT make installworld after the buildworld w/o building and installing a new kernel FIRST. You will be unable to build a new kernel otherwise on a system with new binaries and an old kernel. I'm looking for recommendations on how to recover, hopefully without trashing my critical system files like /etc/passwd. Ideally, I guess I'd like a way to replace all the broken binaries and any related libraries without overwriting other files. If I do a floppy-based install and then select Custom/Expert than request a minimal install, I presume it will install a small set of binaries but also overwrite /etc/passwd, /etc/ssh/* and so on. Is there a way to have it just update binaries and libraries? If I have to, I could add another disk to this box. Then I could do a floppy install of 5.x on to that new disk. Then I could boot it, and mount the old disk's partitions. Then install the new install's binaries on the old partitions. Or perhaps I could do a make buildworld, kernel, installworld the proper way, using the old disk's partitions as the target. Or could I -- somehow -- push a 64-bit-aware kernel onto this box so that the newly broken binaries will work again? How? Again, I've got no shell access any more so everything's gonna have to be done from floppy or maybe CD if I can borrow a burner. Naturally, this is my net boot server for my diskless clients so I can't go that route either. :-( Any other suggestions? Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] Best suggestion would be to get a 5.0-CURRENT live CD off of current.snapshot.org with the kernel with the new statfs changes if it exists (I forget if we make live CD's daily or not) That or you can loadup a emergency holoshell of 5.1 RELEASE, reinstall /bin /sbin /usr/sbin etc and then rebuild the kernel to the new statfs kernel, then install the new world once again. The basic problem is you need a kernel with the new statfs changes, maybe you can find someone nice enough here to email you their kernel with the new changes that'll boot on your computer, and then you can get it corrected. Even I had that problem, luckily the machine was just a test machine so reinstallation wasn't going to kill me. Scott -- I think we ought to be out there doing what we do best - making large holes in other people's countries. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: recurring installworld problem
On Mon, 2003-11-17 at 16:19, Aron HÃ¥kanson wrote: Tis 2003-11-18 klockan 00.25 skrev [EMAIL PROTECTED]: Hey all... Been trying to get 5.1-CURRENT installed since thursday. This is my procedure: cvsup make buildworld make buildkernel make installkernel -- reboot -- make installworld This is the error I've been getting (probably 25x since thursday... yes.. 25 fresh installs since then) ... /usr/src/bin/csh/../../contrib/tcsh/complete.tcsh /usr/src/bin/csh/../../contrib/tcsh/csh-mode.el /usr/share/examples/tcsh gencat -new et_EE.ISO8859-15.cat et_EE.ISO8859-15.msg gencat:No such file or directory ... Yes, I must use -CURRENT because that apparently is the only way for me to use the multi-ip jail patch. However, these errors occur without the patch. Once I successfully bring the box to 5.1-CURRENT, then I'll try the patch. My goal now is to just get -CURRENT up and running. Any ideas? If you're just interested in finishing the installworld you can do it quick by touch(ing) /usr/src/contrib/tcsh/et_EE.ISO8859-15.msg so gencat will find its msg-file. Aron HÃ¥kanson Comitor Konsult http://www.comitor.se/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] Too bad finishing it only leads to more problems. Suddenly ls core dumps, hell everything does. anything that's dynamically linked core dumps on my Dual P2-450, nothing useful on the backtrace. Quite fun as i'm trying to get everything straightened out. not quite sure how to, since even 'install' core dumps. -- I think we ought to be out there doing what we do best - making large holes in other people's countries. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Radeon DRM-Problem
On Fri, 2003-11-07 at 13:23, Ralf Folkerts wrote: Hi, I have a Problem with DRM (Radeon) on my Current-Box. I cvsuped and made my last buildworld/-kernel/installkernel/-world last week (Oct 31). FreeBSD penguin.home.folkerts-net.de 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Oct 31 20:04:27 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PENGUINKERNEL i386 From this List I think this Problem should have been fixed a while ago?! When starting X I get agp0: binding memory at bad offset 0 error: [drm:pid704:radeon_cp_init] *ERROR* radeon_cp_init called without lock held error: [drm:pid704:radeon_unlock] *ERROR* Process 704 using kernel context 0 on the Console. When I then shutdown X and start it up again I don't get any display any longer (however, the machine still works and i.e. can be shutdown -r now, but w/o seing anything until the reboot). Pls note: Except for these Problems (Lock when restarting X and no DRM) X runs nice and w/o any other Problems! Does anyone have a hint? Did I shred my Config(s)? Or is this a real Problem? Thanks, _ralf_ Sounds like a problem with your AGPGART possibly. What AGP Gart would you be using? Intel? Via? ALI? SiS? NVidia? Please god don't tell me Nvidia. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Radeon DRM-Problem
On Fri, 2003-11-07 at 14:12, Ralf Folkerts wrote: Hi Erik and Scott, The agpmessage, however, is something I haven't seen or heard about before. What does dmesg| grep agp say? the Board uses an Intel Chipset; here's the dmesg | grep agp... agp0: Intel 82815 (i815 GMCH) host to PCI bridge mem 0xd800-0xd9ff at device 0.0 on pci0 (This is w/o starting X after boot ;-)) Btw: I'm also running Linux (Gentoo) on that box (dual-boot). However Gentoo's DRM just works fine... Any hints are welcome; however, as I also have a 4.9 box running STABLE I can just live with that Problem :D _ralf_ Do you happen to force it to AGP 4x? or 1x? or don't even try? ie. Options AGPMode 4 in XF86Config ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Intel I440GX+
Hi, I have a test server here that runs -CURRENT, just cvs'd to the latest and greatest. Well, it doesn't seem to like my ACPI is my guess. Once it display's the motherboard's ACPI it panic's and reboots. I'll have to of course go back to an old kernel since I stupidly tookout the debugger. This isn't my normal email address also so if you could send reply's to this email address. I was wondering most of all if anyone else with an Intel I440GX+ P2-450 roughly was experiencing problems? Onboard SCSI, 1gig of ECC, dual P2-450's. Never had this problem before. Quite rare. Thanks -- Scott Likens [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel I440GX+
On Thu, 2003-11-06 at 03:27, Tom wrote: On Thu, 6 Nov 2003, Scott Likens wrote: ... Onboard SCSI, 1gig of ECC, dual P2-450's. Never had this problem before. I hope you are using P3s, or Xeon CPUs not P2s, since P2s are not able to cache memory above 512MB, which means that things will be real slow. No, Dual P2 Xeons. Thanks but no thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel I440GX+
On Thu, 2003-11-06 at 21:09, RMH wrote: Roberto de Iriarte wrote: Scott Likens wrote: On Thu, 2003-11-06 at 03:27, Tom wrote: On Thu, 6 Nov 2003, Scott Likens wrote: ... Onboard SCSI, 1gig of ECC, dual P2-450's. Never had this problem before. I hope you are using P3s, or Xeon CPUs not P2s, since P2s are not able to cache memory above 512MB, which means that things will be real slow. No, Dual P2 Xeons. Hmmm ? Are you sure ? I own an L440GX+ and Xeon's do not fit on it. You might have either an MS440GX or a C440GX, the former being a workstation board (with AGP), the later an entry level server board if there are PII Xeon CPU's on it. Only first PIIs had L2 cache which was unable to store data located beyond 512Mb memory boundary (233-300MHz, Klamath), and some of them even didn't support ECC for L2 cache. All the next PIIs (333-450MHz, Deschutes) had L2 cache with ECC, capable of all 4Gb. So PIIs are not so bad as some people may think. Besides, L2 cache of PIIXeons and some PIIIXeons (Drake Tanner) is slow because it is off-core, regardless of running at full core speed. --- Regards, Rhett Also to note, that now the computer boots again with the madt.c 1.4.4 Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Software RAID
On Thu, 2003-10-30 at 16:22, Steve Lee wrote: Does FreeBSD support Software RAID ? if so, what can it do ? RAID 0, 1, 5 ?? also would it be able to mirror the root parition ? Thanks. any advice would be cool. http://www.freebsd.org/handbook There's always good stuff in there about everything, as far as raid, 0, 1, 5, I imagine 0+1, 10, prolly the only thing it lacks is JBOD. But as far as your 'root' partition that I don't think so, mirroring the root partition usually isn't worth it anywho. Since the root partition is typically 250megs for / and yeah you can mirror /usr /var, etc with vinum (mdconfig) or you could use ccd if you wish. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-Current and XFree86
On Thu, 2003-10-23 at 17:00, James Tanis wrote: Attempted this, first did a deinstall of XFree86-Server and then built/installed XFree86-Server-snap. It built and installed perfectly fine, from what I can see it runs fine too.. but I get the same error. You weren't wrong, in the log once of the supported cards listed is the ATI Radeon 9800 NH (AGP), although I have no idea what the NH stands for. The only problem is I'm getting the same exact error I was previously.. From the log file: (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) No devices detected. I did not attempt any different settings from the norm at this time since, if my memory serves me right this is the same exact error I was getting before and nothing I tried seemed to fix it. Here is the device section as it is now for my radeon 9800, these are the same settings that I used to use and worked perfectly fine with my radeon 7000, although I have tried a config without the extra options it did not seems to help nor is their any reason that I can think of that these options would not work with the 9800. Section Device Identifier Radeon 9800 Driver radeon #VideoRam131072 # Insert Clocks lines here if appropriate Option AGPMode 4 Option AGPFastWrite 1 Option EnablePageFlip1 EndSection My problems seem to stem from the fact that the driver has no idea what to do with BusID PCI 1:0:1 which may or may not be the actual device that I want to be using.. I have no idea what to do about it though. This is a plain vanilla ATI Radeon 9800 (AGP) not a pro or some other upgraded/downgraded version.. I would think this would be supported by the driver. Thanks again for any input, James. At 05:12 PM 10/23/2003, Eric Anholt wrote: On Thu, 2003-10-23 at 13:59, James Tanis wrote: I'm having problems with XFree86 that result from the fact that the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I would like to upgrade to current/cvs version of XFree86, 4.3.99 since the next release isn't going to be for around another 2 months. My question is, what is the most flawless way to do this? Is there a FreeBSD concentric repository, or should I just get the sources from the standard XFree86 cvs repository? Is there a place where I can instead get frequently updated ports of the repository? Building from source is there any configure switches that I need to successfully build? Last but not least is it possible to build only the radeon drivers and use those in 4.3.0.. if so, how do I go about doing that? I had some problems when I only downloaded the graphics drivers module. Thanks for any Please use XFree86-4-Server-snap if you are looking for CVS X Server. The snap is slightly out of date due to problems getting 4.2.99.14 building (the monolithic nature of XFree86 is a major issue for maintaining these ports), but it should include radeon 9800 support. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] James Tanis Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] I may be well out of my league here, but if memory serves you prolly will require DRI HEAD to run, that or XFree86 CVS. Maybe Eric knows better, but that's off my recolection with ATI experience. Requiring the DRI head, that or you can install the drivers from the linux distro, and just not the kernel driver for obvious reasons. I have been known from time to time to use the ATI linux modules in FreeBSD, works quite well actually. Just a thought for you to try. You'll either have it work, or maybe a hard lock or no luck. 50/50 Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA drive lock-up
On Mon, 2003-09-22 at 06:54, Derek Ragona wrote: I couldn't make a kernel with 9/19 cvsuped. I downloaded and installed the 9/20 snapshot. That also wouldn't complete a buildworld without breaking with the hard drive error. I booted windows and stress tested the drive with all kinds of I/O. Not a hiccup. It isn't the hardware, it has to be the driver code under 5.1-current. -Derek Okay, this is off the subject here on this. But I wanted to comment, Just because something 'works' in another OS doesn't mean it's working right. Just because my VIA KT133A chipset doesn't hiccup in Windows, doesn't mean it's not broken. Just because I get Data corruption in FreeBSD due to my KT133A chipset, doesn't mean it's FreeBSD's fault. Infact, you'll find FreeBSD and other accompany'ing OS's that are GNU/GPL/BSD licenesed to have a more strict driver set. They can show you things you wouldn't normally see in other OS's so to speak. As i said this is off topic, but saying But it works in Windows, is like saying But i'm a complete idiot who doesn't have a friggen clue how to help. Don't take this at all personally, it's just that i've hung out in the usenet groups, and irc channels long enuf to see the same thing over and over again. So I wanted to stop this trend before it started. From my personal experience, if you want something fixed with any Free OS you need to give the person who's fixing the problem as much information as possible. In otherwords, turning on all the debugging features, including DDB and trying to help them delve into it and find out what the exact problem really is. It maybe a problem with the controller, maybe the drive, maybe your system. At any rate, you're other OS *cough* does work properly. That doesn't mean that the driver in that other OS isn't correcting a hardware issue on the controller that was seen after manufactering. Infact it's quite common to see Defects after manufactering that the driver does correct. So please bear in mind a few things, One, everyone here does this for the Love of FreeBSD, Two, it's free. So in essence you get what you pay for, We do what we can to bring you the best damned Free OS possible. But we don't always have the resources to get all the information possible to create the drivers. Some Hardware Manufacter'ers are more then willing to give us specs and hardware to test their hardware and help us write drivers. Others are flat out do it yourself. Then you have even to the more extreme where they don't want us to write drivers. So, if you could please get as much information possible as to why? It may mean your system working properly and not. Sincerely, Scott M. Likens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network problems
On Sat, 2003-09-20 at 15:10, Cameron Murdoch wrote: I have a strange problem with my Dell Inspiron Laptop. The network card will stop responding to all network traffic. This happens very regulally, though without any obvious pattern. Sometimes it only appears as slight packet lose though normally the network connection goes completly. But then at other times the connection stays up for a resonable time. I have tried different cables, hubs, etc but to no avail. Link status doesn't seem to get dropped, only IP. When the connection gets dropped doing an ifconfig down/up on the interface does ? Unplugging and then inserting the network cable will restore the connection for at least a few seconds. I am running a recent current: FreeBSD opal.macaroon.net 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Sep 19 21:59: 12 BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/OPAL i386 The network card is an integrated intel card, (fxp0): fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet 10.1.10.200 netmask 0xff00 broadcast 10.1.10.255 ether 00:20:e0:69:50:3c media: Ethernet autoselect (100baseTX half-duplex) status: active Unfortunatly I can't remember when it started happening. I have been tracking current weekly for the past few months. It certainly seems to be getting worse though. Any help would be much appriciated. Cameron First few questiond i'd have to ask is simple, First, do you use DHCP? What are you doing exactly when it looses 'net or 'ip? Specifically, does it come out of suspend mode? cable fall out? maybe the dhcp server times out? Is there any messages on the console or viewable via 'dmesg'? Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network problems
On Sat, 2003-09-20 at 15:10, Cameron Murdoch wrote: I have a strange problem with my Dell Inspiron Laptop. The network card will stop responding to all network traffic. This happens very regulally, though without any obvious pattern. Sometimes it only appears as slight packet lose though normally the network connection goes completly. But then at other times the connection stays up for a resonable time. I have tried different cables, hubs, etc but to no avail. Link status doesn't seem to get dropped, only IP. When the connection gets dropped doing an ifconfig down/up on the interface does ? Unplugging and then inserting the network cable will restore the connection for at least a few seconds. I am running a recent current: FreeBSD opal.macaroon.net 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Sep 19 21:59: 12 BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/OPAL i386 The network card is an integrated intel card, (fxp0): fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=3RXCSUM,TXCSUM inet 10.1.10.200 netmask 0xff00 broadcast 10.1.10.255 ether 00:20:e0:69:50:3c media: Ethernet autoselect (100baseTX half-duplex) status: active Unfortunatly I can't remember when it started happening. I have been tracking current weekly for the past few months. It certainly seems to be getting worse though. Any help would be much appriciated. Cameron First few questiond i'd have to ask is simple, First, do you use DHCP? What are you doing exactly when it looses 'net or 'ip? Specifically, does it come out of suspend mode? cable fall out? maybe the dhcp server times out? Is there any messages on the console or viewable via 'dmesg'? Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Shared object libintl.so.4 not found
On Fri, 2003-09-12 at 17:17, Michael Goffin wrote: I recently upgraded one of my machines to 5.1-current, and for some reason I keep getting Share object 'libintl.so.4' not found errors when I attempt to install from ports or execute certain commands/programs. I read that upgrading my version of gettext would fix the issue, but it has not. Is there any other way to get this object? Mike This would fall under, gettext. You will need to rebuild everything that depends on libintl.so.4 Thus, more then likely gmake, and alot of other things. My suggestion would be to rebuild gmake by hand, then install portupgrade then portupgrade -r gettext Couple hours later, all will be fine. Fortunatly for me because I rebuilt using portupgrade so it kept libintl.so.4 in a nice backup directory that's ldconfig'd at bootup. So it wasn't too painful. Food for thought, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
