Le jeudi 28 décembre 2006 à 01:55 -0800, Thomas Chung a écrit : Yes that is a chipset that is supported by the Linux Kernel. Chipsets that are not supported by the kernel and ndiswrapper was the subject of my post. Both of my USB adaptors are cheap and unsupported. Both work just fine with ndiswrapper and device files created in /etc/sysconfig/networking and /etc/sysconfig/network-scripts. One works with the standard FC5 and 6 kernels but the Linksys requires a kernel with 16K stack size. Tony

Le jeudi 28 décembre 2006 à 18:24 +0530, Rahul Sundaram a écrit : This is one place where I think Fedora is wrong. It isn't impossible to build a CD that supports ndiswrapper the kernel thing is however working against the end user. Think of the new user who wants to try FC for the first time and who may have any sort of WiFi card. FC liveCD can not have all the Windows drivers for every WiFi card on the market that is common sense. But delivering a kernel that prevents ndiswrapper from working with adaptors made by Linksys - one of the major networking players - is a non sense... This is just my own personal opinion. Cheers Tony

On Thu, 2006-12-28 at 10:05 +0100, Tony Grant wrote: The live cd tools easily support if people wants to do this... Just build your own live cd and add --repo=livna,http://address.of.livna.repo/find_it_yourself --package=kmod-ndiswrapper See [1] for options. You can also use the --base-on option, then something along the lines of # livecd-creator --base-on=FC-6-i386-livecd-1.iso --fs-label=This-Is-Not-An-Offical-Fedora-6-LiveCD --repo=livna,http://address.of.livna.repo/find_it_yourself --package=kmod-ndiswrapper should do the trick. Rahul already explained why we cannot include this software on the live CD; it's really no different from why we can't include it in Fedora. And that's also one reason you probably can't call such a live cd "Fedora". But, sure, you can include all the Forbidden Items on a live cd if you want; how well it works is for your self and possibly others to find out. [2] David [1] : [davidz@hook ~]$ livecd-creator No packages specified. usage: livecd-creator [--help] [--repo=<name1>,<url1> ...] [--repo=<name2>,<url2>] --package=<p1> [--package=<p2> ...] [--exclude-package=<e1>] --exclude-package=<e2> ...] [--base-on=<path-to-iso-file>] [--fslabel=<label>] --help : Print usage and exit --repo : Path to yum repository --package : Include this package --exclude-package : Exclude this package --base-on : Add packages to an existing live CD iso9660 image --fslabel : File system label (default: livecd-YYYYMMDD-HHMI) [2] : Just for kicks I tried, to test that this really works, to include the ATI graphics driver and it doesn't work well on the live cd as it relies on the user manually having to edit the /etc/X11/xorg.conf file. In contrast the free video drivers from X.org have moved beyond this. Make up your own mind.

On Tue, 2007-01-02 at 18:48 +0100, Tony Grant wrote: Not sure whether one can even redistribute said Windows drivers but if you can it's possible to include it on a live CD; just package it up as RPM's and build your own live CD image. It's definitely not something you can call an official Fedora live CD though. (We probably need to have some guide lines on such live cd's if people start creating them; most likely something for the FAB to consider.) Except what happens when that kernel needs a security fix? And why is it reasonable for users to use "some modified scripts"? Networking should just work out of the box, if it doesn't file a bug in Bugzilla against either NetworkManager or the kernel. As I stated earlier, most networking bugs are with the kernel drivers at this point. It's really really easy: just get hardware with a working driver and things "Just Work". Well, it's true that it's a royal pain to use binary drivers especially with Fedora as we don't bend over (unlike some other distros who cares more about their amount of users, much less about freedom) and include these things with the OS. I know it's really easy to say "just buy hardware that is supported by Linux" and, at this point, it's all we can say. Sorry. The Fedora Live CD is not different from normal Fedora installs and it shouldn't be really. Hopefully in some star trek future most hardware out there in the hands of consumers will just work. We're just not there yet. Perhaps it would be good if Fedora (and others) were better about having a compatibility list of the good stuff to buy. David

Tony Grant wrote: Yes. absolutely. Mike McGrath, our infrastructure team super hero is working on a hardware profiler based on new RHEL 5 rhn-client tools (It used to be based on kudzu but kudzu is deprecated and it is now based on lshal). We are likely to include in the next release (which wont be called FC7 btw since we intend to merge core and extras and do multiple release spins as described in http://fedoraproject.org/wiki/Core/Schedule). See http://fedoraproject.org/wiki/MikeMcGrath/HardwareProfiler. This has several benefits. We would be able to collect very detailed information what stuff works and importantly what doesnt and which hardware is more popular so that we can prioritize that on QA etc. Rahul

On Tue, 2 Jan 2007, David Zeuthen wrote: At the upcoming FUDCon we'll be talking about building The Great Hardware Compatibility Matrix in the sky. In the abstract, it's pretty simple: 1. Add a pretty button to the desktop that says "Click Here If Your System Works Great!" 2. lshal | mail &quot;hardware-monitor(a)fedoraproject.org&quot; 3. A script dumps lshal data into a database. Anyway, this is really just an excuse to announce FUDCon again: http://barcamp.org/FudconBoston2007 --g ------------------------------------------------------------- Greg DeKoenigsberg || Fedora Project || fedoraproject.org Be an Ambassador || http://fedoraproject.org/wiki/Ambassadors -------------------------------------------------------------