At 10:25 PM 04/06/2004, Rafael R Obelheiro wrote:
This is the culprit. I was having the same problem (PPPoE stopped
working), but recompiling my system with the previous (1.2.2.14) of
ng_ether.c solved it. Archie, is it possible to fix this (either by
reverting the patch or by applying a new one)?
Vivek Khera wrote:
You might want to reconsider the PERC controllers offered with that
hardware. They (PERC3/SC and PERC4/SC) use the amr (megaraid) driver,
and we've had serious stability problems under FreeBSD 4.9 and 5.2.1
with that controller
I'll counter this remark with a "works great her
> Not sure what else to show... should I attach my serial console to get
> the cd boot messages?
Yes please.
Here is the boot -sv using the 4.10-RELEASE cd
SMAP type=01 base= len=0009fc00
SMAP type=02 base=000f len=0001
SMAP type=02 base=fec0
Lee Harr wrote:
So, now... what could be the difference that allows the cd to boot, but
not the same kernel booting from the hard drive?
Do we know that the cd has the same kernel? Could it be possible that
the install cd's kernel isn't GENERIC?
___
[EMA
On Fri, Jun 04, 2004 at 01:14:23AM -0400, Rob Clark wrote:
> On Thu, 3 Jun 2004 20:10:16 -0400
> Rob Clark <[EMAIL PROTECTED]> wrote:
>
> > On Thu, 03 Jun 2004 18:16:00
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Dear all,
> > >
> > > I update my system 4.10-STABLE(27 May) to FreeBSD
> > > 4.10-STA
Hi All,
I was wondering if there's a way to block port scans in ipfw. Is there
something similar to the psd module for iptables?
Thank you,
Khoi
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscrib
sc0 flags = 0x100 by default.
hint.sc.0.flags="0x100"
(...)
atkbdc0: port 0x60,0x64 irq 1 on acpi0
atkbd0: flags 0x1 irq 1 on atkbdc0
atkbd: unable to set the command byte.
(...)
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
(...)
Matthew George wrote:
try setting the f
Doug White wrote:
Also, Lite-on drives are known to have buggy firmware. Does removing the
CDROM drive make it boot?
No. It hangs on whatever the last drive is. For example, if I have a
hard drive and a cd-rom it displays ad0... for the hard drive and then
will hang on the cdrom (after displaying
On Jun 4, 2004, at 4:15 AM, Sven Hazejager wrote:
The Athlon PC runs a 4.10 world, built with pentiumpro optimizations.
If I
buildworld with pentium optimizations, does that newly built world
rely on
any pentiumpro optimized libraries of the Athlon PC base? That would
surely hose the Pentium PC!
On Fri, 4 Jun 2004, D. Pageau wrote:
> Keyboard error on IBM xSeries 335 with Freebsd 5.2.1 but work fine with
> 4.10.
>
are you using 'flags 0x100' on your device sc0 line in your kernel?
--
Matthew George
SecureWorks Technical Operations
___
[EMAI
Keyboard error on IBM xSeries 335 with Freebsd 5.2.1 but work fine with
4.10.
The keyboard work well in installation process (floppy install), then I
reboot. Keyboard work fine at the boot manager but died as soon FreeBSD
is booted.
The hardware is IBM xSeries 335. I can confirm that problem
11 matches
Mail list logo