Boot Problems

[depawl]

I recently installed Mandrake Linux 8.1 on a
dual boot system with Win 98. Everything seemed to go ok, but when Linux is booting up, it locks for about five minutes on: "Current State: Booting.... finding Module Discrepancies", then eventually it continues booting. Then on shutdown, it locks for about five minutes on "Current State Halt.... Stopping Portmap services."
Oh, and BTW, neither my sound card (sound blaster) nor my cable internet connection work. I've tried configuring them but no luck.
Thanks.

[angelus]

From experience it is trying to use your network connection -which you say is not working yet. I think this will go away if either you get it working or you have the machine think it is not on a network.

Hope this helps.

[depawl]

Well, it correctly recognizes my ethernet card as an SiS900 (onboard), but when I try
to connect to the internet it always fails.
I don't know enough about Linux yet to know what to do next.
Thanks.

[mdwatts]

Does ifconfig show eth0?

Are you using dhcp or static ip?

Can you ping anything? If you can, then it's just the matter of adding the isp's dns servers to /etc/resolv.conf.

[depawl]

I'm using the Mandrake control Center/Network & Internet/conection. It shows:
LAN Connection:
Interface: eth0
Protocol: dhcp
Driver: Sis900
State: down
Remember, a real Linux newbie. I don't know
how to use ifconfig, or how to ping anything.
Thanks.

[mdwatts]

Try

ifconfig eth0 up

and see what that gives you.

man ifconfig for more info.

Before doing this, make sure PnP OS is turned off in the bios. That could be causing both problems with your nic and soundcard.

[depawl]

ifconfig eth0 up returns the following:
bash: ifconfig: command not found

I was abe to get man ifconfig to work, but being the newbie I am I didn't really understand much.

Thanks.

[DMR]

The command WattsMD gave needs to be run as root; normal users don't have permission to enable/disable devices.

For your problems in general, a full listing of your hardware specs would be helpful.

[depawl]

Athlon XP 1600
256 M SDRAM
ECS K7S5A MB w/Sis900 nic onboard
Soundblaster PCI 16 bit Soundcard
ATI Rage 32M Video
Motorola Surfboard Cable Modem

Video works ok, sound works but has a low
frequency buzzing sound.
Linux recognizes the nic but can't connect
to internet.
Thanks.

[DMR]

The buzzing could be something being radiated into the sound card. Try moving it away from other cards, especially the vid card. Also check any wiring from/to the card and see if rerouting the wiring makes a difference (check the connections too). It could also be the speakers and/or their wiring; that's an easy one to isolate.

As for the NIC, get ready: you're about to learn some command line! :eek:

The GUI utilities can be unreliable, and often the only way to absolutely know what's going on is by getting down and dirty at the prompt. By the way- do you get the "Bringing up device eth0- Failed message at boot?

1)Log in as root, open a terminal window, and type "ifconfig -a" (omit the quotes). ifconfig gives you the InterFace CONFIGuration. The result should look something like this:# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:00:C0:41:F7:E4
BROADCAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:18 dropped:0 overruns:0 carrier:27
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x1000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:246 errors:0 dropped:0 overruns:0 frame:0
TX packets:246 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 eth0 is your NIC, and lo is the loopback device. At the very least, you should see lo's stats. What do you get on your system? This will determine if Linux really recognizes the NIC.

2. Next, type lsmod to LiSt your MODules. The Sis900 uses the (surprise) sis900.o module as its driver. Does it apear in the list that lsmod outputs?

3. If the above two steps check out, try to ping my ftp server:ping -c 10 209.133.27.161This will send 10 ping requests to the server. If it works, you'll get something similar to:64 bytes from 199.33.245.57: icmp_seq=0 ttl=64 time=0.8 ms
64 bytes from 209.133.27.161: icmp_seq=1 ttl=64 time=0.7 ms
64 bytes from 209.133.27.161: icmp_seq=2 ttl=64 time=0.6 ms
64 bytes from 209.133.27.161: icmp_seq=3 ttl=64 time=0.6 ms
.
.
.

If that works, you probably have a DNS issue. I don't think you'll get this far though, as your DNS servers are automatically assigned by DHCP, which brings us to this:

You need to see if the dhcp client daemon is running. Type the following:ps -ax |grep dhcpdhcpcd is the daemon's name; is it running?
Also, type "less /etc/sysconfig/network-scripts/ifcfg-eth0" to view your network configuration script. The file should contain the following lines:

DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
Does it?

[ 05 March 2002: Message edited by: DMR ]

[depawl]

