Hello all,
I'v been trying to get this dvd burner to burn, but there seems to be
something wrong with the driver for the controller or the drive..
On boot it is detected as:
acd0: DMA limited to UDMA33, controller found non-ATA66 cable
acd0: DVDR ATAPI DVD A DH20A4P/9P57 at ata0-master
Quoting Jerahmy Pocott, who wrote on Tue, Jun 10, 2008 at 03:58:37PM +1000 ..
Hello all,
I'v been trying to get this dvd burner to burn, but there seems to be
something wrong with the driver for the controller or the drive..
On boot it is detected as:
acd0: DMA limited to UDMA33,
Jerahmy Pocott wrote:
On loading atapicam module it says:
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
I have never managed to use burncd with any drive.
In order to use atapicam, you must enable the pass? devices. My
devfs.conf contains:
# Commonly used by many ports
link
Joe Kelsey wrote:
Jerahmy Pocott wrote:
On loading atapicam module it says:
acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00
I have never managed to use burncd with any drive.
In order to use atapicam, you must enable the pass? devices. My
devfs.conf contains:
# Commonly
On 2008-06-10, Joe Kelsey wrote:
I have never managed to use burncd with any drive.
Just for the record, I've been using burncd successfully with a variety
of drives from the early days of FreeBSD through to at least 7.0-R, so I
doubt if the above means very much.
Greg
Greg Black wrote:
On 2008-06-10, Joe Kelsey wrote:
I have never managed to use burncd with any drive.
Just for the record, I've been using burncd successfully with a variety
of drives from the early days of FreeBSD through to at least 7.0-R, so I
doubt if the above means very much.
I have
On Tue, Jun 10, 2008 at 10:40:44AM +0200, Johan van Selst wrote:
I have had lots of problems with burncd as well: it works fine with some
CD burners, not with others; and hardly ever with the (cheap) DVD drives
that I use. However using atapicam and growisofs as outlined in
Greg Black wrote:
On 2008-06-10, Joe Kelsey wrote:
I have never managed to use burncd with any drive.
Just for the record, I've been using burncd successfully with a variety
of drives from the early days of FreeBSD through to at least 7.0-R, so I
doubt if the above means very much.
I
On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote:
Jona Joachim wrote:
On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote:
Jona Joachim wrote:
Hi!
pkg_delete core dumps on me when it tries to remove linux-tiff.
I can reproduce this reliably.
FWIW you can find
On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote:
On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote:
Jona Joachim wrote:
On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote:
Jona Joachim wrote:
Hi!
pkg_delete core dumps on me when it tries to
On Tue, Jun 10, 2008 at 03:26:30PM +0200, Jona Joachim wrote:
On Tue, Jun 10, 2008 at 05:42:45AM -0700, Jeremy Chadwick wrote:
On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote:
On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote:
Jona Joachim wrote:
On Sun, Jun
On Tue, Jun 10, 2008 at 06:48:40AM -0700, Jeremy Chadwick wrote:
On Tue, Jun 10, 2008 at 03:26:30PM +0200, Jona Joachim wrote:
On Tue, Jun 10, 2008 at 05:42:45AM -0700, Jeremy Chadwick wrote:
On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote:
On Tue, Jun 10, 2008 at 03:14:13AM
This is a small patch that Sam came up with for me, it will allow
drivers to know
when a vlan attaches.
It is transparent to any code that doesn't want to change, but this
will allow my
drivers to finally utilize the vlan hardware filter (something Linux has had for
ever but we lacked).
My test
On Tue, 10 Jun 2008, Timo Sirainen wrote:
On Mon, 2008-06-09 at 22:27 -0500, Sean C. Farley wrote:
On Mon, 9 Jun 2008, Timo Sirainen wrote:
I think clearing environment using:
environ[0] = NULL;
has been kind of a semi-standard for a while now. At least Dovecot
and Postfix clears their
yesterday, as a newbie in his dotage, i was trying to get
packages, re cups, under freebsd 7.0...
got the message that pkg-config later than 0.22, which is
available in packages, was needed...
please advise of any workaround
but should not packages be internally consistent?
Am Tue, 10 Jun 2008 18:03:21 +1000
schrieb Greg Black [EMAIL PROTECTED]:
Just for the record, I've been using burncd successfully with a
variety of drives from the early days of FreeBSD through to at least
7.0-R, so I doubt if the above means very much.
Hi.
I have 2 drives here that don't
On Tue, 10 Jun 2008, Jerahmy Pocott wrote:
*snip*
The drive is able to mount and read cds/dvds fine, but on trying to
use burncd it says:
acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00
Any further attempts produce the above message with no delay to read
from the drive,
On 6/10/08, Jack Vogel [EMAIL PROTECTED] wrote:
This is a small patch that Sam came up with for me, it will allow
drivers to know
when a vlan attaches.
It is transparent to any code that doesn't want to change, but this
will allow my
drivers to finally utilize the vlan hardware filter
On Tue, 2008-06-10 at 12:17 -0500, Sean C. Farley wrote:
I suggest reading the two paragraphs from Open Group's getenv()[1]
documentation starting at Conforming applications are required not
to modify environ directly, ... for the rationale in the new design.
Obviously, applications are
On Mon, 9 Jun 2008 17:52:24 -0700
Jo Rhett [EMAIL PROTECTED] wrote:
The first time mention of BETA and RC cycles came up was in his
reply to me, which was full of personal insults and attacks like the
following, so I discarded it without reply:
I see no reason to assume competence on
Il giorno 27/mag/08, alle ore 16:52, Gerrit Kühn ha scritto:
Hi folks,
I have four identical ITX boards from Jetway here, each having two
re(4)
onboard nics:
[EMAIL PROTECTED]:0:9:0: class=0x02 card=0x10ec16f3 chip=0x816710ec
rev=0x10
hdr=0x00 vendor = 'Realtek Semiconductor'
Hi,
While make buildworld to upgrade:
BerMeJo% uname -a
FreeBSD
BERMEJO-BSD 7.0-RELEASE FreeBSD 7.0-RELEASE #2: Fri Mar 14 20:46:53 CET
2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BERMEJO-BSD i386
Get next error:
.
cc
-fpic -DPIC -O -pipe -march=athlon-mp -I/usr/src/lib/libc/include
://people.freebsd.org/~yongari/re/re.HEAD.20080610
Please also make sure to post dmesg output related with re(4).
--
Regards,
Pyun YongHyeon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
I/m new to FreeBSD (but not Unix in general) and I am setting up an embedded
server to acquire data from a weather station. The data comes from the weather
station console via the USB port on the server. The USB device is a Silicon
Labs CP2102 USB to UART Bridge Controller. Apparently this
From: bazzoola [EMAIL PROTECTED]
Subject: Auto bridge for qemu network [was: kqemu support: not compiled]
Date: Thu, 15 May 2008 03:06:25 -0400
Thanks for updating the port!
I have few suggestions:
#cat /etc/rc.conf
[...]
#KQEMU for qemu
kqemu_enable=YES
#Bridge for qemu
Dennis Flynn wrote:
That doesn't seem right to me. Shouldn't I see something like
7.0-RELEASE-p1 or 7.0-STABLE? Did I do something wrong in my update
to RELEASE? How do I know if I'm running the STABLE kernel with the
driver I want? How can I tell if the driver (uslcom) is there and/or
26 matches
Mail list logo
