Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Jason DiCioccio

I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old
floppy, I could set the parameters for ed0 and it would find ed0.. now it
doesn't find ed0 at all although it still finds 'unknown0' .. When you
fixed this freezing, did this ruin some other detection or something to
that effect?  I told it to probe 0x240 @ IRQ 7 which is where it is.. all
my bios settings etc have no changed since last time I used floppy (the
one that froze but still found ed0) ..

Thanks in advance,
Jason DiCioccio

On Sat, 9 Oct 1999, Doug Rabson wrote:

 On Sat, 9 Oct 1999, Jason DiCioccio wrote:
 
  
  Yes yes.. Long subject, but anyhow.. The problem I am having is that 4.0
  insists on detecting my ethernet card PnP at installation even though Id
  ont want it to.. When it does, it freezes up, and its much easier for me
  just to input the settings manually info the visual config.. I need to
  disable on install disk, or get a 4.0 floppy that doesn't freeze on
  'unknown0', of course, not having it detected at all would be preferable
  :)..
 
 There was a problem with the pnp code which caused freezes like this which
 I fixed. What date was the snap that you tried?
 
 --
 Doug Rabson   Mail:  [EMAIL PROTECTED]
 Nonlinear Systems Ltd.Phone: +44 181 442 9037
 
 
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: breakage in libgcc?

1999-10-10 Thread Poul-Henning Kamp


Sounds like you havn't -current.

In message [EMAIL PROTECTED], Mike Smith writes:
 just cvsupped

Your system; I just finished a world not five minutes ago.  Suspect the
usual.

 echo '#include xm-freebsd.h'  config.h
 echo '#include "i386/xm-i386.h"'  tconfig.h
 echo '#include "i386/i386.h"'  tm.h
 echo '#include "i386/att.h"'  tm.h
 echo '#include "i386/freebsd.h"'  tm.h
 echo '#include "i386/perform.h"'  tm.h
 cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC 
-I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o 
/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
 *** Signal 12
 
 Stop in /usr/src/gnu/lib/libgcc.
 *** Error code 1
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message


--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



scsi tape driver wants an update

1999-10-10 Thread Andy Farkas


Just a reminder I guess,

# uname -v
FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999

# mt retension

console emits (in bright white):

WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1")



--
 
 :{ [EMAIL PROTECTED]
  
Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/
  




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Doug Rabson

On Sun, 10 Oct 1999, Jason DiCioccio wrote:

 I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old
 floppy, I could set the parameters for ed0 and it would find ed0.. now it
 doesn't find ed0 at all although it still finds 'unknown0' .. When you
 fixed this freezing, did this ruin some other detection or something to
 that effect?  I told it to probe 0x240 @ IRQ 7 which is where it is.. all
 my bios settings etc have no changed since last time I used floppy (the
 one that froze but still found ed0) ..

To debug this, I need the output of dmesg and pnpinfo from a kernel which
exhibits the problem.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: maxphys = 0??

1999-10-10 Thread Daniel C. Sobral

Poul-Henning Kamp wrote:
 
 Meanwhile the mystery has been solved.  I was a miscommunication
 between sos and me.  He only committed one half of the fix for
 this issue.
 
 He has now committed the rest along with the latest version of
 his ata drivers (he claims :-)

Things are fine here now.

--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]

"I always feel generous when I'm in the inner circle of a
conspiracy to subvert the world order and, with a small group of
allies, just defeated an alien invasion. Maybe I should value myself
a little more?"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Signal breakage?

1999-10-10 Thread Mark Murray

Hi

On line 72 of signal.h, there is a reference to 'union sigval',
which is declared in sys/signal.h, but inside #ifndef _POSIX_SOURCE.
The X build heavily uses _POSIX_SOURCE, so this breaks.

Should line 72 of signal.h not move a little further down into
the #ifndef _POSIX_SOURCE block below it?

M


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Signal breakage?

1999-10-10 Thread Bruce Evans

 On line 72 of signal.h, there is a reference to 'union sigval',
 which is declared in sys/signal.h, but inside #ifndef _POSIX_SOURCE.
 The X build heavily uses _POSIX_SOURCE, so this breaks.
 
 Should line 72 of signal.h not move a little further down into
 the #ifndef _POSIX_SOURCE block below it?

This is supposed to be handled by a _POSIX_1B_VISIBLE feature test, but
the test is broken (nonexistent) in sys/signal.h.  Try changing the
ifdef for sigval fom _POSIX_SOURCE to _POSIX_1B_VISIBLE.

Bruce



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: staroffice

1999-10-10 Thread Nick Hibma

o unzip setup.zip to someplace comfortable
 
 Don't both with that.
 
 use "export LD_LIBRARY_PATH=/tmp/sv001.tmp:." before running the setup binary.
 ^^^

That number changes, so you might have to go into /tmp and delete stale
directories.

Nick
-- 
e-Mail: [EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: breakage in libgcc?

1999-10-10 Thread Randy Bush

 *** Signal 12
 Stop in /usr/src/gnu/lib/libgcc.
 *** Error code 1
 Suspect that you need a newer kernel before you can build the world.

had to
  o make new config
  o make new kernel
  o reboot
  o make world
  o ...

must have been an exciting time in current while i was on the road the last
three weeks. :-)

randy


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: breakage in libgcc?

1999-10-10 Thread Peter Wemm

Randy Bush wrote:
 just cvsupped
 
 echo '#include xm-freebsd.h'  config.h
 echo '#include "i386/xm-i386.h"'  tconfig.h
 echo '#include "i386/i386.h"'  tm.h
 echo '#include "i386/att.h"'  tm.h
 echo '#include "i386/freebsd.h"'  tm.h
 echo '#include "i386/perform.h"'  tm.h
 cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/
usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC 
-I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib
/libgcc/../../../contrib/egcs/gcc/libgcc1.c
 *** Signal 12
 
 Stop in /usr/src/gnu/lib/libgcc.
 *** Error code 1

You need to build a new kernel *before* you 'make world'.

Cheers,
-Peter



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Kerberized telnet not installed

1999-10-10 Thread Patrick Hartling

I just built and installed sources cvsup'd at 17:45 CDT October 9 with
${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed.  I
looked over the recent changes to add SRA to telnet, but I am not familiar
enough with the order in which things are built and installed to figure
out what happened.  I did notice that secure/usr.bin/telnet/Makefile was
brought back to life after being dead for about 3 years, but this was the
only change that really jumped out at me as being significant.  Is there
something new I need do to get a Kerberized telnet?  Thanks.

 -Patrick


Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ATA driver

1999-10-10 Thread Kenneth Culver

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 the kernel with make
-j8 and building gnomelibs):

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
Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error
Oct 10 12:29:51 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
- res
etting
Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. done
Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04
Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error
Oct 10 12:29:54 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
- res
etting
Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. DANGER
active=3
Oct 10 12:29:54 culverk /kernel: done
Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04
Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error
Oct 10 12:29:57 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
- res
etting
Oct 10 12:29:57 culverk /kernel: ata0: resetting devices .. done
Oct 10 12:32:03 culverk /kernel: sigreturn: eflags = 0x0

