D. Rock schrieb:
Soren Schmidt schrieb:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hi,
again no luck. Same problem persists, the devices
looks like and my problem with sil 3112 which still exist...
- Original Message -
From: Daniel Rock
To: Soren Schmidt
Cc: [EMAIL PROTECTED]
Sent: Wednesday, September 03, 2003 16:15 PM
Subject: Re: ATAng probe updated please test
Just an additional notice: Booting in PIO mode
It seems Daniel Rock wrote:
Just an additional notice: Booting in PIO mode (by setting
hw.ata.ata_dma=0 in /boot/loader.conf):
[...]
GEOM: create disk ad0 dp=0xc10b3b70
ad0: 9671MB IBM-DTTA-351010 [20960/15/63] at ata0-master PIO4
GEOM: create disk ad1 dp=0xc10b3470
ad1: 1221MB Seagate
On Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hello,
The new stuff
On Tue, Sep 02, 2003 at 10:23:02AM +0200, Jan Srzednicki wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hello,
The new
;), Mon, Sep 01, 2003 at 01:16:00PM +0200, Soren Schmidt said that
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
Soren Schmidt wrote on Monday, September 01, 2003 6:16 AM
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
I cvsupped after I saw this
Soren Schmidt schrieb:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Hi,
again no luck. Same problem persists, the devices got probed
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
___
[EMAIL PROTECTED] mailing
Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
Mine is working perfectly now (see below). With atapicam
Matt wrote:
Soren Schmidt wrote:
I've gone over the probe code once again.
Please test, and in case it fails to detect or misdetects anything,
mail me the output of dmesg from a verbose boot, and state what
devices actually are there.
Thanks!
-Søren
Mine is working perfectly now (see below).
I've gone over the probe code once again.
I upgraded, and now my DVDROM (ata1-slave) is working again, but
my Plextor 8/4/32A CDRW (ata1-master) still won't probe correctly.
atacontrol list appears to send out the same message as before.
dmesg atacontrol list output attached.
Andrew Lankford
I upgraded, and now my DVDROM (ata1-slave) is working again, but
my Plextor 8/4/32A CDRW (ata1-master) still won't probe correctly.
atacontrol list appears to send out the same message as before.
dmesg atacontrol list output attached.
Andrew Lankford
Crap, I attached the wrong file (an
13 matches
Mail list logo
