Im getting problems to get the DVD burner in udma4 mode. It says:
ata1-master: DMA limited to UDMA33, non-ATA66 cable or device
This is wrong, the device is udma4 capable.
The problem seems to be in the detection of the cable type, it detects it as
40-pin, while its a 80-pin one. (dmsg is at
Billy Newsom wrote:
Okay, I'm going to dig up someone who might be responsible or might be
able to fix it. Two strikes while doing the same upgrade... While I'm
thinking about it, would you see if it happens on the next reboot? I
haven't tried, because my system is a firewall that I need to
Hello,
I've run into an issue that has me stumped. Anything that I link against
libpthread on my FreeBSD-5.4-RELEASE/i386 installation will segfault as
soon as it tries making use of the threads. For example:
$ kedit
zsh: segmentation fault (core dumped) kedit
$ gdb `which kedit` -c kedit.core
[
Hi Robert and all,
I'm really sorry for my cross posting, I posted my problem a year ago and
I'm still having trouble with tftp server.
I switched to Windows tftp server like 3Com 3C daemon for a while and now I
want to use tftp server on FreeBSD.
I'm using FreeBSD 5.4-STABLE and I tested def
On Sun, May 29, 2005 at 01:24:01AM +0400, Boris Samorodov wrote:
> Hi!
>
>
> What do you think in minor change to /etc/rc.d/var:
>
Content-Description: patch to /etc/rc.d/var
> --- var.orig Sun May 29 01:05:47 2005
> +++ var Sun May 29 01:06:12 2005
> @@ -28,7 +28,7 @@
> #
>
> # PROV
On Sun, May 29, 2005 at 10:10:24PM +0100, Imobach Gonz??lez Sosa wrote:
> Hi all,
>
> Ok, I'm new to FreeBSD (for second time :)) and I'm getting an strange
> behaviour. I don't know if you could help me, but I've to try. I've read the
> handbook, manpages and search google for a while, but I don'
Hi all,
Ok, I'm new to FreeBSD (for second time :)) and I'm getting an strange
behaviour. I don't know if you could help me, but I've to try. I've read the
handbook, manpages and search google for a while, but I don't know how to
solve it.
I have some machines in my network, connected to Internet
Hello,
Today I noticed following message in the log:
> KDB: stack backtrace:
> kdb_backtrace(c07163b8,2,c661994c,0,22) at kdb_backtrace+0x2e
> getdirtybuf(d109ebac,0,1,c661994c,1) at getdirtybuf+0x2b
> flush_deplist(c282f4cc,1,d109ebd4,d109ebd8,0) at flush_deplist+0x57
> flush_inodedep_deps(c15ba
On Sun, May 29, 2005 at 08:09:49PM +0200, K?vesd?n G?bor wrote:
> No, I don't have anything in syslog, but I've relaized, when I run make,
> these errors happen more often. You mentioned, there this is a common
> problem on SMP systems when one start more processes simultaneously, but
> it is a
No, I don't have anything in syslog, but I've relaized, when I run make,
these errors happen more often. You mentioned, there this is a common
problem on SMP systems when one start more processes simultaneously, but
it is a single processor system. Might this error also exist on single
processo
On May 28, 2005, at 15:56, Claus Guttesen wrote:
whatever. The ports-collection will take care of dependencies.
Upgrading is done by portupgrade zsh for instance.
Just a small hint: personally I tend to always use the "-b" option to
create a backup copy of the previous version (usually saved
Michael Grant <[EMAIL PROTECTED]> wrote:
> # mdconfig -l -u md0
> md0 vnode 23503425 KBytes
-current has support for showing the file name:
# mdconfig -lu0
md0 vnode 3.0M /home/dima/test
I don't know when this will be MFC'd.
> Furthermore, could we have that info when we run
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.11.17 - Release Date: 25.05.2005
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To uns
On Sat, 28 May 2005 18:18:41 +0200 (CEST)
Tomas Pluskal <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm using 5-STABLE and it panics when I try to unload the sound
> module (for Sound Blaster PCI 128).
>
> # kldunload es_137x.ko
> pcm0: unregister: mixer busy
> kldunload: can't unload file: Devi
Hello,
I'm using 5-STABLE and it panics when I try to unload the sound module
(for Sound Blaster PCI 128).
# kldunload es_137x.ko
pcm0: unregister: mixer busy
kldunload: can't unload file: Device busy
when I do that once more:
# kldunload es_137x.ko
WARNING: Driver mistake: destroy_dev on
15 matches
Mail list logo