Everyone, Thank you for your help and suggestions. I was able to add rootdelay=5 to the kernel line and this resolved the issue for me.
Sincerely. Shane On Mon, Sep 30, 2013 at 8:51 AM, Chris Bannister <cbannis...@slingshot.co.nz> wrote: > On Mon, Sep 30, 2013 at 05:16:38PM +0300, Georgi Naplatanov wrote: >> I had impression that 'rootdelay=5' had solved your problem and that >> is why I gave you that link. > > If you read the thread, you will see it was not me. Also note, it was > another poster (Hugo) who suggested that the OP try 'rootdelay=5' to see > if it helped. > >> To your question - if 'rootdelay=5' solves your problem then it's a >> known problem. > > Incorrect. A known problem is one that is explicitly documented for that > specific version of software. > > I can see that language barriers may confuse the meaning of words. > > Think of the well known ports 1-1024 as an example of the use of > the word "known". It is the same usage in regards to a known bug. > > -- > "If you're not careful, the newspapers will have you hating the people > who are being oppressed, and loving the people who are doing the > oppressing." --- Malcolm X > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/20130930145059.GA25109@tal > -- Shane D. Johnson IT Administrator Rasmussen Equipment -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caplo1l54pyo8avs3gnddw4yusukftsecm6q4d6sq15bk3zb...@mail.gmail.com
