Hello, I installed suse 10.1 on my notebook... There is NIC Broadcom NetXtreme 5788 NIC is installed with tg3 module. But when I can't return IP adress from DHCP... When I put static IP, everything works good... thanks, miso ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
On Friday 12 May 2006 9:32 am, Michal Hlavac wrote:
Hello,
I installed suse 10.1 on my notebook... There is NIC Broadcom NetXtreme 5788
NIC is installed with tg3 module. But when I can't return IP adress from DHCP... When I put static IP, everything works good... Just one question, did you get a "waiting for mandatory devices" message?
--
Jerry Feldman
Jerry Feldman wrote / napísal(a):
On Friday 12 May 2006 9:32 am, Michal Hlavac wrote:
Hello,
I installed suse 10.1 on my notebook... There is NIC Broadcom NetXtreme 5788
NIC is installed with tg3 module. But when I can't return IP adress from DHCP... When I put static IP, everything works good... Just one question, did you get a "waiting for mandatory devices" message?
Hello Jerry, I change DHCP_DEBUG to yes... here is output from /var/log/messages thanks, miso May 15 01:55:32 hlavki dhcdbd: Started up. May 15 01:55:32 hlavki zmd: NetworkStatus (WARN): Network has been disconnected May 15 01:55:32 hlavki zmd: NetworkStatus (WARN): Network has been disconnected May 15 01:55:36 hlavki dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 May 15 01:55:39 hlavki dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 May 15 01:55:46 hlavki dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 May 15 01:55:58 hlavki dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 May 15 01:56:10 hlavki dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 May 15 01:56:18 hlavki dhclient: caught deadly SIGTERM May 15 01:56:18 hlavki dhclient: could not restore resolv.conf: No such file or directory May 15 01:56:29 hlavki kernel: martian source 255.255.255.255 from 10.23.224.1, on dev eth0 May 15 01:56:29 hlavki kernel: ll header: ff:ff:ff:ff:ff:ff:00:0f:f8:b6:40:54:08:00 May 15 01:56:30 hlavki zmd: ShutdownManager (WARN): Preparing to sleep... May 15 01:56:31 hlavki zmd: ShutdownManager (WARN): Going to sleep, waking up at 05/16/2006 01:36:30 May 15 01:56:31 hlavki kernel: martian source 255.255.255.255 from 10.23.224.1, on dev eth0 May 15 01:56:31 hlavki kernel: ll header: ff:ff:ff:ff:ff:ff:00:0f:f8:b6:40:54:08:00 May 15 01:56:31 hlavki SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. May 15 01:56:31 hlavki SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... May 15 01:56:31 hlavki kernel: martian source 255.255.255.255 from 10.23.224.1, on dev eth0 May 15 01:56:31 hlavki kernel: ll header: ff:ff:ff:ff:ff:ff:00:0f:f8:b6:40:54:08:00 May 15 01:56:31 hlavki SuSEfirewall2: batch committing... May 15 01:56:31 hlavki SuSEfirewall2: Firewall rules successfully set May 15 01:56:35 hlavki kernel: martian source 255.255.255.255 from 10.23.224.1, on dev eth0 May 15 01:56:35 hlavki kernel: ll header: ff:ff:ff:ff:ff:ff:00:0f:f8:b6:40:54:08:00 May 15 01:56:35 hlavki kernel: martian source 255.255.255.255 from 10.23.224.1, on dev eth0 May 15 01:56:35 hlavki kernel: ll header: ff:ff:ff:ff:ff:ff:00:0f:f8:b6:40:54:08:00 May 15 01:56:37 hlavki kernel: tg3: eth0: Link is down. May 15 01:56:37 hlavki SuSEfirewall2: Warning: ip6tables does not support state matching. Extended IPv6 support disabled. May 15 01:56:37 hlavki SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... May 15 01:56:38 hlavki SuSEfirewall2: Warning: no interface active May 15 01:56:38 hlavki SuSEfirewall2: batch committing... May 15 01:56:38 hlavki SuSEfirewall2: Firewall rules successfully set
Just one question, did you get a "waiting for mandatory devices" message? I change DHCP_DEBUG to yes... here is output from /var/log/messages I did some investigation on this over the weekend. First, the problem is NOT DHCP. "waiting for mandatory devices" comes from /etc/init.d/network In my case, this started to occur when I set up different profiles. I found when I booted into init 3, in all cases the network modules were not loaded. In my case for the wireless, ndiswrapper and for the wired, tg3. However, when I booted into KDE using my wireless profile, while I did receive the above message, and the wireless did not come up immediately under KDE, it did come up a few seconds later. The wired still showed it was down, so I clicked on the network button in
On Sunday 14 May 2006 11:55 am, Michal Hlavac wrote:
the tray, which brings up YaST. At that point the wired network came up.
My preliminary conclusion is that in the case of my laptop, the issue is
with the way I set up the profiles. I have not determined if this is a bug
or a cockpit error. It is a minor irritant that can be easily solved by a
number of things. I may switch to KNetworkManager in the future.
--
Jerry Feldman
/etc/init.d/network issues the message: "waiting for mandatory devices".
As I mentioned, in my case, I use profiles and when booting to use the
ethernet port, the network fails to come up, so I must do one of the
following:
Run YaST Network devices module. Just by running this, the network comes up.
or simply modprobe the tg3 driver.
One solution to this in my case, is to go into the sysconfig editor:
open system/kernel/MODULES_LOADED and add tg3.
I've tried a couple of other things, but none of these caused the driver to
load. the down side of this is that it forces the driver to load everytime
you boot the kernel.
--
Jerry Feldman
On Wed, 17 May 2006 10:40:31 -0400
Jerry Feldman
/etc/init.d/network issues the message: "waiting for mandatory devices". As I mentioned, in my case, I use profiles and when booting to use the ethernet port, the network fails to come up, so I must do one of the following: Run YaST Network devices module. Just by running this, the network comes up. or simply modprobe the tg3 driver.
One solution to this in my case, is to go into the sysconfig editor: open system/kernel/MODULES_LOADED and add tg3. As I mentioned, I did not like this approach. Upon further investigation, when I edit the wireless connection: Yast/Network Devices/ Edit the wireless, Advanced button/Hardware details Adding ndiswrapper under Module Name seems to correct the issue for both wireless profiles and the wired profiles. I like this better than setting MODULES_LOADED. -- Jerry Feldman
Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
participants (2)
-
Jerry Feldman
-
Michal Hlavac