any ideas?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Jason DiCioccio

Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
show ed0 being probed at all.. In other words, it does nto even say 'ed0
not found at 0x240' .. And I am not deleting the device :-).. Are there
any conditions where this would happen?

Thanks

On Sun, 10 Oct 1999, Doug Rabson wrote:

 On Sun, 10 Oct 1999, Jason DiCioccio wrote:
 
  I just tried the latest -CURRENT snapshot, 19991009 ,.. Now, on the old
  floppy, I could set the parameters for ed0 and it would find ed0.. now it
  doesn't find ed0 at all although it still finds 'unknown0' .. When you
  fixed this freezing, did this ruin some other detection or something to
  that effect?  I told it to probe 0x240 @ IRQ 7 which is where it is.. all
  my bios settings etc have no changed since last time I used floppy (the
  one that froze but still found ed0) ..
 
 To debug this, I need the output of dmesg and pnpinfo from a kernel which
 exhibits the problem.
 
 --
 Doug Rabson   Mail:  [EMAIL PROTECTED]
 Nonlinear Systems Ltd.Phone: +44 181 442 9037
 
 
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



X-related panic

1999-10-10 Thread Patrick Hartling

For quite some time, I've been having panics while running X and never saw
the actual message.  This time, I happened to be in console mode when the
crash happened.  Here is the panic message:

kernel: type 12 trap, code=0
Stopped at pmap_remove_pages+0xd0: decl 0(%ecx)

The stack trace I got was:

pmap_remve_pages(c7bf1f28,0,bfbfe000,c7c42e6c,c7371034) at pmap_remove_pages+0xd0 
exec_new_vmspace(c7c42e6c,c7bd7700,3,c02388fc,4e070840) at exec_elf_imgact+0x109
execve(c7bd7700,c7c42f80,80f740c,,80f74c0) at execve+0x1fe
syscall(2f,2f,2f,80f74c0,) at syscall+0x199
Xint0x80_syscall() at Xint0x80_syscall()+0x31

Is this helpful?

 -Patrick


Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA driver

1999-10-10 Thread Soren Schmidt

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 the kernel with make
 -j8 and building gnomelibs):
 
 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
 Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error
 Oct 10 12:29:51 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
 - res
 etting
 Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. done
 Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04
 Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error
 Oct 10 12:29:54 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
 - res
 etting
 Oct 10 12:29:54 culverk /kernel: ata0: resetting devices .. DANGER
 active=3
 Oct 10 12:29:54 culverk /kernel: done
 Oct 10 12:29:54 culverk /kernel: ad1: status=51 error=04
 Oct 10 12:29:54 culverk /kernel: ad_interrupt: hard error
 Oct 10 12:29:57 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
 - res
 etting
 Oct 10 12:29:57 culverk /kernel: ata0: resetting devices .. done
 Oct 10 12:32:03 culverk /kernel: sigreturn: eflags = 0x0
 
 any ideas?
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Doug Rabson

On Sun, 10 Oct 1999, Jason DiCioccio wrote:

 Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
 show ed0 being probed at all.. In other words, it does nto even say 'ed0
 not found at 0x240' .. And I am not deleting the device :-).. Are there
 any conditions where this would happen?

Due to the nature of the pnp code, it might be probed as ed1 instead of
ed0. If at all possible, could you put the card into a working FreeBSD box
so that I can see the pnpinfo. If we are missing a pnp ID for the card,
I need that information to fix it.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Jason DiCioccio

Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
it should be on irq 7

On Sun, 10 Oct 1999, Doug Rabson wrote:

 On Sun, 10 Oct 1999, Jason DiCioccio wrote:
 
  Sorry I can't get pnpinfo, I can tell you though that dmesg does not even
  show ed0 being probed at all.. In other words, it does nto even say 'ed0
  not found at 0x240' .. And I am not deleting the device :-).. Are there
  any conditions where this would happen?
 
 Due to the nature of the pnp code, it might be probed as ed1 instead of
 ed0. If at all possible, could you put the card into a working FreeBSD box
 so that I can see the pnpinfo. If we are missing a pnp ID for the card,
 I need that information to fix it.
 
 --
 Doug Rabson   Mail:  [EMAIL PROTECTED]
 Nonlinear Systems Ltd.Phone: +44 181 442 9037
 
 
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA driver

1999-10-10 Thread Soren Schmidt

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

Uh oh, I had one of those once, no end of trouble, have you ever had
it working in any DMA mode reliably (mine wouldn't).. 
One possible solution is to tell the bios it is PIO3 only mode, the
ATA driver will then run DMA on it but with relaxed timing...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA driver

1999-10-10 Thread Kenneth Culver

It doesn't seem to have bad sectors...


found- vendor=0x109e, dev=0x036e, revid=0x02
class=04-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
intpin=a, irq=9
map[0]: type 3, range 32, base ea002000, size 12
found- vendor=0x109e, dev=0x0878, revid=0x02
class=04-80-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
intpin=a, irq=9
map[0]: type 3, range 32, base ea00, size 12
found- vendor=0x1011, dev=0x0009, revid=0x22
class=02-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=10
map[0]: type 4, range 32, base e400, size  7
map[1]: type 1, range 32, base ea001000, size  7
pci0: PCI bus on pcib0
pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0
found- vendor=0x8086, dev=0x7800, revid=0x21
class=03-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
intpin=a, irq=255
map[0]: type 3, range 32, base e600, size 24
map[1]: type 1, range 32, base e500, size 19
pci1: PCI bus on pcib1
vga-pci0: VGA-compatible display device at device 0.0 on pci1
isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0
isa0: ISA bus on isab0
ata-pci0: Intel PIIX4 IDE controller at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0: iobase=0x01f0 altiobase=0x03f6
ata0: mask=03 status0=50 status1=50
ata0: mask=03 status0=50 status1=50
ata0: devices = 0x3
ata0 at 0x01f0 irq 14 on ata-pci0
ata1: iobase=0x0170 altiobase=0x0376
ata1: mask=03 status0=50 status1=10
ata1: mask=03 status0=50 status1=10
ata1: devices = 0x9
ata1 at 0x0170 irq 15 on ata-pci0
chip1: UHCI USB controller irq 11 at device 7.2 on pci0
intpm0: Intel 82371AB Power management controller at device 7.3 on pci0
intpm0: I/O mapped 5000
intpm0: intr IRQ 9 enabled revision 0
smbus0: System Management Bus on intsmb0
smb0: SMBus general purpose I/O on smbus0
intpm0: PM I/O mapped 4000 
pci0: unknown card (vendor=0x121a, dev=0x0002) at 13.0
pci0: unknown card (vendor=0x121a, dev=0x0002) at 15.0
bktr0: BrookTree 878 irq 9 at device 17.0 on pci0
using shared irq9.
brooktree0: PCI bus latency is 64.
bktr0: buffer size 3555328, addr 0x500
bktr: GPIO is 0x00fb
subsytem 0x0070 0x13eb
bktr0: Hauppauge Model 61291 D110
Hauppauge WinCast/TV, Philips NTSC tuner, remote control.
pci0: unknown card (vendor=0x109e, dev=0x0878) at 17.1 irq 9
de0: Digital 21140A Fast Ethernet irq 10 at device 19.0 on pci0
de0: 21140A [10-100Mb/s] pass 2.2
de0: address 00:c0:f0:1f:21:02
bpf: de0 attached
fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1440-KB 3.5" drive on fdc0 drive 0
atkbdc0: keyboard controller (i8042) at port 0x60-0x6f on isa0
atkbd0: AT Keyboard irq 1 on atkbdc0
atkbd: the current kbd controller command byte 0047
atkbd: keyboard ID 0x41ab (2)
kbdc: RESET_KBD return code:00fa
kbdc: RESET_KBD status:00aa
kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d
psm0: current command byte:0047
kbdc: TEST_AUX_PORT status:
kbdc: RESET_AUX return code:00fa
kbdc: RESET_AUX status:00aa
kbdc: RESET_AUX ID:
psm: status 00 02 64
psm: status 00 00 64
psm: status 00 03 64
psm: status 00 03 64
psm: status 10 00 64
psm: data 08 00 00
psm: data 08 00 00
psm: status 00 02 64
psm0: PS/2 Mouse irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3-00, 3 buttons
psm0: config:, flags:, packet size:4
psm0: syncmask:c8, syncbits:08
vga0: Generic ISA VGA at port 0x3b0-0x3df iomem 0xa-0xb on isa0
fb0: vga0, vga, type:VGA (5), flags:0x7007f
fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa 0x2
fb0: init mode:24, bios mode:3, current mode:24
fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k
vga0: vga: WARNING: video mode switching is not fully supported on this adapter
VGA parameters upon power-up
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
VGA parameters in BIOS for mode 24
28 0b 10 ff ff 09 0f 00 0e eb 2d 27 28 90 2b 91 
bf 1f c0 9c 0e 8f 28 96 b9 01 01 01 01 00 28 0e 
10 ff ff 09 0f 00 0e eb 31 27 28 92 2c 90 05 3e 
c0 e9 0c df 28 e9 fc 02 01 01 01 00 32 11 10 ff 
EGA/VGA parameters to be used for mode 24
50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 
bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 
b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 
3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff 
sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x200
sc0: fb0 kbd0
sio0: irq maps: 0x41 0x51 0x41 0x41
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: irq maps: 0x41 0x49 0x41 0x41
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc: parallel port found at 0x378
ppc: chipset forced to generic
ppc0: EPP SPP
ppc0 at port 0x378-0x37f 

Re: ATA driver

1999-10-10 Thread Kenneth Culver

sure, as soon as i get a chance, I'll do that for ya.

Ken

On Sun, 10 Oct 1999, Soren Schmidt wrote:

 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
  Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error
 
 OK, it suggests that you have bad sectors on your drive, could you mail
 me your dmesg from a boot -v ?
 
 -Søren
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Doug Rabson

On Sun, 10 Oct 1999, Jason DiCioccio wrote:

 Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
 it should be on irq 7

Actually, we can put the card on any irq which it supports as long as
there isn't a conflict. Unless you have a sio1 in that box (which normally
uses irq 3), it is perfectly ok.

Your card is an SMC EtherEZ (8416). I think that needs some special extra
tricks to get it supported. Matt Dodd [EMAIL PROTECTED] was working on
this recently but I don't know if he has it working yet.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA driver

1999-10-10 Thread Soren Schmidt

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
 Oct 10 12:29:49 culverk /kernel: ad_interrupt: hard error

OK, it suggests that you have bad sectors on your drive, could you mail
me your dmesg from a boot -v ?

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA driver

1999-10-10 Thread Peter Wemm

Soren Schmidt wrote:
 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
 
 Uh oh, I had one of those once, no end of trouble, have you ever had
 it working in any DMA mode reliably (mine wouldn't).. 
 One possible solution is to tell the bios it is PIO3 only mode, the
 ATA driver will then run DMA on it but with relaxed timing...


Heh, Just looking at the linux ide driver:

const char *bad_ata66_4[] = {
"WDC AC310200R",
NULL
};

const char *bad_ata66_3[] = {
"WDC AC310200R",
NULL
};

const char *bad_ata33[] = {
"Maxtor 92720U8", "Maxtor 92040U6", "Maxtor 91360U4", "Maxtor 91020U3",
"Maxtor 90845U3", "Maxtor 90650U2",
"Maxtor 91360D8", "Maxtor 91190D7", "Maxtor 91020D6", "Maxtor 90845D5",
"Maxtor 90680D4", "Maxtor 90510D3", "Maxtor 90340D2",
"Maxtor 91152D8", "Maxtor 91008D7", "Maxtor 90845D6", "Maxtor 90840D6",
"Maxtor 90720D5", "Maxtor 90648D5", "Maxtor 90576D4",
"Maxtor 90510D4",
"Maxtor 90432D3", "Maxtor 90288D2", "Maxtor 90256D2",
"Maxtor 91000D8", "Maxtor 90910D8", "Maxtor 90875D7", "Maxtor 90840D7",
"Maxtor 90750D6", "Maxtor 90625D5", "Maxtor 90500D4",
"Maxtor 91728D8", "Maxtor 91512D7", "Maxtor 91303D6", "Maxtor 91080D5",
"Maxtor 90845D4", "Maxtor 90680D4", "Maxtor 90648D3", "Maxtor 90432D2",
NULL
};

Looks like the Maxtor's have a bit of a track record...

Cheers,
-Peter



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Matthew N. Dodd

On Sun, 10 Oct 1999, Doug Rabson wrote:
 Your card is an SMC EtherEZ (8416). I think that needs some special
 extra tricks to get it supported. Matt Dodd [EMAIL PROTECTED] was
 working on this recently but I don't know if he has it working yet.

I've got uncommitted patches that fix this I believe.  I need to go back
and test them before I commit but they should work.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Heads up!

1999-10-10 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], Assar Westerlund writes:
Poul-Henning Kamp [EMAIL PROTECTED] writes:
 We have now come so far that we can start to kill cdevsw_add()
 calls and rely on make_dev() for most of the device drivers.

So how is this supposed to work for device kld's?  Currently,
cdevsw_add() gets called from the glue generated by DEV_MODULE.

The same as for any other driver, once you find your hardware
you call make_dev() for it.

Use the variant of MODULE macro which doesn't take a cdevsw agument.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Heads up!

1999-10-10 Thread Assar Westerlund

Poul-Henning Kamp [EMAIL PROTECTED] writes:
 We have now come so far that we can start to kill cdevsw_add()
 calls and rely on make_dev() for most of the device drivers.

So how is this supposed to work for device kld's?  Currently,
cdevsw_add() gets called from the glue generated by DEV_MODULE.

/assar


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Matthew N. Dodd

On Sun, 10 Oct 1999, Matthew N. Dodd wrote:
 On Sun, 10 Oct 1999, Doug Rabson wrote:
  Your card is an SMC EtherEZ (8416). I think that needs some special
  extra tricks to get it supported. Matt Dodd [EMAIL PROTECTED] was
  working on this recently but I don't know if he has it working yet.
 
 I've got uncommitted patches that fix this I believe.  I need to go back
 and test them before I commit but they should work.

Ok, I've tested my patches and remembered why I didn't ever do anything
with them.

*** ISA_GET_RESOURCE(,,SYS_RES_MEMORY,...) failed (2)
unknown0: SMC EtherEZ (8416) at port 0x240-0x25f irq 9 on isa0

ed_probe_WD80x3() doesn't understand boards that have no shared memory.

While these cards work just fine in softset mode, turning on their PnP
features seems to disable the use of shared memory.

mihoshi# pnpinfo
Checking for Plug-n-Play devices...

Card assigned CSN #1
Vendor ID SMC8416 (0x1684a34d), Serial Number 0xbba8d5c1
PnP Version 1.0, Vendor Version 16
Device Description: SMC EtherEZ (8416)

Logical Device ID: SMC8416 0x1684a34d #0
Device supports I/O Range Check
IRQ: 3 5 7 9 10 11 IRQ: High true edge sensitive
I/O Range 0x240 .. 0x3e0, alignment 0x20, len 0x20
[not 16-bit addr]
End Tag

Successfully got 5 resources, 1 logical fdevs
-- card select # 0x0001

CSN SMC8416 (0x1684a34d), Serial Number 0xbba8d5c1

Logical device #0
IO:  0x0240 0x 0x 0x 0x 0x 0x 0x
IRQ 9 0
DMA 0 0
IO range check 0x00 activate 0x01

This output appears to agree with what Win95 finds.

I'm investigating the possibility of making ed_probe_WD80x3() a bit more
flexible.

-- 
| Matthew N. Dodd  | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD  |
| [EMAIL PROTECTED] |   2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent  | ISO8802.5 4ever |



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: X-related panic

1999-10-10 Thread Patrick Hartling

Patrick Hartling [EMAIL PROTECTED] wrote:

} For quite some time, I've been having panics while running X and never saw
} the actual message.  This time, I happened to be in console mode when the
} crash happened.

I meant to include that I'm using XFree86 3.3.5 built from the ports
collection with a kernel and userland built from sources cvsup'd at 17:45
CDT October 9.

 -Patrick


Patrick L. Hartling | Research Assistant, VRAC
[EMAIL PROTECTED] | Carver Lab - 0095E Black Engineering
http://www.137.org/patrick/ | http://www.vrac.iastate.edu/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: {a}sync updates (was Re: make install trick)

1999-10-10 Thread Tony Finch

I have noticed similarly odd behaviour from softupdates during heavy
IO load, where something is creating lots of little files or
directories and not much else is happening. Using `vmstat 1` I can see
that softupdates isn't very good at evening out the IO rate over time:
there's a roughly sinusoidal back-and-forth between frantic disk
thrashing (lots of TPS) and lots of syscall activity. Visible progress
is correspondingly uneven.

For example, the `vmstat 1` output while the script
for i in `jot 256`
do
for j in `jot 256`
do
mkdir -p $i/$j
done
done
is running is appended below. Behaviour is much smoother during an
`rm -r *` of the resulting directory tree.

Tony.
-- 
f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED]
  Apache Software Foundation Member

 procs  memory page   disksfaults  cpu
 r b w avm   fre  flt  re  pi  po  fr  sr da0 fd0 pa0   in   sy  cs us sy id
 2 1 0 4183836 11172 3389   0   0   0 3188   0 273   0   0  512 6015 1210 71 29  0
 1 1 0 4183836 11172  447   0   0   0 444   0 427   0   0  667 3198 1128 93  7  0
 1 1 0 4183836 11172  411   0   0   0 408   0 459   0   0  699 3424 1039 89 11  0
 1 1 0 4183836 11172  428   0   0   0 425   0 469   0   0  713 3430 1039 96  4  0
 2 0 0 4183832 2 3544   0   0   0 3285   0 296   0   0  535 6820 990 67 32  1
 3 0 0 4184036 11084 10155   0   0   0 9427   0  60   0   0  298 14837 1026 45 55  0
 2 0 0 4184044 11092 7856   0   0   0 7292   0   0   0   0  242 12077 1013 52 48  0
 3 0 0 4183588 11216 13700   0   0   0 12718   0   0   0   0  239 18826 960 26 74  0
 3 0 0 4184056 6 12824   0   0   0 11880   0   5   0   0  245 17635 977 35 65  0
 2 0 0 4183836 11164 8604   0   0   0 8011   0   1   0   0  242 12450 1008 55 45  0
 2 1 0 4183900 11168 5770   0   0   0 5386   0 189   0   0  428 9073 1241 57 43  0
 1 1 0 4183836 11168  497   0   0   0 489   0 472   0   0  712 3006 1107 91  9  0
 1 2 0 4183496 11136  502   0   0   0 483   0 577   0   0  829 3449 1059 88 12  0
 1 1 0 4183496 11156 1444   0   0   0 1365   0 538   0   0  779 4620 1049 86 14  0
 3 0 0 4183248 11120 11937   0   0   0 11068   0 107   0   0  344 16580 892 22 78  0
 2 0 0 4183308 11132 15356   0   0   0 14213   0   1   0   0  241 20742 979 18 82  0
 3 0 0 4183704 11048 12665   0   0   0 11713   0   0   0   0  239 17461 990 28 72  0
 2 0 0 4183492 11092 10878   0   0   0 10126   0  21   0   0  259 15238 986 45 55  0
 2 0 0 4183496 2 12151   0   0   0 11276   0  50   0   0  289 16767 982 28 72  0
 2 1 0 4183496 11144  422   0   0   0 425   0 510   0   0  756 2444 1217 84 16  0
 1 1 0 4183496 11100  475   0   0   0 462   0 575   0   0  820 3299 1131 87 13  0
 1 1 0 4183496 11092 1024   0   0   0 976   0 550   0   0  792 4130 1049 88 12  0
 3 0 0 4183648 11104 7254   0   0   0 6747   0 291   0   0  530 11196 949 53 47  0
 2 1 0 4183768 11140 12570   0   0   0 11678   0   5   0   0  249 17381 1002 33 67  0
 2 0 0 4183832 11028 13877   0   0   0 12846   0   7   0   0  249 18952 986 25 75  0
 2 0 0 4183648 11028 12263   0   0   0 11400   0  16   0   0  259 16964 1015 38 62  0
 3 0 0 4183768 11036 11108   0   0   0 10353   0   5   0   0  244 15567 1017 32 68  0
 3 0 0 4183836 10952 5932   0   0   0 5539   0 190   0   0  429 9087 1153 55 45  0
 2 1 0 4183836 10900  475   0   0   0 459   0 542   0   0  782 2865 1257 91  9  0
 1 2 0 4183768 10936  766   0   0   0 749   0 562   0   0  809 3732 1219 87 13  0
 1 1 0 4184312 10900  853   0   0   0 803   0 557   0   0  799 4189 1142 90 10  0
 2 0 0 4184124 10812 11847   0   0   0 10971   0 101   0   0  340 16642 969 29 71  0
 2 0 0 4184520 10720 8599   0   0   0 7976   0   6   0   0  244 13098 1065 48 52  0
 2 0 0 4184312 10732 7968   0   0   0 7410   0   5   0   0  242 12228 1034 50 49  1


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: installworld broken from R/O /usr/obj

1999-10-10 Thread Andrew Gallatin


Bruce Evans writes:
   W`hile installworld is being discussed, I wanted to get this out there:
   
   Since rev 1.13 of usr.bin/make/arch.c, I've been seing a problem with
   ELF archive libraries being rebuilt unnecessarily.  I believe that
   this problem can be traced to the RANLIBMAG string being set to "/".
  
  There's a PR about this now.  The smaller fix in the PR seems to work.

Ah yes, in bin/14167.  The fix is much tighter  appears to work.

--
Andrew Gallatin, Sr Systems Programmer  http://www.cs.duke.edu/~gallatin
Duke University Email: [EMAIL PROTECTED]
Department of Computer Science  Phone: (919) 660-6590






To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: PnP problems on install floppy in 4.0-SNAPS from current.freebsd.org

1999-10-10 Thread Jason DiCioccio

It worked when it was probed non-pnp :-).. As long as I set the params..
DId you get my email with pnpinfo and dmesg?

On Sun, 10 Oct 1999, Doug Rabson wrote:

 On Sun, 10 Oct 1999, Jason DiCioccio wrote:
 
  Another note :) .. PnP also probes unknown0 on the wrong irq (irq 3) while
  it should be on irq 7
 
 Actually, we can put the card on any irq which it supports as long as
 there isn't a conflict. Unless you have a sio1 in that box (which normally
 uses irq 3), it is perfectly ok.
 
 Your card is an SMC EtherEZ (8416). I think that needs some special extra
 tricks to get it supported. Matt Dodd [EMAIL PROTECTED] was working on
 this recently but I don't know if he has it working yet.
 
 --
 Doug Rabson   Mail:  [EMAIL PROTECTED]
 Nonlinear Systems Ltd.Phone: +44 181 442 9037
 
 
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: installworld broken from R/O /usr/obj

1999-10-10 Thread Andrew Gallatin


Julian Elischer writes:
  that fix was applied by me about 5 minutes ago..
  


Thank you!

Drew



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: installworld broken from R/O /usr/obj

1999-10-10 Thread Julian Elischer

that fix was applied by me about 5 minutes ago..


On Sun, 10 Oct 1999, Andrew Gallatin wrote:

 
 Bruce Evans writes:
W`hile installworld is being discussed, I wanted to get this out there:

Since rev 1.13 of usr.bin/make/arch.c, I've been seing a problem with
ELF archive libraries being rebuilt unnecessarily.  I believe that
this problem can be traced to the RANLIBMAG string being set to "/".
   
   There's a PR about this now.  The smaller fix in the PR seems to work.
 
 Ah yes, in bin/14167.  The fix is much tighter  appears to work.
 
 --
 Andrew Gallatin, Sr Systems Programmerhttp://www.cs.duke.edu/~gallatin
 Duke University   Email: [EMAIL PROTECTED]
 Department of Computer SciencePhone: (919) 660-6590
 
 
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Still waiting for xl driver reports

1999-10-10 Thread Bill Paul

A while back I posted a message here saying that I'd changed the xl driver
a bit to hopefully improve performance for 3c90xB and later adapters (i.e.
the "cyclone," "hurricane" and "tornado" chipsets). I asked for people
to report if the changes helped, hurt, made no difference or were totally 
broken.

So far not one person has said so much as a word to me on this subject.

I need feedback from people so that I know it's safe to merge this
stuff into -stable, so let's hear it already. It's been several weeks
since I made the changes. Surely there are people running -current
with 3Com 3c90xB cards.

To reiterate, this only concerns people with the following adapters:

- 3c905B-TX 10/100
- 3c905B-FX/SC fiber optic
- 3c905B-COMBO 10/100 plus BNC and AUI
- 3c905C-TX 10/100
- 3c980-TX server adapter
- 3c980B-TX server adapter
- 3c980C-TX server adapter
- 3cSOHO100-TX 10/100

