Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.misc > #14788 > unrolled thread

fedora 20 installing

Back to article view | Back to comp.os.linux.misc

Contents

  fedora 20 installing "Bill Cunningham" <nospam@nspam.invalid> - 2015-05-14 18:53 -0400
    Re: fedora 20 installing Dan Espen <despen@verizon.net> - 2015-05-14 20:00 -0400
      Re: fedora 20 installing "Bill Cunningham" <nospam@nspam.invalid> - 2015-05-14 20:03 -0400
      Re: fedora 20 installing "Bill Cunningham" <nospam@nspam.invalid> - 2015-05-14 20:04 -0400
    Re: fedora 20 installing Andreas Kohlbach <may15.7.ankman@spamgourmet.net> - 2015-05-15 16:18 -0400
      Re: fedora 20 installing "Bill Cunningham" <nospam@nspam.invalid> - 2015-05-16 14:34 -0400
        Re: fedora 20 installing Andreas Kohlbach <may15.7.ankman@spamgourmet.net> - 2015-05-16 15:45 -0400
          Re: fedora 20 installing "Bill Cunningham" <nospam@nspam.invalid> - 2015-05-17 12:00 -0400
            Re: fedora 20 installing "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-05-17 12:29 -0400
              Re: fedora 20 installing "Bill Cunningham" <nospam@nspam.invalid> - 2015-05-17 12:55 -0400

#14788 — fedora 20 installing

    I don't know if anyone has run into this problem or not. I am still 
using f20 haven't went to f21 yet. When I install the netinstall which has 
never given me problems before. Well as soon as it starts to boot my monitor 
goes blank. There must be some kind of resolution issue here. I tried 
installing at a lower resolution and everything installed well but I can't 
see everything. My monitor is 1024x768. It will not accept that resolution 
anymore.

    A lower res will install but I can't see anything. I tried resetting the 
monitor and this still happens. Anyone have any idea what's going on?

Bill

[toc] | [next] | [standalone]

#14789

"Bill Cunningham" <nospam@nspam.invalid> writes:

>     I don't know if anyone has run into this problem or not. I am still 
> using f20 haven't went to f21 yet. When I install the netinstall which has 
> never given me problems before. Well as soon as it starts to boot my monitor 
> goes blank. There must be some kind of resolution issue here. I tried 
> installing at a lower resolution and everything installed well but I can't 
> see everything. My monitor is 1024x768. It will not accept that resolution 
> anymore.
>
>     A lower res will install but I can't see anything. I tried resetting the 
> monitor and this still happens. Anyone have any idea what's going on?

What kind of video card?
The nv drivers once gave me that symptom.
Couldn't get anywhere without the Nvidia drivers.

Now I'm on FC21 and Nouveau is working reasonably well.

-- 
Dan Espen

[toc] | [prev] | [next] | [standalone]

#14790

"Dan Espen" <despen@verizon.net> wrote in message 
news:mj3csi$h76$1@dont-email.me...
> "Bill Cunningham" <nospam@nspam.invalid> writes:
>
>>     I don't know if anyone has run into this problem or not. I am still
>> using f20 haven't went to f21 yet. When I install the netinstall which 
>> has
>> never given me problems before. Well as soon as it starts to boot my 
>> monitor
>> goes blank. There must be some kind of resolution issue here. I tried
>> installing at a lower resolution and everything installed well but I 
>> can't
>> see everything. My monitor is 1024x768. It will not accept that 
>> resolution
>> anymore.
>>
>>     A lower res will install but I can't see anything. I tried resetting 
>> the
>> monitor and this still happens. Anyone have any idea what's going on?
>
> What kind of video card?
> The nv drivers once gave me that symptom.
> Couldn't get anywhere without the Nvidia drivers.
>
> Now I'm on FC21 and Nouveau is working reasonably well.

    ATI Radeon Xpress 200. Of course I think that's AMD that owns ATI now.

Bill

[toc] | [prev] | [next] | [standalone]

#14791

