Arne Posted December 2, 2005 Report Share Posted December 2, 2005 Hello Guys, Running 2006.0 I sometimes on boot have a problem with with initializing the firewire controller. Verbose boot says "initializing fireware controller ohci1394" and the boot process stop for approc. 2 minutes. Other times it's complete fast. It seems this is random happening. It shows up in LAN as eth1 which I do not use. I have tried to give it some unused IP address but it still occur at random. How can I remedy this completely????? Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted December 2, 2005 Report Share Posted December 2, 2005 Hi Arne, Just checking, although I'm sure you've probably done this. Have you applied all updates to the system? I usually apply all Normal/System/Bug Fixes, and all working OK for me on 2006. Although I'm not using Firewire, but worth a shot if you've not tried it. Other than that, can you check your /var/log/boot.log to see if it gives any more light as to why it's taking so long? If not maybe one of the other log files /var/log/syslog or messages perhaps. These are quite big, and might need a bit of hunting through to find an error relating to it. Also, check /var/log/dmesg too for some info that might relate to it. That's all I can think of at the min! Quote Link to comment Share on other sites More sharing options...
Arne Posted December 2, 2005 Author Report Share Posted December 2, 2005 Hello Ian, Thank's for reply. Everything updatet a week ago. I will dig into the log's and see what I can find and report back. Thank's Quote Link to comment Share on other sites More sharing options...
Gul Dukat Posted December 2, 2005 Report Share Posted December 2, 2005 Don't now if you're making use of the Firewire-controller. But if not, you can probable disable your Firewire-controller in your Bios. Only if it's an onboard-controller, that is. Quote Link to comment Share on other sites More sharing options...
aRTee Posted December 2, 2005 Report Share Posted December 2, 2005 You can also tell the system not to start the controller at boot, AFAIK, by modifying the file /etc/sysconfig/network-scripts/ifcfg-eth1 which in my case (incidentally for the firewire on my audigy2 soundcard) contains this: DEVICE=eth1BOOTPROTO=dhcp ONBOOT=yes Just change the 'yes' into 'no'. Quote Link to comment Share on other sites More sharing options...
Arne Posted December 4, 2005 Author Report Share Posted December 4, 2005 Hello guys, I use my PCI firewire card for my scanner. The scanner runs better on firewire than USB. So aRTee, if I stop booting the controller eth1 will the scanner connection still work???? Quote Link to comment Share on other sites More sharing options...
Arne Posted December 4, 2005 Author Report Share Posted December 4, 2005 Hello again, My digging into /va/log/syslog reveal some strange competition between Samba and something else "fighting" which one should the main browser for my LAN. When I installed 2006 the last time I did not tick the "server" and then later I downloaded and installed several packages which may compete. This maybe the reason ...or. Some extracts show this: (please excuse the lenght) Dec 4 10:26:39 linuxhost nmbd[6572]: add_domain_logon_names:Dec 4 10:26:39 linuxhost nmbd[6572]: Attempting to become logon server for workgroup MDKGROUP on subnet 192.168.1.1 Dec 4 10:26:39 linuxhost nmbd[6572]: [2005/12/04 10:26:39, 0] nmbd/nmbd_logonnames.c:add_logon_names(163) Dec 4 10:26:39 linuxhost nmbd[6572]: add_domain_logon_names: Dec 4 10:26:39 linuxhost nmbd[6572]: Attempting to become logon server for workgroup MDKGROUP on subnet 192.168.1.2 Dec 4 10:26:39 linuxhost nmbd[6572]: [2005/12/04 10:26:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282) Dec 4 10:26:39 linuxhost nmbd[6572]: become_domain_master_browser_bcast: Dec 4 10:26:39 linuxhost nmbd[6572]: Attempting to become domain master browser on workgroup MDKGROUP on subnet 192.168.1.1 Dec 4 10:26:39 linuxhost nmbd[6572]: [2005/12/04 10:26:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) Dec 4 10:26:39 linuxhost nmbd[6572]: become_domain_master_browser_bcast: querying subnet 192.168.1.1 for domain master browser on workgroup MDKGROUP Dec 4 10:26:39 linuxhost nmbd[6572]: [2005/12/04 10:26:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(282) Dec 4 10:26:39 linuxhost nmbd[6572]: become_domain_master_browser_bcast: Dec 4 10:26:39 linuxhost nmbd[6572]: Attempting to become domain master browser on workgroup MDKGROUP on subnet 192.168.1.2 Dec 4 10:26:39 linuxhost nmbd[6572]: [2005/12/04 10:26:39, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bcast(295) Dec 4 10:26:39 linuxhost nmbd[6572]: become_domain_master_browser_bcast: querying subnet 192.168.1.2 for domain master browser on workgroup MDKGROUP ------------------------------------------------------------break in listing Dec 4 10:26:43 linuxhost nmbd[6572]: [2005/12/04 10:26:43, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) Dec 4 10:26:43 linuxhost nmbd[6572]: become_logon_server_success: Samba is now a logon server for workgroup MDKGROUP on subnet 192.168.1.1 Dec 4 10:26:43 linuxhost nmbd[6572]: [2005/12/04 10:26:43, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(124) Dec 4 10:26:43 linuxhost nmbd[6572]: become_logon_server_success: Samba is now a logon server for workgroup MDKGROUP on subnet 192.168.1.2 Dec 4 10:26:47 linuxhost nmbd[6572]: [2005/12/04 10:26:47, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) Dec 4 10:26:47 linuxhost nmbd[6572]: ***** Dec 4 10:26:47 linuxhost nmbd[6572]: Dec 4 10:26:47 linuxhost nmbd[6572]: Samba server LINUXHOST is now a domain master browser for workgroup MDKGROUP on subnet 192.168.1.1 Dec 4 10:26:47 linuxhost nmbd[6572]: Dec 4 10:26:47 linuxhost nmbd[6572]: ***** Dec 4 10:26:47 linuxhost nmbd[6572]: [2005/12/04 10:26:47, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(113) Dec 4 10:26:47 linuxhost nmbd[6572]: ***** Dec 4 10:26:47 linuxhost nmbd[6572]: Dec 4 10:26:47 linuxhost nmbd[6572]: Samba server LINUXHOST is now a domain master browser for workgroup MDKGROUP on subnet 192.168.1.2 Dec 4 10:26:47 linuxhost nmbd[6572]: Dec 4 10:26:47 linuxhost nmbd[6572]: ***** ------------------------------------------------------------------break in listing Dec 4 10:27:02 linuxhost nmbd[6572]: [2005/12/04 10:27:02, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396) Dec 4 10:27:02 linuxhost nmbd[6572]: ***** Dec 4 10:27:02 linuxhost nmbd[6572]: Dec 4 10:27:02 linuxhost nmbd[6572]: Samba name server LINUXHOST is now a local master browser for workgroup MDKGROUP on subnet 192.168.1.1 Dec 4 10:27:02 linuxhost nmbd[6572]: Dec 4 10:27:02 linuxhost nmbd[6572]: ***** 192.168.1.1 = linux on dual boot PC which should act as server for 192.168.1.4 = notebook with mdv 10.1. Both with static protocol 192.168.1.2 = I have given the eth1 this name in order to not interfere with eth0, my LAN Can any one shed light on this and how to remedy it???????? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.