> < said:
>
> > The enumerator should assign these resources to a placeholder; I was
> > thinking the nexus was as good an owner as any. If there's an
> > "unknown" device that's probably even better.
>
> Some of them should be claimed by real devices -- for example, the
> pseudo-i8237 ISA DM
> > ummm... I thought that the plan was to disable all PnP devices, do the
> > legacy isa probes, and then reenable the PnP devices and probe them...
>
> The fact that a device is reported via PnP does not guarantee that you
> can disable it. Most of the "devices" reported by the PnP BIOS can
< said:
> The enumerator should assign these resources to a placeholder; I was
> thinking the nexus was as good an owner as any. If there's an
> "unknown" device that's probably even better.
Some of them should be claimed by real devices -- for example, the
pseudo-i8237 ISA DMA controller sho
> > This is one reason why I think that the PnP scan should be done
> > _before_ the legacy scan; there are cases where the legacy scan is
> > going to find stuff that the PnP enumerator also knows about. If the
> > PnP enumerator has already found it, then the legacy scan aborts; in
> > the
Gerhard Häring scribbled this message on Sep 5:
> I have some linux experience and I have recently installed freebsd. I
> understand -current is not for serious work. I wonder if it is i)
> possible ii) a good idea to install the *kernel* of -current in my
> freebsd 3.1 system. Or are there too ma
Hello freebsd wizards!
I have some linux experience and I have recently installed freebsd. I
understand -current is not for serious work. I wonder if it is i)
possible ii) a good idea to install the *kernel* of -current in my
freebsd 3.1 system. Or are there too many user programs that heavily
de
Mike Smith scribbled this message on Sep 4:
> > > I'm curious what can be made of the PNP resource list we get from the BIOS
> > > at boot time... It lists motherboard resources too, we could probably end
> > > up with a fairly complete map of known resources to avoid.
> >
> > I bet we can roll
> > I'm curious what can be made of the PNP resource list we get from the BIOS
> > at boot time... It lists motherboard resources too, we could probably end
> > up with a fairly complete map of known resources to avoid.
>
> I bet we can roll another enumerator similar to pnp.c which takes the bi
Hi Ken,
Sorry, I'm really confused about who has the problem,
but I *do know* my system isn't working properly.
Also, it is different...I didn't know about the two
drives until after I sent mail to you.
Anyway...here goes-->
On 04-Sep-99 Kenneth D. Merry said:
> Rick Lotoczky wrote...
...my
On Sat, 4 Sep 1999, Doug Rabson wrote:
> On Fri, 3 Sep 1999, Steve Price wrote:
>
> > Can anyone think of a good reason why I can't migrate the
> > old PNP ids to the new sio.c? I just rebooted my box with
> > a fresh kernel and much to my shagrin (sp?) my USR PNP
> > modem didn't work anymore.
Doug Rabson <[EMAIL PROTECTED]> wrote:
> Does your bios have a setting for 'PNP compliant OS' or similar? If it
> does, set it to 'no' and see if it helps. The current pci code relies on
> the bios to program port and memory locations for cards and its possible
> that this isn't happening for you
Steve Kargl wrote...
> Kenneth D. Merry wrote:
> > This sounds like it could be a different problem than Randy Busy is having.
> > He has two CDROM drives, and it looks like they have been swapped somehow.
> >
> > It sounds like you've only got one CDROM drive in each machine.
> >
> > Please sen
On Sun, 5 Sep 1999, Peter Wemm wrote:
> Doug Rabson wrote:
> > On Sat, 4 Sep 1999, John-Mark Gurney wrote:
> >
> > > Doug Rabson scribbled this message on Sep 4:
> > > > > This is of course a special case, a cranky network card and a
> > > > > non-compiling driver for it. If the new pnp code av
On Sat, 4 Sep 1999, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Doug
>Rabson writes:
> : + aha = aha_alloc(device_get_unit(dev),
> : + I386_BUS_SPACE_IO, ioport);
>
> Shouldn't we be getting the bus_space_tag and bus_space_handle from
> the port_res r
In message <[EMAIL PROTECTED]> Doug Rabson
writes:
: + aha = aha_alloc(device_get_unit(dev),
: + I386_BUS_SPACE_IO, ioport);
Shouldn't we be getting the bus_space_tag and bus_space_handle from
the port_res resource?
Warner
To Unsubscribe: send mail to [
>I ask because I'm not having much luck getting it to work!
>I followed the instructions in README.FREEBSD, and none of the
>machines on my network can see the fake netware server.
After some experimentation and playing around with debug options
on IPXrouted and mars_nwe, it turns out that it's o
In message <[EMAIL PROTECTED]> Doug Rabson
writes:
: I have just taken a pass through the aha_isa driver to convert it to
: newbus and to make it use the new pnp system. Unfortunately I don't own
: the hardware so I need testers, preferably both with non-pnp and pnp
: cards. The code does compile
According to Doug Rabson:
> Can I see your kernel config and dmesg lines both from an old (working)
> kernel and from the new kernel.
To add positive note to this, I just rebooted my dual PPro with newpcm and the
sound card was recognised and is working.
-=-=-
unknown0: on isa0
pcm0: at port
Kenneth D. Merry wrote:
> This sounds like it could be a different problem than Randy Busy is having.
> He has two CDROM drives, and it looks like they have been swapped somehow.
>
> It sounds like you've only got one CDROM drive in each machine.
>
> Please send the output of the following, with
Doug Rabson wrote:
> On Sat, 4 Sep 1999, John-Mark Gurney wrote:
>
> > Doug Rabson scribbled this message on Sep 4:
> > > > This is of course a special case, a cranky network card and a
> > > > non-compiling driver for it. If the new pnp code avoids using resource
s
> > > > hard-wired to non
On Sat, 4 Sep 1999, John-Mark Gurney wrote:
> Doug Rabson scribbled this message on Sep 4:
> > > This is of course a special case, a cranky network card and a
> > > non-compiling driver for it. If the new pnp code avoids using resources
> > > hard-wired to non-pnp isa devices (it may, I changed
In message <[EMAIL PROTECTED]>, "Kenneth D. Merry" writes:
>Randy Bush wrote...
>> > I am having the same problem with the CD as Ken is.
>>
>> actually, it was ken helping me with my problem.
>>
>> and it turns out my problem was that the two drives had been physically
>> swapped, and when jet-l
>
> The problems might be wholly unrelated. I've just reconfigured my BIOS
> to put everything onto irq 11
>
> uhci0: irq 11 at device 1.2 on
> pci0
> ohci0: irq 11 at device 9.0 on
> pci0
> vga-pci0: irq 11 at device 10.0 on pci0
> ed1: irq 11 at device 11.0 on pci0
Hmm. I just remembered
Doug Rabson scribbled this message on Sep 4:
> > This is of course a special case, a cranky network card and a
> > non-compiling driver for it. If the new pnp code avoids using resources
> > hard-wired to non-pnp isa devices (it may, I changed hardware before the
> > code was fixed), there should
Randy Bush wrote...
> > I am having the same problem with the CD as Ken is.
>
> actually, it was ken helping me with my problem.
>
> and it turns out my problem was that the two drives had been physically
> swapped, and when jet-lag subsided the ing idiot pilot realized his
> stupidity.
Whew.
After i got 1.117 everything went back to normal.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Sat, 4 Sep 1999, Doug Rabson wrote:
> On Sat, 4 Sep 1999, Arthur H. Johnson II wrote:
>
> > Done, and I have pci.c 1.117. When did it get broken then fixed?
Rick Lotoczky wrote...
> I am having the same problem with the CD as Ken is.
> I also tried the suggested diagnostics with exactly the
> same results. Media is in the drive, but it is not being
> recognized. I've been building kernels since FBSD-0.9 so
> I think I got that right by now. This c
Randy Bush wrote...
> >> # camcontrol tur cd0 -v
> >> Unit is not ready
> >> (pass2:ahc0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> >> (pass2:ahc0:0:4:0): NOT READY asc:3a,0
> >> (pass2:ahc0:0:4:0): Medium not present
> > Well, there's your problem, for better or worse.
>
>
I ask because I'm not having much luck getting it to work!
I followed the instructions in README.FREEBSD, and none of the
machines on my network can see the fake netware server.
My requirement, incidentally, is to have a networking client, for
DOS, that will fit on a boot floppy. The server is F
> I am having the same problem with the CD as Ken is.
actually, it was ken helping me with my problem.
and it turns out my problem was that the two drives had been physically
swapped, and when jet-lag subsided the ing idiot pilot realized his
stupidity.
apologies to all.
randy
To Unsubscribe
On Fri, 3 Sep 1999, Evren Yurtesen wrote:
>
> I think you should install an old library... see this page
> http://minnie.cs.adfa.edu.au/Misc/staroffice.html
That page refers to StarDivion's StarOffice 5.1, not (what appears
to be) the slightly tweaked/updated version that Sun is now
distribut
On Fri, 3 Sep 1999, Chris D. Faulhaber wrote:
> Doug Rabson wrote:
>
> > I have just taken a pass through the aha_isa driver to convert it to
> > newbus and to make it use the new pnp system. Unfortunately I don't own
> > the hardware so I need testers, preferably with both non-pnp and pnp
> > c
On Sat, 4 Sep 1999, Arthur H. Johnson II wrote:
> Done, and I have pci.c 1.117. When did it get broken then fixed? I ran
> make update and make world just thursday.
The bug in pci.c 1.116 only affected pnp cards so perhaps you have another
problem. If so, you need to try to work with Cameron G
On Sat, 4 Sep 1999, Blaz Zupan wrote:
> On Sat, 4 Sep 1999, Doug Rabson wrote:
> > Does your bios have a setting for 'PNP compliant OS' or similar? If it
> > does, set it to 'no' and see if it helps. The current pci code relies on
> > the bios to program port and memory locations for cards and it
Done, and I have pci.c 1.117. When did it get broken then fixed? I ran
make update and make world just thursday.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Sat, 4 Sep 1999, Doug Rabson wrote:
> On Sun, 5 Sep 1999, Andrew Kenneth Milton wrote:
>
> > +
On Sat, 4 Sep 1999, Doug Rabson wrote:
> Does your bios have a setting for 'PNP compliant OS' or similar? If it
> does, set it to 'no' and see if it helps. The current pci code relies on
> the bios to program port and memory locations for cards and its possible
> that this isn't happening for your
On Sun, 5 Sep 1999, Andrew Kenneth Milton wrote:
> +[ Doug Rabson ]-
> | On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
> |
> | > +[ Arthur H. Johnson II ]-
> | > | I fixed the sound card problem I
Crap, the old kernel is gone. I was going to save the old working kernel
but its gone now. I attached the old config file thou.
Arthur H. Johnson II
http://www.linuxberg.com
Linuxberg Manager
[EMAIL PROTECTED]
On Sat, 4 Sep 1999, Doug Rabson wrote:
> On Sat, 4 Sep 1999, Andrew Kenneth Milton
On Sat, 4 Sep 1999, Steve Price wrote:
> On Sat, 4 Sep 1999, Doug Rabson wrote:
>
> # The reason I didn't move the old ids wholesale is that the old system
> # matched against the vendor id (which is bogus for multifunction cards).
> # The new system matches with the logical device id which is o
+[ Doug Rabson ]-
| On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
|
| > +[ Arthur H. Johnson II ]-
| > | I fixed the sound card problem I was having. I just commented out the pnp
| > | driver. I k
As in
diff -wu brooktree848.c.orig brooktree848.c
--- brooktree848.c.orig Sat Sep 4 14:38:14 1999
+++ brooktree848.c Sat Sep 4 14:38:19 1999
@@ -6865,9 +6865,6 @@
unsigned int rev = pci_get_revid(dev);
static int once;
- if (!once++)
- cdevsw_add(&
On Sat, 4 Sep 1999, Doug Rabson wrote:
# The reason I didn't move the old ids wholesale is that the old system
# matched against the vendor id (which is bogus for multifunction cards).
# The new system matches with the logical device id which is often different
# from the vendor id. Some simple s
On Sat, 4 Sep 1999, Blaz Zupan wrote:
> I'm trying to configure my new Compex NE2000 PCI card under 4.0-current.
> Just before the latest PnP changes, the card was just recognized like
> this:
>
> ed0: irq 10 at device 13.0 on pci0
>
> It did not display the MAC, and "ifconfig -a" did not show
On Sat, 4 Sep 1999, Andrew Kenneth Milton wrote:
> +[ Arthur H. Johnson II ]-
> | I fixed the sound card problem I was having. I just commented out the pnp
> | driver. I know I will run into problems later if I ever get pnp devices,
> | but its a
On Sat, 4 Sep 1999, Zach N. Heilig wrote:
> On Sat, Sep 04, 1999 at 10:21:51AM +0100, Doug Rabson wrote:
> > The pnp command should no longer be needed (crossed fingers) since the new
> > code automatically detects devices and assigns resources to them.
>
> What about the situation where:
>
> p
The problems might be wholly unrelated. I've just reconfigured my BIOS
to put everything onto irq 11
uhci0: irq 11 at device 1.2 on
pci0
ohci0: irq 11 at device 9.0 on
pci0
vga-pci0: irq 11 at device 10.0 on pci0
ed1: irq 11 at device 11.0 on pci0
and that works just fine:
addr 1: UHCI roo
cdevsw_add is called in devsw_module_handler and in bktr_probe. Patch
attached. It looks like the init in bktr_probe became superfluous in
revision 1.90 of brooktree848.c:
revision 1.90
date: 1999/08/23 20:59:12; author: phk; state: Exp; lines: +7 -20
Convert DEVFS hooks in (most) drivers to
Hi,
I am having the same problem with the CD as Ken is.
I also tried the suggested diagnostics with exactly the
same results. Media is in the drive, but it is not being
recognized. I've been building kernels since FBSD-0.9 so
I think I got that right by now. This cropped up somewhat
recently
I'm trying to configure my new Compex NE2000 PCI card under 4.0-current.
Just before the latest PnP changes, the card was just recognized like
this:
ed0: irq 10 at device 13.0 on pci0
It did not display the MAC, and "ifconfig -a" did not show ed0/ed1 as
configured. I even tried booting a generi
>> # camcontrol tur cd0 -v
>> Unit is not ready
>> (pass2:ahc0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
>> (pass2:ahc0:0:4:0): NOT READY asc:3a,0
>> (pass2:ahc0:0:4:0): Medium not present
> Well, there's your problem, for better or worse.
it's even kinkier than that. despit
>> panic() no longer works when called early. E.g., after booting with -d,
>> typing `panic' at the debugger prompt produces no output and
>> hangs.
>>
>> This may be because panic() now depends on uninitialized event handlers.
This is because no shutdown_final event handlers have been register
On Sat, Sep 04, 1999 at 10:21:51AM +0100, Doug Rabson wrote:
> The pnp command should no longer be needed (crossed fingers) since the new
> code automatically detects devices and assigns resources to them.
What about the situation where:
pnp sound card (soundblaster awe64).
non pnp network card
Something that was working yesterday no longer works since I've made
world.
Out of memory (Needed 8192 bytes)
python in free(): warning: junk pointer, too high to make sense.
Out of memory (Needed 8192 bytes)
python in free(): warning: junk pointer, too high to make sense.
I've rebuilt python an
Hi
I have put new common error code in; compile_et and libcom_err
need rebuilding. The recommended method is a "make world".
M
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
+[ Arthur H. Johnson II ]-
| I fixed the sound card problem I was having. I just commented out the pnp
| driver. I know I will run into problems later if I ever get pnp devices,
| but its a temporary fix.
Pcm doesn't work for me anymore with or wi
On Fri, 3 Sep 1999, Steve Price wrote:
> Can anyone think of a good reason why I can't migrate the
> old PNP ids to the new sio.c? I just rebooted my box with
> a fresh kernel and much to my shagrin (sp?) my USR PNP
> modem didn't work anymore. The following patch got it
> working again.
The r
56 matches
Mail list logo
