Re: cy0: port not found
q wrote: > Hi, I need some advice to build dial-in server. > I've Cyclades Cyclom 32 YeP and FreeBSD 4.3. > This is first time for me to Install multiport Serial. > I'm trying to look at FreeBSD 4.3 manual : > > # man cy > > and I follow to add the lines to my kernel options, > recompile it, and restart the computer. > But reported : > > cy0: port not found > > What should I do ??? > Thank's. Maybe you forgot to make the devices cuac00 - cuac0v with # sh /dev/MAKEDEV cuac0. And you also want to to al look in /etc/rc.serial at the cyclades section I guess. Success, Arjan Knepper > > > Q > -- > Email ini dikirim oleh PlasaCom : http://www.plasa.com > Cepat di-download via TelkomNet Instan http://www.plasa.com/instan > Rindukah Anda bertemu dengan ex teman-teman satu sekolah dulu ? > Kunjungilah mereka (47.033 anggota) di KSI : http://ksi.plasa.com > -- > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Kernel Console speed
Dear People, I have configured a couple of machines to use the serial console. Now with some machines, the console speed cannot be set correctly. I have read the appropriate chapters in the handbook, and I getting the serial console working at all, is not a problem. Just the speed setting does not work at _some_ machines. As far as I understand it, there are several components that interact as (serial) console: - boot2 - loader - the kernel - the getty (if a getty is configured at the console device) My problems only apply to the kernel, not to the bootstrap, and the getty intially uses, what the kernel used. What I did: set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf set options CONSPEED=38400 in KERNEL compiled and installed kernel and new bootstrap (with disklabel). changed /etc/ttys to use std.38400 as argument to getty. further: set machdep.conspeed=38400 in /boot/loader.conf I've checked with kgdb the constants in the debugging kernel, that in /sys/isa/sio.c:sysctl_machdep_comdefaultrate() comdefaultrate is indeed 38400. The bootstraps works with 38400, (both boot2 and loader), but as soon as the kernel boots, it switches back to 9600. If the system is up, I can change the sysctl parameter: sysctl -w machdep.conspeed=38400 back to 38400, which works then (it also worked automaticalle if I place this in /etc/sysctl.conf). But I seem to have no chance to make it actually boot with that speed, so that the booting messages of the kernel can be viewed from the console-server. I run 4.3-STABLE on the box. The strange things is, that it works on another machine, but not on two other ones. All run the same release, all are i386 PCs with 16550A UARTs. The hardware is of course capable of running at different speeds than 9600, since the bootstrap runs at 38400 and a running system can be set to it, too. The hardware is very different though: Working boxes: Athlon 700 on Asus A7V Not working ones: Dell PowerEdge 4/200: 4xPPro 200 SMP, (with chipset info) Intel 82454KX/GX (Orion) host to PCI bridge Intel 82375EB PCI-EISA bridge Thanks and Best regards, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - *Daniel Lang * [EMAIL PROTECTED] * +49 89 289 25735 * http://www.leo.org/~dl/* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bootable CD IV
So, I guess my next questions is: How do create the 2.88M boot floppy image with the MFS stuff on it? I guess it merges somehow inside the kernel? Am I right? If so, how do i compile my mfs into the kernel, and what do I put in the MFS? Also, what files do I need to put on the boot floppy and what configuration files do I need to edit? If I cannot mount the cd as /, and only the MFS can be /, then can I at lease mount it as /usr? I am assuming I would edit /etc/rc.local on the mfs root. What I am wanting is a bootable cd that will take the user into an automatic restore script, that will ask them to put the last tape in the drive, and do a fdisk, disklabel, and newfs the hard drive, then restore from tape. Basicly, it's a foolproof method for disaster recovery is what i am trying to get at. Thanks. Sincerely, Rick Duvall On Tue, 1 May 2001, Jordan Hubbard wrote: > From: Rick Duvall <[EMAIL PROTECTED]> > Subject: Bootable CD IV > Date: Tue, 1 May 2001 12:03:21 -0700 (PDT) > > > So, let me get this straight: To make a bootable CD, you need to: > > [steps alided] > > That will essentially work, yes, though I've never seen someone use > /usr directly as a scratch directory before. :-) > > > Okay, got that far. But, it will load the kernel, then hang and say that > > it cannot mount root device /dev/fd0. This doesn't make any sense to me > > becuase I specifically told fstab on the cd to use the cdrom as root. Am > > I stupid or something? > > Not stupid, just not thinking this all the way through. The root > mounting code runs well ahead of anything which looks into /etc/fstab; > how indeed could it even find fstab if it didn't know where the root > partition was? You need to change the kernel's mind about where to > find its root partition, something which can be accomplished in a > variety of ways. In the case of the boot floppy, we don't even try; > we just use MFS for the root partition and mount the CD elsewhere. > Of all the options, this is in fact the simplest. > > - Jordan > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cy0: port not found
Arjan Knepper wrote: > > q wrote: > > > Hi, I need some advice to build dial-in server. > > Maybe you forgot to make the devices cuac00 - cuac0v with # sh > /dev/MAKEDEV cuac0. Is this also necessary when you use the kernel option DEVFS? -- Falco KrepelPhone: +49-(0)30 - 34 63 - 7 276 GMD-FOKUS Fax:+49-(0)30 - 34 63 - 8 276 Kaiserin-Augusta-Allee 31 e-mail: [EMAIL PROTECTED] 10589 BerlinWWW:http://www.fokus.gmd.de/usr/krepel To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On Wed, May 02, 2001 at 02:16:00AM -0500, Andrew Hesford wrote: > The screensaver isn't bad, and it gets pretty trippy when you focus at > infinity and let the 3D-Illusions (TM) effect set in. If I were to make > one suggestion, it would be to animate Beastie, so that he walks around > the screen rather than teleporting everywhere. Heh. My main aim was to make it as low-overhead as possible for my poor old firewall box, but animating him wouldn't add much, especially on modern computers. :) > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. I agree; however I'm running FreeBSD on my firewall box, which has an old vga monitor which isn't DPMS-capable, so it doesn't really ever shut down unless I turn it off. For all I know I may be the only one who actually uses these screensavers. So I thought I'd try maximize my entertainment value. -Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bootable CD IV
From: Rick Duvall <[EMAIL PROTECTED]> Subject: Re: Bootable CD IV Date: Wed, 2 May 2001 09:16:13 -0700 (PDT) > So, I guess my next questions is: > > How do create the 2.88M boot floppy image with the MFS stuff on it? I > guess it merges somehow inside the kernel? Am I right? If so, how do i > compile my mfs into the kernel, and what do I put in the MFS? In the interests of sparing my fingers, I'll simply direct you to /usr/src/release/Makefile at this point; you can see how it builds the mfsroot.flp bits and how it also stuffs them into a "big kernel" for the boot.flp bits. Don't be surprised if you have to read it about 11 times to really get the gist, but it will eventually make sense if you have the patience. :) Good luck! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Bootable CD IV
On Wed, May 02, 2001 at 09:59:26AM -0700, Jordan Hubbard wrote: > From: Rick Duvall <[EMAIL PROTECTED]> > Subject: Re: Bootable CD IV > Date: Wed, 2 May 2001 09:16:13 -0700 (PDT) > > > So, I guess my next questions is: > > > > How do create the 2.88M boot floppy image with the MFS stuff on it? I > > guess it merges somehow inside the kernel? Am I right? If so, how do i > > compile my mfs into the kernel, and what do I put in the MFS? > > In the interests of sparing my fingers, I'll simply direct you to > /usr/src/release/Makefile at this point; you can see how it builds the > mfsroot.flp bits and how it also stuffs them into a "big kernel" > for the boot.flp bits. Don't be surprised if you have to read > it about 11 times to really get the gist, but it will eventually > make sense if you have the patience. :) Good luck! Beer helps too.. -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) BultePowered by FreeBSD/alpha http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: new syscons screensaver
On 02-May-01 Andy Sloane wrote: > Hello, > > I just wrote a new syscons screensaver which I think is much more > interesting than the other ones, while still being relatively easy on the > CPU (much less CPU intensive than "fire", anyway). Please review it and > let me know what you think. > > It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) > floating (with a realtime shadow!) above a bunch of tiled spheres which > move around and morph. It's only one palette change per frame, until the > bsd daemon moves. > > http://fear.incarnate.net/~andude/balls.tar.gz > > I'm not on this list, so please reply directly to me. Thanks. Looks cool. I think it would be kind of cool to have the daemon walking around as well, but other than that it is neat. If you are looking for another idea for a scresn saver, a really cool one to have would be the 'swarm' or 'bees' saver either as a text or graphical one. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
> > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. > What about implementing some code from green_saver into his saver to enable DPMS support? And have a sysctl value to set the delay after the green saver will begin :) Maybe there's a better way, to let his beastie_saver.ko load green_saver.ko (and possibly unload itself) after a specified delay? G`luck, Torbjorn Kristoffersen [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On Wed, May 02, 2001 at 08:42:01PM +0200, Torbjorn Kristoffersen wrote: > > > > However, I'm quite fond of the green_saver module, which shuts down my > > monitor after 15 minutes. Other screensavers are really just for > > entertainment; I think green_saver is the only one that serves a really > > good purpose. > > > > What about implementing some code from green_saver into his saver to > enable DPMS support? And have a sysctl value to set the delay after the > green saver will begin :) Maybe there's a better way, to let his > beastie_saver.ko load green_saver.ko (and possibly unload itself) after a > specified delay? > > G`luck, > Torbjorn Kristoffersen > [EMAIL PROTECTED] > > THAT'S an idea. I would love to see some fancy screensaver put to good use, as long as I know that it will eventually turn off my monitor. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cy0: port not found
Falco Krepel wrote: > Arjan Knepper wrote: > > > > q wrote: > > > > > Hi, I need some advice to build dial-in server. > > > > Maybe you forgot to make the devices cuac00 - cuac0v with # sh > > /dev/MAKEDEV cuac0. > > Is this also necessary when you use the kernel option DEVFS? I don't know, I think it is needed as long as you want to use the /dev/cuac0* entries to access to cyclades serial ports. Arjan Knepper To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On Wed, May 02, 2001 at 08:42:01PM +0200, Torbjorn Kristoffersen wrote: > What about implementing some code from green_saver into his saver to > enable DPMS support? And have a sysctl value to set the delay after the > green saver will begin :) Maybe there's a better way, to let his > beastie_saver.ko load green_saver.ko (and possibly unload itself) after a > specified delay? Actually, looking at the code, it would be very easy to do so. The only issue is how does one set the delay... sysctl would work, I suppose, and one could introduce a general sysctl variable for screensaver standby mode timeout or something, and then all the other screensavers could be updated. Or it could be handled by the underlying screensaver driver, which seems to make more sense to me, although I don't know much about it. (i.e. after the timeout expires, stop calling the scrn_saver_t "saver" function and perform a blank_display(V_DISPLAY_STAND_BY)...) -Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel Console speed
> The bootstraps works with 38400, (both boot2 and loader), > but as soon as the kernel boots, it switches back to 9600. You forgot to edit /etc/ttys to set the getty that runs on your console port to 38400 as well. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel Console speed
Dear Mike, Mike Smith wrote on Wed, May 02, 2001 at 12:49:04PM -0700: > > The bootstraps works with 38400, (both boot2 and loader), > > but as soon as the kernel boots, it switches back to 9600. > > You forgot to edit /etc/ttys to set the getty that runs on your console > port to 38400 as well. No, I didn't, I even mentioned it: [..] > > What I did: > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf > > set options CONSPEED=38400 in KERNEL > > compiled and installed kernel and new bootstrap (with disklabel). > > changed /etc/ttys to use std.38400 as argument to getty. And additionally, if it would have been the getty, the kernel boot messages would have been printed at the right speed. Thanks anyway, Daniel -- IRCnet: Mr-Spock- Eddie would go! - Daniel Lang * [EMAIL PROTECTED] * +49 89 289 25735 * http://www.leo.org/~dl/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
Andrew Hesford wrote: > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. You might consider trying the apm_saver module instead, especially on laptops. I have found instances in the past of monitor/BIOS/video combinations where green didn't do the right thing but that the APM got right. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On Wed, 2 May 2001, Andrew Hesford wrote: > However, I'm quite fond of the green_saver module, which shuts down my > monitor after 15 minutes. Other screensavers are really just for > entertainment; I think green_saver is the only one that serves a really > good purpose. Perhaps we should make it so the green_saver can kick in after x minutes of the regular screensaver? Users would be used to this type of control. later.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
KEvent doesnt return and KEvent sample troubles
I've been looking to start using the KEvent system and I've been
experimenting with it. However I've been having several problems, with my
own code as well as samples from http://www.flugsvamp.org.
It appears I am able to create the correct structure's and register the
events. However the event never returns and never responds to any action.
For example if I use a sample which monitors the actions on a file I can
read from, and write to the file and it shows no sign of noticing.
I was wondering if it's simply a mistake of my own, however the failure for
the samples I've found has puzzled my further. I'm working on a 4.3-STABLE
machine using GCC version 2.95.3.
Here is an example of code that I am using which doesn't seem to catch any
events. Its a slightly modified version of read_test.c from flugsvamp.com
which I edit so it would compile happily.
It doesn't seem to work however.
>
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
main(int argc, char **argv)
{
int fd, kq, n;
struct kevent event[1];
struct kevent *evp[1];
char buffer[128];
struct stat st;
struct aiocb iocb;
struct timespec ts = {0, 0};
if (argc != 2)
errx(1, "Usage: %s file\n", argv[0]);
fd = open(argv[1], O_RDONLY);
if (fd < 0)
err(1, "open: %s\n", argv[1]);
lseek(fd, 0, SEEK_END);
kq = syscall(SYS_kqueue);
if (kq < 0)
err(1, "kqueue");
event[0].ident = fd;
event[0].filter = EVFILT_READ;
event[0].flags = EV_ADD | EV_ENABLE;
evp[0] = &event[0];
n = syscall(SYS_kevent, kq, 1, evp, 0, NULL, 0);
for (;;) {
n = syscall(SYS_kevent, kq, 0, NULL, 1, event, ts);
if (n < 0)
err(1, "kevent");
printf("kevent flags: 0x%x, data: 0x%x\n",
event[0].flags, event[0].data);
n = read(fd, buffer, 128);
buffer[n] = '\0';
printf("%s", buffer);
}
}
<
I'd appreciate any feedback very much.
Thank you
Dominic Marks
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: KEvent doesnt return and KEvent sample troubles
* Dominic Marks <[EMAIL PROTECTED]> [010502 14:29] wrote: > I've been looking to start using the KEvent system and I've been > experimenting with it. However I've been having several problems, with my > own code as well as samples from http://www.flugsvamp.org. www.flugsvamp.org doesn't seem to resolve. > > It appears I am able to create the correct structure's and register the > events. However the event never returns and never responds to any action. > For example if I use a sample which monitors the actions on a file I can > read from, and write to the file and it shows no sign of noticing. > > I was wondering if it's simply a mistake of my own, however the failure for > the samples I've found has puzzled my further. I'm working on a 4.3-STABLE > machine using GCC version 2.95.3. > > Here is an example of code that I am using which doesn't seem to catch any > events. Its a slightly modified version of read_test.c from flugsvamp.com > which I edit so it would compile happily. > > It doesn't seem to work however. > [snip..] > kq = syscall(SYS_kqueue); > if (kq < 0) > err(1, "kqueue"); > > event[0].ident = fd; > event[0].filter = EVFILT_READ; > event[0].flags = EV_ADD | EV_ENABLE; > evp[0] = &event[0]; > n = syscall(SYS_kevent, kq, 1, evp, 0, NULL, 0); uh, what the heck? Why not just use the kqueue call directly like the manpage explains? I think you have the arguments to kevent() wrong. -- -Alfred Perlstein - [[EMAIL PROTECTED]] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On Wed, May 02, 2001 at 11:27:46AM -0700, John Baldwin wrote: > > On 02-May-01 Andy Sloane wrote: > > Hello, > > > > I just wrote a new syscons screensaver which I think is much more > > interesting than the other ones, while still being relatively easy on the > > CPU (much less CPU intensive than "fire", anyway). Please review it and > > let me know what you think. > > > > It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) > > floating (with a realtime shadow!) above a bunch of tiled spheres which > > move around and morph. It's only one palette change per frame, until the > > bsd daemon moves. > > > > http://fear.incarnate.net/~andude/balls.tar.gz > > > > I'm not on this list, so please reply directly to me. Thanks. Looks great; please submit this as a PR. Kris PGP signature
NMI during procfs mem reads (#2)
I tried sending this from my work account, but our new exchange server isn't
exactly sending mail correctly... Excuse the duplicate post if you see it.
:)
-- Kevin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We're working on a custom PCI card, that on occasion requires several
retries to complete a read (talking to a very slow device). We had a
small bug that would cause it to retry forever, if the device never
responded. It seems that our PCI chipset generates an NMI if the PCI
retry limit is hit. That's OK with us, except that if the read is
going through procfs_rwmem, we get a kernel trap.
If we run a test that attempts to do a read from a PCI mmap()ed
memory register that will retry forever, without using GDB, we get:
NMI ISA b0, EISA ff
RAM parity error, likely hardware failure.
Followed by a bus error. This is exactly what we'd expect to happen,
and I'm happy with that. If we run the exact same code through gdb
(which seems to use procfs somehow) we get:
Fatal trap 19: non-maskable interrupt trap while in kernel mode
instruction pointer = 0x8:0xc0306860
stack pointer = 0x10:0xede2ce28
frame pointer = 0x10:0xede2ce54
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, IOPL = 0
current process = 211 (gdb)
interrupt mask = none
Program received signal SIGEMT, Emulation trap.
0xc0306860 in generic_bcopy ()
(kgdb) bt
#0 0xc0306860 in generic_bcopy ()
#1 0xede2cf0c in ?? ()
#2 0xc01dbe55 in procfs_rwmem (curp=0xeca5b560, p=0xeca5b3c0,
uio=0xede2cf0c) at ../../miscfs/procfs/procfs_mem.c:208
#3 0xc01dbf48 in procfs_domem (curp=0xeca5b560, p=0xeca5b3c0,
pfs=0x0, uio=0xede2cf0c) at ../../miscfs/procfs/procfs_mem.c:264
#4 0xc01b83b9 in ptrace (curp=0xeca5b560, uap=0xede2cf80) at
../../kern/sys_process.c:399
#5 0xc0307f29 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds =
47, tf_edi = 675283088, tf_esi = 0, tf_ebp = -1077938072,
tf_isp = -303902764, tf_ebx = 675283088, tf_edx = 673855764,
tf_ecx = 1, tf_eax = 26, tf_trapno = 7, tf_err = 2,
tf_eip = 673315836, tf_cs = 31, tf_eflags = 518, tf_esp =
- -1077938148, tf_ss = 47}) at machine/smp.h:190
#6 0xc02fc3b5 in Xint0x80_syscall ()
Is it supposed to work this way?
pcib0: on
motherboard
pci0: on pcib0
pcib1: at device 8.0 on pci0
pci1: on pcib1
ikapci0: mem
0xb400-0xb7ff,0xc000-0xdfff irq 11 at device 9.0 on
pci1
-BEGIN PGP SIGNATURE-
Version: PGP Personal Privacy 6.5.3
iQA/AwUBOvBFHc0YFqTZRQvqEQKjaQCeM/oZScd+FkHMV63ia0rgC5LAcfQAoKIx
+1YDufmdbiTBK+J8/IIl46sj
=LbQh
-END PGP SIGNATURE-
--
Kevin Day
[EMAIL PROTECTED] - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On Wed, May 02, 2001 at 01:58:06PM -0700, Nick Sayer wrote: > You might consider trying the apm_saver module instead, especially on > laptops. I have found instances in the past of monitor/BIOS/video > combinations where green didn't do the right thing but that the APM got > right. Both apm_saver and green_saver are essentially (once you get past all the screensaver setup code) one-line routines to turn off the display. I think it would make sense to both tell the VGA chip to blank (green_saver) and tell APM to shut down (apm_saver) with proper #ifdeffing around the APM stuff. I also think it would make sense to do this inside dev/fb/splash.c (or perhaps dev/syscons/syscons.c) instead of inside each screensaver, so that it's automatically handled. And maybe a new 'vidcontrol' option to set the blanking delay (as opposed to the screensaver delay) would be necessary. There may be an even better place to put this, but I am mostly unfamiliar with the kernel source tree and as such I won't attempt to write a patch for this yet. -Andy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KEvent doesnt return and KEvent sample troubles
>* Dominic Marks <[EMAIL PROTECTED]> [010502 14:29] wrote:
> > I've been looking to start using the KEvent system and I've been
> > experimenting with it. However I've been having several problems, with
>my
> > own code as well as samples from http://www.flugsvamp.org.
>
>www.flugsvamp.org doesn't seem to resolve.
Yes, a mistake on my part. It should have been flugsvamp.com.
>
> >
> > It appears I am able to create the correct structure's and register the
> > events. However the event never returns and never responds to any
>action.
> > For example if I use a sample which monitors the actions on a file I can
> > read from, and write to the file and it shows no sign of noticing.
> >
> > I was wondering if it's simply a mistake of my own, however the failure
>for
> > the samples I've found has puzzled my further. I'm working on a
>4.3-STABLE
> > machine using GCC version 2.95.3.
> >
> > Here is an example of code that I am using which doesn't seem to catch
>any
> > events. Its a slightly modified version of read_test.c from
>flugsvamp.com
> > which I edit so it would compile happily.
> >
> > It doesn't seem to work however.
> >
>
>[snip..]
>
> > kq = syscall(SYS_kqueue);
> > if (kq < 0)
> > err(1, "kqueue");
> >
> > event[0].ident = fd;
> > event[0].filter = EVFILT_READ;
> > event[0].flags = EV_ADD | EV_ENABLE;
> > evp[0] = &event[0];
> > n = syscall(SYS_kevent, kq, 1, evp, 0, NULL, 0);
>
>uh, what the heck? Why not just use the kqueue call directly like
>the manpage explains? I think you have the arguments to kevent()
>wrong.
>
I just copied the example directly here so I couldn't comment absolute on
the decisions here. Having browsed through the man page I've edited the
original sample, moving some of the arguments around - where these ever
moved one way and since changed perhaps? However what I believe to be
correct now equally refuses to respond.
Updated:
>
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
main(int argc, char **argv)
{
int fd, kq, n;
struct kevent event[1];
struct kevent *evp[1];
char buffer[128];
struct stat st;
struct aiocb iocb;
struct timespec ts = {0, 0};
if (argc != 2)
errx(1, "Usage: %s file\n", argv[0]);
fd = open(argv[1], O_RDONLY);
if (fd < 0)
err(1, "open: %s\n", argv[1]);
lseek(fd, 0, SEEK_END);
kq = kqueue();
if (kq < 0)
err(1, "kqueue");
event[0].ident = fd;
event[0].filter = EVFILT_READ;
event[0].flags = EV_ADD | EV_ENABLE;
evp[0] = &event[0];
n = kevent(kq, *evp, 1, NULL, 0, &ts);
for (;;) {
n = kevent(kq, 0, NULL, event, 1, NULL);
if (n < 0)
err(1, "kevent");
printf("kevent flags: 0x%x, data: 0x%x\n",
event[0].flags, event[0].data);
n = read(fd, buffer, 128);
buffer[n] = '\0';
printf("%s", buffer);
}
}
<
>--
>-Alfred Perlstein - [[EMAIL PROTECTED]]
>Instead of asking why a piece of software is using "1970s technology,"
>start asking why software is ignoring 30 years of accumulated wisdom.
Thanks again
Dominic Marks
_
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
On 02-May-01 Andy Sloane wrote: > On Wed, May 02, 2001 at 01:58:06PM -0700, Nick Sayer wrote: >> You might consider trying the apm_saver module instead, especially on >> laptops. I have found instances in the past of monitor/BIOS/video >> combinations where green didn't do the right thing but that the APM got >> right. > > Both apm_saver and green_saver are essentially (once you get past all the > screensaver setup code) one-line routines to turn off the display. I think > it would make sense to both tell the VGA chip to blank (green_saver) and > tell APM to shut down (apm_saver) with proper #ifdeffing around the APM > stuff. > > I also think it would make sense to do this inside dev/fb/splash.c (or > perhaps dev/syscons/syscons.c) instead of inside each screensaver, so that > it's automatically handled. And maybe a new 'vidcontrol' option to set the > blanking delay (as opposed to the screensaver delay) would be necessary. > There may be an even better place to put this, but I am mostly unfamiliar > with the kernel source tree and as such I won't attempt to write a patch > for this yet. You could just add new ioctl's to do this the same way that vidcontrol does settings now. This approach does sound the most sensible to me, FWIW, as it avoids duplicating code all over the place. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KEvent doesnt return and KEvent sample troubles
In local.freebsd.hackers you write: >>* Dominic Marks <[EMAIL PROTECTED]> [010502 14:29] wrote: >> > I've been looking to start using the KEvent system and I've been >> > experimenting with it. However I've been having several problems, with >>my >> > own code as well as samples from http://www.flugsvamp.org. >> >>www.flugsvamp.org doesn't seem to resolve. >Yes, a mistake on my part. It should have been flugsvamp.com. [...] >I just copied the example directly here so I couldn't comment absolute on >the decisions here. Having browsed through the man page I've edited the >original sample, moving some of the arguments around - where these ever >moved one way and since changed perhaps? However what I believe to be >correct now equally refuses to respond. Works here (4.3-RC, Apr 19), provided that you append to the file. If you just overwrite it with the same amount of data, read() will return zero, and you get no output. Check out the source for tail(1) for a more complete example (in /usr/src/usr.bin/tail/forward.c) $.02, /Mikko -- Mikko Työläjä[EMAIL PROTECTED] RSA Security To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel Console speed
Daniel Lang wrote: > > > What I did: > > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf > > > set options CONSPEED=38400 in KERNEL > > > compiled and installed kernel and new bootstrap (with disklabel). > > > changed /etc/ttys to use std.38400 as argument to getty. "Me, too." Same thing, just with 115200 instead of 38400, and on 4.2-RELEASE. -- Lars Eggert <[EMAIL PROTECTED]> Information Sciences Institute http://www.isi.edu/larse/ University of Southern California S/MIME Cryptographic Signature
Re: ipfw routing/netmask problem
Nick Rogness wrote: > > On Mon, 30 Apr 2001, John Wilson wrote: > > This probably belongs on freebsd-net or freebsd-questions. -questions, please. -net is for discussing FreeBSD networking code, not for configuration problems. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NAT and IPFiltering
Matt Dillon wrote: > > :Hi! > : > :I'm configuring a server able to do NAT and IP FILTERING (IPF). > : > :What are the required options that I should set to the kernel? > : > :I have this: > :... > :Jesús Arnáiz > > I think all you need is: > > options IPFIREWALL > options IPDIVERT Those are for ipfw/natd. For ipfilter, you need: > I usually also have (because it is useful): > > options IPFILTER If you want to use ipmon to log ipf actions, you'll need: options IPFILTER_LOG The default state in ipf is open, you can change it to block with: options IPFILTER_DEFAULT_BLOCK That's it. ipnat uses ipfilter in the kernel and requires only the IPFILTER option. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: x86-64 Hammer and IA64 Itainium
"Michael C . Wu" wrote: > > > You've just ruined any real reason for me to continue my education > as a computer architecture student :P > "Let all the computer scientists design the CPU and hope that > they take into account the electromagnetic effects!!" Er, turn this around to: design the system so the software will actually run quickly on it. This was the design goal of RISC, and it moved a giant leap towards that goal, as long as memory was as fast as the processor. Now that processors outpace their memory subsystems by many times, it's probably time to start going the other direction again. This time hopefully we'll do it intelligently. There's your reason for sticking around. > | Now imagine you get a fully programmable add-on card. If something get > | wrong, the device driver writer can fix it and not just put hacks to > | handle this or this revision of a chip. Even further, computation part > | of the DD can be pushed onto the card. Imagine a NIC pushing you mbufs, > | pcb entries, etc... You will also not have to wait for the good willing > | of XYZ company to release documentation or seeing a version of a chip > | being phased out in favor of the new super-one released only with an > | opaque Windows driver. > > Can you picture the difficulty of writing drivers for these > devices that do so many specific things? I am sure Bill Paul, > Mike Smith, et al. will be so thrilled to read thousands of pages > of documentation to write one driver. > Engineering is about K.I.S.S., not making it very complicated for > everyone involved. Snort. You should look inside a layer 3 (or higher) switch. Queueing engines with 16K - 64K queues, multiple queues per port, with programmable priorities per-queue/per-port, programmable thresholds per queue, auto- magic buffer management, etc., etc., all in the hardware. If you think that's exotic, wait'll the next generation of hardware firewalls enters the field. That'll be a heyday. Engineering: building something that customers want to buy, that can be produced profitably. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KEvent doesnt return and KEvent sample troubles
On Wed, 2 May 2001, Dominic Marks wrote: > I've been looking to start using the KEvent system and I've been > experimenting with it. However I've been having several problems, with my > own code as well as samples from http://www.flugsvamp.org. > > It appears I am able to create the correct structure's and register the > events. However the event never returns and never responds to any action. > For example if I use a sample which monitors the actions on a file I can > read from, and write to the file and it shows no sign of noticing. For that you want status change notifications. You've registerted just a simple read() notification a la select(), which will trigger until you've read the entire file then stop. You might find this more interesting if you point it at a named pipe then use something to stuff data down it. Take a look at the EVFILT_VNODE type in the kqueue(2) manpage. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: new syscons screensaver
This looks pretty good, and it seems to be getting good comments. It seems that you either need to file a PR or have a committer volunteer to get it in the tree. Any takers? I may have some spare time later this weekend. -john - Andy Sloane's Original Message - > Hello, > > I just wrote a new syscons screensaver which I think is much more > interesting than the other ones, while still being relatively easy on the > CPU (much less CPU intensive than "fire", anyway). Please review it and > let me know what you think. > > It's the bsd daemon logo (with much editing, thanks to my coworker Waylon) > floating (with a realtime shadow!) above a bunch of tiled spheres which > move around and morph. It's only one palette change per frame, until the > bsd daemon moves. > > http://fear.incarnate.net/~andude/balls.tar.gz > > I'm not on this list, so please reply directly to me. Thanks. > > -Andy > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: KEvent doesnt return and KEvent sample troubles
In article [EMAIL PROTECTED]> you write: >I've been looking to start using the KEvent system and I've been >experimenting with it. However I've been having several problems, with my >own code as well as samples from http://www.flugsvamp.org. AAARGH. /me hastily goes and removes that example directory. Sorry about that; those examples were correct during the initial kqueue development, and haven't been updated to reflect reality. I'll put the examples back up after I've corrected them to work with the current version of FreeBSD. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel Console speed
> Daniel Lang wrote: > > > > What I did: > > > > set BOOT_COMCONSOLE_SPEED=38400 in /etc/make.conf > > > > set options CONSPEED=38400 in KERNEL > > > > compiled and installed kernel and new bootstrap (with disklabel). > > > > changed /etc/ttys to use std.38400 as argument to getty. > > "Me, too." > > Same thing, just with 115200 instead of 38400, and on 4.2-RELEASE. You don't want to set CONSPEED in the kernel config, or change the loader configuration. Just build/install boot1/boot2 with a new BOOT_COMCONSOLE_SPEED, and ensure that /etc/ttys is correctly set for your desired console rate. This works. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Command like "sar" on solaris ????
Dear all: I want to know buffer cache hit ratio on Freebsd , I know the command "sar" on solaris has the fuction, But It doesn't appear on FreeBSD. Is there the same function command on FreeBSD . Please tell me , Thanks Richard_Lin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