I'm sure the buzzing sound is a configuration problem,when I open certain programs (like the Control Center, etc.) it starts, then stops when I close the program.
As for the nic stuff here's what I found.
1)The result I get is almost identical to yours, just some of the RX & TX packet #'s are different.

2) I get the following:
Size Used by
sis900 11968 0 (autorun)

3)When I try to ping your server I get
"connect: network is unreachable"

4) In response to ps -ax|grep dhcp I get:
2196 pts/3 s 0:00 grep dhcp

5) The network configuration script is the same as yours, except between BOOTPROTO and ONBOOT I have:
NETMASK = 255.255.255.0

I have no idea what this stuff means, hopefully you can tell me where to go from here.
Thanks.

[DMR]

Hm,

It seems like the dhcp process isn't running, but just to be more concise, try this alteration of the "ps" command I gave earlier and let me know what you get:ps -ax |grep dhcpcd"dhcpcd" is the exact name of the process, so I'm just being a little stricter here than I was the first time.

Are you sure that you should be using DHCP, or were you assigned a static address by your ISP? It's probably DHCP, but I just thought I'd ask.

I'm leaving work now, but I'll post a few more suggestions In an hour or so when I get home.

[depawl]

How would I know if I should be using DHCP or not?

[depawl]

DMR,
In reply to: ps -ax|grep dhcpcd
I get:
1903 pts/2 S 0:00 grep dhcpcd

Since this is similar to the last one, I assume this is not a good thing?
Any more ideas?
Thanks.
BTW, I found this article when searching the Mandrake stff: http://www.mandrakeuser.org/docs/connect/ccable.html

Since I have Roadrunner, I was wondering if this may be applicable to my problem?

[FyberOptyx]

in console type:
cat /etc/dhcpc/dhcpcd-eth0.info

this should give you your dynamically asigned info (if any)

[DMR]

You are correct, DHCP definitely isn't running.
Originally posted by depawl:
<STRONG>How would I know if I should be using DHCP or not?</STRONG>That is something your ISP has to tell you. If they gave you IP numbers to use for your IP, Netmask, DNS servers, etc., then you are not supposed to be using DHCP; you'll have to enter that info manually.

Try tying dhcpcd -r eth0 and tell us what you get.

The RoadRunner article at Mandrake might apply, but I've never used RR, so I can't help you there.
Hmm, I'm starting to get the feeling that we're missing something basic here, but can't put my finger on it.

[depawl]

DMR,
Well I finally got my internet connection working (woohoo). I got all of the info from winipcfg (dns, subnet, etc.), fiddled around with the settings in the Mandrake Control center for awhile and it finally connected.
Now my only problem is the lock on:
Finding module dependendies: on boot up,
and now it also locks on:
shutting down eth0:
when I shut down.
Thanks again for all your help.

[FyberOptyx]

Originally posted by depawl:
<STRONG>I got all of the info from winipcfg (dns, subnet, etc.), fiddled around with the settings in the Mandrake Control center for awhile and it finally connected.</STRONG>
If you have manually set up your ip instead of configuring dhcp, it will work for a while but when you reconnect you could be using an ip which has now been issued to someone else and your isp will not be happy.


ps.
If you are struggling with dhcp you could try the now prefered method and use pump

[ 07 March 2002: Message edited by: FyberOptyx ]

[DMR]

Originally posted by FyberOptyx:
<STRONG>If you have manually set up your ip instead of configuring dhcp, it will work for a while but when you reconnect you could be using an ip which has now been issued to someone else and your isp will not be happy.</STRONG>depawl, this is true. The info you got from winipcfg could be only your current settings obtained from your ISP via DHCP. If so, they'll probably change at some point, as FyberOptyx said. Check your Win network settings again- if they indicate that you should obtain your settings via DHCP, then that will certainly be the case. I'd have to reboot into Windows to verify the following (ugh; I try not to do that, so this comes from my memory):
Since you have a working, net-connected Win setup, you can find out whether or not you use DHCP by doing this (assuming Win95/98):

-Open the Network Control Panel.
-Under the Configuration tab, double-click on the TCP/IP Protocol entry.
-From the TCP/IP Properties window, click on the IP Address window.
-If the Obtain an IP Addres Automatically button is checked, you use DHCP, and your Linux box must as well.
-If the Specify an IP address button is checked, then the steps you've already taken concerning the manual entry of IP values on your Linux box are correct.

