* results of my try.
@ Karen Lewellen
` Cheryl Homiak
` (2 more replies)
0 siblings, 3 replies; 11+ messages in thread
From: Karen Lewellen @ UTC (permalink / raw)
To: Linux for blind general discussion
Hi all,
here is what happened when seeking the ip address.
Let me explain how I set up the machine.
before even booting I put the dsl cable I am using now to send
this message into the linux box, keeping it connected to my
modem/rooter as usual.
Because we were pressed for time, after letting speakup start,
and entering my username, Karen, and my password, I simply used
the print screen key to silence speakup.
the error message we got is below.
I saw karen@suburst:~s and there was no other place to type so
after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed
the message we got was: eth0: error fetching interface
information: Device not Found
We tried the step more than once to be sure.
let me add that typing shutdown -h also produced an error, so I
simply turned off the machine after restoring speakup.
The Ethernet card was in the computer before the hard drive
containing Debian was installed, so was the rest of the hardware
Linux identified.
thoughts?
Karen
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: results of my try. results of my try Karen Lewellen @ ` Cheryl Homiak ` Willem van der Walt ` Tim Chase 2 siblings, 0 replies; 11+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: Linux for blind general discussion I don't think this is the only problem from the errors you got, but shouldn't you have been doing these commands "ifconfig" and "shutdown" as root rather than as your user? Also, ~# is for root and ~$ is for a normal user but what is ~s for? Maybe I missed the post that explained more about what you are doing? But in debian you would usually do shutdown -h as root and you would need a further designation such as now if you want it to shut down immediately. An ifconfig command would also usually be done as root. Also, are you sure that your ethernet card works and is recognized by your debian installation? If the card wasn't recognized or a module was needed for the ethernet card that you don't have loading, I think you might get that error. I admit I hadn't really noticed or been following this thread so what I am writing may be something you already know or your setup may be different than I think it is, but I am a debian user. -- Cheryl "Move forward by looking back! "Above all, fear the Lord and worship Him faithfully with all your heart; consider the great things He has done for you." (1 Samuel 12:24 (HCSB) On Jan 27, 2015, at 7:13 PM, Karen Lewellen <klewellen@shellworld.net> wrote: Hi all, here is what happened when seeking the ip address. Let me explain how I set up the machine. before even booting I put the dsl cable I am using now to send this message into the linux box, keeping it connected to my modem/rooter as usual. Because we were pressed for time, after letting speakup start, and entering my username, Karen, and my password, I simply used the print screen key to silence speakup. the error message we got is below. I saw karen@suburst:~s and there was no other place to type so after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed the message we got was: eth0: error fetching interface information: Device not Found We tried the step more than once to be sure. let me add that typing shutdown -h also produced an error, so I simply turned off the machine after restoring speakup. The Ethernet card was in the computer before the hard drive containing Debian was installed, so was the rest of the hardware Linux identified. thoughts? Karen _______________________________________________ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. results of my try Karen Lewellen ` Cheryl Homiak @ ` Willem van der Walt ` Karen Lewellen ` Tim Chase 2 siblings, 1 reply; 11+ messages in thread From: Willem van der Walt @ UTC (permalink / raw) To: Linux for blind general discussion Hi, As root, do: ifconfig and check which interfaces show up. Your ethernet might be picked up as another interface, e.g. eth1. You should simply first test by pinging your router. HTH, Willem On Tue, 27 Jan 2015, Karen Lewellen wrote: > Hi all, > here is what happened when seeking the ip address. > Let me explain how I set up the machine. > before even booting I put the dsl cable I am using now to send > this message into the linux box, keeping it connected to my > modem/rooter as usual. > Because we were pressed for time, after letting speakup start, > and entering my username, Karen, and my password, I simply used > the print screen key to silence speakup. > the error message we got is below. > I saw karen@suburst:~s and there was no other place to type so > after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed > the message we got was: eth0: error fetching interface > information: Device not Found > > We tried the step more than once to be sure. > let me add that typing shutdown -h also produced an error, so I > simply turned off the machine after restoring speakup. > The Ethernet card was in the computer before the hard drive > containing Debian was installed, so was the rest of the hardware > Linux identified. > thoughts? > Karen > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > -- > This message is subject to the CSIR's copyright terms and conditions, e-mail > legal notice, and implemented Open Document Format (ODF) standard. The full > disclaimer details can be found at http://www.csir.co.za/disclaimer.html. > > This message has been scanned for viruses and dangerous content by > MailScanner, and is believed to be clean. > > Please consider the environment before printing this email. > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Willem van der Walt @ ` Karen Lewellen ` Cheryl Homiak 0 siblings, 1 reply; 11+ messages in thread From: Karen Lewellen @ UTC (permalink / raw) To: Linux for blind general discussion I believe I have made it very clear how much experimentation is possible in prior discussions. I followed Tim's directions, there are the results. Karen On Wed, 28 Jan 2015, Willem van der Walt wrote: > Hi, > As root, do: > ifconfig and check which interfaces show up. Your ethernet might be picked > up as another interface, e.g. eth1. > You should simply first test by pinging your router. > HTH, Willem > > > On Tue, 27 Jan 2015, Karen Lewellen wrote: > >> Hi all, >> here is what happened when seeking the ip address. >> Let me explain how I set up the machine. >> before even booting I put the dsl cable I am using now to send >> this message into the linux box, keeping it connected to my >> modem/rooter as usual. >> Because we were pressed for time, after letting speakup start, >> and entering my username, Karen, and my password, I simply used >> the print screen key to silence speakup. >> the error message we got is below. >> I saw karen@suburst:~s and there was no other place to type so >> after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed >> the message we got was: eth0: error fetching interface >> information: Device not Found >> >> We tried the step more than once to be sure. >> let me add that typing shutdown -h also produced an error, so I >> simply turned off the machine after restoring speakup. >> The Ethernet card was in the computer before the hard drive >> containing Debian was installed, so was the rest of the hardware >> Linux identified. >> thoughts? >> Karen >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> -- >> This message is subject to the CSIR's copyright terms and conditions, >> e-mail legal notice, and implemented Open Document Format (ODF) standard. >> The full disclaimer details can be found at >> http://www.csir.co.za/disclaimer.html. >> >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> Please consider the environment before printing this email. >> >> > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Karen Lewellen @ ` Cheryl Homiak ` Karen Lewellen ` Geoff Shang 0 siblings, 2 replies; 11+ messages in thread From: Cheryl Homiak @ UTC (permalink / raw) To: Linux for blind general discussion Actually, the suggestions don't require any more experimentation than what you did. But the command you did as a regular user really does have to be done as root. Also the only difference between ifconfig eth0 and ifconfig is that the ifconfig without the argument allows debian to show you which interfaces if any are working. It is quite possible that your setup is working but under a different interface than eth0. -- Cheryl "Move forward by looking back! "Above all, fear the Lord and worship Him faithfully with all your heart; consider the great things He has done for you." (1 Samuel 12:24 (HCSB) On Jan 28, 2015, at 10:34 AM, Karen Lewellen <klewellen@shellworld.net> wrote: I believe I have made it very clear how much experimentation is possible in prior discussions. I followed Tim's directions, there are the results. Karen On Wed, 28 Jan 2015, Willem van der Walt wrote: > Hi, > As root, do: > ifconfig and check which interfaces show up. Your ethernet might be picked up as another interface, e.g. eth1. > You should simply first test by pinging your router. > HTH, Willem > > > On Tue, 27 Jan 2015, Karen Lewellen wrote: > >> Hi all, >> here is what happened when seeking the ip address. >> Let me explain how I set up the machine. >> before even booting I put the dsl cable I am using now to send >> this message into the linux box, keeping it connected to my >> modem/rooter as usual. >> Because we were pressed for time, after letting speakup start, >> and entering my username, Karen, and my password, I simply used >> the print screen key to silence speakup. >> the error message we got is below. >> I saw karen@suburst:~s and there was no other place to type so >> after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed >> the message we got was: eth0: error fetching interface >> information: Device not Found >> >> We tried the step more than once to be sure. >> let me add that typing shutdown -h also produced an error, so I >> simply turned off the machine after restoring speakup. >> The Ethernet card was in the computer before the hard drive >> containing Debian was installed, so was the rest of the hardware >> Linux identified. >> thoughts? >> Karen >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> -- >> This message is subject to the CSIR's copyright terms and conditions, >> e-mail legal notice, and implemented Open Document Format (ODF) standard. >> The full disclaimer details can be found at >> http://www.csir.co.za/disclaimer.html. >> >> This message has been scanned for viruses and dangerous content by >> MailScanner, and is believed to be clean. >> >> Please consider the environment before printing this email. > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > > _______________________________________________ Blinux-list mailing list Blinux-list@redhat.com https://www.redhat.com/mailman/listinfo/blinux-list ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Cheryl Homiak @ ` Karen Lewellen ` Christopher Chaltain ` Geoff Shang 1 sibling, 1 reply; 11+ messages in thread From: Karen Lewellen @ UTC (permalink / raw) To: Linux for blind general discussion To paraphrase Tim, those suggestions require eyeballs. If you read the information, it should be clear I had to get someone else to do that, and it took some arranging. On Wed, 28 Jan 2015, Cheryl Homiak wrote: > Actually, the suggestions don't require any more experimentation than what you did. But the command you did as a regular user really does have to be done as root. Also the only difference between ifconfig eth0 and ifconfig is that the ifconfig without the argument allows debian to show you which interfaces if any are working. It is quite possible that your setup is working but under a different interface than eth0. > > -- > Cheryl > > "Move forward by looking back! > "Above all, fear the Lord > and worship Him faithfully with all your heart; > consider the great things He has done for you." > (1 Samuel 12:24 (HCSB) > > > > > > On Jan 28, 2015, at 10:34 AM, Karen Lewellen <klewellen@shellworld.net> wrote: > > I believe I have made it very clear how much experimentation is possible in prior discussions. > I followed Tim's directions, there are the results. > Karen > > > On Wed, 28 Jan 2015, Willem van der Walt wrote: > >> Hi, >> As root, do: >> ifconfig and check which interfaces show up. Your ethernet might be picked up as another interface, e.g. eth1. >> You should simply first test by pinging your router. >> HTH, Willem >> >> >> On Tue, 27 Jan 2015, Karen Lewellen wrote: >> >>> Hi all, >>> here is what happened when seeking the ip address. >>> Let me explain how I set up the machine. >>> before even booting I put the dsl cable I am using now to send >>> this message into the linux box, keeping it connected to my >>> modem/rooter as usual. >>> Because we were pressed for time, after letting speakup start, >>> and entering my username, Karen, and my password, I simply used >>> the print screen key to silence speakup. >>> the error message we got is below. >>> I saw karen@suburst:~s and there was no other place to type so >>> after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed >>> the message we got was: eth0: error fetching interface >>> information: Device not Found >>> >>> We tried the step more than once to be sure. >>> let me add that typing shutdown -h also produced an error, so I >>> simply turned off the machine after restoring speakup. >>> The Ethernet card was in the computer before the hard drive >>> containing Debian was installed, so was the rest of the hardware >>> Linux identified. >>> thoughts? >>> Karen >>> >>> _______________________________________________ >>> Blinux-list mailing list >>> Blinux-list@redhat.com >>> https://www.redhat.com/mailman/listinfo/blinux-list >>> >>> -- >>> This message is subject to the CSIR's copyright terms and conditions, >>> e-mail legal notice, and implemented Open Document Format (ODF) standard. >>> The full disclaimer details can be found at >>> http://www.csir.co.za/disclaimer.html. >>> >>> This message has been scanned for viruses and dangerous content by >>> MailScanner, and is believed to be clean. >>> >>> Please consider the environment before printing this email. >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> >> > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Karen Lewellen @ ` Christopher Chaltain ` Karen Lewellen 0 siblings, 1 reply; 11+ messages in thread From: Christopher Chaltain @ UTC (permalink / raw) To: Linux for blind general discussion I don't understand the need to get someone sighted, and I read the whole thread. You mention silencing Speakup, but I'm not sure why. Why can't you leave Speakup running, run the commands with Speakup and capture the output to share with the list? If you're referring to content in another thread, I don't recall that information. I'm not a paid support staff member, I'm just another Linux user trying to help. On 01/28/2015 05:28 PM, Karen Lewellen wrote: > To paraphrase Tim, those suggestions require eyeballs. If you read the > information, it should be clear I had to get someone else to do that, > and it took some arranging. > > > On Wed, 28 Jan 2015, Cheryl Homiak wrote: > >> Actually, the suggestions don't require any more experimentation than >> what you did. But the command you did as a regular user really does >> have to be done as root. Also the only difference between ifconfig >> eth0 and ifconfig is that the ifconfig without the argument allows >> debian to show you which interfaces if any are working. It is quite >> possible that your setup is working but under a different interface >> than eth0. >> >> -- >> Cheryl >> >> "Move forward by looking back! >> "Above all, fear the Lord >> and worship Him faithfully with all your heart; >> consider the great things He has done for you." >> (1 Samuel 12:24 (HCSB) >> >> >> >> >> >> On Jan 28, 2015, at 10:34 AM, Karen Lewellen >> <klewellen@shellworld.net> wrote: >> >> I believe I have made it very clear how much experimentation is >> possible in prior discussions. >> I followed Tim's directions, there are the results. >> Karen >> >> >> On Wed, 28 Jan 2015, Willem van der Walt wrote: >> >>> Hi, >>> As root, do: >>> ifconfig and check which interfaces show up. Your ethernet might be >>> picked up as another interface, e.g. eth1. >>> You should simply first test by pinging your router. >>> HTH, Willem >>> >>> >>> On Tue, 27 Jan 2015, Karen Lewellen wrote: >>> >>>> Hi all, >>>> here is what happened when seeking the ip address. >>>> Let me explain how I set up the machine. >>>> before even booting I put the dsl cable I am using now to send >>>> this message into the linux box, keeping it connected to my >>>> modem/rooter as usual. >>>> Because we were pressed for time, after letting speakup start, >>>> and entering my username, Karen, and my password, I simply used >>>> the print screen key to silence speakup. >>>> the error message we got is below. >>>> I saw karen@suburst:~s and there was no other place to type so >>>> after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed >>>> the message we got was: eth0: error fetching interface >>>> information: Device not Found >>>> >>>> We tried the step more than once to be sure. >>>> let me add that typing shutdown -h also produced an error, so I >>>> simply turned off the machine after restoring speakup. >>>> The Ethernet card was in the computer before the hard drive >>>> containing Debian was installed, so was the rest of the hardware >>>> Linux identified. >>>> thoughts? >>>> Karen >>>> >>>> _______________________________________________ >>>> Blinux-list mailing list >>>> Blinux-list@redhat.com >>>> https://www.redhat.com/mailman/listinfo/blinux-list >>>> >>>> -- >>>> This message is subject to the CSIR's copyright terms and conditions, >>>> e-mail legal notice, and implemented Open Document Format (ODF) >>>> standard. >>>> The full disclaimer details can be found at >>>> http://www.csir.co.za/disclaimer.html. >>>> >>>> This message has been scanned for viruses and dangerous content by >>>> MailScanner, and is believed to be clean. >>>> >>>> Please consider the environment before printing this email. >>> >>> _______________________________________________ >>> Blinux-list mailing list >>> Blinux-list@redhat.com >>> https://www.redhat.com/mailman/listinfo/blinux-list >>> >>> >>> >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list >> >> > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list -- Christopher (CJ) chaltain at Gmail ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Christopher Chaltain @ ` Karen Lewellen 0 siblings, 0 replies; 11+ messages in thread From: Karen Lewellen @ UTC (permalink / raw) To: Linux for blind general discussion because speakup commands do not work with my hands. I do not care for its function, things are used for one side of the keyboard, etc. etc. Oh and the materials for the program leave *much* to be desired. On Wed, 28 Jan 2015, Christopher Chaltain wrote: > I don't understand the need to get someone sighted, and I read the whole > thread. You mention silencing Speakup, but I'm not sure why. Why can't you > leave Speakup running, run the commands with Speakup and capture the output > to share with the list? If you're referring to content in another thread, I > don't recall that information. I'm not a paid support staff member, I'm just > another Linux user trying to help. > > On 01/28/2015 05:28 PM, Karen Lewellen wrote: >> To paraphrase Tim, those suggestions require eyeballs. If you read the >> information, it should be clear I had to get someone else to do that, >> and it took some arranging. >> >> >> On Wed, 28 Jan 2015, Cheryl Homiak wrote: >> >> > Actually, the suggestions don't require any more experimentation than >> > what you did. But the command you did as a regular user really does >> > have to be done as root. Also the only difference between ifconfig >> > eth0 and ifconfig is that the ifconfig without the argument allows >> > debian to show you which interfaces if any are working. It is quite >> > possible that your setup is working but under a different interface >> > than eth0. >> > >> > -- >> > Cheryl >> > >> > "Move forward by looking back! >> > "Above all, fear the Lord >> > and worship Him faithfully with all your heart; >> > consider the great things He has done for you." >> > (1 Samuel 12:24 (HCSB) >> > >> > >> > >> > >> > >> > On Jan 28, 2015, at 10:34 AM, Karen Lewellen >> > <klewellen@shellworld.net> wrote: >> > >> > I believe I have made it very clear how much experimentation is >> > possible in prior discussions. >> > I followed Tim's directions, there are the results. >> > Karen >> > >> > >> > On Wed, 28 Jan 2015, Willem van der Walt wrote: >> > >> > > Hi, >> > > As root, do: >> > > ifconfig and check which interfaces show up. Your ethernet might be >> > > picked up as another interface, e.g. eth1. >> > > You should simply first test by pinging your router. >> > > HTH, Willem >> > > >> > > >> > > On Tue, 27 Jan 2015, Karen Lewellen wrote: >> > > >> > > > Hi all, >> > > > here is what happened when seeking the ip address. >> > > > Let me explain how I set up the machine. >> > > > before even booting I put the dsl cable I am using now to send >> > > > this message into the linux box, keeping it connected to my >> > > > modem/rooter as usual. >> > > > Because we were pressed for time, after letting speakup start, >> > > > and entering my username, Karen, and my password, I simply used >> > > > the print screen key to silence speakup. >> > > > the error message we got is below. >> > > > I saw karen@suburst:~s and there was no other place to type so >> > > > after karen@sunburst:~s I typed /sbin/ifconfig eth0 as instructed >> > > > the message we got was: eth0: error fetching interface >> > > > information: Device not Found >> > > > >> > > > We tried the step more than once to be sure. >> > > > let me add that typing shutdown -h also produced an error, so I >> > > > simply turned off the machine after restoring speakup. >> > > > The Ethernet card was in the computer before the hard drive >> > > > containing Debian was installed, so was the rest of the hardware >> > > > Linux identified. >> > > > thoughts? >> > > > Karen >> > > > >> > > > _______________________________________________ >> > > > Blinux-list mailing list >> > > > Blinux-list@redhat.com >> > > > https://www.redhat.com/mailman/listinfo/blinux-list >> > > > >> > > > -- >> > > > This message is subject to the CSIR's copyright terms and >> > > > conditions, >> > > > e-mail legal notice, and implemented Open Document Format (ODF) >> > > > standard. >> > > > The full disclaimer details can be found at >> > > > http://www.csir.co.za/disclaimer.html. >> > > > >> > > > This message has been scanned for viruses and dangerous content by >> > > > MailScanner, and is believed to be clean. >> > > > >> > > > Please consider the environment before printing this email. >> > > >> > > _______________________________________________ >> > > Blinux-list mailing list >> > > Blinux-list@redhat.com >> > > https://www.redhat.com/mailman/listinfo/blinux-list >> > > >> > > >> > > >> > >> > _______________________________________________ >> > Blinux-list mailing list >> > Blinux-list@redhat.com >> > https://www.redhat.com/mailman/listinfo/blinux-list >> > >> > >> > _______________________________________________ >> > Blinux-list mailing list >> > Blinux-list@redhat.com >> > https://www.redhat.com/mailman/listinfo/blinux-list >> > >> > >> >> _______________________________________________ >> Blinux-list mailing list >> Blinux-list@redhat.com >> https://www.redhat.com/mailman/listinfo/blinux-list > > -- > Christopher (CJ) > chaltain at Gmail > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Cheryl Homiak ` Karen Lewellen @ ` Geoff Shang 1 sibling, 0 replies; 11+ messages in thread From: Geoff Shang @ UTC (permalink / raw) To: Linux for blind general discussion On Wed, 28 Jan 2015, Cheryl Homiak wrote: > Actually, the suggestions don't require any more experimentation than what you did. But the command you did as a regular user really does have to be done as root. You can run ifconfig as a user, you just can't use it to actually do network configuration and you will need to specify the path as sbin is not normally in a user's path. This is what Karen did. Geoff. ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. results of my try Karen Lewellen ` Cheryl Homiak ` Willem van der Walt @ ` Tim Chase ` Karen Lewellen 2 siblings, 1 reply; 11+ messages in thread From: Tim Chase @ UTC (permalink / raw) To: blinux-list On January 27, 2015, Karen Lewellen wrote: > I typed /sbin/ifconfig eth0 as instructed the message we got was: > eth0: error fetching interface information: Device not Found That's very strange. It's almost as if it can't find the network card. A couple possibilities occur to me: 1) the network card got unseated and just needs to be firmly pushed back into its socket (this might happen if it was a PCI/ISA card and it came loose during shipment). If it's built into the motherboard as many are now, that's not really a consideration. An easy way to test/check would just be to jiggle the location where the network cable goes into the PC and if it feels loose, re-seat it (or have someone pop the case and do it for you). 2) the network card is physically attached, but it's an unsupported card. This is pretty rare as Linux tends to have excellent support for all manner of networking hardware from ancient to bleeding-edge. This may be the hardest to track down. Saving the output from "lspci" might help indicate whether it's even showing up on the PCI bus. 3) the network card might be disabled in the BIOS. Unfortunately, on most PCs, the BIOS is inaccessible, so you'd have to get some sighted help to determine what the magic key is upon startup that lets you into the BIOS configuration. Just on the handful of computers I've got here, it's "escape" on one, "F2" on another, and "0" on yet another. When the machine is first powered-on, it usually flashes a "press {some key} to enter setup" message. Then your extra eyes would have to poke around for something that would read like "disable/enable internal NIC" and make sure that it's not disabled. 4) There's a freak possibility that the ethernet card(s) failed to start at "0" when numbering. If that's the case, you can remove the "eth0" from the original command that I gave you to check the output of /sbin/ifconfig | grep -i '^[a-z]' which should list all the known network adapters that it can see. > let me add that typing shutdown -h also produced an error, Most systems require root privileges to shut down, so you might have had to use either "sudo shutdown -h", "sudo halt", or "su -l -c halt" to do so. That said... > so I simply turned off the machine after restoring speakup. as discussed in the previous thread, this shouldn't harm anything. So unfortunately, diagnosing hardware (particularly BIOS) issues may require additional sighted assistance. But, it sounds like there's no major rush. -tim ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: results of my try. ` Tim Chase @ ` Karen Lewellen 0 siblings, 0 replies; 11+ messages in thread From: Karen Lewellen @ UTC (permalink / raw) To: Linux for blind general discussion Tim, You skipped the obvious and most likely. that the person who installed debian on this drive left out the network option all together. First, as I have been working with computers since 1988, I know that it is best to be certain a card is not loose before testing. that is why I used my own regular Ethernet cable, giving me a chance to check the card. This machine was not shipped anywhere by anyone. Instead, it was built by the electrical engineer friend of mine who maintains my main computers. The person who did this install considered themselves solid in debian and speech, put the console structure on a hard drive complete with root and user passwords, and shipped it to me here from Florida. i assure you that my computer builder here, as a former IBM employee, and a present one of motherboard manufacture amd, knows how to configure an Ethernet card. Lord if we can configure USB for dos printing and external drives, a bios is child's play. Equally it would be almost impossible for Linux not to have a driver for this card, it found everything else in the box when the drive was installed, even the modem shows up. Additionally, I suspect the card is a name brand, so it likely starts as your command indicates. You may not have noticed the comments from others about the odd nature of the bash line presented. As I have said many many times, I have little direct knowledge of Linux. I prefer the efficiency of in person training and installations, not materializing here in Toronto. Still even I was surprised when my associate shared the line she was getting, the one with my name. Granted freebds clearly works more efficiently then Debian, even Ubintu, in my personal experience, but that does not look like any bash line I have ever encountered. As for no rush, perhaps. The only motivation I have for creating a ssh TELNET door into that box is to run a very few programs music wise that I cannot find yet in DOS. Still if I did not consider that composition project to be critical, I would not have tested the Linux box for ssh TELNET whatsoever. Given this install of Debian has issues, and I have not located first hand debian wisdom I may just dump the present install totally. the hardware in this box is of too good a quality to be wasted with a poorly configured structure. If I can find an edition of AbC Notation for Dos, to go with some recent dos music programs, then I will just replace debian with a real, for me at least, operating system. I still think trying freebds might have been fun, but there is no compile that I can find of the software I am interested in running for music work in freebds. If I have no other real composition options but Linux, then I will try one possible door. Toronto has a 2600.org chapter. The uniqueness might interest someone there, or I can dump what is here and participate with help in installing just enough Linux for my needs. Thanks for checking in, frankly, I have serious doubts about how the install was done, but getting forthright information is far from forth coming on the debian main list. I do appreciate what this person tried to do. My own install efforts on yet another computer were totally disastrous, fortifying my desire for in person help only. Still I am not the tinker type. I respect that such things interest others, but I have businesses to run, and music to render into copyright ready form. Kare On Wed, 28 Jan 2015, Tim Chase wrote: > On January 27, 2015, Karen Lewellen wrote: >> I typed /sbin/ifconfig eth0 as instructed the message we got was: >> eth0: error fetching interface information: Device not Found > > That's very strange. It's almost as if it can't find the network > card. A couple possibilities occur to me: > > 1) the network card got unseated and just needs to be firmly pushed > back into its socket (this might happen if it was a PCI/ISA card and > it came loose during shipment). If it's built into the motherboard > as many are now, that's not really a consideration. An easy way to > test/check would just be to jiggle the location where the network > cable goes into the PC and if it feels loose, re-seat it (or have > someone pop the case and do it for you). > > 2) the network card is physically attached, but it's an unsupported > card. This is pretty rare as Linux tends to have excellent support > for all manner of networking hardware from ancient to bleeding-edge. > This may be the hardest to track down. Saving the output from > "lspci" might help indicate whether it's even showing up on the PCI > bus. > > 3) the network card might be disabled in the BIOS. Unfortunately, on > most PCs, the BIOS is inaccessible, so you'd have to get some sighted > help to determine what the magic key is upon startup that lets you > into the BIOS configuration. Just on the handful of computers I've > got here, it's "escape" on one, "F2" on another, and "0" on yet > another. When the machine is first powered-on, it usually flashes a > "press {some key} to enter setup" message. Then your extra eyes > would have to poke around for something that would read like > "disable/enable internal NIC" and make sure that it's not disabled. > > 4) There's a freak possibility that the ethernet card(s) failed to > start at "0" when numbering. If that's the case, you can remove > the "eth0" from the original command that I gave you to check the > output of > > /sbin/ifconfig | grep -i '^[a-z]' > > which should list all the known network adapters that it can see. > >> let me add that typing shutdown -h also produced an error, > > Most systems require root privileges to shut down, so you might have > had to use either "sudo shutdown -h", "sudo halt", or "su -l -c halt" > to do so. That said... > >> so I simply turned off the machine after restoring speakup. > > as discussed in the previous thread, this shouldn't harm anything. > > So unfortunately, diagnosing hardware (particularly BIOS) issues may > require additional sighted assistance. But, it sounds like there's no > major rush. > > -tim > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > > ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
results of my try Karen Lewellen
` Cheryl Homiak
` Willem van der Walt
` Karen Lewellen
` Cheryl Homiak
` Karen Lewellen
` Christopher Chaltain
` Karen Lewellen
` Geoff Shang
` Tim Chase
` Karen Lewellen
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).