Re: How the hell does one create a new bus?!
[hackers removed from Cc to prevent excessive crossposting] On Sun, 14 Feb 1999, Garrett Wollman wrote: On Sun, 14 Feb 1999 16:44:37 -0800 (PST), Julian Elischer jul...@whistle.com said: The trouble is Doug, that until there IS a developer's guide, the only person capable if moving PCI and ISA to your scheme, is you. and as you pointed out.. you're short of time right now.. No, there are more people than just Doug. Certainly me (if I had time), Nicolas (if he had time), probably Andrew Gallatin since he's done a lot of work on the Alpha side of things (but he probably has no more time than the rest of us). Don't forget Nick Hibma. He should be quite familiar with the system after working on the USB code. There is a proper mailing list for this discussion, and we'd be happy to talk over any doco that someone should choose to write. Please take any followups to new-bus-a...@bostonradio.org. Good idea. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problesm w/ 4.0-current wine
When I try to run wine on FreeBSD 4.0-CURRENT, I get the following message: Feb 15 05:19:56 myname /kernel: Patch manager interface is currently broken. Sorry Feb 15 05:19:56 myname /kernel: Patch manager interface is currently broken. Sorry wine: can't exec 'demo1.exe': error=0 wine: no executable file found. I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. Donn To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
I'm also using wine(latest from ports) with 4.0-current and it works for me (elf kernel). Donn Miller wrote: When I try to run wine on FreeBSD 4.0-CURRENT, I get the following message: Feb 15 05:19:56 myname /kernel: Patch manager interface is currently broken. Sorry Feb 15 05:19:56 myname /kernel: Patch manager interface is currently broken. Sorry wine: can't exec 'demo1.exe': error=0 wine: no executable file found. I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. Donn To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How to power off an ATX power supply machine on shutdown ?
Alex Zepeda wrote: Is a delay needed between the final sync's and the actual power off? Apparently so. There is/was a recently added sysctl for this purpose. Poke around in the archives. Was that sysctl added to the -STABLE branch? I am running 3.1-BETA and I cannot find it. -- JMA --- José Mª Alcaide | mailto:j...@we.lc.ehu.es Universidad del País Vasco | mailto:j...@es.freebsd.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 --- Go ahead... make my day. - H. Callahan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Disk locks and weird things
Matthew Thyer m...@camtech.com.au writes: On Sun, 14 Feb 1999, Erik Funkenbusch wrote: During a make world (usually about 10-20 minutes in on my P100) everything just comes to a grinding halt. No disk activity, but the screen saver will kick in (despite the shell being in the middle of said make world). Shouldn't a make world take about 10 hours on a P100 ?? -depends on the speed of your disks. More like five or six. But he wasn't saying his make world took ten minutes, he was saying it died after ten minutes. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Weird piecemeal reads over socketpair() pipe breaks up small writes into even smaller reads.
When the writer blocks, the reader runs and uses a buggy loop to read only the first chunk of input. On an otherwise idle system, the need_resched() condition seems to be true always. I would have expected the synchronisation provided by the sleep(1) to bias need_resched() in the opposite direction. A reschedule has been done, normally just after the previous hardclock() call, just before the writer wakes up, so another one should not be done soon (until after the next hardclock() call). Sorry everyone, I'll be away for a week and won't put in my scheduler fixes until I get back. Most of the changes are on Freefall in my home directory. I hate to be so passive about committing tested code, but my schedule is such over the last few months that I'm never around to fix things up if the unexpected happens. I'm working hard on a proposal that will let me spend some quality time on this - wish me luck. Meanwhile, I'm off all the lists. I'll check e-mail sent to either dufa...@hda.com or dufa...@freebsd.org intermittently. Peter -- Peter Dufault (dufa...@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
On Mon, 15 Feb 1999, Donn Miller wrote: I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Heads up! /etc/rc.conf.site is dead.
On Fri, 12 Feb 1999 16:56:48 PST, Jaye Mathisen wrote: mergemaster is your friend. Mergemaster will help you update /etc/defaults/rc.conf, but you'll need to use something else to merge changes from that file into /etc/rc.conf . Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
Kris Kennaway wrote: On Mon, 15 Feb 1999, Donn Miller wrote: I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Did that. I installed the kernel, updated the new bootblocks with disklabel -B /dev/rwd0s2a, echo /boot/loader /boot.conf. Now, when I enter -c at the boot: prompt, it boots with the new boot loader, and never goes into UserConfig (it continues booting as if I never entered -c at the boot prompt). Donn To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
On Mon, 15 Feb 1999, Donn Miller wrote: Kris Kennaway wrote: On Mon, 15 Feb 1999, Donn Miller wrote: I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Did that. I installed the kernel, updated the new bootblocks with disklabel -B /dev/rwd0s2a, echo /boot/loader /boot.conf. Now, when I enter -c at the boot: prompt, it boots with the new boot loader, and never goes into UserConfig (it continues booting as if I never entered -c at the boot prompt). That sounds like a bug, but the boot: prompt is NOT the new boot loader, it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you actually yet to BTX, try boot -c. Donn To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New print interface
Chuck Robey wrote: If IO is generic, then printing the type of printer it finds is meaningless, right? It's going to announce generic no matter what, then it should stay silent, right? Better to say nothing than to get it wrong every time, especially with the correct info sitting mere lines above, advertising the mistake. This would be like not showing the ide cd-rom drive manufacturer/model. They are all atapi, sure, but it is nice to know what it call itself. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
Donn Miller wrote: Kris Kennaway wrote: On Mon, 15 Feb 1999, Donn Miller wrote: I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Did that. I installed the kernel, updated the new bootblocks with disklabel -B /dev/rwd0s2a, echo /boot/loader /boot.conf. Now, when I enter -c at the boot: prompt, it boots with the new boot loader, and never goes into UserConfig (it continues booting as if I never entered -c at the boot prompt). Sorry for not answering this the first time... I'm having a little trouble typing... :-( At the loader prompt (which you can get at by typing anything at the autoboot message), type boot -c. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
Brian Feldman wrote: That sounds like a bug, but the boot: prompt is NOT the new boot loader, it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you actually yet to BTX, try boot -c. Terminology errors abound here. I know, because I made many of them in the past. boot0 is the booteasy prompt (F?). BTX is a kernel. Prompt doesn't apply here. The twisting | is boot2. If you type something at this time, you get boot2 prompt. Unless you type enter, od course. The later stage is called loader. So, change BTX with loader, and your advice stands. :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
At the prompt: set boot_userconfig boot Tom Veldhouse ve...@visi.com -Original Message- From: Donn Miller dmm...@bellatlantic.net To: Kris Kennaway kkenn...@physics.adelaide.edu.au Cc: curr...@freebsd.org curr...@freebsd.org Date: Monday, February 15, 1999 6:34 AM Subject: Re: Problesm w/ 4.0-current wine Kris Kennaway wrote: On Mon, 15 Feb 1999, Donn Miller wrote: I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Did that. I installed the kernel, updated the new bootblocks with disklabel -B /dev/rwd0s2a, echo /boot/loader /boot.conf. Now, when I enter -c at the boot: prompt, it boots with the new boot loader, and never goes into UserConfig (it continues booting as if I never entered -c at the boot prompt). Donn To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
On Mon, 15 Feb 1999, Daniel C. Sobral wrote: Brian Feldman wrote: That sounds like a bug, but the boot: prompt is NOT the new boot loader, it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you actually yet to BTX, try boot -c. Terminology errors abound here. I know, because I made many of them in the past. boot0 is the booteasy prompt (F?). BTX is a kernel. Prompt doesn't apply here. The twisting | is boot2. If you type something at this time, you get boot2 prompt. Unless you type enter, od course. The later stage is called loader. So, change BTX with loader, and your advice stands. :-) Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is the kernel loader, and they're all by Mr. Nordier. The BTX loader does have a prompt by default and if you interrupt the countdown. The prompt is, of course, Forth :) -- Daniel C. Sobral (8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Weird piecemeal reads over socketpair() pipe breaks up small writes into even smaller reads.
Ok, so perhaps tweeking the rescheduling changes in kern_subr.c to not try to do it in the first few thousand bytes copied is the solution? kern_subr.c can't do that, because `struct uio' doesn't give the original count. Would you like to do it or should I? This isn't high priority but it should definitely not be rescheduling after the first 96 bytes. That's just a waste of cpu. The waste for rescheduling should be insignificant, since it should only occur every ROUNDROBIN_INTERVAL (default 100 msec). It actually seems to be rescheduling more often. Rescheduling _after_ the first 96 bytes is surprising, since the rescheduling is done before doing any i/o, so sync effects from sleep(1) should cause rescheduling before any i/o is done. Then the reader won't run, but other processes may. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
Kris Kennaway wrote: On Mon, 15 Feb 1999, Donn Miller wrote: I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Did that. I installed the kernel, updated the new bootblocks with disklabel -B /dev/rwd0s2a, echo /boot/loader /boot.conf. Now, when I enter -c at the boot: prompt, it boots with the new boot loader, and never goes into UserConfig (it continues booting as if I never entered -c at the boot prompt). /boot.conf is completely ignored; it does nothing. You should have nothing in /boot.config or /boot.help (delete them both). Use the 'help' command in the loader, or read any of the dozens of posts I've made on this topic to date. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
That sounds like a bug, but the boot: prompt is NOT the new boot loader, it's the semi-new boot0 (which is quite nice, Mr. Nordier). 'boot:' comes from boot2, actually. When you actually yet to BTX, try boot -c. ... and you never get to BTX, you end up the loader. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How to power off an ATX power supply machine on shutdown ?
Is a delay needed between the final sync's and the actual power off? Apparently so. There is/was a recently added sysctl for this purpose. Poke around in the archives. Was that sysctl added to the -STABLE branch? I am running 3.1-BETA and I cannot find it. No, they were added after the split and weren't backported to the 3.x branch. But if you are impatient, you could just grab a copy of sys/kern/kern_shutdown.c from a 4.0 branch and copy it to your tree. The added sysctl is for now the only difference in this file. Then you can specify somewhere in your rc files sysctl -w kern.shutdown.poweroff_delay = x with x measured in ms. I have only seen one machine so far which suffers this problem of powering off the machine too fast. On all other machines I know of either the mainboard or the power supply (don't know which) have a small delay before powering off the machine, which seems to be long enough for the drives to flush their buffers. On this particular machine, I set the delay to 1.5 seconds, and I never got unclean filesystems again. Daniel To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
easily reproducible NFS-related panic
Sorry for the cross-posting, but I am running -STABLE and I would like to hear from -CURRENT users about this problem. The panic is easily reproducible: simply, try to hard-link a file from a local filesystem to a NFS-mounted one (yes, I _know_ that this is non-sense): mount remotesys:/exportedfs /mnt cd /mnt ln /bin/ls . -- this complaints about cross-device link, OK ln /bin/ls . -- (yes, again) panic: vrele: negative ref cnt -- CRASH!!! I have confirmed this with recent 3.0-STABLE and 3.1-BETA clients and servers, and also with a Solaris 2.5.1 NFS server. However, it does not happen on a 2.2.8-RELEASE client. Some feedback from the NFS gurus ;-) would be very useful. -- JMA --- José Mª Alcaide | mailto:j...@we.lc.ehu.es Universidad del País Vasco | mailto:j...@es.freebsd.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 --- Go ahead... make my day. - H. Callahan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panics deciphering VMSTAT output
Previously on Sun, Feb 14, 1999 at 09:37:01PM -0500, tc...@staff.circle.net wrote: : I've been trying to track down a regular, but not : manually reproducible crash in 3.0-BETA (19990205). : : I can't get a crashdump due to a DSCHECK negative : number bug. I think my swap space of 3+GB is : too large for it. So, I've been having it send We have seen this too DANGER editing your disklabel to have only 2GB swap, without displacing the other partitions fixes this/DANGER[1] : me the output of vmstat -m every 15 minutes to : try to track it down. The couple of times I've : seen the panic message on the console, it was : typically, but not always: : pipeinit: cannot allocate pipe - out of kvm We were also seeing this Matt (Frost) found an outstanding PR with a suggested fix that reordered some code, we haven't seen this crash since (5 days). (Vague I know maybe Matt will be along in a bit.) [1] Do not atempt ot do this unlest you are **VERY*** ***VERY*** sure you know what you are doing ***AND*** what will happen if you do it wrong. -- GeoffB To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: easily reproducible NFS-related panic
:Sorry for the cross-posting, but I am running -STABLE and I would :like to hear from -CURRENT users about this problem. : :The panic is easily reproducible: simply, try to hard-link a file :from a local filesystem to a NFS-mounted one (yes, I _know_ that :this is non-sense): :.. : : mount remotesys:/exportedfs /mnt : cd /mnt : ln /bin/ls . -- this complaints about cross-device link, OK : ln /bin/ls . -- (yes, again) : panic: vrele: negative ref cnt -- CRASH!!! : :I have confirmed this with recent 3.0-STABLE and 3.1-BETA clients :and servers, and also with a Solaris 2.5.1 NFS server. However, :it does not happen on a 2.2.8-RELEASE client. : :Some feedback from the NFS gurus ;-) would be very useful. : :-- JMA :--- :José Mª Alcaide | mailto:j...@we.lc.ehu.es :Universidad del País Vasco | mailto:j...@es.freebsd.org This was fixed yesterday. Get the latest -stable and see if it still occurs. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Weird piecemeal reads over socketpair() pipe breaks up small writes into even smaller reads.
:kern_subr.c can't do that, because `struct uio' doesn't give the original :count. : :Would you like to do it or should I? This isn't high priority but it :should definitely not be rescheduling after the first 96 bytes. That's :just a waste of cpu. : :The waste for rescheduling should be insignificant, since it should only :occur every ROUNDROBIN_INTERVAL (default 100 msec). It actually seems :to be rescheduling more often. Rescheduling _after_ the first 96 bytes :is surprising, since the rescheduling is done before doing any i/o, so :sync effects from sleep(1) should cause rescheduling before any i/o is :done. Then the reader won't run, but other processes may. : :Bruce sleep() is not relevant... what is relevant is that the sub-process is doing a write() while the parent is sitting in a select() -- the parent process is thus going to have priority over the child. The moment the child allows a reschedule, the parent gets the cpu. I would like to point out that this type of situation will occur with most piping situations. The reader is almost always blocked waiting to read while the writer is obviously always running, in the middle of the write. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: support for 3Com 3C575 network controller?
On Sat, 13 Feb 1999, Steve Price wrote: Is anyone out there successfully using a 3Com 3C375 network controller in there laptop? I got a new Dell Inspiron 7000 that came with one of these jewels and I haven't been able to find the trick to make it work. CardBus cards aren't supported. Period. Doug White Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Weird piecemeal reads over socketpair() pipe breaks up small writes into even smaller reads.
Isn't it easier to reclassify the bug as uipc_send() wakes up the reader before it's done appending the data from a write() to the socket buffer and use my patch? I don't think it makes sense for uipc_send() to depend on sorwakeup() not actually waking up anyone in certain situations. Bill To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: easily reproducible NFS-related panic
On 15 February 1999, Jose M. Alcaide proclaimed: Sorry for the cross-posting, but I am running -STABLE and I would like to hear from -CURRENT users about this problem. The panic is easily reproducible: simply, try to hard-link a file from a local filesystem to a NFS-mounted one (yes, I _know_ that this is non-sense): mount remotesys:/exportedfs /mnt cd /mnt ln /bin/ls . -- this complaints about cross-device link, OK ln /bin/ls . -- (yes, again) panic: vrele: negative ref cnt -- CRASH!!! I have confirmed this with recent 3.0-STABLE and 3.1-BETA clients and servers, and also with a Solaris 2.5.1 NFS server. However, it does not happen on a 2.2.8-RELEASE client. Some feedback from the NFS gurus ;-) would be very useful. A fix for this has just recently been committed to 4.0. Look through -current in the last week for mail from myself, matt dillon and a couple of others about negative ref cnt. It's a simple one line patch to fix. I'm not sure if Matt has committed the fix to -stable yet. -- Dom Mitchell -- Palmer Harvey McLane -- Unix Systems Administrator Free your mind -- http://www.opensource.org/ -- ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ** To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: support for 3Com 3C575 network controller?
On Mon, 15 Feb 1999, Doug White wrote:
# CardBus cards aren't supported. Period.
Eek, I didn't realize this was a CardBus card. :{ I quess
this begs the question though, is anyone working on CardBus
support for FreeBSD since this is the 32-bit version of
PCMCIA? Yes I understand they are *completely* different.
Just curious.
Thanks, Steve
# Doug White
# Internet: dwh...@resnet.uoregon.edu| FreeBSD: The Power to Serve
# http://gladstone.uoregon.edu/~dwhite| www.freebsd.org
#
#
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Problems in VM structure ?
Hi. I saw that my 4-CURRENT box from 8 February dropped to ddb after my last make world. I rebuilt world today, and the same problem is occuring. These problems started occuring after Matt Dillon's changes to the VM system. What is worrying/troubling is that in single user mode, the machine is stable, and manages to build world without a problem. When booted into multi-user mode, it's stable and usable for anywhere from 1 to 3 hours, and then panics. There are no active users on at the time, and the machine is not heavily loaded (0.0-0.2) I suspected a hardware error, so swopped all the RAM from a production machine, and it still produces the same fault. The error is panic: vm_fault: fault on nofault entry, addr : f2572000 Debugger (panic) Stopped at Debuger+0x37: movl $0,in_Debugger When I hit c, I get this : Syncing disks... Fatal trap 12 : page fault while in kernel mode fault virtual address = 0x18 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0145d98 stack pointer = 0x10:0xf79b97fc frame pointer = 0x10:0xf79b9810 code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 2035 (sendmail) interrupt mask = net tty bio cam kernel: type 12 trap, code=0 stopped at softclock+0x48: cmpl %esi,0x8 (%ecx) Does anyone know what this means ? The machine was idle at the time - I'm the only user, and it isn't used as a public access server. The process varies, sometimes httpd, other times sendmail. I am using CAM, softupdates and NFS (not heavily though). I haven't seen anything like this on -current or -hackers, and searching the mailing lists didn't reveal anything relevant. The only non standard thing I'm doing is disabling the vfs reallockblks that was causing the machine to panic months ago. I re-enabled it, and it still does the same thing. So, that's not it. I'm doing this by issuing /sbin/sysctl -w vfs.ffs.doreallocblks=0 on boot up. My kernel config and dmesg is listed below. TIA! dmesg - Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Feb 15 12:50:24 SAST 1999 r...@chain.freebsd.os.org.za:/usr/src/sys/compile/CHAIN Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 200455997 Hz CPU: Pentium/P54C (200.46-MHz 586-class CPU) Origin = GenuineIntel Id = 0x52c Stepping=12 Features=0x1bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8 real memory = 67108864 (65536K bytes) avail memory = 62050304 (60596K bytes) Preloaded elf kernel kernel at 0xf02c9000. ccd0-1: Concatenated disk drivers Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=1039 device=5591) rev 0x02 on pci0.0.0 ide_pci0: PCI IDE controller (busmaster capable) rev 0xd0 int a irq 14 on pci0.0.1 chip1: SiS 85c503 rev 0x01 on pci0.1.0 chip2: PCI to PCI bridge (vendor=1039 device=0001) rev 0x00 on pci0.2.0 vga0: S3 Trio graphics accelerator rev 0x53 int a irq 10 on pci0.9.0 de0: Digital 21041 Ethernet rev 0x11 int a irq 5 on pci0.13.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:f9:2f:c8 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit 01f0:0: warning, IDE controller timing not set wdc0: unit 0 (wd0): WDC AC21000H, DMA, 32-bit, multi-block-16 wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S ide_pci: generic_dmainit 01f0:1: warning, IDE controller timing not set wdc0: unit 1 (wd1): QUANTUM FIREBALL1080A, DMA, 32-bit, multi-block-8 wd1: 1039MB (2128896 sectors), 2112 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit 0170:0: warning, IDE controller timing not set wdc1: unit 0 (wd2): ST32140A, DMA, 32-bit, multi-block-32 wd2: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S ppc0 at 0x378 irq 7 on isa ppc0: Winbond chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 ppi0: generic parallel i/o on ppbus 0 aha0 at 0x330-0x333 irq 11 drq 6 on isa aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs npx0 on motherboard npx0: INT 16 interface vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa de0: enabling 10baseT port Intel Pentium detected, installing workaround for F00F bug IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging limited to 100 packets/entry de0 XXX:
Re: support for 3Com 3C575 network controller?
On Mon, 15 Feb 1999, Steve Price wrote:
On Mon, 15 Feb 1999, Doug White wrote:
# CardBus cards aren't supported. Period.
Eek, I didn't realize this was a CardBus card. :{ I quess
this begs the question though, is anyone working on CardBus
support for FreeBSD since this is the 32-bit version of
PCMCIA? Yes I understand they are *completely* different.
Just curious.
No-one is actively working on it right now. I do own one of the cards and
it should be possible to use the existing xl driver without too many
changes after the initial cardbus hurdle is dealt with. Paid work is
monopolising my time right now, so I don't expect to play with it anytime
soon.
--
Doug Rabson Mail: d...@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
Hi. I saw that my 4-CURRENT box from 8 February dropped to ddb after my last make world. I rebuilt world today, and the same problem is occuring. These problems started occuring after Matt Dillon's changes to the VM system. What is worrying/troubling is that in single user mode, the machine is stable, and manages to build world without a problem. When booted into multi-user mode, it's stable and usable for anywhere from 1 to 3 hours, and then panics. There are no active users on at the time, and the machine is not heavily loaded (0.0-0.2) I suspected a hardware error, so swopped all the RAM from a production machine, and it still produces the same fault. The error is panic: vm_fault: fault on nofault entry, addr : f2572000 This indicates an unmapped struct buf, should be a software bug. Debugger (panic) Stopped at Debuger+0x37: movl $0,in_Debugger When I hit c, I get this : Could you type in bt next time this happens, and post the result? -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problems in VM structure ?
On Monday, 15 February 1999 at 18:00:16 -0500, Luoqi Chen wrote: Hi. I saw that my 4-CURRENT box from 8 February dropped to ddb after my last make world. I rebuilt world today, and the same problem is occuring. These problems started occuring after Matt Dillon's changes to the VM system. What is worrying/troubling is that in single user mode, the machine is stable, and manages to build world without a problem. When booted into multi-user mode, it's stable and usable for anywhere from 1 to 3 hours, and then panics. There are no active users on at the time, and the machine is not heavily loaded (0.0-0.2) I suspected a hardware error, so swopped all the RAM from a production machine, and it still produces the same fault. The error is panic: vm_fault: fault on nofault entry, addr : f2572000 This indicates an unmapped struct buf, should be a software bug. Debugger (panic) Stopped at Debuger+0x37: movl $0,in_Debugger When I hit c, I get this : Could you type in bt next time this happens, and post the result? It's t in ddb, not bt. Isn't consistency wonderful? Khetan, you should also take a dump. The backtrace is a good start, but it probably won't be enough to solve the problem. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ifq_maxlen on lo0
On Thu, Feb 11, 1999 at 12:53:05PM -0500, Chuck Robey wrote: My boot messages recently have included a warning about the lo0 interface not setting the ifq_maxlen. Same here. Rebuilt a few hours ago, and now I see: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 1000 packets/entry lo0 XXX: driver didn't set ifq_maxlen Not sure if it is significant that I'm using IPFIREWALL. I'll do some digging. -Jamie To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ifq_maxlen on lo0
On Tue, 16 Feb 1999, Jamie Clark wrote: On Thu, Feb 11, 1999 at 12:53:05PM -0500, Chuck Robey wrote: My boot messages recently have included a warning about the lo0 interface not setting the ifq_maxlen. Same here. Rebuilt a few hours ago, and now I see: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging limited to 1000 packets/entry lo0 XXX: driver didn't set ifq_maxlen Not sure if it is significant that I'm using IPFIREWALL. I'll do some digging. Yeah. I saw where the problem is, but I haven't the network experience to tell what the *right* fix is, to set the struct up, or to disable the error message. I think it was in if_loop.c. -Jamie To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message +--- Chuck Robey | Interests include any kind of voice or data chu...@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). +--- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is the kernel loader, and they're all by Mr. Nordier. Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap; all by Robert. The loader, OTOH, uses Robert's BTX code, Ficl, and a lot of code derived by me from the NetBSD standalone loader. The BTX loader does have a prompt by default and if you interrupt the countdown. The prompt is, of course, Forth :) The BTX loader doesn't have a prompt at all. The kernel loader has a prompt, and the prompt is not written in Forth (yet). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
HELP: vm_fault
Can anyone give me a hand with this problem? Machines are dropping like flies from this, one I haven't managed to get back at all (hangs on syncing disks). Anyway, this web server runs just fine for 1 - 3 days, then loses one of it's drives (da1). I'm not a kernel hacker, so I was looking for advice on exactly what I need to do to get this fixed. Ever since switching to 3.0 Release I have had any number of problems, while my 971025 3.0 snapshot was like a rock. Would it be in my best interest to drop back to this snapshot (as painful as that would be)? I did go back and check messages regarding this problem, but they all seem to involve NFS problems. I am not running nfs on this system at all. Any an all help would be GREATLY appreciated. Thanks. -Ted Feb 15 20:20:53 dns /kernel: Unexpected busfree. LASTPHASE == 0x0 Feb 15 20:20:54 dns /kernel: SEQADDR == 0x10f Feb 15 20:20:54 dns /kernel: (da1:ahc0:0:1:0): Invalidating pack Feb 15 20:20:54 dns last message repeated 4 times Feb 15 20:20:54 dns /kernel: spec_getpages: I/O read failure: (error code=6) Feb 15 20:20:54 dns /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Feb 15 20:21:37 dns /kernel: spec_getpages: I/O read failure: (error code=6) ... 100+ lines cut ... Feb 15 20:21:37 dns /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Feb 15 20:21:37 dns /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 1 Feb 15 20:21:37 dns /kernel: vm_fault: pager read error, pid 26342 (httpd) Feb 15 20:24:10 dns reboot: rebooted by ted Feb 15 20:24:10 dns syslogd: exiting on signal 15 Feb 15 20:25:55 dns /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Feb 15 20:25:55 dns /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 15 20:25:55 dns /kernel: The Regents of the University of California. All rights reserved. Feb 15 20:25:55 dns /kernel: FreeBSD 3.0-RELEASE #0: Sun Nov 8 12:47:59 PST 1998 Feb 15 20:25:55 dns /kernel: r...@dns.wwwtek.com:/usr/src/sys/compile/wwwtek Feb 15 20:25:55 dns /kernel: Timecounter i8254 frequency 1193182 Hz cost 2848 ns Feb 15 20:25:55 dns /kernel: Timecounter TSC frequency 300683425 Hz cost 160 ns Feb 15 20:25:55 dns /kernel: CPU: Pentium II (300.68-MHz 686-class CPU) Feb 15 20:25:55 dns /kernel: Origin = GenuineIntel Id = 0x633 Stepping=3 Feb 15 20:25:55 dns /kernel: Features=0x80fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,MMX Feb 15 20:25:55 dns /kernel: real memory = 335544320 (327680K bytes) Feb 15 20:25:55 dns /kernel: avail memory = 323284992 (315708K bytes) Feb 15 20:25:55 dns /kernel: Probing for devices on PCI bus 0: Feb 15 20:25:55 dns /kernel: Correcting Natoma config for non-SMP Feb 15 20:25:55 dns /kernel: chip0: Intel 82440FX (Natoma) PCI and memory controller rev 0x02 on pci0.0.0 Feb 15 20:25:55 dns /kernel: chip1: Intel 82371SB PCI to ISA bridge rev 0x01 on pci0.7.0 Feb 15 20:25:55 dns /kernel: vga0: ATI Mach64-GX graphics accelerator rev 0x01 on pci0.17.0 Feb 15 20:25:55 dns /kernel: fxp0: Intel EtherExpress Pro 10/100B Ethernet rev 0x05 int a irq 10 on pci0.18.0 Feb 15 20:25:55 dns /kernel: fxp0: Ethernet address 00:a0:c9:e0:fa: Feb 15 20:25:55 dns /kernel: e4 Feb 15 20:25:56 dns /kernel: ahc0: Adaptec 2940 Ultra SCSI adapter rev 0x00 int a irq 11 on pci0.19.0 Feb 15 20:25:56 dns /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Feb 15 20:25:56 dns /kernel: Probing for devices on the ISA bus: Feb 15 20:25:56 dns /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Feb 15 20:25:56 dns /kernel: sc0: VGA color 16 virtual consoles, flags=0x0 Feb 15 20:25:56 dns /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Feb 15 20:25:56 dns /kernel: sio0: type 16550A Feb 15 20:25:56 dns /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Feb 15 20:25:56 dns /kernel: sio1 not found at 0x2f8 Feb 15 20:25:56 dns /kernel: psm0 not found at 0x60 Feb 15 20:25:56 dns /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Feb 15 20:25:56 dns /kernel: fdc0: FIFO enabled, 8 bytes threshold Feb 15 20:25:56 dns /kernel: fd0: 1.44MB 3.5in Feb 15 20:25:56 dns /kernel: wt0 not found at 0x300 Feb 15 20:25:56 dns /kernel: npx0 on motherboard Feb 15 20:25:56 dns /kernel: npx0: INT 16 interface Feb 15 20:25:56 dns /kernel: Waiting 15 seconds for SCSI devices to settle Feb 15 20:25:56 dns /kernel: changing root device to da0s1a Feb 15 20:25:56 dns /kernel: da1 at ahc0 bus 0 target 1 lun 0 Feb 15 20:25:56 dns /kernel: da1: SEAGATE ST19101W 0014 Fixed Direct Access SCSI2 device Feb 15 20:25:56 dns /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled Feb 15 20:25:56 dns /kernel: da1: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Feb 15 20:25:56 dns /kernel: da0 at ahc0 bus 0 target 0 lun 0 Feb 15 20:25:56 dns /kernel: da0: SEAGATE ST19101W 0014 Fixed Direct Access SCSI2 device Feb 15 20:25:56 dns /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, Feb 15 20:25:56 dns /kernel: 16bit), Tagged Queueing Enabled Feb 15 20:25:56 dns
Re: HELP: vm_fault
I'd move forward, not back.. take the 3.1 release that will be available in a day or so.. 3.0 was a bit experimental still. On Mon, 15 Feb 1999, T.D. Brace wrote: Can anyone give me a hand with this problem? Machines are dropping like flies from this, one I haven't managed to get back at all (hangs on syncing disks). Anyway, this web server runs just fine for 1 - 3 days, then loses one of it's drives (da1). I'm not a kernel hacker, so I was looking for advice on exactly what I need to do to get this fixed. Ever since switching to 3.0 Release I have had any number of problems, while my 971025 3.0 snapshot was like a rock. Would it be in my best interest to drop back to this snapshot (as painful as that would be)? I did go back and check messages regarding this problem, but they all seem to involve NFS problems. I am not running nfs on this system at all. Any an all help would be GREATLY appreciated. Thanks. -Ted Feb 15 20:20:53 dns /kernel: Unexpected busfree. LASTPHASE == 0x0 Feb 15 20:20:54 dns /kernel: SEQADDR == 0x10f Feb 15 20:20:54 dns /kernel: (da1:ahc0:0:1:0): Invalidating pack Feb 15 20:20:54 dns last message repeated 4 times Feb 15 20:20:54 dns /kernel: spec_getpages: I/O read failure: (error code=6) Feb 15 20:20:54 dns /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Feb 15 20:21:37 dns /kernel: spec_getpages: I/O read failure: (error code=6) ... this looks a bit like a bad disk or scsi power supply.. 100+ lines cut ... Feb 15 20:21:37 dns /kernel: size: 4096, resid: 4096, a_count: 4096, valid: 0x0 Feb 15 20:21:37 dns /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 1 Feb 15 20:21:37 dns /kernel: vm_fault: pager read error, pid 26342 (httpd) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Netscape, again
Chris Tubutis ch...@tci.com writes: whenever I click a mailto: HREF it inadvertly dumps core. Does it truly dump core, or does it merely go away? Can't speak for the original poster, but my Netscrap 4.5 shows the same behaviour: [16]a...@darkstar:/alex #/usr/local/netscape/netscape [now clicking on a mailto:] zsh: bus error /usr/local/netscape/netscape [17]a...@darkstar:/alex #lsl *.core -rw--- 1 alex staff 5697536 Feb 16 02:52 netscape.core Launching the messgenger before using any mailto: links does in fact help. P.S. -current, everything ELF (except netscape of course). Not that I think that matters... -- # /AS/ http://privat.schlund.de/entropy/ # To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
On Mon, 15 Feb 1999, Mike Smith wrote: Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is the kernel loader, and they're all by Mr. Nordier. Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap; all by Robert. The loader, OTOH, uses Robert's BTX code, Ficl, and a lot of code derived by me from the NetBSD standalone loader. Boot2 is, as you say, correctly identified as the bootstrap, however you cannot deny that boot2 is a kernel loader as it can load a pure executable (a.out kernel or /boot/loader) or an ELF kernel. The BTX loader does have a prompt by default and if you interrupt the countdown. The prompt is, of course, Forth :) The BTX loader doesn't have a prompt at all. The kernel loader has a prompt, and the prompt is not written in Forth (yet). By BTX loader I refer to the BTX kernel and system which can bootstrap a kernel and load modules. The prompt isn't OF Forth, I stated that the prompt TAKES Forth; perhaps I could have said that better. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
vesa and X wierdness
Hi, if I load the vesa kld module from loader.rc, in order to use a high-res splash screen, when X starts the screen is very dim. Usually I start xdm from ttys, but its the same if I use startx. The cursor looks normal, its really bright against the dim screen. Its fine if I don't load vesa and use a 320x200 splash screen, and if I do load it, the vesa modes work great; I can load a 1024x768 splash image, its just when X starts. I'm running 4.0-current as of about noon on Sunday, Diamond Viper V330 pci video card (riva 128) on a pci motherboard (no agp). I've also got a bt848 TV card, but I doubt that would affect it. Not sure what else would be significant. I imagine its something peculiar to my video card, the console text used to be a gross yellow when I used vesa, but that's been fixed. I didn't want to send huge boot -v or dmesg output to the list until I got some feedback. Thanks To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: vesa and X wierdness
Hi, if I load the vesa kld module from loader.rc, in order to
use a high-res splash screen, when X starts the screen is very dim.
Usually I start xdm from ttys, but its the same if I use startx.
The cursor looks normal, its really bright against the dim screen.
Its fine if I don't load vesa and use a 320x200 splash screen,
and if I do load it, the vesa modes work great; I can load
a 1024x768 splash image, its just when X starts.
Please try the attached patch for /sys/i386/isa/vesa.c and
see if it works.
Kazu
--- vesa.c-1.17 Sun Feb 7 14:01:43 1999
+++ vesa.c Tue Feb 16 16:36:02 1999
@@ -838,9 +838,9 @@
if ((adp == vesa_adp) (vesa_adp_info-v_flags V_DAC8)
((bits = vesa_bios_set_dac(8)) 6)) {
error = vesa_bios_save_palette(0, 256, palette, bits);
+ vesa_bios_set_dac(6);
if (error == 0)
return 0;
- vesa_bios_set_dac(6);
}
return (*prevvidsw-save_palette)(adp, palette);
@@ -855,9 +855,9 @@
if ((adp == vesa_adp) (vesa_adp_info-v_flags V_DAC8)
((bits = vesa_bios_set_dac(8)) 6)) {
error = vesa_bios_load_palette(0, 256, palette, bits);
+ vesa_bios_set_dac(6);
if (error == 0)
return 0;
- vesa_bios_set_dac(6);
}
return (*prevvidsw-load_palette)(adp, palette);
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Problesm w/ 4.0-current wine
I spent sometime just staring at the subject, before reading the message, trying to remember if I had been to any FreeBSD drinking problems thread... :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: vesa and X wierdness
Please try the attached patch for /sys/i386/isa/vesa.c and see if it works. Kazu Yes, that worked. No more dim screen. Thanks alot! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
