Hi all Fedora users,
I have just joined this list. I am running the latest Fedora but I can't get
my 3C900Combo networking card to work. I can see that the card is installed
but no IP-address is asigned to it and I can't set it. So I think that there
is a bug in that driver. Any other user out there who have a solution for
Best regards and thanks,
I know that is not a specific question about Fedora, but I can't find answer on the kernel mailing list.
Is somebody having server with integrated ATI RAGE XL video card? Is it possible to patch the kernel to support this video card? If I add VGA=791 in my grub.conf, I will have a resolution of 1024x768 which is good, but the display is very slow (especially when the screen is scrolling). If I use I this: "video=aty128fb:1024x768@70" it will not work. I'm using kernel 2.4.22 but I will try 2.6.0-test11 today.
If somebody has a patch, a link or anything else that can help me, it will be appreciated.
Thanks for your help.
Administrateur Réseau/Network Manager
Institut de Pharmacologie de Sherbrooke
3e étage (Édifice Z5)
3001 12e avenue Nord
Tél.: +1 819 820-6040
Direct: +1 819 820-6855
Fax.: +1 819 820-6841
I have two similar PC (old Pentium but workin fine)
In Pc no.1 I upgraded from RH8 to Fedora and it went fine: Soundblaster
is working fine
In Pc no.2 I made a fresh installation but in redhat-sound-config Fedora
doesn't see any card, that was working on Redhat 9 after soundconfig...
Where is the trick?? I assume that my Sounblaster is an old 16...but
fine on a router/firewall.
I've made some progress on troubleshooting this "ssh & port 22 problem".
Here was my original post:
When I try to connect from a remote machine to my one at home
using ssh I get the error message "ssh: connect to host 220.127.116.11 port
22: Connection refused" -- but using ssh in the outgoing direction (i.e.
from home to the remote location) works fine.
Here's what's happened since:
I have two machines (PuteA and PuteB) sharing an ActionTec DSL modem. The IP
I was using was that of my "Gateway" ISP (18.104.22.168) -- an error. But
when I used the correct, static IP address of the ActionTec
(22.214.171.124) I got this message:
ssh: connect to host 126.96.36.199 port22: Connection refused
I thought I had port forwarding (for port 22) set correctly on the modem. For
troubleshooting, my ISP advised me to run "tcpdump -n host 192.168.0.2" on
PuteA, where 192.168.0.2 is the "internal" IP of PuteA. Then I logged on
to the remote location from PuteB and tried to ssh from there to PuteA
using the static IP address. The ssh from the remote location timed out
with the same "port 22: connection refused" message. The tcpdump on Pute
A gave this message:
> tcpdump: listening on eth0
> 17:27:33.662753 arp who-has 192.168.0.2 tell 192.168.0.1
where 188.8.131.52 is the "internal" IP of the modem. (Sorry if I have
this terminology wrong.)
My ISP says the problem is the firewall on PuteA and that he doesn't do linux
Here are my replies to the people who responded to my first post:
(1) "Do you have the firewall configured to deny incoming packets to port
How do I check this?
(2) "You need to check that sshd is running on your system."
Yes. I comes up with each boot. Also "service sshd status" gives
"sshd (pid 787) is running".
(3) "sshd uses /etc/hosts.allow and /etc/hosts.deny. Check that they are
configured to allow your remote machine in."
Both files have only commented lines.
(4) "Also, if your /etc/ssh/sshd_config file has VerifyReverseMapping
turned on, you will get kicked out if your remote address does not work
with a reverse dns lookup."
There's a "VerifyReverseMapping no" line in the file but it's been commented
(5) "Just to be sure: when you are at home machine, try 'ssh localhost'.
If this works, you probably need to check your firewall."
It seems to work -- I ssh to the machine itself.
(6) "This is common on every system I have ever loaded with FC2. Your
iptables are blocking the connection. You can do one of the following:
iptables -A INPUT -m tcp -p tcp --dport 22 - j ACCEPT"
I tried this. The ssh to PuteA from the remote location still times out.
(7) "Oh yes I also took out the REDHAT firewall entrie as I dont have a
clue as to how to work with it."
I've fiddled endlessly with this "system tool" at each of the three levels
of security as well as using the "customize" option to set eth0 as a
trusted device and to allow incoming ssh. It doesn't show the settings
that actually exist.
(8) "If your fedora box is connected directly to a DSL modem, you should
be able to find your IP address by running ifconfig from the command
line and looking for 'inet addr:' (probably under 'eth0')."
eth0 Link encap:Ethernet HWaddr 00:40:05:81:60:8E
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2184 errors:0 dropped:0 overruns:0 frame:0
TX packets:2005 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:1122075 (1.0 Mb) TX bytes:190214 (185.7 Kb)
Interrupt:5 Base address:0x3000
Could this be the problem -- the "inet addr" of 192.168.0.4? As far as I
can tell, the modem is 192.168.0.1, PuteA is 192.168.0.2, and PuteB is
192.168.0.3. I haven't set anything as 192.168.0.4.
(9) "nmap 184.108.40.206"
(The 1598 ports scanned but not shown below are in state: closed)
Port State Service
23/tcp open telnet
53/tcp open domain
80/tcp open http
Shouldn't ssh be here? And what's telnet doing open? The books have me
scared to death of this... hackers, crackers, script kiddies, etc.
Thanks for the help!
each time i boot fedora i must enable by hand the eth0 device (by the
What must i do to enable the device at boot?
# cat /etc/sysconfig/network
# cat /etc/sysconfig/networking/devices/ifcfg-eth0
# cat /etc/sysconfig/networking/profiles/default/ifcfg-eth0
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
all 3 the same output
# Macronix, Inc. [MXIC]|MX987x5
alias wfx (http://teg.sf.net)
I seem to have (finally :) ) acquired a complete(ish) / working x86_64
system .. but I'm still having trouble with a few bits, not least "yum".
Server: Fedora Core 1 - i386 - Base
Server: Fedora Core 1 - i386 - Released Updates
Server: Fedora Core 1 - i386 - Unreleased Updates
Finding updated packages
Traceback (most recent call last):
File "/usr/bin/yum", line 60, in ?
File "yummain.py", line 204, in main
File "clientStuff.py", line 363, in getupdatedhdrlist
File "clientStuff.py", line 409, in bestversion
IndexError: list index out of range
(This is a modified system [2.6.0-test11] however it seems to run well)
Pointing it at mozilla's channel for SeaMonkey seems to work if I
disable the default channels, however...
Anyone any ideas ?
(I was sort of expecting to see it say "no x86_64 updates supported yet"
as opposed to a complete crash)
Also, can yum pull SRPMS and rebuild them ?
I can't understand the behavior of kudzu in respect to my serial
modem. After initial installation it detects the modem but after that
it is ignored. What I mean is I can remove the modem and kudzu ignores
the change, or I can remove the modem from the kudzu database and
kudzu ignores the change. I can run: kudzu --class MODEM and kudzu
will remove all my hardware from its database except the MOUSE but it
still ignores the modem.
How can I get kudzu to notice that I have changed, removed or added
One Trinity Place.
San Antonio, TX 78212-7200
Hello everyone. I have a problem I was hoping someone could help me
with. When I try to boot my Fedora CD I get this message
ISOLINUX 2.06 2003-08-22 isolinux: disk error 01, AX = 4293, 9F
I have no idea what it means or what to do. Any help that someone could
give me would be appreciated.
> When I try to connect from a remote machine to my one at home
> using ssh I get the error message "ssh: connect to host 220.127.116.11 port
> 22: Connection refused" -- but using ssh in the outgoing direction (i.e.
> from home to the remote location) works fine. Any suggestions as to how
> to troubleshoot this?
I looked at your IP to see what kind of router you had.
It appears to be supplied by your ISP, because telnet showed:
Sawtooth Technologies, LLC Stevenson, WA Unauthorized Access is Prohibited
gw-sawtooth.pdx.rain.net 98.10.20-0 For Service Call +1 509 427-4865
Sawtooth Technologies Ether 18.104.22.168 PL/DHGL/109201/ELG 22.214.171.124
So you may need to call them to get the password or to forward port 22