No more Fedora 13 on Toshiba laptop!

[Anne Wilson]

Without any warning or obvious reason, Fedora has ceased to function.  I 
cannot get any graphical login.  kdm.log has huge numbers of lines like

intel_bufmgr_gem.c:1043:Error mapping buffer 40639 (pixmap): Cannot allocate 
memory
intel_bufmgr_gem.c:962:Error mapping buffer 40968 (surface_state)): Cannot 
allocate memory.

messages contains the line "kdm: :0[2287]: Fatal X server IO error: 
interrupted system call.

I checked that the last kernel is also affected, and tried xfce, which has the 
same result as a kde session.

I did install some packages a couple of days earlier, but I've been away from 
the internet for several days, so there was nothing newly installed when this 
happened.  Googling didn't show me anything helpful.  Any ideas?  I'll tinker 
with the system rescue from the DVD this afternoon - of course I didn't have 
it with me when all this happened.

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org

[Frank Thieme]

Hi!


On Saturday 21 August 2010 17:20:09 Anne Wilson wrote:
>  intel_bufmgr_gem.c:1043:Error mapping buffer 40639 (pixmap): Cannot
>  allocate memory
>  intel_bufmgr_gem.c:962:Error mapping buffer 40968 (surface_state)): Cannot
>  allocate memory. 
Maybe a memory defect? Try memtest86+

Bye...Frank

[Anne Wilson]

On Saturday 21 August 2010 15:47:52 Frank Thieme wrote:
>  Hi!
>  
>  On Saturday 21 August 2010 17:20:09 Anne Wilson wrote:
>  > intel_bufmgr_gem.c:1043:Error mapping buffer 40639 (pixmap): Cannot
>  > allocate memory
>  > intel_bufmgr_gem.c:962:Error mapping buffer 40968 (surface_state)):
>  > Cannot allocate memory.
>  
>  Maybe a memory defect? Try memtest86+
>   
I don't think so.  I've run memtest86+ for over 13 hours without finding
any 
problems.

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org

[Chris Smart]

2010/8/22 Anne Wilson <cannewilson(a)googlemail.com&gt;:
>  Without any warning or obvious reason, Fedora has ceased to function.
>  I
>  cannot get any graphical login.  kdm.log has huge numbers of lines like
>  
Boot to recovery mode/single user mode/runlevel 3 and create an X.org
config file that uses vesa driver (i.e. run 'X -configure' and move
that file to /etc/X11/xorg.conf and edit it to make sure Video card
section driver is set to "vesa"). Then boot to runlevel 5 (init 5) and
see if it works.

-c

[Anne Wilson]

On Sunday 22 August 2010 13:24:49 Chris Smart wrote:
>  2010/8/22 Anne Wilson <cannewilson(a)googlemail.com&gt;:
>  > Without any warning or obvious reason, Fedora has ceased to function.  I
>  > cannot get any graphical login.  kdm.log has huge numbers of lines like
>  
>  Boot to recovery mode/single user mode/runlevel 3 and create an X.org
>  config file that uses vesa driver (i.e. run 'X -configure' and move
>  that file to /etc/X11/xorg.conf and edit it to make sure Video card
>  section driver is set to "vesa"). Then boot to runlevel 5 (init 5) and
>  see if it works.
>   
Good idea.  Pity it didn't work.  Running X -configure xorg.conf.new gave me a

black screen.  Booting into run level 5 gave me a blue screen with dashes 
across it.  Attempting to boot back into a run level 1 to get rid of it gave 
me a black screen with the fan running like mad.  I don't seem to have any way 
of getting in now.

Unfortunately, on this occasion I had installed from the Live CD.  I don't 
have the DVD though I do have an F12 one.  Hopefully that will allow me to use 
rescue mode to delete xorg.conf

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org

[Chris Smart]

2010/8/23 Anne Wilson <cannewilson(a)googlemail.com&gt;:
> >
>  Good idea.  Pity it didn't work.  Running X -configure xorg.conf.new gave me a
>  black screen.  Booting into run level 5 gave me a blue screen with dashes
>  across it.  Attempting to boot back into a run level 1 to get rid of it gave
>  me a black screen with the fan running like mad.  I don't seem to have any way
>  of getting in now.
>  
Try this:
When you boot your computer after POST, continually press the esc key
every half second until you get the GRUB boot menu.
With the top entry highlighted, press the "e" key to edit the line.
Select the kernel line and hit "e" again.

At the end of the kernel line, remove any of the words like "splash",
"quiet", "rhgb" - and *add* the words, "single nomodeset" -
then hit
the enter key and then "b" to boot it.

Does that work? If so, try running "X -configure" from here and see if it
works.

-c

[Kevin Kofler]

Chris Smart wrote:
>  At the end of the kernel line, remove any of the words like
> "splash",
>  "quiet", "rhgb" - and *add* the words, "single nomodeset" -
> then hit
>  the enter key and then "b" to boot it. 
I'd try "3" instead of "single". That's the normal text mode
runlevel, which 
should be enough to debug X.Org X11 problems while booting into a more 
usable system than single-user mode.

        Kevin Kofler

[Anne Wilson]

On Monday 23 Aug 2010 07:04:22 Kevin Kofler wrote:
>  Chris Smart wrote:
>  > At the end of the kernel line, remove any of the words like "splash",
>  > "quiet", "rhgb" - and *add* the words, "single
> nomodeset" - then hit
>  > the enter key and then "b" to boot it.
>  
>  I'd try "3" instead of "single". That's the normal text mode
> runlevel,
>  which should be enough to debug X.Org X11 problems while booting into a
>  more usable system than single-user mode.
>   
Thanks, both of you, for trying to help.  I've tried all the things suggested,

and had no success.  In the end I gave in and installed OpenSUSE on this 
laptop.  Fedora has simply never been happy with it.  I suspect it's the Intel 
video that it doesn't like, but I've had endless problems since I bought it.  
We'll see whether OpenSUSE handles it any better.  Meanwhile, I still have 
Fedora 13 on the other laptop which also gets regular use.

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org