public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Jayson Smith" <ratguy@insightbb.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Ethernet not working, a weird one!
Date: Sat, 25 Jul 2009 17:42:31 -0400	[thread overview]
Message-ID: <315CDBF91008414B988342B021146E3F@Boe> (raw)
In-Reply-To: <20090725201650.GA4231@romuald.net.eu.org>

Hi,

     You nailed it. Near the end of dmesg, I get this line:
udev: renamed network interface eth0 to eth1
That would just about do it. Question is, why's it doing it, and how do I 
stop it? I am not at all familiar with udev, so a simple explanation would 
probably be best.
Thanks,
Jayson

----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, July 25, 2009 4:16 PM
Subject: Re: Ethernet not working, a weird one!


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, Jul 25, 2009 at 12:47:18PM -0400, Jayson Smith wrote:
>>     On June 18, lightning struck our home.
>
> Wow, do you mean that literally? If you mean that lightning struck your
> power/phone lines, then I'd strongly suggest investing in a surge
> protector, one with protection for both power and phone, and hook up
> your pc to it, including network hub/switch, and dsl/dial-up modems to
> the phone line through the protector. If you have cable, then there
> are surge protectors that also have coax jacks.
>
>> What could this be?
>
> If the card shows up in lspci, and you have the driver for it loaded,
> it should also show up in dmesg. So, what does dmesg have to say? I'd
> say you might have a udev issue somewhere, though that's just a
> guess. Also, are you sure that the card isn't in fact recognized? It
> could be recognized, but assigned a different interface, like eth1
> instead of eth0. If that's the case, then that's a udev rule issue. To
> answer your other question in another post, no, if you have the driver
> built into the kernel, then there are no modules to load.
>
>>     If I end up having to rebuild from scratch, what is a currently good
>> distro for console only, no GUI Linux that supports Speakup? If I were
>> rebuilding anyway, I would strongly consider switching from Gentoo to an
>> easier to maintain distro.
>
> I'd recommend debian myself.
>
> Greg
>
>
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkpraDIACgkQ7s9z/XlyUyBmcACgmx1zbLj6rU/fZSOQe6TyG6qZ
> wg4An1hkrkt5B911HKoKxN9JysQOHVwR
> =caB1
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup 


  parent reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jayson Smith
 ` James Homuth
   ` Jayson Smith
 ` Gregory Nowak
   ` Jayson Smith
   ` Jayson Smith [this message]
     ` Gregory Nowak
       ` Jayson Smith
 ` Joseph C. Lininger
 ` Tony Baechler
   ` Gregory Nowak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=315CDBF91008414B988342B021146E3F@Boe \
    --to=ratguy@insightbb.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).