On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote:
Marcus,
Can you have a look at this?
Are there any news?
Thanks,
Rainer
--HPS
On Friday 14 January 2011 16:21:00 Rainer Hurling wrote:
After looking around I had been able to localise the cause for the
described messages, see below:
On Sunday 30 January 2011 14:57:37 Rainer Hurling wrote:
On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote:
Marcus,
Can you have a look at this?
Are there any news?
I don't have any news, except it is a HAL problem and it needs to be solved
there.
--HPS
On 30.01.2011 15:13 (UTC+1), Hans Petter Selasky wrote:
On Sunday 30 January 2011 14:57:37 Rainer Hurling wrote:
On 14.01.2011 20:10 (UTC+1), Hans Petter Selasky wrote:
Marcus,
Can you have a look at this?
Are there any news?
I don't have any news, except it is a HAL problem and it needs
On Sunday 30 January 2011 16:15:02 Rainer Hurling wrote:
Wouldn't it be useful to integrate the device info into the usb driver?
You can check if your kernel is compiled with options USB_VERBOSE. That
should bring some more verbosity based on sys/dev/usb/usbdevs.
--HPS
On 30.01.2011 16:22 (UTC+1), Hans Petter Selasky wrote:
On Sunday 30 January 2011 16:15:02 Rainer Hurling wrote:
Wouldn't it be useful to integrate the device info into the usb driver?
You can check if your kernel is compiled with options USB_VERBOSE. That
should bring some more verbosity
Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After
rebooting I get the following messages two times per second in an
endless run:
-
...
Jan 14 09:37:47 krabat kernel: (sg1:umass-sim0:0:0:0):
cam_periph_release_locked: release
After looking around I had been able to localise the cause for the
described messages, see below:
On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote:
Today I updated my 9.0-CURRENT system (amd64) to revision 199506: After
rebooting I get the following messages two times per second in an
endless
Marcus,
Can you have a look at this?
--HPS
On Friday 14 January 2011 16:21:00 Rainer Hurling wrote:
After looking around I had been able to localise the cause for the
described messages, see below:
On 14.01.2011 10:07 (UTC+1), Rainer Hurling wrote:
Today I updated my 9.0-CURRENT system