Re: Problem with X
> Date: Thu, 27 Jul 2000 03:15:10 -0700 > From: Torrey Peacock <[EMAIL PROTECTED]> > Subject: Re: Problem with X > To: James Polson <[EMAIL PROTECTED]>, debian-user@lists.debian.org > James, > I have a Rage 128 Pro card (XPert2000 Pro) and have got it working with > XFree86 version 3.3.6. The tip on David St. Clair's page was crucial, of > adding "ChipId 0x5246" to the "Device" section of XF86Config. With that > modification, the r128 driver will work. > > How did you manage to install 4.01? The Debian package is not available > yet, and I could not get the source to compile - too many broken > dependencies. > I simply downloaded all the files from the XFree86 website, then ran Xinstall.sh and answered all the questions. Am I being naive about this? Is there anything else I should have done? James
Problem with X
Hi, I'm still trying to setup X windows and make it compatible with my ATI Rage 128 Pro video card. This card is not supported with the XFree86 software supplied with slink Debian linux. Fortunately, I found help on the web (David St. Clair at http://www4.ncsu.edu/~distclai/rage128-howto.html) who wrote a configuation tool to setup XF86Config. The problem is that it only works with XFree86 4.x - so I installed the 4.0.1 (?) version (the most recent available). So I constructed a proper(?) XF86Config and ran startx. The result: it looks okay - but everything is frozen. The system locks. Hmmm. Now, some of you may have read my earlier cry for help when my system would freeze on booting - just when it came to run xfs. It gave the following complaint message: Starting X font server: xfsFontCacheInitialize: hi=1045876, lo=786432, bal=70 just before it froze. To get around the problem of the boot freeze, I disabled xfs, and was able to get into the system as before. I assume that the problem with xfs may be related to my problem with the system locking when I run startx. Finally, for what it's worth, when I log into the system with xfs disabled, the following message is displayed: Checking for valid XFree86 server configuration...error in configuation file Any help with this problem would be appreciated! Thanks, James Polson
HELP: system locks during boot
Hi, I have a big problem. I tried to use XF86Setup to configure my system for X-windows. Unfortunately, not only did it not work, but now the system doesn't boot properly. The last message displayed is: Starting X font sever: xfs and then the system locks. Obviously a result of what I tried to do before. I tried to log on remotely to kill the xfs process (?) but couldn't log on. Help! James Polson
XF86Setup with ATI Rage Pro 128
Hi, I'm having trouble using XF86Setup to configure my system - namely because the graphics card is not included in the card list. I'm using an older version of XF86Setup, I guess, but I was wondering if there was a relatively easy way of creating an XF86Config file without having to install the newer version of the setup program. Thanks, James Polson
Another ethernet configuration problem
Hi, After having solved one problem with configuring an ethernet card on one computer (thanks to the response to an earlier email like this one!), I now have a problem with a different ethernet card on another computer! The info I have on the card is as follows: 3Com905C Etherlink 10/100 PCI (-TX) Also, I've installed Debian 2.1. >From what I can tell, the problem is that I'm lacking the proper driver in the directory /lib/modules/2.0.36/net (?). There is a module called 3c59x.o (?) which I thought should work, but which doesn't seems to. I would appreciate any help on this matter very much! After searching on the web, I understand that a 3c90x driver does exist, so I suspect, it's simply a matter of downloading the driver, putting it in this directory, and then loading it up, etc. Problem (trivial, I'm sure): how do I download the driver when I don't yet have a connection to the internet? I could download it when I'm using Windows 98, but then how do I then get it from one disk partition to the other? Anyway, I think you can see what I'm getting at. Again, any help would be appreciated! Thanks, James Polson
Re: network/ethernet card configuration problem?
Hi,
Many thanks again to the several people who offered their advice
to help me solve my configuation problem with my
ethernet card (Simon Hales, John (?), Bolan Meek, Esko Lehtonen,
and John Pearson)! The method described below (by John Pearson)
was the first that I tried, and it worked perfectly. (Note: the card
did turn out to be a PnP card).
James Polson
> Date: Wed, 19 Jul 2000 10:47:35 +0930
> From: John Pearson <[EMAIL PROTECTED]>
> Subject: Re: network/ethernet card configuration problem?
> To:debian-user@lists.debian.org
> On Tue, Jul 18, 2000 at 12:00:46PM -0300, James Polson wrote
> > Hi,
> >
> > Thanks to all who answered my call for help! This message here is in
> > response to the one from John Pearson.
> >
> >
> > > Date: Tue, 18 Jul 2000 13:15:56 +0930
> > > From: John Pearson <[EMAIL PROTECTED]>
> > > Subject: Re: network/ethernet card configuration problem?
> > > To:debian-user@lists.debian.org
> >
> >
> > > The "correct" way to proceed depends on which version of Debian you are
> > > using (slink (2.1), potato (2.2), etc.); which is it?
> >
> > It is slink (2.1)
> >
> > >
> > > You can check if things are going to work out for you by trying the
> > > following commands as root:
> > >
> > > # lsmod
> > >
> > > This lists the driver modules currently loaded.
> > > If the "ne" or "ne2k-pci"driver is loaded then you
> > > should see it listed in the output to this command,
> > > like so:
> > > ne2k-pci4136 1
> >
> > It was not loaded!
> >
> > >
> > > Assuming it isn't loaded, try loading it by hand.
> > > If your NIC is a PCI card you should use the ne2k-pci
> > > driver, like so:
> > > # modprobe ne2k-pci
> > >
> > > PCI cards shouldn't need any extra parameters.
> > >
> > > If it's an ISA card you will need to use the ne module,
> > > and will need to pass at least the IO port as a parameter,
> > > with a command like this:
> > > # modprobe ne io=0x300 irq=10
> > >
> > > You can skip the IRQ parameter, but if you know what it is
> > > then it makes things a little more bullet-proof. If you don't
> > > know what IO address the card is using, the Windows Device Manager
> > > (under System in Control Panels) will probably tell you.
> > >
> > > If the card is a bona-fide ISA/PNP card (as opposed to a
> > > traditional ISA card) then this will fail after a cold boot, and
> > > you will need to set the card up using isapnp before you can
> > > use it under Linux.
> > >
> >
> > The full name of the card is D-Link DE220 ISA PnP -- is this
> > a bona-fide ISA/PNP adaptor?
> >
> > I tried using the command
> >
> > # modprobe ne io=0x300 irq=03(these are the proper settings)
> >
> > and it didn't complain. However, I infer from your remarks that
> > I will have to use 'isapnp'. I guess that this means I will have to
> > edit (properly!) the /etc/isapnp.conf file. I looked at the website
> >
> > http://www.roestock.demon.co.uk/isapnptools
> >
> > and it looks like I will need a line in the file like:
> >
> > (CONFIGURE EDI0119/236861364 ( ... etc.
> >
> > The code 'EDI0119' identifies the ethernet card -- but how can
> > I find what code to use for my card?
> >
> > Please let me know if there is anything else I have to know about
> > 'isapnp'.
> >
>
> OK.
>
> Firstly, some ISA/PnP cards have a "Software Configuration"
> mode that allows you to specify a configuration using their
> setup disk, rather than doing PnP configuration at run time.
> Ignore all of the ISA/PNP stuff below if your card has that
> option and you're using it; skip to the line
> "(If it isn't a PNP card, start here)" in that case.
>
> isapnp is the utility you use to set up ISA/PNP cards; there is a
> companion utility, pnpdump, that will interrogate your ISA/PNP cards
> for you.
>
> First, make asure that the card isn't in use by running
> # lsmod
>
> to list the currently loaded modules, and use
> # rmmod ne
> # rmmod 8390
>
> to unload the ne and 8390 modules if necessary ("8390" is a
> low-level module that is used by the "ne" module to talk to
> ne-compatible NICs). Chang
Re: network/ethernet card configuration problem?
Hi, Thanks to all who answered my call for help! This message here is in response to the one from John Pearson. > Date: Tue, 18 Jul 2000 13:15:56 +0930 > From: John Pearson <[EMAIL PROTECTED]> > Subject: Re: network/ethernet card configuration problem? > To:debian-user@lists.debian.org > The "correct" way to proceed depends on which version of Debian you are > using (slink (2.1), potato (2.2), etc.); which is it? It is slink (2.1) > > You can check if things are going to work out for you by trying the > following commands as root: > > # lsmod > > This lists the driver modules currently loaded. > If the "ne" or "ne2k-pci"driver is loaded then you > should see it listed in the output to this command, > like so: > ne2k-pci4136 1 It was not loaded! > > Assuming it isn't loaded, try loading it by hand. > If your NIC is a PCI card you should use the ne2k-pci > driver, like so: > # modprobe ne2k-pci > > PCI cards shouldn't need any extra parameters. > > If it's an ISA card you will need to use the ne module, > and will need to pass at least the IO port as a parameter, > with a command like this: > # modprobe ne io=0x300 irq=10 > > You can skip the IRQ parameter, but if you know what it is > then it makes things a little more bullet-proof. If you don't > know what IO address the card is using, the Windows Device Manager > (under System in Control Panels) will probably tell you. > > If the card is a bona-fide ISA/PNP card (as opposed to a > traditional ISA card) then this will fail after a cold boot, and > you will need to set the card up using isapnp before you can > use it under Linux. > The full name of the card is D-Link DE220 ISA PnP -- is this a bona-fide ISA/PNP adaptor? I tried using the command # modprobe ne io=0x300 irq=03(these are the proper settings) and it didn't complain. However, I infer from your remarks that I will have to use 'isapnp'. I guess that this means I will have to edit (properly!) the /etc/isapnp.conf file. I looked at the website http://www.roestock.demon.co.uk/isapnptools and it looks like I will need a line in the file like: (CONFIGURE EDI0119/236861364 ( ... etc. The code 'EDI0119' identifies the ethernet card -- but how can I find what code to use for my card? Please let me know if there is anything else I have to know about 'isapnp'. > The way modules are handled changed a couple of times in older > (pre-2.1) Debian releases; you should check if the following files > exist: > /etc/modules.conf This one wasn't there! > /etc/conf.modules Present. > /etc/modutils/ (a directory) Present. > /etc/modules Present. > Get back to us when you've tried this and let us know what Debian > release you're using, and you should get some better-targeted > help. > Looking forward to it! James Polson
network/ethernet card configuration problem?
Hi, I'm completely new to Linux, so the solution to my problem may be trivial to all of you experienced Debian Linux users (so I hope!). I'm trying to install Debian Linux (mostly with success), but I think that I'm having problems connecting with the ethernet card in my computer. The symptoms are: (1) A message during booting that is something like "network is unreachable" (I don't know what log file to look for to get the exact wording). (2) When I type "ifconfig -a", I should see listings for two interfaces, "lo" and "eth0", but the second one (the ethernet one) is not there. (3) Not surprisingly, telnet, ftp, etc. can't be used. (4) In the /var/log/syslog file, there is a message: cardmgr[189]: starting, version is 3.0.5 cardmgr[189]: no sockets found! cardmgr[189]: exiting I think that this problem reported is related. Information about my system: (1) I have a D-Link DE 220 card. (2) I have the NC2000 driver in /lib/modules/2.0.36/net This is the appropriate driver for the card, according to the D-Link website. I would really appreciate it if anyone could help me with this problem. Until it's fixed, I have to rely on Windows 95 :( to connect to the internet. Thanks, James Polson