"Dan Espen" <despen@verizon.net> wrote in message 
news:mj3csi$h76$1@dont-email.me...
> "Bill Cunningham" <nospam@nspam.invalid> writes:
>
>>     I don't know if anyone has run into this problem or not. I am still
>> using f20 haven't went to f21 yet. When I install the netinstall which 
>> has
>> never given me problems before. Well as soon as it starts to boot my 
>> monitor
>> goes blank. There must be some kind of resolution issue here. I tried
>> installing at a lower resolution and everything installed well but I 
>> can't
>> see everything. My monitor is 1024x768. It will not accept that 
>> resolution
>> anymore.
>>
>>     A lower res will install but I can't see anything. I tried resetting 
>> the
>> monitor and this still happens. Anyone have any idea what's going on?
>
> What kind of video card?
> The nv drivers once gave me that symptom.
> Couldn't get anywhere without the Nvidia drivers.
>
> Now I'm on FC21 and Nouveau is working reasonably well.

    Its always worked until now.

Bill

[toc] | [prev] | [next] | [standalone]

#14792

Bill Cunningham wrote on 14. May 2015:
>
>     I don't know if anyone has run into this problem or not. I am still 
> using f20 haven't went to f21 yet. When I install the netinstall which has 
> never given me problems before. Well as soon as it starts to boot my monitor 
> goes blank. There must be some kind of resolution issue here. I tried 
> installing at a lower resolution and everything installed well but I can't 
> see everything. My monitor is 1024x768. It will not accept that resolution 
> anymore.
>
>     A lower res will install but I can't see anything. I tried resetting the 
> monitor and this still happens. Anyone have any idea what's going on?

Can you boot into safe mode? If you can call xrandr which lists you
available resolutions, and the one currently set labeled with an *. Since
you are in safe-mode it might not list all (higher) available resolutions.

Or press CTRL-ALT-F1 if safe-mode isn't working either. You might be able
to get a login prompt. Login in with your root password because you might
need to change things on the system.

Open /var/log/Xorg.0.log and go all to the end, and slowly scroll up,
until you might see the cause of the crash (if X crashed at all). Often a
viewer called "less" is installed you can use to open /var/log/Xorg.0.log
with.

In case you are also online already (just without a working X), and have
a text browser installed, like Lynx, links or w3m. You could then try to
find a solution doing a web search for what ever the Xorg log complaints
about.
-- 
Andreas

I use a Unix based operating system, which means I get laid almost as often
as I have to reboot my computer.

[toc] | [prev] | [next] | [standalone]

#14794

"Andreas Kohlbach" <may15.7.ankman@spamgourmet.net> wrote in message 
news:874mndzjb6.fsf@usenet.ankman.de...
> Bill Cunningham wrote on 14. May 2015:
>>
>>     I don't know if anyone has run into this problem or not. I am still
>> using f20 haven't went to f21 yet. When I install the netinstall which 
>> has
>> never given me problems before. Well as soon as it starts to boot my 
>> monitor
>> goes blank. There must be some kind of resolution issue here. I tried
>> installing at a lower resolution and everything installed well but I 
>> can't
>> see everything. My monitor is 1024x768. It will not accept that 
>> resolution
>> anymore.
>>
>>     A lower res will install but I can't see anything. I tried resetting 
>> the
>> monitor and this still happens. Anyone have any idea what's going on?
>
> Can you boot into safe mode? If you can call xrandr which lists you
> available resolutions, and the one currently set labeled with an *. Since
> you are in safe-mode it might not list all (higher) available resolutions.
>
> Or press CTRL-ALT-F1 if safe-mode isn't working either. You might be able
> to get a login prompt. Login in with your root password because you might
> need to change things on the system.
>
> Open /var/log/Xorg.0.log and go all to the end, and slowly scroll up,
> until you might see the cause of the crash (if X crashed at all). Often a
> viewer called "less" is installed you can use to open /var/log/Xorg.0.log
> with.
>
> In case you are also online already (just without a working X), and have
> a text browser installed, like Lynx, links or w3m. You could then try to
> find a solution doing a web search for what ever the Xorg log complaints
> about.

    Well I just zero'd out my mbr and reinstalled. I get tired of trying to 
