audio pops and snaps?
by thomas cameron
All -
I have an Abit KN8 SLI motherboard with an AMD Athlon 64 X2 Dual Core
Processor 4600+ (Socket 939) and 4GB memory. The sound card is an
on-board nVidia Corporation CK804 AC'97 Audio Controller (rev a2).
I installed off the F10 x86_64 beta DVD ISO image and updated against
rawhide about an hour ago.
I'm noticing a *lot* of audio pops and snaps. For instance, I use
Pidgin and I have sound events turned on for pretty much everything.
Often the snaps come as a sound event occurs like someone "speaking" on
IRC - instead of a clear note when someone "talks" there is a snap and
then the note. Also, when someone joins or leaves, the note is often
(but not always) interrupted by either a short sound dropout or a pop.
In other cases, just sitting here typing away on this e-mail with no
sound event being triggered, I hear a pop.
This system works great with RHEL 5.2 installed, and I don't recall any
audio issues under F9. This seems to be unique to F10/rawhide.
BZ 466840 filed.
TC
15 years, 7 months
Ndiswrapper working with F10?
by Arch Willingham
I have the beta of F10 working on a desktop at the office.....it works great. I thought I'd give it a shot on my laptop. My laptop currently runs F9 and ndiswrapper which it gets from the repository. Does anyone have F10 working with Ndiswrapper?
Thanks!
Arch
15 years, 7 months
Yum Upgrade To F10 Beta
by Jonathan Roberts
I've just upgraded my F9 machine to F10 beta via yum. The only change
I had to make to get things functional was to switch to a virtual
terminal and remove my old xorg.conf (I hear this is no longer used?).
Thought I'd share this for anyone who was going to try the same thing.
I'd quite like to get my user account set up though as is the default
for a fresh installation: what . folders do I need to remove for this
to happen? /me finally learnt not to remove all . because of
gnupg/ssh!
Other quick impressions:
boot was with the text based progress bar, intel 945 here.
Grub doesn't seem to have updated and still shows F9 splash screens
and counts down - is there any way to fix this other than manually
changing menu.conf?
Boot seemed fairly quick - approx 45 seconds to login prompt on a
1.6Ghz Intel Atom. If it's still obeying old settings, think I have
some services disabled more than standard.
Will keep an eye out for other interesting points...
Jon
15 years, 7 months
Re: GNOME woes on the XO / A modest proposal
by Josh Bressers
----- "Jeremy Katz" <katzj(a)redhat.com> wrote:
>
> The big problem *ISN'T* GNOME vs XFCE. The problem is the (large)
> hit
> we take on performance with squashfs decompression. So with the
> snap1
> images, things have been changed a bit so that we can instead use the
> ext3fs and take decompression out of it. Which makes an impressive
> amount of difference
>
I'm running the new snap1 image without compression, and I'm not seeing a huge difference. It is a bit snappier, but unless I do some surgery, it still freezes once all the RAM is consumed.
I would say as for performance, on a scale of 1 to 10, you've gone from perhaps a 3 to a 4. The gains I see aren't all that spectacular, especially considering all the folks with 2 Gig cards are SOL now.
--
JB
15 years, 7 months
Using the XO with the gnome image
by Josh Bressers
So previously I voiced my concern over getting gnome to run on the XO. I'm
not not convinced it's a good idea, but here's how to make it work. My SD
card has a 512M swap partition and a 2 Gig overlay (I have the 4 Gig card).
If you don't fix the image, the machine will eat up too much RAM and
won't run, so you need to use an overlay file so the changes stick between
reboots.
First, make the laptop boot into single user mode (runlevel 1). To do
this, mount the SD card, open boot/olpc.fth and look for the line that looks
like this:
root=UUID=48EE-AC2A rootfstype=vfat rw liveimg overlay=UUID=48EE-AC2A quiet
rhgb
Add a 1 , as in the number one, before the quiet, so it should look like:
"overlay=UUID=48EE-AC2A 1 quiet"
Boot the SD card and it will drop you into a root prompt.
Now, once you have a prompt, you need to disable some services. Here is
the list I disabled, you can obviously pick and choose. To do this, run
the command 'chkconfig <service> off" replacing <service> with an actual
name. For example 'chkconfig setroubleshoot off'.
At the very least, turn off setroubleshoot, that's the one really eat a lot of RAM.
Here is the list of services I've shut off:
setroubleshoot sendmail rsyslog rpcidmapd rpcgssd rpcbind portreserve
nfslock netfs mdmonitor kerneloops irqbalance cups bluetooth avahi-daemon
auditd
I admit, I'm not completely sure about all the rpc stuff I'm shutting off,
but it doesn't seem to have an adverse affect.
Now shutdown the XO, and remove the 1 you added above, then boot back into the
SD card.
Now once you get into Gnome, it's still doing many sill things. Open
the Session Preferences tool (System->Preferences->Personal->Sessions) and
just remove most of the stuff there. The things I kept are:
Gnome Settings Daemon, Gnome Settings Daemon Helper, Network Manager, Power
Manager, and PulseAudio Sound System
This leaves me with enough free memory to run various things without too
much trouble.
--
JB
15 years, 7 months
GNOME woes on the XO / A modest proposal
by Steven Salevan
Hey guys,
At the moment, it appears that GNOME is borderline dysfunctional on my
XO, despite applying the recommended speed fixes (creating a persistent
overlay, turning off swappiness). On runlevel 3, the box seems to be
stable and at least usable, but if I switch over to runlevel 5, I cannot
use the box for more than about 3 minutes without receiving a kernel
panic that leads to a total system freeze. Alas, this panic is not
logged to any system log, but I'll be connecting up a serial console
over the next day or two get it off of the system and into a new BZ.
Outside of the panic issue, how goes GNOME testing for everyone else on
the list? For the few minutes that the device actually works, the
system seems to crawl along at glacial speeds, taking over a minute to
bring up simple tools such as the Appearance preferences configurator.
Firefox takes more time to load than the box has before reaching the
aforementioned system freeze.
So... if my hunch is right, and I fear it is, I don't know if 2.5
weeks' worth of testing is going to ensure that we ship a functional
GNOME-laden version of F10. From what I've read and heard, the plan is
to maintain a sizeable swap space on the SD card, as the 256MB of
built-in RAM alone is not sufficient to run GNOME, which will wear out
the card in time along with limiting available space (especially if
we're leaning on shipping the 2G card with each XO).
This might be a controversial viewpoint, and if so, so be it, but I
wonder if we shouldn't change our focus to a more lightweight window
manager such as XFCE. There's already been work performed to this effect:
http://dev.laptop.org/git?p=projects/fedora-xo;a=summary
GNOME may indeed be more familiar to users, but what use is familiarity
if there's no functionality? At least XFCE can run comfortably on the
limited resources of the XO, allowing us to focus on the issues that we
can indeed address in the limited time we have. What do you guys think?
-Steve Salevan
ssalevan(a)redhat.com
15 years, 7 months
Re: GNOME woes on the XO / A modest proposal
by Josh Bressers
----- "Joshua Daniel Franklin" <jdf.lists(a)gmail.com> wrote:
> I'd love to see multiple "spins" for anyone with the time to try them
> out.
> This would include xfce, headless, beowulf cluster, etc. :)
>
> However, I think in the testing period we should stick to our goal of
> running the stock Fedora 10 LiveCD on the XO. Keep in mind that
> if that's not possible, then running Fedora 10 LiveCD on *any* older
> hardware similar to the XO is also not possible. That sounds like a
> bug to me. Maybe we need to check bogomips in firstboot and cut
> down on services and switch to some sort of "lightweight GNOME"
> or xfce. I would argue for GNOME first since there are a lot of
> guides and screenshots for newbies that assume certain things
> about the menus.
>
As far as I know, this is the plan, but I admit, there is a rather serious
leadership vacuum for this testing effort. What is the plan to make the current
images usable? They obviously are not acceptable in their current state and I
presume we won't be giving the G1G1 participants a lengthy and error prone set of
directions.
Perhaps it would be worth creating an "tiny" spin or something similar for these
little netbooks.
You can get Gnome to run, without swap, as long as you follow my previous
directions to disable most services and disable most of the things that Gnome runs
(like the packagekit daemon, which is a real killer when it tries to update things).
I'd also suggest you install the Midori web browser. It uses considerably less RAM
than Firefox. It's not as robust, but in this instance, I think saving RAM is more
important than features.
--
JB
15 years, 7 months
XO: livecd-iso-to-disk.sh on rhel5 seems problematic
by Eric Sandeen
I was trying to use Jeremy's livecd-iso-to-disk.sh script w/ the
olpc-gnome.iso to get my XO up and running and it got very weird boot
failures:
Stuff like "<buffer@800000>:2: Can't find word to replace"
and "Can't open boot device"
Running the script on an F8 box got it going properly.
I'm not sure what the problem is at this point but just in case anyone
else has had the same trouble...
-Eric
15 years, 7 months