Re: Strange phenomen accessing a CDROM contents under linuxerator

2000-04-14 Thread Nick Hibma
The one directory I can remember that was missing from the acroread file selector was a symbolic link (to the directory with the documents I wanted of course :-). /usr/export was not found, but /usr/export/usb was found when typed in in the top edit box. I see the same thing on 4.0-STABLE, so

Problems with MAKEDEV.

2000-04-14 Thread Ashley Penney
When booting up I noticed the block device warning message. I did some investigation and discovered that some ad4/ad5 devices were still block ones. It seems that the MAKEDEV script only makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). Simply adding ad4 ad5 onto the script

Re: Problems with MAKEDEV.

2000-04-14 Thread Steve Ames
On Fri, Apr 14, 2000 at 08:58:29PM +1000, Peter Jeremy wrote: On 2000-Apr-14 20:43:12 +1000, Ashley Penney [EMAIL PROTECTED] wrote: It seems that the MAKEDEV script only makes up to ad3, but my disks are on ad4/ad5 (ATA-66, Abit BP6). "MAKEDEV all" is designed to create a generic set of

Re: MLEN and crashes

2000-04-14 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], Peter Jeremy write s: Many years ago, I wrote a tool that analysed stack requirements by parsing the assembler output from the compiler. It determined the stack frame requirements and built a call flow graph to determine total stack depth. It had some hooks to

Re: MLEN and crashes

