Re: Notebook Network Issues
> OK, I still don't know what the problem is. The FA510 worked in RedHat > 6.2, and 8.0 but just won't work in Fedora Core 3. > > I downloaded the PCMCIA package update (to a different computer) and > used a disk to get it to the notebook. Once I upgrade PCMCIA, I tried > again. Still got nothing (although the error when restarting pcmcia went > away). So I tried an FA410 instead of the 510, and it worked. So that's > what I'm going to use. > > Thanks for everyones help! No I just need to figure out if I can use the > winmodem (LT Win Modem - HSM0a19) One big difference here is the kernel. Fedora Core 3 uses the 2.6 kernel, and some modules were not ported to it. While this may not be relevant, in the class I teach at NEU, we installed Linux in class. The students had a choice of Fedora Core 4 or SuSE 10.0. One student with a laptop had previously loaded Fedora Core 4, and was unable to get the wireless running. When he installed SuSE 10, the wireless (IPW2200) came right up. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Notebook Network Issues
OK, I still don't know what the problem is. The FA510 worked in RedHat 6.2, and 8.0 but just won't work in Fedora Core 3. I downloaded the PCMCIA package update (to a different computer) and used a disk to get it to the notebook. Once I upgrade PCMCIA, I tried again. Still got nothing (although the error when restarting pcmcia went away). So I tried an FA410 instead of the 510, and it worked. So that's what I'm going to use. Thanks for everyones help! No I just need to figure out if I can use the winmodem (LT Win Modem - HSM0a19) -- TARogue (Linux user number 234357) If God had wanted us to vote, he would have given us candidates. --Jay Leno ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Notebook Network Issues
On Feb 9, 2006, at 09:55, Thomas M. Albright wrote: /etc/modprobe.conf says: alias eth0 tulip but trying 'insmod eth0' returns insmod: can't read 'eth0': no such file or directory and trying 'insmod tulip' returns insmod: can't read 'tulip': no such file or directory I think depmod can help here. I had a similar issue on a FC3->FC4 upgrade: sudo depmod -ae -F /boot/System.map-[your `uname -a` kernel version here] seemed to do it. -Bill - Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 [EMAIL PROTECTED] Cell: 603.252.2606 http://www.bfccomputing.com/Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf smime.p7s Description: S/MIME cryptographic signature
Re: Notebook Network Issues
Ben said: > Boot the machine with the card removed. > Check the logs and/or dmesg for problems with PCMCIA. 'dmesg | grep -i pcmcia' came back empty So I tried restarting PCMCIA: /etc/init.d/pcmcia restart hutting down PCMCIA services: done. Starting PCMCIA services: cardmgr [2579]: open_sock(socket 2) failed: bad file descriptor cardmger [2579]: watching 2 sockets done. When I instered the card i saw: PCI: Enabling device :05:00.0 ( -> 0003) lsmod before and after only showed one change: yenta_socket changed from 'Used by 0' to 'Used by 1' /etc/modprobe.conf says: alias eth0 tulip but trying 'insmod eth0' returns insmod: can't read 'eth0': no such file or directory and trying 'insmod tulip' returns insmod: can't read 'tulip': no such file or directory My routing tables look good, the firewall has been flushed, and I still can't ping even inside the network. -- TARogue (Linux user number 234357) -Give a man a fish & he's fed for a day. Teach him to fish & he'll spend all day drinking beer getting sunburned. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Notebook Network Issues
On Tuesday 07 February 2006 06:42 pm, Thomas M. Albright wrote: > I have an old Acer Extensa 368D notebook computer I want to use as my > router. I installed Fedora Core 3 and everthing went fine. Or so it > seemed ... > > The network *says* it's running, but I can't get out! Just for kicks, have you verified that "/sbin/route" shows the way out? Have you tried to ping by IP address to anything on the local network? Have you tried disabling any IPTables stuff that may be in the way? "/sbin/iptables -L" should just tell you that the three primary chains are all set to ACCEPT. Other than that, the rest of the information requested by Ben would be helpful. -N ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Re: Notebook Network Issues
On 2/7/06, Thomas M. Albright <[EMAIL PROTECTED]> wrote: > I have an old Acer Extensa 368D notebook computer I want to use as my > router. I installed Fedora Core 3 and everthing went fine. Or so it > seemed ... > > The network *says* it's running, but I can't get out! > > The card is a Netgear FA510 > Restarting the PCMCIA gives me ... I suspect we need more information. Suggested troubleshooting strategy: Boot the machine with the card removed. Check the logs and/or dmesg for problems with PCMCIA. Check the module list to see what is currently loaded. Insert the card. Check the logs and/or dmesg for problems with PCMCIA or that card. Check the module list to see if additional modules were loaded. If so, cross-reference between the modules being loaded and the card. Make sure they're the right modules for the card, and look for any known issues. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
Notebook Network Issues
I have an old Acer Extensa 368D notebook computer I want to use as my router. I installed Fedora Core 3 and everthing went fine. Or so it seemed ... The network *says* it's running, but I can't get out! The card is a Netgear FA510 Restarting the PCMCIA gives me: Shutting down PCMCIA services: ERROR: Module ds is in use by pcnet_cs ERROR: Module pcmcia_core is in use by yenta_socket,pcnet_cs,ds done. Starting PCMCIA services: cardmgr[2955]: open_sock(socket 2) failed: Bad file descriptor cardmgr[2955]: watching 2 sockets done. This card worked fine when the laptop was running RedHat 6.2 How do I fix that? -- TARogue (Linux user number 234357) The more corrupt the state, the more numerous the laws. - Tacitus, 56-120 A.D. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss
