XO Performance Team meeting
by Josh Bressers
So we had the first XO Performance Team meeting. Given we have a pretty defined
scope, there wasn't a ton to talk about.
I updated the wiki page with our high level goals:
https://fedoraproject.org/wiki/QA/TestPlans/XO_Performance
Right now, the plan is this:
lmacken is going to look at some kernel foo I don't understand.
mrhodes Is going to look at the services.
We could still stand someone looking at the gnome bits
and how to make firefox more usable.
I'll deal with some image creation things.
So any other team members who weren't around, feel free to grab a task, fill in
the wiki with more details, or start discussion on the mailing list.
--
JB
15 years, 6 months
XO: Random Findings
by Adam D. Ligas
Hey folks,
My original XO was electrically challenged, so I had to wait for my
replacement XO. The new one has arrived, and armed with my 4GB SD card,
I've got Fedora up and running. I did need to use the 384/256 setting
with Snap3 to avoid any low space errors when running the creation
script.
Lots of folks seem to be working/commenting on the performance things,
so I thought I would take a stroll through some of the other test plans
in the wiki and give some random things a try.
On the display side of things, most of the fonts seem to be chopped in
half and some buttons appear blacked out. I can't seem to predict when
either will occur, but both occur often. Looked for settings to change
the DPI as suggested, but I couldn't find any.
Gave "Cheese" a try with the built in camera. Appears to function
normally, though it is pretty slow to initialize the camera and get it
displayed on screen. Effects work, but cause a significant delay in the
refresh rate. Maybe being CPU limited here?
Setup the 802.11g wireless via NetworkManager, and had no trouble.
Connecting to my WPA2-PSK/AES network without any difficulty was quite a
joy!
Firefox worked and didn't seem to be completely miserable. Maybe I'm
luckier then most. I didn't browse around too much though.
I was going to play with some audio but my initial testing ended here
with Power Management. Basically, the XO just died :). Fedora didn't
detect it was running on a battery, and so I received no alert that the
battery was low, and it just ran out of juice.
Interesting little machine - I'm looking forward to more testing once I
get back home to the charger.
- Adam
15 years, 6 months
freecell crashes x while yum is running
by shmuel siegel
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
graphics chip.
15 years, 6 months
Re: Received your XO? Let us know!
by Jatin Nansi
Hello all,
I received the XO yesterday, will be installing build 767 on it today.
Then get involved with the power mgmt team.
Jatin Nansi
15 years, 6 months
XO: USB video adapter (sisusb)
by Terry Stewart
Hello everyone,
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
(UVA200) <http://www.futureshop.ca/catalog/proddetail.asp?logon=&langid=EN&sku_id=0...>)
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
blank vt).
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:
------------------
Section "Device"
Identifier "Device1"
VendorName "SiS"
BoardName "SiS"
Driver "sisusb"
EndSection
Section "Monitor"
Identifier "Monitor1"
VertRefresh 50-75
HorizSync 30-90
Option "DPMS"
EndSection
Section "Screen"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 16
SubSection "Display"
Depth 16
Modes "1024x768"
EndSubSection
EndSection
----------------
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
Backtrace:
0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812b8db]
1: /usr/bin/Xorg(xf86SigHandler+0x51) [0x80bc911]
2: [0x130400]
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?
Thank you,
Terry
15 years, 6 months
ext4 able to boot from ext3 mbr?
by stan
Hi,
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
workaround?
Just in case, will preupgrade work for F10?
Thanks.
15 years, 6 months
luks related change is prevented boots of system with encryption over raid
by Bruno Wolff III
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.
15 years, 6 months
Rescue activation of network doesn't work
by Bruno Wolff III
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.
15 years, 6 months
Fedora Bug Triage Meeting Recap 2008-10-28
by John Poelstra
Recap and full IRC transcript found here:
https://fedoraproject.org/wiki/BugZappers/Meetings/Minutes-2008-Oct-28
Please make corrections and clarifications to the wiki page.
== Attendees ==
* poelcat
* jds2001
* kulll
* jlaska
* quantumburnz
== 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
important"
* getting
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora10 prepared
** 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 ==
15 years, 6 months
