George Langford on Mon, 29 Apr 2002 05:00:13 +0200


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

[PLUG] Re: Newbie's first question[s]


Hello fellow PLUGgers !

Still struggling ...

Fred Ollinger wrote:

> I'm posting back to the list so you get the best advice.

OK; so will I.

... snippage ...

>> Regarding the ftp client ... doesn't seem to matter; one was 
>> Terminal's ftp; another two came from Xwindow's programs.  All 
>> will access my amenex.com server, but not any www site.

> This is strange to me. Don't know why it would be like this.

Most of what I know about ftp (not much) seems to work.   I
can ping any IP address and get a reply.  I could actually ftp
to my web server, if I dared at this stage.  Of course, I did
it all the time with CuteFTP on the old W95 computer that is
about to be disemboweled to transplant its data to the Linux
machine.  The Linux machine's modem appears to be working
fine.  It's the browsers that won't communicate.

> Contents of /etc/resolv.conf:

>       domain voicenet.com #kppp temp entry
>       # search localdomain #entry disabled by kppp
>       nameserver 192.168.2.1
>       nameserver 24.130.1.32
>       nameserver 24.130.4.8
>       nameserver 209.71.158.2 #kppp temp entry
>       nameserver 207.103.206.67 #kppp temp entry

> Did you try pinging those sites?
These ?; not yet; all the others that I tried replied OK.

>> I don't like the first one: nameserver 192.168.2.1 as it has local
>> address. I suggest putting a # in front to comment it out and retry
>> pinging google.

All attempts to contact a named server have failed.  I'll try this
suggestion during my first session in the AM.  Gotta start doing
useful work; four full days invested in this startup ...

>> Should I be replying directly; or is the protocol to send my replies 
>> to The List so that others can watch this develop ?  I'll summarize 
>> the solution when we're done, of course.  I sometimes see that done 
>> on other lists ...

> I suggest sending it back to the list. We need more tech discussions 
> here. :) Also, I'm not perfect, I might be missing something.

> Do a 'route' and post that as well.

Whazzat ?

> This looks like a nameserver problem. Can you put the ip address
> into the www browser and see it? Can you ping an ip address?

I get a "connection refusal" reply when I enter:

	http://207.103.140.16 

in Netscape; or the like (fictitious IP address here).  Actually,
this seems to be a major breakthrough, akin to the first time I
got slapped after all the others simply ignored me.

> Here's google's: 216.239.51.101

Hmmm.  I got 216.239.32.10 with NSLookup.  This result indicates
that I cannot expect to surf the Net with IP addresses; they change
dynamically.

> If you can use ip addresses, then it's a nameserver. Route should 
> be ok if you can use ftp. Can you ftp everywhere?

Even across the Earthlink-Voicenet path to Voicenet's ftp server.

> Try to ftp: ftp.gnu.org

Nope; no luck.

> if this doesn't work then try:

> 199.232.41.9 [which is the ip address]

Memory says that this worked OK.
......................................................
Enough about my browser-less Linux PC ...
......................................................

Regarding the CDROM-lessness of the Linux PC:

>> Oops.  This morning the CD-R drive wouldn't mount, so I looked
>> into the matter and discovered that during an intervening reboot
>> the BIOS had switched back to "NONE" for the Primary Slave
>> IDE drive.   So I changed it again to AUTO and got the BIOS to

> Did you reboot the machine overnight? 

Several times; got into that habit from running W95 and
W98 day after day.  Few problems take less than 25 reboots
before going away.

> Not being wise here, but many of us leave our machines on all 
> the time.

I'm tempted; but when it's froze, what's a fella to do ?

> If the bios "forgot" what mode it was in, I suggest sending it 
> back as it's a hw problem. I don't see the point in trying to 
> get back hw to work esp if you just bought it. Big waste of 
> time, and if it works, it probably won't work as long as non-
> faulty hw.

We must have scared the BIOS.  It's found the CDWriter several
times in a row now.

> Alas, Linux cannot reliably detect the CDROM drive, except when
> I place the PC mfgr's (Boot PC) CDROM setup disk in the drive and
> reboot.  It will then open the CDROM disk, and it will even ...

> Not familiar w/ this cd. 

Came with the Book PC; nothing special except that it's for
setting up the machine in DOS/Windows.  So I don't expect
it'll be of much use.  Just another disk for now.

> How does it work? 

