Re: [Fedora-livecd-list] btrfs for Fedora 12 and 13 LiveCD/DVD ?
by dexter
On 25 April 2010 19:47, Alan Pevec <apevec gmail.com> wrote:
> On Sat, Apr 24, 2010 at 4:38 PM, Valent Turkovic
> <valent.turkovic gmail.com> wrote:
>> Hi,
>> how to make Fedora 12 and Fedora 13 LiveCD/DVD that is btrfs formated
>> and not ext4?
>> What options need to be enables in kicstart file so that
>> livecd-creator makes btrfs iso images?
>
> Didn't try it, but should be enough to change fstype in fedora-live-base.ks
>> part / --size 3072 --fstype ext4
>
> Alan
CrossPosting:
A quick scan reveals adjusting fstype will not be enuff, btrfs uses
different userspace tools from ext[34] "btrfs-progs", so livecd-tools
will need a patch.
...dex
13 years, 7 months
Are all cores unlocked?
by Terry Polzin
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 4
model name : AMD Phenom(tm) II X2 555 Processor
stepping : 3
cpu MHz : 800.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid
pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock
nrip_save
bogomips : 6399.37
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
processor : 1
vendor_id : AuthenticAMD
cpu family : 16
model : 4
model name : AMD Phenom(tm) II X2 555 Processor
stepping : 3
cpu MHz : 3200.000
cache size : 512 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid
pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm
sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock
nrip_save
bogomips : 6400.39
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
13 years, 7 months
Re: Kernel update scrambles catalyst driver output
by Marko Vojinovic
On Thu, Sep 23, 2010 at 8:48 AM, Peter Boy <pboy(a)barkhof.uni-bremen.de> wrote:
> Am Mittwoch, den 22.09.2010, 11:15 +0200 schrieb Marko Vojinovic:
>> For all issues with the catalyst driver you should contact ATI (and
>> good luck with that). It's closed source, they are the only ones who
>> know how to fix it.
>
> In general you are right, but this time it seems not to be ATI but
> kernel and associated kmod and wrapper magic. As I noted in my post:
> Same ATI binary driver in combination with kernel-2.6.32.21-166 works
> just fine. Some stuff in kernel-2.6.32.21-168 introduces regression.
In most cases it is not a regression, but rather the usual kernel
API/ABI change. This requires a rebuild or and/or source code
modification to all affected kernel modules, sometimes the graphics
drivers (and in this case apparently VirtualBox kernel module, and
maybe some others as well).
The kernel does require such changes occasionally, and it is the
responsibility of third-party module suppliers to keep up and adjust
to the new API/ABI. Depending on the severity of the kernel change, it
might be enough just to recompile the module against the new kernel,
or it might require interventions at the source code level, in which
case the module providers usually push a new version of their
software.
So old modules keep working with the old kernel, but fail to be
compatible with the new one. But this is not a regression of the
kernel, but rather its rapid advancement. And it is the responsibility
of module providers to adapt to the new changes.
Now in this case, given that the catalyst driver is closed source,
only ATI folks can make any relevant changes, if source code needs to
be modified. Otherwise, rpmfusion folks can just recompile the module
against new kernel and push it as an update. The same thing happens to
closed source nVidia drivers.
With open source drivers you don't have this problem because they get
rebuilt and updated along with the new kernel, so the whole problem is
transparent to the end-user.
>> For buying ATI hardware, you have only yourself to blame. :-)
>
> Years ago I changed my Hardware from Nvidia to ATI because the free ATI
> driver supported dual monitor xinerama those times, the free nvidia
> driver did not. The ATI hardware and free driver combo worked for years
> perfectly well.
>
> ATI is not as bad as some rumour may spread. :-)
Well, if ATI works for your needs, fine, I don't mind. But my
experience is that both open and closed source ATI drivers tend to
break quite often, compared to nVidia and Intel. That makes every ATI
graphics card unreliable from a user's perspective, and it is often a
gamble whether the latest drivers will work with any particular model
or not.
And fuurthermore, when something doesn't work with the open source
nouveau driver, the devs have a good excuse since they need to RE it.
But when something doesn't work with the open source radeon driver,
the devs have no such excuse, since all specs are (supposedly)
available. Or otherwise ATI is lying to its Linux customers.
:-)
Marko
13 years, 7 months
Re: Kernel update scrambles catalyst driver output
by Marko Vojinovic
On Wed, Sep 22, 2010 at 1:41 AM, Peter Boy <pboy(a)barkhof.uni-bremen.de> wrote:
> Folks,
>
> the latest kernel update for Fedora 12
> (kernel-2.6.32.21-168.fc12.x86_64) leaves me with a scrambled screen
> using the catalyst driver (ATI Radeon HD 3470). Reverting back to
> kernel-2.6.32.21-166.fc12.x86_64 resolves the problem.
>
> Unfortunately, the free ATI driver is not an option because it's dual
> DVI monitor setup doesn't work since several releases (BZ entry in
> place).
>
> I suppose, fedora project doesn't care about catalyst (for good
> reasons), but who does?
For all issues with the catalyst driver you should contact ATI (and
good luck with that). It's closed source, they are the only ones who
know how to fix it.
For all issues with the free radeon driver create a bugzilla entry.
It's open source, but only the initiated are capable of fixing it
(after they break it).
For buying ATI hardware, you have only yourself to blame. :-)
HTH, :-)
Marko
13 years, 7 months
Testing disk I/O?
by Tom Horsley
I know about the smart tools, but they run disk tests
pretty much entirely within the disk drive (I think?).
Is there a good tool for testing the whole disk I/O
system that will wind up exercising the disk, the
controller/chipset, etc? (Hopefully available in the
fedora repos).
I have a feeling something is going funny in the head
on my system and the smart disk tests report all OK
(as does a few passes of memtest86+). I want to get
the motherboard into the mix now.
13 years, 7 months
list server returning lots of undeliverables
by JD
This morning I got about 10 of these:
This is the mail system at host lists.fedoraproject.org.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to<postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<users(a)lists.fedoraproject.org>: mail forwarding loop for
users(a)lists.fedoraproject.org
13 years, 7 months
change login screen to KDE
by Jamie Bohr
I have googled and googled on how to make the login screen use KDE rather
than Gnome on Fedora 13. Many references say to put DISPLAYMANAGER=KDE in
/etc/sysconfig/desktop however when I do that I get a console window for the
login screen. I have even tried a lowercase kde rather than an uppercase,
still no good. I have an FC12 install that works fine but it only has KDE
installed.
Any help or pointer would be great.
--
Jamie Bohr
13 years, 7 months
test management system
by Piscium
Hiya,
I am looking for a test management system, to help software/firmware
testing. Something like an application that runs on a server that
would allow testers to create test plans, write test cases, mark test
cases as passed or failed once tested.
Ideally it could be used with a browser as client, and there would be
a way to create reports showing what percentage of the test cases were
run, success rate and so on. Due to the nature of the products
involved there is no requirement for automatic testing, that is, all
testing is manual.
Is there such a beast, preferably open-source and available in Fedora?
Thanks.
13 years, 7 months