On 2001-Aug-26 16:44:54 -0600, Warner Losh <[EMAIL PROTECTED]> wrote:
>In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
>: About a week agao (last Saturday to be exact) I cvsup'd 4.4 RC onto my
>: primary work machine, which is a laptop.
>:
>: It broke badly. Specificly none of the pcmci
In message <[EMAIL PROTECTED]> John Hay writes:
: For those who care, the net4501 only maps the "video" area (0xa -
: 0xb) to the pci bus and not the rest of the hole below 1M. So
: 0xc to 0xe is not usable.
Yuck. If I had more energy for OLDCARD, I'd see how hard it would be
to
> In message <[EMAIL PROTECTED]> John
> Hay writes:
> : pci_cfgintr: BIOS 2.00 doesn't support interrupt routing
>
> I think this is an issue for sopris. However, if you comment out the
> version check in pci_cfgintr, it might work none the less.
I received a new BIOS from Soren at Soekris and
In my last message, I wrote:
"The PC is a Compaq Presario 7360 (a desktop) with a Lucent PC<->PCMCIA
adaptor (but with *no* PCMCIA card in the adaptor)."
Er, I meant Lucent *PCI*<->PCMCIA adaptor.
Ross.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable"
This is with the latest stable cvs (as of about 03:00 UTC on Aug 27th).
The PC is a Compaq Presario 7360 (a desktop) with a Lucent PC<->PCMCIA
adaptor (but with *no* PCMCIA card in the adaptor).
While booting, the console prints
Automatic boot in progress...
pccard: card inse
Any chance I can get a dmesg output of the hang?
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
On 27-Aug-01 Michel Hoche-Mong wrote:
> ...
> I had a similar problem with a Vaio FX220. I reported it last week,
> (and someone else confirmed having similar problems) but it may have
> gotten lost in all the mail about the TI chipset problems, and I thought
> I'd wait until you had that sorted
In message <[EMAIL PROTECTED]> Michel Hoche-Mong writes:
: I had a similar problem with a Vaio FX220. I reported it last week,
: (and someone else confirmed having similar problems) but it may have
: gotten lost in all the mail about the TI chipset problems, and I thought
: I'd wait until you had
On Sun, 26 Aug 2001 at 23:18:52 -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Jim Mock writes:
> : On Sun, 26 Aug 2001 at 22:08:32 -0500, Mark Hittinger wrote:
> : > >Mounting root from ufs:/dev/ad0s1a
> : >
> : > Recompile a kernel with all the USB stuff at the bottom of the
> :
In message <[EMAIL PROTECTED]> Jim Mock writes:
: On Sun, 26 Aug 2001 at 22:08:32 -0500, Mark Hittinger wrote:
: > >Mounting root from ufs:/dev/ad0s1a
: >
: > Recompile a kernel with all the USB stuff at the bottom of the config file
: > commented out. There is something wrong with the USB s
On Sun, 26 Aug 2001, Alex Varju wrote:
> It should be mentioned that I have added new ram to each of these
> machines within the last month. Thinking about it now, it seems to me
> that the problems on the second machine could be attributed to this.
> It could be that it runs fine for a while, an
All rules like this:
pass out quick on * proto tcp from any to any keep state
should have a "flags S" in them.
Darren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Hi,
What were the changes made to ng_pppoe or pppoed in 4.4-RC? Now I can't see
the pppoe service (running a pppoe server) after syncing and re-compiling my
box with 4.4-RC code. Is there anything I should change or changes perhaps
in the client code? The client, Windows 98, is using RASPPPOE.
-
I have this same problem with my Vaio FX220. Attached is two verbose dmesgs
that I took over a serial cable, one of a kernel from last night's source
and one from my old kernel (source from maybe a month ago).
On Sun, 26 Aug 2001, Jim Mock wrote:
> Date: Sun, 26 Aug 2001 18:57:51 -0700
> From:
14 matches
Mail list logo
