installing to external USB drive: FC5 any better?
by Michael McFarland
Like many others, I've been struggling to get FC4
installed onto an external USB drive. This seems like
it would be a great method to recommend for people who
want to test the linux waters without touching their
windows installs.... if some major distro would make
it work!
After following the impressive instructions at
http://www.vigla.eclipse.co.uk to create & tweak a new
initrd image, I'm still seeing nothing but kernel
panics.
Now, it's my understanding so far that this could all
be avoided if the default initrd image used for the
standard install would just include the proper
modules. Or maybe it could add those libraries to the
image if it was determined in the DiskDruid
parititioning step that I'm installing to an external
device.
Does anyone know if this change is being included (or
considered) for the upcoming release of FC5? Would
fixing this be significantly harder than it sounds?
Also, just to be sure... I've seen a few (apparently
untested) suggestions that it might be possible to
avoid the initrd mess if I were to specifying some
kernel parameters during the normal install. Is there
any truth to that?
I really think it's in everyone's best interests to
find some kind of real solution here. (preferably
soon)
- Michael
18 years, 2 months
Re: FC4 kernel with nvidia driver
by Todd Simi
If you download from NVIDIA, make sure you check for all the patches you
will need. There are several depending on which kernel version you are
running.
> > From: Matthew Saltzman <mjs(a)ces.clemson.edu>
> > Reply-To: For users of Fedora Core releases <fedora-list(a)redhat.com>
> > To: For users of Fedora Core releases <fedora-list(a)redhat.com>
> > Subject: Re: FC4 kernel with nvidia driver
> > Date: Sun, 26 Feb 2006 10:11:36 -0500 (EST)
> >
> > On Sun, 26 Feb 2006, Randy Vice wrote:
> >
> > > Are there any rpm'd FC4 kernels for nvidia's driver? I know, evil
> > > closed source driver, but AFAIK, I'll need it for using Cedega
> > > (transgaming). Figure closed source driver is better then dealing with
> > > multi-booting XP with FC. ;)
> >
> > There are NVidia driver RPMs for FC4 kernels at rpm.livna.org.
> > Alternatively, you can get the drivers directly from nvidia.com and
> > rebuild them yourself for any FC4 kernel.
> >
>
>
18 years, 2 months
kernel 2.6.15-1.1831_FC4, system hangs at reboot
by oleksandr korneta
Hello there,
I got AMD Turion based laptop. Installed FC4 for x86_64 on it.
Everything was more or less fine. but after last kernel update the
system hangs whenever I want to reboot it. No matter whether I
initialize the reboot from command line or from gdm. I can see all the
messages about halting the processes and stuff and then it says
"rebooting the system" and screen goes black and that is it... Sometimes
though, it seems like trying to reboot the computer and there are
vertical white stripes across the screen (?), but no more than that.
I can still poweroff it normally.
did anyone experienced anything similar?
thanks in advance.
--
regards,
Oleksandr Korneta
/The nice thing about standards is that there are so many to choose from./
18 years, 2 months
Re: Announcing Fedora Core 5 Test 3
by Jim Cornette
The question was asked regarding FC5T3 release. FC5T3 was released
today and is available for download.
Replying to the anounce list!
Jim
Jesse Keating wrote:
>Forty-four years ago, John Hershel Glenn Jr. is successfully launched
>into space aboard the Friendship 7 spacecraft on the first orbital
>flight by an American astronaut. Russia had already sent two cosmonauts
>into orbit at this time. In the many following years Russian and
>America race each other for space superiority. Much later Russia and
>America have finally started cooperating in Earth's adventures into
>space. Competition is good, but collaboration can by so much better.
>
>Today, Open Source stands as one of the ultimate examples of
>collaboration. No boundaries, no borders, no barriers. As an example
>of this collaboration, we are proud to announce:
>
>Fedora Core 5 Test 3 Now Available
>==================================
>The Fedora Project announces the third release of the Fedora Core 5
>development cycle, available for the i386, x86_64, and PPC/PPC64
>architectures. Beware that Test releases are recommended only for Linux
>experts/enthusiasts or for technology evaluation, as many parts are
>likely to be broken and the rate of change is rapid.
>
>http://fedora.redhat.com/About/schedule/
>Final is scheduled for release March 15. This aggressive schedule makes vitally
>important your help in testing, reporting and suggesting fixes for bugs.
>Please direct bugs to http://bugzilla.redhat.com, Product Fedora Core,
>Version fc5test3. As always, be sure that your bug is not already fixed
>by updates and search for existing bugs before filing.
>
>http://fedoraproject.org/wiki/Core/ReleaseFreezeProcess/
>During the continual freeze process, very few changes will be
>introduced. This is to prevent new bugs from surfacing and to ensure
>that Fedora Core 5 is the best release we can make it. Rawhide reports
>over the next three weeks should be very sparse. Please do test the few
>updates extensively.
>
>Thanks to all in the Fedora Project who have contributed to this
>release. Your continued efforts are what makes Fedora possible.
>
>Downloads
>=========
>DVD, CD and network installation are available.
>Please read the Important Warnings below in this announcement for more
>details.
>
>http://torrent.fedoraproject.org/
>The recommended method of download is via BitTorrent from this site.
>
>http://fedora.redhat.com/download/mirrors.html
>HTTP, FTP, and RSYNC downloads are available from Fedora Project mirrors
>listed above. Note that not all mirrors may be synced at this time.
>
>Notable Features of FC5 Test 3
>==============================
>* Xen, now with x86_64!
>* Package selection within the installer has been reenabled.
>* Rebuilt again on later gcc4.1 snapshot for performance and security
>* Hibernate should be functional on a wide variety of hardware again
>(use pm-hibernate to test)
>* PPC Install CDs are bootable once again
>* Unified SRPM set instead of one per arch
>* Lots of bugfixes from Test 2 release testing
>* 1600+ Extras packages conveniently available via yum
>
>http://fedora.redhat.com/docs/release-notes/
>Latest version of release notes are available from here. (not yet
>uploaded, will be soon.
>
>Important Warnings
>==================
>http://fedoraproject.org/wiki/FC5Test3CommonProblems
>Please see this page for an updated list of important notes for FC5test3
>in order to avoid common problems and troubleshoot problems that you may
>see.
>
>Have fun testing this release, and enjoy the collaboration
>of Linux.
>
>
>
--
The more you sweat in peace, the less you bleed in war.
18 years, 2 months
[akonstam: Re: cups sucks me]
by akonstam@trinity.edu
On Tue, Feb 21, 2006 at 03:21:23PM -0600, John Pierce wrote:
> Well, I had similar problems getting cups to serve up to my local
> network, what I found was the cupsd.conf file says that certain
> defaults exist to serve a local network, and according to the
> documentation in the conf file those defaults should allow local
> machines to print to it.
>
> What I discovered was having to manually set the defaults to make it
> work, I think the redhat/fedora developers tell it not to share on the
> network for security reasons, but fail to adjust the documentation to
> match their build configuration.
>
> Take the following for example:
>
> ########
> ######## Network Options
> ########
> #
> # Ports/addresses that we listen to. The default port 631 is reserved
> # for the Internet Printing Protocol (IPP) and is what we use here.
> #
> # You can have multiple Port/Listen lines to listen to more than one
> # port or address, or to restrict access:
> #
> # Port 80
> # Port 631
> # Listen hostname
> # Listen hostname:80
> # Listen hostname:631
> # Listen 1.2.3.4
> # Listen 1.2.3.4:631
> According to the above statement the system should allow connection on
> port 631, but if I do not add the following two lines I cannot print
> to this host.
>
> Listen localhost
> Listen 192.168.0.70:631
>
> Go through and check the configuration file.
>
> John
Ok, lets take this from the top. The cupsd.conf should have only one
Listen statement in most cases, and that is:
Listen 127.0.0.1
Clients on the same LAN will be able to print to the printer without
any further configuration. That is , no server line needs o appear in
the clients.conf file. Further, if the Server line appears in the
client.conf file then the client will not be able to print to a local
printer.
Under no circumstances should system-config-printer be used to
configure CUPS printers. It has serious flaws for this purpose.
If the original poster used system-config-printer to configure the
server printers this is one reason printer might have not worked on
the clients.
--
-------------------------------------------
Aaron Konstam
Computer Science
Trinity University
telephone: (210)-999-7484
----- End forwarded message -----
--
=======================================================================
When the bosses talk about improving productivity, they are never talking
about themselves.
-------------------------------------------
Aaron Konstam
Computer Science
Trinity University
telephone: (210)-999-7484
18 years, 2 months
ref: Subject: Is SELinux resetting permissions?
by Don Bedsole
Hi Anne,
See if this helps. It was posted a while back.
//////////////////////////////////////quote//////////////////////////////////////////////////
Date: Thu, 9 Feb 2006 08:32:53 +0000
From: James Wilkinson <fedora(a)westexe.demon.co.uk>
Subject: Re: chmod
To: fedora-list(a)redhat.com
Message-ID: <20060209083253.GA4043(a)westexe.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
gary wrote:
> In a attempt to get audacity running again (now I get i/o errors
> in user mode) I decided change permissions on /dev/dsp from 600
> to 660 to see what effect that would have on my audacity problem.
> Each time I leave root, /dev/dsp reverts back to 600.
>
> Why can't I change permissions on /dev/dsp?
How are you becoming root? Are you logging in, or using su - from a
terminal?
I suspect you're logging in. This is generally considered a Bad Idea,
because mistakes made while root are potentially more serious (they can
do more damage), so it makes sense to limit the time spent as root.
It would also mean that when you log back in again, udev carefully
recreates /dev/dsp with the appropriate permissions -- 600.
But in any case, I think you're barking up the wrong tree. Either udev
is seriously screwed, or /dev/dsp should be read-write for you anyway.
$ ls -l /dev/dsp
crw------- 1 james root 14, 3 Feb 9 07:42 /dev/dsp
dsp should be owned by whoever's logged in at the console. Anything done
by that owner should have full access to /dev/dsp.
Hope this helps,
James.
/////////////////////////////end of quote/////////////////
18 years, 2 months
samba shares in FC4
by Louis Garcia
I am trying to share a directory in FC4. readable and writable to everyone.
The directory is /data/public : 2777 root:root. It is an ext3 partition.
This is my smb.conf:
[global]
workgroup = HOMENETWORK
netbios name = server
server string = Samba Server
security = SHARE
guest account = guest
hosts allow = 127.0.0.1, 192.168.0.0/24
hosts deny = 192.168.0.1/24
[public]
comment = Public Stuff
path = /data/public
read only = No
guest ok - Yes
I am able to browse the server but when I open the share public I get an
error that the directory doesn't exist.
The /data directory is a ext3 partition. I am able to share a directory in
the / partition with no problems.
I am stumped. --Louis
18 years, 2 months
APIC error on CPU0: 40(40)
by D. Hugh Redelmeier
I'm getting a lot of these messages showing up in dmesg output.
What is a lot? At this point, 314 during my 3 days of uptime.
Description of system:
- HP Pavilion a1350n desktop computer
- AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
- ATI chipset
- nVidia 7800GTX PCIe video card (and 450w Antec power supply to
support it)
- Fedora Core 4 for x86_64 with updates as of last week
- kernel-smp-2.6.15-1.1831_FC4 for x86_64
>From http://lkml.org/lkml/2004/4/5/280 I infer that this message means
"Receive Illegal Vector" on the APIC bus.
I would guess that booting with "noapic" would suppress the problem.
I would rather solve it. My machine is new and under warranty (but HP
does not support Linux).
=> if you are running a Athlon X2 CPU, could you check to see whether you are
getting these messages too?
dmesg | grep 'APIC error'
I'd be interested in hearing from you either way. Please describe
your system.
=> The machine came with WinXP MCE. Is there any way I should be able
to observe this problem from WinXP? That would make it easier to ask
for support from HP.
Anecdote:
I used to get APIC errors, years ago, on my Abit BP-6 motherboard running
dual Celeron 300A CPUs. I just put it down to the fact that:
- Celerons were not specifieded to be dual processors (but lots of folks
did run them this way)
- Celerons were on speced to run 50% overclocked (but this was
considered to be Standard Operating Procedure by most folks)
- the BP6 signal runs were not designed as Intel specified for a dual
processor
18 years, 2 months
Kernel Compilation failure
by Jeff Mutonho
Hi
I'm trying to install the USB driver for an IPWireless modem.I've downloaded
the driver from
(http://www.neology.co.za/support/index.php?page=MyWirelessLinuxDrivers
) and followed instructions on how to install it.
When I get to rebuilding the kernel(make bzImage) , the build is failing
with the following message:
CC arch/i386/kernel/asm-offsets.s
In file included from include/asm/thread_info.h:16,
from include/linux/thread_info.h:21,
from include/linux/spinlock.h:12,
from include/linux/capability.h:45,
from include/linux/sched.h:7,
from arch/i386/kernel/asm-offsets.c:7:
include/asm/processor.h:87: error: array type has incomplete element type
make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1
make: *** [arch/i386/kernel/asm- offsets.s] Error 2
I googled and found the suggestion that I should backup my .config file ,
run 'make mrproper' ,restore the .config file , run 'make xconfig' and
enabled the usb ipwireless driver as a module , save the .config file , run
'make clean' and finally run ' make bzImage'.But I'm still getting the same
error message.
I can paste the contents of my .config file , if it may help solve this
problem.
Jeff Mutonho
GoogleTalk : ejbengine
Skype : ejbengine
Registered Linux user number 366042
18 years, 2 months