I saw many postings on the listserver regarding Xwindows
resolution problems and lockage.
I myselft have been having the same problem:
-> When booting, the nice boot screen (fram buffer) is jittery
and only displays on half the page.
-> When the system boots and I choose to "log out" of gnome or
kde desktop, the OS locks and the screen keeps getting brighter.
The thing to do at this point is either rip the batter out or
hold the power button down for a while to cycle the system.
Last night I have found a fix/workaround that seems to be
working to fix both problem above.
First you need to know the correct resolution your laptop screen
was built for. For example, my Dell Inspiron is meant to do
1400x1050 . In my xorg.conf file I noticed that it had only
1024x768, 800x600, 640x480 as the resolutions. So I added
1400x1050 as the default. I was then able to view the screen at
the correct resolution, but still had lockage.
So, I removed all resolution settings and only kept the
1400x1050. Now the boot screen looks perfect and no lockage
when logging out.
From my work, it seems that when you log out of a desktop, Xorg
tries to cycle/test the different resolutions and that is what
locks the system up. Also I found other listings regarding
DDC/laptop issues. I don't know much about the DDC stuff (only
that some laptops support it and some dont), so if anyone else
can maybe think why this is and explain it to the rest of us.
By only having one resolution setting, it does not try others.
Works for me. Now I can use the system without cursing it.
Hope this helps.
To all that contributed to Fedora and Linux in general; Great
Director Services - The NewMedia Group
Montana Tech Blackboard Administrator
As with Test 2, the install CD boots fine in VirtualPC 6 and installs.
Once it has installed, it gets as far as saying Ok, booting the kernel
before crashing. Can anyone suggest what might be different between
the kernel used by the installer, and the one that is installed that
might cause this (and ideally how to disable whatever it is)?
P.S. Core 1 runs fine in VirtualPC.
The Adaptec 2100S RAID card was supported inherantly in FC1.
FC2T3 does not seem to detect it. It does probe and load the I2O_block and
I2O_core modules, but the installer fails saying it cannot find a hard
Can anyone shed some light on this? I read a thread in the archives anout
Adaptec Hostraid that basically said Adaptec RAID support has always been
iffy, but I haven't had any problems with this card till now. It works in
RH7.2, 7.3, 8, 9, FC1.
Yesterday I was complaining about missing RPMs and the fact that
the update icon, and up2date were out of sync., so today I thought I'd
look at it some more.
Today, my icon still says there are 2 RPMs to upgrade, but up2date
says that only one is available. But up2date hangs while trying
to resolve dependencies.
So I went back to using yum.
Yum told me that there are two other RPMs (gaim and rpmdb-fedora)
that needed updating, and that there were problems with perl-XML-Twig
that needs XML::Path, which is not found.
So again I told it to ignore perl-XML-Twig, and yum installed gaim
and rpmdb-fedora. But alas the icon and up2date are still as
confused as ever.
Looking at the alert notification tool I see that it says:
Package Version Installed Version Available
perl-Net-DNS perl-Net-DNS-0.31.3.2 perl-Net-DNS-0.45-2
perl-XML-Twig perl-XML-Twig-3.09-3 perl-XML-Twig-3.13-4
OK, I need perl-XML-Twig-3.13-4. So I manually look at the mirror
and the only version of perl-XML-Twig it has is 3.09-3 and
the same goes for perl-Net-DNS (only the old version).
Now i look in the mirrors header directory, and they don't have the
new version either. But at some time, my system did fetch that header
and now it thinks that's what it needs.
Did someone release new versions of the headers, without the RPMs,
(that my machine sucked)... and then pulled back the new headers, (causing
my machine to get into a mode)?
1/ If so, why?
2/ And how do I get my machine to forget about the headers that point to
Go to icecast.org
Select Ogg stream
Opens in "Music Player".
I get "Error: Could not pause playback"
Anyone else getting this?
Maybe I'll try xmms instead.
Will Backman <whb(a)ceimaine.org>
Coastal Enterprises, Inc.
This has been since Test 1 and yet, no one has fixed
this problem. Now it's Test 3 and this problem still
persist. I want to be heard! So I launch
gnome-sound-recorder to make sure that the people may
hear my mindless rantings, but wait...once I press the
record button the program just crashes! Oh who will
hear me now!
Upgraded and rebooted into the 2.6.5-1.327 kernel and lost all sound.
Booted back into 2.6.3-184.108.40.206.1 and BAM! crystal clear sound. All
necessary AlSA packages are installed (I assume since it works in the
previous kernel). Has the sound device changed (is /dev/dsp in
Running on a Dell Latitude C600.
Musa Williams Systems Engineer
NCR e-Commerce Solutions
work - 410.953.7783
cell - 410.624.6436
email - mw180013(a)ncr.com
Is there going to be support for the 3114 chipset in FC2? I have read that
libata supports it but needs to be patched on to the kernel tree?
This mail sent using V-webmail - http://www.v-webmail.org
I just managed to install FC2 Test 3 on a PC with a Logitech optical mouse,
PS/2, OEM version.
During the install process, the pointer acted weirdly (random movements,
buttons not functioning properly), being unuseable... I had to use the
keyboard in anaconda in order to install FC2.
The same problem presented after the reboot... I tried several other mouse
drivers in X (not only the IMPS/2 one) with no success.
There does not seem to be many options for creating boot disks in the
images directory of FC2-test3
I want to do a net install by booting off a floppy. Will these be
available in the final release. I find them quite valuable as I normally
just keep an image of the RPMS directory on a server.
Focus Computer Consulting