SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0003524: Endless looping of usbhid messages as reported - MantisBT
MantisBT - Endian Firewall
View Issue Details
0003524Endian FirewallInstallationpublic2011-03-08 03:512011-03-25 15:27
0003524: Endless looping of usbhid messages as reported
Installation of efw 2.4/2.4.1 DL380G4: Unsuccessful as the aforementioned problem persisted.

Endless looping of usbhid messages as reported above:

FATAL: Module usbhid not found
Running command: /bin/mount -t usbfs none /proc/bus/usb
... failed: device or resource busy
running command /bin/
scanning source media

No tags attached.
Issue History
2011-03-08 03:51narikkiNew Issue
2011-03-08 07:22lorenzo-endianNote Added: 0005867
2011-03-08 07:22lorenzo-endianAssigned To => lorenzo-endian
2011-03-08 07:22lorenzo-endianStatusnew => feedback
2011-03-20 12:29bacanolNote Added: 0005995
2011-03-25 10:17lorenzo-endianNote Added: 0006012
2011-03-25 15:27bacanolNote Added: 0006016

2011-03-08 07:22   
Hi narikki,

are you using any hardware/software raid? in that case, can you try to disable it and run the installer again?

If you have 2 hdd, the installer creates a software raid (RAID1) during the installation.

Thanks a lot

2011-03-20 12:29   
Hi all!

I have got the same issue with 2.4 and 2.4.1 on Fujitsu Siemens Futro S400. I did a bit of research and it seems to me that this is due a missing driver. If I proceed I will try to give additional feedback on this.

Best regards,

2011-03-25 10:17   
Hi all,

the driver could be a feasible source of this problem :/

I will wait for a feedback from you!

Thanks in advance!

2011-03-25 15:27   
Hi Lorenzo,

I did a little bit of investigation and I found that an installation from internal CDROM with the nousb boot option is working. I think there might be a missing module for the kernel. After installation on the target drive the system is booting ok, without any errors. So there must be a difference in the install environment and the installed environment.

I hope this helps.

Best regards,