On Sun, Feb 14, 1999 at 07:14:26AM +0100, Leif Neland wrote:
On Sat, 13 Feb 1999, Jordan K. Hubbard wrote:
until I realized that /etc/rc.conf was empty. It's the anti-POLA! ;)
That's POMA :)
Could somebody tell me the meaning of those acronyms?
POLA - Policy? Of Least Astonishment
On Sat, Feb 13, 1999 at 10:03:41PM -0500, Chuck Robey wrote:
I have to add an addendum here, to my previous question about the new
config file setup for a simple printer. I was looking forward to seeing
the probing come back to my dmesg, when I finally got it right, but
seeing this:
Feb 13
On Sat, Feb 13, 1999 at 08:04:12PM +0100, Dag-Erling Smorgrav wrote:
Nicolas Souchu nso...@teaser.fr writes:
controller ppbus0 # The ppbus system
device nlpt0 at ppbus? # The printer driver
OBTW, when are you planning to rename nlpt0 to lpt0?
Today.
On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
On Sat, 13 Feb 1999, Nicolas Souchu wrote:
Hi folks,
I've just committed the alpm(4) driver to -current: the Aladdin SMBus
driver.
Great, my newest mobo is an AcerLabs.
With an onboard system management chip (lm7x or
Recently I've been trying to upgrade an early januarrry -current to
current -current. I've rebuilt the kernel several times over the last few
days (with new cvsup's) so i've eliminated any freak check-in mismatches.
During a make world (usually about 10-20 minutes in on my P100) everything
just
On Sat, 13 Feb 1999, Thomas Dean wrote:
I changed to the new nlpt. No luck.
It appears that the parallel port is not found.
I am running SMP-current, as of this afternoon. From uname -a:
... FreeBSD 4.0-CURRENT #0: Sat Feb 13 16:11:56 PST 1999
In my config, I changed to include
I'm getting something similar. I thought it was my mainboard, as the one
I currently have has some other problems (doesn't take the Nvidia TNT
card)
During heavy disk i/o the system freezes up for about 10 seconds or so,
and then things continue. I'm getting these messages:
wd0: interrupt
I had the same problem with a non Aladin system.
I believe the problem is that Takanori's examples no longer work
since changes were made to pcisupport.c.
Why do I say this ? Because Takanori said so in email to me.
I dont understand how it all works but if I show you Takanori's
comments maybe
Date: Sat, 13 Feb 1999 19:17:14 +0100
From: Nicolas Souchu nso...@teaser.fr
You need:
controllerppbus0 # The ppbus system
devicenlpt0 at ppbus? # The printer driver
And finally the parallel port chipset interface,
controllerppc0at
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
On Sat, 13 Feb 1999, Nicolas Souchu wrote:
Example program to fetch temperature or voltages is available at
http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/
There's
Shouldn't a make world take about 10 hours on a P100 ?? -depends on
the speed of your disks.
You should probably remove all the junk in /usr/obj from previous
make worlds, then run make cleandir in /usr/src and then try
a make world again.
The messages about no such user 'tty' indicate your /etc
On Sun, 14 Feb 1999, Erik Funkenbusch wrote:
Recently I've been trying to upgrade an early januarrry -current to
current -current. I've rebuilt the kernel several times over the last few
days (with new cvsup's) so i've eliminated any freak check-in mismatches.
During a make world (usually
$Id: LINT,v 1.555 1999/02/14 12:00:00 nsouch Exp $
controller ppc0at isa? port? tty irq 7
$Id: GENERIC,v 1.149 1999/02/14 12:00:00 nsouch Exp $
device ppc0at isa? port? tty irq 7
Are the lables device and controller interchangeable?
On Sun, Feb 14, 1999 at 05:31:08AM -0800, Jonathan M. Bresler wrote:
Date: Sat, 13 Feb 1999 19:17:14 +0100
From: Nicolas Souchu nso...@teaser.fr
You need:
controller ppbus0 # The ppbus system
device nlpt0 at ppbus? # The printer driver
And
On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
On Sat, 13 Feb 1999, Nicolas Souchu wrote:
Example program to fetch temperature or voltages is available at
On Sat, Feb 13, 1999 at 10:03:41PM -0500, Chuck Robey wrote:
I have to add an addendum here, to my previous question about the new
config file setup for a simple printer. I was looking forward to seeing
the probing come back to my dmesg, when I finally got it right, but
seeing this:
Feb 13
=== pccardc
cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static
-c /usr/src/usr.sbin/pccard/pccardc/beep.c
/usr/src/usr.sbin/pccard/pccardc/beep.c: In function `beep_main':
/usr/src/usr.sbin/pccard/pccardc/beep.c:74: `PIOCSBEEP' undeclared (first
use this function)
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
I *never* expected to see the PNP functions actually pick up the name of
my printer. I was economically bushwacked by the Windows corps into
buying the 693C (the version with the Windows software floppies tacked
on) so I was actually pleased that it
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
On Sat, 13 Feb 1999, Nicolas Souchu wrote:
Example program to
On Sat, 13 Feb 1999, Daniel C. Sobral wrote:
Do you use the Power up at time/date feature of the BIOS?
No.
After this thread, I figured I'd try out shutdown -p, and lo and behold it
didn't work. Well I thought, I have apm enabled, apm(1) shows that. The
probe shows that and so on. A
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
I *never* expected to see the PNP functions actually pick up the name of
my printer. I was economically bushwacked by the Windows corps into
buying the 693C (the version with the Windows software floppies tacked
on) so I was actually pleased that it
No, not a joke :)
nlpt name was only a trick not to collide with lpt while both were in
the system. As you noticed, the old isa lpt driver has been removed.
Consequently, nlpt makes no more sense. This is I hope the last confusion
about printing drivers... before the next one.
So, here is one
On Sun, Feb 14, 1999 at 11:52:04AM -0500, Chuck Robey wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
I *never* expected to see the PNP functions actually pick up the name of
my printer. I was economically bushwacked by the Windows corps into
buying the 693C (the version with the Windows
On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote:
FWIW, I would also like to see this happen.
What's the deadline? I did it for -current this day. I'm waiting for
some feedback before the 3.1 replica.
On 13 Feb 1999, Dag-Erling Smorgrav wrote:
Nicolas Souchu
On Sun, Feb 14, 1999 at 12:11:09PM -0500, Brian Feldman wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sat, Feb 13, 1999 at 05:22:00PM -0500, Brian Feldman wrote:
On Sat,
On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote:
FWIW, I would also like to see this happen.
What's the deadline? I did it for -current this day. I'm waiting for
some feedback before the 3.1 replica.
Actually, subsequent discussions with Dag-Erling have sort of shown
On Sun, Feb 14, 1999 at 12:48:56PM -0500, Chuck Robey wrote:
But there's at least FIFO+DMA support in the nlpt driver. Try 'lptcontrol -e'
with you BIOS configured to ECP. Recompile with the appropriate
drq on the 'device ppc at isa?...' line.
Experimentation mode (on a machine I can crash
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sun, Feb 14, 1999 at 12:11:09PM -0500, Brian Feldman wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sun, Feb 14, 1999 at 08:40:11AM -0500, Brian Feldman wrote:
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sat, Feb 13, 1999 at
On Sun, 14 Feb 1999, Jordan K. Hubbard wrote:
On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote:
FWIW, I would also like to see this happen.
What's the deadline? I did it for -current this day. I'm waiting for
some feedback before the 3.1 replica.
Actually,
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
There are a couple of things that have happened that strike me as worthy
of comment. Here's my relevant dmesg part:
ppc0 at 0x378 irq 7 drq 3 on isa
ppc0: SMC FDC37C665GT chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/15 bytes
It says generic every time, whther or not there's a printer attached.
lpt0: generic printer on ppbus 0
lpt0: Interrupt-driven port
should be
lpt0: generic printer port on ppbus 0
lpt0: Interrupt-driven port
Brian Feldman_ __ ___ ___ ___
gr...@unixhelp.org
In message pine.bsf.4.05.9902141208450.13678-100...@janus.syracuse.net, Brian
Feldman wrote:
I attach you the detect.c program. It's very simple and may help us
in knowing what I2C hardware you have on your mobo.
Where's my detect.c? I think you forgot to attach it :)
:) here it is!
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
On Sun, Feb 14, 1999 at 01:16:11PM -0500, Chuck Robey wrote:
ppc0 at 0x378 irq 7 drq 3 on isa
ppc0: SMC FDC37C665GT chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/15 bytes threshold
ppb0: IEEE1284 device found /NIBBLE/ECP
Probing for PnP devices on ppbus0:
ppbus0:
On Sun, Feb 14, 1999 at 01:01:27PM -0500, Brian Feldman wrote:
[...]
Sorta. It did work. Then it stopped working. Running detect seems to kill my
SM (or at least reset it to some weird state)
{/home/green/examples}$ ./detect
{/home/green/examples}$
You mean you got some output from spd? Which?
On Sun, Feb 14, 1999 at 01:33:24PM -0500, Brian Feldman wrote:
It says generic every time, whther or not there's a printer attached.
Yes, fun isn't it?
lpt0: generic printer on ppbus 0
lpt0: Interrupt-driven port
should be
lpt0: generic printer port on ppbus 0
lpt0: Interrupt-driven port
You
On Sun, Feb 14, 1999 at 09:58:39AM -0800, Jordan K. Hubbard wrote:
On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote:
FWIW, I would also like to see this happen.
What's the deadline? I did it for -current this day. I'm waiting for
some feedback before the 3.1 replica.
Ok, we should keep lpt, but I'll need to sync ppbus before the release
just to fix some bugs discovered by all these new testers.
OK, better do it soon then! :)
BTW, I really don't know when 3.1 will be released.
The tag goes down tonite (in approximately 7 hours) and the release is
tomorrow
On Mon, Feb 15, 1999 at 03:55:07AM +0900,
takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote:
d2 found.
I want to know about this address. SMBus in my motherboard will hang
up when I issue RECV_BYTE method for this port.
It does not for me. It's supposed to be the address of a clock chip,
On Sun, Feb 14, 1999 at 11:43:36AM -0800, Jordan K. Hubbard wrote:
Ok, we should keep lpt, but I'll need to sync ppbus before the release
just to fix some bugs discovered by all these new testers.
OK, better do it soon then! :)
BTW, I really don't know when 3.1 will be released.
The tag
Jordan K. Hubbard j...@zippy.cdrom.com writes:
Actually, subsequent discussions with Dag-Erling have sort of shown
this to have been rather too ambitious of me and now I've major second
thoughts. :(
I *can* do it if you want. It's pretty straightforward, it's just that
there are a lot of
The alternative is to just update GENERIC, LINT et al to use ppbus
instead of the old lpt driver, and throw in a warning in the probe
messages in src/sys/i386/lpt.c telling people to move to ppbus. It
should be pretty safe.
Now that I could live with. Are you up for that?
- Jordan
To
fprintf(stderr,
-usage: pccardc enabler slot driver [-m addr size] [-a iobase] [-i irq]\n);
+Usage: enabler slot driver [-m addr size] [-a iobase] [-i irq]\n);
Usage string use to start with usage, not Usage. Progname should
follow.
- fprintf(stderr, usage: pccardc subcommand arg
This is under -current. I don't know when it started, but I think whatever
change is causing this was in the last week or two.
This isn't a 'bug', per say, but it bothers me that a small 128 byte
write() is being somehow broken apart into two smaller read()s. It isn't
:Recently I've been trying to upgrade an early januarrry -current to
:current -current. I've rebuilt the kernel several times over the last few
:days (with new cvsup's) so i've eliminated any freak check-in mismatches.
:
:During a make world (usually about 10-20 minutes in on my P100) everything
=== pccardc
cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static
-c /usr/src/usr.sbin/pccard/pccardc/beep.c
/usr/src/usr.sbin/pccard/pccardc/beep.c: In function `beep_main':
/usr/src/usr.sbin/pccard/pccardc/beep.c:74: `PIOCSBEEP' undeclared (first
use this function)
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sun, Feb 14, 1999 at 01:01:27PM -0500, Brian Feldman wrote:
[...]
Sorta. It did work. Then it stopped working. Running detect seems to kill my
SM (or at least reset it to some weird state)
{/home/green/examples}$ ./detect
G. Alright, I give up: how does one create a new 'bus' layer?
By that I mean like /sys/dev/iicbus and /sys/dev/smbus. Yes, I've read
the code in these two directories, but I'm confused as to which parts
relate to the bus architecture in general and which parts are speficic
to the I2C and
=== pccardc
cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static
-c /usr/src/usr.sbin/pccard/pccardc/beep.c
/usr/src/usr.sbin/pccard/pccardc/beep.c: In function `beep_main':
/usr/src/usr.sbin/pccard/pccardc/beep.c:74: `PIOCSBEEP' undeclared (first
use this
On Sun, Feb 14, 1999 at 11:58:48AM -0800, Jordan K. Hubbard wrote:
The alternative is to just update GENERIC, LINT et al to use ppbus
instead of the old lpt driver, and throw in a warning in the probe
messages in src/sys/i386/lpt.c telling people to move to ppbus. It
should be pretty safe.
On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote:
On spd I would get an error message, and if I ever did spd 1 it got as far
as printing 128 bytes used, then erred out...
rm alpm.o ; make CC=cc -DDEBUG
I'll rm alpm.o; CC='cc -DDEBUG' make alpm.o; make, if that's what you mean.
On Sun, 14 Feb 1999, Jordan K. Hubbard wrote:
On Sat, Feb 13, 1999 at 07:36:37PM -0800, Jordan K. Hubbard wrote:
FWIW, I would also like to see this happen.
What's the deadline? I did it for -current this day. I'm waiting for
some feedback before the 3.1 replica.
Actually,
I did what I thought was a complete pulldown, but tonite's build will
tell.
On Sun, 14 Feb 1999, Nate Williams wrote:
=== pccardc
cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static
-c /usr/src/usr.sbin/pccard/pccardc/beep.c
Did you upgrade your include files?
I had this same thing happen to me while doing a 'make buildworld'. Once
I did a 'make includes', followed by 'make', the build completed. I would
have expected that the buildworld environment would have had all the required
include files in it.
On Sun, 14 Feb 1999, Brian Feldman wrote:
I'm also getting messages from de0 and lo0 that say:
de0 XXX: driver didn't set ifq_maxlen
That's mostly harmless. It's a warning to driver maintainers that was just
put in recently; the driver hasn't ever set ifq_maxlen, no doubt.
I see this
On Sun, 14 Feb 1999, Brian Feldman wrote:
Sorta. It did work. Then it stopped working. Running detect seems to kill my
SM (or at least reset it to some weird state)
Ahh yes, I'm not alone. Running detect here came up with four ports (5a,
60, 9a, a0 I think). It also caused anything else
On Sun, 14 Feb 1999, Bill Paul wrote:
G. Alright, I give up: how does one create a new 'bus' layer?
By that I mean like /sys/dev/iicbus and /sys/dev/smbus. Yes, I've read
the code in these two directories, but I'm confused as to which parts
relate to the bus architecture in general and
On Sun, 14 Feb 1999, Nicolas Souchu wrote:
On Sun, Feb 14, 1999 at 04:30:27PM -0500, Brian Feldman wrote:
On spd I would get an error message, and if I ever did spd 1 it got as far
as printing 128 bytes used, then erred out...
rm alpm.o ; make CC=cc -DDEBUG
I'll rm alpm.o; CC='cc
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..
This stuff is very cryptic.
On Mon, 15 Feb 1999, Doug Rabson wrote:
I hope I've explained some things.
On Sun, 14 Feb 1999, Alex Zepeda wrote:
Note there's no mention of the limiting to version 1.1 or 1.0. Anyhow..
try rebooting with the flags set to 0x0 and see if that works. I assume
that if you've got an ATX mobo, the BIOS is new enough that the APM
implementation shouldn't be too
On Mon, 15 Feb 1999, Leif Neland wrote:
Could it be because the system thinks everything is flushed, but something
is still in the disk's write-cache? (If such a beast exists...)
I think for whatever reason the computer is being powered off before it's
finished syncing.. as in it doesn't check
I put the line /boot/loader in /boot.conf just like the docs said
(http://www.freebsd.org/~peter/elfday.html). However, I couldn't enter
-c to enter userconfig to configure the kernel. When I entered -c at
the boot: prompt, it didn't go into UserConfig mode, but continued
booting (without me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is anyone currently working on, or planning to implement, hesiod
passwd lookups (either through irs.conf, or nsswitch.conf, etc) in the
getpw* and getgr* libc calls?
- - --
Joey Miller
Lead Programmer
Inficad Communications
888.265.4423
-BEGIN
On Sun, Feb 14, 1999, Donn Miller put this into my mailbox:
I put the line /boot/loader in /boot.conf just like the docs said
(http://www.freebsd.org/~peter/elfday.html). However, I couldn't enter
-c to enter userconfig to configure the kernel. When I entered -c at
the boot: prompt, it
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
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
me the output of vmstat -m every 15 minutes to
try
Yesterday I did an upgrade from 3.0-Release to 3.1-beta. I did
make world, then I made the kernel. At the end of the make kernel,
I got a message about the kernel being elf!!! Bad timing to find
out about this - I was told to look at
http://www.freebsd.org/~peter/elfday.html
and by this time,
This isn't a 'bug', per say, but it bothers me that a small 128 byte
write() is being somehow broken apart into two smaller read()s. It isn't
efficient, and it shouldn't be happening.
Breaking apart write() into read()s would be a BUG :-).
Breaking apart read() into read()s seems to
On Mon, 15 Feb 1999, Kris Kennaway wrote:
I see this on lo0 every time I boot - is this a problem in 3.1 as well, or
just -current? It's probably not good to leave these messages in 3.1 as it
ships, if the former.
FWIW I'm seeing this at bootup now:
ep0 XXX: driver didn't set ifq_maxlen
lo0
:
:This isn't a 'bug', per say, but it bothers me that a small 128 byte
:write() is being somehow broken apart into two smaller read()s. It isn't
:efficient, and it shouldn't be happening.
:
:Breaking apart write() into read()s would be a BUG :-).
:
:Breaking apart read() into
How about a 1-line fix:
Index: uipc_usrreq.c
===
RCS file: /home/ncvs/src/sys/kern/uipc_usrreq.c,v
retrieving revision 1.37
diff -u -r1.37 uipc_usrreq.c
--- uipc_usrreq.c 1998/10/25 17:44:51 1.37
+++ uipc_usrreq.c
71 matches
Mail list logo
