i wonder what is happening to the ida driver for comapq's smart array
controller series.
people say the pci version works but the eisa version is not.
in the ida.c file is says:
* Specific probe routines are in:
* pci/ida_pci.c
* i386/eisa/ida_eisa.c
but unfortunatly the
Eines schoenen Tages schrieb Warner Losh:
> : > Someone thought that tm_year was the last two digits of the year
> : > rather than year - 1900.
> :
> : Is ELM [version 2.4 PL25 PGP6] that much broken?
>
> Looks that way...
just compiled elm 2.5.2 ... looks to me, that is fixes my
"problem" ... b
Eines schoenen Tages schrieb Andre Oppermann:
>
> Warner Losh wrote:
> >
> > In message <[EMAIL PROTECTED]> Andre Oppermann writes:
> > : Sat, 1 Jan 100 17:16:30 +0100 (MET)
> > : Oliver, how old is your PC?
it's not a pc ... it's a sun ultra 1 ... and unfortunatly it's not mine. it
belongs to
> > i wonder what is happening to the ida driver for comapq's smart array
> > controller series.
>
> Work on this driver is stalled owing to the fact that nobody that can and
> wants to work on it has access to the Compaq hardware required. You
> can't use these controllers except in Compaq sy
hello *!
i am using the vx driver in for my two 3c397 boards.
when booting i get the following message:
vx0 XXX: driver didn't set ifq_maxlen
obviosly the ifq_maxlen is not set in the eisa nor in the pci version in the
driver.
actually, to set this, would be one line in the driver, but unfrotun
hello *!
i was very happy to se, that the eisa bus attachment stuff had been reviewed
and comitted to the source tree. the kernel compiles w/o problems but
panics, when booting :-(
has anybody with an eisa board have had success (maybe my setup is somehow
wrong?!)
relevent kernel messages:
ahb0:
Eines schoenen Tages schrieb Matthew N. Dodd:
[snip]
> Could you add
>
> printf("0x%lx\n0x%lx0x%lx\n", qcb, completed, qcb_done);
>
> to ida.c:ida_wait() after this line:
>
> 454:qcb_done = idahwqcbptov(ida, completed & ~3);
>
> And show us the output.
there we go:
qcb = 0xc0ca7000
com
Eines schoenen Tages schrieb Matthew N. Dodd:
[snip]
> Doh! Looks like Jonathan didn't merge the latest ida_eisa.c that I'd
> worked on when he fixed the driver to support multiple access methods and
> added EISA support.
>
> Try this patch:
[snip]
hmm ... the controller shows up with another i
Eines schoenen Tages schrieb Matthew N. Dodd:
> On Tue, 14 Mar 2000, Oliver Schonefeld wrote:
> > hmm ... the controller shows up with another io-adress, but now the driver
> > panics because of a time out :-(
>
> Try this patch:
[snip]
again, no success. the driver counts
hello!
[snipped-a-lot]
i am currently building world and will be testing the driver. in about 4 - 5
hours (it's not the fastet machine ;-) i will be able to send feedback ...
cheers,
oliver
--
"Mein Gott, es ist voller Sterne!"
email: [
hello!
all right ... things take longer then we expect them to take.
the kernel (everything cvsup'd on saturday) boot fine and the array
controller is detected just perfect. also fdisk'ing, disklabel'ing and
newfs'ing the drive was no problem. i copied almost the whole current source
tree on the
i recently updated my -current system from -current as of about mid-march to
lest sundays's -current (jep, from 4.0 to 5.0) due to the work done to the
ida driver.
well, the ida driver seems to work, but the network hast complety stopped
working.
with sunday's -current, after about 2-5 minutes upt
well, after cvsup'ing and building of the world, the network seems to work a
litte better.
but under faily heavy load (flood pinging _form_ the host and floodpint _to_
the host) results in a trap 12. seem that actually the heavy output kills
the machine.
Fatal trap 12: page fault while in kernel
Eines schoenen Tages schrieb Andrey A. Chernov:
> On Sun, May 07, 2000 at 06:44:39PM +0930, Greg Lehey wrote:
> > I've just built a new kernel, based on a cvsup at 2030 UTC on 6 May,
> > and since then *some* Ethernet transactions don't work. I've checked
> > that it's not just a dead card: the p
Eines schoenen Tages schrieb Oliver Schonefeld:
[snip]
> > It is not dead card, it is broken TCP, see my similar report in -current, I
> > notice it several hours ago right after TCP changes was commited.
>
> Same thing here, but the problems have gone to -stabe too. due t
Eines schoenen Tages schrieb Ted Sikora:
> Christian Weisgerber wrote:
> >
> > On this machine which runs -CURRENT from two days ago or so, I'm
> > seeing frequent cvsup client failures of this type:
> >
> > TreeList failed: Network write failure: Connection closed
> >
> > I don't recall ever r
Hello freebsd-current!
The loader or the kernel crashed badly on my Gericom Overdose II notebook.
I was trying to boot from the bootdisk-set. The mfsroot image is successfuly
loaded and the "bootcountdown" ist displayed.
After that it looks like there are some cpu-registers dumped.
unfortunalty
17 matches
Mail list logo
