files which start with a dot and firefox gmail
by Mark Ryden
Hello,
When I am using gmail in firefox and I am trying to attach files , I
cannot see files
which start with a dot (for example, pressing attach a file and
navigating to /root does not
show files like .tcshrc).
Is there a way to overcome it (except of course making another copy of
the file which starts with a dot)?
Rgs,
Mark
14 years, 11 months
Re: f10livecd installs but wont boot, Error 2
by Jackson Byers
jackson byers wrote
I finally got the f10liveinstallcd to install, to sda1
it evidently went thru w no errors
--unchkd sda,sdb initially then went to custom install
--chose not mbr, instead firstsector of sda1
--the grub.conf uses UUID for its root=
I copied the grub.conf stanza to my fc5 grub.conf, it is in control
title Fedora (2.6.27.5-117.fc10.i686)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27.5-117.fc10.i686 ro
root=UUID=4e1021d9-e637-4
d03-97cb-fdd0d4b4cbee rhgb quiet
initrd /boot/initrd-2.6.27.5-117.fc10.i686.img
it all looks normal to me, altho use of UUID instead of /dev/sda1
i did not expect
But,
on attempting to boot it lists the above kernel line,
followed by
Error 2: Bad file or directory type
===========
new data:
get different error response if i do either:
a) in my fc5 grub.conf a stanza with
root(hd0,0)
chainloader +1
or, b) cp the f10 kernel, initrd to my fc5 /boot
and in my fc5 grub.conf a stanza with
root(hd1,5) # sdb6, my fc5 install
kernel /boot/vmlinuz-2.6.27.5-117.fc10.i686 ro
root=UUID=4e1021d9-e637-4d0
3-97cb-fdd0d4b4cbee rhgb quiet
initrd /boot/initrd-2.6.27.5-117.fc10.i686.img
Then, the error message from either a) or b)
after getting past the kernel line and the initrd line
and after getting to the bluesun graphic screen,
then screen goes back to console and:
Unable to access resume device....
mount: error mounting /dev/root on /sysroot as ext3: no such file or
directory
can anyone interpret for me either/both:
the errror 2 message or this new one?
thanks for advice
Jack
14 years, 11 months
Setting up CVS repository and avoiding Selinux issues?
by Dan Thurman
I am trying to get my CVS repository setup. Apparently,
it appears that the repository must be in the root directory,
otherwise I get selinux permission denials.
What I tried to do initially was to locate the repository
on a NTFS filesystem for which the context is fusefs
which could not be changed, no matter what I tried.
I got selinux permission errors.
Giving that up, I moved the repository to a ext3 filesystem
located on a separate drive/partition, mounted on /f-App1,
where the repository is located @ /f-App1/Develop/cvs, and did:
cd /f-App1/Develop/
chown -R cvs:cvs cvs
chcon -R -t cvs_data_t cvs
find cvs -type d -exec chmod 755 {} \;
find cvs -type t -exec chmod 754 {} \;
ln -s /f-App1/Develop/cvs /cvs
and I got selinux complaining that the files are not /cvs rooted.
So I did:
cp -a /f-App1/Develop/cvs /cvs1
rm -f /cvs
ln -s /cvs1 /cvs
And it worked.
How can I place my repository in a non-rooted, non-standard
repository location and avoid the selinux complaints?
14 years, 11 months
kernel panic with f10 install disk
by François Patte
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
I want to upgrade my f8 laptop to f10 but the boot on f10 install disk
stop after a few seconds:
Kernel panic - not syning: VFS: unable to mount root fs on unknown
block(0,0)
I am unable to enter any options like mediacheck....
I don't know where to type somthing like: "linux xxxx (xxxx= valid option)
Where is the "boot prompt?
Thanks.
- --
François Patte
UFR de mathématiques et informatique
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 4286 2145
http://www.math-info.univ-paris5.fr/~patte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkn4DOIACgkQdE6C2dhV2JXKzQCgnw7QmA4Png1KrHKpl3VyypVB
+UsAoMxfPHUTZ+Hr7Yr/7xqvg8BLU5Xp
=6lfC
-----END PGP SIGNATURE-----
14 years, 11 months
F10 - KDE - Wake from screensaver lock screen
by Craig White
F10/KDE
Since the last round of updates, it seems that when I wake the screen
from sleep/non-use, it shows me the entire screen instead of a dark
background while I am prompted to enter a password.
Blank screen - Start Automatically/10 minutes - Require Password After
60 seconds
Is this a bug?
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
14 years, 11 months
Problem: no X11 with NVIDIA G72M and 4Gb RAM
by Neville Dempsey
Summary: no X11 with NVIDIA G72M and 4Gb RAM, Fedora9 PAE kernel & Core
Duo T2250 (32Bit) on HP Pavilion dv6000 series laptop.
Basically X11 does not launch on Fedora9. Due to excess RAM (4Gb)?
I get:
> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko': -1 No such device
It fails when I initially when I run "sh
NVIDIA-Linux-x86-180.51-pkg1.run" on the 4Gb configuration. Also when I
rebuild the driver with 2.5GB and restart X11 with 4Gb.
But it works fine on 2.5Gb, AND X11 launches fine.
I'm getting the impression that with Core Duo CPU "T2250" (apparently
CPU is not 64 bit) gets no bonus address space from the PAE kernel. Not
even for paging. Any suggestions?
There is talk for configuring/changing the BIOS. But I have not found
such an option in the BIOS on my HP Pavilion:
http://ubuntuforums.org/showthread.php?t=675203
Would it be right to say that because nVidia is using the top +600Mb of
RAM, then Fedora9 on the Core Duo CPU "T2250" just cannot use it.
Note that "free" does not see the memory last 600Mb of memory either.
[root@november ~]# free
total used free shared buffers
cached
Mem: 3373480 199192 3174288 0 9036
96360
-/+ buffers/cache: 93796 3279684
Swap: 1048568 0 1048568
Work around it to install only 3Gb RAM.
I have not tried Fedora10+, also CPU "T2250" is only 32bit. c.f.
* http://en.wikipedia.org/wiki/Core_Duo#Yonah &
* http://ark.intel.com/cpu.aspx?groupId=27232
Is this the only work around? (I was hoping that PAE would give me some
kind of relief)
Cheers
N
p.s.
Other details:
> [root@november ~]# lspci | grep -i nvid
> 01:00.0 VGA compatible controller: nVidia Corporation G72M [GeForce Go 7400] (rev a1)
> [root@november ~]# uname -a
> Linux november 2.6.27.21-78.2.41.fc9.i686.PAE #1 SMP Mon Mar 23 23:34:11 EDT 2009 i686 i686 i386 GNU/Linux
> # grep model /proc/cpuinfo | sort -u
> model : 14
> model name : Intel(R) Core(TM) Duo CPU T2250 @ 1.73GHz
Extract from /var/log/nvidia-installer.log :
> -> Kernel module compilation complete.
> ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most
> frequently when this kernel module was built against the wrong or
> improperly configured kernel sources, with a version of gcc that differs
> from the one used to build the target kernel, or if a driver such as
> rivafb/nvidiafb is present and prevents the NVIDIA kernel module from
> obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU
> installed in this system is not supported by this NVIDIA Linux graphics
> driver release.
>
> Please see the log entries 'Kernel module load error' and 'Kernel
> messages' at the end of the file '/var/log/nvidia-installer.log' for
> more information.
> -> Kernel module load error: insmod: error inserting './usr/src/nv/nvidia.ko':
> -1 No such device
> -> Kernel messages:
> NVRM: This is a 64-bit BAR mapped above 4GB by the system BIOS or
> NVRM: Linux kernel. The NVIDIA Linux graphics driver and other
> NVRM: system software do not currently support this configuration
> NVRM: reliably.
> nvidia: probe of 0000:01:00.0 failed with error -1
> NVRM: The NVIDIA probe routine failed for 1 device(s).
> NVRM: None of the NVIDIA graphics adapters were initialized!
> NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
> NVRM: BAR1 is 256M @ 0x00000000 (PCI:0000:01.1)
> NVRM: This is a 64-bit BAR mapped above 4GB by the system BIOS or
> NVRM: Linux kernel. The NVIDIA Linux graphics driver and other
> NVRM: system software do not currently support this configuration
> NVRM: reliably.
> nvidia: probe of 0000:01:00.0 failed with error -1
> NVRM: The NVIDIA probe routine failed for 1 device(s).
> NVRM: None of the NVIDIA graphics adapters were initialized!
> NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
> NVRM: BAR1 is 256M @ 0x00000000 (PCI:0000:01.1)
> NVRM: This is a 64-bit BAR mapped above 4GB by the system BIOS or
> NVRM: Linux kernel. The NVIDIA Linux graphics driver and other
> NVRM: system software do not currently support this configuration
> NVRM: reliably.
> nvidia: probe of 0000:01:00.0 failed with error -1
> NVRM: The NVIDIA probe routine failed for 1 device(s).
> NVRM: None of the NVIDIA graphics adapters were initialized!
> ERROR: Installation has failed. Please see the file
> '/var/log/nvidia-installer.log' for details. You may find suggestions
> on fixing installation problems in the README available on the Linux
> driver download page at www.nvidia.com.
Extract from /var/log/Xorg.0.log :
>
> X.Org X Server 1.5.2
> Release Date: 10 October 2008
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.18-128.1.1.el5 i686
> Current Operating System: Linux november 2.6.27.21-78.2.41.fc9.i686.PAE #1 SMP Mon Mar 23 23:34:11 EDT 2009 i686
> Build Date: 17 March 2009 07:38:58PM
> Build ID: xorg-x11-server 1.5.2-6.fc9
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> Module Loader present
> ...
> (II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
> (II) NVIDIA(0): enabled.
> (EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
> (EE) NVIDIA(0): *** Aborting ***
> (II) UnloadModule: "nvidia"
> (II) UnloadModule: "wfb"
> (II) UnloadModule: "fb"
> (EE) Screen(s) found, but none have a usable configuration.
>
> Fatal server error:
> no screens found
> [root@november ~]# find /lib/modules/2.6.27.21-78.2.41.fc9.i686.PAE/ -name "nvid*" | xargs ls -l
> -rw-r--r-- 1 root root 8746945 2009-04-29 07:33 /lib/modules/2.6.27.21-78.2.41.fc9.i686.PAE/kernel/drivers/video/nvidia.ko
> -rwxr--r-- 1 root root 49376 2009-03-24 14:01 /lib/modules/2.6.27.21-78.2.41.fc9.i686.PAE/kernel/drivers/video/nvidia/nvidiafb.ko
>
> /lib/modules/2.6.27.21-78.2.41.fc9.i686.PAE/kernel/drivers/video/nvidia:
> total 56
> -rwxr--r-- 1 root root 49376 2009-03-24 14:01 nvidiafb.ko
14 years, 11 months
strange ImageMagick dependencies
by brian
I was about to yum install ImageMagick on a FC8 server when I saw that
it would require some 47MB of dependencies, including a ton of gnome
packages, metacity, bluecurve-icon-theme and other xWindow stuff. This
is a headless server and I'd really rather not have to install all this
(in this particular situation) cruft.
Anyone have any idea how to get around this? If there are just a couple
of libs i can install that'll keep yum from listing off ~60
dependencies, that'd be fine. I'm just not that familiar with all of
this to be able to pick through it.
14 years, 11 months
Video Card for SuperMicro SuperWorkstation 5046A-XB
by Steven P. Ulrick
Hello Everyone
I am building a system with the following specifications:
Chassis: SuperMicro SuperWorkstation 5046A-XB
Mainboard: Super C7X58
Processor: Intel Quad Core Xeon E5504 2GHz
Hard Drives: Western Digital 320 GB 7200 RPM Caviar SE16 Sata Hard Drive
Memory: Kingston 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10600)
Dual Channel Kit Desktop Memory
What I am now after is a video card. I don't need anything fancy. I
think I would be satisfied with whatever functionality that I can get
just using the apporpriate open source driver. So, I don't mind using,
let's say an NVidia card. I further don't mind completely and totally
AVOIDING any issues involved with depending on a proprietary company
keeping their proprietary binary blob in sync with the latest Kernel
updates. I just want a card that will "Just Work" the above described
system, with a minimum of headaches.
Thank you in advance for your knowledge and wisdom,
Steven P. Ulrick
14 years, 11 months
f10livecd installs but wont boot, Error 2
by Jackson Byers
I finally got the f10liveinstallcd to install, to sda1
it evidently went thru w no errors
--unchkd sda,sdb initially then went to custom install
--chose not mbr, instead firstsector of sda1
--the grub.conf uses UUID for its root=
I copied the grub.conf stanza to my fc5 grub.conf, it is in control
title Fedora (2.6.27.5-117.fc10.i686)
root (hd0,0)
kernel /boot/vmlinuz-2.6.27.5-117.fc10.i686 ro
root=UUID=4e1021d9-e637-4
d03-97cb-fdd0d4b4cbee rhgb quiet
initrd /boot/initrd-2.6.27.5-117.fc10.i686.img
it all looks normal to me, altho use of UUID instead of /dev/sda1
i did not expect
But,
on attempting to boot it lists the above kernel line,
followed by
Error 2: Bad file or directory type
I have seen some google msgs w this response
but no help to me
I ran across one google msg re liveinstall cd saying
it installed fine, but locked up on booting-- no further detail
also another msg saying wouldnt boot if using scsi disks ( I am)
but again no detail
is the liveinstallcd known to have problems booting?
any advice?
try f10dvd instead?
Jack
14 years, 11 months
Remooving U3 from USB drive.
by Aaron Konstam
A question which appeared on fedora-list recently was how to remove U#W
from a USB drive. I did not see a resolution until the following web
link:
http://www.u3.com/uninstall
--
=======================================================================
"Life, loathe it or ignore it, you can't like it." -- Marvin the
paranoid android
=======================================================================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam(a)sbcglobal.net
14 years, 11 months
