Intenet access with LiveCD?

[Jim Dever]

Hi,

I was excited to see the release of the Fedora LiveCD as I'm looking
around at different distributions but for some reason I can't get it to
see my internet connection at all.

If anyone could point me in the right direction I'd appreciate it.

NIC:  Cnet PRO200WL PCI (not wireless)
Router:  Linksys RTP300

Output of ifconfig:

eth0  Link encap:Ethernet  HWaddr 00:80:AD:79:95:90
      inet addr: 192.168.15.102  Bcast: 192.168.15.255  Mask: 255.255.255.0
      inet6 addr: fe80::280:adiff:fe79:9590/64  Scope: Link
      UP BROADCAST MULTICAST MTU:1500 Metric: 1
      RX packets: 13  errors: 170  dropped: 0  overruns: 0  frame: 0
      TX packets: 0  errors: 10  dropped: 0  overruns: 0  carrier: 10
      collisions: 0  txqueuelen: 1000
      RX bytes: 2597 (2.5 KiB)  TX bytes: 0  (0.0 b)
      Interrupt: 201  Base address: 0xec00

-----

I noticed that it says UP but not RUNNING.

The Ubuntu LiveCD access the internet just fine so I know it's possible
to MAKE it work.  I just like to see it work before making room for a
full install.

I've used Linux before but it's been ages ago and before I had a NIC so
I'm pretty new to this part.

Any help would be appreciated!

[Thomas Chung]

On 12/27/06, Jim Dever  wrote:
> Hi,
>
> I was excited to see the release of the Fedora LiveCD as I'm looking
> around at different distributions but for some reason I can't get it to
> see my internet connection at all.
>
> If anyone could point me in the right direction I'd appreciate it.
>
> NIC:  Cnet PRO200WL PCI (not wireless)
> Router:  Linksys RTP300
>
> Output of ifconfig:
>
> eth0  Link encap:Ethernet  HWaddr 00:80:AD:79:95:90
>       inet addr: 192.168.15.102  Bcast: 192.168.15.255  Mask: 255.255.255.0
>       inet6 addr: fe80::280:adiff:fe79:9590/64  Scope: Link
>       UP BROADCAST MULTICAST MTU:1500 Metric: 1
>       RX packets: 13  errors: 170  dropped: 0  overruns: 0  frame: 0
>       TX packets: 0  errors: 10  dropped: 0  overruns: 0  carrier: 10
>       collisions: 0  txqueuelen: 1000
>       RX bytes: 2597 (2.5 KiB)  TX bytes: 0  (0.0 b)
>       Interrupt: 201  Base address: 0xec00
>
> I noticed that it says UP but not RUNNING.
>
> The Ubuntu LiveCD access the internet just fine so I know it's possible
> to MAKE it work.  I just like to see it work before making room for a
> full install.
>
> I've used Linux before but it's been ages ago and before I had a NIC so
> I'm pretty new to this part.
>
> Any help would be appreciated!
>
> --
> Jim

I'm not sure if this will help but please refer to:
http://fedoraproject.org/wiki/ThomasChung/LiveCD
Regards,

[Jim Dever]

Thomas Chung wrote:
> I'm not sure if this will help but please refer to:
> http://fedoraproject.org/wiki/ThomasChung/LiveCD

Thanks!  I found your well written wiki earlier and at least it gave me
something to try before asking.  Unfortunately I've tried configuring
both for DHCP and a static IP and the internet is still unreachable.
The RUNNING attribute never appears on ifconfig.

I may not be doing the static config properly though as I'm not sure
what to use for the domain in the "search" keyword in /etc/resolve.conf.
 Maybe knowing this would help.

Any other ideas greatly appreciated!

Thanks!

[Jim Dever]

Thomas Chung wrote:
> I'm not sure if this will help but please refer to:
> http://fedoraproject.org/wiki/ThomasChung/LiveCD

By the way... I tried following your instructions again after you sent
me your reply just to see if I screwed up something and had no luck.

[Jim Dever]

Thomas Chung wrote:
> I'm not sure if this will help but please refer to:
> http://fedoraproject.org/wiki/ThomasChung/LiveCD

Just for the record this has been resolved.  After much hair pulling and
searching the internet it turns out to be a driver conflict.

Intenet access was obtained by:

ifdown eth0
modprobe -r dmfe
modprobe -r tulip
modprobe dmfe
ifup eth0

Evidently the tulip and dmfe modules togehter have a conflict with my
network card.  I'm hoping this can be solved after an install by
blacklisting the tulip module.

Thanks!

[Thomas Chung]

