Re: Newbie bull brings own china shop.
If it is OK with you, I would rather not interleave my responses. I just
got over some serious eye problems and find that spending too much time
editing and working with the dim Debian text output on my daughter's
computer, makes my eyes complain a lot. I am trying to keep the eye
strain at a tolerable level. I hope you understand.
No output, means no output. It just processed the command and went to a
new line with the command prompt and blinking cursor. Absolutely nothing
happened. No error, no message, no nothing.
The output of "$ dpkg -l dhc* | grep ^ii" was: ii dhcp-client 2.0p15-11
I have been thinking that with regards to log files and the like, where
you would like me to post the contents, it might be a good idea to try
to get the USB floppy drive working. That way, I could copy files and
move them to my Win2k box. Likewise, if you wanted me to try using a
different /etc/network/interfaces file, you could post that to me, I
could copy it to the system and we could see if that helped. Or is this
idea more trouble than it is worth? I made sure to implement USB mass
storage support in the kernel before it was installed.
The output of "# tail /var/log/messages" was as follows:
sda: status=1, message=00, host=0, driver=08
sda: I/O error: dev 08:00, sector0
unable to read partition table
The output of "# tail /var/log/syslog" was as follows:
named: exiting (due to assertion failure)
kdm: server /usr/X11R6/bin/ X cannot be executed.
kdm: Server unexpectedly dies. Server for display : 0 cannot be
started, session disabled.
While not all of the output, the above is what looked to me to be the
most serious messages. There was nothing with "eth0" or "dhcp" or
The output of "$ /sbin/ifconfig eth0" was the same as the last time:
Link encap: Ethernet HWaddr 00:30:67:06:4F:86
BROADCAST MULTICAST MTU:1500 Metric 1
and then follows RX and TX packet values, all of which are zeroes, as
they were last time as well.
The output of # pump (which installed like a dream) was:
eth0: Media Link off
eth0: Media Link off
The result of a "winipcfg" command on one of the Win 98SE machines on my
Wan/LAN provided the following result:
Windows 98 IP Configuration
0 Ethernet adapter :
IP Address. . . . . . . . . : 0.0.0.0
Subnet Mask . . . . . . . . : 0.0.0.0
Default Gateway . . . . . . :
1 Ethernet adapter :
IP Address. . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
I haven't been able to find out how "ipconfig" output, which is used in
Win2k, can be sent to a text file or copied from the command prompt.
However, I can tell you that my Win2k box's IP address is 192.168.1.101.
I hope the above helps.
sean finney wrote:
On Fri, Feb 28, 2003 at 04:19:38PM +0700, Brian Durant wrote:
OK, I didn't get the difference between "#" and "$". Tried again, in
root (#), same result. Added the two lines in /etc/network/interfaces
restarted the network and tried again. Same result - nada - zip -zilch
interfaces didn't exist? strange...
response. No response with /sbin/ifconfig either. Thanks for all your
what do you mean by "no response" was there output, but just not
the address? was there an error?
time so far. Is there any place that we can go from here? I did a sort
of default full install with tasksel and dselect. Got a lot of stuff I
didn't want, but even the stuff that I do want will not do any good if I
don't get this @£5#+* eth0 working.
right. okay, at this point a few things posted would be very helpful. i
know it's hard to get it to use without a network, but the following
might shed some light:
$ dpkg -l dhc* | grep ^ii
(this will tell use what kind of dhcp client you have installed, hopefully)
after you do /etc/init.d/networking restart, show us anything that looks
# tail /var/log/messages /var/log/syslog
(those two files are log files for various parts of the system)
$ /sbin/ifconfig eth0
namely, for the above, we're interested in the first few lines.
also, what are you running that's giving out the dhcp addresses?
do you have anyway of looking at it's logs?
okay, and if none of this works, try this:
# apt-get --reinstall install netbase ifupdown pump
(pump is a dhcp client that i think is a little less picky than
the dhclient -- i don't really like it all that much, but it works)
after doing this, try just typing "pump" in a root prompt and see if
also, everything else failing, istr someone said something about the
sis900 driver maybe not supporting dhcp, so we can try setting it
manually. so when you have a chance, go to another machine and find
out its ip address, netmask, and dns information. i know on the older
windows machines this was by running "winipcfg", but i don't know off
the top of my head what does it in XP these days.
ps - since there are a lot of instructions and questions in here, when
you reply, please interleave your responses with the text of this mail,
like what's done at the top of this mail, to avoid as much confusion