Re: Help saving my system
Ah, such a strong comment from such a strong member. I would have thought you were to high to stoop that low? But I guess it's good to be flamed for being honest? is it not? --On Sunday, October 19, 2003 8:45 PM +0200 Dag-Erling Smørgrav <[EMAIL PROTECTED]> wrote: "Scott M. Likens" <[EMAIL PROTECTED]> writes: Comments anyone? Yes: you're an idiot. Go play somewhere else. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help saving my system
--On Saturday, October 18, 2003 6:25 PM -0400 Dan Langille <[EMAIL PROTECTED]> wrote: On 18 Oct 2003 at 12:16, Scott M. Likens wrote: [stuff deleted] Comments anyone? Yes. Next time, don't bother posting. I apologise for my previous post. I should have added what I was thinking. That follows. There's little use or sense in reacting the way you did (not that my original post was much better). In reply to a plea for help, it would have been much better to have suggested course of action to remedy the situation, such as others have done. This is a community mailing list and people are expected to contribute in a positive manner. Ridicule is unacceptable. Cherse Cheers? ^^ -- Dan Langille : http://www.langille.org/ You know one thing i've learned in this world is to do your research before you ask your questions. Try and be absolutely sure that you can't fix it on your own. Then you lay out the problem in the most descriptive way possible. Of course that isn't always possible. But you try to be as descriptive as possible. Now here is my problem a user installs 5.1-release, then downgrades to 4.9, then wants to go back to 5.1? or even stays at 4.9 Okay, there is a serious problem with this because as we all know library's changed drastically both in the extension and purpose from 4.x to 5.x So to downgrade, can be extremely painful and you can't expect much to work right. I think we all can agree on this. But in this situation it should come under CYA, (Cover your ass). You shoud at this point, backup, reformat and get it over with. Because at that point you've just spent more time then it's worth. Takes 30mins to reinstall, maybe 30more mins to get the basic packages installed and setup? Well here we just waisted a few hours of time on the mailing list, atleast .5seconds cpu time, and roughly 8k-10k bandwidth that could have been used otherwise. So when I see a message like that I get offended, because I always tell people NEVER to downgrade from 5.x to 4.x, nor to upgrade from 4.x to 5.x But I guess he's not a client, so it does not matter. The point is, use your brain, and you'll find yourself asking less questions and getting more done. Scott --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Help saving my system
Actually, I think I did... mergemaster? Maybe no one caught it and assumed it was just a ranting flame, But I imagine running mergemaster and making sure the system is synch'd would make a world of difference. Just a token thought. --On Saturday, October 18, 2003 12:52 PM -0700 Jason Dictos <[EMAIL PROTECTED]> wrote: Thanks scott, I'll try that out and let you know how it worked.. Oh wait.. You didn't say anything helpful n/m -Jason -Original Message- From: Scott M. Likens [mailto:[EMAIL PROTECTED] Sent: Saturday, October 18, 2003 12:16 PM To: Jason Dictos; '[EMAIL PROTECTED]' Okay, let's see here. First off you install FreeBSD 5.1, UFS2 possibly but I guess UFS1 since it booted 4.9 Some stupid reason you downgraded to 4.9, didn't run mergemaster, so all your /etc files are out of whack, and now you're bitching that you're trying to do buildworld again, and getting errors. Amazing. Truly Amazing Comments anyone? --On Friday, October 17, 2003 10:53 PM -0700 Jason Dictos <[EMAIL PROTECTED]> wrote: Hi Guys, here's the scenario: 1. Had FreeBSD 5.1 system running. 2. Did a cvsup get of stable (that's right, stable, so 4.9) 3. Compiled make buildworld, then did a make build world, and re-compiled with generic kernel 4. Booted into a system which could not mount the file system (expected since its 4.9) So now I am trying to save the system and here's where I've gotten to: 1. Booted disc 2 of 5.1 cd into "fixme" mode. 2. Mounted live cdrom filesystem and then mounted my root drive to /mnt 3. Did a chroot to /mnt so that I would emulate my live system environment 4. Re-did a cvsup of the branch current. 5. Ran make buildworld from /usr/src Here is what happens when I do that: "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator make: fatal errors encountered -- cannot continue "/usr/src/Makefile.inc1", line 156: warning: "/usr/obj/usr/src/make.i386/make -f /dev/null -m /usr/src/share/mk CPUTYPE=dummy -V CPUTYPE" returned non-zero status "/usr/src/Makefile.inc1", line 158: CPUTYPE global should be set with ?=. *** Error code 1 Help! -Jason __ __ This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com __ __ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Help saving my system
Okay, let's see here. First off you install FreeBSD 5.1, UFS2 possibly but I guess UFS1 since it booted 4.9 Some stupid reason you downgraded to 4.9, didn't run mergemaster, so all your /etc files are out of whack, and now you're bitching that you're trying to do buildworld again, and getting errors. Amazing. Truly Amazing Comments anyone? --On Friday, October 17, 2003 10:53 PM -0700 Jason Dictos <[EMAIL PROTECTED]> wrote: Hi Guys, here's the scenario: 1. Had FreeBSD 5.1 system running. 2. Did a cvsup get of stable (that's right, stable, so 4.9) 3. Compiled make buildworld, then did a make build world, and re-compiled with generic kernel 4. Booted into a system which could not mount the file system (expected since its 4.9) So now I am trying to save the system and here's where I've gotten to: 1. Booted disc 2 of 5.1 cd into "fixme" mode. 2. Mounted live cdrom filesystem and then mounted my root drive to /mnt 3. Did a chroot to /mnt so that I would emulate my live system environment 4. Re-did a cvsup of the branch current. 5. Ran make buildworld from /usr/src Here is what happens when I do that: "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator "/dev/null", line 1: Need an operator make: fatal errors encountered -- cannot continue "/usr/src/Makefile.inc1", line 156: warning: "/usr/obj/usr/src/make.i386/make -f /dev/null -m /usr/src/share/mk CPUTYPE=dummy -V CPUTYPE" returned non-zero status "/usr/src/Makefile.inc1", line 158: CPUTYPE global should be set with ?=. *** Error code 1 Help! -Jason This email has been scanned for all viruses by the MessageLabs Email Security System. For more information on a proactive email security service working around the clock, around the globe, visit http://www.messagelabs.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- The word bipartisan usually means some larger-than-usual deception is being carried out. - George Carlin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Text file busy
On Thu, 2003-09-04 at 07:44, Paul Richards wrote: > Overwriting a file that's currently executing results in a "Text file > busy" error. > > When did this start happening? > > This was something that was fixed way back on FreeBSD but it seems to be > a problem again. > > Paul. this "feature" has always existed in FreeBSD for as long as I remember. Of course there are ways to bypass this "feature" but it's there for your protection. You shouldn't be upgrading a program that's in resident memory. That's like trying to reinstall X while running in X. You're just asking for problems. turnoff postfix, install the new version and be happy. Every single 'flavor' of Unix/Unices has always had this feature. I've seen it on HP-UX box's on Solaris Servers, Linux, NetBSD, OpenBSD, FreeBSD. Maybe you wern't paying attention but, that is one of those things I think should fall under duh, i shouldn't do that it might make things crash hard. Scott. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question related to FreeBSD Serial Console...
On Tue, 2003-09-02 at 01:33, Bruce Evans wrote: > About the original question: multiple consoles in the kernel are > unsupported in FreeBSD-4 but are standard in -current. Unfortunately, > their implementation is slightly incomplete even in -current. In > -current, you get them by booting with -D after booting using the > kern.console sysctl. The number of consoles is limited only by the > number of devices that support consoles. Low level console i/o (mainly > boot messages and other kernel messags printed by kernel printfs) is > then sent to and received from all the consoles, but for some reason > high-level console output (all i/o from/to /dev/console) is only sent > to the first console in the list. This should be easy to fix for > writes and ioctls though not so easy for reads. I think booting with > -Dh makes the serial console first and booting with -D makes the video > console first (if both are configured). The order can be changed using > the sysctl. Eh veh, 10 different answers to 1 question. The mailing list is doing it's job. But okay, yes I was wanting both consoles to be initialized at the same exact time really. So I would guess then, -current would be best supported for this. That or find a motherboard with builtin serial console support. What a solution, was hoping for something more of an easy answer. But Thanks! > On Mon, 1 Sep 2003, Scott Long wrote: > > > John Birrell wrote: > > > On Mon, Sep 01, 2003 at 05:29:09PM -0600, Scott Long wrote: > > > > > >>At one time I was working on patches to the loader to make the console > > >>speed configurable. At the time, at least, I didn't see any evidence > > >>that the settings were stored in the boot0 block, but maybe I was wrong. > > There are already too many places to set it. > > > > AFAIK, the boot0 block uses bios int 0x16 to get a key-press and bios int > > > 0x10 to display a character, so in a situation where you *want* a serial > > > console, the F1 etc stuff can't be used unless the bios supports console > > > re-direction. And you have to live with whatever baud rate the bios sets. > > I think boot0 is already full (unless you unportabalize it by expanding it > beyond one sector). It doesn't have its own serial i/o routines mainly > because there is no space for them. > > > > Once you get to boot2, then the serial console can work if set in /boot.config. > > > > > > It would be nice to have a boot.config setting for the baud rate. I have a > > > board here that allows bios re-direction to either the first or second serial > > > port at a fixed baud rate of 38400. I have to build boot2 with > > > BOOT_COMCONSOLE_SPEED=38400, and then the kernel with CONSPEED=38400 to > > > get all the ducks in a row. > > The latter shouldn't be necessary. The kernel (i386 sio only) uses the > same speed that boot2 used if the kernel was booted with -h. It should > also use the same speed if the kernel was booted with -D. > > > > But it would be even nicer if both boot2 and the kernel would just work with > > > whatever baud rate the bios set. > > > > This is exactly the problem that I was working on. > > Unfortunately most BIOSes don't provide a way to set the speed. I'm not > sure that it even has a default. I always use 115200 bps, but at least he > old BIOS interface is limited to 9600 bps. I may work on this a bit soon > to make 921600 bps work. > > Bruce -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Question related to FreeBSD Serial Console...
On Mon, 2003-09-01 at 16:13, Nicole wrote: > On 01-Sep-03 Unnamed Administration sources reported Scott Long said : > > Scott M. Likens wrote: > >> I have a question related to FreeBSD Serial console, > >> > >> I am aware you can use -Dh for both internal and serial, but is it > >> possible to see the 'kernel' "boot" messages sent on both the serial and > >> the console? > >> > >> It was a question that was asked to me by a client, and after > >> researching it more, it seems that it's not possible. > >> > >> Am i wrong? or did I miss an option that's not documented? > >> > >> Sincerely, > >> > >> Scott M. Likens > >> > >> > > > > I'm a little confused by your request, but maybe adding the following > > line to /boot/loader.conf will get what you want? > > > > console="comconsole" > > > > There is also a way to get the console directed to both the video and > > serial at the same time, but I've forgotten the magic and can't find it > > at the moment. > > Heh magic is the right word ;) > > According to what I have found it is supposed to be: > > console="vidconsole" To make it still choose internal console even if it does > not find a keyboard present at boot time. So you can walk up later and connect > a keyboard and have it work. > > > Everytime I asked on the lists I got.. Oh go look here for the answer. Which I > had.. to which I got, oh well the answers in there.. No one ever was able to > say DO THIS. Let alone anyone saying do this and have it work :( > > If you find the Magic please do let me know :) My god I think i'm gonna create a 10line signature to compete with you guys. At any rate, Thank you for the console="vidconsole" that should do the trick of what i was seeking. I just basically want it to send to both serial + vga at the same time, that's all. Because sometimes serial is required for remote purposes, ssh into a control server, minicom over to the serial, wam. Or if i'm at the server, switchover the kvm and see what's up. Can be hard during the boot process when something hangs and you can't see shit until it's fully booted. But thank you for your responses. --- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Question related to FreeBSD Serial Console...
I have a question related to FreeBSD Serial console, I am aware you can use -Dh for both internal and serial, but is it possible to see the 'kernel' "boot" messages sent on both the serial and the console? It was a question that was asked to me by a client, and after researching it more, it seems that it's not possible. Am i wrong? or did I miss an option that's not documented? Sincerely, Scott M. Likens signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
interesting time_t error...
I noticed this earlier. /usr/bin/tar: Archive octal value 20366603014 is out of time_t range; assuming two's complement /usr/bin/tar: Archive octal value 20366603014 is out of time_t range; assuming two's complement I was doing portupgrade on xine-ui. Knowing how to read the time I know it's due to the file date, but that's quite an interesting way of saying that. BTW, yes the date on my computer is fine. it must have been the ftp server I grabbed it off of. My only real comment on this, was the way it said it. Maybe we could have made it more informational to the not savvy user? signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Filesystem problem
On Sun, 2003-08-31 at 11:36, Kevin Bockman wrote: > Hi. I have been experencing some filesystem problems > for the last month or so. I was running 4.8-STABLE and > updated to 5.1-RELEASE-p2. While I was running 4.8 > and I tried to run a command that required hard disk > activity, the process would 'hang' and I would no > longer be able to ssh or telnet in. I would get stuck > after typing in my login. Have you concidered it might be related to your hard drive, and or controller? It seems to be that you had problems with 4.8 and 5.1, since you low level formatted the drive i'm assuming that it is IDE. Chances are if you waited long enough you might find some really unique/cool error messages posting to the console. It sounds like for whatever reason you're hard drive is timing out on responses. That or it could be your controller, at any rate. Maybe you should look into those. > Running 5.1 is a different story. I did a low level > format of the drive then I did a clean > install of 5.1-RELEASE and cvsup'd to -p2. Every time > I do this, it's great for a day or so then it acts up. > Before after it started, even if I rebooted it would > immediately start up. On 5.1, it is only hanging for > that process and everything else is fine. I can still > login, webserver responds, etc. > > Here is a little info: > > FreeBSD devel.neoninternet.net 5.1-RELEASE-p2 FreeBSD > 5.1-RELEASE-p2 #0: Sat Aug 23 20:12:41 PDT 2003 > [EMAIL PROTECTED]:/usr/src/sys/i386/compile/SLURPEE > i386 > > CPU: AMD Athlon(tm) XP 2600+ (2086.51-MHz 686-class > CPU) > real memory = 1073676288 (1023 MB) > ad0: 117246MB [238216/16/63] at > ata0-master UDMA133 > > root 1173 0.0 0.1 1436 916 p3 D+6:38PM > 0:00.00 man vmstat > root784 0.0 0.1 752 636 d0 D 4:34PM > 0:00.02 make all DIRPRFX=i386/libi386/ > root847 0.0 0.0 312 212 d0 D 4:34PM > 0:00.00 (cc) > root848 0.0 0.3 4104 3488 d0 D 4:34PM > 0:00.01 (cc1) > root849 0.0 0.1 928 668 d0 D 4:34PM > 0:00.00 /usr/bin/as -o comconsole.o - > > last pid: 1252; load averages: 0.00, 0.00, 0.00 > up 0+02:37:22 > 19:04:48 > 64 processes: 1 running, 63 sleeping > CPU states: 0.0% user, 0.0% nice, 0.0% system, > 0.0% interrupt, 100% idle > Mem: 34M Active, 23M Inact, 38M Wired, 204K Cache, 22M > Buf, 906M Free > Swap: 2048M Total, 2048M Free > > devel# vmstat > procs memory pagedisks >faults cpu > r b w avmfre flt re pi po fr sr ad0 da0 > in sy cs us sy id > 1 7 0 144612 928056 16 0 0 0 9 0 0 0 > 3310 254 0 0 100 > > Anyone have any suggestions? I can not control-C out > of 'man vmstat'. While doing 'make' in > /usr/src/sys/boot it was hanging on as, when I > restarted it, it got to i386/libi386 and will not do > anything else. I'm running that through serial > console, it let me ^C out of that. I tried going into > single user mode and running umount, now it just sits > there and I can't ^C. I have no ideas, this was all > working yesterday!! :-) > > Any ideas on what else to check or other helpful hints > would help bunches. > > Sorry for the cross-posts. Just not sure where to go > with this one. > > Thanks, > > Kevin as i said, seems like the problem is the same it just gets a little farther in with 5.1 signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: vmware-guestd on vmware hosted Windows
On Sat, 2003-08-30 at 04:32, Masahide -mac- NODA wrote: > Sorry, this is repot only. > > I'm upgrading from 2003/08/19 current to 2003/08/30 current on vmware > 3.x(host OS is Windows), and I tried to run vmware-guestd, > ># ./vmware-guestd >ELF binary type "0" not known. >/usr/local/sbin/vmware-guestd: Exec format error. Wrong Architecture > > I suggested on IRC, try > > # brandelf -t FreeBSD ./vmware-guestd > > I tried this and succeceed to run vmware-guestd. > > Before brandelf -t, brandelf result is, > > % brandelf vmware-guestd > File 'vmware-guestd' is of brand 'SVR4' (0). > > and after brandelf -t is, > > % brandelf vmware-guestd > File 'vmware-guestd' is of brand 'FreeBSD' (9). > > > Any comments? If memory serves, you'll need COMPAT3x in order to use that. Unfortunatly VMWare really hasn't updated their drivers, since well FreeBSD 3.x I could be wrong, if i am tell me. But that's what I remember. signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: buildworld failure
On Fri, 2003-08-29 at 09:04, Sheldon Hearn wrote: > On (2003/08/29 11:48), Robert Watson wrote: > > > The differences here seem to be: > > > > (1) I'm using -O, not -O2 > > (2) I'm optimizing -mcpu as pentiumpro, not pentium4 > > Isn't pentium4 a known-broken optimization at the moment? > > Ciao, > Sheldon. I wouldn't even go that far, it has been known that -O2 can create broken code at times. I don't imagine that GCC 3.3 branch has changed this much. Personally I feel that downgrading it to -O1 is much more feasable. Infact, awhile back I built my window manager by accident with -O2 and found it quite unstable. Rebuilt it with -O1 and it's been acting much more happy. The reality is Speed Vs. Stability, and in my humble opinion i'd rather have it running 24/7 with a 1-2% speed decrease, then have it down 1-2hours out of the day and 3% faster. My 10cents. signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: System freezes with radeon 9100 graphics card
On Sat, 2003-08-23 at 20:38, Glenn Johnson wrote: > On Sat, Aug 23, 2003 at 02:11:15PM -0500, Glenn Johnson wrote: > > > I have had an ongoing problem with -current freezing during a restart > > of the X serer. The graphics card is an ATI Radeon 9100. I am pretty > > sure this is related to DRI as I have not had it happen with DRI > > disabled. > > > > I am not sure if the problem is with the radeon kernel module, with > > XFree86-Server, or something else. The freezes totally lock up the > > machine, no ssh access is possible, no crash dumps are produced, I > > have to hit the reset button and run fsck in single user mode. > > > > Is anyone else seeing this with a radeon card? Any options I can set > > to alleviate the problem? I going to turn on DRM_DEBUG and see what > > that yields. > > > > Thanks. > > Some more info: > > I get the following error messages when the X server starts: > > drm0: port 0x9000-0x90ff mem > 0xf900-0xf900,0xe000-0xefff irq 2 at device 0.0 on pci1 > info: [drm] Initialized radeon 1.9.0 20020828 on minor 0 > error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held > error: [drm:radeon_unlock] *ERROR* Process 579 using kernel context 0 > error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held > error: [drm:radeon_unlock] *ERROR* Process 738 using kernel context 0 > error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held > error: [drm:radeon_unlock] *ERROR* Process 865 using kernel context 0 I might suggest to you that you try the DRI lists... see http://dri.sf.net or email [EMAIL PROTECTED] Also please teach your email client to word wrap. That's nasty. -- signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dual P4 2.4Ghz Xeon With Hyperthreading enabled...
On Tue, 2003-08-12 at 15:41, Brooks Davis wrote: > On Tue, Aug 12, 2003 at 03:38:29PM -0700, Scott M. Likens wrote: > > Well friend of mine just landed a Dual P4 2.4Ghz Xeon with > > Hyperthreading Enabled, and yet I know there's a hyperthreading option > > in 4.8-RELEASE but I don't see one at ALL in 5.1? > > > > am I suddenly blind or do I need to cvsup to CURRENT to take proper > > advantage? > > There is no option in current. Instead, you use the sysctl > machdep.hlt_logical_cpus to indicate if you want to use the logical > cpus. > > -- Brooks For clarification, setting this to 2 would mean 2 processor's to process? Thanks. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dual P4 2.4Ghz Xeon With Hyperthreading enabled...
Well friend of mine just landed a Dual P4 2.4Ghz Xeon with Hyperthreading Enabled, and yet I know there's a hyperthreading option in 4.8-RELEASE but I don't see one at ALL in 5.1? am I suddenly blind or do I need to cvsup to CURRENT to take proper advantage? I am aware of a few problems where sometimes process's can be sent to a virtual process/limbo which is why i'm trying to get more information on this. Any information would be greatful, thanks. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ATAng
On Sat, 2003-08-09 at 11:40, Matt Douhan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I cvsup'd current src today and applied the conf-patch and replaced the > /usr/src/sys/dev/ata/* > > now in my dmesg output I see this, > > Waiting (max 60 seconds) for system process `vnlru' to stop...stopped > Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped > Waiting (max 60 seconds) for system process `syncer' to stop...stopped > > syncing disks, buffers remaining... 13 13 > done > > if I look at dmesg.yesterday I do not see these messages, maybe I just dont > know what I am doing then please say so, but I thought it worth sending > anyway That has ALWAYS been there. Maybe you hadn't noticed it, but on my server I ALWAYS get it. Even without the ATAng patch, but since i run SCSI the ATAng patch is worthless to me or else i'd be testing it myself. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: another buildworld -j4 panic
On Thu, 2003-08-07 at 22:36, Mike Silbersack wrote: > ok, here goes: > > duplicate free from zone FFS1 dinode > > traceback: > Debugger > panic > uma_dbg_free > uma_zfree_arg > ffs_ifree > ufs_reclaim > ufs_vnoperate > vclean > gdonel > getnewvnode > ffs_vget > ufs_lookup > ufs_vnoperate > vfs_cache_lookup > ufs_vnoperate > lookup > namei > stat > syscall > Xint0x80_syscall > > Whee! > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" IS it possible for you to duplicate without the -j4? like a simple make buildworld? Your I/O controller maybe not able to keep up. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACLS on UFS2 from FreeBSD 5.1-RELEASE install.
Has anyone noticed the ACLS being disabled? tunefs -p /dev/da1s1c shows that ACLS are disabled on every partition I have, i've gone through them all. any reason why? tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f)16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
On Fri, 2003-07-25 at 16:38, James Tanis wrote: > Has anybody had problems compiling, kde most notably, with gcc3.3 in > -current? I'd post the error, which seemed STL related, but I thought I'd ask > first. I tried installing the stlport port on the offchance this would fix > the problem, but that also came to (a much quicker) screeching halt. I > believe it can't find ctime. It's been doing this for sometime, I'm also > wondering if I have any dependencies missing since this last install is the > first time I've ever installed kde without using source originally.. but I > haven't been able to find anything that the ports system could be missing. These issues have been addressed in KDE 3.1.3 if you're patient enough for Will to work out the kinks the ports will be updated in a week or less. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VMWare inflicted kernel panic
On Fri, 2003-07-25 at 04:54, Sławek Żak wrote:
> vmware3-3.2.1-2237_1, rtc-2002.03.05.2_2, world built on 21-7, backtrace:
>
> (kgdb) bt
> #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
> #1 0xc02217d9 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:372
> #2 0xc0221bb8 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
> #3 0xc0373f66 in trap_fatal (frame=0xe219c710, eva=0)
> at /usr/src/sys/i386/i386/trap.c:836
> #4 0xc03734a3 in trap (frame=
> {tf_fs = -1069481960, tf_es = -1067974640, tf_ds = -979763184, tf_edi =
> -979938720, tf_esi = -979943236, tf_ebp = -501626976, tf_isp = -501627076, tf_ebx =
> 1, tf_edx = 1966080, tf_ecx = -979938720, tf_eax = -1071470963, tf_trapno = 12,
> tf_err = 2, tf_eip = -1070127771, tf_cs = 8, tf_eflags = 77826, tf_esp =
> -1071470963, tf_ss = -979938720}) at /usr/src/sys/i386/i386/trap.c:256
> #5 0xc0363ef8 in calltrap () at {standard input}:102
> #6 0xc02214c2 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:312
> #7 0xc0221bb8 in panic () at /usr/src/sys/kern/kern_shutdown.c:550
> #8 0xc0373f66 in trap_fatal (frame=0xe219c8d0, eva=0)
> at /usr/src/sys/i386/i386/trap.c:836
> #9 0xc03734a3 in trap (frame=
> {tf_fs = -1069481960, tf_es = -1067974640, tf_ds = -1051525104, tf_edi =
> -979938720, tf_esi = -979943236, tf_ebp = -501626528, tf_isp = -501626628, tf_ebx =
> 0, tf_edx = 1966080, tf_ecx = -979938720, tf_eax = -1071470963, tf_trapno = 12,
> tf_err = 2, tf_eip = -1070127771, tf_cs = 8, tf_eflags = 78342, tf_esp =
> -1071470963, tf_ss = -979938720}) at /usr/src/sys/i386/i386/trap.c:256
> #10 0xc0363ef8 in calltrap () at {standard input}:102
> #11 0xc0229d2f in msleep (ident=0xce521990, mtx=0xc041dce0, priority=68,
> wmesg=0x0, timo=0) at /usr/src/sys/kern/kern_synch.c:256
> #12 0xc0270c40 in bwait (bp=0xce521990, pri=68 'D', wchan=0xc03a340a "spread")
> at /usr/src/sys/kern/vfs_bio.c:3735
> #13 0xc01dc5f6 in spec_getpages (ap=0xe219cab8)
> at /usr/src/sys/fs/specfs/spec_vnops.c:749
> #14 0xc01daf08 in spec_vnoperate (ap=0x0)
> at /usr/src/sys/fs/specfs/spec_vnops.c:122
> #15 0xc03104b2 in ffs_getpages (ap=0xe219cb20) at vnode_if.h:1314
> #16 0xc033dfdb in vnode_pager_getpages (object=0xc4604a68, m=0x0, count=0,
> reqpage=0) at vnode_if.h:1314
> #17 0xc0323bc2 in vm_fault (map=0xc6b45400, vaddr=673882112,
> fault_type=1 '\001', fault_flags=0) at /usr/src/sys/vm/vm_pager.h:125
> #18 0xc0373ae5 in trap_pfault (frame=0xe219cd48, usermode=1, eva=673882112)
> at /usr/src/sys/i386/i386/trap.c:726
> #19 0xc037359c in trap (frame=
> {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 135054704, tf_esi = -1077939004,
> tf_ebp = -1077940796, tf_isp = -501625484, tf_ebx = 674764720, tf_edx = 135010302,
> tf_ecx = -1077939004, tf_eax = 135054704, tf_trapno = 12, tf_err = 4, tf_eip =
> 673882110, tf_cs = 31, tf_eflags = 78470, tf_esp = -1077949236, tf_ss = 47}) at
> /usr/src/sys/i386/i386/trap.c:321
> #20 0xc0363ef8 in calltrap () at {standard input}:102
>
> /S
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
I've been running VMWare 3 with FreeBSD for quite some time and have come to this
conclusion.
Disable RTC, our rtc module hella sucks. The difference of 92-99% cpu
usage on vmware and 3%.
Secondly enable AIO i've found a great performance and less crash happy
experience by doing so, make sure also you're using linux_compat and not
linux_compat8 that creates further problems unfortunatly.
Beyond that expect panics, I can get it to run 'once' flawlessly and
then I have to reboot my workstation or else the 2nd time I boot into
it, it WILL panic in mid-boot of Windows 2000.
and BTW,
RTC is only needed if you run Windows 98 for the 'fades' and 'effects'
so if you don't use them, kill the kernel module. You won't miss much.
Infact it shouldn't be a dependancy since VMWare does NOT require it to
work. It complains and gives you a hint to disable that
'complaint/hint'. But nothing more.
Good luck
--
"I think we ought to be out there doing what we do best - making large
holes in other people's countries." - George Carlin
signature.asc
Description: This is a digitally signed message part
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SMPng status?
Out of curiosity I was wondering what the SMPng status was? I have heard it's not fully implemented due to KSE/libthr not fully implemented. I was wondering if this was incorrect information or what? The reason i'm asking is there is a Dual P2-450 here that i'm trying to decide what to install on it. Thus SMPng becomes the question do i run -CURRENT or 4.8 or do something more evil? Any ideas? -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ASMTP setup on 4.8
On Fri, 2003-07-18 at 13:10, Hajimu UMEMOTO wrote: > Hi, > > > On Fri, 18 Jul 2003 12:14:08 -0700 > > "Drew Tomlinson" <[EMAIL PROTECTED]> said: > > drew> I've been trying to get saslauthd working with PAM on my 4.8-RELEASE but > drew> have been unsuccessful. > > Umm, it's strange. Actually, I didn't change any PAM related > settings, and it is working here. > > drew> I installed saslauthd from the ports. One of the problems is > drew> that the man page is unreadable. Is there some way to fix it? > > Okay, I found the problem, and I've just committed the fix. Please > re-cvsup and try it. > > drew> It's been a few weeks since I looked at it but I recall having to create > drew> a /usr/local/lib/sasl2/smtpd.conf file. What should the correct > drew> contents be? > > Though I have no experience with postfix, I heared that > /usr/local/lib/sasl2/smtpd.conf is for postfix. Are you using > sendmail? If so, it should be /usr/local/lib/sasl2/Sendmail.conf. > > drew> And what might I need to put in /etc/pam.conf to make it all work. > > The `other' entries which are provided as default sould be sufficient > for saslauthd. I didn't make any change into my /etc/pam.conf. > > Sincerely, > > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED],jp.}FreeBSD.org > http://www.imasy.org/~ume/ > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > the most common Misconception of ASMTP and Cyrus is that CRAM-MD5 and DIGEST-MD5 and such work with PAM. They do not, you need to make sure that you are using PLAINTEXT or otherwise you will have to add users into /usr/local/etc/sasldb2 which is not exactly fun. As far as sendmail i'm not much of help I can explain it with Postfix pretty easily but I don't use Sendmail anymore alas. If you have any questions feel free to comment. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
On Sat, 2003-07-12 at 10:40, Scott M. Likens wrote: > On Sat, 2003-07-12 at 07:51, Christopher Nehren wrote: > > The "not implemented" error message suggests to me that the VM (in this > > case, Win2K) is attempting to perform an operation that the emulation > > software (or its underlying operating system -- in this case, Linux > > 2.4.2 under FreeBSD emulation) doesn't know how to perform. I received a > > similar message when attempting to install Windows XP on VMWare 2.x -- > > however, IIRC, mine didn't crash or require a hard reboot. My hypothesis > > is that -- were this a real, modern Linux machine -- that operation > > would succeed. However, since this is a binary emulation situation (one > > that itself manages its own layer of binary emulation), and one that > > more directly interfaces with the underlying hardware than most Linux > > emulated programs, the likelihood for such an operation to fail > > increases. As far as I understand it, the solution involves more fully > > implementing the Linux emulation. > > Actually it's during shutdown that this bug occurs > > It's quite annoying on top of the 'rtc.ko' wanting to dump and creating > a infinite loop panic at shutdown isn't that great either. > > I know i'm not the only person experiencing this, just the only person > who cares. > > So i've come to this conclusion, I'll just need linux. > > You are right thought it's obviously a call it's making like sync() i > imagine that we arn't implementing properly in the emulation. So when > VMWare try's to make this what should exist call, it's not really there > and fudges up. > > Thus leaving crap in the kernel i imagine, and thus creating the > problem. > > > > Either this, or it could just be a plain bug in VMWare -- though I've > > learned from experience that it's always best to blame oneself before > > assuming others are at fault. Nah it's still there with VFS_AIO compiled into the kernel. Obviously it's more then meats the eye, but I don't know where it lacks it, thus why I asked the list to see if I missed it. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
On Sat, 2003-07-12 at 08:00, Daniel Eischen wrote: > On 11 Jul 2003, Scott M. Likens wrote: > > > I've been using VMWare in 5.1-RELEASE for quite some time and such, and > > have ALWAYS gotten this bug and haven't been able to figure out exactly > > why it does this, but it requires me to reboot. > > > > Anyhow here's the layout of the system. > > > > P3 800Mhz with 512meg of SDRAM > > AHA 2940U2W, Dual 17Gig Ultra Scsi 2's (LVD) > > no IDE devices, IDE is normally disabled, Matrox G400 Dual head without > > HAL. > > Soundblaster PCI 512, (emu10k1) > > > > using waimea as the window manager (or kde doesn't seem to make this bug > > better) > > > > using netgraph bridging, i have the RTC.ko loaded (that's another > > nuisance i'd love to correct maybe when I have more time) > > > > I've tried reinstalling VMWare and even on a fresh FreeBSD install it > > gives this error. > > Do you have VFS_AIO in your kernel (or the AIO module loaded)? > > (I don't use VMWare, just guessing by looking at your error message). I wasn't aware of that module, Thanks. I'll have to rebuild the kernel because it's actually a 'option' not a simple kernel module. But that will make things happier. now if the new scheduler would work with me better, so it doesn't stick to 97% cpu I would be perfectly happy. But alas, that is for another thread. -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin signature.asc Description: This is a digitally signed message part ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding VMWare 3.0 Port and an odd bug that i've beengetting over and over again...
On Sat, 2003-07-12 at 07:51, Christopher Nehren wrote: > The "not implemented" error message suggests to me that the VM (in this > case, Win2K) is attempting to perform an operation that the emulation > software (or its underlying operating system -- in this case, Linux > 2.4.2 under FreeBSD emulation) doesn't know how to perform. I received a > similar message when attempting to install Windows XP on VMWare 2.x -- > however, IIRC, mine didn't crash or require a hard reboot. My hypothesis > is that -- were this a real, modern Linux machine -- that operation > would succeed. However, since this is a binary emulation situation (one > that itself manages its own layer of binary emulation), and one that > more directly interfaces with the underlying hardware than most Linux > emulated programs, the likelihood for such an operation to fail > increases. As far as I understand it, the solution involves more fully > implementing the Linux emulation. Actually it's during shutdown that this bug occurs It's quite annoying on top of the 'rtc.ko' wanting to dump and creating a infinite loop panic at shutdown isn't that great either. I know i'm not the only person experiencing this, just the only person who cares. So i've come to this conclusion, I'll just need linux. You are right thought it's obviously a call it's making like sync() i imagine that we arn't implementing properly in the emulation. So when VMWare try's to make this what should exist call, it's not really there and fudges up. Thus leaving crap in the kernel i imagine, and thus creating the problem. > Either this, or it could just be a plain bug in VMWare -- though I've > learned from experience that it's always best to blame oneself before > assuming others are at fault. -- "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]"
Regarding VMWare 3.0 Port and an odd bug that i've been gettingover and over again...
I've been using VMWare in 5.1-RELEASE for quite some time and such, and have ALWAYS gotten this bug and haven't been able to figure out exactly why it does this, but it requires me to reboot. Anyhow here's the layout of the system. P3 800Mhz with 512meg of SDRAM AHA 2940U2W, Dual 17Gig Ultra Scsi 2's (LVD) no IDE devices, IDE is normally disabled, Matrox G400 Dual head without HAL. Soundblaster PCI 512, (emu10k1) using waimea as the window manager (or kde doesn't seem to make this bug better) using netgraph bridging, i have the RTC.ko loaded (that's another nuisance i'd love to correct maybe when I have more time) I've tried reinstalling VMWare and even on a fresh FreeBSD install it gives this error. Attached are some files for you to see Scott M. Likens -- "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin Copyright (c) 1992-2003 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 5.1-RELEASE #0: Thu Jul 10 18:28:48 PDT 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LIVID Preloaded elf kernel "/boot/kernel/kernel" at 0xc04fd000. Preloaded elf module "/boot/kernel/vesa.ko" at 0xc04fd1f4. Preloaded elf module "/boot/kernel/linux.ko" at 0xc04fd2a0. Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc04fd34c. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc04fd3fc. Preloaded elf module "/boot/kernel/mga.ko" at 0xc04fd4a8. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04fd550. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 797968113 Hz CPU: Intel Pentium III (797.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 536854528 (511 MB) avail memory = 515981312 (492 MB) Pentium Pro MTRR support enabled VESA: v3.0, 16384k memory, flags:0x1, mode table:0xc00c52bd (c00052bd) VESA: Matrox Graphics Inc. npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00f0e60 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 drm0: mem 0xe080-0xe0ff,0xe100-0xe1003fff,0xe200-0xe3ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xe400 64MB info: [drm] Initialized mga 3.1.0 20021029 on minor 0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ahc0: port 0xb800-0xb8ff mem 0xe000-0xefff irq 10 at device 14.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs pcm0: port 0xb400-0xb41f irq 7 at device 16.0 on pci0 pcm0: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xa800-0xa87f mem 0xdf80-0xdf80007f irq 11 at device 17.0 on pci0 xl0: Ethernet address: 00:50:da:1c:29:c8 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.PX40.PS2M._STA] (Node 0xc4010800), AE_AML_REGION_LIMIT
Re: 3D graphic cards
On Fri, 2003-07-11 at 11:24, Brian Reichert wrote: > On Thu, Jul 10, 2003 at 11:34:00AM -0700, Scott M. Likens wrote: > > That's funny knowing I have a ATI Radeon 7200 and I have ALWAYS > > supported FreeBSD and the ATI Radeon for ages. Ever since one person > > known as 'erek' showed me DRI-HEAD i've learned that XFree86 4.3.0 is > > just a little outdated. > > Is 'DRI-HEAD' a CVS tag? > no it's just generic terms... just do co without any tags... and it'll be fine. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: radeon lockups w/ 5.1-R
On Thu, 2003-07-10 at 15:25, Matthias Buelow wrote: > Scott M. Likens writes: > > >Are you using the drm kernel drivers from the kernel, or are you using > >DRI-HEAD from dri.sf.net? > > >From the kernel (I didn't install anything else). Yes you can get it from dri.sf.net Easiest way and most painful as you have to download alot, cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri login cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dri -z3 co xc 2hours later, or whatever it may be. cd xc/xc make World then after that's done, yes you'll want libGL and such... so first off cd ~/xc/xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel make -f Makefile.bsd then make -f Makefile.bsd install then go through and install the proper stubs and drivers, you can it easily done at, xc/xc/programs/Xserver/hw/xfree86/drivers make install xc/xc/lib/GL make install and go through you don't need to install the whole thing, unless you want. Either works... but that will give you native support make sure the radeon.kld from the os-support/... gets into /boot/kernel kldxref /boot/kernel radeon_load="YES" in /boot/loader.conf and that will give you MUCH more recent DRI support that'll get you OpenGL 1.3 support which you can verify with glxinfo. If you have any questions you can email me, or the list... i prefer the list for educational purposes. the DRI-HEAD as it is builds perfectly for FreeBSD and NetBSD i believe... FreeBSD i have exp with. if you need linux support, we can work on that too. -- Scott M. Likens <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: radeon lockups w/ 5.1-R
On Thu, 2003-07-10 at 12:14, Matthias Buelow wrote: > Hi folks, > > anyone else still seeing occasional lockups when using a Radeon > graphics card? I've had these frequently with a R7500 on 5.0p7 > and now installed 5.1 hoping that the issue had been fixed in > the meantime. It went well for two days but it just fscked up > again so the problem is still there. It only happens when I > exit the X session. Display becomes garbled and the machine > locked up completely (didn't always do so in the past with 5.0, > I sometimes could log in over the network and reboot the machine.) > I think the problem was already known for 5.0, or does it warrant > a new PR? Are you using the drm kernel drivers from the kernel, or are you using DRI-HEAD from dri.sf.net? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3D graphic cards
On Thu, 2003-07-10 at 07:03, Bruno Afonso wrote: > Dag-Erling Smørgrav wrote: > > > "Julian St." <[EMAIL PROTECTED]> writes: > > > >>is there any list that provides information about what graphic cards > >>on FreeBSD have supported 3D acceleration? (I need only X-Video > >>support in particular, but it seems tied to 3D acceleration). > > > > > > http://people.freebsd.org/~anholt/dri/ > > > > Radeon-based cards (up to 8500) are fairly cheap and work well. > > No they don't. I have a radeon 7200 and at the moment the support seems > to be broken (I don't think anyone has updated XFree to fix it). This is > on 5.1. Search the -current archives and you will someone also > complaining about it. That's funny knowing I have a ATI Radeon 7200 and I have ALWAYS supported FreeBSD and the ATI Radeon for ages. Ever since one person known as 'erek' showed me DRI-HEAD i've learned that XFree86 4.3.0 is just a little outdated. I use DRI-HEAD on my other server that is using a Matrox G400 Dual Head also, works snappy on 5.1 I stopped relying on XFree to keep updating their stuff along time ago. I've had problems with DRI admitidly but it works now. They get the kinks out in waves if you ask me. -- Scott M. Likens <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: who am i
On Thu, 2003-07-03 at 15:46, Richard Arends wrote: > Hello, > > Please take a look at this: > > = > [snowlap] ~$ who am i > richard ttyp5Jul 4 00:34 (:0.0) > [snowlap] ~$ su - > Password: > Last login: Fri Jul 4 00:31:17 on ttyp5 > snowlap# who am i > root ttyp5Jul 4 00:34 > snowlap# exit > logout > [snowlap] ~$ who am i > root ttyp5Jul 4 00:34 > = > > Of course the latest 'who am i' should return 'richard' and not(!) 'root' > > Regards, > > Richard. > Quite interesting, I do concur... I get the same thing here... [EMAIL PROTECTED]:~> who am i damm ttyp5Jul 3 16:06 (:0.0) [EMAIL PROTECTED]:~> su - Password: Last login: Thu Jul 3 14:06:16 on ttyp4 [EMAIL PROTECTED]:~# who am i root ttyp5Jul 3 16:06 [EMAIL PROTECTED]:~# logout [EMAIL PROTECTED]:~> who am i root ttyp5Jul 3 16:06 [EMAIL PROTECTED]:~> Quite odd... yet true. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