2000-04-14 Thread Thomas David Rivers
Peter Jeremy [EMAIL PROTECTED] wrote: On 3/04, John Polstra wrote: [don't allocate big structs on kernel stack] Many years ago, I wrote a tool that analysed stack requirements by parsing the assembler output from the compiler. It determined the stack frame requirements and built a call

middle mouse button emulation broken in 4.0-STABLE?

2000-04-14 Thread Robert Watson
Not sure if this should go to -current or -stable, since we seem to get a lot of instant MFC's these days :-). I upgraded a notebook from 4.0-RELEASE to -STABLE last night. After doing so, I noticed that the middle mouse button emulation in moused seems to be fairly broken -- i.e., once it's

PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Michael I. Vasilenko
Recently our firm bought Lucent wireless hardware - PCI Adapter and PCMCIA card. After unsucsessfull trying to get it work on 3.4+PAO, I've upgraded to 5.0-CURRENT. All hardware ssems to be detected, pccardc pccardmem 0xd4000 is ok, but after running pccardd it says: pccardd[166]: Card

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Bill Paul
Of all the gin joints in all the towns in all the world, Michael I. Vasilenko had to walk into mine and say: pccardd[166]: Card "Lucent Technologies"("WaveLAN/IEEE") matched "Lucent Technologies" ("WaveLAN/IEEE") pccardd[166]: Using I/O addr 0x100, size 64 pccardd[166]: Setting config

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread John Hay
Delete or rename /dev/card1 and you should get further. It will most probably still not work, but it won't hang anymore. You probably also have to tell pccardd to use the same interrupt that pcic-pci0 got, because I don't see how else it can work, but I'm not sure. I mean a PCI card can't

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Warner Losh
In message [EMAIL PROTECTED] Michael Vasilenko writes: : : : On Fri, 14 Apr 2000, John Hay wrote: : : Delete or rename /dev/card1 and you should get further. It will most : probably still not work, but it won't hang anymore. : : Thanks, it still don't work, but didn't hang anymore :) : :

Re: Netscape 6 Linux pre-release, got it going.

2000-04-14 Thread Donn Miller
"Dr. Brain" wrote: I've had a good deal of success getting Mozilla to build straight out of the nightly source tar files: ftp://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-source.tar.gz Over the past month, in -current, I've had weird problems with Mozilla. The message I'm seeing on

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread John Hay
In message [EMAIL PROTECTED] John Hay writes: : You probably also have to tell pccardd to use the same interrupt that : pcic-pci0 got, because I don't see how else it can work, but I'm not : sure. I mean a PCI card can't generate different interrupts than the : one(s) connected to its pins

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread John Hay
Delete or rename /dev/card1 and you should get further. It will most probably still not work, but it won't hang anymore. Thanks, it still don't work, but didn't hang anymore :) You probably also have to tell pccardd to use the same interrupt that pcic-pci0 got, because I don't see

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Warner Losh
In message [EMAIL PROTECTED] John Hay writes: : Uhmm, but if pcic use that interrupt, then there is no interrupt that : pccardd can give to the pcmcia card? Or can you have more than one : interrupt from the PCI card to the motherboard? Yes. PCI cards have 4 different interrupt lines, although

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Viren R.Shah
"Matthew" == Matthew N Dodd [EMAIL PROTECTED] writes: MD mdodd 2000/04/13 11:09:07 PDT MD Modified files: MD sys/dev/ida ida_eisa.c MD Log: MD - Add an additional call to eisa_add_iospace() so we get the right IOPORT MD in attach. MD - Change a

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Warner Losh
In message [EMAIL PROTECTED] John Hay writes: : This is where I'm stuck too. I think there might be some more initialization : of the TI1225 necesary. I've added some init of the ti chipsets to -current. They are enough for my TI-1221 based card to allow me to talk to the modems that I have.

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Matthew N. Dodd
On Fri, 14 Apr 2000, Viren R.Shah wrote: I just tried it. Here's what I get: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0:

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Viren R.Shah
"MD" == Matthew N Dodd [EMAIL PROTECTED] writes: MD On Fri, 14 Apr 2000, Viren R.Shah wrote: I just tried it. Here's what I get: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Edwin Culp
Michael, I just threw one in my laptop a couple of days ago. I didn't even have to recompile the kernel. I just added the stock WaveLAN section to my pccard.conf let it load the if_wi.ko and it worked. Although when I reboot I have to take the card out and put it back in because there seems

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Matthew N. Dodd
On Fri, 14 Apr 2000, Viren R.Shah wrote: If you will tell me how. Can I just compile in DDB without building the kernel with debug enabled? If so, that should work (I'm currently gzipping the kernel onto the kern.flp floppy, and booting off of it.). options DDB In your kernel config

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Viren R.Shah
"Matthew" == Matthew N Dodd [EMAIL PROTECTED] writes: Matthew On Fri, 14 Apr 2000, Viren R.Shah wrote: If you will tell me how. Can I just compile in DDB without building the kernel with debug enabled? If so, that should work (I'm currently gzipping the kernel onto the kern.flp floppy,

Re: PCI-CardBus bridge + PCMCIA Lucent WaveLAN IEEE troubles

2000-04-14 Thread Edwin Culp
Edwin Culp wrote: Michael, I just threw one in my laptop a couple of days ago. I didn't even have to recompile the kernel. I just added the stock WaveLAN section to my pccard.conf let it load the if_wi.ko and it worked. Although when I reboot I have to take the card out and put it back

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Viren R.Shah
"MD" == Matthew N Dodd [EMAIL PROTECTED] writes: MD On Fri, 14 Apr 2000, Viren R.Shah wrote: If you will tell me how. Can I just compile in DDB without building the kernel with debug enabled? If so, that should work (I'm currently gzipping the kernel onto the kern.flp floppy, and booting

Re: Problems with MAKEDEV.

2000-04-14 Thread David O'Brien
On Fri, Apr 14, 2000 at 11:41:55AM +0100, Ashley Penney wrote: When booting up I noticed the block device warning message. I did some investigation and discovered that some ad4/ad5 devices were still block ones. It seems that the MAKEDEV script only makes up to ad3, but my disks are on

IEEE 1394 Firewire issues

2000-04-14 Thread Southwell
Ok Guys Help needed -- I would be grateful for any information which would be useful for a project to provide IEEE 1394 (firewire support) on FreeBSD 4.0. In particular to start with the Texas Instruments OHCI compliant controller. If it cannot be done with that chip then I will look at other

Re: IEEE 1394 Firewire issues

2000-04-14 Thread Brooks Davis
On Fri, Apr 14, 2000 at 02:30:03PM -0800, Southwell wrote: Ok Guys Help needed -- I would be grateful for any information which would be useful for a project to provide IEEE 1394 (firewire support) on FreeBSD 4.0. In particular to start with the Texas Instruments OHCI compliant

RFC: Patches for mounting fdesc on /dev/fd and general cleanup

2000-04-14 Thread Chris Costello
(Trying -current since -arch wasn't very interested.) I've modified the fdesc file system so that it will be mounted on /dev/fd directly (rather than as a union mount on /dev) and have fixed a lot of items relating to missing data and incorrect cloning. Documentation:

Re: Problems with MAKEDEV.

2000-04-14 Thread Peter Jeremy
On 2000-Apr-14 22:49:40 +1000, Steve Ames [EMAIL PROTECTED] wrote: That's always struck me a bit odd... I thought 'MAKEDEV std' made the generic set of devices and that 'MAKEDEV all' should make... well.. _ALL_. *shrug* What do you define as `all'? Say I have a big FTP server with 8 wide SCSI

Re:cvs commit: src/sys/dev/ida ida_eisa.c

2000-04-14 Thread Matthew N. Dodd
On Fri, 14 Apr 2000, Viren R.Shah wrote: Here it is: mainboard0: CPQ1519 (System Board) on eisa0 slot 0 eisa0: unknown card CPQ6101 (0x0e116101) at slot 5 ida0: Compaq SMART array controller at 0x6000-0x60ff, 0x6c88-0x6c9e ida0: irq 15 (level) on eisa0 slot 6 ida0: drives=1 firm_rev=1.66

Re: Problems with MAKEDEV.

2000-04-14 Thread Neil Blakey-Milner
On Fri 2000-04-14 (18:34), David Scheidt wrote: Sure. What's the point of having both std and all, though? How much does it hurt to have a few extra device files kicking around? 'std' is standard devices (leaving out exotic ones), and 'all' is at least one of every device out there. Neil

Re: Problems with MAKEDEV.

2000-04-14 Thread Nate Williams
That's always struck me a bit odd... I thought 'MAKEDEV std' made the generic set of devices and that 'MAKEDEV all' should make... well.. _ALL_. *shrug* What do you define as `all'? Say I have a big FTP server with 8 wide SCSI controllers, each with 15 disks - that's da0..da119. I