On 12/28/06, Jim Dever  wrote:
> Just for the record this has been resolved.  After much hair pulling and
> searching the internet it turns out to be a driver conflict.
>
> Intenet access was obtained by:
>
> ifdown eth0
> modprobe -r dmfe
> modprobe -r tulip
> modprobe dmfe
> ifup eth0
>
> Evidently the tulip and dmfe modules togehter have a conflict with my
> network card.  I'm hoping this can be solved after an install by
> blacklisting the tulip module.
>
> Thanks!

Thank you for letting me know.
Regards,

[David Zeuthen]

Hi,

On Thu, 2006-12-28 at 21:43 -0500, Jim Dever wrote:
> Intenet access was obtained by:
>
> ifdown eth0
> modprobe -r dmfe
> modprobe -r tulip
> modprobe dmfe
> ifup eth0
>
> Evidently the tulip and dmfe modules togehter have a conflict with my
> network card.  I'm hoping this can be solved after an install by
> blacklisting the tulip module.

Weird. Users should never have to blacklist modules nor even know what a
LKM is. So this should probably get filed in Bugzilla at

https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core

and if you can paste the bug number here I'll follow up with one of our
kernel dudes, thanks! Basically, if you have a driver that works the
live cd should automatically connect to wired network using DHCP.

Likewise, if your wireless chipset is supported and you have the
firmware etc. connecting to a wireless network (either cleartext, WEP,
WPA, etc.) via DHCP should be as easy as selecting it from a drop-down
menu.

So, in 99% of all cases, non-working network connectivity is most likely
either a kernel/driver bug or simply missing firmware / drivers.

David

[Jim Dever]

David Zeuthen wrote:
> Hi,
>
> On Thu, 2006-12-28 at 21:43 -0500, Jim Dever wrote:
> > Intenet access was obtained by:
> >
> > ifdown eth0
> > modprobe -r dmfe
> > modprobe -r tulip
> > modprobe dmfe
> > ifup eth0
> >
> > Evidently the tulip and dmfe modules togehter have a conflict with my
> > network card.  I'm hoping this can be solved after an install by
> > blacklisting the tulip module.
>
> Weird. Users should never have to blacklist modules nor even know what a
> LKM is. So this should probably get filed in Bugzilla at
>
> https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core
>
> and if you can paste the bug number here I'll follow up with one of our
> kernel dudes, thanks! Basically, if you have a driver that works the
> live cd should automatically connect to wired network using DHCP.
>
> Likewise, if your wireless chipset is supported and you have the
> firmware etc. connecting to a wireless network (either cleartext, WEP,
> WPA, etc.) via DHCP should be as easy as selecting it from a drop-down
> menu.
>
> So, in 99% of all cases, non-working network connectivity is most likely
> either a kernel/driver bug or simply missing firmware / drivers.

I realize this is a thread I started a long time ago but just wanted you
guys to know that the Fedora 7 Test 4 LiveCD works with my network card
(a Cnet PRO200WL PCI) straight out of the box and without any fiddling
around.  Glad to see it!

Thanks!

Jim

[Thomas Chung]

On 5/9/07, Jim Dever  wrote:
> David Zeuthen wrote:
> > Hi,
> >
> > On Thu, 2006-12-28 at 21:43 -0500, Jim Dever wrote:
> > > Intenet access was obtained by:
> > >
> > > ifdown eth0
> > > modprobe -r dmfe
> > > modprobe -r tulip
> > > modprobe dmfe
> > > ifup eth0
> > >
> > > Evidently the tulip and dmfe modules togehter have a conflict with my
> > > network card.  I'm hoping this can be solved after an install by
> > > blacklisting the tulip module.
> >
> > Weird. Users should never have to blacklist modules nor even know what a
> > LKM is. So this should probably get filed in Bugzilla at
> >
> > https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Core
> >
> > and if you can paste the bug number here I'll follow up with one of our
> > kernel dudes, thanks! Basically, if you have a driver that works the
> > live cd should automatically connect to wired network using DHCP.
> >
> > Likewise, if your wireless chipset is supported and you have the
> > firmware etc. connecting to a wireless network (either cleartext, WEP,
> > WPA, etc.) via DHCP should be as easy as selecting it from a drop-down
> > menu.
> >
> > So, in 99% of all cases, non-working network connectivity is most likely
> > either a kernel/driver bug or simply missing firmware / drivers.
>
> I realize this is a thread I started a long time ago but just wanted you
> guys to know that the Fedora 7 Test 4 LiveCD works with my network card
> (a Cnet PRO200WL PCI) straight out of the box and without any fiddling
> around.  Glad to see it!
>
> Thanks!
>
> Jim

Thank you for letting us know. :)
Regards,