Cross patches
I've had a bunch of requests for what I'm using to cross build. I've put up the cross compilation development patches that I have done so far at http://www.village.org/villagers/imp/freebsd-cross-1.patch.gz for anybody to give a test spin. There are no directions, but if you do a make buildworld TARGET=i386 TARGET_ARCH=i386 on an alpha, you should get a complete i386 world that can be installed on a i386 machine. It is critically important that you include both the TARGET and TARGET_ARCH on the command line, otherwise this won't work. They patch the two files that I needed to patch to get the cross building stuff working. However, note that so far I've not gotten past building the libraries on mips, due to kernel include files I've not written/imported yet, so I don't know how far it will make it. I release these patches in the hopes they are useful. I don't know if this is the direction that FreeBSD wants to take wrt cross building binaries or not. It is certainly a good learning experience. I also don't know if our tools are up to the task of generating working alpha code on a i386 box. I got all kinds of warnings when I tried to do that which lead me to believe that the answer was no (things like shifts > 32 bits). Please let me know what you think of these patches. If you have updates to them, please let me know. I'd have to characterize them as a "rapid prototyping learning experience" at the moment. However, every time I tried to do something more elegant I ran into boatloads of problems. Warner To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
Brian Feldman wrote: > > > > I just wish april would go away, very, very fast... > > > > > Here's a challenge to help you get by the rest of the days, figure out > > how to write my name, in its original form I was given at birth :-) > > Hmm... is it cheating to use Hiragana? (^_^) Being a chinese name (I think -- not a japanese one, for sure), I don't think it will help. Besides, you can't spell an L in hiragana. :-) My own take is (japanese characters -- sorry, no chinese input) 陳 for Chen. For Luoqi, japanese shift-jis/euc-jp just won't do. Well, I cheated, anyway... -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Problems with symbol sequences in recent kernels
I've just had a strange experience. I have some gdb macros which I use for debugging Vinum. One, ps, gives me a ps-like listing: (kgdb) ps Check your .gdbinit, it contains a y command pidprocaddr uid ppid pgrp flag stat comm wchan 1544 c68a5100 c6df30000 1534 1544 004006 2 Vinum 1534 c68a57e0 c6ddb0000 1524 1534 004086 3 bash wait c68a57e0 1524 c68a5c00 c6dc9000 1004 1516 1524 004086 3 bash wait c68a5c00 Another macro helps me load symbols from a kld: Without: (kgdb) bt #0 Debugger (msg=0xc11696a0 "vinum debug") at ../../i386/i386/db_interface.c:318 #1 0xc1163585 in ?? () #2 0xc01826ea in spec_ioctl (ap=0xc6df4e1c) at ../../miscfs/specfs/spec_vnops.c:440 With: (kgdb) bt #0 Debugger (msg=0xc11696a0 "vinum debug") at ../../i386/i386/db_interface.c:318 #1 0xc1163585 in vinumioctl (dev=0x40001901, cmd=0xc008464b, data=0xc6df4ee0 "", flag=0x3, p=0xc68a5100) at /src/PANIC/src/sys/modules/Vinum/../../dev/Vinum/vinumioctl.c:96 #2 0xc01826ea in spec_ioctl (ap=0xc6df4e1c) at ../../miscfs/specfs/spec_vnops.c:440 This has worked quite nicely for some time. Since yesterday, after building a kernel with newbus support, I get strange messages if I read in the Vinum symbols before reading in the kernel symbols: (kgdb) bt #0 Debugger (msg=0xc11696a0 "vinum debug") at ../../i386/i386/db_interface.c:318 #1 0xc1163585 in vinumioctl (dev=0x40001901, cmd=0xc008464b, data=0xc6df4ee0 "", flag=0x3, p=0xc68a5100) at /src/PANIC/src/sys/modules/Vinum/../../dev/Vinum/vinumioctl.c:96 During symbol reading, "repeated" header file opt_global.h not previously seen, at symtab pos 23. During symbol reading, Invalid symbol data: type number (2,2) out of range at symtab pos 25.. #2 0xc01826ea in spec_ioctl (ap=0xc6df4e1c) at ../../miscfs/specfs/spec_vnops.c:440 The following stack frames also look strange: #5 0xc017ccdd in vn_ioctl (fp=, com=, data=, p=) at vnode_if.h:395 #6 0xc015c5f7 in ioctl (p=0xc68a5100, uap=0xc6df4f94) at ../../kern/sys_generic.c:564 #7 0xc021e916 in syscall (frame=) at ../../i386/i386/trap.c:1071 I debugged gdb and found that it was finding these references (opt_global.h) in cd9660_rrip.o, which it read after reading the Vinum kld symbols. If I can convince it to read the kernel symbols first, I don't have any trouble. I don't think that it's anything to do with that particular file; there must be about 30 files in a typical kernel build which refer to this symbol. If I don't get any response on the list, I'll put in a PR, but I thought there's a good chance that somebody will recognize this problem and be able to fix it. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: pcm broken
Ken, I can't offer you any help, just moral support :P - mine just broke too. Same message. Andrew. On Thu, 22 Apr 1999, Kenneth Wayne Culver wrote: > Date: Thu, 22 Apr 1999 22:50:46 -0400 (EDT) > From: Kenneth Wayne Culver > To: freebsd-current@freebsd.org > Subject: Re: pcm broken > > For some reason, when I rebuilt the kernel after a cvsup this morning, > sound will no longer work. It gives this kernel warning when I try to play > sound: > > timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x00c1 > > sound worked fine yesterday, before I cvsupped. > > Can anyone give me an idea as to what happened here? Any help would be > appreciated. > > Thanks. > > Kenneth Culver > > > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
On Thu, Apr 22, 1999 at 02:01:35AM -0700, Amancio Hasty wrote: >Just a kind reminder we can unplug and plug a usb mouse as >well as a usb keyboard currently we have a small problem with >moused that it does not attempt to gain access of the mouse if there >is a usb disconnect / connect sequence. I'll let you OS guys sort that out with moused first :-). We have an X server extension that allows a pointer device to be reopened (and reconfigured) This was intended mainly for use by configuration tools, but it could be used by some daemon to tell the X server to reopen the mouse, and maybe change its parameters. It might turn out that it is easier to handle this solely within moused, and just configure the X server to use moused. We'll keep this sort of thing in mind as we rework the input device handling for XFree86 4.0. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
On Thu, 22 Apr 1999, Luoqi Chen wrote: > > Steve Kargl wrote: > > > > > > > > That's a little foolish since we've still not found all the egcs > > > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > > > work! :-) > > > > > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > > > > > > > "Luigi" is an interesting spelling of "Louqi". > > > > To my defense, I thought it was Louqi, but since I have been making > > a lot of mistaken comments lately, I decided to trust what Jordan > > has said... > > > I thought you guys had better things to do other than arguing about how > to spell my name. None of them is correct anyway, it is not even in > alphabets... > > > I just wish april would go away, very, very fast... > > > Here's a challenge to help you get by the rest of the days, figure out > how to write my name, in its original form I was given at birth :-) Hmm... is it cheating to use Hiragana? (^_^) > > > -- > > Daniel C. Sobral(8-DCS) > > d...@newsguy.com > > d...@freebsd.org > > > > "Well, Windows works, using a loose definition of 'works'..." > > > > -lq > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Thu, 22 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > >> Hmm, I have a ZIP here which works, and I have reports from mike that > >> his LS120 works too, so I'm a bit confused here. > >> How does it not work ?? > > > >I get consistent errors reading from it (not hard errors, data errors). The > >md5 checksums I created on the disk using the wd driver do not match the > >varying checksums md5 gives me on the LS-120 with the new ATA. > > Hmm, does it still work with the old driver ?? Yep, flawlessly. > Does it share the channel with another device ?? (ata/atapi??) ata0: master: settting up UDMA2 mode on Aladdin chip OK ad0: ATA-4 disk at ata0 as master ad0: 6103MB (12500460 sectors), 13228 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode ata1: slave: settting up WDMA2 mode on Aladdin chip OK ad3: ATA-? disk at ata1 as slave ad3: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad3: piomode=4, dmamode=2, udmamode=-1 ad3: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata0 as slave acd0: drive speed 2067KB/sec, 128KB cache acd0: supported read types: CD-R, CD-DA acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked afd0: rewriteable drive at ata1 as master afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: Unknown media (0x0) > It sounds like a HW problem of some sort to me.. > Or one that's exacerbated by the new drivers. > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: pcm broken
For some reason, when I rebuilt the kernel after a cvsup this morning, sound will no longer work. It gives this kernel warning when I try to play sound: timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x00c1 sound worked fine yesterday, before I cvsupped. Can anyone give me an idea as to what happened here? Any help would be appreciated. Thanks. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
IMPT HELP: maxproc at 128
/etc/login.conf has a default entry of unlimited for maxproc. I need more processes to be run (in the kernel config the MAXUSER is 256). please help, jay To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Boot error
Ayan George wrote: > Ever since installing 4.0-CURRENT, I've gotten the following > message when I boot FreeBSD: > > Disk error 0x1 (lba=0x12007f) > No /boot/loader > > >> FreeBSD/i386 BOOT > Default: 0:wd(0,a)kernel > > boot: > > > If I type: > > wd(0,a)/boot/loader > > at the boot prompt, it claims it cant find the file but I know it > exists. > > I can load the kernel from the boot prompt however. I've tried > rebuilding /boot/loader from newer source to no avail. > > There is obviously something I'm overlooking. Has anyone else seen > this problem and know how to fix it? > > -Ayan Disk error 0x1 means "invalid argument". The most likely cause is that your / filesystem spans cylinder 1023 and /boot/loader is inaccessible for this reason. -- Robert Nordier To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
pcm broken
For some reason, when I rebuilt the kernel after a cvsup this morning, sound will no longer work. It gives this kernel warning when I try to play sound: timeout flushing dbuf_out, chan 1 cnt 0xff00 flags 0x00c1 sound worked fine yesterday, before I cvsupped. Thanks. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: NFSv3 seriously broken in 3.1
:> Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP. :> AMD defaults to tcp. : :I made a commit to -STABLE a few weeks ago (but not -CURRENT) that should :have made v3/udp the default. : :-- :-- David(obr...@nuxi.com -or- obr...@freebsd.org) Ah, cool. I'll bet the author was using the 3.1 CD's Fixing TCP is on the list, but probably won't happen for a while ( though if other people want to take a crack at it I'll accept patches ). -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: NFSv3 seriously broken in 3.1
> Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP. > AMD defaults to tcp. I made a commit to -STABLE a few weeks ago (but not -CURRENT) that should have made v3/udp the default. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
New IDE drivers problem
Hi: As I had stated earlier, the new IDE drivers broke on me yesterday. I have done some investigation and discovered that the ATA driver no longer believes I have any devices on ata1 (I think!). I have included the dmesg text. Any help in solving the problem would be greatly appreciated. Rick Whitesel Scientist NBase-Xyplex rwhite...@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Thu Apr 22 16:05:29 EDT 1999 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff real memory = 268435456 (262144K bytes) avail memory = 258252800 (252200K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc031b000. Pentium Pro MTRR support enabled, default memory type is uncacheable Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 chip0: at device 0.0 on pci0 chip1: at device 1.0 on pci0 isab0: at device 4.0 on pci0 ata-pci0: at device 4.1 on pci0 ata-pci0: type=71118086 class=01 subclass=01 cmd=0285 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 ata1: mask=03 status0=a5 status1=50 ata1: mask=03 status0=50 status1=50 ata1: devices = 0x0 chip2: at device 4.3 on pci0 ahc0: at device 6.0 on pci0 ahc0: interrupting at irq 19 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs fxp0: at device 9.0 on pci0 fxp0: interrupting at irq 19 fxp0: Ethernet address 00:a0:c9:b7:be:e9 fxp1: at device 10.0 on pci0 fxp1: interrupting at irq 18 fxp1: Ethernet address 00:a0:c9:b7:bf:5f hea0: at device 11.0 on pci0 hea0: interrupting at irq 17 isa0: on motherboard fdc0: interrupting at irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 atkbdc0: at port 0x60 on isa0 atkbd0: on atkbdc0 atkbd0: interrupting at irq 1 psm0: on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 psm0: interrupting at irq 12 vga0: on isa0 sc0: on isa0 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 sio2: not probed (disabled) sio3: not probed (disabled) ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppc0: interrupting at irq 7 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 ds0 XXX: driver didn't set ifq_maxlen SMP: AP CPU #1 Launched! ata0: master: settting up UDMA2 mode on PIIX4 chip OK ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 31 depth queue, DMA mode Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) changing root device to wd0s1a To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: NFSv3 seriously broken in 3.1
:Symptoms are the following: We upgraded a perfectly running 2.2.7 client :to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging :for ten, twenty seconds, even five minutes or more. : :Adding the NFSv2 compatibility option to the AMD tables solved the :problem. : :Gerald :-- :Gerald "Jerry" pfei...@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ It's really hard to say. It kinda sounds like it is trying to use a tcp connection. Make sure AMD is compiled/configured to use UDP with NFSV3, not TCP. AMD defaults to tcp. -Matt Matthew Dillon To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
3.1-STABLE is currently broken
... because usr.bin/colldef/data/de_DE.DIS_8859-15.src has been updated:
# $Id: de_DE.DIS_8859-15.src,v 1.3.2.1 1999/04/22 08:34:03 foxfair Exp $
without the corresponding update to scan.l and parse.y in the colldef
source. End result:
===> usr.bin/colldef/data
colldef -I /usr/src/usr.bin/colldef/data -o de_DE.DIS_8859-15.out
/usr/src/usr.bin
/colldef/data/de_DE.DIS_8859-15.src
colldef: syntax error near line 6
*** Error code 69
Stop.
*** Error code 1
This is from a 3.1-RELEASE box, attemtping a buildworld to 3.1-STABLE.
Using usr.bin/colldef/data/{scan.l,parse.y} from -CURRENT and generating
colldef from these seems to fix the problem.
Steinar Haug, Nethelp consulting, sth...@nethelp.no
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
ncr scsi doesn't boot
Here's what it is under 2.2.8: Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 ncr0 rev 1 int a irq 11 on pci0:1:0 The following snapshots fail to find it: 3.1-19990421-STABLE no disks found, no PCI probes done 4.0-19990418-CURRENT gets to visual configuration but no PCI probing. 4.0-19990420-CURRENT gets to visual configuration but no PCI probing. 4.0-19990421-CURRENT after visual configuration, it stops at "rootfs is 2880 bytes compiled in MFS". No PCI probes at all. Doesn't get to visual configuration At that point, I gave up. cheers. btw: this is the new NZ mirror I'm trying to set up. Mind you, we can always run it on 2.2.8. But I'd prefer 3.1. -- Dan Langille - DVL Software Limited The FreeBSD Diary - http://www.FreeBSDDiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Boot error
Ayan George wrote: > > Ever since installing 4.0-CURRENT, I've gotten the following What were you running before? How did you make the upgrade? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: nice little kernel task for somebody
> Here's a thing I've missed a couple of times: I'd like to be > able to see the limits for a process in /proc. I'd like to be able to open processes file discriptors too (so you can still get files back if all the filsystem references to it have gone, but a process still has it open). I might have a go at doing both - if it isn't too Linuxesque. David. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
newbus resource manager
< said: > Can newbus resource manager manage discontinuouse I/O port? > Many PC-98 devices use discontinuous I/O port like: > 0x00d0, 0x10d0, 0x20d0, 0x30d0, 0x40d0, ..., 0xf0d0 > Current API seems to assume contiguity and not to be able to manage > such I/O port addresses. Each one of these is a single port, so it needs to be reserved individually. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
newbus - kernel compile failure (old + new PCI drivers)
Since the newbus changes, I have had kernel compile failures, due to
the fact that I don't have any old style PCI drivers configured
on my system. By #ifdef'ing out the code that wraperises the
old driver code.
Diffs are as follows (this requires defining "NOOLDPCIDRIVERS").
Obviously, this code should eventually all disappear, but is there
a more elegant way of doing things at the moment? Are these
changes worth committing?
*** pci.c.orig Mon Apr 19 08:21:08 1999
--- pci.c Wed Apr 21 23:41:33 1999
***
*** 846,851
--- 846,852
#include "pci_if.h"
+ #if !defined(NOOLDPCIDRIVERS)
/*
* A simple driver to wrap the old pci driver mechanism for back-compat.
*/
***
*** 921,928
--- 922,932
{ 0, 0 }
};
+ #endif
+
static devclass_t pci_devclass;
+ #if !defined(NOOLDPCIDRIVERS)
/*
* Create a new style driver around each old pci driver.
*/
***
*** 946,951
--- 950,956
devclass_add_driver(pci_devclass, driver);
}
}
+ #endif
/*
* New style pci driver. Parent device is either a pci-host-bridge or a
***
*** 1330,1336
--- 1335,1343
{
switch (what) {
case MOD_LOAD:
+ #if !defined(NOOLDPCIDRIVERS)
pci_wrap_old_drivers();
+ #endif
break;
case MOD_UNLOAD:
*** userconfig.c.orig Wed Apr 21 23:45:28 1999
--- userconfig.cWed Apr 21 23:41:22 1999
***
*** 570,575
--- 570,576
insdev(&scratch,ap[i].id_enabled?active:inactive);
}
#if NPCI > 0
+ #if !defined(NOOLDPCIDRIVERS)
for (i = 0; i < pcidevice_set.ls_length; i++)
{
if (pcidevice_set.ls_items[i])
***
*** 595,600
--- 596,602
}
}
}
+ #endif
#endif/* NPCI > 0 */
}
--
Geoff Rehmet, The Internet Solution - Infrastructure
tel: +27-11-283-5462, fax: +27-11-283-5401 mobile: +27-83-292-5800
email: geo...@is.co.za
URL: http://www.is.co.za
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Boot error
All, Ever since installing 4.0-CURRENT, I've gotten the following message when I boot FreeBSD: Disk error 0x1 (lba=0x12007f) No /boot/loader >> FreeBSD/i386 BOOT Default: 0:wd(0,a)kernel boot: If I type: wd(0,a)/boot/loader at the boot prompt, it claims it cant find the file but I know it exists. I can load the kernel from the boot prompt however. I've tried rebuilding /boot/loader from newer source to no avail. There is obviously something I'm overlooking. Has anyone else seen this problem and know how to fix it? -Ayan To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
Hi: I built a version that removed the SCSI and ATM support with no change. Something has changed such that only one channel of the PCI IDE controller is reported. I will continue my investigation. Rick - Original Message - From: Soren Schmidt To: Christopher Masto Cc: Sent: Wednesday, April 21, 1999 2:47 AM Subject: Re: New ATA driver and crash dumps It seems Christopher Masto wrote: > My machine panicked today for the first time since switching to the > new ATA drivers, and I noticed that I no longer have crash dumps. > Is this something that is expected to be put back in soon? > > I know Søren's a busy guy, and I'm glad we have the results of his > work. I just hope the old drivers don't get killed off until the > replacement has the same functionality. > > Then again, wddump() is only 100 lines of code, so I should probably > try to fix it myself before whining. I know :), it has just not been done yet. It will be done eventually but I have other areas in the driver I want finish first. Also the old wd driver will probably not be killed off entirely, as its the only one we have that support old ST506/ESDI drives. -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: NFSv3 seriously broken in 3.1
On Thu, 22 Apr 1999 00:51:03 +0200, Gerald Pfeifer wrote: > Symptoms are the following: We upgraded a perfectly running 2.2.7 client > to 3.1, and out of a sudden NFS performed sluggish, sometimes even hanging > for ten, twenty seconds, even five minutes or more. > > Adding the NFSv2 compatibility option to the AMD tables solved the > problem. CURRENT has been giving me similar problems that weren't (as) obvious in 2.2-STABLE . I've found two client-side work-arounds to improve the situation: 1) Use ``opts:=vers=2,soft,intr'' in /etc/amd.map (see the AMD info page for more details). 2) Don't use AMD. Use direct mounts out of /etc/fstab, eg: src.noc:/a/ncvs /home/ncvs nfs soft,intr 0 0 This causes an apparent hang during FreeBSD boot if the server is unavailable (eg: network fault). Otherwise, all I can suggest is patience. :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: _my_ world is broken
>On Thu, 22 Apr 1999, Alexander Leidinger wrote:
>
>
>unsetenv CXXFLAGS
>
>I don't know if you're supposed to be able to make world with this
>variable set, but it screws up several things at present. I tripped
>over this myself a few weeks back.
>
>Kris
>
Look in /usr/share/mk/sys.mk and you will find:
CXXFLAGS?= ${CXXINCLUDES} ${CFLAGS}
So if you want your CFLAGS used for CXX you do nothing. If you need
to set some specific CXXFLAGS that you don't want set in CFLAGS then
you need to make sure that you also have ${CXXINCLUDES} listed on your
CXXFLAGS line.
--
Glenn Johnson
Technician
USDA, ARS, SRRC
New Orleans, LA
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
> Steve Kargl wrote: > > > > > > That's a little foolish since we've still not found all the egcs > > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > > work! :-) > > > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > > > > "Luigi" is an interesting spelling of "Louqi". > > To my defense, I thought it was Louqi, but since I have been making > a lot of mistaken comments lately, I decided to trust what Jordan > has said... > I thought you guys had better things to do other than arguing about how to spell my name. None of them is correct anyway, it is not even in alphabets... > I just wish april would go away, very, very fast... > Here's a challenge to help you get by the rest of the days, figure out how to write my name, in its original form I was given at birth :-) > -- > Daniel C. Sobral (8-DCS) > d...@newsguy.com > d...@freebsd.org > > "Well, Windows works, using a loose definition of 'works'..." > -lq To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
Steve Kargl wrote: > > > > That's a little foolish since we've still not found all the egcs > > > optimizer bugs and whatnot; didn't you guys see the one Luigi found > > > the other day for ftpd? Now *that* had to be some obscure debugging > > > work! :-) > > > > Clearly, that goes to show Luigi must have no life... :-) > > > > "Luigi" is an interesting spelling of "Louqi". To my defense, I thought it was Louqi, but since I have been making a lot of mistaken comments lately, I decided to trust what Jordan has said... I just wish april would go away, very, very fast... -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org "Well, Windows works, using a loose definition of 'works'..." To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New IDE
Hi: No change. I forget to mention that there is an ATM card in the system. I am going to build a version that does not support the ATM card or the SCSI. I will let you know what happens. Rick - Original Message - From: Soren Schmidt To: Rick Whitesel Cc: Sent: Thursday, April 22, 1999 9:45 AM Subject: Re: New IDE It seems Rick Whitesel wrote: > Hi: > I am using /sys/dev/ata/ata-all.c rev 1.11. All this worked just fine > with the new IDE drivers until yesterday. Hmm, wierd, I see no problems here.. Try do a config -r configfile, make depend, make and see if the problem is still there... -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
On Thu, 22 Apr 1999, Daniel Eischen wrote:
> I have to echo these feelings. NFS, as both server and client, is
> working without noticeable problems for us under the old 2.2-stable.
> I am afraid of upgrading to 3.1-stable with the reported NFS problems,
> and we can't get by without NFS.
I was refering to the find/grep problem - I tried to start a thread in
sta...@freebsd.org...
> Dan Eischen
> eisc...@vigrid.com
>
>
--
:{ an...@speednet.com.au
Andy Farkas
System Administrator
Speed Internet Services
http://www.speednet.com.au/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: New IDE
It seems Rick Whitesel wrote: > Hi: > I am using /sys/dev/ata/ata-all.c rev 1.11. All this worked just fine > with the new IDE drivers until yesterday. Hmm, wierd, I see no problems here.. Try do a config -r configfile, make depend, make and see if the problem is still there... -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
nice little kernel task for somebody
Here's a thing I've missed a couple of times: I'd like to be able to see the limits for a process in /proc. Any takers ? -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New IDE
Hi: I am using /sys/dev/ata/ata-all.c rev 1.11. All this worked just fine with the new IDE drivers until yesterday. Rick - Original Message - From: Soren Schmidt To: Rick Whitesel Cc: Sent: Thursday, April 22, 1999 9:11 AM Subject: Re: New IDE It seems Rick Whitesel wrote: > Hi: > I have been using the new IDE drivers on a ASUS P2B-DS (Dual P II > with Adaptec SCSI) motherboard without any problems until yesterday > afternoon. I noticed that when I booted up yesterday afternoon with the > latest build that I no longer had a IDE CD-ROM. In fact dmesg shows that > only one controller channel is found, e.g. ata-pci0, ata0 and ad0. I > reverted to the "standard" IDE drivers and everything was fine. Anyone have > any ideas what has happened? Be sure you have /sys/dev/ata/ata-all.c rev 1.10 or later, there was problems in the first round of Peters changes.. -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: _my_ world is broken
On Thu, 22 Apr 1999, Alexander Leidinger wrote: > c++ -Os -march=pentium -pipe -Wall -fexpensive-optimizations > -fomit-frame-pointer -funroll-loops -I/ > usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -c > /usr/src/gnu/lib/libgcc/../.. > /../contrib/egcs/gcc/cp/exception.cc -o exception.o > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:33: > eh-common.h: No such file or d > irectory > /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:89: syntax > error before `;' unsetenv CXXFLAGS I don't know if you're supposed to be able to make world with this variable set, but it screws up several things at present. I tripped over this myself a few weeks back. Kris - The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New IDE
It seems Rick Whitesel wrote: > Hi: > I have been using the new IDE drivers on a ASUS P2B-DS (Dual P II > with Adaptec SCSI) motherboard without any problems until yesterday > afternoon. I noticed that when I booted up yesterday afternoon with the > latest build that I no longer had a IDE CD-ROM. In fact dmesg shows that > only one controller channel is found, e.g. ata-pci0, ata0 and ad0. I > reverted to the "standard" IDE drivers and everything was fine. Anyone have > any ideas what has happened? Be sure you have /sys/dev/ata/ata-all.c rev 1.10 or later, there was problems in the first round of Peters changes.. -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
New IDE
Hi: I have been using the new IDE drivers on a ASUS P2B-DS (Dual P II with Adaptec SCSI) motherboard without any problems until yesterday afternoon. I noticed that when I booted up yesterday afternoon with the latest build that I no longer had a IDE CD-ROM. In fact dmesg shows that only one controller channel is found, e.g. ata-pci0, ata0 and ad0. I reverted to the "standard" IDE drivers and everything was fine. Anyone have any ideas what has happened? Rick Whitesel Scientist NBase-Xyplex rwhite...@nbase-xyplex.com "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
PNP and CURRENT-19990421
Hi all, I CVSUP'd last night (4-21-99) to the latest and greatest. I created a completely new kernel configuration file based upon GENERIC and LINT. My problem arose when I added the support for "pnp0". I have a Yamaha sound card (pcm0) which needs PNP. When compiling the kernel, it failed with an error saying the PNP something or other was already defined (sorry, I don't have the output). The funny thing is I went in my configuration file and removed the reference to "pnp0" and recompiled. The kernel compiled just fine and the computer boots ok. However, during the boot process the kernel was doing pnp probes of the hardware. Is PNP a permanant and mandatory feature in the kernel now? If not, how do I remove it? At some point I will take a snapshot of current and put it on my old 486/ISA box (no pnp). Tom Veldhouse ve...@visi.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Temporary fix for PCCARD's to work...
Below find a quick fix that makes PCCARD work again.
Beware that if you have it compiled in the kernel you should
remove the kldload in /etc/rc.pccard, as it will happily
load the module, and screw up the whole situation...
Index: i386/isa/intr_machdep.c
===
RCS file: /home/ncvs/src/sys/i386/isa/intr_machdep.c,v
retrieving revision 1.19
diff -u -r1.19 intr_machdep.c
--- intr_machdep.c 1999/04/21 07:26:27 1.19
+++ intr_machdep.c 1999/04/23 11:16:30
@@ -877,6 +877,7 @@
free(irec, M_DEVBUF);
return -1;
}
+ isareclist[intr] = irec;
return 0;
}
Index: pccard/pccard.c
===
RCS file: /home/ncvs/src/sys/pccard/pccard.c,v
retrieving revision 1.73
diff -u -r1.73 pccard.c
--- pccard.c1999/03/10 15:00:54 1.73
+++ pccard.c1999/04/23 11:18:23
@@ -527,7 +527,7 @@
if (!(mask & imask))
continue;
INTRMASK(*maskp, mask);
- if (register_pcic_intr(irq, 0, 0, hand, maskp, unit) == 0) {
+ if (register_pcic_intr(irq, unit, 0, hand, maskp, unit) == 0) {
/* add this to the PCIC controller's mask */
if (pcic_imask)
INTRMASK(*pcic_imask, (1 << irq));
Index: pci/pcisupport.c
===
RCS file: /home/ncvs/src/sys/pci/pcisupport.c,v
retrieving revision 1.100
diff -u -r1.100 pcisupport.c
--- pcisupport.c1999/04/20 11:36:36 1.100
+++ pcisupport.c1999/04/23 11:20:40
@@ -1166,7 +1166,9 @@
if (pci_get_class(dev) == PCIC_BRIDGE
&& pci_get_subclass(dev) != PCIS_BRIDGE_PCI
&& pci_get_subclass(dev) != PCIS_BRIDGE_ISA
- && pci_get_subclass(dev) != PCIS_BRIDGE_EISA)
+ && pci_get_subclass(dev) != PCIS_BRIDGE_EISA
+ && pci_get_subclass(dev) != PCIS_BRIDGE_PCMCIA
+ && pci_get_subclass(dev) != PCIS_BRIDGE_CARDBUS)
return pci_bridge_type(dev);
return NULL;
-Søren
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
> "Daniel" == Daniel O'Connor writes: Daniel> On 22-Apr-99 Amancio Hasty wrote: >> The problem was not really a bios problem not sure what the guys >> did to fix the boot loader probably switch to using a dos int function >> to access the keyboard from the boot loader. Daniel> Hmm.. what does it do now? Just talk to the keyboard Daniel> controller directly? The BIOS I have here have an option Daniel> 'Port 60/64 emulation' in the USB related section...
Re: New ATA driver and crash dumps
It seems Brian Feldman wrote: >> Hmm, I have a ZIP here which works, and I have reports from mike that >> his LS120 works too, so I'm a bit confused here. >> How does it not work ?? > >I get consistent errors reading from it (not hard errors, data errors). The >md5 checksums I created on the disk using the wd driver do not match the >varying checksums md5 gives me on the LS-120 with the new ATA. Hmm, does it still work with the old driver ?? Does it share the channel with another device ?? (ata/atapi??) It sounds like a HW problem of some sort to me.. -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Thu, 22 Apr 1999, Soren Schmidt wrote: > It seems Brian Feldman wrote: > > >This and atapi-fd not working are the only hang-ups I have with using ATA. > >Heck, the benefits even outweigh that since my new UDMA2 hard drive is only > >supported with your wonderful new ATA drivers, not wd! The Aladdin support > >works great. > > Is there any way I can help in getting the atapi-fd driver to work with > >LS-120's? > > Hmm, I have a ZIP here which works, and I have reports from mike that > his LS120 works too, so I'm a bit confused here. > How does it not work ?? I get consistent errors reading from it (not hard errors, data errors). The md5 checksums I created on the disk using the wd driver do not match the varying checksums md5 gives me on the LS-120 with the new ATA. > > -S?ren > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
It seems Brian Feldman wrote: >This and atapi-fd not working are the only hang-ups I have with using ATA. >Heck, the benefits even outweigh that since my new UDMA2 hard drive is only >supported with your wonderful new ATA drivers, not wd! The Aladdin support >works great. > Is there any way I can help in getting the atapi-fd driver to work with >LS-120's? Hmm, I have a ZIP here which works, and I have reports from mike that his LS120 works too, so I'm a bit confused here. How does it not work ?? -Søren To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: New ATA driver and crash dumps
On Wed, 21 Apr 1999, Soren Schmidt wrote: > It seems Christopher Masto wrote: > > My machine panicked today for the first time since switching to the > > new ATA drivers, and I noticed that I no longer have crash dumps. > > Is this something that is expected to be put back in soon? > > > > I know S?ren's a busy guy, and I'm glad we have the results of his > > work. I just hope the old drivers don't get killed off until the > > replacement has the same functionality. > > > > Then again, wddump() is only 100 lines of code, so I should probably > > try to fix it myself before whining. > > I know :), it has just not been done yet. It will be done eventually > but I have other areas in the driver I want finish first. This and atapi-fd not working are the only hang-ups I have with using ATA. Heck, the benefits even outweigh that since my new UDMA2 hard drive is only supported with your wonderful new ATA drivers, not wd! The Aladdin support works great. Is there any way I can help in getting the atapi-fd driver to work with LS-120's? > > Also the old wd driver will probably not be killed off entirely, as > its the only one we have that support old ST506/ESDI drives. > > -S?ren > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
> People desperate for current functionality can wait, back port themselves or > run current. I have taken all three options in the past :-) I agree. I have recently installed 3.1-STABLE on two machines, and in each case the ethernet drivers (xl and lnc) had been broken since 3.1 (both are now fixed). Stable is already not stable enough! -- Richard To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers files)
> This is the only thing stopping me from upgrading our production machines > to 3.1-STABLE. > > Please, please, please backport these fixes! I have to echo these feelings. NFS, as both server and client, is working without noticeable problems for us under the old 2.2-stable. I am afraid of upgrading to 3.1-stable with the reported NFS problems, and we can't get by without NFS. Some serious consideration should be given to fix the NFS problems in 3.1 - at least to make it more reliable. Perhaps there can be well announced unstable periods of -stable for things like merging non-trivial changes from -current? Dan Eischen eisc...@vigrid.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: LINT Question
>LINT has two versions of values for ports. One is in quotes and the >other is not. > >For example, > >device npx0at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 >device sio0at isa? port "IO_COM1" tty flags 0x10 irq 4 > >The definition of IO_NPX and IO_COM1 have the same form in >sys/isa/isareg.h, sys/i386/isa/isa.h, etc. > >Some time back, someone posted guidance like "if it contains letters >and numbers, quote it, otherwise don't." More precisely, quote if it contains multiple tokens and multiple tokens are not wanted, otherwise don't. `IO_COM1' contains 2 tokens, `IO_COM' and `1' so not quoting would give the same syntax error as `port IO_COM 1'. >Which form should be used for these values? Follow the rule. >LINT shows ppc0 as a device and 'man ppc' says it is a controller. I >believe earlier versions of LINT had ppc as a controller. Which is >correct? `controller' was correct, but it didn't matter. new-bus may change this. >sio1 is not in LINT, but it is in GENERIC. Some devices like fd have >both fd0 and fd1. Since two serial ports is common should LINT have >sio1? Newer machines are more likely to have two serial ports than >two floppy drives. LINT is not supposed to show all devices. It is for testing that all code at least compiles. It needs to show sio1 as much as it needs to show sio65535 (not). Bruce To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
Hi David! Just a kind reminder we can unplug and plug a usb mouse as well as a usb keyboard currently we have a small problem with moused that it does not attempt to gain access of the mouse if there is a usb disconnect / connect sequence. Regards -- Amancio Hasty ha...@star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
On Thu, Apr 22, 1999 at 10:18:13AM +0200, Nick Hibma wrote: >I've heard of no one trying, but I (we!) would love to hear whether you >get this to work. > >There is not problem is using two keyboards at the same time, but I am >not sure whether X can already handle more than one keyboard attached to >a system. I don't think that you can specify the keyboard /dev/ entry >int he X configuration. That's correct, but we're planning to allow the Device to be specified in XFree86 4.0. >Try looking at the XFree pages. I remember someone asking me whether >this would be possible soon in FreeBSD because they were working on >support for multiple keyboards. Supporting multiple keyboards with a single X server should be relatively easy. Supporting multiple X servers on the same host will be difficult because of video hardware resource sharing/control issues, specifically for the legacy VGA resources. In our initial approach with XFree86 4.0, the X server will assume control of all of the VGA-compatible video hardware so that it can do the necessary coordination of access to the VGA resources. As Amancio implied, it should be possible to do better than that for hardware that has a PCI class/subclass that indicates no VGA core. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
_my_ world is broken
Hi, _my_ world breaks with: c++ -Os -march=pentium -pipe -Wall -fexpensive-optimizations -fomit-frame-pointer -funroll-loops -I/ usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -c /usr/src/gnu/lib/libgcc/../.. /../contrib/egcs/gcc/cp/exception.cc -o exception.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:33: eh-common.h: No such file or d irectory /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:89: syntax error before `;' /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:156: type specifier omitted for pa rameter /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:156: parse error before `*' /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc: In function `void * __cplus_type_ matcher(...)': /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: `exception_table' undeclared (first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: (Each undeclared identifier i s reported only once /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: for each function it appears in.) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:160: `EH_LANG_C_plus_plus' undecla red (first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:163: `match_info' undeclared (firs t use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:163: `CATCH_ALL_TYPE' undeclared ( first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:164: `info' undeclared (first use this function) /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/exception.cc:168: confused by earlier errors, b ailing out *** Error code 1 My last finished world is from Apr, 7 and since then I wasn't able to build the world anymore. First I thought I have to rebuild cc as described in UPDATING, so I did: foreach i ( /usr/src/includes /usr/src/lib /usr/src/gnu/usr.bin/cc ) cd $i make clean cleandir depend make make install clean cleandir end After that I tried to make the world again, but it fails. If I change eh-common.h to ../eh-common.h it fails too, but a little bit later. What am I doing wrong? Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
That might be the case however I and Viren R. Shah have found out that with the lastest current we can indeed talk to the bootloader which we couldn't before. The only thing which change in my computer was a cvsup update ,i.e., I did not touch my bios setting nor do I have an AT keyboard attached. > > I am quite sure that you using the legacy USB keyboard support of your > BIOS. The USB keyboard can not kick in before the PCI probes have been > done. > > Nick > > > On Wed, 21 Apr 1999, Amancio Hasty wrote: > > > Hi, > > > > >is now. My only concern is that the FreeBSD bootloader does not appear > > > > If you are running -current as of at least last nite you will not have > > any problems with the bootloader and your USB keyboard in fact > > I just rebooted my test system and was able to select the kernel > > to boot; previously, you are right the bootloader didn't work with > > a USB keyboard only system. > > > > > > -- > > > > Amancio Hasty > > ha...@star-gate.com > > > > > > > -- Amancio Hasty ha...@star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
I've heard of no one trying, but I (we!) would love to hear whether you get this to work. There is not problem is using two keyboards at the same time, but I am not sure whether X can already handle more than one keyboard attached to a system. I don't think that you can specify the keyboard /dev/ entry int he X configuration. Try looking at the XFree pages. I remember someone asking me whether this would be possible soon in FreeBSD because they were working on support for multiple keyboards. Nick On Thu, 22 Apr 1999, Mikhail Teterin wrote: > Viren R. Shah once stated: > > =Amancio and Nick helped me get my system with only a USB keyboard and > =USB mouse up and running. Right now I'm pretty happy with the way it is > =now. My only concern is that the FreeBSD bootloader does not appear to > =see keystrokes from the USB keyboard (which kinda makes it difficult to > =switch OSes on an USB only system). > > Provided I configure two video cards not to conflict, can I use > two USB keyboard and two USB mice (or one USB and one usual of > each) and run two independent X-servers? Two instances of sc? > > Thanks! > > -mi > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
LINT Question
I think I mis-directed this earlier. I am running 4.0-current SMP as of Apr 21. LINT has two versions of values for ports. One is in quotes and the other is not. For example, device npx0at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 device sio0at isa? port "IO_COM1" tty flags 0x10 irq 4 The definition of IO_NPX and IO_COM1 have the same form in sys/isa/isareg.h, sys/i386/isa/isa.h, etc. Some time back, someone posted guidance like "if it contains letters and numbers, quote it, otherwise don't." Which form should be used for these values? LINT shows ppc0 as a device and 'man ppc' says it is a controller. I believe earlier versions of LINT had ppc as a controller. Which is correct? sio1 is not in LINT, but it is in GENERIC. Some devices like fd have both fd0 and fd1. Since two serial ports is common should LINT have sio1? Newer machines are more likely to have two serial ports than two floppy drives. tomdean To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
I am quite sure that you using the legacy USB keyboard support of your BIOS. The USB keyboard can not kick in before the PCI probes have been done. Nick On Wed, 21 Apr 1999, Amancio Hasty wrote: > Hi, > > >is now. My only concern is that the FreeBSD bootloader does not appear > > If you are running -current as of at least last nite you will not have > any problems with the bootloader and your USB keyboard in fact > I just rebooted my test system and was able to select the kernel > to boot; previously, you are right the bootloader didn't work with > a USB keyboard only system. > > > -- > > Amancio Hasty > ha...@star-gate.com > > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
buildworld as normal user...
well, I just completed buildworld as a normal user, and would like to
recieve comments on various fixes...
a) create GAMEGRP in bsd.own.mk and change games in
games/Makefile.inc to use ${GAMEGRP}
b) add conditional of NOFSCHG in addition to PRECIOUSLIB in
bsd.lib.mk so libdes and friends try to be installed with
schg flag set
these are the only two that I came across... I have attached patches
that I created to fix them... also attached is my dobuildworld script
that I use to start the whole process...
comments?
I am thinking of changing NOFSCHG to NOSCHG, but I was just doing the
patch real quickly...
--
John-Mark Gurney Voice: +1 541 684 8449
Cu Networking P.O. Box 5693, 97405
"The soul contains in itself the event that shall presently befall it.
The event is only the actualizing of its thought." -- Ralph Waldo Emerson
Index: src/share/mk/bsd.lib.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.lib.mk,v
retrieving revision 1.86
diff -u -r1.86 bsd.lib.mk
--- bsd.lib.mk 1999/03/23 03:06:25 1.86
+++ bsd.lib.mk 1999/04/22 05:47:01
@@ -262,7 +262,7 @@
beforeinstall:
.endif
-.if defined(PRECIOUSLIB)
+.if defined(PRECIOUSLIB) && !defined(NOFSCHG)
SHLINSTALLFLAGS+= -fschg
.endif
Index: src/share/mk/bsd.own.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.own.mk,v
retrieving revision 1.22
diff -u -r1.22 bsd.own.mk
--- bsd.own.mk 1999/04/20 14:24:52 1.22
+++ bsd.own.mk 1999/04/22 05:08:42
@@ -136,6 +136,7 @@
# Binaries
BINOWN?= root
BINGRP?= wheel
+GAMEGRP?= games
BINMODE?= 555
NOBINMODE?=444
Index: src/games/Makefile.inc
===
RCS file: /home/ncvs/src/games/Makefile.inc,v
retrieving revision 1.9
diff -u -r1.9 Makefile.inc
--- Makefile.inc1998/10/18 09:48:26 1.9
+++ Makefile.inc1999/04/22 05:08:02
@@ -1,6 +1,6 @@
# @(#)Makefile.inc8.1 (Berkeley) 5/31/93
-BINGRP= games
+BINGRP= ${GAMEGRP}
BINDIR?= /usr/games
.if defined(HIDEGAME)
#!/bin/sh -e -
z=`pwd`
z=`basename $z`
if [ "x${z}" = "xsrc" ]; then
cd ..
z=`pwd`
z=`basename $z`
cd src
if [ -f /tmp/buildworldoutput.$z ]; then
mv /tmp/buildworldoutput.$z /tmp/buildworldoutput.${z}.last
fi
date | tee /tmp/buildworldoutput.$z
chown jmg /tmp/buildworldoutput.$z
time -l make BINGRP=admin BINOWN=jmg TMACOWN=jmg TMACGRP=admin
SHAREOWN=jmg SHAREGRP=admin GAMEGRP=admin NOINFO= NOPROFILE= NOTCL= NOTERMCAP=
NOFSCHG= $* buildworld 2>&1 | tee -a /tmp/buildworldoutput.$z
echo 'NOTE: You must build share/termcap by hand!!' | tee -a
/tmp/buildworldoutput.$z
date | tee -a /tmp/buildworldoutput.$z
else
echo 'You must be in the src dir to do a buildworld'
fi
Re: USB keyboard attach function?
> Not quite a fix however the following patches fixes disconnect /reconnect
> problems with my USB mouse and the 3com USB modem . This is a
> bandage please don't commit is just that right if I diconnect my usb
> modem or usb mouse my system panics hence the following simple patch.
That looks like a proper hack. I'll have to sort out something more
reliable than that :-)
> Disconnected and reconnected my mouse several times and got no
> panic plus every time someone calls here the USB modem does
> not crash my system 8)
:-) You can quitely answer the phone while your system is doing an fsck
of a 18Gb disk that is 80% full...
> One thing though someone ought to fix moused so that if
> it is talking to a usb mouse which gets disconnected and
> then reconnected to enable again the mouse. I managed
> to get back my mouse operational by sending a "HUP"
> signal to moused.
One of the things we might to have a daemon do. Another option would be
to just reconnect the mouse to the same open file descriptor, but I
don't know whether this is possible.
The following is no longer necessary (I think). I fixed that yesterday.
diff -r -c usb/usb_port.h usb.new/usb_port.h
*** usb/usb_port.h Wed Apr 21 15:33:44 1999
--- usb.new/usb_port.h Wed Apr 21 18:29:20 1999
***
*** 202,208
((dev)->softc = device_get_softc(bdev)) : 0)
/* conversion from one type of queue to the other */
! #define SIMPLEQ_REMOVE_HEAD STAILQ_REMOVE_HEAD
#define SIMPLEQ_INSERT_HEAD STAILQ_INSERT_HEAD
#define SIMPLEQ_INSERT_TAIL STAILQ_INSERT_TAIL
#define SIMPLEQ_NEXT STAILQ_NEXT
--- 202,216
((dev)->softc = device_get_softc(bdev)) : 0)
/* conversion from one type of queue to the other */
! /* #define SIMPLEQ_REMOVE_HEADSTAILQ_REMOVE_HEAD */
! #define SIMPLEQ_REMOVE_HEAD(head, field) do {
\
! if ((head)->stqh_first != NULL ) {
\
! if (((head)->stqh_first =
\
!(head)->stqh_first->field.stqe_next) == NULL)
\
! (head)->stqh_last = &(head)->stqh_first;
\
! }
\
! } while (0)
!
#define SIMPLEQ_INSERT_HEAD STAILQ_INSERT_HEAD
#define SIMPLEQ_INSERT_TAIL STAILQ_INSERT_TAIL
#define SIMPLEQ_NEXT STAILQ_NEXT
--
ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
> Did you update your rc.conf lately? It should contain the startup of
> the usbd daemon.
I know start usbd upon startup 8)
> > A side note, someone fixed syscons so it no longer panics if
> > the atkbd device is not configured . In my case, I have
> > a USB keyboard and a USB mouse connected to the
> > system with no atkbdc nor atbkd device . It works like
> > a charm now 8)
>
> Cool!
>
Not quite a fix however the following patches fixes disconnect /reconnect
problems with my USB mouse and the 3com USB modem . This is a
bandage please don't commit is just that right if I diconnect my usb
modem or usb mouse my system panics hence the following simple patch.
Disconnected and reconnected my mouse several times and got no
panic plus every time someone calls here the USB modem does
not crash my system 8)
One thing though someone ought to fix moused so that if
it is talking to a usb mouse which gets disconnected and
then reconnected to enable again the mouse. I managed
to get back my mouse operational by sending a "HUP"
signal to moused.
Enjoy
diff -r -c usb/ugen.c usb.new/ugen.c
*** usb/ugen.c Fri Apr 16 16:13:36 1999
--- usb.new/ugen.c Wed Apr 21 19:16:54 1999
***
*** 947,953
struct ugen_endpoint *sce;
int revents = 0;
int s;
!
if (sc->sc_disconnected)
return (EIO);
--- 947,953
struct ugen_endpoint *sce;
int revents = 0;
int s;
! if (sc == NULL ) return (EIO);
if (sc->sc_disconnected)
return (EIO);
diff -r -c usb/ukbd.c usb.new/ukbd.c
*** usb/ukbd.c Sun Apr 11 15:28:38 1999
--- usb.new/ukbd.c Wed Apr 21 19:15:29 1999
***
*** 306,311
--- 306,312
ukbdpoll(dev_t dev, int event, struct proc *p)
{
USB_GET_SC(ukbd, UKBDUNIT(dev),sc);
+ if (sc == NULL ) return 0;
return genkbdpoll(&sc->sc_gensc, sc->sc_kbd, event, p);
}
diff -r -c usb/ums.c usb.new/ums.c
*** usb/ums.c Fri Apr 16 16:13:47 1999
--- usb.new/ums.c Wed Apr 21 18:59:09 1999
***
*** 664,669
--- 664,670
USB_GET_SC(ums, UMSUNIT(dev), sc);
int revents = 0;
int s;
+ if (sc == NULL ) return revents;
s = splusb();
if (events & (POLLIN | POLLRDNORM)) {
diff -r -c usb/usb_port.h usb.new/usb_port.h
*** usb/usb_port.h Wed Apr 21 15:33:44 1999
--- usb.new/usb_port.h Wed Apr 21 18:29:20 1999
***
*** 202,208
((dev)->softc = device_get_softc(bdev)) : 0)
/* conversion from one type of queue to the other */
! #define SIMPLEQ_REMOVE_HEAD STAILQ_REMOVE_HEAD
#define SIMPLEQ_INSERT_HEAD STAILQ_INSERT_HEAD
#define SIMPLEQ_INSERT_TAIL STAILQ_INSERT_TAIL
#define SIMPLEQ_NEXT STAILQ_NEXT
--- 202,216
((dev)->softc = device_get_softc(bdev)) : 0)
/* conversion from one type of queue to the other */
! /* #define SIMPLEQ_REMOVE_HEADSTAILQ_REMOVE_HEAD */
! #define SIMPLEQ_REMOVE_HEAD(head, field) do { \
! if ((head)->stqh_first != NULL ) { \
! if (((head)->stqh_first = \
!(head)->stqh_first->field.stqe_next) == NULL) \
! (head)->stqh_last = &(head)->stqh_first;\
! } \
! } while (0)
!
#define SIMPLEQ_INSERT_HEAD STAILQ_INSERT_HEAD
#define SIMPLEQ_INSERT_TAIL STAILQ_INSERT_TAIL
#define SIMPLEQ_NEXT STAILQ_NEXT
Amancio Hasty
ha...@star-gate.com
Re: solid NFS patch #6 avail for -current - need testers files)
Previously on Wed, Apr 21, 1999 at 12:31:03PM -0700, Matthew Dillon wrote: : : I think the existing release schedule is pretty good. Any faster and : we might as well not have two branches at all. We really need a : -current branch in order to make and test radical changes, and the : companies & people who use FreeBSD need a -stable branch to keep : production boxes up to date without having to bet the farm. : : We already have the ability to shortcut certain things simply by : copying them from -current to -stable wholesale after we've determined : their stability under -current. The issue here really is safety. I : know some of you really want some of the things in -current to be : backported into -stable more quickly, but you have to be patient. We : can't compromise -stable's stability by acting too quickly. : Speaking as a heavy stable user and also a Net and OpenBSD user the big selling point I have for using FreeBSD over the other 'free' BSDs, Linux and some commercial OSs is the release structure. I believe radical alterations to this structure would be best avoided. It is only post 3.1 release that I have become confident in the RelEng3 branch as a service platform. People desperate for current functionality can wait, back port themselves or run current. I have taken all three options in the past :-) -- GeoffB To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: USB keyboard attach function?
> While playing over here with the USB stuff, I rebooted the system and > disconnected the USB keyboard waited till the system was fully up > and re-connected the USB keyboard which resulted in the system > not attaching the USB keyboard. Did you update your rc.conf lately? It should contain the startup of the usbd daemon. > A side note, someone fixed syscons so it no longer panics if > the atkbd device is not configured . In my case, I have > a USB keyboard and a USB mouse connected to the > system with no atkbdc nor atbkd device . It works like > a charm now 8) Cool! Nick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
