At 1:31 AM +0100 1999/9/27, Brian Somers wrote:
> An interesting extension: If an AOL MX receives a message with an
> AOL from address from a non-AOL relay it's accepted for delivery and
> dropped in the bit-bucket. Well, it's obviously spam (isn't it?) !
This item kept coming up about
On Mon, 27 Sep 1999, Mitsuru IWASAKI wrote:
> Hi, Mike.
> # I'm very happy because of your reply :)
>
> > > > We wrote experimental ACPI driver for 4.0-CURRENT.
> > >
> > > This was just one week work so its functionallity is very very poor :-)
> > > but I think it is good idea to start with th
On Sun, 26 Sep 1999, Donald J . Maddox wrote:
> On Sun, Sep 26, 1999 at 12:29:46PM -0700, Mike Smith wrote:
> > >
> > > But we do have a working driver for the AWE64. Or rather, it worked fine
> > > before the new PnP code was comitted, now it doesn't. It seems to me that
> > > this indicates
On Sun, 26 Sep 1999, Donald J . Maddox wrote:
> I couldn't get my PnP Creative AWE64G to work with the new PnP
> code, so I tried compiling a kernel with pcm instead. All I get is:
>
> unknown0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0
> unknown1: at port 0x200-0x207
On Sun, 26 Sep 1999, Doug wrote:
> Peter Wemm wrote:
> >
> > "Donald J . Maddox" wrote:
> > > Ok, will do. Thanks.
> > >
> > > This may be a silly question, but... The old PnP driver recognized
> > > a lot of devices, including my AWE64. Isn't there a list of IDs it
> > > was aware of that sh
> It requires converting the ancient voxware driver to newbus which isn't
> really feasable.
I am not sure about that ... The irq handling, card registration on the voxware
is fairly straight forward.
--
Amancio Hasty
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
* Soren Schmidt ([EMAIL PROTECTED]) [990927 09:18]:
>It seems Jason Young wrote:
>>
>> I looked at this yesterday (we just got one in). The HighPoint controller
>> has some specific initialization needs, just like the Promise controller.
>>
>> I wonder if Soren (sorry, I don't know how to persua
Hi all,
I've done some major reworking of the Bt848/Bt878 driver in the last few
weeks
and everything is now committed to -current.
The old brooktree848.c file has gone.
It is now replaced by bktr_core.c bktr_audio.c bktr_tuner.c bktr_card.c
and bktr_os.c
which neatly seperate out the main Bt84
It seems Jeroen Ruigrok/Asmodai wrote:
>
> you know I have the possession of a development box with the HPT366,
> right? [well you should since I mailed you those timing-tables =P ]
I know :)
> Anyways, as soon as I have enough cash again I will buy an /66 disk
> and stuff it on the free contro
> :I finally saw my first -current panic in more than 5 months (not a bad
> :track record).
> :
> :I have a panic that I can duplicate with a 24 hour old "make world"
> :and a 4 hour old -current kernel. If I run the linux netscape (installed
> :from ports less than a week ago), the kernel panics
$apm -Z
// going to sleep
//... 10 hours later ...
// key pressed
ata0: resetting devices .. done
ata1: resetting devices ..
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x4
fault code = supervisor read, page not present
instruction pointer = 0x8:0
I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
(primary slave) and a CDROM as secondary master. The driver detects the
8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd provide
more info if I could but / lives on the second drive so I'm not sure if
I ca
6 4.0-19990918-SNAP
drwxr-xr-x 20 root wheel 1024 Sep 22 16:30 4.0-19990922-SNAP
drwxr-xr-x 20 root wheel 1024 Sep 24 06:58 4.0-19990924-SNAP
drwxr-xr-x 20 root wheel 1024 Sep 27 07:06 4.0-19990927-SNAP
Unfortunately, I have no way of making these SNAPs publicly
available due to the firew
It seems Jeremy L. Stock wrote:
> I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
> (primary slave) and a CDROM as secondary master. The driver detects the
> 8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd provide
> more info if I could but / lives on
Following the suggestion of Mr. Peter Wemm, I manage to get my ESS1869
sound card work again. The attachments are the `dmesg' message and the
`pnpinfo -v' output. I am grateful if the ID can be added.
Thank you very much.
regards,
Wang Shidong
Copyright (c) 1992-1999 The FreeBSD Project.
Copyr
On Mon, 27 Sep 1999, Soren Schmidt wrote:
>It seems Jeremy L. Stock wrote:
>> I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
>> (primary slave) and a CDROM as secondary master. The driver detects the
>> 8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd
It seems Jeremy L. Stock wrote:
>>Are you sure you have the latest versions of everything in /sys/dev/ata ??
>>There was a window of opportunity where I messed up unless ATA_STATIC_ID
>>was defined...
>>
>>-Søren
>>
>
>Fairly positive I have the latest versions. I cvsup'ed twice yesterday. I
>forg
> > I'm having a problem where the "vinum start" command crashes my system.
> > This happens regardless of whether it's being issued during bootup via
> > /etc/rc or from the command line on a running system.
> >
> > Interestingly, however, if I issue the start command from the vinum
> > interacti
On Mon, 27 Sep 1999, Soren Schmidt wrote:
>It seems Jeremy L. Stock wrote:
>>>Are you sure you have the latest versions of everything in /sys/dev/ata ??
>>>There was a window of opportunity where I messed up unless ATA_STATIC_ID
>>>was defined...
>>>
>>>-Søren
>>>
>>
>>Fairly positive I have the
> "Soren" == Soren Schmidt <[EMAIL PROTECTED]> writes:
Soren> It seems Viren R. Shah wrote:
>>
>> I made world and build a new kernel on Friday the 24th, and later that
>> evening, I got these:
>>
>> Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact -
>r
> I'm just suggesting here that it would be nice if the authors of
> this code would make it _equally functional_ to what was removed.
> It's not nice to remove functionality unconditionally and then
> provide no replacement at all...
That work is underway, and something to understand about -curr
> > I'm just suggesting here that it would be nice if the authors of
> > this code would make it _equally functional_ to what was removed.
> > It's not nice to remove functionality unconditionally and then
> > provide no replacement at all...
>
> That work is underway, and something to understand
In message <[EMAIL PROTECTED]> Doug Rabson
writes:
: case 0x31008c0e: /* CTL0031 */
: case 0x41008c0e: /* CTL0041 */
: case 0x42008c0e: /* CTL0042 */
: + case 0x44008c0e: /* CTL0044 */
: case 0x45008c0e: /* CTL0045 */
What is CTL0043? Seems like a logical progression
> If that was only true. Or should I ask why didn't CAM from -3.3 get
> reverted to the old scsi code before 3.3 was released. I have seen
> no less than 2, and perhaps 3 people try to get cards that did work
> under pre-CAM 3.x working under post-CAM 3.x. I know this is a slippery
> slope, but
auth fdfda9f6 unsubscribe freebsd-current [EMAIL PROTECTED]
auth 8a3cc747 unsubscribe cvs-all [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
As Jonathan M. Bresler wrote ...
>
> stopping chat on the tech lists is an open research project ;)
Very much so. It will most likely require GenuineIntelligence
(as opposed to AI or the organic, carbon based variant we all know too
well ;-)
GenuineIntelligence is not scheduled for release for
http://phk.freebsd.dk/tty
--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED] "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
According to Peter Jeremy:
> That's the way I remembered things. What threw me is that I currently
> have two _different_ gcc directories, both claiming to be EGCS 1.1.2,
> and both being updated.
The main reason is that we don't lose history with the directory change. At
first we had contrib/gc
I was concerned about the extra checks by devices that
have control devices. But a quick sample of drivers indicates that
the test for si_tty != NULL catches those. I haven't done an exhaustive
test, but it looks like these changes are functionally equivalent to old
code assuming that si_tty is c
At 01:05 PM 9/27/99 -0400, Brad Chisholm wrote:
>Well, I believe I discovered the source of my problem. It turns out that
>I did not have the correct devices configured in /dev for the component
>drives. I had da[0-3]e, but not da[0-3]s1e. The documentation seemed to
>indicate that the da?s1?
God knows, I'll second that one... :-) Hear, hear!
On Sun, Sep 26, 1999 at 07:39:27PM -0700, Darryl Okahata wrote:
> I want to publicly thank Peter Wemm for posting a reply that is
> courteous, informative, and useful. Recently, there has been too much
> noise in this and other FreeBSD lis
Thanks, Doug. Peter already provided an equivalent patch, and I am
happy to report that it works like a charm (of course :-)).
On Mon, Sep 27, 1999 at 10:35:46AM +0100, Doug Rabson wrote:
> On Sun, 26 Sep 1999, Donald J . Maddox wrote:
>
> > I couldn't get my PnP Creative AWE64G to work with th
I'm happy to report that for my WinTV card, the bktr drivers are working
well with the latest changes. Keep up the good work.
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #:
On Monday, 27 September 1999 at 15:37:30 -0500, Jeffrey J. Mountin wrote:
> At 01:05 PM 9/27/99 -0400, Brad Chisholm wrote:
>> Well, I believe I discovered the source of my problem. It turns out that
>> I did not have the correct devices configured in /dev for the component
>> drives. I had da[0
Donald J . Maddox scribbled this message on Sep 26:
> I see that support has been added for demand-loading network
> if drivers. I seem to recall that the last time I tried using
> network drivers as klds, nothing that required bpf to work
> was functional anymore, because bpf required that the d
> : case 0x31008c0e: /* CTL0031 */
> : case 0x41008c0e: /* CTL0041 */
> : case 0x42008c0e: /* CTL0042 */
> : + case 0x44008c0e: /* CTL0044 */
> : case 0x45008c0e: /* CTL0045 */
> What is CTL0043? Seems like a logical progression to me :-
Thanks for the info. I do read the commit logs, and I was aware
of this commit; however, it's not entirely clear to me if this
commit resolves the issue I'm talking about.
The problem, as I recall, had to do with the bpf pseudo-device
attaching to devices _only_ at boot time, so it would not see
Running rvplayer crashes the system. Catting a small .au
file works but a large one panics the system so I think the
problem may just be the drq difference. I know a number of
people in the FreeBSD crowd have this system (a Toshiba
Equium 6200M -- a `good' buy 15 months back) so this can't be
an
On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
> Good software shouldn't panic.
I wish _I_ could convince some people of this :-(.
> > Most certainly is. Could use the functionality to add to a plex's size for
> > striped or RAID5, but a bit of planning cures that. 8-)
>
> It's a
On Tuesday, 28 September 1999 at 12:59:34 +1000, Peter Jeremy wrote:
> On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>> Good software shouldn't panic.
> I wish _I_ could convince some people of this :-(.
>
>>> Most certainly is. Could use the functionality to add to a plex's size f
hi,
i just recently upgraded from stable->current successfully. a program i use
often is unable to run any more though. the program dies in the following spot:
__builtin_apply( serv->cb, __builtin_apply_args(), MAX_DIM_ARGS_LIST));
it dies with a signal 8, floating point exception. browsing ove
Check this out, if anyone is intrested.
I found this on packetstorm.securify.com tonight. Any ideas??
[Resending once, since it's been 10.5 days...]
Here's an interesting denial-of-service attack against FreeBSD >=3.0
systems. It abuses a flaw in the `new' FreeBSD vfs_cache.c; it has no
way t
this was fixed in the final hours before 3.3-release.
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_cache.c
1.38.2.3 Thu Sep 16 2:02:15 1999 UTC by alfred
CVS Tags: RELENG_3_3_0_RELEASE; Branch: RELENG_3
Diffs to 1.38.2.2
Limit aliases to a vnode in the namecache to a sysctl
At 08:41 AM 9/28/99 +0930, Greg Lehey wrote:
>It has changed (again).
And the preferred method is...
a) /dev/da0
b) /dev/da0s1
c) /dev/da0s1e
(-current and -stable I hope :)
>> Not to surprising that it paniced with what appeared to be a
>> "dedicated" disk (ie da0e).
>
>It's surprising. Good s
On Tuesday, 28 September 1999 at 0:36:40 -0500, Jeffrey J. Mountin wrote:
> At 08:41 AM 9/28/99 +0930, Greg Lehey wrote:
>> It has changed (again).
>
> And the preferred method is...
> a) /dev/da0
> b) /dev/da0s1
> c) /dev/da0s1e
> (-current and -stable I hope :)
(b) or (c). (a) isn't a slice.
> On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
> > Good software shouldn't panic.
> I wish _I_ could convince some people of this :-(.
>
> > > Most certainly is. Could use the functionality to add to a plex's size for
> > > striped or RAID5, but a bit of planning cures that. 8-)
46 matches
Mail list logo