To a lesser extent it also concerns people with these adapters (these
are 10Mbps only so the change isn't likely to be as noticable):

- 3c900B-TPO twisted pair only
- 3c900B-TPC twisted paid and coax (BNC)
- 3c900B-COMBO twisted pair, AUI and BNC
- 3c900B-FL fiber optic

Ideally, the changes should provide slightly faster performance with
less CPU usage. Performance/CPU overhead comparisons with other cards
(in the same machine!) would he helpful as well as comparisons with
the same 3Com card using the older driver revision.

Things that would not be helpful include:

- Asking about an unrelated problem from 3.2-RELEASE, 3.3-RELEASE or
  3.3-STABLE.

- Telling me that your card isn't detected properly and not realizing
  that you have "plug and play OS" set to "yes" in your BIOS config.

- Asking about a completely different card. From a completely different
  manufacturer.

- Saying that you'll be happy to run some tests "as soon as you find
  some time." If you couldn't find the time by now, you never will.

- Giving me an excuse for not sending me any feedback earlier. I
  don't care if your dog got run over, your house was invaded by
  giant ants, your entire family contracted the bubonic plague or
  aliens stole your computer.

- Asking me how to set up a 3Com card in Linux. (Comparing the xl
  driver's performance with the Linux 3Com driver is acceptable,
  provided you run the comparison on the same hardware. Comparing
  a PIII 600Mhz host running Linux to a PII 300Mhz host running
  FreeBSD is not a fair comparison. Unless FreeBSD ends up being
  faster. :)


-Bill

-- 
=
-Bill Paul(212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home:  [EMAIL PROTECTED] | Columbia University, New York City
=
 "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Nate Williams

 I Can't believe this email only produced TWO responses!
 I would have thought that this wouldhav brought out the chainsaws!
 Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't
 work? (the only responders got it via 'core')

Interesting.  It appears that somehow I got 'unsubscribed' from arch.
Not sure why, but in May I was subscribed, but I'm no longer subscribed.

Did everyone get unsubscribed when it went idle?

(I'm not commenting on the content as I haven't done enough research to
agree/disagree with anything yet.)


Nate


 
 julian
 
 On Sat, 9 Oct 1999, Bruce Evans wrote:
 
   PHK has been moving steadily in this direction to remove as many 
   dependencies within the kernel on block devices as possible.
   The question is, When did the decision to do so become official?
  
  Never.
  
   I don't believe it has been a stated official decision yet and so in order
   to put some clarity into the air over this I'd like to launch a PURELY
   TECHNICAL discussion on the topic.
   
   Here are some starters.
   
1/ block device writes have to be synchrnous or the user doesn't get
   write errors.
  
  Block devices should be implmented properly or the user doesn't get write
  errors.
  
  A proper implementation is quite close.  Write errors should be reported
  on last-close and on fsync().  They already are as far as I can see, modulo
  the bugs that (in -current) VOP_FSYNC() = ffs_fsync() sometimes hangs
  instead of returning a write error and vinvalbuf() sometimes panics instead
  of returning a write error.  The bugs are different and worse in RELENG_3.
  The bugs are different and more benign in RELENG_2_2 (write errors are
  ignored).  Note that the bugs have very little to do with specfs.  All
  specfs can reasonably do is kill the endless retries at a suitable time,
  probably after calling vinvalbuf() in last-close.
  
1A/ if they are not synchronous, errors need to be coped with in some
   other manner.
  
  Normal error handling suffices, modulo bugs.
  
2/ People with old UNIX experience expect to be able to do unalligned
   transfers on block devices. 
3/ DEVFS can cope just fine with block and char devices
   (I include this because DEVFS has been used as an argument for
   removing them)
  
  Correct.
  
4/ Most of the block buffering code in the kernel will remain due to 
   the VM and VFS systems.
  
  Well, if the Nth rewrite of vm wants to drop support for buffers in vfs,
  then use of buffers for block devices shouldn't stop it.
  
5/ New users don't tend to understand the rather strange distinctions
   between BLK and CHR devices. Some people consider having both POLA and
  
  This is an argument for removing character (disk) devices, since most
  new users will be from Linux where block (disk) devices were the only
  ones available until recently.  Block devices have always worked better
  in Linux.  E.g., media change is detected for floppies, and buffers
  remain valid across last-close, until media change.  The latter behaviour
  can be not what is wanted (extra ioctls are needed to discard the buffers),
  but it is often useful.
  
   others consider having only one POLA. Linux had til just recently,
   only BLK disk devices. They just aded CHR disk devices but I don't
   know if they created a whole second calss of device to do so. (I doubt it)
   6/  It should be possible to make an overlay device (similar to the way
   ccd works), that supplies buffered characteristics to a disk. This may
   be a different minor number or a differnt major number.. but be a CHR
   type device.
  
  This would involve needless duplicatication of half of the buffer cache
  implementation (maybe the simple half) unless the buffer cache goes away.
  
  Bruce
  
  
 
 
 


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-10 Thread Nate Williams

Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't
work? (the only responders got it via 'core')
   
   Interesting.  It appears that somehow I got 'unsubscribed' from arch.
   Not sure why, but in May I was subscribed, but I'm no longer subscribed.
   
   Did everyone get unsubscribed when it went idle?
  
  Not *everybody*, at least - my subscription has kept.  I do not know
  of any mass-unsubscription.
 
 Hmm, weird.  I can see that the 'old' list of people was saved on hub as
 'freebsd-arch.19990501', of which I'm a member.  However, I never
 received the email Simon Shapiro sent out in June that I just read, so I
 know I was removed then.

I note that David is no longer on the list ([EMAIL PROTECTED] was
'unsubscribed, either accidentally or intentionally).  Justin is gone,
and many other folks I would have considered to be folks interested that
were once subscribed...



Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: People getting automatically unsub'ed from -arch

1999-10-10 Thread Nate Williams

 [Mayhaps too many Cc:'s kept in order to reach relevant audience]

Thanks, sorry about the X-posting...

 On Sun, Oct 10, 1999 at 02:57:55PM -0600, Nate Williams wrote:
   I Can't believe this email only produced TWO responses!
   I would have thought that this wouldhav brought out the chainsaws!
   Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't
   work? (the only responders got it via 'core')
  
  Interesting.  It appears that somehow I got 'unsubscribed' from arch.
  Not sure why, but in May I was subscribed, but I'm no longer subscribed.
  
  Did everyone get unsubscribed when it went idle?
 
 Not *everybody*, at least - my subscription has kept.  I do not know
 of any mass-unsubscription.

Hmm, weird.  I can see that the 'old' list of people was saved on hub as
'freebsd-arch.19990501', of which I'm a member.  However, I never
received the email Simon Shapiro sent out in June that I just read, so I
know I was removed then.

I also note that freebsd-arch is the only 'list' that has a backup copy,
so *something* happened, and someone knew about it.  (I'm not implying
that it was intentional to remove people, or what, but *something*
happened and there was no mention of it...)



Nate


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



People getting automatically unsub'ed from -arch

1999-10-10 Thread Eivind Eklund

[Mayhaps too many Cc:'s kept in order to reach relevant audience]

On Sun, Oct 10, 1999 at 02:57:55PM -0600, Nate Williams wrote:
  I Can't believe this email only produced TWO responses!
  I would have thought that this wouldhav brought out the chainsaws!
  Maybe no-one is listenning on 'arch' any more, or maybe 'arch' doesn't
  work? (the only responders got it via 'core')
 
 Interesting.  It appears that somehow I got 'unsubscribed' from arch.
 Not sure why, but in May I was subscribed, but I'm no longer subscribed.
 
 Did everyone get unsubscribed when it went idle?

Not *everybody*, at least - my subscription has kept.  I do not know
of any mass-unsubscription.

Eivind, ex-moderator and now pseudo-moderator of -arch.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Oliver Fromme

Nate Williams wrote in list.freebsd-current:
  Interesting.  It appears that somehow I got 'unsubscribed' from arch.
  Not sure why, but in May I was subscribed, but I'm no longer subscribed.
  
  Did everyone get unsubscribed when it went idle?

FWIW, I got unsubscribed, too.  While I were at it, I sent a
"which" command to the majordomo, and the result did not list
me as a member of freebsd-announce and freebsd-security-
notifications.  When I tried to re-subscribe, it told me that
I am already subscribed...

Seems like majordomo is major buggy.  ;-)

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Jonathan M. Bresler

 
 FWIW, I got unsubscribed, too.  While I were at it, I sent a
 "which" command to the majordomo, and the result did not list
 me as a member of freebsd-announce and freebsd-security-
 notifications.  When I tried to re-subscribe, it told me that
 I am already subscribed...
 
 Seems like majordomo is major buggy.  ;-)
 
 Regards
Oliver

youare subscribed to freebsd-announce as
[EMAIL PROTECTED] which oes not match the email
address that you sent your which request from
"[EMAIL PROTECTED]", therefore majordomo did not show
your addresses as subscribed.

i expect that you get the rest of the mail via newsgate.
again you are not subscribed, so majordomo does not show your address
in response to a which.

this is not a majordomo bug.

jmb


 
 -- 
 Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
 (Info: finger userinfo:[EMAIL PROTECTED])



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Majordomo problems (Re: The eventual fate of BLOCK devices.)

1999-10-10 Thread Peter Jeremy

On 1999-Oct-11 08:35:41 +1000, Oliver Fromme wrote:
Nate Williams wrote in list.freebsd-current:
  Interesting.  It appears that somehow I got 'unsubscribed' from arch.
  Not sure why, but in May I was subscribed, but I'm no longer subscribed.
  
  Did everyone get unsubscribed when it went idle?

FWIW, I got unsubscribed, too.

Same here.

  While I were at it, I sent a
"which" command to the majordomo, and the result did not list
me as a member of freebsd-announce and freebsd-security-
notifications.

I did the same and also found significant differences between the
mailing lists that I am receiving mail from and the ones that
majordomo thinks I am subscribed to.  I sent a note to
[EMAIL PROTECTED] last Friday, but haven't seen anything
back yet (I'm not particularly fussed).

Peter
-- 
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St  Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015   Fax:   +61 2 9690 5982


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Still waiting for xl driver reports

1999-10-10 Thread John Birrell

On Sun, Oct 10, 1999 at 04:59:34PM -0400, Bill Paul wrote:
 I need feedback from people so that I know it's safe to merge this
 stuff into -stable, so let's hear it already. It's been several weeks
 since I made the changes. Surely there are people running -current
 with 3Com 3c90xB cards.
 
 To reiterate, this only concerns people with the following adapters:
 
 - 3c905B-TX 10/100

I installed 3.2-RELEASE and upgraded to 4.0-CURRENT on a new machine
last week. The machine came with NT installed - it is far more useful
running FreeBSD. 8-)

I can't comment about the relative performance, because I have 
nothing to compare it against. It works fine for me. 

-- 
John Birrell - [EMAIL PROTECTED]; [EMAIL PROTECTED] http://www.cimlogic.com.au/
   [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Majordomo problems (Re: The eventual fate of BLOCK devices.)

1999-10-10 Thread Jonathan M. Bresler


send it to postmaster instead.

jmb


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Oliver Fromme

Jonathan M. Bresler wrote in list.freebsd-current:
   FWIW, I got unsubscribed, too.  While I were at it, I sent a
   "which" command to the majordomo, and the result did not list
   me as a member of freebsd-announce and freebsd-security-
   notifications.  When I tried to re-subscribe, it told me that
   I am already subscribed...
   
   Seems like majordomo is major buggy.  ;-)
  
   youare subscribed to freebsd-announce as
  [EMAIL PROTECTED] which oes not match the email
  [...]

Oh, I'm very sorry for the confusion.  When I said "I", I
really did not mean myself but the local newsgate (I prefer
to read the lists via NNTP, which is very convenient).

The newsgate is "[EMAIL PROTECTED]".
I sent both the "which" and the "subscribe" commands under
that address, when the problem occured that I described in
my previous mail (see above).  I'm pretty sure that I didn't
do anything wrong.

Here's the whole story:

 - I sent a "which" command from the newsgate account.

 - Got a response with about 30 lists to which that account
   is subscribed.

 - Compared those lists to the lists that the newsgate
   is prepared to handle (and to which it was once subscribed).

 - Noticed that three lists were missing:  announce, arch, and
   security-notifications.

 - Sent "subscribe" commands for those three lists to the
   majordomo, again using the newsgate account.

 - Re-subscription to the -arch list was successful.  For the
   other two lists, I received a notice that I (the newsgate
   account) was already subscribed.

   this is not a majordomo bug.

It is.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
 (Terry Pratchett)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Jonathan M. Bresler

 
 Here's the whole story:
 
  - I sent a "which" command from the newsgate account.
 
  - Got a response with about 30 lists to which that account
is subscribed.
 
  - Compared those lists to the lists that the newsgate
is prepared to handle (and to which it was once subscribed).
 
  - Noticed that three lists were missing:  announce, arch, and
security-notifications.

arch and security-notifications do not honor which requests.

 
  - Sent "subscribe" commands for those three lists to the
majordomo, again using the newsgate account.
 
  - Re-subscription to the -arch list was successful.  For the
other two lists, I received a notice that I (the newsgate
account) was already subscribed.

correct.

 
  this is not a majordomo bug.
 
 It is.

sigh

jmb


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: How do I get a PCCARD modem to work?

1999-10-10 Thread Justin T. Gibbs

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

The pccard brokenness is not sio's fault.  If I were following where
our PCCARD support was going, I might take a stab at fixing this myself...
Perhaps I'll learn more at FreeBSD-con.

--
Justin



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Archie Cobbs

Jonathan M. Bresler writes:
  Here's the whole story:
  
   - I sent a "which" command from the newsgate account.
  
   - Got a response with about 30 lists to which that account
 is subscribed.
  
   - Compared those lists to the lists that the newsgate
 is prepared to handle (and to which it was once subscribed).
  
   - Noticed that three lists were missing:  announce, arch, and
 security-notifications.
   
   arch and security-notifications do not honor which requests.

It sounds like it would be nice then to have majordomo add a note
to its response indicating this. Is that possible to configure?

-Archie

___
Archie Cobbs   *   Whistle Communications, Inc.  *   http://www.whistle.com


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: The eventual fate of BLOCK devices.

1999-10-10 Thread Matthew Dillon

:  6/  It should be possible to make an overlay device (similar to the way
:  ccd works), that supplies buffered characteristics to a disk. This may
:  be a different minor number or a differnt major number.. but be a CHR
:  type device.
: 
: This would involve needless duplicatication of half of the buffer cache
: implementation (maybe the simple half) unless the buffer cache goes away.
: 
: Bruce

It should be noted that the current implementation of block devices is
fairly trivial, only a few dozen lines of code.  I agree with Bruce:  it
would be silly to throw that away and spend days rewriting it.  There
is nothing wrong with block device's that can't be trivially fixed other
then the fact that Poul seems rabidly intent on destroying them, and there
isn't anything wrong with using filesystem buffers either.

It should also be noted that in order to maintain cache coherency 
between read/write and mmap() on a block device, you either have to go
through the buffer cache or you have to rewrite considerably more then
just specfs.

There are several trivial ways to solve the write-error problem.  First, 
implement writes as write-through so a synchronous error can be returned.
Second, implement an error code on close.  There are other possibilities 
as well, such as implementing a single buffer pipeline and returning a
delayed error, which preserves some of the write pipelining performance, 
or implementing an intermediate backing layer (such as swap) to buffer 
errored blocks for later retrieval.  There are also situations where
errors can be assumed to not occur, such as when using buffered VN
partition which is backed by a file or swap.

It isn't inconceivable that the methodology could be selected with an
ioctl(), with the write-through-synchronous-return for writes made the
default.  This is all of a dozen lines of code.

-Matt



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



MajorDomo Problems

1999-10-10 Thread Tom Embt


I've been mysteriously unsubscribed from -questions sometime between Oct
7th and Oct 10th.  My guess puts it at late morning/early afternoon EDT on
the 7th.

It would seem something is up...  good thing somebody mentioned the 'which'
command (I'd never heard of it), I was wondering why noone was responding
to an earlier post ;)


Tom Embt
[EMAIL PROTECTED]



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: MajorDomo Problems

1999-10-10 Thread Alex

Tom Embt wrote:
 
 I've been mysteriously unsubscribed from -questions sometime between Oct
 7th and Oct 10th.  My guess puts it at late morning/early afternoon EDT on
 the 7th.
 
 It would seem something is up...  good thing somebody mentioned the 'which'
 command (I'd never heard of it), I was wondering why noone was responding
 to an earlier post ;)


Hey - I was unsubscribed from -cvs-all, -advocacy, -emulation, -hackers,
-mobile, -multimedia, -new-bus, -announce and -stable!  In other words,
ALL mailing lists I was subscribed to except -current.

This happened twice!  The first time was a couple of weeks ago - I just
ignored it and resubscribed - but having to do it again is just too
much!  Please do something about it, sort it out!  It really sucks
having to acknowledge every subscribe request and then receive a whole
bunch of confirmation messages.

Alex


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: scsi tape driver wants an update

1999-10-10 Thread Matthew Jacob


Huh?

I'll check it out..


On Sun, 10 Oct 1999, Andy Farkas wrote:

 
 Just a reminder I guess,
 
 # uname -v
 FreeBSD 4.0-CURRENT #0: Sun Oct 10 16:16:34 EST 1999
 
 # mt retension
 
 console emits (in bright white):
 
 WARNING: driver sa should register devices with make_dev() (dev_t = "#sa/1")
 
 
 
 --
  
  :{ [EMAIL PROTECTED]
   
 Andy Farkas
 System Administrator
Speednet Communications
  http://www.speednet.com.au/
   
 
 
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kerberized telnet not installed

1999-10-10 Thread Mark Murray

 I just built and installed sources cvsup'd at 17:45 CDT October 9 with
 ${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed.  I
 looked over the recent changes to add SRA to telnet, but I am not familiar
 enough with the order in which things are built and installed to figure
 out what happened.  I did notice that secure/usr.bin/telnet/Makefile was
 brought back to life after being dead for about 3 years, but this was the
 only change that really jumped out at me as being significant.  Is there
 something new I need do to get a Kerberized telnet?  Thanks.

Please send me the output of

# ldd /usr/bin/telnet

Thanks!

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Kerberized telnet not installed

1999-10-10 Thread Mark Murray

 I just built and installed sources cvsup'd at 17:45 CDT October 9 with
 ${MAKE_KERBEROS4} enabled, but the Kerberized telnet was not installed.  I
 looked over the recent changes to add SRA to telnet, but I am not familiar
 enough with the order in which things are built and installed to figure
 out what happened.  I did notice that secure/usr.bin/telnet/Makefile was
 brought back to life after being dead for about 3 years, but this was the
 only change that really jumped out at me as being significant.  Is there
 something new I need do to get a Kerberized telnet?  Thanks.

I found the problem. I'll commit later on today.

M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: staroffice

1999-10-10 Thread Edwin Culp

I just installed it out of curiosity.  Everything went well until I try to execute
it.  It starts as if it were going to work and then it gives me a core dump with a
message box that says, "An unrecoverable error has occurred.  All modified files
have been saved and probably can be recovered at reset" .  My Linux emulation is
working fine.  I am using linux netscape 4.7 with glibc and many linux plugins with
no problems.

Anyone else seeing that.

Thanks,

ed

Nick Hibma wrote:

 o unzip setup.zip to someplace comfortable
 
  Don't both with that.
 
  use "export LD_LIBRARY_PATH=/tmp/sv001.tmp:." before running the setup binary.
  ^^^

 That number changes, so you might have to go into /tmp and delete stale
 directories.

 Nick
 --
 e-Mail: [EMAIL PROTECTED]

 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: staroffice

1999-10-10 Thread Johan Karlsson

At Sun, 10 Oct 1999 23:40:04 PDT, Edwin Culp wrote:
I just installed it out of curiosity.  Everything went well until I try to exe
cute
it.  It starts as if it were going to work and then it gives me a core dump wi
th a
message box that says, "An unrecoverable error has occurred.  All modified fil
es
have been saved and probably can be recovered at reset" .  My Linux emulation 
is
working fine.  I am using linux netscape 4.7 with glibc and many linux plugins
 with
no problems.

Anyone else seeing that.


This happend to me, removing the dir Office51 in my home directory solved it.

/K

-- 
Johan Karlsson  mailto:[EMAIL PROTECTED]
SWEDEN




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message