Re: /tmp on a ramdisk?
On 30-Jul-00 Brian Fundakowski Feldman wrote: The issue is that mount_mfs is simply newfs with a catch: it constructs the new filesystem completely in memory and lives on as the storage for the mounted filesystem. If you view the processes on a system using MFS, you will notice that one of them is the original mount_mfs, having become a daemon. Yes, things are stored twice in memory: once in the buffer cache and once in the MFS process. Yes, they are also copied multiple times. MFS simply can't perform as well as you might expect. The malloc disk device can because it simply creates a kernel-memory backing store. The disadvantage here is that it's wired memory and can't get swapped out like mount_mfs can. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' Please forgive my late reply.. Just trying to catch up.. Given all of the above statements, why does BSD/OS (at least on 4.0 and 4.1) want to set up tmp as a Ramdisk? I don't even think there is a way around it during the install. Nicole To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message [EMAIL PROTECTED] |\ __ /| (`\ http://www.unixgirl.com/ [EMAIL PROTECTED] | o_o |__ ) ) http://www.dangermouse.org/ // \\ ---(((---(((- -- Powered by Coka-Cola and FreeBSD -- -- Strong enough for a man - But made for a Woman -- -- OWNED? MS: Who's Been In/Virused Your Computer Today? -- --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
module if_disc.ko - network module
I am using FreeBSD 3.4R. I am currently investigating on how easy it is to transform a kernel network device driver into a dynamically loadable module. I found and loaded the if_disc.ko module into memory, it seems to work fine because I have a new entry with ifconfig -a. I have no idea what this pseudo network interface is for, and I could not find any man on it. Any idea, pointers ? Where could I find the source ? I wrote a network device driver for a very specialized satellite reception card. This driver is compiled, as most of the network drivers, in the kernel. I am just wondering if it is possible to make this driver a loadable module. Assuming that the board is in on PCI bus, supports DMA bus mastering, may transfer data up to 40Mbps. Any idea, pointers ? What should I pay attention to, what are the limits... ? Thanks in advance, Emmanuel Duros -- UDcast: Where IP and UniDirectional links meet http://www.UDcast.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: module if_disc.ko - network module
On 11-Aug-00 Emmanuel Duros wrote: I am using FreeBSD 3.4R. Ahh well.. I am currently investigating on how easy it is to transform a kernel network device driver into a dynamically loadable module. Upgrade, and ye shall see.. At least it's in -current, and I'm fairly sure it's in 4.0 too. Last I checked though, unloading the network interface tended to be a risky prospect so maybe it hasn't been MFC'd yet.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
makeLINT.pl - Bug or am I just stupid
Hi there!
I just searched the LINT config file, and I just saw a makeLINT.pl. So I
thought this would build me my configuration file.
But it just builds me error messages:
[frederik@server conf]$ sh makeLINT.pl
=0: not found
makeLINT.pl: 5: Syntax error: redirection unexpected
[frederik@server conf]$
Line 5 sais:
while () {
I'm not familiar with Perl, so I can't fix the problem myself.
Or am I just stupid.
I'm running a just build userland from last Thursday.
TIA
--
Best Regards,
Freddy
=
Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org
Bavaria/Germany OpenVMS and Unix Howtos and much more
FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
RE: makeLINT.pl - Bug or am I just stupid
[frederik@server conf]$ sh makeLINT.pl =0: not found makeLINT.pl: 5: Syntax error: redirection unexpected [frederik@server conf]$ try: perl makeLINT.pl NOTES thanks, emax To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: makeLINT.pl - Bug or am I just stupid
Hi! try: perl makeLINT.pl NOTES Thanks! It works! -- Best Regards, Freddy = Frederik Meerwaldt ICQ: 83045387 Homepage: http://www.freddym.org Bavaria/Germany OpenVMS and Unix Howtos and much more FREEBSD, NETBSD, OPENBSD, TRU64, OPENVMS, ULTRIX, BEOS, LINUX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Installation Problems on Dell PowerEdge 6100/200
We have a machine here in the lab that is the precurser of your machine that we also had boot problems with. What I found was that the adaptec BIOS Disks 1GB support was breaking the linux and FreeBSD boot routine. When I disabled Disks 1GB my problems were solved. It seems the BIOS setting is for machines running OSes that need help looking at large disks. I hope this helps. If you already have your machine working great; I hope this my help someone else then. james On Tue, 8 Aug 2000, Daniel Lang wrote: Hi, we've got a Dell PowerEdge 6100/200 here, which is an older SMP server, featuring 4 PPro 200 CPU's two internal AIC7880 channels and an Adaptec 2940UW PCI controller. One of the AIC's is connected to a SCA Backplane that holds 4 disks. Now before even having a chance to see if FreeBSD-SMP works with this box, I didn't manage to install FreeBSD (4.1) correctly. Well, installation seems to go well in any attempt: - Floppy boots, Kernel finds all ahc's and disks - Installation seems to succeed (Partitioning, installation, etc) But then, the machine won't boot. It seems to happen, that the MBR of the target device (da0, which is the first disk on the second controller, channel A of internal AIC's) is found, but the next stage of the bootstrapping process cannot be found. I played also around using boot0 and installing on other disks, this is like what I got: Standard MBR and System on da0: - Missing operating system boot0 MBR and System on da0:- F1 - *beep* (nothing else) boot0 MBR (and old System) on da0, standard MBR and System on da1: booting from da0: F1 - *beep*, F5 (disk2) - Missing operating system booting from da1: - Missing operating system So it seems no boot-block after the MBR can be found. I tried: - installing and booting from different disks on internal ahc - disabling some of the controllers - installing and booting from a disk on the 2940, as well while disabling the others It all had no effect. All adaptec's BIOS has Disks 1GB and INT13 enabled (of course the BIOS itself is enabled, too) Previously Solaris 7/x86 was running on this machine, there were no such problems, but we don't really want to run Solaris... :-} Any clue ? Many thanks, Daniel -- IRCnet: Mr-Spock - My name is Pentium of Borg, division is futile, you will be approximated. - *Daniel Lang * [EMAIL PROTECTED] * +49 89 289 25735 * http://www.leo.org/~dl/* -- IRCnet: Mr-Spock - May His Shadow fall upon thee - *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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ESS Solo users, try this patch
The last patch improved, but did not completely eliminate the warnings.
This one appears to do the job perfectly. The question is, does calling
DELAY() like this cause any concerns for anyone?
Index: solo.c
===
RCS file: /home/ncvs/src/sys/dev/sound/pci/solo.c,v
retrieving revision 1.8
diff -u -r1.8 solo.c
--- solo.c 2000/08/09 07:14:56 1.8
+++ solo.c 2000/08/11 17:01:22
@@ -756,7 +756,7 @@
static int
ess_dmapos(struct ess_info *sc, int ch)
{
- int p = 0;
+ int p = 0, i = 0, j = 0;
u_long flags;
KASSERT(ch == 1 || ch == 2, ("bad ch"));
@@ -766,11 +766,20 @@
/*
* During recording, this register is known to give back
* garbage if it's not quiescent while being read. That's
- * why we spl, stop the DMA, wait, and be vewy, vewy quiet
+ * why we spl, stop the DMA, and try over and over until
+ * adjacent reads are "close", in the right order and not
+ * bigger than is otherwise possible.
*/
ess_dmatrigger(sc, ch, 0);
- DELAY(20);
- p = port_rd(sc-vc, 0x4, 2) + 1;
+ DELAY(20);
+ do {
+ DELAY(10);
+ if (j 1)
+ printf("DMA count reg bogus: %04x %04x\n",
+ i, p);
+ i = port_rd(sc-vc, 0x4, 2) + 1;
+ p = port_rd(sc-vc, 0x4, 2) + 1;
+ } while ((p sc-dmasz[ch -1 ] || i p || (p - i) 0x8) j++
+1000);
ess_dmatrigger(sc, ch, 1);
}
else if (ch == 2)
Re: R. Stevens select() Collisions Scenario
Alfred Perlstein wrote: Yes. :) When FreeBSD gets scheduler activations you'll be able to change to a single threaded process that will have excellent performance, the scheduler activations are just around the corner. Can you explain what scheduler activations are? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
IPC, shared memory, syncronization
What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid race conditions, etc)? Right now I'm using posix semaphores but I would like to know if there is a substitute like the way kqueue is for select/poll. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: R. Stevens select() Collisions Scenario
* Jonas Bulow [EMAIL PROTECTED] [000811 10:45] wrote: Alfred Perlstein wrote: Yes. :) When FreeBSD gets scheduler activations you'll be able to change to a single threaded process that will have excellent performance, the scheduler activations are just around the corner. Can you explain what scheduler activations are? Please CC. schedulder activations are like 'LWP on-demand' a really simplified explanation would be shared address space fork that only happens when you block in certain parts of the kernel, like during disk/io. the problem with normal LWP is that if you're going to do any sort of disk IO you really want an LWP _per_ disk bound thread otherwise you risk blocking on disk IO inside the kernel, scheduler activations make sure you almost never block as well as making it unnecessary to 'pre-allocate' LWP contexts to avoid such problems. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Maestro2E patch (Was: US$100 prize for adding ESSAudiodrivesupport to pcm)
Munehiro Matsuda wrote: Hello Joseph, From: Joseph Scott [EMAIL PROTECTED] Date: Thu, 10 Aug 2000 17:36:52 -0700 :: I have created a patch that trys to enable internal speakers. :: :: The first part of the patch (for maestro.c) didn't apply cleanly for ::me, so I ended up doing it by hand. Thats funny. Did you aply my patch to the original 2725 version? Yes. I even went and redownloaded it to make sure. The first patch you included below didn't apply cleanly either. I applied it by hand again. :: It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works :: for everybody. Patch is based on Linux driver, but simplified. :: :: If it does not work, 1) try setting GPIO values to what your PC is at :: when rebooting from Windows, 2) try original way the Linux driver do. :: Let me know, if you want to know what Linux driver does. :: :: Unfortunately this didn't work for mine (Dell Inspiron 7500). How to ::I find out the GPIO values that make windows work? I'm open to trying ::what the Linux driver does. Mind you my C programing skills are ::pretty much useless, but I'm willing to try things out :-) Aha, Dell Inspiron 7500! There was some extra stuff in the Linux driver for it. I have recreated my patch (mstr2_spk.patch2) to include them. Please aply the new patch to the original 2725 version source code! This seems to have to done the trick! I now get sound out of both internal speakers! Yeah And also, I added a small patch (mstr2_gpio.patch) that should print GPIO values. Aply GPIO patch after the mstr2_spk.patch2! I didn't try this patch since the first one got the speakers working. Would it be helpful to find out GPIO values at this point? If so let me know and I'll apply the patch and see what I get. Otherwise I'll just go with what I've got. Let me know how that works out. BTW, I'll be out of town for few days. So my reply may get delayed. sorry. Thank you, Haro No problem. Thank you again, now I won't have to carry about headphones or external speakers with my notebook :-) -- Joseph Scott [EMAIL PROTECTED] Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Need help with driver....
Hi all,
I'm a newbie to device driver writing and I have been learning well by
reading the code of the other drivers in the system. I would ultimately
like to port a linux driver for a VoIP telephony card (Quicknet
PhoneJack) to FreeBSD, and so far I have a skeleton driver which does
successfully probe the card.
The problem I'm having is that I don't know how to tell whether or not
the card is attaching correctly. How can I determine this? I thought
that I would be able to make a device file in /dev if it correctly
attached but MAKEDEV responds with:
{root@dbm /dev]# ./MAKEDEV phone
phone - no such device name
For reference, here is my attach routine:
static int
ixj_isa_attach (dev)/* attach device*/
device_t dev;
{
int unit = device_get_unit(dev);
struct ixj_softc *sc = device_get_softc(dev);
struct resource *res;
int rid;
int size;
if (sc-port_used 0) {
size = sc-port_used;
rid = sc-port_rid;
res = bus_alloc_resource(dev, SYS_RES_IOPORT, rid,
0, ~0, size, RF_ACTIVE);
if (res) {
sc-port_rid = rid;
sc-port_res = res;
sc-port_used = size;
}
}
make_dev(ixj_cdevsw, UNIT(dev), UID_ROOT, GID_WHEEL,
0666, "phone%d", unit);
return (0);
}
What am I doing wrong? How can I tell if this is working? Why can't I
make the device file?
Thanks in advance.
--
Regards, Devin.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: makeLINT.pl - Bug or am I just stupid
"Yevmenkin, Maksim N, CSCIO" wrote: [frederik@server conf]$ sh makeLINT.pl =0: not found makeLINT.pl: 5: Syntax error: redirection unexpected [frederik@server conf]$ try: perl makeLINT.pl NOTES thanks, emax or: make LINT which is easier still. :-) Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Need help with driver....
I'm a newbie to device driver writing and I have been learning well by
reading the code of the other drivers in the system. I would ultimately
like to port a linux driver for a VoIP telephony card (Quicknet
PhoneJack) to FreeBSD, and so far I have a skeleton driver which does
successfully probe the card.
It does? How? Is this a PnP card?
The problem I'm having is that I don't know how to tell whether or not
the card is attaching correctly. How can I determine this? I thought
that I would be able to make a device file in /dev if it correctly
attached but MAKEDEV responds with:
{root@dbm /dev]# ./MAKEDEV phone
phone - no such device name
MAKEDEV is a script which does not interact with the kernel in any way.
You need to explicitly update MAKEDEV to know about your device.
For reference, here is my attach routine:
static int
ixj_isa_attach (dev)/* attach device */
device_t dev;
{
int unit = device_get_unit(dev);
struct ixj_softc *sc = device_get_softc(dev);
struct resource *res;
int rid;
int size;
if (sc-port_used 0) {
size = sc-port_used;
rid = sc-port_rid;
Where are you initialising these fields in the softc? (I assume, in your
probe, correct?)
res = bus_alloc_resource(dev, SYS_RES_IOPORT, rid,
0, ~0, size, RF_ACTIVE);
if (res) {
sc-port_rid = rid;
sc-port_res = res;
sc-port_used = size;
}
}
make_dev(ixj_cdevsw, UNIT(dev), UID_ROOT, GID_WHEEL,
0666, "phone%d", unit);
return (0);
}
What am I doing wrong? How can I tell if this is working?
You should check the return values from bus_alloc_resource and make_dev,
both of which you need to save in the softc so that you can detach
correctly.
--
... 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]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: IPC, shared memory, syncronization
Jonas Bulow wrote: What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid race conditions, etc)? Right now I'm using posix semaphores but I would like to know if there is a substitute like the way kqueue is for select/poll. Hmm, I think I lost some word and deeper thought in my previous mail. :-) The problem is as follows: I have a couple of processes using a mmap:ed file as common data area. What I want to do is to make it safe for all processes to update data in this common memory area. I was thinking about using some part of the common data area for semaphores in some way. I just want a simple "test-and-set" operation I can use to make sure there is only one process writing to the common data area. To take the "test-and-set" further, I would like to make the process wait for the lock to be released. Can anyone give me hint how this is best implemented with FreeBSD as OS? I apology if this is not a pure FreeBSD related question but I could not find a better forum for this question. I could only find out solutions based on posix semaphores. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
localhost cannot be resolved
Hello everyone! I sent this question to freebsd-questions, but no one had replied, so I decided to try my luck here. I'm having trouble resolving "localhost" for telnet and fetchmail. All other programs (ftp, rlogin, rsh, ping, lynx) seem to understand "localhost". I'm going to include my configuration files. Please tell me if you'd like to get more info on something. cat /etc/hosts 127.0.0.1 localhost localhost.my.domain myname.my.domain ::1 localhost localhost.my.domain myname.my.domain cat /etc/host.conf hosts bind cat /etc/resolv.conf nameserver 209.226.175.224 nameserver 204.101.251.2 All looks right, does it? Now, when I run telnet or fetchmail, they complain. telnet localhost localhost: No address associated with hostname echo $? 1 fetchmail 9 messages for MYUSERNAME at pop.mail.yahoo.com (64648 octets). reading message 1 of 9 (13403 octets) .fetchmail: SMTP connect to localhost failed fetchmail: SMTP transaction error while fetching from pop.mail.yahoo.com fetchmail: Query status=SMTP echo $? 10 At the same time fetchmail causes ipfw to produce these messages: Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from ::0001:1063 Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1065 Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP ::0001:25 from ::0001:1066 Aug 11 21:41:47 mydomain /kernel: Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1067 Actually, could someone tell me, what does ::0001 mean? Should this be in /etc/hosts with an alias of localhost? These strange things started to happen soon after I cvsup'ed ports-all and reinstalled libtool. I also compiled firewall support into the kernel a few days ago. Just in case any of this might be related to the problem. Thank you all for any suggestions! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: IPC, shared memory, syncronization
In article [EMAIL PROTECTED], Jonas Bulow [EMAIL PROTECTED] wrote: Jonas Bulow wrote: What is the "BSD-way" of access to shared memory (mmap:ed) secure (avoid race conditions, etc)? Right now I'm using posix semaphores but I would like to know if there is a substitute like the way kqueue is for select/poll. Hmm, I think I lost some word and deeper thought in my previous mail. :-) The problem is as follows: I have a couple of processes using a mmap:ed file as common data area. What I want to do is to make it safe for all processes to update data in this common memory area. I was thinking about using some part of the common data area for semaphores in some way. I just want a simple "test-and-set" operation I can use to make sure there is only one process writing to the common data area. If you want the "BSD way" you should probably create a 0-length temporary file somewhere and use the flock(2) system call on it. The file itself isn't important; it's just something to lock. Or you could use semop(2) on semaphores. But that's the SYSV way, not the BSD way. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ACPI project progress report (final?)
It is related with quite wide areas, not only for power management. # I'm interested in power management part personally for the first step # though. Do I understand correctly that things like monitoring cooling fans etc is also possible? I guess the people running (lots of) servers will be interested in those features too. Yes, of course :-) ACPI covers the thermal management also. I could imagine that there are quite big needs in this area for server computing. I think this is what you are interested in, from ACPI 1.0b spec. contents; 12. THERMAL MANAGEMENT 12.1 Thermal Control 12.1.1 Active, Passive, and Critical Policies 12.1.2 Dynamically Changing Cooling Temperatures 12.1.3 Hardware Thermal Events 12.1.4 Active Cooling Strength 12.1.5 Passive Cooling Equation 12.1.6 Critical Shutdown You can get ACPI spec. documents from http://www.teleport.com/~acpi/spec.htm # I haven't checked ACPI spec 2.0 yet though :-) Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ACPI project progress report (final?)
In message [EMAIL PROTECTED] Mitsuru IWASAKI writes: : # I haven't checked ACPI spec 2.0 yet though :-) Wouldn't you know it. I printed the 1.0, and then the errata for it. Now I have to kill another couple of trees to print the 2.0 spec. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: ACPI project progress report (final?)
On Sat, Aug 12, 2000 at 12:35:27AM +0900, Mitsuru IWASAKI wrote: I'm not quite sure what it does, but it seems to work fine here on my ASUS CUSL2, at least the shutdown part. Thank you for your report. It would be helpful to check http://www.teleport.com/~acpi/whatis1.htm and it's links. Interesting information, thanks for the pointer. It is related with quite wide areas, not only for power management. # I'm interested in power management part personally for the first step # though. Do I understand correctly that things like monitoring cooling fans etc is also possible? I guess the people running (lots of) servers will be interested in those features too. -- Wilko Bulte [EMAIL PROTECTED] Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