As far as the shutdown problem goes, see my response in this thread (http://www.linuxnewbie.org/cgi-bin/ubbcgi/ultimatebb.cgi?ubb=get_topic&f=4&t=015210), it might help.

Originally posted by FyberOptyx:
<STRONG>ps.
If you are struggling with dhcp you could try the now prefered method and use pump</STRONG>
Yeah, but if Mandy 8.1 doesn't use that by default, we'll be opening up a much bigger can 'o worms there...
;)

[ 08 March 2002: Message edited by: DMR ]

[bugfix]

I had a similar problem when my network card was sitting in my computer but not connected to anything. I think it just sat there hoping to find a friend on a network. I remedied it by sticking a terminator on the BNC jack - it seemed happy enough to talk to itself then.

[depawl]

DMR,
Yes, unfortunately my Windows Network settings indicate that I should be using DHCP, but it appears that,at least so far, Linux won't work that way, only with the static addresses entered. I've tried everything on this post (as well as some others) with no solution yet.
As far as the shutdown problem, i've already tried that USB fix, and while it does work, I would then not be able to use my USB printer, because the USB ports are disabled, right?
Also, the start up problem (locks on "finding module dependencies") is more annoying (I swear to God it locks for at least 5 minutes) , I usually go grab a beer and a sandwich while waiting, and I haven't been able to find any troubleshooting hints anywhere for this particular problem.
Once again, thanks loads for your help, I really appreciate it.

[depawl]

One more thing I just discovered about the lock problem on boot up. I turned off Aurora so I could see the text during boot up, and I get a green "OK" after "Finding module dependencies", and then it locks. So it appears the next entry "checking file systems" may be causing the problem?

[DMR]

Originally posted by depawl:
<STRONG>As far as the shutdown problem, i've already tried that USB fix, and while it does work, I would then not be able to use my USB printer, because the USB ports are disabled, right?</STRONG>No, it's just telling the system to use a different (and non-broken) USB module.
Originally posted by depawl:
<STRONG>Also, the start up problem (locks on "finding module dependencies") is more annoying (I swear to God it locks for at least 5 minutes) , I usually go grab a beer and a sandwich while waiting, and I haven't been able to find any troubleshooting hints anywhere for this particular problem.</STRONG>That might be the system stalling when it tries to obtain a DHCP lease. It will usually try for quite some time before it gives up.
To enable your machine to contact your ISP's DHCP server, you'll at least have to enter the hostname (and probably domian name) that they supplied into your network settings. You can try entering them in netconf; hopefully they'll take. You should restart after that and see what happens on startup.

It could be an issue with one of your filesystems, but when Linux detects filesystem errors at boot it usually warns you, and gives you a chance to manually run the filesystem checker (fsck).

[depawl]

DMR,
After I fixed the USB related shutdown problem, I now get an error on start up, saying it can't connect to the USB port (or something similar).
Also, I've entered the host and domain names
in the Mandrake Control center, but it still won't connect with DHCP. I was wondering if it could possibly be a problem with my onboard nic?
I have a LinkSys ethernet card that I was wondering if it would be worth trying?

[DMR]

Originally posted by depawl:
<STRONG>After I fixed the USB related shutdown problem, I now get an error on start up, saying it can't connect to the USB port (or something similar).</STRONG>I don't know what's happening there; your kernel should support uhci or usb-uhci. Perhaps you have more than one thing going on. Check the resources at linux-usb.org (http://www.linux-usb.org/) to see if they have anything enlightening to say.
<STRONG>Also, I've entered the host and domain names in the Mandrake Control center, but it still won't connect with DHCP. I was wondering if it could possibly be a problem with my onboard nic? I have a LinkSys ethernet card that I was wondering if it would be worth trying?</STRONG>It might be worth a try, but you said in an earlier post that you could connect if you typed in static addresses, so I don't think it's the NIC per se that's got problems. Still, it couldn't hurt...

As for your /etc/sysconfig/network-scripts/ifcfg-eth0 file, it's sounds OK. The "NETMASK=" entry should be ignored when using DHCP; you can delete the 255.255.255.0 part of it if you want.

Can you please post the contents of your /etc/sysconfig/network file?

[DMR]

By the way,

your profile says you're from "Upstate NY"; where exactly? Just curious...I used to live in and around Syracuse.

[depawl]

Actually, I'm from Adams Center, which is about an hour north on I81. I go through Syracuse quite a bit as my daughter goes to Ithaca College. Also, I'm an SU grad, way back in the seventies.
Anyways, here's my netconf file:
NETWORKING= yes
FORWARD_IPV4 = false
DHCP_HOSTNAME = dP3
HOSTNAME = dP3.twcny.rr.com
DOMAINNAME = twcny.rr.com
GATEWAY = 66.66.48.1

