pkg_add conflicts
Can someone tell me, when was the @conflicts command added to the package system? I keep trying to install things on my 4.9-RELEASE box and getting complaints from pkg_add about this command. -Rob D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel
On Monday 01 November 2004 16:09, Martes Wigglesworth wrote: > My kernel panic seems to come from the usb port actually having a device > in the port, at boot. When I do not have a device in the port, bootup > continues, however, my usb ports are not usable. This is my dmesg > output. > > > dmesg|grep usb > > usb0: on uhci0 > usb0: USB revision 1.0 > usb1: on uhci1 > usb1: USB revision 1.0 > usb2: on uhci2 > usb2: USB revision 1.0 Over a week ago I discovered a bug in the UHCI driver that causes problems when devices are plugged in during boot. I filed a PR with a patch that has been taken into the UHCI driver in -CURRENT : http://www.freebsd.org/cgi/query-pr.cgi?pr=73000 Can you try the patch that's at the end of the PR on your system? (It should patch without a problem on 5.2.1-RELEASE). I'm not sure if it fixes your problem since your problem seems to be EHCI-related, but you never know. Good luck, Daan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel
Martin Nilsson wrote: Martes Wigglesworth wrote: My kernel panic seems to come from the usb port actually having a device in the port, at boot. When I do not have a device in the port, bootup continues, however, my usb ports are not usable. This is my dmesg output. I have the same problem with a SeverWorks P3 machine and a 7in1 USB cardreader. It panics at the end of kernel init if the cardreader is plugged into the machine. This machine does not have EHCI controller or USB 2.0 I don't know if this considered a showstopper for 5.3R but it can be very confusing if you don't know what is causing the panic! Not a good first FreeBSD experience! I don't think this constitutes a show stopper. A show stopper would be if a bug in sysinstall caused it to zero all your harddrives regardless of your desires. -- Ryan Sommers [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel
Martes Wigglesworth wrote: My kernel panic seems to come from the usb port actually having a device in the port, at boot. When I do not have a device in the port, bootup continues, however, my usb ports are not usable. This is my dmesg output. I have the same problem with a SeverWorks P3 machine and a 7in1 USB cardreader. It panics at the end of kernel init if the cardreader is plugged into the machine. This machine does not have EHCI controller or USB 2.0 I don't know if this considered a showstopper for 5.3R but it can be very confusing if you don't know what is causing the panic! Not a good first FreeBSD experience! /Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel
My kernel panic seems to come from the usb port actually having a device in the port, at boot. When I do not have a device in the port, bootup continues, however, my usb ports are not usable. This is my dmesg output. > dmesg|grep usb usb0: on uhci0 usb0: USB revision 1.0 usb1: on uhci1 usb1: USB revision 1.0 usb2: on uhci2 usb2: USB revision 1.0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 usb3: unrecoverable error, controller halted usb3: blocking intrs 0x10 usb3: port reset timeout > Any ideas? I am not getting mail from the questions forum, yet, so I just thought that I would post here, just in case someone has a solution -- Respectfully, M.G.W. System: Asus M6N Intel Dothan 1.7 512MB RAM 40GB HD 10/100/1000 NIC Wireless b/g (not working yet) BSD-5.2.1 GCC-3.3.5/3.3.3(until I replace indigenous gcc) IFORT-for linux(Intell Fortran) gfortran python-2.3 Perl-5.6.1/5.8.5 Java-sdk-1.4.2_5 KDE-3.1.4 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel
My kernel panic seems to come from the usb port actually having a device in the port, at boot. When I do not have a device in the port, bootup continues, however, my usb ports are not usable. This is my dmesg output. > dmesg|grep usb usb0: on uhci0 usb0: USB revision 1.0 usb1: on uhci1 usb1: USB revision 1.0 usb2: on uhci2 usb2: USB revision 1.0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 usb3: unrecoverable error, controller halted usb3: blocking intrs 0x10 usb3: port reset timeout > Any ideas? I am not getting mail from the questions forum, yet, so I just thought that I would post here, just in case someone has a solution -- Respectfully, M.G.W. System: Asus M6N Intel Dothan 1.7 512MB RAM 40GB HD 10/100/1000 NIC Wireless b/g (not working yet) BSD-5.2.1 GCC-3.3.5/3.3.3(until I replace indigenous gcc) IFORT-for linux(Intell Fortran) gfortran python-2.3 Perl-5.6.1/5.8.5 Java-sdk-1.4.2_5 KDE-3.1.4 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
