Hi. I have problem with sounde device on my notebook(Sony PCG-C1VSX/K)
If I kldload snd_ds1, then sound device is recognized as follows
pcm0: mem 0xfc108000-0xfc10 irq 9 at device 9.0 on pci0
;; % cat /dev/sndstat
;; FreeBSD Audio Driver (newpcm) Aug 9 2001 23:38:44
;; Installed devices:
Hi. On my machine (Sony PCG-C1VSX/K notebook), Lid open/close (or, acpiconf -s 1)
output following messages
/boot/kernel/kernel: acpi_lid0: Lid closed
/boot/kernel/kernel: acpi0: AcpiHwObtainSleepTypeRegisterData failed - AE_NOT_FOUND
/boot/kernel/kernel: acpi_lid0: Lid opened
/boot/kernel/kernel
On 09-Aug-01 Paul Saab wrote:
> David Malone ([EMAIL PROTECTED]) wrote:
>> On Thu, Aug 09, 2001 at 11:12:32AM -0700, John Baldwin wrote:
>> > > It appears that gas is now properly padding the end of the text
>> > > section (and inserting the jmp and nops). This, in turn, misaligns
>> > > the lo
David Malone ([EMAIL PROTECTED]) wrote:
> On Thu, Aug 09, 2001 at 11:12:32AM -0700, John Baldwin wrote:
> > > It appears that gas is now properly padding the end of the text
> > > section (and inserting the jmp and nops). This, in turn, misaligns
> > > the loader that is tacked onto the end of t
On Thu, Aug 09, 2001 at 11:12:32AM -0700, John Baldwin wrote:
> > It appears that gas is now properly padding the end of the text
> > section (and inserting the jmp and nops). This, in turn, misaligns
> > the loader that is tacked onto the end of the pxeldr. I'm currently
> > not setup to test
Hi folks:
Well, after threatening to do it for a long time, I finally sat down and
converted one of my ethernet drivers to use the bus_dma API so that I
no longer have to do things like call contigmalloc() and/or vtophys()
directly. The changes I made are to the driver in -current, and the
new co
On 09-Aug-01 Harti Brandt wrote:
>
> Hello,
>
> some time ago we reported a problem with pxeboot under -current (see below).
> We have tried to track down the problem and it seems to be a bug or a
> feature in gas or libbfd. It turns out, that the output from pxeldr before
> the binutils-2.11 i
On 09-Aug-01 Mark Peek wrote:
> At 4:46 PM +0200 8/9/01, Harti Brandt wrote:
>>some time ago we reported a problem with pxeboot under -current (see below).
>>We have tried to track down the problem and it seems to be a bug or a
>>feature in gas or libbfd. It turns out, that the output from pxeldr
I was trying to do a make -j 16.. silly me:
lock order reversal
1st 0xfe000a90c508 process lock @ ../../../vm/vm_glue.c:469
2nd 0xfe0ddcc0 lockmgr interlock @ ../../../kern/kern_lock.c:239
pid 35005 (cc), uid 0: exited on signal 6 (core dumped)
pid 35003 (sh), uid 0: exited on sign
Thus spake David O'Brien ([EMAIL PROTECTED]):
>
> > It's far removed from being "plain" OpenSSH or "portable" OpenSSH.
> This the "FreeBSD" added to the version string.
If it's of any interest: I'd also prefer "FreeBSD OpenSSH" as
David suggested.
Thanks
Alex
To Unsubscribe: send mail to [EMA
At 4:46 PM +0200 8/9/01, Harti Brandt wrote:
>some time ago we reported a problem with pxeboot under -current (see below).
>We have tried to track down the problem and it seems to be a bug or a
>feature in gas or libbfd. It turns out, that the output from pxeldr before
>the binutils-2.11 import on
Hello,
some time ago we reported a problem with pxeboot under -current (see below).
We have tried to track down the problem and it seems to be a bug or a
feature in gas or libbfd. It turns out, that the output from pxeldr before
the binutils-2.11 import on 5/29/2001 was 500 bytes long. After the
< said:
> Usually it involves an NMI switch. :( Can you cvs (or cvsup) by dates on the
> kernel sources to narrow down exactly what day (and possibly what commit)
> causes these lockups? I.e., does it work fine on August 4th, but break on
> August 5th?
I have a July 26th kernel which every wee
On Tue, Aug 07, 2001 at 11:46:45PM -0500, Sean Kelly wrote:
> I'm surry I don't have much data to provide, but...
>
> I've been experiencing random lockups on a -CURRENT kernel from the August
> 5th source. I've gotten it a lot when running screen and ssh on two
> different terminals at the same
David!
As you have been warned, revisions 1.19 and 1.20 to file/Makefile
broke cross builds and upgrade path from 4.x to 5.0. This is due
to the use of just built ./file binary to produce magic.mgc and
magic.mime.mgc files. In the case of 4.x->5.0 upgrade, buildworld
bombs with
./file -C -m ma
15 matches
Mail list logo