This is a patch for better (I think) error handling for pccardc.
(obtained from PAO3)
Please review.
--
Jun Kuriyama // kuriy...@sky.rim.or.jp
// kuriy...@freebsd.orgIndex: pccardc/dumpcis.c
===
RCS file:
This is a patch for better (I think) error handling for pccardc.
(obtained from PAO3)
Please review.
Some of it I like, and others I don't.
@@ -138,9 +138,9 @@
usage(msg)
char *msg;
{
- warnx(enabler: %s, msg);
+ fprintf(stderr, enabler: %s\n, msg);
Hi folks,
I've just committed the alpm(4) driver to -current: the Aladdin SMBus
driver.
With an onboard system management chip (lm7x or w87381),
it offers monitoring capabilities to recent Acer based motherboards like
the ASUS P5AB.
Example program to fetch temperature or voltages is available
Recently I noticed that lpt0 has been replaced by the ppbus stuff, in
LINT. The problem is, I can't find any example as to how to set it up
for a plain, vanilla printer ppbus has so many more capabilities
than lp, I think it's embarrassed about it's dowdy origins. I don't
know what
On 8 Jan 1999, Dag-Erling Smorgrav wrote:
Can anyone tell me if the inetd realloc (and other) problems have been
fixed yet? Searching Deja News shows conflicting reports. I checked
the current diffs, and built version 1.46 - is this a safe version to
use? It's been running on my local
You need:
controller ppbus0 # The ppbus system
device nlpt0 at ppbus? # The printer driver
And finally the parallel port chipset interface,
controller ppc0at isa? port? tty irq 7 drq 3
See ppbus(4) and/or
On Sat, 13 Feb 1999, Chuck Robey wrote:
Recently I noticed that lpt0 has been replaced by the ppbus stuff, in
LINT. The problem is, I can't find any example as to how to set it up
for a plain, vanilla printer ppbus has so many more capabilities
than lp, I think it's embarrassed about
Nicolas Souchu nso...@teaser.fr writes:
controllerppbus0 # The ppbus system
devicenlpt0 at ppbus? # The printer driver
OBTW, when are you planning to rename nlpt0 to lpt0?
DES
--
Dag-Erling Smorgrav - d...@flood.ping.uio.no
To Unsubscribe: send
: dying daemons bug. There have been two attemps to fix the inetd bug:
: one by Matt Dillon in rev. 1.42 and 1.43, and one by me (based on
: patches submitted by Graham Wheeler) in rev. 1.44 and 1.45. I haven't
: heard any complaints about the inetd bug lately, so I'll tentatively
: postulate that
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.
Here are some specifics. If you need more info please let me
know.
- The model
I've been getting the following message, usually within a minute or so after
booting. It shows up only once, and doesn't seem to interfere with normal
operation of the CDR:
(cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(cd1:ahc0:0:5:0): NOT READY asc:4,0
On Sat, Feb 13, 1999 at 10:44:24PM +0100, Ben Stuyts wrote:
I've been getting the following message, usually within a minute or so after
booting. It shows up only once, and doesn't seem to interfere with normal
operation of the CDR:
(cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0
Ben Stuyts wrote...
I've been getting the following message, usually within a minute or so after
booting. It shows up only once, and doesn't seem to interfere with normal
operation of the CDR:
(cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(cd1:ahc0:0:5:0): NOT
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 w87381),
it offers monitoring capabilities to recent Acer based
On Sat, 13 Feb 1999, Chris D. Faulhaber wrote:
cd1: Attempt to query device size failed: NOT READY, Logical unit not
ready, cause not reportable
There is no CD in the drive, which makes the device 'not ready' and therefore
unable to query device size.
If you put a CD in the drive and
On Sat, 13 Feb 1999, Chris D. Faulhaber wrote:
Interesting, this happens to both my CDR and regular CD:
cd0 at ahc0 bus 0 target 3 lun 0
cd0: MATSHITA CD-ROM CR-508 XS03 Removable CD-ROM SCSI-2 device
cd0: 10.0MB/s transfers (10.0MHz, offset 15)
cd0: Attempt to query device size failed: NOT
On 13 Feb 1999, 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?
Hopefully before 3.1 goes
On Sat, 13 Feb 1999, Kenneth D. Merry wrote:
(cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
(cd1:ahc0:0:5:0): NOT READY asc:4,0
(cd1:ahc0:0:5:0): Logical unit not ready, cause not reportable
cd1 at ahc0 bus 0 target 5 lun 0
cd1: PHILIPS CDD2600 1.06 Removable
I just installed a 4.0-SNAP on my laptop (replacing the old 2.2.7
installation), and I must say once I stopped doing stupid things the
install went nicely. But I noticed after I rebooted that
'myname.my.domain' didn't write out any of the config information to
rc.conf (which, of course, doesn't
On 13-Feb-99 Ben Stuyts wrote:
I've been getting the following message, usually within a minute or so after
booting. It shows up only once, and doesn't seem to interfere with normal
operation of the CDR:
(cd1:ahc0:0:5:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
On 13-Feb-99 Ben Stuyts wrote:
On Sat, 13 Feb 1999, Chris D. Faulhaber wrote:
cd1: Attempt to query device size failed: NOT READY, Logical unit not
ready, cause not reportable
There is no CD in the drive, which makes the device 'not ready' and
therefore
unable to query device size.
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 14:02:01 picnic /kernel: ppc0 at 0x378 irq 7 on isa
Feb 13
Today Matthew D. Fuller wrote:
I just installed a 4.0-SNAP on my laptop (replacing the old 2.2.7
installation), and I must say once I stopped doing stupid things the
install went nicely. But I noticed after I rebooted that
'myname.my.domain' didn't write out any of the config information to
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 ppbus0, nlpt0, and ppc0, exactly as
in LINT:
snip
#
According to Matthew Dillon:
strings /usr/sbin/inetd | fgrep Id
ident(1) is your friend :-)
/usr/sbin/inetd:
$Id: inetd.c,v 1.46 1999/01/05 11:56:35 danny Exp $
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr
FreeBSD keltia.freenix.fr 3.0-CURRENT #69:
On Sat, Feb 13, 1999 at 10:19:27PM -0500, a little birdie told me
that jack remarked
I think it's a feature. RELENG_3, as of this morning, does the
same thing for a new install, except that the file exists but is
empty except for the ...just the overrides... header.
For an `upgrade'
I found my problem.
I did a cut-paste from LINT.
# Parallel-Port Bus
# nlpt Parallel Printer
controller ppbus0
# devicelpt0at isa? port? tty irq 7 vector lptintr
device nlpt0 at ppbus?
controller ppc0at isa? disable port ? tty irq 7
FWIW, I would also like to see this happen.
On 13 Feb 1999, Dag-Erling Smorgrav wrote:
Nicolas Souchu nso...@teaser.fr writes:
controllerppbus0 # The ppbus system
devicenlpt0 at ppbus? # The printer driver
OBTW, when are you planning to
On Tue, Feb 09, 1999 at 06:40:58PM -0500, Christopher Masto wrote:
mergemaster
Yes, I have. It doesn't make much of a dent in the real problem, which
is separating diffs like:
variations on a theme deleted
Good point.
I adopted the rc.local solution some time ago, which simplified matters
a
Hmmm. No, that's not what's expected. I've got a test release
rolling on my own machine right now and will install my spam box
with it once it finishes. The intention is definitely for the
changes (and only those) to be written out to /etc/rc.conf.
- Jordan
I just installed a 4.0-SNAP on my
Ben Stuyts wrote...
On Sat, 13 Feb 1999, Chris D. Faulhaber wrote:
Interesting, this happens to both my CDR and regular CD:
cd0 at ahc0 bus 0 target 3 lun 0
cd0: MATSHITA CD-ROM CR-508 XS03 Removable CD-ROM SCSI-2 device
cd0: 10.0MB/s transfers (10.0MHz, offset 15)
cd0: Attempt to
I think it's a feature. RELENG_3, as of this morning, does the
same thing for a new install, except that the file exists but is
empty except for the ...just the overrides... header.
For an `upgrade' install it copies _all_ of the old rc.conf
values into the new one, advertising them as
Today Jordan K. Hubbard wrote:
Erm. Neither of these behaviors are intended, if that's what's going
on. Like I said, I'm waiting for my own release build to finish right
now and will happily fix this if I can reproduce it. It should write
only the customized variables in either the install
until I realized that /etc/rc.conf was empty. It's the anti-POLA! ;)
That's POMA :)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Could anyone point me where FreeBSD development load map if
such one exists?
Is threaded kenel implemented with 4.[0,1,2] ?
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
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?
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of
36 matches
Mail list logo
