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.free
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
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
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
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: U
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: U
6 matches
Mail list logo