Thanks again for yor help.
BTW, how did you like California?

[DMR]

I believe the "DHCP_HOSTNAME=" entry belongs in /etc/sysconfig/network-scripts/ifcfg-eth0 instead of /etc/sysconfig/network. Also, you can try putting "GATEWAY_DEV=eth0" in /etc/sysconfig/network. DHCP is supposed to figure that out, but it won't hurt.

I remember passing through Adams Center a few times in my northern rambles, although I never spent any length of time there.
I've been living in Marin county, about 20 miles above San Fransisco, and I love it. The people are friendly and laid-back, the area is great (lots of state parkland, biking/hiking trails, beaches closeby), and the weather is just the right mix for me; we have more than one season (as opposed to Southern Cal), but I don't have to worry about digging my car out of a 5-foot snowdrift in the middle of February.
I do miss fall in the Adirondaks though, I used to camp up there quite a bit.

[ 15 March 2002: Message edited by: DMR ]

[slapNUT]

depawl
One more thing I just discovered about the lock problem on boot up. I turned off Aurora so I could see the text during boot up, and I get a green "OK" after "Finding module dependencies", and then it locks. So it appears the next entry "checking file systems" may be causing the problem?

It's possible you are doing a filesystem check on every boot.
Look in /etc/fstab and make sure any vfat partitions have 0 0 as the last entry.

Try tune2fs -l /dev/hda2 and look for
Maximum mount count: 20

[depawl]

DMR-
The only way I know how to change those files
is with the Mandrake File editor, and it won't let me change them.
slapNUT-
my vfat partitions (c & d, my Windows partitions) both have 0 0 after them, as do several other lines in that file.
tune2fs -l/dev/hda6 (hda6 is my first Linux partition) gives me an "invalid option --/" error.
tune2fs -C/dev/hda6 gives me a "bad mounts count" error.
Thanks.

[DMR]

Originally posted by depawl:
<STRONG>DMR-
The only way I know how to change those files
is with the Mandrake File editor, and it won't let me change them.</STRONG>You will have to be logged in as root to edit those files. If you're using KDE, you should find a few basic graphical, east to use text editing programs by clicking on the "K" button on the taskbar and going to Applications--&gt;Editors. Just make sure you pay attention to case, spacing, etc., as Linux is very finicky about syntax. And that brings us to:
<STRONG>slapNUT-
my vfat partitions (c & d, my Windows partitions) both have 0 0 after them, as do several other lines in that file.
tune2fs -l/dev/hda6 (hda6 is my first Linux partition) gives me an "invalid option --/" error.
tune2fs -C/dev/hda6 gives me a "bad mounts count" error.
Thanks.</STRONG>In the two tune2fs lines you posted above, you need to put a space between the options ("-l" in the first line, "-C in the second) and the device (/dev/hda6). Without the space to separate the two, the command thinks that the slashe is part of the option, not the device name.

[ 15 March 2002: Message edited by: DMR ]

[depawl]

I hate to appear how ignorant I am but Ican't figure out how to use any of those editors as root.
My Maximum mount count is 29. I that bad? I do believe it does a file system check on every boot. Shouldn't it?
Thanks.

[depawl]

Well, I finally got my internet connection working, I changed to a different nic, reconfigured and everything came up fine.
Unfortunately, the problem with hanging on "finding module dependencies" at boot still remains.
Any more ideas?
Thanks.

[DMR]

Yoiks! The Thread That Wouldn't Die... run for your lives!
:D

There are just too many things that could be causing the hang while finding dependancies. I'll take a look at my Linux boxen when I get home and see if I can find something enlightening there.
What happens when you try to resolve dependencies manually? Run "depmod -a" and see if it barfs any errors at you.

As for editing the network config files, I wouldn't wory about it if everything seems to be functioning now. I'm not sure why you can't get the text editors to work for you, but I guess you should stay away from vi or emacs for now...
:D

[ 26 March 2002: Message edited by: DMR ]

[depawl]

ok, ok, I promise this is my last post (at least for this thread). ;)
Anyways, in the Mandrake Control Center I found a tool that retrieves logs, and the next line after 'finding module dependencies' is ":loading module: bttv".
I believe bttv is the driver for my video capture card for my video cam (which I haven't been able to get to work in Linux). And according to the times listed this entry took about 6 minutes to complete (hence the hang).
Unfortunately, I don'y know how to get Linux to stop running this command. I tried disabling the device in the Mandrake Control Center, but it still hangs on boot.
Once and for all, thanks for all your help, especially DMR.