As Red Skeleton was known to say, "I just do them, I don't explain
them". I have noticed more than once that x freezes if I am playing
freecell while running "sudo yum update" from a gnome terminal. I have
not had X freeze in any other scenario. The symptoms of the freeze are:
1. yum is downloading at the time
2. It happens while I am dragging a card - the motion freezesa
3. The mouse still moves but none of the rollovers do anything and
clicking doesn't have any effect
4. The keyboard doesn't have any effect. Not even ctrl-alt-del,
ctrl-alt-f2, or ctrl-alt-backspace
5. The gnome monitor panel applet freezes
6. ssh works. I can log in from another machine
7. /sbin/init 3 doesn't do anything
I am running F10 rawhide on a Dell Latitude D620 - integrated Intel
I am attempting to test the sisusb support under Snap3 on the XO
laptop. This should allow the use of a USB VGA adapter so that an
external monitor/projector can be used on the XO. I have successfully
done this with Ubuntu on the XO, and it seems to work fine under Sugar
(the system that comes with the XO) as well (see
<http://wiki.laptop.org/go/Remote_Display> for details). However, I
have been unable to do this under Fedora.
My approach has been to boot up the machine with Snap3, modify
xorg.conf, plug in the usb vga adapter (GXT USB 2.0 To VGA Adapter
and then reset X (ctrl-alt-backspace). When I do this I get a blank
screen on both displays (the LCD and the VGA adapter) with a repeating
flicker every few seconds as if they are changing display modes. The
LCD seems to be alternating between a text mode and a graphics mode,
since there is a visible blinking cursor half the time (exactly like a
My best guess is there is some sort of initialization failure
happening, and it keeps retrying. If I unplug the USB VGA adapter
while this is occurring, it stops flickering and successfully starts X
(but without the second screen, of course).
Here is what I added to xorg.conf:
I also added this to the ServerLayout:
Screen 1 "Screen1" 0 0
The last bit of Xorg.0.log looks like this:
(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(--) RandR disabled
(II) SISUSB(1): Setting standard mode 0x4a
(II) SISUSB(1): Framebuffer from (0,0) to (1023,7902)
(==) SISUSB(1): Backing store disabled
(**) Option "dpms"
(**) SISUSB(1): DPMS enabled
(II) SISUSB(1): Initialized SISCTRL extension version 0.1
(II) SISUSB(1): Registered screen 1 with SISCTRL extension version 0.1
(--) RandR disabled
0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812b8db]
1: /usr/bin/Xorg(xf86SigHandler+0x51) [0x80bc911]
3: /usr/bin/Xorg(xf86EnterServerState+0x54d) [0x80b14ad]
4: /usr/bin/Xorg(xf86PostScreenInit+0x213) [0x80b2b53]
5: /usr/bin/Xorg(InitOutput+0x335) [0x80a3d65]
6: /usr/bin/Xorg(main+0x279) [0x806b4e9]
7: /lib/libc.so.6(__libc_start_main+0xe5) [0x42e6d5]
8: /usr/bin/Xorg [0x806aad1]
Fatal server error:
Caught signal 11. Server aborting
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
Does anyone have any suggestions as to what else I can try for this?
When I installed F9 from the liveCD I decided to use the
EXT4 file system. Unfortunately, there was no way to boot
from my ext3 mbr. It kept hanging when it went to the boot
partition. I tried some playing around but didn't get it to
work. I ended up using preupgrade, which worked flawlessly
but left me in ext3.
When F10 is available I would like to run it in an ext4
filesystem. Will this incompatibility between ext3 and ext4
still be a problem? F10 will not be installed on the same
disk as the mbr is on. If it is a problem, is there a
Just in case, will preupgrade work for F10?
I rebooted this morning after pulling in some changes from last night (a mix of rawhide and koji updates) and my system was not booting.
I so far have noticed that the /dev/mapper/luks-8 naming format has changed and I think that is relating to my problems. I haven't gotten
things totally fixed, but i now have my file systems mount under /mnt/sysimage when rebooting. Hopefully now that the /dev directory is
there a new mkinitrd will clean things up.
I think using the luks ids in the names is a good idea, but it would have been nice to have something automatically handle the transition.
I haven't seen a big heads up about this and there probably should have been one. It also was a bad thing to change right before the freeze.
So far I have changed /boot/grub/grub.conf and /etc/fstab to use the new names. I'll report back again after hopefully finishing getting
things to work again.
When using a rescue usb made from a combination of last night's boot.iso and a livecd to liveusb tool I get a traceback if I try to activate
the network devices. I am not sure where the fault is in this and it is an odd configuration, but it might be worth testing more conventionally.
I'll eventually get a change to try using the boot.iso from a cd/dvd but right now I can't and I probably won't have time for a copule of days
to futz with it. If I can reproduce it, I make a bugzilla for it.
Recap and full IRC transcript found here:
Please make corrections and clarifications to the wiki page.
== Attendees ==
== Important points ==
* Still no update from FEver owner--poelcat sent email
* triage priorities remain the same... http://tinyurl.com/6llac8
** 605 untriaged bugs presently
* poelcat still needs to update BugZapper wiki page with "why triage is
** quantumburnz updated the page and took a shot at the queries--we need
to double check them
** whiteboard tag of ''noauto'' is not in use for any bug--we will not
include it in our queries
** bugs which package maintainers want to remain indefinitely in
''rawhide'' version should add keyword: ''FutureFeature''
*** even if it is not an RFE this is okay
== Meeting Time and Day ==
* With change to Day Light Savings Time meeting will still occur at
10:00 AM Eastern
* Adjust to new time of 15:00 UTC starting with next meeting on 2008-11-04
== IRC Transcript ==
Hi, I have several laptops all with different Intel graphic cards
(915, 945 ...) and I would like to test plymouth if it is possible.
Now when I boot rawhide (Fedora 10) I don't get grub but only a black
screen and after that I see black screen with white-blue progress bar
Do I need even newer intel drivers than ones in Rawhide?
Is there a way to use latest intel drivers (if needed) or to somehow
enable plymouth and to see how it should work?
linux, blog, anime, spirituality, windsurf, wireless
registered as user #367004 with the Linux Counter, http://counter.li.org.
ICQ: 2125241, Skype: valent.turkovic