figure every little thing for this.

    It seems to be working now. If a fresh install doesn't do it. You are in 
a bad situation. It seems to have worked this time though.

Bill

[toc] | [prev] | [next] | [standalone]

#14795

Bill Cunningham wrote on 16. May 2015:
>
> "Andreas Kohlbach" <may15.7.ankman@spamgourmet.net> wrote in message 
> news:874mndzjb6.fsf@usenet.ankman.de...
>>
>> Can you boot into safe mode? If you can call xrandr which lists you
>> available resolutions, and the one currently set labeled with an *. Since
>> you are in safe-mode it might not list all (higher) available resolutions.
>>
>> Or press CTRL-ALT-F1 if safe-mode isn't working either. You might be able
>> to get a login prompt. Login in with your root password because you might
>> need to change things on the system.
>>
>> Open /var/log/Xorg.0.log and go all to the end, and slowly scroll up,
>> until you might see the cause of the crash (if X crashed at all). Often a
>> viewer called "less" is installed you can use to open /var/log/Xorg.0.log
>> with.
>>
>> In case you are also online already (just without a working X), and have
>> a text browser installed, like Lynx, links or w3m. You could then try to
>> find a solution doing a web search for what ever the Xorg log complaints
>> about.
>
>     Well I just zero'd out my mbr and reinstalled. I get tired of trying to 
> figure every little thing for this.

That is the Windows method.

>     It seems to be working now. If a fresh install doesn't do it. You are in 
> a bad situation. It seems to have worked this time though.

If Linux might have a problem there to identify the hardware it might
just happen again in the future. But reading logs and then trying to
solve problems doing a web search or asking here can solve almost any
Linux related problem in future.
-- 
Andreas

I use a Unix based operating system, which means I get laid almost as often
as I have to reboot my computer.

[toc] | [prev] | [next] | [standalone]

#14796

"Andreas Kohlbach" <may15.7.ankman@spamgourmet.net> wrote in message 
news:87egmgl30w.fsf@usenet.ankman.de...

> If Linux might have a problem there to identify the hardware it might
> just happen again in the future. But reading logs and then trying to
> solve problems doing a web search or asking here can solve almost any
> Linux related problem in future.

    The thing is something really odd happened the other day and it never 
happened before. I used the rebuilddb switch to rpm. and makecache to yum. 
It seemed like *every* mirror was down. Things were pathetically slow. I had 
to install all new upgrade rpms. A new kernel rpm it was like support for 
f20 had ended. Since it's not happened again.

    I might look at f21 soon.

Bill

[toc] | [prev] | [next] | [standalone]

#14797

On Sun, 17 May 2015 12:00:04 -0400, Bill Cunningham <nospam@nspam.invalid> wrote:

>     The thing is something really odd happened the other day and it never
> happened before. I used the rebuilddb switch to rpm. and makecache to yum.
> It seemed like *every* mirror was down. Things were pathetically slow. I had
> to install all new upgrade rpms. A new kernel rpm it was like support for
> f20 had ended. Since it's not happened again.
>
>     I might look at f21 soon.

Just fyi. The server used for mageia.org had problems with network
connections for at least an hour earlier today. The servers were
working, but the network was getting 95% packet loss. It's now
working again. With the internet, stuff happens.

Regards, Dave Hodgins

-- 
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

[toc] | [prev] | [next] | [standalone]

#14798

"David W. Hodgins" <dwhodgins@nomail.afraid.org> wrote in message 
news:op.xysf29xha3w0dxdave@hodgins.homeip.net...

> Just fyi. The server used for mageia.org had problems with network
> connections for at least an hour earlier today. The servers were
> working, but the network was getting 95% packet loss. It's now
> working again. With the internet, stuff happens.
>
> Regards, Dave Hodgins

    Interesting. Vint Cerf told me about a nice little website to look at 
for packet loss. From what I can understand of it it shows latency, loss, 
and packets that are getting through on higher tiers of the backbone.

    www.internetpulse.net

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.misc

csiph-web