[OT] any ideas why Maven 2.0.4 can not connect to any external repositories?
Hello, I finally got around to updating to 5.5-Stable from about a 6-9 months before its last update. Since then, I've been unable to connect with Maven 2.0.4 and Limewire for that matter. Any ideas, a config file I need to change now? Thank you, -- Michael E. Mercer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do I mount a USB hard drive?
Its a FreeBSD partition from another box. However the drive itself is not showing up when I do a "usbdevs -d -v". This is the problem I am having. I know how to mount and all that stuff, just not exactly what I need to do to get FreeBSD to see the drive itself. Thanks Michael FreeBSD questionsFreeBSD questionsOn Sun, 2004-07-18 at 19:26, 3BSD wrote: > On Sun, 18 Jul 2004 16:29:03 -0400, Michael E. Mercer <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I had a hard drive (8 Gig) sitting around and thought I would try the > > new USB 2.0 hard drive kits. It works just fine in Winblows but I am > > unable to get it to show up under FreeBSD. > > > > 4.10-Stable > > > > kernel conf file below... > > > You need to provide some additional information. > > 1. What filesystem has the drive been formatted with? If its NTFS, I > suggest you re-format the drive using FAT32 because you don't have > NTFS support in your kernel config, and even if you did, the drive > will not be of much use to you in FreeBSD as NTFS support is not all > that great. > > 2. What's the mount command you're using to mount the drive? I use the > following to mount my external USB2 drive: > > # mount -t msdos /dev/da0s1 /mnt/ext > > And it works perfectly with both USB and FireWire, better under > FireWire, if you ask me. ;-) > > -Assad > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do I mount a USB hard drive?
That's what I started with... I have everything in my kernel that is mentioned on that page. Nothing is appearing when I connect/disconnect the drive. On Sun, 2004-07-18 at 19:20, Marc Fonvieille wrote: > On Sun, Jul 18, 2004 at 04:29:03PM -0400, Michael E. Mercer wrote: > > Hello, > > > > I had a hard drive (8 Gig) sitting around and thought I would try the > > new USB 2.0 hard drive kits. It works just fine in Winblows but I am > > unable to get it to show up under FreeBSD. > > > > 4.10-Stable > > > [...] > > Read USB Storage Devices section: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/usb-disks.html > > Marc > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How do I mount a USB hard drive?
Hello, I had a hard drive (8 Gig) sitting around and thought I would try the new USB 2.0 hard drive kits. It works just fine in Winblows but I am unable to get it to show up under FreeBSD. 4.10-Stable kernel conf file below... # # g4.9 -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.56 2003/12/19 22:52:44 jhb Exp $ machine i386 cpu I686_CPU ident g49 maxusers512 # # SMP OPTIONS: # # SMP enables building of a Symmetric MultiProcessor Kernel. # APIC_IO enables the use of the IO APIC for Symmetric I/O. # # Notes: # # An SMP kernel will ONLY run on an Intel MP spec. qualified motherboard. # # Be sure to disable 'cpu I386_CPU' && 'cpu I486_CPU' for SMP kernels. # # Check the 'Rogue SMP hardware' section to see if additional options # are required by your hardware. # # Mandatory: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options MATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV# install a CDEV entry in /dev options AHC_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~128k to driver. options AHD_REG_PRETTY_PRINT# Print register bitfields in debug # output. Adds ~215k to driver. device isa device eisa device pci device pcm # Floppy drives device fdc0at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives device atapicam# emulate ATAPI devices as SCSI ditto via CAM # needs CAM to be present (scbus & pass) options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0at atkbdc? irq 12 device vga0at isa? # splash screen/screen saver pseudo-device splash # syscons is the d
Re: permissions problem with installations from PORTS
btw: I just verified that my umask is 022. Which is what you stated it should be set to. And those ports still installed some directories with 700 permissions. later Michael On Wed, 2004-04-14 at 21:11, Michael E. Mercer wrote: > Hello, > > I got a new machine that is blazingly fast. > I also installed gnome-lite which in turn installed a majority of these > ports that are having these problems. > > What I am getting at, is I never *saw* that warning. > > later > Michael > > On Wed, 2004-04-14 at 08:50, Dag-Erling Smørgrav wrote: > > Joan Picanyol <[EMAIL PROTECTED]> writes: > > > * Dag-Erling Sm?rgrav <[EMAIL PROTECTED]> [20040413 19:58]: > > > > Joan Picanyol <[EMAIL PROTECTED]> writes: > > > > > I can second this. It also happens with mozilla and friends (my umask is > > > > > set to 077) > > > > Pilot error. Your umask should be 022 or 002 when installing ports. > > > > Otherwise, you get what you ask for. > > > May I disagree? I expected the ports system to use install to properly > > > set up permissions for all files. At the very least, it should be > > > documented somewhere. > > > > You deliberately ignored the following warning: > > > > ===> Warning: your umask is 077 > > If this is not desired, set it to an appropriate value > > and install this port again by ``make reinstall'' > > > > DES > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Gimp 2 does not come with help?
I noticed a number of ports are installing directories with permissions 700. You may need to chmod those to 755 to get applications to work. HTH Michael On Wed, 2004-04-14 at 05:59, Rob wrote: > Hi, > > I have gimp, version 2.0.0, with "WITH_HTML_HELP_BROWSER=yes" > installed. When I click on Help->Help, I get an empty browser, > but also a message pop-up, that says > > 'Could not open '/usr/X11R6/share/gimp/help/en/gimp-help.xml' > for reading: No such file or directory. > > Is this gimp install incomplete, or do I need another port > for the help XML pages of gimp? > > Regards, > Rob. > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Anybody Use 2 or More CPU at Production Env. ( SMP )
I am using 4.9-Stable on a Dual Xeon 450MHz processors and have not had any problems as reported by others. Been running SMP from the beginning later MEM On Thu, 2003-12-18 at 14:32, Vahric MUHTARYAN wrote: > Hi Everybody , > > > I watching freebsd-stable list I saw that somebody have a problem > with SMP support which they are using 4.9 . I know that some improvement are > coming with 5.x But this problem are very important for example > somebody when enable SMP support system start to reset itself or under high > load crashed ?! > > I wonder Does anybody use SMP Support without Problem . Because SMP > is very important things ... > > I wonder too What about HyperThreading ?! > > > Second How can I learn What is 1:1 and M:N thread libraries ? ! How > it's work ?! How SMP work on FreeBSD ?! > > > Because I'm using Redhat for a long time and I don't have any > problem with it of course under high load ... > > > Thanks > Vahric MUHTARYAN > > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How do I have sendmail forward emails from root...
In /etc/mail, I ran: make cf maps aliases install stop start after every change... More info, now that I think of it. The mail server is getting the emails, but kicks it back because the the "From:" header has an unknown host. [EMAIL PROTECTED] How do I remedy this? Thanks Michael On Wed, 2003-12-17 at 17:13, Kevin Stevens wrote: > On Wed, 17 Dec 2003, Michael E. Mercer wrote: > > > I've tried quite a few things and just can't seem to get > > sendmail to forward emails generated by root processes to > > go to "[EMAIL PROTECTED]". > > > > I am running 4.9-Stable. > > > > How am I supposed to configure this? > > > > I have added a line to /etc/mail/aliases > > root: [EMAIL PROTECTED] > > Did you run 'make aliases' to update the database afterwards? > > KeS ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How do I have sendmail forward emails from root...
Hello peoples, I've tried quite a few things and just can't seem to get sendmail to forward emails generated by root processes to go to "[EMAIL PROTECTED]". I am running 4.9-Stable. How am I supposed to configure this? I have added a line to /etc/mail/aliases root: [EMAIL PROTECTED] Also added to my domain specific .mc configuration file these lines: MASQUERADE_AS(`nc.rr.com')dnl MASQUERADE_DOMAIN(`mmercer.com') FEATURE(allmasquerade)dnl FEATURE(masquerade_envelope)dnl FEATURE(masquerade_entire_domain)dnl FEATURE(nocanonify)dnl define(`SMART_HOST', `smtp-server.nc.rr.com') Thanks in advance! Michael ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SOLVED: Re: SCSI Disk not found
Hello peoples, I am not sure which of these changes fixed the problem with FreeBSD not seeing the drive because I did them all at one time. But anyways, FreeBSD sees it and I am happy. Thanks to all who gave their input! Michael E Mercer Set all jumper setting were on the Western Digital SCSI Drive. :SCSI Termination. :Auto-Start Delay. :Disable Target Initiated Synchronous/Wide Negotiation. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SCSI Disk not found
The drive that can not be found is a Western Digital WD Enterprise 4360 4.3 GB Wide-Ultra SCSI I have removed the second SCSI controller card (PCI) and the Seagate SCSI Hard Drive. All that remains is the On-motherboard scsi controller and the western digital SCSI drive. The Compaq Configuration Utility sees the drive. But FreeBSD does not. Any ideas? Is this Drive supported? Thanks Michael E Mercer On Wed, 2003-12-03 at 22:06, Riley J. McIntire wrote: > > From: Michael E. Mercer > > > Ok, its the "System Configuration Utility" supplied by Compaq not the > > BIOS. > > > Michael > > Just to jump in...after reading the thread you probably have hardware > raid 0 (mirroring) on the system using 2 controllers and 2 drives--the > Compaq cu should tell you what's going on. The OS will see the 2 > mirrored drives as one. I'd be careful about changing scsi IDs until you > determine what's going on. > > hth, > > Riley > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: SCSI Disk not found
Ok, its the "System Configuration Utility" supplied by Compaq not the BIOS. I added puc to kernel and it still has the same irq. This machine was in the closet for a long while... and it had no operating system installed when I got it, but I think it may have had windows NT. Thanks for your help, Michael On Wed, 2003-12-03 at 09:49, fbsd_user wrote: > What do you mean SCSI HD show in PC bios? I have not seen any PC > bio's that know about SCSI drives. They are not part of the normal > PC hardware inventory. SCSI drives are 3rd party hardware. Your > bio's option 'drive to boot from' is the only place that knows about > SCSI. It should say boot from SCSI drive, or something along those > lines. The SCSI PCI control card knows about the 2 drive if it's > there. During the PC boot process you should see msg about SCSI > controller being enabled. AT that point you should be able to enter > SCSI setup utility. > > I see from dmesg that both drives are using same irq. This is common > problem with older PC bios, FBSD can not reassign different IRQ to > second device. Add device puc statement to your kernel source and > recompile kernel. Them check Dmesg boot log to see if different > IRQ's get assigned. > > Before you installed FBSD on this PC, was it running ms/windows and > did you see the both SCSI drives? > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Michael E. > Mercer > Sent: Wednesday, December 03, 2003 9:14 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: RE: SCSI Disk not found > > Hello, > > I wish it were that easy... I really meant that FreeBSD does NOT > see it at all. I have tried to mount it myself, but it tells > me that the device is not configured. > > The SCSI hard drive appears in the system BIOS, and when the machine > first boots up, but it is gone everywhere else. > > Any ideas? > > Michael > > On Wed, 2003-12-03 at 09:09, fbsd_user wrote: > > You have to add an line to the /etc/fstab file for the second HD. > > You can mount it as an msdos HD or you can use FBSD to fdisk, > label, > > and format it to FBSD file system. It's up to you and how you > want > > to use it. > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Michael > E. > > Mercer > > Sent: Tuesday, December 02, 2003 11:38 PM > > To: [EMAIL PROTECTED] > > Subject: SCSI Disk not found > > > > Hello peoples, > > > > I was given a Compaq Proliant 800 machine...its a pentium pro > > 200 MHz. I got 4.9-Stable installed and everything is running > > smooth. > > > > However, I noticed that is does indeed have two scsi disks, > > but freebsd only finds one. > > > > Attached is the dmesg... notice the sym0 and sym1. > > Does this supposed to tell me anything? > > > > Thanks > > Michael E Mercer > > > > Copyright (c) 1992-2003 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.9-STABLE #0: Tue Dec 2 21:45:22 EST 2003 > > [EMAIL PROTECTED]:/usr/src/sys/compile/slow_4_9 > > Timecounter "i8254" frequency 1193182 Hz > > CPU: Pentium Pro (199.43-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0x619 Stepping = 9 > > > > > Features=0xf9ff > CMOV> > > real memory = 301989888 (294912K bytes) > > avail memory = 288219136 (281464K bytes) > > Preloaded elf kernel "kernel" at 0xc0491000. > > Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. > > ccd0-3: Concatenated disk drivers > > VESA: v1.2, 1024k memory, flags:0x0, mode table:0xc03f8994 > (114) > > VESA: STB COMPAQ 5440 > > Pentium Pro MTRR support enabled > > md0: Malloc disk > > npx0: on motherboard > > npx0: INT 16 interface > > pcib0: on motherboard > > pci0: on pcib0 > > pcib1: at device 8.0 on pci0 > > pci1: on pcib1 > > sym0: <875> port 0x7000-0x70ff mem > > 0x4010-0x40100fff,0x40102000-0x401020ff irq 5 at device 4.0 on > > pci1 > > sym0: No NVRAM, ID 7, Fast-20, SE, parity checking > > sym1: <875> port 0x7400-0x74ff mem > > 0x40101000-0x40101fff,0x40102100-0x401021ff irq 5 at device 8.0 on > > pci1 > > sym1: No NVRAM, ID 7, Fast-20, SE, parity checking > > pci1: at 9.0 > > tl0: port 0x6000-0x600f mem > > 0x4000-0x40
RE: SCSI Disk not found
Hello, I wish it were that easy... I really meant that FreeBSD does NOT see it at all. I have tried to mount it myself, but it tells me that the device is not configured. The SCSI hard drive appears in the system BIOS, and when the machine first boots up, but it is gone everywhere else. Any ideas? Michael On Wed, 2003-12-03 at 09:09, fbsd_user wrote: > You have to add an line to the /etc/fstab file for the second HD. > You can mount it as an msdos HD or you can use FBSD to fdisk, label, > and format it to FBSD file system. It's up to you and how you want > to use it. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Michael E. > Mercer > Sent: Tuesday, December 02, 2003 11:38 PM > To: [EMAIL PROTECTED] > Subject: SCSI Disk not found > > Hello peoples, > > I was given a Compaq Proliant 800 machine...its a pentium pro > 200 MHz. I got 4.9-Stable installed and everything is running > smooth. > > However, I noticed that is does indeed have two scsi disks, > but freebsd only finds one. > > Attached is the dmesg... notice the sym0 and sym1. > Does this supposed to tell me anything? > > Thanks > Michael E Mercer > > Copyright (c) 1992-2003 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.9-STABLE #0: Tue Dec 2 21:45:22 EST 2003 > [EMAIL PROTECTED]:/usr/src/sys/compile/slow_4_9 > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium Pro (199.43-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x619 Stepping = 9 > > Features=0xf9ff CMOV> > real memory = 301989888 (294912K bytes) > avail memory = 288219136 (281464K bytes) > Preloaded elf kernel "kernel" at 0xc0491000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. > ccd0-3: Concatenated disk drivers > VESA: v1.2, 1024k memory, flags:0x0, mode table:0xc03f8994 (114) > VESA: STB COMPAQ 5440 > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 8.0 on pci0 > pci1: on pcib1 > sym0: <875> port 0x7000-0x70ff mem > 0x4010-0x40100fff,0x40102000-0x401020ff irq 5 at device 4.0 on > pci1 > sym0: No NVRAM, ID 7, Fast-20, SE, parity checking > sym1: <875> port 0x7400-0x74ff mem > 0x40101000-0x40101fff,0x40102100-0x401021ff irq 5 at device 8.0 on > pci1 > sym1: No NVRAM, ID 7, Fast-20, SE, parity checking > pci1: at 9.0 > tl0: port 0x6000-0x600f mem > 0x4000-0x400f irq 9 at device 16.0 on pci0 > tl0: Ethernet address: 00:80:5f:35:d8:6d > miibus0: on tl0 > tlphy0: on miibus0 > tlphy0: 10base2/BNC, 10base5/AUI, 10baseT, 10baseT-FDX, auto > isab0: at device 20.0 on pci0 > isa0: on isab0 > atapci0: port 0xf100-0xf10f at device > 20.1 > on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > eisa0: on motherboard > mainboard0: on eisa0 slot 0 > orm0: at iomem > 0xc-0xc7fff,0xe8000-0xedfff,0xee000-0xe on isa0 > pmtimer0 on isa0 > pca0 at port 0x40 on isa0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on > isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: cannot reserve I/O port range > IPsec: Initialized Security Association Processing. > ncp_load: [210-213] > ad1: 8207MB [16676/16/63] at ata0-slave WDMA2 > acd0: CDROM at ata0-master PIO3 > Waiting 15 seconds for SCSI devices to settle > Mounting root from ufs:/dev/da0s1a > da0 at sym1 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged > Queueing > Enabled > da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SCSI Disk not found
Ok. I have what looks to be two host adapters. The one on the motherboard and a PCI? card. Not sure what exactly I am supposed to do for I have never had a PC with SCSI before... Any help is appreciated. Thanks MeM On Tue, 2003-12-02 at 23:57, Mike Maltese wrote: > > I was given a Compaq Proliant 800 machine...its a pentium pro > > 200 MHz. I got 4.9-Stable installed and everything is running > > smooth. > > > > However, I noticed that is does indeed have two scsi disks, > > but freebsd only finds one. > > > > Attached is the dmesg... notice the sym0 and sym1. > > Does this supposed to tell me anything? > > Yes, it is. Either the host adapter has two channels or you have two host > adapters in the machine. I'm not sure what card you have exactly, but my > guess is that it's the former. I would crack the box open and see what's > what with the SCSI configuration. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SCSI Disk not found
Hello peoples, I was given a Compaq Proliant 800 machine...its a pentium pro 200 MHz. I got 4.9-Stable installed and everything is running smooth. However, I noticed that is does indeed have two scsi disks, but freebsd only finds one. Attached is the dmesg... notice the sym0 and sym1. Does this supposed to tell me anything? Thanks Michael E Mercer Copyright (c) 1992-2003 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.9-STABLE #0: Tue Dec 2 21:45:22 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/slow_4_9 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xf9ff real memory = 301989888 (294912K bytes) avail memory = 288219136 (281464K bytes) Preloaded elf kernel "kernel" at 0xc0491000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. ccd0-3: Concatenated disk drivers VESA: v1.2, 1024k memory, flags:0x0, mode table:0xc03f8994 (114) VESA: STB COMPAQ 5440 Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 8.0 on pci0 pci1: on pcib1 sym0: <875> port 0x7000-0x70ff mem 0x4010-0x40100fff,0x40102000-0x401020ff irq 5 at device 4.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x7400-0x74ff mem 0x40101000-0x40101fff,0x40102100-0x401021ff irq 5 at device 8.0 on pci1 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking pci1: at 9.0 tl0: port 0x6000-0x600f mem 0x4000-0x400f irq 9 at device 16.0 on pci0 tl0: Ethernet address: 00:80:5f:35:d8:6d miibus0: on tl0 tlphy0: on miibus0 tlphy0: 10base2/BNC, 10base5/AUI, 10baseT, 10baseT-FDX, auto isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0xf100-0xf10f at device 20.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 eisa0: on motherboard mainboard0: on eisa0 slot 0 orm0: at iomem 0xc-0xc7fff,0xe8000-0xedfff,0xee000-0xe on isa0 pmtimer0 on isa0 pca0 at port 0x40 on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: cannot reserve I/O port range IPsec: Initialized Security Association Processing. ncp_load: [210-213] ad1: 8207MB [16676/16/63] at ata0-slave WDMA2 acd0: CDROM at ata0-master PIO3 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at sym1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 255H 63S/T 522C) Copyright (c) 1992-2003 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.9-STABLE #0: Tue Dec 2 21:45:22 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/slow_4_9 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xf9ff real memory = 301989888 (294912K bytes) avail memory = 288219136 (281464K bytes) Preloaded elf kernel "kernel" at 0xc0491000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c. ccd0-3: Concatenated disk drivers VESA: v1.2, 1024k memory, flags:0x0, mode table:0xc03f8994 (114) VESA: STB COMPAQ 5440 Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 8.0 on pci0 pci1: on pcib1 sym0: <875> port 0x7000-0x70ff mem 0x4010-0x40100fff,0x40102000-0x401020ff irq 5 at device 4.0 on pci1 sym0: No NVRAM, ID 7, Fast-20, SE, parity checking sym1: <875> port 0x7400-0x74ff mem 0x40101000-0x40101fff,0x40102100-0x401021ff irq 5 at device 8.0 on pci1 sym1: No NVRAM, ID 7, Fast-20, SE, parity checking pci1: at 9.0 tl0: port 0x6000-0x600f mem 0x4000-0x400f irq 9 at device 16.0 on pci0 tl0: Ethernet address: 00:80:5f:35:d8:6d miibus0: on tl0 tlphy0: on miibus0 tlphy0: 10base2/BNC, 10base5/AUI, 10baseT, 10baseT-FDX, auto isab0: at device 20.0 on pci0 isa0: on isab0 atapci0: port 0xf100-0xf10f at device 20.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 eisa0: on motherboard m
USB Question: unable to open /dev/ugen0 more than once
Hello peoples, Question: Should I be able to open /dev/ugen0 more than once? I am using FreeBSD 4.9-Stable, libusb-0.1.7. >From reading the libusb docs, you must open the device for each interface you want to acquire. However, once it is opened once, it can't be opened again. Furthermore, calls to usb_find_devices() shows that /dev/ugen0 has disappeared. Investigation on how they(libusb) finds devices, shows they are trying to open the device read only... this is where it tries to open it the second time. This second try fails and therefore libusb thinks the device was removed. Question: Is this the correct behavior? Any help/insight would be greatly appreciated. Michael E Mercer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mergemaster fails when building temproot
Thanks, that was it! later Michael On Fri, 2003-09-05 at 13:31, Gregory Neil Shapiro wrote: > > mergemaster fails saying freebsd.cf does not exist when > > building temproot. > > > > Have I missed something here? > > You need to install the new version of mergemaster before > running it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mergemaster fails when building temproot
Hello peoples, mergemaster fails saying freebsd.cf does not exist when building temproot. Have I missed something here? Thanks Michael Mercer cd /usr/src/etc/sendmail; make distribution install -C -o root -g wheel -m 644 /usr/src/etc/sendmail/freebsd.mc freebsd.cf /var/tmp/temproot/etc/mail install: freebsd.cf: No such file or directory *** Error code 71 Stop in /usr/src/etc/sendmail. *** Error code 1 Stop in /usr/src/etc. *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to the temproot environment ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
THANKS!!! Re: USB mouse/keyboard causes kernel panic during bootsequence
As of Saturday evening, the kernel no longer panics and boots up fine with USB devices plugged in. THANK YOU! THANK YOU! THANK YOU! to the person who made the last change to USB code! later Michael Mercer On Wed, 2003-07-09 at 21:48, Michael E. Mercer wrote: > > > > There is one last thing you can do: put > > > > options DDB > > > > in your kernel config file. Recompile. Reproduce. > > > > ddb> trace > > > > ... > > > > ddb> continue > > > > ... > > > > ddb> continue > > > > Uptime - 0s > > > > Rebooting... > > > > > > > > -- Josh > > Next time it involves this much typing... don't tell me... :P > > uhci_idone(0,c2e17180,c2e18000,c2e17180,c0494d6c) at +0xc > uhci_waitintr(c2e18000,c2e17180,c2e17180,8,c0494d7c) at +0xb6 > uhci_device_ctrl_start(c2e17180,0,c0494da4,c026f219,c2e17180) at +0x2c > uhci_device_ctrl_transfer(c2e,17180,0,c2e17180,c0494e0c,c026fc12) at > +0x1f > usbd_transfer(c2e17180,c0494dd4,c026fc1b,c2e17180,c2e17130) at +0xd1 > usbd_sync_transfer(c2e17180,c2e17130,c2e17100,c2e17130,c2e0daf0) at > +0x10 > usbd_request_flags(c2e17100,c0494e0c,c2e17130,0,0) at +0x5f > usbd_do_request(c2e17100,c0494e0c,c2e17130,c2e17100,0) at +0x18 > usbd_get_desc(c2e17100,1,0,8,c2e17130) at +0x67 > usbd_new_device(c2e17300,c2e18000,1,200,1,c2e17260) at +0x148 > uhub_explore(c2e17480,c2e17500,c2e17c00,0,c0494ea0) at +0x2be > usb_attach(c2e17500,c0494ebc,c0186f0f,c2e17500,c2e18000) at +0x112 > DEVICE_ATTACH(c2e17500,c2e18000,c2e17c00,0,1) at +0x2e > device_probe_and_attach(c2e17500) at +0x63 > uhci_pci_attach(c2e17c00,c0494f08,c0186f0f,c2e17c00,c2e17c00) at +0x2c6 > DEVICE_ATTACH(c2e17c00,c2e17c00,c2e16280,0,0) at +0x2e > device_probe_and_attach(c2e17c00) at +0x63 > bus_generic_attach(c2e16100,c0494f40,c0186f0f,c2e16100,c2e16100) at > +0x16 > DEVICE_ATTACH(c2e16100,c2e16100,c2e16400,0,1) at +0x2e > device_probe_and_attach(c2e16100) at +0x63 > bus_generic_attach(c2e16280,c0494f78,c0186f0f,c2e16280,c2e16280) at > +0x16 > DEVICE_ATTACH(c2e16280,c2e16280,c1454880,0,1) at +0x2e > device_probe_and_attach(c2e16280) at +0x63 > bus_generic_attach(c2e16400,c2e16400,c0494fa4,c012dd6e,c2e16400) at > +0x16 > nexus_attach(c2e16400,c0494fc0,c0186f0f,c2e16400,c2e16400) at +0xd > DEVICE_ATTACH(c2e16400,c2e16400,c0386ad0,49c000,1) at +0x2e > device_probe_and_attach(c2e16400) at +0x63 > root_bus_configure(c1454880,c035e6ec,0) at +0x16 > configure(0,491c00,49c00,0,c012d660) at +0x2a > mi_startup(0,0,0,0,0) at +0x69 > begin() at +0x47 > > That's it... hope I read my writing correctly :) > Michael > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tcsh script: quote and spaces problems
ok ok... I noticed one thing while playing with this...
the script hello.sh
#!/bin/tcsh -f
set JUNK='-f "t "'
echo ">>${JUNK}<<"
echo ">>"${JUNK}"<<"
The first echo prints it -f "t "
and the second -f "t "
Can you use it with the double quotes around it?
later
MeM
On Thu, 2003-07-31 at 22:12, Michael E. Mercer wrote:
> On Thu, 2003-07-31 at 21:42, Rob Lahaye wrote:
> > When I use
> >set flag='-f "t "'
> >
>
> When I echo this out, I get what you are wanting...
> can you show us how you are using this, to get the "weird" behavior?
>
> Thanks
> MeM
>
> ___
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tcsh script: quote and spaces problems
On Thu, 2003-07-31 at 21:42, Rob Lahaye wrote: > When I use >set flag='-f "t "' > When I echo this out, I get what you are wanting... can you show us how you are using this, to get the "weird" behavior? Thanks MeM ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: windowmaker problem
Don't know much about bash, but do you need to update your shell's path? For instance, running "rehash" under csh will tell the shell to update its list of executables found in the path. HTH Michael On Wed, 2003-07-23 at 08:32, Rus Foster wrote: > yOn Wed, 23 Jul 2003, marlon corleone wrote: > > > bash-2.05b$ pkg_info | grep -i windowmaker > > wmtop-0.84 Windowmaker dock app to display > > top 3 CPU consuming process > > bash-2.05b$ windowmaker > > bash: windowmaker: command not found > > > > > > why wont windowmaker run? i did install the packaged, > > as you can see. i hope anyone got a tip. > > Try "wmaker.inst" then wmaker > > Rgds > > Rus Foster ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: KDE process is unkillable ==> COMMENT
Mental note: don't use machine maintained by Benjamin... :P Michael On Tue, 2003-07-15 at 14:58, Neu, Benjamin S. wrote: > That's a bunch of non-sense! :) nobody will notice.. If they do then > you show'em who's boss: rmuser * > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 15, 2003 1:56 PM > To: Neu, Benjamin S. > Cc: [EMAIL PROTECTED] > Subject: RE: KDE process is unkillable > > > Reboot! :) > > I can't reboot. This is a server. > > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > [EMAIL PROTECTED] > > Sent: Tuesday, July 15, 2003 1:52 PM > > To: [EMAIL PROTECTED] > > Subject: KDE process is unkillable > > > > Hi all! > > I've got a problem with KDE, maybe you can help me. > > > > I just started KDE as root (yes, I know that's not good). > > KDE hangs and I can't do anything on the console, but I > > can log in over SSH, where I tried to kill KDE. One of > > the processes is in disk wait state and trying to exit. > > > > Is there a way to kill the process? > > I would appreciate any help. > > Thanks in advance. > > > > Daniela > > > > -- > > +++ GMX - Mail, Messaging & more http://www.gmx.net +++ > > > > Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern! > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to question: create mp3 from music video mpeg file?
Hello peoples, I want to extract the audio from a few music videos (mpg,avi) I have and create mp3's from them. However I just can seem to find out how to do this. Thanks Michael Mercer ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [SAGE] FreeBSD 4.4-REL to FreeBSD 4.8-STABLE upgrade problem.
Not sure if this is the problem but my copy of MAKEDEV only makes ad0 thru ad3 when you type sh MAKEDEV all You may still need to run sh MAKEDEV ad4 later MEM On Wed, 2003-07-09 at 21:53, Dustin Puryear wrote: > Before reading below: I am considering a new install rather than an upgrade > of our servers. However, now I just want to beat this problem. :) > > At 02:19 PM 7/8/2003 +, Phil Pennock wrote: > >On 2003-07-08 at 14:09 +, Phil Pennock wrote: > > > There was a fairly major update to the IDE disk device handlers which > > > required new device nodes. Bringing in the new MAKEDEV script and > > > running that to create the disk devices will probably let you boot on > > > the new kernel and try to repair things from there. > > > >Okay, I'll go get more coffee after sending this. You noticed this one. > >Sorry. > > > >There are two mergemaster steps, one which does the minimum needed to > >let the rest of the build continue. > > Yes, I ran 'mergemaster -p' but found that it really only merged my passwd > and group files with the new ones. Unless it did some other things behind > the scenes then there is no fix here. > > >The issue is, as you note, the device stuff. As I said though, just > >pull in MAKEDEV manually and run it. That will fix this. Either > >"sh MAKEDEV all" or "sh MAKEDEV ad0" ... > > I keep thinking it's the device stuff myself, but even MAKEDEV didn't do > the trick (interesting notes below this stuff): > > # cd /usr/src > # make update > # /usr/src/usr.sbin/mergemaster/mergemaster.sh -p > # make buildworld > # make buildkernel > # make installkernel > # cd /etc > # mv MAKEDEV MAKEDEV.old > # cp /usr/src/etc/MAKEDEV . > # sh MAKEDEV all > # reboot > > Upon reboot I get my favorite lines: > > blah, blah > blah, blah > ar0: ... [...] status: READY subdisks: > 0 READY ad4: ... at ata2-master UDMA100 > 1 READY ad6: ... at ata3-master UDMA100 > acd0: CDROM ... at ata0-master PIO4 > Mounting root from ufs:/dev/ad4s1a > Root mount failed: 16 > > Manual root filesystem specification: > blah, blah > > Okay, so I reboot, but this time I load kernel.good and the system comes up > fine with the old 4.4-REL kernel: > > ar0: ... [...] status: READY subdisks: >ad4: ... at ata2-master UDMA100 >ad6: ... at ata3-master UDMA100 > acd0: CDROM ... at ata0-master using PIO4 > > Oh, and I found that this server has a HighPoint RAID controller which can > do RAID 0, 1, 0+1, and JBOD. Looking in my array configuration I see that > we have: > > ChannelMode Status > Primary Master: Mirror (RAID 1) for array #0 UDMA 5HDD0 > Secondary Master: Mirror ... UDMA 5Hidden > > I initially said that this was a Promise controller. > > Here is my /etc/fstab for /: > > /dev/ad4s1a / ufs rw 1 1 > > Following is /var/run/dmesg.log after booting from kernel.good: > > Copyright (c) 1992-2001 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.4-RELEASE #1: Sun Jun 30 21:23:39 CDT 2002 > [EMAIL PROTECTED]:/usr/src/sys/compile/WWW > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 1494468860 Hz > CPU: Pentium 4 (1494.47-MHz 686-class CPU) >Origin = "GenuineIntel" Id = 0xf07 Stepping = 7 > > Features=0x3febf9ff,ACC> > real memory = 268369920 (262080K bytes) > avail memory = 257404928 (251372K bytes) > Preloaded elf kernel "kernel.good" at 0xc0375000. > md0: Malloc disk > Using $PIR table, 12 entries at 0xc00fdea0 > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 irq 12 > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > rl0: port 0x9000-0x90ff mem > 0xd900-0xd9ff irq 11 at device 3.0 on pci2 > rl0: Ethernet address: 00:50:ba:60:7b:83 > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > atapci0: port > 0xa400-0xa4ff,0xa000-0xa003,0x9c00-0x9c07,0x9800-0x9803,0x9400-0x9407 irq > 10 at device 6.0 on pci2 > ata2: at 0x9400 on atapci0 > ata3: at 0x9c00 on atapci0 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port 0xf000-0xf00f at device 31.1 > on pci0 > ata0: at 0x1f0 irq 14 on atapci1 > ata1: at 0x170 irq 15 on atapci1 > pci0: at 31.2 irq 11 > pci0: (vendor=0x8086, dev=0x2443) at 31.3 irq 0 > pci0: at 31.4 irq 11 > pci0: (vendor=0x8086, dev=0x2445) at 31.5 irq 9 > orm0: at iomem 0xcc000-0xcf7ff on isa0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual
Re: USB mouse/keyboard causes kernel panic during boot sequence
> > > There is one last thing you can do: put > > > options DDB > > > in your kernel config file. Recompile. Reproduce. > > > ddb> trace > > > ... > > > ddb> continue > > > ... > > > ddb> continue > > > Uptime - 0s > > > Rebooting... > > > > > > -- Josh Next time it involves this much typing... don't tell me... :P uhci_idone(0,c2e17180,c2e18000,c2e17180,c0494d6c) at +0xc uhci_waitintr(c2e18000,c2e17180,c2e17180,8,c0494d7c) at +0xb6 uhci_device_ctrl_start(c2e17180,0,c0494da4,c026f219,c2e17180) at +0x2c uhci_device_ctrl_transfer(c2e,17180,0,c2e17180,c0494e0c,c026fc12) at +0x1f usbd_transfer(c2e17180,c0494dd4,c026fc1b,c2e17180,c2e17130) at +0xd1 usbd_sync_transfer(c2e17180,c2e17130,c2e17100,c2e17130,c2e0daf0) at +0x10 usbd_request_flags(c2e17100,c0494e0c,c2e17130,0,0) at +0x5f usbd_do_request(c2e17100,c0494e0c,c2e17130,c2e17100,0) at +0x18 usbd_get_desc(c2e17100,1,0,8,c2e17130) at +0x67 usbd_new_device(c2e17300,c2e18000,1,200,1,c2e17260) at +0x148 uhub_explore(c2e17480,c2e17500,c2e17c00,0,c0494ea0) at +0x2be usb_attach(c2e17500,c0494ebc,c0186f0f,c2e17500,c2e18000) at +0x112 DEVICE_ATTACH(c2e17500,c2e18000,c2e17c00,0,1) at +0x2e device_probe_and_attach(c2e17500) at +0x63 uhci_pci_attach(c2e17c00,c0494f08,c0186f0f,c2e17c00,c2e17c00) at +0x2c6 DEVICE_ATTACH(c2e17c00,c2e17c00,c2e16280,0,0) at +0x2e device_probe_and_attach(c2e17c00) at +0x63 bus_generic_attach(c2e16100,c0494f40,c0186f0f,c2e16100,c2e16100) at +0x16 DEVICE_ATTACH(c2e16100,c2e16100,c2e16400,0,1) at +0x2e device_probe_and_attach(c2e16100) at +0x63 bus_generic_attach(c2e16280,c0494f78,c0186f0f,c2e16280,c2e16280) at +0x16 DEVICE_ATTACH(c2e16280,c2e16280,c1454880,0,1) at +0x2e device_probe_and_attach(c2e16280) at +0x63 bus_generic_attach(c2e16400,c2e16400,c0494fa4,c012dd6e,c2e16400) at +0x16 nexus_attach(c2e16400,c0494fc0,c0186f0f,c2e16400,c2e16400) at +0xd DEVICE_ATTACH(c2e16400,c2e16400,c0386ad0,49c000,1) at +0x2e device_probe_and_attach(c2e16400) at +0x63 root_bus_configure(c1454880,c035e6ec,0) at +0x16 configure(0,491c00,49c00,0,c012d660) at +0x2a mi_startup(0,0,0,0,0) at +0x69 begin() at +0x47 That's it... hope I read my writing correctly :) Michael ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
Josh, Is there an easy way to capture this without me having to handwrite all that info down myself? Michael Mercer On Wed, 2003-07-09 at 13:19, Joshua Oreman wrote: > On Tue, Jul 08, 2003 at 01:05:18PM -0400 or thereabouts, Michael E. Mercer wrote: > > On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote: > > > On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote: > > > > Alrighty then, > > > > > > > > Ok, after following FAQ 18.13 on the freebsd web site, > > > > I've been struggling for the last 4 hours trying to get this thing to > > > > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > > > > and also read about kernel init problems need to have dumpdev added to > > > > the loader. So I added it to loader.conf as well. > > > > > > Your swap partition must be at least a few megs bigger than your physical > > > RAM. > > > > > My swap is 1 Gig. I also changed MAXMEM in my kernel to a much smaller > > size... still can not get a dump... > > Ah, silly me. Since this is a device probe panic, rc.conf setting dumpdev > won't ever happen. > > There is one last thing you can do: put > options DDB > in your kernel config file. Recompile. Reproduce. > ddb> trace > ... > ddb> continue > ... > ddb> continue > Uptime - 0s > Rebooting... > > -- Josh > > > > > Any ideas? > > > > > > > > > > Anyways, the method it points to is uhci_idone. > > > > > > Thanks! > > > > No, thank you for your help! > > > > Michael > > > > > > -- Josh > > > > > > > > > > > That's all I can find out at the moment, unless someone can inform me of > > > > what I am doing wrong. > > > > > > > > Thanks > > > > Michael > > > > > > > > > > > > > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > > > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer > > > > > wrote: > > > > > > Anybody?!?!?! > > > > > > > > > > > > > > > > > > > > > > > > Hello peoples, > > > > > > > > > > > > I have posted this before and unfortunately I still have this problem. > > > > > > During the boot sequence, when it probes for the USB devices, it causes > > > > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > > > > and/or keyboard attached. > > > > > > > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > > > > them, they work just fine. > > > > > > > > > > > > Any ideas? > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > > fault virtual address = 0x4 > > > > > > fault code = supervisor read, page not present > > > > > > instruction pointer = 0x8: 0xc02583c4 > > > > > > > > > > > stack pointer = 0x10: 0xc045fd20 > > > > > > frame pointer = 0x10: 0xc045fd3c > > > > > > code segment= base 0x0, limit 0xf, type 0x1b > > > > > > = DPL 0, pres 1, def 32 1, gran 1 > > > > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > > > > current process = 0(swapper) > > > > > > interrupt mask = none <- SMP: XXX > > > > > > trap number = 12 > > > > > > panic: page fault > > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > > Uptime - 0s > > > > > > > > > > That pointer I highlighted is important; it is also kernel-dependent. > > > > > Please read FAQ #18.13 to find out how to give us some useful function names, > > > > > or better yet, a backtrace. > > > > > > > > > > -- Josh > > > > > > > > > > > > > > > > > Thanks > > > > > > Michael Mercer > > > > > > > > > > > > > > > > > > ___ > > > > > > [EMAIL PROTECTED] mailing list > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote: > On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote: > > Alrighty then, > > > > Ok, after following FAQ 18.13 on the freebsd web site, > > I've been struggling for the last 4 hours trying to get this thing to > > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > > and also read about kernel init problems need to have dumpdev added to > > the loader. So I added it to loader.conf as well. > > Your swap partition must be at least a few megs bigger than your physical > RAM. > My swap is 1 Gig. I also changed MAXMEM in my kernel to a much smaller size... still can not get a dump... Any ideas? > > > > Anyways, the method it points to is uhci_idone. > > Thanks! No, thank you for your help! Michael > > -- Josh > > > > > That's all I can find out at the moment, unless someone can inform me of > > what I am doing wrong. > > > > Thanks > > Michael > > > > > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote: > > > > Anybody?!?!?! > > > > > > > > > > > > > > > > Hello peoples, > > > > > > > > I have posted this before and unfortunately I still have this problem. > > > > During the boot sequence, when it probes for the USB devices, it causes > > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > > and/or keyboard attached. > > > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > > them, they work just fine. > > > > > > > > Any ideas? > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > fault virtual address = 0x4 > > > > fault code = supervisor read, page not present > > > > instruction pointer = 0x8: 0xc02583c4 > > > > > > > stack pointer = 0x10: 0xc045fd20 > > > > frame pointer = 0x10: 0xc045fd3c > > > > code segment= base 0x0, limit 0xf, type 0x1b > > > > = DPL 0, pres 1, def 32 1, gran 1 > > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > > current process = 0(swapper) > > > > interrupt mask = none <- SMP: XXX > > > > trap number = 12 > > > > panic: page fault > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > Uptime - 0s > > > > > > That pointer I highlighted is important; it is also kernel-dependent. > > > Please read FAQ #18.13 to find out how to give us some useful function names, > > > or better yet, a backtrace. > > > > > > -- Josh > > > > > > > > > > > Thanks > > > > Michael Mercer > > > > > > > > > > > > ___ > > > > [EMAIL PROTECTED] mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
Alrighty then, Ok, after following FAQ 18.13 on the freebsd web site, I've been struggling for the last 4 hours trying to get this thing to dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf and also read about kernel init problems need to have dumpdev added to the loader. So I added it to loader.conf as well. Anyways, the method it points to is uhci_idone. That's all I can find out at the moment, unless someone can inform me of what I am doing wrong. Thanks Michael On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote: > > Anybody?!?!?! > > > > > > > > Hello peoples, > > > > I have posted this before and unfortunately I still have this problem. > > During the boot sequence, when it probes for the USB devices, it causes > > a kernel panic (page fault) if there is either (or both) a USB mouse > > and/or keyboard attached. > > > > If I remove the mouse and keyboard and let it boot up, then connect > > them, they work just fine. > > > > Any ideas? > > > Fatal trap 12: page fault while in kernel mode > > mp_lock = 0024; cpuid = 0; lapic.id = > > fault virtual address = 0x4 > > fault code = supervisor read, page not present > > instruction pointer = 0x8: 0xc02583c4 > > > stack pointer = 0x10: 0xc045fd20 > > frame pointer = 0x10: 0xc045fd3c > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def 32 1, gran 1 > > processor eflags= interrupt enabled, resume, IOPC=0 > > current process = 0(swapper) > > interrupt mask = none <- SMP: XXX > > trap number = 12 > > panic: page fault > > mp_lock = 0024; cpuid = 0; lapic.id = > > Uptime - 0s > > That pointer I highlighted is important; it is also kernel-dependent. > Please read FAQ #18.13 to find out how to give us some useful function names, > or better yet, a backtrace. > > -- Josh > > > > > Thanks > > Michael Mercer > > > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB mouse/keyboard causes kernel panic during boot sequence
Anybody?!?!?! Hello peoples, I have posted this before and unfortunately I still have this problem. During the boot sequence, when it probes for the USB devices, it causes a kernel panic (page fault) if there is either (or both) a USB mouse and/or keyboard attached. If I remove the mouse and keyboard and let it boot up, then connect them, they work just fine. Any ideas? Thanks Michael Mercer uname -a FreeBSD dual.mmercer.com 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 1 11:44:10 EDT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/dualII_4_8 i386 snippet from dmesg uhci0: port 0xef80-0xef9f irq 2 at device 7.2 on pci0 uhci0: LegSup = 0x003a usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ERROR MESSAGE uhub2: 2 ports with 2 removable, self powered Fatal trap 12: page fault while in kernel mode mp_lock = 0024; cpuid = 0; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc02583c4 stack pointer = 0x10: 0xc045fd20 frame pointer = 0x10: 0xc045fd3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPC=0 current process = 0(swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0024; cpuid = 0; lapic.id = Uptime - 0s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fatal Trap 12 on SMP
On Tue, 2003-07-01 at 18:11, Susan wrote: > MY equipment is a Tyan 2460 dual CPU with 760 of ram. I am running > FreeBSD 5.1 Release without the SMP compilied into the kernel.When I > build and install kernel with the SMP components the new kernel will not > load. I get the Fatal Trap 12 error. I have compiled the SMP components I get a Fatal Trap 12 with Tyan Tiger 100 dual processors and SMP compiled into the kernel only when I have a USB device attached when FreeBSD is booting. later MeM ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB mouse/keyboard causes kernel panic during boot sequence
Hello peoples, I have posted this before and unfortunately I still have this problem. During the boot sequence, when it probes for the USB devices, it causes a kernel panic (page fault) if there is either (or both) a USB mouse and/or keyboard attached. If I remove the mouse and keyboard and let it boot up, then connect them, they work just fine. Any ideas? Thanks Michael Mercer uname -a FreeBSD dual.mmercer.com 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 1 11:44:10 EDT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/dualII_4_8 i386 snippet from dmesg uhci0: port 0xef80-0xef9f irq 2 at device 7.2 on pci0 uhci0: LegSup = 0x003a usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ERROR MESSAGE uhub2: 2 ports with 2 removable, self powered Fatal trap 12: page fault while in kernel mode mp_lock = 0024; cpuid = 0; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc02583c4 stack pointer = 0x10: 0xc045fd20 frame pointer = 0x10: 0xc045fd3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPC=0 current process = 0(swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0024; cpuid = 0; lapic.id = Uptime - 0s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB mouse/keyboard causes kernel panic during boot sequence
Hello peoples, I have posted this before and unfortunately I still have this problem. During the boot sequence, when it probes for the USB devices, it causes a kernel panic (page fault) if there is either (or both) a USB mouse and/or keyboard attached. If I remove the mouse and keyboard and let it boot up, then connect them, they work just fine. Any ideas? Thanks Michael Mercer uhub2: 2 ports with 2 removable, self powered Fatal trap 12: page fault while in kernel mode mp_lock = 0024; cpuid = 0; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc02583c4 stack pointer = 0x10: 0xc045fd20 frame pointer = 0x10: 0xc045fd3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPC=0 current process = 0(swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0024; cpuid = 0; lapic.id = Uptime - 0s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Java support
On Wed, 2003-06-11 at 13:24, Augusto Jun Devegili wrote: > Hhmm. Does this mean that, if I install a Mozilla binary compiled for > Linux, plugins might work? I would assume yes, but do not know for sure... MeM > > Michael E. Mercer wrote: > > Keep in mind that any port with "linux" in the name is a linux binary > > and runs on FreeBSD under linux emulation. Therefore linux plugins will > > not run with native applications. > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Java support
On Wed, 2003-06-11 at 11:49, Augusto Jun Devegili wrote: > Hi all, > > I'm using FreeBSD 5.1-RELEASE and managed to install JDK 1.4.1. However, > I'm not being able to install the Java plugin for Mozilla. > linux-sun-jdk1.4.1 comes with plugins for netscape (ns4, ns600 and > ns610), but none of them worked with my Mozilla 1.1. > > Any ideas? > Keep in mind that any port with "linux" in the name is a linux binary and runs on FreeBSD under linux emulation. Therefore linux plugins will not run with native applications. later MeM > TIA, > > Augusto > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Java support
I would suggest you fully read these pages... http://www.freebsd.org/java after that, to get a usable jdk14 upgrade freebsd to 4.8-Stable. later MeM On Wed, 2003-06-11 at 11:19, Michael Vest wrote: > Dear FreeBSD, > > I am curently running FreeBSD 4.5. I am interested in doing > Java development on FreeBSD. I have installed Java 1.1.8 via the > /usr/ports mechanism. It works fine. However, when I try to make > some of the later versions of Java (1.2, 1.3, and 1.4), I get errors > during the make process. Are these later versions supported? If so, > what is the best way to install them? > > Mike Vest > [EMAIL PROTECTED] > > > - > Do you Yahoo!? > Free online calendar with sync to Outlook(TM). > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Mount additional hard drive (ufs)
On Sun, 2003-06-08 at 11:48, Martin Schweizer wrote: > Hello > > I installed a second hard drive (ufs) and mount it (like described in the > handbook) but if I reboot it isn't anymore mounted? After a reboot I have to > re-mount the second hard drive again and all works fine. What do I forget? add an entry to /etc/fstab ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 4.7 +JDK 1.4.x
Check the archives, a patch is out there to get them to work as a normal user... later MEM Pascal Giannakakis wrote: > Hi there, > > did anybody ever get this (FreeBSD 4.7 and JDK 1.4.x) to run? While it > works as root, it crashes immediately with any other users. I have tried sun, > blackdown and ibm JDKs, none of them worked with "normal" users. IBM freezed > even as root. > > Sticking with 1.3.1 is not an option in this case. If you have any tips, > please let me know! > > Thx > > -- > +++ GMX - Mail, Messaging & more http://www.gmx.net +++ > NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen! > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: sound vchans and gaim sound conflict
Jim, I had this problem for a bit, but just recently cvsup'd source and saw a sound.c change. I rebuilt world and I haven't had that annoying buzzing since Not sure if it will help you but its probably worth a try... later Michael Mercer Jim Arnold wrote: > Sometimes when I use Gaim and I get too many sounds > going at once my sound card gets confused and starts a > loud buzzing that can only be stopped by a reboot. > This seems to happen when two people IM me at the same > time. > > I turned off the sound in Gaim for all but incoming > messages but I still have that problem on occasion. > Having to reboot for this is pretty lame. > > My sysctl.conf is set to: hw.snd.pcm0.vchans=4 > Xmms uses dev/dsp0.3 and Gaim uses /drv/dsp0.1 > > Here's my audio card: > pcm0: port 0xe800-0xe83f irq 9 at > device 11.0 on pci0 > > The above did eliminate those annoying messages that > another app had grabbed the sound card. Any ideas on > how to get this to stop? Is it just a byproduct of a > cheap sound card? > > Thanks, > Jim > > __ > Do you Yahoo!? > Yahoo! Web Hosting - Let the expert host your site > http://webhosting.yahoo.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
healthd question: how do I correct the problems healthd complains about?
Hello peoples, I just recently installed healthd and it is printing these messages... healthd: A value of 2.06 for CPU #0 Core Voltage with a range of (1.95 <= n <= 2.05) healthd: A value of 31.00 for Chip Set Temperature with a range of (0.00 <= n <= 30.00) healthd: A value of -5.76 for -5 Volt with a range of (-5.50 <= n <= -4.50) healthd: A value of -13.89 for -12 Volt with a range of (-13.20 <= n <= -10.80) healthd: A value of 0.00 for CPU #0 Cooling Fan with a range of (3000.00 <= n <= .00) healthd: A value of 1.00 for CPU #1 Temperature with a range of (10.00 <= n <= 30.00) How do I correct these problems? thanks Michael Mercer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
HELP. KDE3 locks up system,
Hello all, Once KDE3 locks up system, nothing can be done except to hit the power button. I rebuilt the world and kernel based on todays cvsup and it still locks up 4.7-STABLE KDE 3.0.4 This is actually my second attempt at sending this email, because the system locked up while I was writing the first one. Any help would be appreciated... otherwise I will be forced to use some other desktop environment, but I really like KDE. thanks Michael Mercer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Machine locks up when running KDE3...
Hello, The machine locks up shortly after starting KDE3. I have deinstalled XF86 and KDE3 and reinstalled from scratch. It still locks up. Any help would be greatly appreciated... what information do you need ? thanks Michael Mercer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: speaker now makes buzzing noise...
Brett, Thanks for the info, but that does not help. The buzzing continues Thanks Michael Mercer Brett Harris wrote: > Michael, > > > However, I used GAIM and after a few messages from > > people, the speakers start > > buzzing and the only way I can stop it is to reboot. > > You may find that the noise is your soundcard picking > up interference from your hard drives etc. Ive noticed > that if your CDrom/aux/mic inputs are turned up, they > will pick up interference. If you're not using your > mic/aux/cdrom etc inputs, you should turn them down. > Look at the man page for 'mixer', but from memory it's > something like: > > mixer mic 0:0 > > I usually put similar lines in rc.local, one for each > sound 'device' I'm not using, as well as boosting the > treble to about 80 and the bass to 60, just for a > little more oomph :) > > Hope this helped, its my first day on these lists :) > > Brett Harris > > http://careers.yahoo.com.au - Yahoo! Careers > - 1,000's of jobs waiting online for you! > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: speaker now makes buzzing noise...
Sue Blake wrote: > On Sun, Nov 03, 2002 at 06:58:58PM -0500, Michael E Mercer wrote: > > Hello all, > > > > I recently followed the instructions to from > > http://www.onlamp.com/pub/a/bsd/2002/09/19/FreeBSD_Basics.html > > > > and added all the lines in the files it states... > > > > I rebooted my machine and all seems fine. > > > > However, I used GAIM and after a few messages from people, the speakers start > > buzzing and the only way I can stop it is to reboot. > > > > How to do I stop this noise, and hopefully fix it altogether? > > Are any error messages written to /var/log/messages when that happens? > Nov 3 18:39:53 dual /kernel: pcm0:virtual:2: play interrupt timeout, channel dead the only thing I see related to sound... thanks Michael > > -- > > Regards, > -*Sue*- > > http://www.sievx.com/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
speaker now makes buzzing noise...
Hello all, I recently followed the instructions to from http://www.onlamp.com/pub/a/bsd/2002/09/19/FreeBSD_Basics.html and added all the lines in the files it states... I rebooted my machine and all seems fine. However, I used GAIM and after a few messages from people, the speakers start buzzing and the only way I can stop it is to reboot. How to do I stop this noise, and hopefully fix it altogether? thank you Michael Mercer To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
UPDATE: configure scripts failing in ports looking for libXext
Hello peoples,
After looking at the config.log file, the problem seems to be a missing
-L/usr/X11R6/lib from the compile line when it is testing for Xext.
I noticed it is in other compile lines preceding the Xext test but not
there for Xext.
Where is the actual problem here? I have never tried to modify a configure
script.
Thanks
Michael Mercer
--
Sorry if this is a repeat, got a response that this email was not allowed...
I subscribed to freebsd-questions and now resent this...
later
Michael
Hello,
Has anyone came across this error and know how to fix it?
Thanks
Michael Mercer
the ports are ksetispy, ksetiwatch, and uml.
They all complain about not finding libXext.
It is found in /usr/X11R6/lib directory.
root on dual(ttyp5), 2002/10/24 Thu 14:55:32
/usr/ports
> ls -l /usr/X11R6/lib/libXext*
-rw-r--r-- 1 root wheel 72204 Oct 22 09:33 /usr/X11R6/lib/libXext.a
lrwxr-xr-x 1 root wheel 12 Oct 22 09:33 /usr/X11R6/lib/libXext.so@ ->
libXext.so.6
-rwxr-xr-x 1 root wheel 62684 Oct 22 09:33 /usr/X11R6/lib/libXext.so.6*
output from configure...
+
root on dual(ttyp3), 2002/10/24 Thu 14:53:40
/usr/ports/devel/uml
> make
===> Configuring for uml-1.0.3
/bin/mkdir -p /usr/ports/devel/uml/work/uml-1.0.3/auto-bin
/bin/ln -sf /usr/local/bin/autoconf213
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/autoconf
/bin/ln -sf /usr/local/bin/autoheader213
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/autoheader
/bin/ln -sf /usr/local/bin/automake14
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/automake
/bin/ln -sf /usr/local/bin/aclocal14
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/aclocal
cd /usr/ports/devel/uml/work/uml-1.0.3 && env
PATH=/usr/ports/devel/uml/work/uml-1.0.3/auto-bin:$PATH gmake -f Makefile.dist
This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** Creating acinclude.m4
!!! If you get recursion errors from autoconf, it is advisable to set the
environment variable M4 to something including "--nesting-limit=500"
*** Creating list of subdirectories
*** Creating configure.in
*** Creating aclocal.m4
*** Creating configure
*** Creating config.h template
*** Creating Makefile templates
*** Postprocessing Makefile templates
*** Creating date/time stamp
*** Finished
Don't forget to run ./configure
If you haven't done so in a while, run ./configure --help
loading cache ./config.cache
checking host system type... i386-portbld-freebsd4.7
checking target system type... i386-portbld-freebsd4.7
checking build system type... i386-portbld-freebsd4.7
checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... (cached) cc
checking whether the C compiler (cc -O -pipe -w ) works... yes
checking whether the C compiler (cc -O -pipe -w ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for c++... (cached) c++
checking whether the C++ compiler (c++ -O -pipe -w ) works... yes
checking whether the C++ compiler (c++ -O -pipe -w ) is a cross-compiler...
no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking whether c++ supports -fno-exceptions... (cached) yes
checking whether c++ supports -fno-check-new... (cached) yes
checking whether c++ supports -fexceptions... (cached) yes
checking how to run the C++ preprocessor... (cached) c++ -E
checking whether c++ supports -frepo... (cached) yes
checking for ld used by GCC... (cached) /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... (cached) yes
checking for /usr/libexec/elf/ld option to reload object files... (cached) -r
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking how to recognise dependant libraries... (cached) pass_all
checking for ranlib... (cached) ranlib
checking for strip... (cached) strip
checking for Cygwin environment... (cached) no
checking for mingw32 environment... (cached) no
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking whether -lc should be explicitly linked in... (cached) no
checking for objdir... .libs
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... (cached) yes
checking if cc static flag -static works... (cached) yes
finding the maximum length of command line arguments... (cached) 36865
checking if cc supports -c -o file.o... (cached) yes
checking if cc supports -fno-rtti -fno-exc
Re: RESEND: configure scripts failing in ports looking for libXext
Kent, Thanks for that info however I completely removes all ports on this last upgrade. I cvsup'd all source and ports... I have been running KDE3 and XFree86-4 for a very long time now with no problems. This problem here just started 2 days ago when I rebuilt everything. Any more suggestions? Thanks Michael Mercer Kent Stewart wrote: > Michael E Mercer wrote: > > Sorry if this is a repeat, got a response that this email was not allowed... > > I subscribed to freebsd-questions and now resent this... > > > > later > > Michael > > > > > > Hello, > > > > Has anyone came across this error and know how to fix it? > > It always occured on my machines when I mixed bag kde-3 and XFree86. > If you are upgrading from major levels, it works better if you remove > them first and then upgrade. Kde-3 doesn't work with XFree86-3.x.x. It > is just the initial install where this happens. I think XFree86-4 > stores stuff in different areas. For example, you need to rename > /etc/XF86Config to something else and then configure version 4. > > Kent > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
RESEND: configure scripts failing in ports looking for libXext
Sorry if this is a repeat, got a response that this email was not allowed...
I subscribed to freebsd-questions and now resent this...
later
Michael
Hello,
Has anyone came across this error and know how to fix it?
Thanks
Michael Mercer
the ports are ksetispy, ksetiwatch, and uml.
They all complain about not finding libXext.
It is found in /usr/X11R6/lib directory.
root on dual(ttyp5), 2002/10/24 Thu 14:55:32
/usr/ports
> ls -l /usr/X11R6/lib/libXext*
-rw-r--r-- 1 root wheel 72204 Oct 22 09:33 /usr/X11R6/lib/libXext.a
lrwxr-xr-x 1 root wheel 12 Oct 22 09:33 /usr/X11R6/lib/libXext.so@ ->
libXext.so.6
-rwxr-xr-x 1 root wheel 62684 Oct 22 09:33 /usr/X11R6/lib/libXext.so.6*
output from configure...
+
root on dual(ttyp3), 2002/10/24 Thu 14:53:40
/usr/ports/devel/uml
> make
===> Configuring for uml-1.0.3
/bin/mkdir -p /usr/ports/devel/uml/work/uml-1.0.3/auto-bin
/bin/ln -sf /usr/local/bin/autoconf213
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/autoconf
/bin/ln -sf /usr/local/bin/autoheader213
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/autoheader
/bin/ln -sf /usr/local/bin/automake14
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/automake
/bin/ln -sf /usr/local/bin/aclocal14
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/aclocal
cd /usr/ports/devel/uml/work/uml-1.0.3 && env
PATH=/usr/ports/devel/uml/work/uml-1.0.3/auto-bin:$PATH gmake -f Makefile.dist
This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** Creating acinclude.m4
!!! If you get recursion errors from autoconf, it is advisable to set the
environment variable M4 to something including "--nesting-limit=500"
*** Creating list of subdirectories
*** Creating configure.in
*** Creating aclocal.m4
*** Creating configure
*** Creating config.h template
*** Creating Makefile templates
*** Postprocessing Makefile templates
*** Creating date/time stamp
*** Finished
Don't forget to run ./configure
If you haven't done so in a while, run ./configure --help
loading cache ./config.cache
checking host system type... i386-portbld-freebsd4.7
checking target system type... i386-portbld-freebsd4.7
checking build system type... i386-portbld-freebsd4.7
checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... (cached) cc
checking whether the C compiler (cc -O -pipe -w ) works... yes
checking whether the C compiler (cc -O -pipe -w ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for c++... (cached) c++
checking whether the C++ compiler (c++ -O -pipe -w ) works... yes
checking whether the C++ compiler (c++ -O -pipe -w ) is a cross-compiler...
no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking whether c++ supports -fno-exceptions... (cached) yes
checking whether c++ supports -fno-check-new... (cached) yes
checking whether c++ supports -fexceptions... (cached) yes
checking how to run the C++ preprocessor... (cached) c++ -E
checking whether c++ supports -frepo... (cached) yes
checking for ld used by GCC... (cached) /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... (cached) yes
checking for /usr/libexec/elf/ld option to reload object files... (cached) -r
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking how to recognise dependant libraries... (cached) pass_all
checking for ranlib... (cached) ranlib
checking for strip... (cached) strip
checking for Cygwin environment... (cached) no
checking for mingw32 environment... (cached) no
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking whether -lc should be explicitly linked in... (cached) no
checking for objdir... .libs
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... (cached) yes
checking if cc static flag -static works... (cached) yes
finding the maximum length of command line arguments... (cached) 36865
checking if cc supports -c -o file.o... (cached) yes
checking if cc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared libraries...
yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.7 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libra
configure scripts failing in ports looking for libXext
Hello,
Has anyone came across this error and know how to fix it?
Thanks
Michael Mercer
the ports are ksetispy, ksetiwatch, and uml.
They all complain about not finding libXext.
It is found in /usr/X11R6/lib directory.
root on dual(ttyp5), 2002/10/24 Thu 14:55:32
/usr/ports
> ls -l /usr/X11R6/lib/libXext*
-rw-r--r-- 1 root wheel 72204 Oct 22 09:33 /usr/X11R6/lib/libXext.a
lrwxr-xr-x 1 root wheel 12 Oct 22 09:33 /usr/X11R6/lib/libXext.so@ ->
libXext.so.6
-rwxr-xr-x 1 root wheel 62684 Oct 22 09:33 /usr/X11R6/lib/libXext.so.6*
output from configure...
+
root on dual(ttyp3), 2002/10/24 Thu 14:53:40
/usr/ports/devel/uml
> make
===> Configuring for uml-1.0.3
/bin/mkdir -p /usr/ports/devel/uml/work/uml-1.0.3/auto-bin
/bin/ln -sf /usr/local/bin/autoconf213
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/autoconf
/bin/ln -sf /usr/local/bin/autoheader213
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/autoheader
/bin/ln -sf /usr/local/bin/automake14
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/automake
/bin/ln -sf /usr/local/bin/aclocal14
/usr/ports/devel/uml/work/uml-1.0.3/auto-bin/aclocal
cd /usr/ports/devel/uml/work/uml-1.0.3 && env
PATH=/usr/ports/devel/uml/work/uml-1.0.3/auto-bin:$PATH gmake -f Makefile.dist
This Makefile is only for the CVS repository
This will be deleted before making the distribution
*** Creating acinclude.m4
!!! If you get recursion errors from autoconf, it is advisable to set the
environment variable M4 to something including "--nesting-limit=500"
*** Creating list of subdirectories
*** Creating configure.in
*** Creating aclocal.m4
*** Creating configure
*** Creating config.h template
*** Creating Makefile templates
*** Postprocessing Makefile templates
*** Creating date/time stamp
*** Finished
Don't forget to run ./configure
If you haven't done so in a while, run ./configure --help
loading cache ./config.cache
checking host system type... i386-portbld-freebsd4.7
checking target system type... i386-portbld-freebsd4.7
checking build system type... i386-portbld-freebsd4.7
checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel
checking whether build environment is sane... yes
checking whether gmake sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... (cached) cc
checking whether the C compiler (cc -O -pipe -w ) works... yes
checking whether the C compiler (cc -O -pipe -w ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether cc accepts -g... (cached) yes
checking for c++... (cached) c++
checking whether the C++ compiler (c++ -O -pipe -w ) works... yes
checking whether the C++ compiler (c++ -O -pipe -w ) is a cross-compiler...
no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking whether c++ supports -fno-exceptions... (cached) yes
checking whether c++ supports -fno-check-new... (cached) yes
checking whether c++ supports -fexceptions... (cached) yes
checking how to run the C++ preprocessor... (cached) c++ -E
checking whether c++ supports -frepo... (cached) yes
checking for ld used by GCC... (cached) /usr/libexec/elf/ld
checking if the linker (/usr/libexec/elf/ld) is GNU ld... (cached) yes
checking for /usr/libexec/elf/ld option to reload object files... (cached) -r
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
checking how to recognise dependant libraries... (cached) pass_all
checking for ranlib... (cached) ranlib
checking for strip... (cached) strip
checking for Cygwin environment... (cached) no
checking for mingw32 environment... (cached) no
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking whether -lc should be explicitly linked in... (cached) no
checking for objdir... .libs
checking for cc option to produce PIC... -fPIC -DPIC
checking if cc PIC flag -fPIC -DPIC works... (cached) yes
checking if cc static flag -static works... (cached) yes
finding the maximum length of command line arguments... (cached) 36865
checking if cc supports -c -o file.o... (cached) yes
checking if cc supports -fno-rtti -fno-exceptions ... yes
checking whether the linker (/usr/libexec/elf/ld) supports shared libraries...
yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... freebsd4.7 ld.so
checking command to parse /usr/bin/nm -B output... ok
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for dlfcn.h... (cached) yes
checking whether a program can dlopen itself... (cach
