Re: my mail
[Ooops, sorry for forgetting to pass a Subject header to sendmail..., and the bogus envelope sender] David O'Brien went a little something like this: On Wed, Nov 29, 2000 at 08:06:14AM +0100, News User wrote: I'm building news machines with two partitions for OSen, to allow me to boot into my choice, where my choice has been FreeBSD-STABLE or FreeBSD-CURRENT I know, ``don't do that'' but hey... Except for stupidity in libdisk(I believe) and thus sysinstall, there is no, none, zero reason why one cannot have two installations of FreeBSD in two different slices on the same disk. Erm, actually, what I meant by the ``don't do that'' was referring to the idea of using -CURRENT, especially SMPNG current with known problems, on a production machine. But it's my butt on the line. Anyway, I'm surprised to hear that other people have had problems. It's routine for me to put at least two FreeBSDen on any disk I build larger than 2GB, and I've never had problems with the two of them co-existing, or adding yet another OS like NetBSD for further instructive comparisons. Good way to put that extra unused space to use, and to make it easy to choose the desired OS and upgrade without risk. There have been a small number of times when sysinstall has complained that I can't have a root partition where I put it the second time, but not too often, and I've been able to work around it. The only recent difficulty I've had has been when I built an OS on a disk whose geometry was not the usual translated x/255/63 and the install procedure and all utilities recognized the different geometry, but the boot mangler failed to boot the OS partition. I fixed this by just booting into an older OS on a different disk and writing from that sysinstall to the boot sector of the problem disk, and now it boots fine. I've had a few other geometry-related problems when attempting to do 4.x installations, but I haven't bothered to try to dig around for the root cause and repeatable conditions... now i'll just go away barry bouwsma To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ps/2 mouse freezes in X
when i switch from X Window screen to text console and back, my ps/2 mouse cursor often freezes with "psmintr: out of sync ( != 0008)" message from kernel. the problem doesn't depend on moused running or not, as well as on FreeBSD version (4.x or 5.0). lots of my colleagues also report about it. my configuration: * Genius NewScroll PS/2 Mouse * ASUS K7V-T motherboard (VIA KX133 chipset) * XFree4.0.1_4 dmesg related to mouse: psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0 sincerely, ilya naumov (at work) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ps/2 mouse freezes in X
Try disabling APM (device apm) if you currently have that configured in the kernel. I experimented with apm yesterday (Abit KA7, with Via chipset) and got exactly the same problem. Disabling apm fixed it Wilko when i switch from X Window screen to text console and back, my ps/2 mouse cursor often freezes with "psmintr: out of sync ( != 0008)" message from kernel. the problem doesn't depend on moused running or not, as well as on FreeBSD version (4.x or 5.0). lots of my colleagues also report about it. my configuration: * Genius NewScroll PS/2 Mouse * ASUS K7V-T motherboard (VIA KX133 chipset) * XFree4.0.1_4 dmesg related to mouse: psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model NetMouse/NetScroll Optical, device ID 0 sincerely, ilya naumov (at work) 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: USB modem?
I have a USB modem here, (Siemens), that I would like to get to work under FreeBSD, but I can't even find the right tools to get vendor and product ID's to add to usbdevs :-( Try looking in dmesg - USB device that don't have known product and vendor ID's have theirs printed. Failing that, check the usbdevs(8) man page. The serious catch about USB modems is that they have to support the USB CDC spec. Not all of them do. If it does, the serial device will be umodem0 (1, 2, 3, ...), and you use it just like a tty line tied to an external modem. Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I have the modem in the office, not at home. And of course there is that tricky part where Windows wants my BIOS set to PNP OS=YES and FreeBSD wants it set to NO. but well :-) we can survive that for the moment. Mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current.freebsd.org
Hi All- Not sure if this the right place to complain or not, but current.freebsd.org does not appear to be on the net. traceroutes to both current.freebsd.org and usw2.freebsd.org (its alterego) fail. I did find that ftp7.de.freebsd.org has the 27 November 2000 snapshot of current on it .. was this the last time current.freebsd.org was alive? What is the proper place to complain? A quick search of handbook/faq and archives of this list yields nothing ... Thanks, S --- Sean O'ConnellEmail: [EMAIL PROTECTED] Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org
Not sure if this the right place to complain or not, but current.freebsd.org does not appear to be on the net. traceroutes to both current.freebsd.org and usw2.freebsd.org (its alterego) fail. I did find that ftp7.de.freebsd.or g has the 27 November 2000 snapshot of current on it .. was this the last time current.freebsd.org was alive? About 3 days ago; I'm unable to contact anyone at USWest but am working on it. Sigh. Also, for some reason the remote console to usw2 just doesn't work so the remote debugging option is out too. What is the proper place to complain? A quick search of handbook/faq and archives of this list yields nothing ... Probably [EMAIL PROTECTED] since it's an infrastructural issue, but others have been complaining too so -current was as reasonable a place as any in this case since it let me tell all of you the situation at once. :) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org
Jordan: I can probably help you out. 612.664.3078. Brett On Fri, 01 Dec 2000 12:56:32 PST, "Jordan Hubbard" wrote: Not sure if this the right place to complain or not, but current.freebsd.org does not appear to be on the net. traceroutes to both current.freebsd.org and usw2.freebsd.org (its alterego) fail. I did find that ftp7.de.freebsd.o r g has the 27 November 2000 snapshot of current on it .. was this the last time current.freebsd.org was alive? About 3 days ago; I'm unable to contact anyone at USWest but am working on it. Sigh. Also, for some reason the remote console to usw2 just doesn't work so the remote debugging option is out too. --- Brett Rabe [EMAIL PROTECTED] / 612.664.3078 Senior Systems Engineer Qwest - Internet Services So what's the speed of dark? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
world only broken for me?
=== usr.bin/mklocale yacc -d /usr/src/usr.bin/mklocale/yacc.y cp y.tab.c yacc.c lex -t /usr/src/usr.bin/mklocale/lex.l lex.c rm -f .depend mkdep -f .depend -a-I/usr/src/usr.bin/mklocale -I/usr/obj/usr/src/i386/usr/include yacc.c lex.c /usr/src/usr.bin/mklocale/lex.l:48: y.tab.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/mklocale. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA [EMAIL PROTECTED] [EMAIL PROTECTED] If God lived on Earth, people would knock out all His windows. -- Yiddish saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: world only broken for me?
On Fri, Dec 01, 2000 at 05:52:34PM -0600, Michael Harnois wrote: === usr.bin/mklocale yacc -d /usr/src/usr.bin/mklocale/yacc.y cp y.tab.c yacc.c lex -t /usr/src/usr.bin/mklocale/lex.l lex.c rm -f .depend mkdep -f .depend -a-I/usr/src/usr.bin/mklocale -I/usr/obj/usr/src/i386/usr/include yacc.c lex.c /usr/src/usr.bin/mklocale/lex.l:48: y.tab.h: No such file or directory mkdep: compile failed *** Error code 1 Fixed a few hours ago: obrien 2000/12/01 11:36:17 PST Modified files: usr.bin/mklocale Makefile Log: Grrr... GCC 2.95.2 and 2.96 just will not agree what the default include search paths are. So add the requirements of both. :-( -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Mark Huizer [EMAIL PROTECTED] types: I have a USB modem here, (Siemens), that I would like to get to work under FreeBSD, but I can't even find the right tools to get vendor and product ID's to add to usbdevs :-( Try looking in dmesg - USB device that don't have known product and vendor ID's have theirs printed. Failing that, check the usbdevs(8) man page. The serious catch about USB modems is that they have to support the USB CDC spec. Not all of them do. If it does, the serial device will be umodem0 (1, 2, 3, ...), and you use it just like a tty line tied to an external modem. Is it a case of being in the usbdevs list _and_ supporting those specs? Or just following the specs? I believe that being listed in usbdevs isn't a requirement, but I'm not positive. I also haven't had any look getting the thing to work dynamically loading the various modules involved. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant,email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PnP OS = ?
I have the modem in the office, not at home. And of course there is that tricky part where Windows wants my BIOS set to PNP OS=YES and FreeBSD wants it set to NO. but well :-) we can survive that for the moment. Can you expand on what actually goes wrong if you boot -current with it set to YES? This is part of what I'm working on right now... -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
kernel panics in 4.2
I sent this message to -questions earlier, but nobody seems to know about my problem: I just recently tried putting an adaptec 2940w SCSI controller into my FreeBSD machine (running -STABLE cvsupped and recompiled every night at 1:30AM) and since including the driver in my kernel I've noticed some random panics. Most of the time they occur during heavy disk activity, and usually only when I'm running X (hence the reason I couldn't tell you the panic message). Even wierder still, I don't even have any SCSI devices connected yet; I'm using only IDE disks connected via the motherboard's builtin ATA66. I have also searched the various FreeBSD mailinglist archives and found some people with the same problems I was having, but no solutions. Crashes do not occur in Windows with this configuration (at least not any more than usual :-) ) and when I take the ahc driver out of the kernel, the panics stop. I've included my dmesg -v output and my kernel config file, please let me know if anything else is needed. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-STABLE #0: Fri Dec 1 11:55:01 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MYKERNEL Calibrating clock(s) ... TSC clock: 800028138 Hz, i8254 clock: 1193181 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: AMD Athlon(tm) Processor (800.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x642 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR AMD Features=0xc044b18,AMIE,DSP,3DNow! Data TLB: 24 entries, fully associative Instruction TLB: 16 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L2 internal cache: 256 kbytes, 64 bytes/line, 1 lines/tag, 8-way associative real memory = 134152192 (131008K bytes) Physical memory chunk(s): 0x1000 - 0x0009, 651264 bytes (159 pages) 0x0035d000 - 0x07fe7fff, 130592768 bytes (31883 pages) avail memory = 127324160 (124340K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf90 bios32: Entry = 0xfb400 (c00fb400) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb430 pnpbios: Found PnP BIOS data at 0xc00fbf00 pnpbios: Entry = f:bf30 Rev = 1.0 Other BIOS signatures found: ACPI: 000f7ad0 Preloaded elf kernel "kernel" at 0xc0337000. Preloaded elf module "if_xl.ko" at 0xc03370a8. Preloaded elf module "miibus.ko" at 0xc0337148. Preloaded elf module "usb.ko" at 0xc03371e8. Preloaded elf module "ums.ko" at 0xc0337284. Preloaded elf module "bktr_mem.ko" at 0xc0337320. Preloaded elf module "bktr.ko" at 0xc03373c0. Preloaded elf module "agp.ko" at 0xc033745c. bktr_mem: memory holder loaded Pentium Pro MTRR support enabled pci_open(1):mode 1 addr port (0x0cf8) is 0x80003840 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=03051106) pcib-: pcib0 exists, using next available unit number apm0: APM BIOS on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=03051106) pcib0: Host to PCI bridge on motherboard found- vendor=0x1106, dev=0x0305, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base d800, size 26 found- vendor=0x1106, dev=0x8305, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x1106, dev=0x0686, revid=0x22 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x1106, dev=0x0571, revid=0x10 class=01-01-8a, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base d000, size 4 found- vendor=0x1106, dev=0x3038, revid=0x10 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=10 map[20]: type 1, range 32, base d400, size 5 found- vendor=0x1106, dev=0x3038, revid=0x10 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=10 map[20]: type 1, range 32, base d800, size 5 found- vendor=0x1106, dev=0x3057, revid=0x30 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x109e, dev=0x036e, revid=0x02 class=04-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0