Forget about the Book PC's CD; the system came with two Linux
distribution disks (CD's) that the machine will boot from; but
then it's into the Linux Installation menu, and so I got out
of there in a hurry.  And it will still boot from them.

> Does it boot linux after you put cd in? 

I don't let it ...

> Is linux coming from cd or hd?

>From the hard drive; 40GB worth ...

> open my own burner's CD-R disk, but the mount command fails
> and I cannot keep that icon on the bottom toolbar to work; it

> What desktop (just curious).

I'm so confused right now I don't know.  There's one group of
programs labeled KDE; and another, just Programs.  Some of
each seem useful, but not [yet] all of one or the other.  There's
programs scattered all over the place like a weekend handyman's
tools after a flood.  As if Windows were any better.

>> either gives a failure command or crashes altogether.  The last
>> couple of reboots the BIOS settings have remained stable and
>> autodetect the CDWriter, but Linux can no longer find the
>> CDWriter, either when I right-click to find the mounted floppy

> You probably said this, but is this ide?

Yup.  Both the hard drive and the CDWriter.  No SCSI anywhere.

>> (which seems to work OK, except that the file manager no longer
>> detects a file which I saved onto that floppy earlier today and
>> which I could read with a W98 PC) or when I invoke Hardware

> Did you try:

> mount /mnt/floppy
> ls /mnt/floppy

This works; and I can see the contents of the floppy from the
Shell screen.  But not from Nautilus's Tree screen.

> from cli? I'm starting to suspect a faulty gui. 

What's cli ?  

> What program did you use to view floppy from gui?

Shell.  Among the "Programs" file group.

>> Browser.  I'm getting the notion that there's a hardware
>> interference of some sort or that the Linux installation of the
>> CDROM drive has gotten corrupted.  Any help would be appreciated.

> I have never had trouble using a cd-rom (or rw), ide, w/ linux. 
> Ever. Even if drive is mechanically completely hosed, I still 
> get some output from the danged thing.

Reason enough to run, not walk, away from the MS environment.
I have never gotten a CD-R/W drive to work except momentarily,
a few days at a time, in a MS machine.  At one point, I could 
start a multisession CD-R disk in the W95 machine and then add 
to it on the W98 machine, using two different burners but the 
same (nero) S/W. No more; both installations of nero failed and 
nero doesn't answer my E-mails.  So now it's on to Linux.  

> I personally don't like autodetect in bios. I like to tell 
> my machine what to do, but this could just be nuttiness on my 
> part. However, can you just select cd-rom in bios? I'm guessing 
> that this worked worse than autodetect mode.

Except that I haven't found much in the way of parameters for
the Samsung SW212 drive.  Evvybiddy uses auto-detect, so they're
not anywhere I can find them.

> You can snoop in /proc to see what linux really thinks of all
> this.  For ide, so:
> 	cd /proc/ide/
> and look around. In the hdx dirs, you can find a wealth of data. 
> Esp interesting is the /proc/ide/hdc/drivers, yours may be 
> different.

All's I found were: hda, ide0, and sis

> If you use scsi, you can get same thrill from:
> 	cd /proc/scsi

Not applicable.  The CDWriter's a "pure" IDE drive.

> Best stop here is
> 	cat /proc/scsi/scsi

Didn't try this.

> This will tell you if linux ever saw that recalcitrant 
> cdrom drive.

At one point it did - and I could look at a CD-R disk that
I burned with JPG's and HTML files; worked fine.

> Also, you can do the good old:
> 	dmesg
> and grep for cd and other things.

Not much came of my feeble attempts to poke around with these.

> Please let us know back on the list what's up. There are more 
> than a few pluggers who want to get deep into hardware trouble
> shooting right away. :)Thanks for posting. Fred

You're welcome !  This is very educational.

When I try the command:

	mount /mnt/cdrom

In Shell, it comes back with:

	mount: can't find /mnt/cdrom in /etc/fstab or /etc/mtab

Not a good sign ?  Yet, at one stage, it did successfully mount
several CD's, one at a time of course. 

Automount has never worked.  Although if I right-click in the
blank part of the main screen, under drives, it usually shows
floppy.  Once or twice, several dozen reboots ago, it also
listed cdrom among the choices there.  No longer; and even
when the BIOS autodetects the CDWriter, Linux fails to mount
it, automatically or even manually. Hasn't gone "POP" recently,
though.  Still no acrid smells, either.  No visible magic smoke.

A DOS installation disk for the CDWriter came with the system.
Is there anything useful I can do with that ?  The installation
instructions for the CDWriter that came with the system just
say that Windows will Autodetect it.  No help there; no data.

Best regards,
George Langford
amenex@amenex.com
http://www.amenex.com/
http://www.georgesbasement.com/

______________________________________________________________________
Philadelphia Linux Users Group       -      http://www.phillylinux.org
Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce
General Discussion  -  http://lists.phillylinux.org/mail/listinfo/plug