ok i finley got this all fix now
im going to post in what i did so that its in the archives so if any one has
this issue/problem maby itll help them out
what i did was edit /boot/device.hints then i added
hint.acpi.0.disabled=1
saved then rebooted and vwalol it worked i had internet access back
You could probably send an excerpt of dmesg regarding your NICs also.
Since this is not a common problem the proper drivers can be kinda broken
basically.
Say, I didn't experience any problems upgrading from 4.10 to 5.3 with fxp.
ok i finley got this all fix now
im going to post in what i did
On Thu, 09 Dec 2004 14:24:35 +0900, Rob [EMAIL PROTECTED] wrote:
Hi,
In /boot/loader.conf, I have
hw.ata.ata_dma=0
to prevent a WRITE_DMA failure crash at bootup.
Unfortunately, this forces my UDMA100 harddisk to operate
at PIO4 speed.
There are patches flying around on this
I've tried researching this on google and playing around
with various things myself to no avail. I should probably
submit this as a bug report, but I'm not sure it is...
I have a Compaq Proliant 1600 server. It's a large box
with four SCSI disks, and (I believe) three controllers.
It's a beast.
Arjan Van Leeuwen wrote:
On Thu, 09 Dec 2004 14:24:35 +0900, Rob [EMAIL PROTECTED] wrote:
Hi,
In /boot/loader.conf, I have
hw.ata.ata_dma=0
to prevent a WRITE_DMA failure crash at bootup.
Unfortunately, this forces my UDMA100 harddisk to operate
at PIO4 speed.
There are patches flying around on
On Thu, 09 Dec 2004 21:04:19 +0900, Rob [EMAIL PROTECTED] wrote:
Arjan Van Leeuwen wrote:
On Thu, 09 Dec 2004 14:24:35 +0900, Rob [EMAIL PROTECTED] wrote:
Hi,
In /boot/loader.conf, I have
hw.ata.ata_dma=0
to prevent a WRITE_DMA failure crash at bootup.
Unfortunately, this forces
The list of untested nodes has been narrowed down
to the following three:
ng_bridge, ng_l2tp, ng_lmi
Please, if you use one of these three test this patch:
http://people.freebsd.org/~glebius/totest/netgraph_callout
T On Thu, Dec 02, 2004 at 06:10:48PM +0300, Gleb Smirnoff wrote:
T T
Rob wrote:
Hi,
In /boot/loader.conf, I have
hw.ata.ata_dma=0
to prevent a WRITE_DMA failure crash at bootup.
Unfortunately, this forces my UDMA100 harddisk to operate
at PIO4 speed.
There are patches flying around on this mailing list that might
solve the problem. I'm very keen on testing such
Hello!
I am trying to install FreeBSD on my laptop (HP/Compaq nx9105), but as
soon as I choose an alternative on the first menu that appears my
computer shuts down. It happened both with 5.1 and 5.2.1, and it
happens no matter which alternative I choose. I really have no clue
what to do. I have
Btw, the most recent *stable* release is 5.3. You'd better use this one.
What do you mean an alternative on the first menu?
Please choose the stage you experience shutdown in from the following link:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-start.html
Hello!
I am
Hello,
i have a little problem.
I hav Host A andHost B both are connected to an SAN
through an QLA2200 Fibre-Channel (man isp).
On the SAN are 14 Disks da0-da13 these Disks are configured
w/ vinum to an RAID 10 Filesystem.
Now i have the Problem i would make Host A to an PDC and
HOST B
In response to popular demand, I am now providing both GENERIC and
SMP kernels via FreeBSD Update to people running FreeBSD 5.3. To
take advantage of this on your FreeBSD 5.3 (and only 5.3!) SMP system,
run the following commands as root:
# touch /boot/kernel/SMP
# freebsd-update fetch
* Scott Long [EMAIL PROTECTED] [041209 15:59]:
Hello,
It would be nice if I can set hw.ata.ata_dma=0 at the loader
prompt during bootup, so that the system at least will boot from
harddisk. Is that possible?
Yes, that's possible. Drop the loader to the prompt and do the following:
set
[cc'ing to FreeBSD-Stable]
Hi,
I know that the proposed patches I submitted are not the best patches, but
given that the next release of RELENG_4 is coming out, would it not be
better to commit those to RELENG_4 as they allow the modem to work when it
shares an interrupt with another device ?
Hello,
does anyone know a source, where I can download a 3.5(1)-RELEASE
ISO-Image?
Kind regards,
Thomas.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Thu, Dec 09, 2004 at 08:30:39PM +0100, Thoamas Krause -CI- wrote:
does anyone know a source, where I can download a 3.5(1)-RELEASE
ISO-Image?
ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/
--
Ken Smith
- From there to
Søren Schmidt wrote:
Garance A Drosihn wrote:
At 1:01 AM -0600 12/7/04, Tim Welch wrote:
I'm getting NID not found/DMA errors on 5-STABLE with a Seagate 200gb
sata drive:
ad2: FAILURE - WRITE_DMA status=51READY,DSC,ERROR
error=10NID_NOT_FOUND LBA=268435455
This appears to be a result of
Rob wrote:
Hi guys,
This is the first post I have seen on stable about SATA. (ok, maybe I'm
not subscribed to the right lists) Anyway I bought a brand new
beautiful Plextor DVD+RW SATA drive (PX712SA) for use on my AMD64+3800
machine. Win XP64-beta won't recognize it, and neither will
Hey,
I'm seeing a semi-reproducable panic with pfctl in 5.3-RELEASE. The
machine is an IPv6 router/firewall, the pf firewall includes rules for
both ipv4 and ipv6. Sadly, the machine is not running with a debug
kernel, but I do have dumps of the panics. It's a single processor
machine with
Sren Schmidt [EMAIL PROTECTED] probably said:
SATA ATAPI devices are not supported yet.
There are a few gotcha's though. Not all SATA controllers does support
SATA ATAPI even if out driver would, so its a mixed blessing for now.
Anyhow, as soon as I can get my hands on a SATA ATAPI device,
Peter Radcliffe wrote:
Sren Schmidt [EMAIL PROTECTED] probably said:
SATA ATAPI devices are not supported yet.
There are a few gotcha's though. Not all SATA controllers does support
SATA ATAPI even if out driver would, so its a mixed blessing for now.
Anyhow, as soon as I can get my hands on a
Rob [EMAIL PROTECTED] probably said:
Same here, I could remove it and ship it to you today, probably 2nd day
air, or one of the cheaper but fast services. If P, however, doesn't
have to tear his computer all apart LOL, maybe that might be a better
solution for me.
I was more suggesting
On Wed, 8 Dec 2004, Michael Nottebrock wrote:
I.e., do the individual elements work from the debugger. If they do, then
we can try the same from entering the debugger following the panic, and
see how things differ.
All of the above works when entering the debugger from the watchdog
Peter Radcliffe wrote:
Sren Schmidt [EMAIL PROTECTED] probably said:
SATA ATAPI devices are not supported yet.
There are a few gotcha's though. Not all SATA controllers does support
SATA ATAPI even if out driver would, so its a mixed blessing for now.
Anyhow, as soon as I can get my hands on a
At 9:49 PM +0100 12/9/04, Søren Schmidt wrote:
I'm going to work on it soon thats for sure, however I have lots
on the burner currently so its no rush. However all kinds of
(S)ATA/ATAPI gear is always most welcome here in the lab, the
levels of support I can provide is directly proportional to the
On Mon, 29 Nov 2004, Christian Brueffer wrote:
got this panic today on an SMP system. Modifications to the kernel are
polling and altq support for the sf driver and removed SMP ifdefs from
sys/kern/kern_poll.c.
FreeBSD haakonia.hitnet.RWTH-Aachen.DE 5.3-STABLE FreeBSD 5.3-STABLE
#61: Sat
Garance A Drosihn wrote:
At 9:49 PM +0100 12/9/04, Søren Schmidt wrote:
I'm going to work on it soon thats for sure, however I have lots
on the burner currently so its no rush. However all kinds of
(S)ATA/ATAPI gear is always most welcome here in the lab, the
levels of support I can provide is
Sren Schmidt [EMAIL PROTECTED] probably said:
Well, you probably should take care of your sister first :)
And no I dont have a paypal account, so far I've got by fine without it,
by using other means as checks, wiretransfers etc etc...
Do you have a list of things (particular devices or
On Thursday, 9 December 2004 at 14:52:14 +0100, Michael Schuh wrote:
Hello,
sorry for my wrong posting, it was late at night and i have *not*
doublechecked my configuration.
If you get a panic, it's not your fault. You shouldn't be able to
panic the machine with an invalid configuration.
upon the recimendation of dima im posting an excerpt from dmesg listing my
net cards
xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xbc00-0xbc7f mem
0xe2001000-0xe200107f irq 5 at device 9.0 on pci0
miibus0: MII bus on xl0
xlphy0: 3c905C 10/100 internal PHY on miibus0
xlphy0: 10baseT, 10baseT-FDX,
I'm getting reports from a user who can't build a port on 4.10,
because his system has a sys/bitypes.h header which contains
definitions that collide with sys/inttypes.h and sys/types.h.
As far as I can tell, there is no sys/bitypes.h in 4.10.
In fact, I can't find this header file in the
Peter Radcliffe wrote:
Rob [EMAIL PROTECTED] probably said:
Same here, I could remove it and ship it to you today, probably 2nd day
air, or one of the cheaper but fast services. If P, however, doesn't
have to tear his computer all apart LOL, maybe that might be a better
solution for me.
I was
I've had a server freeze three times on me know and I have no idea what
the problem is... of course nothing gets output to the logs. The first
time it was at 3AM on a Sunday so I thought the problem must be one of
the periodic scripts. But those seemed fine when run by hand. The
second two
Hi, Jeremie and Lists.
The previous patch to change if_em's int_throttle_ceil into
sysctl-able cause a kernel panic. If you set em's int_throttle_ceil=0
and then reconfigure the em, it cause a diveded by zero panic.
This patch for original if_em.[ch] which is attached to this mail is
I've tried researching this on google and playing around
with various things myself to no avail. I should probably
submit this as a bug report, but I'm not sure it is...
I have a Compaq Proliant 1600 server. It's a large box
with four SCSI disks, and (I believe) three controllers.
It's a beast.
I had a similar problem with a machine with two Adaptec 2940UW
controllers. When I upgraded from somethng like 4.7 to 4.8 the machine
stopped booting. My workaround was to go with a single controller.
The problem seems to be that at some point in the 4.X development cycle
the way in which
36 matches
Mail list logo
