2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
> >>>> On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> >>>>> I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> >>>>> after going from 7.4 to 9.1 when using ATA
wrote:
I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
a Promise PDC20268 UDMA100 controller. A standard harddisk drive
attached to this controller works well. Cables, controller and drive
where replaced already
gt; > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> > > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> > > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive
> > > > attached to this controller works
gt; > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> > > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> > > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive
> > > > attached to this controller works
On Wed, Apr 17, 2013 at 08:26:00AM +0200, Andre Albsmeier wrote:
> On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
> > On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> > > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> >
On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
> On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> &g
On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> a Promise PDC20268 UDMA100 controller. A standard harddisk drive
> attached to thi
I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
a Promise PDC20268 UDMA100 controller. A standard harddisk drive
attached to this controller works well. Cables, controller and drive
where replaced already.
Kernel
On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote:
> Hello,
>
> I think that reading from CDROM is actually broken
> in 9.0-RELEASE/sparc64.
>
> On FreeBSD 8.2-RELEASE/sparc64, mounting a physical
> CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso
> and running sh
On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote:
> Hello,
>
> I think that reading from CDROM is actually broken
> in 9.0-RELEASE/sparc64.
>
> On FreeBSD 8.2-RELEASE/sparc64, mounting a physical
> CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso
> and running sh
Hello,
I think that reading from CDROM is actually broken
in 9.0-RELEASE/sparc64.
On FreeBSD 8.2-RELEASE/sparc64, mounting a physical
CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso
and running sha256 on usr/freebsd-dist/*.txz yields the same
results as listed in usr/freebsd-dist
On 16/11/2011 15:45, Joel Dahl wrote:
>
> Hmm. We're running many FreeBSD 8.2 machines as guests in VMware but have
> never encountered the panic described above. Should I be worried? :-)
>
I've encountered them often enough that I started removing cdrom devices
from the
On 16-11-2011 16:33, Alexander Motin wrote:
> On 11/16/11 16:14, Bjoern A. Zeeb wrote:
> > On Wed, 16 Nov 2011, Alexander Motin wrote:
> >
> >> Hi.
> >>
> >> On 11/16/11 08:43, Bjoern A. Zeeb wrote:
> >>> we have seen this or a very similar panic for about 1 year now once in
> >>> a while and I th
On 11/16/11 16:14, Bjoern A. Zeeb wrote:
> On Wed, 16 Nov 2011, Alexander Motin wrote:
>
>> Hi.
>>
>> On 11/16/11 08:43, Bjoern A. Zeeb wrote:
>>> we have seen this or a very similar panic for about 1 year now once in
>>> a while and I think I reported it before; this is FreeBSD as guest on
>>> vm
On Wed, 16 Nov 2011, Alexander Motin wrote:
Hi.
On 11/16/11 08:43, Bjoern A. Zeeb wrote:
we have seen this or a very similar panic for about 1 year now once in
a while and I think I reported it before; this is FreeBSD as guest on
vmware. Seems it was a double panic this time. Could someone
Hi.
On 11/16/11 08:43, Bjoern A. Zeeb wrote:
> we have seen this or a very similar panic for about 1 year now once in
> a while and I think I reported it before; this is FreeBSD as guest on
> vmware. Seems it was a double panic this time. Could someone please
> see what's going on there?It
ot doing anything with the cdrom. As a workaround, I now
remove the cdrom device from vmware instances.
> vmware. Seems it was a double panic this time. Could someone please
> see what's going on there?It was on 8.x-STABLE in the past and this
> is 8.2-RELEASE-p4.
>
Hey,
we have seen this or a very similar panic for about 1 year now once in
a while and I think I reported it before; this is FreeBSD as guest on
vmware. Seems it was a double panic this time. Could someone please
see what's going on there?It was on 8.x-STABLE in the past and this
is 8.2-
i think, usermount worked only with user owned and writable dir-s, example:
mkdir ~/cdrom
mount_cd9660 /dev/acd0 ~/cdrom
On 12/28/09, Johan Hendriks wrote:
> Hello all
> I am on 8.0-STABLE now, and using the ahci driver.
>
> All works likei t should, but i can not mount my cdrom
Hello all
I am on 8.0-STABLE now, and using the ahci driver.
All works likei t should, but i can not mount my cdrom anymore as a
regular user.
i have this in my sysctl.conf
vfs.usermount=1
my /etc/devfs.conf looks like this
#CDROM_BURNER permissions
permacd00666
#permacd1
me hardware as my other thread.
> > > > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm
> > > >
> > > > [using 2Gb RAM and SATA in legacy mode]
> > > >
> > > > I'd like to focus only on making the CDROM boot complete.
> &g
me hardware as my other thread.
> > > > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm
> > > >
> > > > [using 2Gb RAM and SATA in legacy mode]
> > > >
> > > > I'd like to focus only on making the CDROM boot complete.
> &g
em/1U/5015/SYS-5015B-MT.cfm
> > >
> > > [using 2Gb RAM and SATA in legacy mode]
> > >
> > > I'd like to focus only on making the CDROM boot complete.
> > >
> > > Summary: hangs just after the CPUs are launched.
> > >
> >
y mode]
> >
> > I'd like to focus only on making the CDROM boot complete.
> >
> > Summary: hangs just after the CPUs are launched.
> >
> > 6.2-RELEASE works okay, no AHCI support
> > 6.3-RELEASE works okay
> > 7.0-RELEASE hangs
> > 7.0-STABLE-
On Tue, Jul 22, 2008 at 05:27:52PM +0100, ian j hart wrote:
> Same hardware as my other thread.
> http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm
>
> [using 2Gb RAM and SATA in legacy mode]
>
> I'd like to focus only on making the CDROM boot complete.
&
Same hardware as my other thread.
http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm
[using 2Gb RAM and SATA in legacy mode]
I'd like to focus only on making the CDROM boot complete.
Summary: hangs just after the CPUs are launched.
6.2-RELEASE works okay, no AHCI su
of the canonical way to find them..
> Easiest would be to look in /dev I guess)
As part of this I wrote a patch that teaches sysinstall how to load
install.cfg from a CDROM or DOS partition (eg USB stick).
I just submitted a PR but haven't got a number yet, here is the patch..
http://www.g
On Friday 01 June 2007 04:58, Vivek Khera wrote:
> On May 31, 2007, at 1:49 AM, Daniel O'Connor wrote:
> > Thanks so much, now I can have an automated install on a USB stick
> > :)
>
> please, please, please share the recipes to make this. I would love
> to omit CD rom drives on my future systems
On May 31, 2007, at 1:49 AM, Daniel O'Connor wrote:
Thanks so much, now I can have an automated install on a USB stick :)
please, please, please share the recipes to make this. I would love
to omit CD rom drives on my future systems as the only thing i ever
use them for is install.
als
On Thursday 31 May 2007 09:39, Adriaan wrote:
> "Because other OS's run the BIOS in real mode, and we run it in vm86
> mode and we don't emulate enough instructions in vm86 mode for the
> Compaq/HP BIOS."
>
> In another post
> http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/0287
>7
On Thursday 31 May 2007 12:33, Daniel O'Connor wrote:
> On Wednesday 30 May 2007 22:52, Kostik Belousov wrote:
> > > -
> > > int=000d ...
> > > ...
> > > BTX halted
> >
> > You boot from the hard drive, right ? Then, boot2 shall be changed
> > too, since it uses btx. You should apply the patch,
On Wednesday 30 May 2007 22:52, Kostik Belousov wrote:
> >
> > -
> > int=000d ...
> > ...
> > BTX halted
>
> You boot from the hard drive, right ? Then, boot2 shall be changed
> too, since it uses btx. You should apply the patch, build the world,
> then install _both_ new boot blocks using bsdl
On 5/30/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
int=000d ...
...
BTX halted
According to John Baldwin in
http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028774.html
:
"Because other OS's run the BIOS in real mode, and we run it in vm86 mode and
we don't emulate eno
On Wednesday 30 May 2007 22:08, Kostik Belousov wrote:
> > The second one is more accurate as I didn't copy it from a blurry
> > photo :)
>
> Could you, please, show the complete output from the boot, including
> btx banner ?
That's it..
With my i965 system I don't appear to be able to get it to
> Alas I still get a BTX halted after replacing loader with one from
> that URL :(
> int=000d err= efl=00030002 eip=2aca
> eax=0900 ebx=55aa ecx= edx=0180
> esi= edi= ebp=03f0 esp=03da
> cs=f000 ds=9e02 es=1400fs= gs=00
On Monday 28 May 2007 13:35, Daniel O'Connor wrote:
> > Yes, there is also a loader/pxeboot in the same directory.
> > As kib@ told me, do not install this loader on your disk
> > which may destroy your data.
>
> I see the binaries, I was thinking of trying one with a USB flash
> boot disk, I'll un
Rong-en Fan wrote:
On 5/28/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
Daniel O'Connor wrote:
>> kib@ has real mode BTX code which appears to work with affected
>> systems of mine, however, the code has not yet made it into CVS. I
>> spliced it into a 6.2 miniboot ISO and it worked.
>
> Ooh a
On 5/28/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote:
Daniel O'Connor wrote:
>> kib@ has real mode BTX code which appears to work with affected
>> systems of mine, however, the code has not yet made it into CVS. I
>> spliced it into a 6.2 miniboot ISO and it worked.
>
> Ooh ahh, please sir, can
Daniel O'Connor wrote:
kib@ has real mode BTX code which appears to work with affected
systems of mine, however, the code has not yet made it into CVS. I
spliced it into a 6.2 miniboot ISO and it worked.
Ooh ahh, please sir, can I have some more^Wit? :)
I did some googling.. Is this the patch
On 5/26/07, Bruce M. Simpson <[EMAIL PROTECTED]> wrote:
Daniel O'Connor wrote:
>
> I believe this is most likely this issue...
> http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t3047441.html
>
> Alas no solution yet as far as I am aware :(
>
Forgot to Cc: my reply to the list:
k
On Saturday 26 May 2007 22:00, Bruce M. Simpson wrote:
> Daniel O'Connor wrote:
> > I believe this is most likely this issue...
> > http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t30
> >47441.html
> >
> > Alas no solution yet as far as I am aware :(
>
> Forgot to Cc: my reply to th
Daniel O'Connor wrote:
I believe this is most likely this issue...
http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t3047441.html
Alas no solution yet as far as I am aware :(
Forgot to Cc: my reply to the list:
kib@ has real mode BTX code which appears to work with affected
On Friday 25 May 2007 16:39, Andrei Kolu wrote:
> int=000d err= efl=00030002 eip=2abf
> eax=0300 ebx= ecx=0001 edx=009f
> esi=000c edi= ebp= esp=03f6
> cs=f000 ds=3fca es=3fac fs= gs= ss=9e3c
> cs:eip=23 0f 01 16 0c 2c 0f 20-c0 0c
Bootloader gave me this error message:
---
BTX loader 1.00 BTX version is 1.01
Consoles: internal video/keyboard
_
int=000d err= efl=00030002 eip=2abf
eax=0300 ebx= ecx=0001 edx=009f
esi=000c edi=000
and report results.
CAUTION: Do not install boot2 or loader on your harddrive, code had very
little exposure and may cause you machine to become unbootable.
Hi Konstantin,
Thanks this worked. I have another question though. I mounted the distro
1 cd and
cd to /cdrom and did
tar cSf - . |(cd
Konstantin Belousov wrote:
On Thu, Apr 05, 2007 at 09:21:05AM -0400, Stephen Clark wrote:
Hello List,
When I boot linux from my usb cdrom it works great
- but when I try the
6.1 release media
it fails - BTX crashes.
I found a listed bug kern/85257 that seems to be
the same problem. Had
Hello List,
When I boot linux from my usb cdrom it works great
- but when I try the
6.1 release media
it fails - BTX crashes.
I found a listed bug kern/85257 that seems to be
the same problem. Had
this been resolved?
Will it be resolved?
Thanks,
Steve
--
"They that give up esse
hi all
I have got a little problem- after rebuilding the kernel my CD ROM doesn't work. I
thought maybe I had commented something necessary (like CD9660), but even if I change
ident and filename from GENERIC to something other after mount /cdrom I get this error:
"cd9660: /dev/acd
>9660: /dev/acd0c: Device not configured
Did you remake the devices? (cd /dev && sh MAKEDEV acd0)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
When ever I try to burn cds, I get the following...
burncd: open(/dev/acd1c): Device not configured
When I try to mount cds I get a similar errorcd
9660: /dev/acd0c: Device not configured
The devices are detected by the kernel, but they won't
work. dmesg says...
acd0: CDROM at ata0-
If I do a "boot -verbose" at the ok prompt when booting, the cdrom is
detected and works fine! (And I do not get the ATA identify retries
exceeded error).
If I do not boot with -verbose, the cdrom does not work.
What gives?
Thanks for any and all i
Doug wrote:
> --- Kevin Oberman <[EMAIL PROTECTED]> wrote:
>
>>Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to
>>re-create them? The new ATA drivers require this as the minor mode
>>must change. If you did a mergemaster after any upgrade, this should
>>have been taken care
--- Kevin Oberman <[EMAIL PROTECTED]> wrote:
> Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to
> re-create them? The new ATA drivers require this as the minor mode
> must change. If you did a mergemaster after any upgrade, this should
> have been taken care of.
>
> > ls -l /de
Doug,
Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to
re-create them? The new ATA drivers require this as the minor mode
must change. If you did a mergemaster after any upgrade, this should
have been taken care of.
> ls -l /dev/acd*
crw-r- 4 root operator 117, 0 A
I just upgraded from 4.5 (off the CD Release) to 4.6 (off the CD
release) and yadda yadda yadda ATA CDROM fails per the Errata (big read
timeout, etc).
The workaround DOESN'T
/home/dob: cat /boot/loader.conf
# -- sysinstall generated deltas -- #
userconfig_script_load="YES"
hw
using vn device).
Russian description is available here:
http://sysoev.ru/freebsd/vmware_cd_image.html
In English, short:
After appling of patch you need rebuild vnconfig and kernel.
vnconfig will get new options - '-s cdrom':
vnconfig -s cdrom -c vn0c image.iso
After configuring vn dev
Hello.
I have seen a few threads with regards to having a problem with
ATAPI cdroms, on 4.6.rcx, and I also have the same problems..
I have several different hardware configurations that I have tested this
with, as well as versions..
4.5 was the last version that worked across the board..
4.6 RC2
On Sat, Apr 27, 2002 at 04:32:18PM -0400, Scott M. Nolde wrote:
> Ian Dowse([EMAIL PROTECTED])@2002.04.27 21:28:11 +:
> > >Interesting, because in the /dev/MAKEDEV script is this concerning the
> > >minor number:
> > ...
> > >... which is exactly what I have. What's in your MAKEDEV? When/why
Ian Dowse([EMAIL PROTECTED])@2002.04.27 21:28:11 +:
> >Interesting, because in the /dev/MAKEDEV script is this concerning the
> >minor number:
> ...
> >... which is exactly what I have. What's in your MAKEDEV? When/why did
> >the "+ 2" get in there if it's incorrect?
>
> You have a stale MA
>Interesting, because in the /dev/MAKEDEV script is this concerning the
>minor number:
...
>... which is exactly what I have. What's in your MAKEDEV? When/why did
>the "+ 2" get in there if it's incorrect?
You have a stale MAKEDEV. You need at least revision 1.243.2.45
(March 18th) to pick up t
Ian Dowse([EMAIL PROTECTED])@2002.04.27 20:26:40 +:
> In message <[EMAIL PROTECTED]>, "Scott M. Nolde" writes:
> >As you can see, acd0 and acd1 are recognized properly by the system. I
> >even remade the devices with /dev/MAKEDEV to no avail:
> >crw-r- 2 root operator 117, 0 Apr 26 2
Ian Dowse([EMAIL PROTECTED])@2002.04.27 20:26:40 +:
> In message <[EMAIL PROTECTED]>, "Scott M. Nolde" writes:
> >As you can see, acd0 and acd1 are recognized properly by the system. I
> >even remade the devices with /dev/MAKEDEV to no avail:
> >crw-r- 2 root operator 117, 0 Apr 26 2
In message <[EMAIL PROTECTED]>, "Scott M. Nolde" writes:
>As you can see, acd0 and acd1 are recognized properly by the system. I
>even remade the devices with /dev/MAKEDEV to no avail:
>crw-r- 2 root operator 117, 0 Apr 26 22:45 /dev/acd0a
>crw-r- 2 root operator 117, 2 Apr 26 2
Hongbo Li([EMAIL PROTECTED])@2002.04.27 02:05:31 +:
> Today I updated src and compiled the kernel using the
> old kernel config file. After rebooting the box, I
> found the cdrom can't be mounted. The message is:
>
> cd9660: /dev/acd0c: Device not configured
>
&
On Fri, Mar 15, 2002 at 13:11:43 -0500, Normand Leclerc wrote:
> This is a SCSI drive. I am wondering, why would SCSI be different from
> IDE in that matter?
The drivers are different, and the SCSI driver uses the disk layer. The
ATAPI cd driver does not.
Please send full dmesg information, in
CTED]
> Subject: Re: CDROM sector size on 4.5
>
> On Thu, Mar 14, 2002 at 13:28:38 -0500, Normand Leclerc wrote:
> > I was wondering if the CDROM sector size detection code has
changed.
> > I own a CDRW with a jumper that let me select the sector size (2048
or
> > 5
oblem when trying to mount one of my CDROMs. I looked around on the
>>>archives and didn't really see an answer. The motherboard sees the
>>>CDROM, and the boot probe seems to detect it correctly too.
>>>
>>>mount /cdrom complains:
>>>cd9660: /dev/
OK, I take it back. I don't think it is a signed versus unsigned
issue, though I still think it is dangerous the way atapi_read
mixes them.
I've been trying to follow the two pr's (kern/31530 and kern/31460)
to see if the panics they're getting were related to the problem I
reported earlier.
OK, I take it back. I don't think it is a signed versus unsigned
issue, though I still think it is dangerous the way atapi_read
mixes them.
I've been trying to follow the two pr's (kern/31530 and kern/31460)
to see if the panics they're getting were related to the problem I
reported earlier. I
Hi!
On Thu, Nov 15, 2001 at 12:30:27AM +0100, Dirk Froemberg wrote:
> I build an CDROM image with a boot image containing a GENERIC kernel
> and an "ordinary" FreeBSD-4.4-STABLE installation.
>
> After booting the kernel I get the "mountroot> " prompt.
Warner Losh <[EMAIL PROTECTED]> wrote:
> Yes. It appears The Daemon News is going to produce CDROM using the
> official iso images that the project will release. The posting was at
> great pains to say they are not associated with WindRiver. I expect
> that others may do
In message <[EMAIL PROTECTED]> Bruce Burden writes:
: >
: > I'm getting a No such file or directory when I try to mount a CDROM with
: > 4-STABLE. I've seen some stuff about this and have tried as many of the
: > suggestions as I can, but no joy.
: >
: Is yo
= 0
1 slots found
I just finished resyncing and making 4-STABLE and I'm seeing the same
behaviour...
mount /cdrom still gives the same error :(
david
> AFAIK it's 16-bit. In fact after rebooting once it was identified as a
> NinjaATA card, which is 16-bit.
>
> david
> &
It seems Andrew Reilly wrote:
>
> Nov 5 12:35:40 gurney /kernel: FreeBSD 4.2-BETA #0: Sun Nov 5 10:15:56 EST 200
> Nov 14 14:39:32 gurney /kernel: FreeBSD 4.2-BETA #0: Mon Nov 13 14:15:20 EST 200
Uhm, seems to me that this is the same source being built or what ??
Upgrade to at least 4.2-RE
5 12:35:41 gurney /kernel: ata0: at 0x1f0 irq 14 on atapci0
Nov 5 12:35:41 gurney /kernel: ata1: at 0x170 irq 15 on atapci0
[...]
Nov 5 12:35:41 gurney /kernel: ad0: 6149MB [13328/15/
63] at ata0-master UDMA33
Nov 5 12:35:41 gurney /kernel: ad1: 6149MB [13328/15/
63] at ata0-slave UDMA33
Nov
> "Soren" == Soren Schmidt <[EMAIL PROTECTED]> writes:
Soren> Oh, you shoudl definitly try the new patch diff-4.2-1...
Soren> -Søren
It definitely solved the case, thanks a lot :)).
Any chance of integration into the tree before 4.2-R ?
Regards
Eric Masson
--
Progress (n) : What le
Ralf Meyer wrote:
>
> Hej all,
>
> after rebuilding world and kernel /stand/sysinstall fails to access my
> CDROM device with the following console messages:
>
> ata0-slave: too many segments in DMA table
> acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 erro
Hej all,
after rebuilding world and kernel /stand/sysinstall fails to access my
CDROM device with the following console messages:
ata0-slave: too many segments in DMA table
acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=02
If I mount the device manually everything works. The old
s
device ata0at isa? port IO_WD1 irq 14
#device ata1at isa? port IO_WD2 irq 15
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
device atapifd
I see unrecovered SCSI parity errors under both 3.4- and 4.0 FBSD.
I checked cables, connectors and terminations and all seem to be okay.
There are other devices on this scsi bus but only cdrom shows errors.
It looks like my UltraPlex PX 32CS is at fault. Audio works fine (even
while as scsi
In message <[EMAIL PROTECTED]>, ian j hart
writes:
> I'm used to doing this
>
> #dd if=/dev/acd0c of=image
>
> [followed by vnconfig, mount, share using samba]
>
> This fails under 4.0-STABLE. The error message is Bad address. No data
> is transfered. This is reprodusable on three machines. Al
Gregory Bond wrote in list.freebsd-stable:
> > wdc0 ist the IDE controller, not the CD-ROM drive.
> > Look for acd0 (ATAPI CD-ROM drive) in your boot messages.
> > Type this command: dmesg | grep acd
>
> Depending on the vintage of his system, the ATAPI CD driver and corresponding
> /dev/
82 matches
Mail list logo
