It seems Matthew Dillon wrote:
Here's some more info. If the dd is stuck and systat -vm 1 is showing
no interrupts occuring on, for example, ahc2 (irq17), and I then do
something that causes an interrupt to occur on mux (irq19), which I
guess is ahc1, ahc2 then starts
It seems Dag-Erling Smorgrav wrote:
"Brian F. Feldman" [EMAIL PROTECTED] writes:
On 4 Jul 1999, Dag-Erling Smorgrav wrote:
Depends on your motherboard. Try to just disable UDMA66 first. If that
doesn't help, or if you have a "known bad" chipset (e.g. AcerLabs
Aladdin), disable UDMA
It seems Peter Wemm wrote:
Well, CAM ATAPI is "fairly" easy, the only problem being all the
little details that are different enough to make it non-trivial to
maintain. I once sat down and tried to get all the details on how
the CCB's where different, and decided that I wouldn't want to
It seems Mike Hoskins wrote:
and I just installed a Promise Ultra66. Here's my relevant kernel config
stuff (following LINT's example):
pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9
Thats the promise controller, try the ata driver instead an use the
following patch,
It seems Kazutaka YOKOTA wrote:
I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92
with 8 MB RAM a I have noticed that VESA module doesn't work with this
graphics card on my -current box - I can't use VESA_XXX console modes now.
Command kldstat says there is loaded
It seems Cejka Rudolf wrote:
Soren Schmidt wrote (1999/08/09):
It seems Kazutaka YOKOTA wrote:
There is a good possibility that the VESA BIOS extension for this card
is provided in a DOS TSR program and the VESA BIOS entry in the ROM
BIOS is just a stub. Such implementation
It seems Geoff Rehmet wrote:
Brian McGroarty writes :
In using the ATA driver, I'm unable to automatically mount a
partition on a master drive on the secondary controller. fsck
complains that device rwd2s1e isn't configured and exists.
Immediately mounting by hand works perfectly.
It seems Geoff Rehmet wrote:
Hmm,
My root device still lands up on "wd0" - even though my fstab has
the root filesystem on ad0s1a. I haven't looked at getting it to
use the ad dev entries for the root file system. (I'm assuming that
is still WIP.)
Our boot blocks/loader dont have the
It seems Thierry Herbelot wrote:
Soren Schmidt wrote:
[SNIP]
Have you tried putting disks on the UDMA66 channel ?? I think it
should work in upto WDMA mode now with the ata driver...
I have first to install 4.0 and from my wd2 (I've got a little help from
RNordier, I should make
It seems Mike Smith wrote:
Our boot blocks/loader dont have the needed computrons to use the
"ad" device name. However I have some patches to boot2 that allows
to boot off an ad root device, provided you dont use the loader, and
put the rigth boot string in boot.config.
This should now
It seems Nicolas Souchu wrote:
acd0: GCD-R520B/1.1 CDROM drive at ata0 as master
acd0: drive speed 0KB/sec
acd0: supported read types:
acd0: Mechanism: caddy
acd0: Medium: CD-ROM unknown medium
Any clue?
The drive was running flawlessly with the old wdc driver and with various
primary
It seems Nicolas Souchu wrote:
On Mon, Aug 23, 1999 at 08:27:15AM +0200, Soren Schmidt wrote:
It seems Nicolas Souchu wrote:
acd0: GCD-R520B/1.1 CDROM drive at ata0 as master
acd0: drive speed 0KB/sec
acd0: supported read types:
acd0: Mechanism: caddy
acd0: Medium: CD-ROM unknown
It seems Kevin Street wrote:
Two things I've noticed:
1) my cdrom delivers about 2M/s which is the same as before DMA. Is
the improvement only in cpu usage or should I be seeing a speed
improvement too?
Depends.. There are many factors involved here, using DMA only lowers
the CPU usage,
It seems Warner Losh wrote:
In message [EMAIL PROTECTED] Michael
Reifenberger writes:
: if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
The ep driver works in -current.
: The message from pccardc is that he failed the resouce allocation.
Fix the resource
It seems Warner Losh wrote:
In message [EMAIL PROTECTED] Soren Schmidt writes:
: Hmm, I'm also having a hell of a time here, on closer inspection it
: turns out that my problem is that the kernel allways finds an ed0
: device allthough none is present. I have both an ed0 an ep0 device
It seems Doug Rabson wrote:
Hmm, I'm also having a hell of a time here, on closer inspection it
turns out that my problem is that the kernel allways finds an ed0
device allthough none is present. I have both an ed0 an ep0 device
in my config as I use both type of cards. So my only
It seems Soren Schmidt wrote:
It seems Doug Rabson wrote:
Hmm, I'm also having a hell of a time here, on closer inspection it
turns out that my problem is that the kernel allways finds an ed0
device allthough none is present. I have both an ed0 an ep0 device
in my config as I
Ten'th update to the new ATA/ATAPI driver:
It been awhile since the last major update, as a benefit there
are some cool things in this one (and new bugs probably :) )...
The ATA driver has grown "real" timeout support for all devices.
This means that it should be possible to get in contact
It seems Cejka Rudolf wrote:
I'm trying to update my -current system compiled from July 12 (both
kernel and base system). But before all system updating I have tried to
compile and run new kernel from today (September 25) - and it won't
boot so I'm afraid to update all the system...
It seems Thomas Veldhouse wrote:
Hello,
I have noticed over time that many people are test driving the new
ATA
Drivers. I attempted to do it a while back but I couldn't boot because of
the device name changes. I did not know what the new device names were.
Anyway - is there a
It seems Cejka Rudolf wrote:
I think internal bad block remapping is long time here. But
in the middle of 1996 I have bought a new Western Digital disk
with some bad sectors and it runs without any problems till today
(and without any new bad sectors - I have tried new disk format
some time
snail mail addresss is:
Soren Schmidt
Soparken 61, Klokkerholm
DK9320 Hjallerup
Denmark
-Soren (and yes today I'm on a 7bit line too :) )
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Jeroen Ruigrok/Asmodai wrote:
you know I have the possession of a development box with the HPT366,
right? [well you should since I mailed you those timing-tables =P ]
I know :)
Anyways, as soon as I have enough cash again I will buy an /66 disk
and stuff it on the free
It seems Jeremy L. Stock wrote:
I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
(primary slave) and a CDROM as secondary master. The driver detects the
8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd provide
more info if I could but / lives on the
It seems Jeremy L. Stock wrote:
Are you sure you have the latest versions of everything in /sys/dev/ata ??
There was a window of opportunity where I messed up unless ATA_STATIC_ID
was defined...
-Søren
Fairly positive I have the latest versions. I cvsup'ed twice yesterday. I
forgot to mention
It seems Kenneth Wayne Culver wrote:
On Thu, 30 Sep 1999, Luke wrote:
On 01-Oct-99 Kenneth Wayne Culver wrote:
The ata driver seems to be having problems staying in contact with my
disks again. Let me know what details are needed to fix the problem, and
I'll get in touch with you.
It seems Daniel M. Eischen wrote:
More info on the kernel hang.
Removing pnp from the kernel configuration will allow me to boot
and successfully detects my pnp modem. So the culprit seems to
be the new pnp code. Suggestions welcome.
Hmm, I also have severe problems with the PnP stuff
It seems Erik H. Bakke wrote:
I am still having problems with the ATA driver.
I am seeing the same error messages as has been reported on the lists during
the last few weeks, both on i386 and alpha platforms.
On the i386, the problem is just an irritating itch, but it seems to be
far more
It seems Justin T. Gibbs wrote:
It looks like both nsio and sio have PCCARD support disabled at the
moment. Is there any other way I can get the system to recognize my
modem?
Fix the broken sio, it might be KNF and all but it doesn't work...
-Soren
To Unsubscribe: send mail to [EMAIL
It seems Kenneth Culver wrote:
Is this with the latest that I committed yesterday ??
-Søren
I finally got a chance to put the ata driver back in my kernel, and this
is what happens: Whenever I am doing something that requires a lot of disk
activity, (on the latest errors, I was recompiling
It seems Kenneth Culver wrote:
ata0: slave: success setting up UDMA2 mode on PIIX4 chip
ad1: piomode=4 dmamode=2 udmamode=2
ad1: Maxtor 84320D4/NAVX1920 ATA-3 disk at ata0 as slave
ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S
ad1: 16 secs/int, 0 depth queue, UDMA33
It seems Kenneth Culver wrote:
Oct 10 12:29:48 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
- res
etting
Oct 10 12:29:49 culverk /kernel: ata0: resetting devices .. DANGER
active=3
Oct 10 12:29:49 culverk /kernel: done
Oct 10 12:29:49 culverk /kernel: ad1: status=51 error=04
It seems Maxim Sobolev wrote:
It seems that ATA is broken - it paniced when kernel is booting. Following is
diagnostic output:
isa0: ISA bus on motherboard
pccard0: PC Card bus -- KLUDGE version on motherboard
Fatal trap 12: page fault while in kernel mode
fault virtual address= 0xc
It seems Maxim Sobolev wrote:
[Charset koi8-r unsupported, filtering to ASCII...]
Soren Schmidt wrote:
It seems Maxim Sobolev wrote:
It seems that ATA is broken - it paniced when kernel is booting. Following is
diagnostic output:
Fatal trap 12: page fault while in kernel mode
It seems Valentin S. Chopov wrote:
How the ATA_16BIT_ONLY in ata-disk.c and atapi-all.c
will be defined - kernel option, autodetection or
device flag?
For now kernel options, later auto for ISA 486 arch machines..
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
It seems Doug Rabson wrote:
On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote:
Have you either tried disabling DMA on the drive? This is easily achieved
by the following (whitespace mangled):
I'll try it on Monday.
Hmm, as well as DMA might be the reason, it only applies to
It seems Amancio Hasty wrote:
It seems Kazutaka YOKOTA wrote:
AFAIK, not all video cards generate the vertical retrace interrupt.
Even worse, some BIOSes have a configuration option which instract the
BIOS NOT to assign an IRQ to the PCI video card.
I fully agree that the
It seems Amancio Hasty wrote:
Just trying to prevent dragging the whole X server to the kernel --
Actually dragging the whole X server to the kernel is not a bad
idea --- however it is something that I can not afford to do right now :(
Ahh, horror, Terry's old idea is coming back again :)
It seems Amancio Hasty wrote:
Lets step back for a moment, this is clearly the wrong solution to
everything, what exactly is it you want to do or want to accomplish??
Lets see if we can come up with another way of doing that...
Okay,
The problem that the XFree86 group is trying to
It seems Andrzej Bialecki wrote:
Oops, sos and I have developed a new version of libsvgl which can
handle VESA modes in addition to the standard VGA graphics modes.
But I haven't committed it to the source tree yet (yes, I should have
done so weeks ago ;-(
Anyway, if you are
It seems F. Heinrichmeyer wrote:
more observations to the zip-drive problem:
First the relevant dmesg-line:
atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00
afd0: IOMEGA ZIP 100 ATAPI/23.D rewriteable drive at ata0 as master
afd0: 96MB (196608 sectors), 32 cyls, 64
It seems Bryan Liesner wrote:
On Fri, 26 Nov 1999, Soren Schmidt wrote:
It seems F. Heinrichmeyer wrote:
more observations to the zip-drive problem:
First the relevant dmesg-line:
I'm also still having a small problem with the ata driver and my HP
Colorado 8G. I have it hanging off
It seems Alexander Leidinger wrote:
I didn´t tried to reproduce this recently, but you could try to format
the ZIP-disc with mtools:
mformat -t 96 -h 64 -s 32 -H 32 z:
I'll dig out my ZIP drive tonight a do some testing...
---snip---
wdc0: unit 1 (atapi): IOMEGA ZIP 100 ATAPI/23.D,
It seems Wes Morgan wrote:
ad0: ST32140A/08.08.04 ATA-? disk at ata0 as master
ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, DMA
ad1: WDC AC418000D/J78OA30K ATA-4 disk at ata0 as slave
ad1: 17206MB (35239680 sectors), 34960 cyls, 16
It seems Christoph Kukulies wrote:
-current of Feb, 26th.
Innocently I wanted to
mount -t cd9660 /dev/acd1c /dist
to grab some newer XF86 from the CD when
cd9660: device not configured
was thrown at me.
And you have an acd1 device ??
check you /dev for up to date entries...
It seems John Hay wrote:
Hi,
I have been trying to install yesterday's 4.0 snap on a no-name brand
motherboard with the VIA chipset, but I'm running in some problems. I
suspect there is a problem with the DMA. The error I'm getting when the
disk is newfs'ed is a repeating:
ad0: WRITE
It seems Ben Smithurst wrote:
ok, this was partly caused by dodgy hardware it seems, so don't worry
too much, but it would be nice if a panic could be avoided.
aaiiighh! I knwo exactly what wrong, dont call make_dev early :)
Thanks, that probably one of the most complete reports I've seen in
It seems Hans Ottevanger wrote:
Hi folks,
I just tried to boot the RC3 install floppies on my Pentium 66 testbox.
It gets through the config stage without trouble, but then panics
immediately with:
...
pcib0: Host to PCI bridge on motherboard
pci0: PCI bus on pcib0
atapci0: RZ 100?
It seems Julian Elischer wrote:
It is most ironic that of course you were the loudest supporter of
SOS when he ripped out all my code that did EXACTLY all this.
(I might add that this was done without any warning to me. The
The commit messages being my first notice).
It was fully working
It seems Donn Miller wrote:
I've got two HD's in my machine: one's an older one (WDMA2) and the other
one, my main one, is newer (UDMA33). With recent kernel builds, I've
noticed some strange problems with the older HD. When I try to to
something like fsck -y on the drive, fsck just hangs.
It seems Matthew Sean Thyer wrote:
Please leave the wd driver for those who cannot use the ATA driver.
At least until the ATA driver gets support for more older disks.
I cant be the only person using an old 80 MB IDE drive as / with
another drive as /usr (a 400 MB SCSI).
I haven't tried
It seems Greg Childers wrote:
Hi,
I can't find the date or sender of the original email - the mailing list archives
haven't been updated since Feb 20 - but my Pentium 66 still panics during boot with a
kernel compiled today. Here's what I get...
atapci0: RZ 100? ATA controller !WARNING!
It seems David Gilbert wrote:
I still have hardware that works with wd and not ata. I posted awhile
ago that ata gets stuck in a retry loop on my system. This is with a
CVSUP of a couple of days ago.
Be sure you have the abosolutely latest version of the ata driver,
a bug was fixed in
It seems Bruce Evans wrote:
On Tue, 14 Mar 2000, Jeroen Ruigrok van der Werven wrote:
Yes...
That's right.
Use ata and related stuff instead.
No.
Yes.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Thomas Veldhouse wrote:
Are there any plans to support the buggy CMD640 interface in the future
now that 4.0-RELEASE has come and gone? I have a box that is running 3.4
happily, and it has this interface. I really would like the chance to use
some of the 4.0 features, but I can not
It seems Mathew Kanner wrote:
Hi All,
I wanted to document my difficuties with Vinum and multiple
disks on Promise controllers. I believe that the problems lies with
multiple cards on the same interupt but what do I know -- execpt that
the problem goes away when I disable most
It seems Chris D. Faulhaber wrote:
On Sat, 18 Mar 2000, Alan Clegg wrote:
Panasonic CD-ROM Changer that is found in by the kernel as:
acd0-4: CDROM with 5 CD changer RD-DRC004-M at ata0-master using PIO4
Mounting /cdrom1 works just fine:
/dev/acd0c on /cdrom1 (cd9660, local,
It seems Luigi Rizzo wrote:
Hi,
sometimes i get IDE disks with hard errors on some sectors
(status 59rdy,seekdone,drq,err error 40uncorr)
and of course this makes it problematic to use a filesystem on it.
I wonder, is there a way to fetch the data from these sectors
(even if
It seems Luigi Rizzo wrote:
I am asking because a strategy which often 'fixes' the
...
Erhm, I would get a new disk :), you dont intend to trust any
data to this setup do you ??
of course, but i need to recover the old stuff first!
Hmm, right...
A comment: this is a 18GB IBM 7200
It seems Warner Losh wrote:
: A comment: this is a 18GB IBM 7200 RPM disk and i noticed it tends
: to become very hot compared to other disks when mounted in the
: same machine (on a removable frame). Do others have the same
: experience ?
Yes. They run very hot. I had to steal an old
It seems Warner Losh wrote:
In message [EMAIL PROTECTED] Soren Schmidt writes:
: TEMPC=`camcontrol cmd -v -n da -u 0 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"`
: Hmm, wonder if one can get that info from their ATA disks as well...
Don't know. You'd have to ask
It seems Giorgos Keramidas wrote:
I built from sources cvsup'ed about 24 hours ago, my kernel and world,
this afternoon. After enabling INVARIANTS and INVARIANT_SUPPORT, I
booted and tried a lot of things. Nothing seemed to make the new kernel
I had (and it's own modules + world) go crazy
It seems Jeroen Ruigrok van der Werven wrote:
the DDB trick works. And it dumps at PIO mode 4, woot!
You have to, there is no garantie that DMA and even less interrupts
is working proberly on a potentially hosed machine..
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
It seems Vallo Kallaste wrote:
Hi
I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel
Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance
increase or such, simply want to get my hands on. Ata driver, as the
-current doesn't have wd anymore.
I have
It seems Greg Lehey wrote:
The problem that Søren and I are looking at is usually a panic. We
don't really know where it's happening, but we're each sure it's not
in *our* code :-) From a Vinum standpoint, it happens between the time
that Vinum sends a request to the driver and when the
It seems Vallo Kallaste wrote:
On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste [EMAIL PROTECTED]
wrote:
I hook up serial console to get full traceback next time, but I don't
have any knowledge for further analysis.
Here's full traceback, environment is all same, except the
It seems Bernd Walter wrote:
On Sun, Apr 02, 2000 at 05:38:01PM +0200, Soren Schmidt wrote:
It seems Vallo Kallaste wrote:
On Sun, Apr 02, 2000 at 03:39:35PM +0200, Vallo Kallaste
[EMAIL PROTECTED] wrote:
I hook up serial console to get full traceback next time, but I don't
It seems Bernd Walter wrote:
On Sun, Apr 02, 2000 at 08:02:54PM +0200, Vallo Kallaste wrote:
Yes, but I don't have space for crashdump and I can't build new kernel
with limited memory usage because I don't have /usr filesystem up and
running. Is there a way to limit memory usage without
It seems Alfred Perlstein wrote:
Just to clearify the things...
Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT?
I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it
might only occur with RAID5...
I've never seen it with just a striped setup:
It seems Bernd Walter wrote:
On Sun, Apr 02, 2000 at 09:39:36PM +0200, Soren Schmidt wrote:
I dont think vinum is/was usable under -current at least not the
RAID5 stuff, its broken, and some of it is because greg is not
up to date with what -current looks like these days.
Can you
It seems Greg Lehey wrote:
Unfortunately I don't have a toy i386 system ready and testet on alpha.
There may be some differences how data corruptions efects on this platform.
I found a potentially serious bug in the RAID calculations yesterday:
it assumed that sizeof (int) == 4. I
It seems Greg Lehey wrote:
This wont fix it on the i386 where the problem is, and btw I havn't seen
any commits yet...
No, I was just about to do something when phk changed the interfaces.
I don't have the time to keep chasing him, so I'll wait until we have
a relatively stable situation
It seems Vallo Kallaste wrote:
Here's the sequence of what I did:
1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system
built from March 31 sources. First I used striping over two disks and
put /usr filesystem onto it, did overnight testing and all was well.
2. Same
It seems Matthew Dillon wrote:
:Same story here, but using softupdates or async mounts I can reproduce
:the hang or panic in less than 60 secs..
:
:Vinum with raid5 is plain broken, include INVARIANTS in the kernel
:and see why...
:
:-Søren
Hang on to that thought. As soon as this
It seems Erik de Zeeuw wrote:
atapci1: HighPoint HPT366 ATA66 controller port \
0xb800-0xb8ff,0xb400-0xb403,0xb000-0xb007 \
irq 11 at device 19.0 on pci0
ata2: at 0xb000 on atapci1
atapci2: HighPoint HPT366 ATA66 controller port \
0xc400-0xc4ff,0xc000-0xc003,0xbc00-0xbc07
It seems John Hay wrote:
I tried to install 4.0-RELEASE on a completely new PC system, but the
install failed with ATA write errors and resets. I moved the disk to another
PC and installed 4.0 via manual disklabels, newfs, bin + src extraction.
4.0 booted fine on this system (a Dell
It seems John Hay wrote:
Yup VIA has a new version of the 82C596 chip, in their usual visdom they
change the interface, but not the chip ID (I'll nominate VIA for the
way they do versioning). However I have worked out the solution with
Chris Wiener [EMAIL PROTECTED], that had this
It seems Brad Knowles wrote:
Like I said in a previous message, Poul broke vinum (among other
things) under 4.0-STABLE, and this needs to be fixed ASAP. If Poul
had kept his changes unique to -CURRENT, then 4.0-STABLE wouldn't
have been affected. But he didn't, and it was.
Where
It seems John Hay wrote:
Hi,
I have installed 4.0-STABLE on our machine with the CD burner and when
I tried to burn a CD, the session went as follows:
===
tien# burncd -s 4 -f /dev/acd0c data 4.0-install.iso fixate
next writeable LBA 0
writing from file 4.0-install.iso size 641174
It seems Maxim Sobolev wrote:
I've tried it on my home machine and failed to reproduce also. However it is
strange, because if it is the CPU/Memory problem, then there should be other signs
- random applications crashes, spontaneous reboots etc., but machine is pretty
stable - up and
Some time ago -core requested that linprocfs should move into the linuxulator.
Nothing has happend on that account, so -core is now forced to take action.
This is the announcement that linprocfs will be removed from the -current
tree in 72 hours, giving the involved parties a final deadline
It seems Alexander Langer wrote:
2320:
* * * W A R N I N G * * *
The ata driver has some issues with the Apollo MVP3 chipset.
Drives work only in pio mode and must be set to pio mode early
int the boot process. Do not upgrade. If you must upgrade
It seems Warner Losh wrote:
In message [EMAIL PROTECTED] Soren Schmidt writes:
: Ehm, is that a warning you have written or ?? I certainly havn't
: issued this warning as the maintainer/author of the ata driver...
I think that I wrote it, and that it is basically wrong. I'll look
It seems John Hay wrote:
Interesting that those same disks work in the same UDMA33 mode on
another motherboard with a different chipset. I have tried both
Samsung and Seagate disks. I have also tried more than one
motherboard and they do the same, so it isn't just a faulty board.
I have also
It seems John Hay wrote:
What board make/version is this ?
There is no name or version on the board itself. The box it came in
said it is a "A+ Mainboard" and on the side there is a label that
says "APRO/BAT Motherboard". And it is made in China.
Uhm
A verbose dmesg with version
It seems Mike Pritchard wrote:
I did notice that I started getting all of the "unknown: PNPx"
messages after the PNPBIOS option became default. On the
machine I'm typing on this on, I used to see those messages
if I defined PNPBIOS in my config file. PNPBIOS became default
some time
It seems Mike Smith wrote:
That's a cool idea, but unfortunately, it won't work with any hardware I
know of.
In order for that to work, the CDROM drive would have to generate an AEN
(Asynchronous Event Notification) and send it to the controller, which
would have to be capable of
It seems Warner Losh wrote:
In message 12213.961613148@localhost "Jordan K. Hubbard" writes:
: Everyone talks about using bitkeeper but none of the people who
: recommend it have ever actually tried to use it for anything.
: Before such recommendations will bear weight, this needs to
:
It seems Mark Murray wrote:
Hola Mondo!
The New /dev/random device is in but there are come caveats.
1) It is not yet cryptographically secure, so those of you using
CURRENT for "live" projects, please be careful!
2) If you do not have the randomdev module loaded, ssh will
fail
It seems Mark Murray wrote:
Hi
Without knowing what you typed (and where), I can't help.
Well, I thought that was obvious :)
Just added options RANDOMDEV as pr your instructions and made
a new kernel with config -r and make depend then make
cc -c -O -pipe -Wall -Wredundant-decls
It seems Mark Murray wrote:
Without knowing what you typed (and where), I can't help.
Well, I thought that was obvious :)
Not really; folks do the darndest things. :-)
Just added options RANDOMDEV as pr your instructions and made
a new kernel with config -r and make depend then
It seems Mark Murray wrote:
Do you have a full crypto distribution (kernel also)?
Nope, just figured that out myself :)
Aren't we supposed to be able to build without crypto ??
I'm not sure about that rule anymore; AFAIK, it is not possible.
Hmm, we also have another rule, and that
It seems Mark Murray wrote:
I'm not sure about that rule anymore; AFAIK, it is not possible.
Hmm, we also have another rule, and that is to test before commit,
the following patch is needed to make a current kernel with
your resent commits compile :)
Fooey. :-(
This is what you
It seems Mark Murray wrote:
He he :) remember the patch to i386/i386/mem.c as that is also
broken, the default statement is best used _inside_ a switch :)
Yeah - I got that :-).
And the one to yarrow.c ??
That makes my kernel compile, but ssh doesn't work anymore,
What are the
It seems Poul-Henning Kamp wrote:
Who knows the cure for this ?
I do :)
Rip out perl from the base system ...
(ducks and runs)
-Søren
=== gnu/usr.bin/perl/perl
Extracting config.h (with variable substitutions)
Extracting cflags (with variable substitutions)
Extracting writemain (with
It seems Mark Murray wrote:
If I'm not mistaken, all open problems are like "Perl lib version
(v5.6.0) doesn't match executable version (5.00503) at Config.pm line
18."
Hmm...
That should be easy to reproduce on your development system by just
copying an old /usr/bin/perl
It seems Nate Lawson wrote:
Looking at the code in atapi-cd.c and atapi-all.c, it seems like the
queued request is getting an EIO. Judging from the behavior when I tried
to close a session that was already finished, I can only guess that what
the ata driver is sending my drive is different
It seems Roderick van Domburg wrote:
ATAng has just been committed. You need to make world after this
update as atacontrol etc needs to pick up the changes.
Coolness. Judging from the CVS log, it also gets ATA out under Giant?
Yes it does.
That should make ATA-run SMP boxes eligible
It seems Matt wrote:
I have just cvsup'd and done a full buildworld/kernel and on reboot had a
kernel panic. Unfortunatly I do not have ddb or anything compiled into the
kernel but I can sort this out and get a proper backtrace etc if you don't
immediatly know what's wrong.
I have the
It seems Wesley Morgan wrote:
On Sun, 24 Aug 2003, Matt wrote:
This did work perfectly with the old ATA, but the new ATA panic's. I have
found that it is due to having device atapicam for the SCSI emulation. If I
recompile the kernel with this option commented out the kernel boots and
1 - 100 of 512 matches
Mail list logo
