On Fri, 31 Aug 2001 08:55:13 -0400 (EDT), Steve <[EMAIL PROTECTED]> wrote:
> On Wed, 29 Aug 2001, Clarence Verge wrote:
>> My Linux X problems were fixed by installing the SVGA rpm.
>> This turned out to be extremely easy.
> Glad to hear it. :-)
>> I elected to use a slightly
>> modified form of the instructions supplied by Steve, so this might
>> be of some use to someone.
>> In Midnight Commander I went to /mnt/CDROM (which I had automounted
>> in fstab) and was lucky enough to have someone around who suggested
>> I look under Redhat for RPMS and there they were. I wouldn't have
>> guessed that myself.
> Er... Step number 3 told you that.
At the time I didn't have a hardcopy of your post on hand.
Now I do. ;-)
>> Trolled down the list and found all the video
>> drivers (is that what they are called in Linux ?) and there was
>> XF86_SVGA something and there was only one so I felt mistakes were
>> unlikely at this point. <G>
>> Here is the easy bit: Hightlight that RPM
>> Hit enter.
>> Something happens. (I dunno - this is Linux) <g>
>> The display panel changes and now we see some new stuff - the most
>> important of which is the word *INSTALL in green.
>> So I slide down to that and hit it. (enter) Could it hurt ?
>> Text screen shows hash marks "#" as Steve said it would and it's done !
>> I exited MC and typed Xconfigurator and this time it ran correctly and
>> I was able to immediately startx. :))
> The reasons I didn't walk you through this way are
Not necessary to supply reasons. Your method was/is the best.
We really need to see that detail in the message. <G>
> 1) not everyone has mc installed, and
> 2) if there is an error this way, say you're missing
> a dependency, mc doesn't show it to you. You have to
> exit mc to see any error messages. If you've had a
> long session and had errors pertaining to many different
> operations, the ones you're really interested in have
> probably already scrolled off the top of the screen.
> mc is great for a lot of things, but I don't really
> recommend it for installing rpms when 'rpm -ivh' is
> so easy.
And difficult to remember. <g> Maybe that will change.
In DOS when I must use applications with hard to remember switches
or options that I might use every time anyway, I make a batch file
to do my remembering for me.
How do you make (and launch) batch files in Linux ?
Are they scripts ? If they are, please don't assume I know how to
make them or where to put them.<G>
>> Next problem. <G>
>> I read the Net3Howto in hopes of getting my box on line.
> I see Steven has already given a pretty good answer,
> (while I was away down south to NYC) so I'll add any
> ..02 later on in the "thread."
dmesg | grep eth0 comes up blank.
insmod <module for my card> ???
How the heck I might know the module name for my card is beyond me.
I browsed many files and finally found a list of possible modules
that could be installed (I think I found it in sysinit or initsys)
about 4 hours ago, and I can't type this and read a Linux screen
at the same time. (or chew gum either)
At any rate, I found a few Dlink numbers in there but they didn't
seem to have mine so I went to the Dlink disk and glory be -
a Linux subdir.
Arrrggghhh.
The damn thing is a SOURCE file.
This must be a conspiracy of some sort. Three years left to live
and I spend time compiling code that would have been smaller, more
friendly, and more error free if it was shipped in binary ?
Please don't tell me how nice it is that I can change the source -
is it possible that someone could produce the binary for me from the
source and makefile ?
I loaded a lot of make and compiler crap and I'm getting nowhere fast.
I didn't want to have anything to do with compiling "C" code before I
started and I'm not any more excited about it now that I've wasted an
hour trying to. <g>
Thanks to anyone that responds.:)
- Clarence Verge.
-- Using Arachne 1.66 on DSL.
