fine before the ATAng code got changed.
Please try this simple patch:
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-lowlevel.c,v
retrieving revision 1.8
diff -u -r1.8 ata-lowlevel.c
--- ata-lowlevel.c 1 Sep 2003
On Mon, Sep 08, 2003 at 05:30:28AM +0200, YazzY wrote:
Isn't the ATAng code great?
It makes it affordable to get a 9007199253773098MB CF for the price of a
32 MB card.
Now I am taking backups of the internet on it.
:)
The old ATA code (in -stable) can only manage to expand my 3102MB disk
. And as I said,
everything worked fine before the ATAng code got changed.
Please try this simple patch:
Forget that, wrong patch, here goes the right one:
Index: ata-lowlevel.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata
It seems Soren Schmidt wrote:
Forget that, wrong patch, here goes the right one:
DOH! things are not going weel this morning, this patch should be right:
Index: ata-lowlevel.c
===
RCS file:
...
Anyway, this bit of dmesg does not look healthy to me. And as I said,
everything worked fine before the ATAng code got changed.
Please try this simple patch:
Forget that, wrong patch, here goes the right one:
Index: ata-lowlevel.c
It seems that the same bug that initially stopped ataraid working
at all is there with rebuild:
kompak# atacontrol rebuild 0
ad4: FAILURE - oversized DMA transfer attempted 131072 65536
ad4: setting up DMA failed
kompak# atacontrol status 0
ar0: ATA RAID1 subdisks: ad4 ad8 status: REBUILDING 0%
It seems Petri Helenius wrote:
It seems that the same bug that initially stopped ataraid working
at all is there with rebuild:
kompak# atacontrol rebuild 0
ad4: FAILURE - oversized DMA transfer attempted 131072 65536
ad4: setting up DMA failed
kompak# atacontrol status 0
ar0: ATA RAID1
YazzY == YazzY [EMAIL PROTECTED] writes:
YazzY Isn't the ATAng code great? It makes it affordable to get a
YazzY 9007199253773098MB CF for the price of a 32 MB card. Now I am
YazzY taking backups of the internet on it. :)
Pocket internet... now there's a product.
Dave
.
But in this case, the detected ad3 doesn't exist. The machine is a
laptop with a drive on channel 0 and a DVD+R on channel 1. If the
DVD is removed, the phantom ad3 doesn't show up, either.
... so that issue with ATAng is unresolved.
Soren Uhm, I'm working on finding the real problem
It seems David Gilbert wrote:
Soren Uhm, I'm working on finding the real problem, and I'd like that
Soren to be the solution. However the above may be a good workaround
Soren for those bitten by this...
Well... is it not possible for malicious hardware to claim to have
zero blocks (by
With a fresh checkout of last night's -current, I cannot boot my laptop.
ATAFD panics the box by reusing freed memory. I do not have a floppy
drive in the laptop and when I do, it's a legacy floppy, not atapi. Here
are the messages:
[normal ad0/acd0 probe message]
afd0: timeout waiting for
It seems Nate Lawson wrote:
With a fresh checkout of last night's -current, I cannot boot my laptop.
ATAFD panics the box by reusing freed memory. I do not have a floppy
drive in the laptop and when I do, it's a legacy floppy, not atapi. Here
are the messages:
[normal ad0/acd0 probe
My recent kernel still got the panic when I tried to do CVSup.
# cvsup -g -z -L 2 /home/yosimoto/mk/daemon-supfile 21 | tee
/var/tmp/log/cvsup.`date +%m%d.%H.%M.%S`;
Parsing supfile /home/yosimoto/mk/daemon-supfile
Connecting to cvsup.jp.FreeBSD.org
Connected to cvsup.jp.FreeBSD.org
Server
It seems Christian Laursen wrote:
Since ATAng was comitted I've had problems with the disk on
which my root filesystem is residing.
If I choose 'Safe mode' in the boot menu, it will boot but
it is then running with DMA and write caching disabled.
This is the dmesg output from a failed
On Sun, 7 Sep 2003, Mark Dixon wrote:
I'm not sure if this is a known problem, but I don't see any references
to it. I've gone from 5.1-RELEASE to todays CURRENT to try to get rid of
a different panic (no news on that yet), but I have hit this one.
If I boot my system with no floppy in the
Hi,
Since the ATAng import, I can't use the cd ripper cdparanoia
(audio/cdparanoia) with my IDE CD-ROM drive. When I direct cdparanoia to
device /dev/acd0, it will exit with the message
006: Could not read any data from drive
Cdparanoia could not find a way to read audio from this drive
Hi.
The latest changes in ATAng code made it impossible to use my CF cards.
I have a few of them which previously worked just fine.
Now, each time I put one to my laptop's PCMCIA slot i get following errors:
pccard0: Allocation failed for cfe 0
ata2: CL ATA FLASH CARD LEXAR TIDALWV at port
On Sun, 7 Sep 2003, Martin Jessa wrote:
The latest changes in ATAng code made it impossible to use my CF cards.
I have a few of them which previously worked just fine.
Now, each time I put one to my laptop's PCMCIA slot i get following errors:
Looks like it mounted fine to me; some
On Sun, 7 Sep 2003, Doug White wrote:
On Sun, 7 Sep 2003, Martin Jessa wrote:
The latest changes in ATAng code made it impossible to use my CF cards.
I have a few of them which previously worked just fine.
Now, each time I put one to my laptop's PCMCIA slot i get following errors:
Looks
Soren Schmidt [EMAIL PROTECTED] writes:
I have one other report of problems on the older Acer chips,
I must have screwed something up there. I'll dig out my
old ASUS board and see what I can find out...
Great, I'll be happy to test stuff.
Bortset fra det kunne vi da snakke dansk ku' vi ikke
I thought I was going to miss out on the ATAng issues...
I use a SanDisk CompactFlash PC Card Adapter to read my digital camera
pictures. It worked fine before ATAng. Now I get:
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
ata2: spurious interrupt - status=0xff error=0x00
On Sun, 7 Sep 2003, Scott Lambert wrote:
I thought I was going to miss out on the ATAng issues...
I use a SanDisk CompactFlash PC Card Adapter to read my digital camera
pictures. It worked fine before ATAng. Now I get:
ata2: spurious interrupt - status=0xff error=0x00 reason=0x00
ata2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To all the english speaking on this list, I'm sorry for this small
internal joke - but when I observe two danes thinking they are the only
ones to understand their language, I need to remind them otherwise ;)
Si for all del ikke noe dritt om meg, for
Mark == Mark Dixon [EMAIL PROTECTED] writes:
Mark Hi, I'm not sure if this is a known problem, but I don't see any
Mark references to it. I've gone from 5.1-RELEASE to todays CURRENT
Mark to try to get rid of a different panic (no news on that yet),
Mark but I have hit this one.
Mark If I boot
Si for all del ikke noe dritt om meg, for jeg forst=E5r dere ;
Soeren cyning,ATAng das blinkenleiten dryhten,
beorna beahgifa, his broþor eac,
Fred,ealdorlangne tir
geslogon æt sæccesweorda ecgum
ymbe [EMAIL PROTECTED] Bordweal clufan,
heowan heaþolindehamora lafan,
afaran Eadweardes,swa him
on channel 0 and a DVD+R on channel 1. If the DVD
is removed, the phantom ad3 doesn't show up, either.
... so that issue with ATAng is unresolved.
Dave.
--
|David Gilbert, Independent Contractor. | Two things can
Hi.
It can be mounted when I boot the laptop and do not take the card out of
the slot.
If I eject it and then put it back in, I cannot mount it or dd files to
it anymore...
Anyway, this bit of dmesg does not look healthy to me. And as I said,
everything worked fine before the ATAng code got
In message: [EMAIL PROTECTED]
Bruce Evans [EMAIL PROTECTED] writes:
: On Sun, 7 Sep 2003, Doug White wrote:
: On Sun, 7 Sep 2003, Martin Jessa wrote:
: ad4: 9007199253773098MB
Isn't the ATAng code great?
It makes it affordable to get a 9007199253773098MB CF for the price of a
32 MB card.
Now I am taking backups of the internet on it.
:)
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Bruce Evans [EMAIL PROTECTED] writes:
: On Sun, 7 Sep 2003, Doug
On Sun, Sep 07, 2003 at 01:59:55PM +0200, Arjan van Leeuwen wrote:
Hi,
Since the ATAng import, I can't use the cd ripper cdparanoia
(audio/cdparanoia) with my IDE CD-ROM drive. When I direct cdparanoia to
device /dev/acd0, it will exit with the message
006: Could not read any data from
On Sun, Sep 07, 2003 at 12:18:56AM +, Mark Dixon wrote:
Hi,
I'm not sure if this is a known problem, but I don't see any references
to it. I've gone from 5.1-RELEASE to todays CURRENT to try to get rid of
a different panic (no news on that yet), but I have hit this one.
If I boot my
Hi,
after recent ATAng changes, cdcontrol close stopped working
with my CD-ROM drive. It used to close the tray. It works with -f
/dev/cd0 but not with /dev/acd0. cdcontrol eject still works fine.
Relevant dmesg parts:
atapci0: VIA 8235 UDMA133 controller port 0xfc00-0xfc0f at device 17.1
Since ATAng was comitted I've had problems with the disk on
which my root filesystem is residing.
If I choose 'Safe mode' in the boot menu, it will boot but
it is then running with DMA and write caching disabled.
This is the dmesg output from a failed boot. If anything
else is needed to figure
On Sat, 6 Sep 2003, Pav Lucistnik wrote:
after recent ATAng changes, cdcontrol close stopped working
with my CD-ROM drive. It used to close the tray. It works with -f
/dev/cd0 but not with /dev/acd0. cdcontrol eject still works fine.
I use the following fix:
%%%
Index: atapi-cd.c
Endianness-related cleanups in ATAng broke detection of the PIO mode capabilty
of old drives by getting the bytes in the retired_piomode word backwards.
%%%
Index: ata-all.c
===
RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v
On Thu, Sep 04, 2003 at 07:59:36AM -0400, Bryan Liesner wrote:
On Wed, 3 Sep 2003, Terry Lambert wrote:
Bryan Liesner wrote:
On Wed, 3 Sep 2003, Martin wrote:
If you notice that your CD-R label looks strange and if you need
the data, you should backup it fast.
No, we're
Hi,
I'm not sure if this is a known problem, but I don't see any references
to it. I've gone from 5.1-RELEASE to todays CURRENT to try to get rid of
a different panic (no news on that yet), but I have hit this one.
If I boot my system with no floppy in the LS-120, the system panics
where
Bryan Liesner wrote:
On Wed, 3 Sep 2003, Martin wrote:
If you notice that your CD-R label looks strange and if you need
the data, you should backup it fast.
No, we're talking about brand new, factory pressed, audio CDs.
Are they copy protected?
The way you can tell is if you try to do
Sean Kelly wrote:
On Wed, Sep 03, 2003 at 07:11:53AM -0400, Bryan Liesner wrote:
No, we're talking about brand new, factory pressed, audio CDs.
And on top of that, my Windows XP machine's DVD-ROM was able to raed my
*commercial audio CDs* perfectly while the CD-RW in the FreeBSD machine was
On Wed, 3 Sep 2003, Terry Lambert wrote:
Bryan Liesner wrote:
On Wed, 3 Sep 2003, Martin wrote:
If you notice that your CD-R label looks strange and if you need
the data, you should backup it fast.
No, we're talking about brand new, factory pressed, audio CDs.
Are they copy
Soren Schmidt [EMAIL PROTECTED] writes:
Can you play those discs in your cd-rw drive ?
Is this a useful test after all? Most drives go down to 1x playing
audio, which is nowhere near 52x or what's current nowadays.
--
Matthias Andree
Encrypt your mail: my GnuPG key ID is 0x052E7D95
Hi,
Lars Eggert wrote:
Soren Schmidt wrote:
ATAng has just been committed. You need to make world after this update
as atacontrol etc needs to pick up the changes.
Funky boot messages, but the system is usable after. This is with
today's -current:
atapci0: Intel ICH2 UDMA100 controller port
On Wed, Sep 03, 2003 at 07:11:53AM -0400, Bryan Liesner wrote:
On Wed, 3 Sep 2003, Martin wrote:
Am Di, 2003-09-02 um 18.56 schrieb Bryan Liesner:
dd then gets slower and slower until it seems to grind to a halt.
I have this problems everywhere (not only ATAng), if I'm trying to
read
It seems Sean Kelly wrote:
I have this problems everywhere (not only ATAng), if I'm trying to
read some of my really old CD-Rs. You should know that they are aging.
Check the surface of the CD-R (the surface is actually the label!).
On few CD-Rs which have been in my car the label
On Wed, 3 Sep 2003, Soren Schmidt wrote:
No, we're talking about brand new, factory pressed, audio CDs.
And on top of that, my Windows XP machine's DVD-ROM was able to raed my
*commercial audio CDs* perfectly while the CD-RW in the FreeBSD machine was
only able to read about 95% of the
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
Hello,
shortly after last sunday, ATAng broke for me with atapicam
enabled; on a Toshiba Satelite 6000 Notebook; first
versions of ATAng worked flawlessly with atapicam, never
tested without.
Things broke when the newer probe-code for CD-slaves etc was
introduced.
Now it hangs as follows
Sometimes when booting after a non-graceful shutdown, the harddisk and cdrom
drives cause the bootup to hang while probing for them. Sometimes is finds
the ad0, but then hangs when it gets to acd0, sometimes it hangs at ad0 too.
I then have to boot to a pre-ATAng kernel to continue
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get burned...
ata2-master: pio=0x0c wdma=0x22 udma=0x45
I also noticed that earlier ATAng spits out these messages; (cutpasting boot -v
is a little tedious, but I can copy it all if it helps)
The err=0x01 caught my eye.
Pete
atapci0: Promise PDC20619 UDMA133 controller port
0x1080-0x10ff,0x1480-0x148f,0x1000-0x107f mem 0x4020-0x4021
It seems Petri Helenius wrote:
I also noticed that earlier ATAng spits out these messages; (cutpasting boot -v
is a little tedious, but I can copy it all if it helps)
The err=0x01 caught my eye.
Err=0x01 is actually OK Im' there signal from an ATA device :)
What I need to know
It seems Petri Helenius wrote:
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get burned...
Do you
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:
It seems Petri Helenius wrote:
ATAng does not seem to detect my RAID set, while ATAold boots it
fine, first boot -v with ATAng kernel and then ATAold.
Any ideas if raid configs should be compatible between them? Should
make sense that they are so people upgrading don't get
It seems Petri Helenius wrote:
Soren Schmidt wrote:
It seems Petri Helenius wrote: ATAng does not seem to detect my RAID set,
while ATAold boots itfine, first boot -v with ATAng kernel and then
ATAold.Any ideas if raid configs should be compatible between them?
Shouldmake sense
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
. Same results with DMA or PIO modes. Shorter
(40 minute) CDs make it through the process OK.
Soren's crdao 1.1.7 for ATAng also grinds to a halt when copying a cd.
--
=
= Bryan D. LiesnerLeezSoft Communications, Inc
set TIMEOUT messages and won't be able to kill the
current dd process. Same results with DMA or PIO modes. Shorter
(40 minute) CDs make it through the process OK.
Soren's crdao 1.1.7 for ATAng also grinds to a halt when copying a cd.
I saw this on ATAold as well, using cdparanoia, dd, dagrab
be able to kill the
current dd process. Same results with DMA or PIO modes. Shorter
(40 minute) CDs make it through the process OK.
Soren's crdao 1.1.7 for ATAng also grinds to a halt when copying a cd.
I saw this on ATAold as well, using cdparanoia, dd, dagrab, etc. I just
chalked it up
Soren Schmidt wrote:
Oh, that one :) fixed...
-Søren
Do you have an idea why my SMP system would crash under heavy load, like
mysql shutdown, just a reboot, etc.?
The system did not have any issues before ATAng was committed.
This is one of the panics;
Debugger(c03ded4a,100,c03f40e5
I have a machine that panics reliably within ten minutes of
operation with ATAng. It subsequently locks up, so I can't obtain
a dump, and I get a small amount of random filesystem corruption
upon rebooting. Everything was fine with ATAog.
I don't have a serial cable handy at the moment
Am Di, 2003-09-02 um 18.56 schrieb Bryan Liesner:
dd then gets slower and slower until it seems to grind to a halt.
I have this problems everywhere (not only ATAng), if I'm trying to
read some of my really old CD-Rs. You should know that they are aging.
Check the surface of the CD-R
On Sun, Aug 31, 2003 at 04:57:57PM +0200, Soren Schmidt wrote:
It seems Jan Srzednicki wrote:
ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66
ad1: 39093MB FUJITSU MPG3409AH EF [79428/16/63] at ata0-slave UDMA66
ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR
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).
Latest ATAng kernel (without atapicam):
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #18: Mon Aug 25 19
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
Hi.
On Thu, 28 Aug 2003 21:57:24 -0700 (PDT)
Nate Lawson [EMAIL PROTECTED] wrote:
With today's ATAng, I can suspend my laptop but when I resume, the system
hangs. I'll try to get the exact dmesg with a serial console since
syscons gets screwed up by resuming (this is normal behavior
As reported to sos@, with a little extra debugging at the bottom...
---
I was playing with atacontrol reinit'ing all of the channels that are
installed on my machine, when I accidentally tried to reinit channel '4',
which clearly doesn't exist. Here's what showed up at the serial
which drive gets detected. But I could not get them both working at one
time, it always detected just one.
Anyway, after some massive disk IO (installworld mergemaster) and
reboot, syncer decided to give up on one buffer. No idea, whether this
is ATAng feature, yet it hasn't been happening on ATAold
It seems Jan Srzednicki wrote:
ad0: 19546MB FUJITSU MPF3204AT [39714/16/63] at ata0-master UDMA66
ad1: 39093MB FUJITSU MPG3409AH EF [79428/16/63] at ata0-slave UDMA66
ata1-slave: FAILURE - ATA_IDENTIFY status=51READY,DSC,ERROR
error=4ABORTED
acd0: CDROM CD-540E at ata1-master UDMA33
cd0 at
the atapicam option.
Atapicam worked fine prior to ATAng.
Strange. No messages on the system console?
Well, I did a fresh cvsup, re-enabled the atapicam bits in my kernel
config, rebuilt/reinstalled world and kernel. I rebooted and started a
Gnome session and starting nautilus did *not* cause
to
load nautilus. Nautilus loads fine after removing the atapicam
option. Atapicam worked fine prior to ATAng.
Strange. No messages on the system console?
Well, I did a fresh cvsup, re-enabled the atapicam bits in my kernel
config, rebuilt/reinstalled world and kernel. I rebooted
,
as of Aug 28, 2003; 11:00 PM CDT), my system locks up when
trying to load nautilus. Nautilus loads fine after removing the
atapicam option. Atapicam worked fine prior to ATAng.
Strange. No messages on the system console?
Well, I did a fresh cvsup, re-enabled the atapicam bits in my
Hi,
I have just cvsup'd this morning and built/installed a new world and kernel:
FreeBSD neo.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sat Aug 30 11:13:06
BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEO i386
I now have a new issue with ATAng that I didn't have last week when I
All,
A constant in one of the kernel header file seems to have been renamed. Change
PCIR_HEADERTYPE to PCIR_HDRTYPE in the NVIDIA code and all will be well.
I have tried this myself and all is well.
Cheers,
Brendon
___
[EMAIL PROTECTED] mailing list
On Sat, Aug 30, 2003 at 11:33:17AM +0100, Matt wrote:
Hi,
I now have a new issue with ATAng that I didn't have last week when I tried
ATAng. My CDRW is now not detected during probing. I get this message:
Aug 30 11:21:00 neo kernel: ad0: 76319MB ST380020A [155061/16/63] at
ata0-master
and Wendy
[EMAIL PROTECTED],[EMAIL PROTECTED]
Subject: Re: Fresh CVSUP, new ATAng problems and nvidia.ko compile issues
Date: Sat, 30 Aug 2003 16:54:58 +0200
On Saturday 30 August 2003 16:20, Brendon and Wendy wrote:
All,
A constant in one of the kernel header file seems to have been renamed
Le 2003-08-30, Glenn Johnson écrivait :
I guess I wrote that too soon, it just locked up again. This time
though, the machine rebooted after about 10 seconds so I could not get
to another machine to see if I could poke around.
If it rebooted, then maybe it panic'd. Do you have a kernel core
Did anybody try it? I've no success with this variant at all, cdrdao
stubbornly reports Cannot setup device cd0 no matter what :-( What
device/driver should I use for ATAPI burner (_NEC CD-RW NR-9100A) to make
use of ATAng backend?
On Wed, 27 Aug 2003, Soren Schmidt wrote:
I've put up cdrdao
retrieving revision 1.20
...snip...
When I have atapicam enabled in my kernel config (-current, as of
Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
nautilus. Nautilus loads fine after removing the atapicam option.
Atapicam worked fine prior to ATAng.
--
Glenn Johnson
[EMAIL
With today's ATAng, I can suspend my laptop but when I resume, the system
hangs. I'll try to get the exact dmesg with a serial console since
syscons gets screwed up by resuming (this is normal behavior). In any
case, my laptop hangs with the drive light on while trying to reset the
ata
Le 2003-08-29, Glenn Johnson écrivait :
When I have atapicam enabled in my kernel config (-current, as of
Aug 28, 2003; 11:00 PM CDT), my system locks up when trying to load
nautilus. Nautilus loads fine after removing the atapicam option.
Atapicam worked fine prior to ATAng.
Strange
the atapicam option.
Atapicam worked fine prior to ATAng.
Strange. No messages on the system console?
I do not really know. Since the keyboard locks up I can not switch to a
console. There was nothing written to the log file that I remember but
I should check that again tonight when I get home. I
Le 2003-08-29, Glenn Johnson écrivait :
console. There was nothing written to the log file that I remember but
I should check that again tonight when I get home. I will also try to
ssh in from another machine and see if the network is still up.
Yes. A serial console could also perhaps
to load
nautilus. Nautilus loads fine after removing the atapicam option.
Atapicam worked fine prior to ATAng.
Strange. No messages on the system console?
I do not really know. Since the keyboard locks up I can not switch to a
console. There was nothing written to the log file that I
,
as of Aug 28, 2003; 11:00 PM CDT), my system locks up when
trying to load nautilus. Nautilus loads fine after removing the
atapicam option. Atapicam worked fine prior to ATAng.
Strange. No messages on the system console?
I do not really know. Since the keyboard locks up I can
my cdrom drive, and got the following error messages, which is very
similar to the messages when trying to dma before ATAng:
Aug 26 22:09:34 littleguy kernel: acd0: WARNING - READ_CD recovered from
missing interrupt
Aug 26 22:09:34 littleguy kernel: acd0: WARNING - READ_CD UDMA ICRC error
to hw.ata.atapi_dma=1 in my /boot/loader.conf. After a reboot I tried to
access my cdrom drive, and got the following error messages, which is very
similar to the messages when trying to dma before ATAng:
Aug 26 22:09:34 littleguy kernel: acd0: WARNING - READ_CD recovered from
missing interrupt
Aug 26
drive. I changed the
hw.ata.atapi_dma=0
to hw.ata.atapi_dma=1 in my /boot/loader.conf. After a reboot I tried
to
access my cdrom drive, and got the following error messages, which is
very
similar to the messages when trying to dma before ATAng:
Aug 26 22:09:34 littleguy kernel: acd0
It seems Anish Mistry wrote:
it DMA was fixed for my CD/DVD combo drive. I changed the
hw.ata.atapi_dma=0
to hw.ata.atapi_dma=1 in my /boot/loader.conf. After a reboot I tried
There is no PIO fallback in ATAng (so far), if you know that your ATAPI
device doesn't do DMA why
My first try with ATAng on -CURRENT as of 18 hours ago ended up dying
around reboot. Other than this, it seems to work as expected.
I don't have WITNESS or INVARIANTS on this box, but I can recompile
kernel with them if it helps.
# reboot
Aug 28 09:24:35 rms21 reboot: rebooted by root
boot
I think I have reported this two days ago, but look like it wasn't gone through.
Here's my problem
that I still suffer with build world/kernel about three hours ago (i.e. Aug 28 12:00
UTC)
With the new world/kernel, I tried to pax a subdirectory to the RAID1 drive (two IBM
DLTA-307030
attached
On Thu, Aug 28, 2003 at 04:47:56PM +0200, Soren Schmidt wrote:
It seems Anish Mistry wrote:
it DMA was fixed for my CD/DVD combo drive. I changed the
hw.ata.atapi_dma=0
to hw.ata.atapi_dma=1 in my /boot/loader.conf. After a reboot I tried
There is no PIO fallback in ATAng (so
201 - 300 of 371 matches
Mail list logo
