Swapping to a large sparse file
by JD
Can it be done?
So far, swapon says:
swapon: /var/swapfile: skipping - it appears to have holes.
I was hoping that the kernel's swapper would allow the filesystem to
allocate
real blocks to the sparse file when they are needed rather than check
up front to see if they already exist.
Maybe the devs can have a look and see if they can modify the swapper to
allow sparse swap files??
9 years, 4 months
Cannot boot laptop due to video driver
by Robin Laing
Hello,
I am trying to help my child whom is across the country repair their
laptop after installing the wrong video driver. They can boot into
emergency mode but not any of the other kernels.
During booting into the system, the boot process stops close to the
point of starting KDM.
We tried the following the guides on the net to remove the bad package
and keep getting stuck.
Tried to modify grub2 during boot to try booting into single mode and
that didn't work or we put the "single" in the wrong place.
A link that I can send them on how to use yum to remove the driver from
emergency mode or get into single user mode would be appreciated.
Either that or instructions on how to do either.
I told them to ask around the computer club as someone there might be
able to help them instead of me trying over the phone.
Current Fedora documentation for using the rescue mode is very sparse.
Tried the procedures on this page with no success. They said that they
couldn't get the chroot command to work. They may have typed something
wrong because it was very late. Going to deal with it tomorrow (Friday).
http://docs.fedoraproject.org/en-US/Fedora/16/html/Installation_Guide/res...
9 years, 4 months
[SOLVED] Re: [F21] NetworkManager won't connect
by Marco Guazzone
On Sat, Jan 17, 2015 at 8:39 AM, Marco Guazzone
<marco.guazzone(a)gmail.com> wrote:
> Hello,
>
> I have connectivity problem since the last two updates of NM.
> Specifically, when I boot the system and I log in in the graphical
> environment (XFCE in my case), the NM applet continuesly animates,
> trying to connect to my network.
> I can wait any time (actually I've tried for a max waiting time of 10
> minutes), but NM seems to have trouble to connect.
> In order to connect I have to:
> 1. Right-click on the NM applet and deselect "Enable Networking". The
> applet stops animating
> 2. Again, right-click on the NM applet and re-select "Enable
> Networking". Now, NM successfully connects to the network.
>
> Am I alone to experience such problem?
>
> The NM version is 0.9.10.1-1.2.20150109git for Fedora 21 x86_64
I've just updated NM to the version that is currently in updates-testing
http://koji.fedoraproject.org/koji/buildinfo?buildID=604111
and the problem seems to be fixed.
Bye,
-- Marco
9 years, 4 months
Nagios 4?
by Konstantin Svist
How come Fedora repos include Nagios 3.5 and not 4?
Version 4 seems to have been released in Oct 2013...
9 years, 4 months
Adding shortcut to desktop
by Alex
Hi,
I have a fedora21 desktop that I'm building for my father-in-law and
have installed gnome-tweak-tool to enable icons on the desktop. Now, I'd
like to add an icon on the desktop to automatically start a qemu
instance of windows7. I'd even settle for an icon that opens
virt-manager in such a way as to be able to start the instance.
How about adding it to the menu that appears when you move the mouse all
the way to the left?
I found this link at gnome.org but I can't believe that it's still this
hard for an end-user (my father-in-law) to add links to his own programs?
https://developer.gnome.org/integration-guide/stable/desktop-files.html.en
Maybe there's a desktop that isn't so deficient?
Any ideas greatly appreciated.
Thanks,
Alex
9 years, 4 months
MC Midnight Commander: error opening PDF files refers to Dolphin
by A.J. Bonnema
Hey all,
I have always used MC as my commandline filemanager and really like it.
However, since Fedora 21, when opening a PDF file it always shows an
error that it cannot open "/usr/bin/dolphin" which is understandable,
because by default gnome uses a different file manager (Nautilus I think).
Has anyone else seen this error? Is it related to MC settings or to
Fedora setting? I couldn't find it in either. Actually, I wouldn't
expect any Dolphin defaultness in gnome version of Fedora.
I attached a printscreen of the error message (hope that's allowed in
this forum).
Kind regards, Guus.
9 years, 4 months
[F21] NetworkManager won't connect
by Marco Guazzone
Hello,
I have connectivity problem since the last two updates of NM.
Specifically, when I boot the system and I log in in the graphical
environment (XFCE in my case), the NM applet continuesly animates,
trying to connect to my network.
I can wait any time (actually I've tried for a max waiting time of 10
minutes), but NM seems to have trouble to connect.
In order to connect I have to:
1. Right-click on the NM applet and deselect "Enable Networking". The
applet stops animating
2. Again, right-click on the NM applet and re-select "Enable
Networking". Now, NM successfully connects to the network.
Am I alone to experience such problem?
The NM version is 0.9.10.1-1.2.20150109git for Fedora 21 x86_64
Cheers,
-- Marco
9 years, 4 months
X server not starting on boot
by Raman Gupta
My X server is no longer starting at boot time. Plymouth simply stops
and X does not start.
I use the open source ATI radeon drivers on a fully updated Fedora 21
system. systemctl status kdm.service reports that the X server failed
to start:
Jan 16 13:16:02 host kdm[1885]: X server for display :0 terminated
unexpectedly
But /var/log/Xorg.0.log contains absolutely no errors, except that
where the following lines would normally be printed:
[ 171.281] (II) RADEON(0): EDID vendor "NEC", prod id 26260
[ 171.282] (II) RADEON(0): Using EDID range info for horizontal sync
[ 171.282] (II) RADEON(0): Using EDID range info for vertical refresh
[ 171.282] (II) RADEON(0): Printing DDC gathered Modelines:
[ 171.282] (II) RADEON(0): Modeline "1680x1050"x0.0 146.25 1680
1960 2136 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
...
instead it looks like it just starts shutting down:
[ 24.280] (II) UnloadModule: "wacom"
[ 24.280] (II) evdev: Eee PC WMI hotkeys: Close
[ 24.280] (II) UnloadModule: "evdev"
... [ more close / unloads, until log end ]
I am able to start X by ssh'ing in to the box (no VTs are available
either), and restarting the kdm service manually (sudo systemctl
restart kdm), at which point everything works perfectly well.
Any ideas what is going on here?
Regards,
Raman
9 years, 4 months
Issue with reinstall live image to same disk
by David Highley
Installed Fedora 21 live image to disk. Now we want to reinstall to the
same disk but it does not show up in the storage selection. Wiped
partitions with fdisk hoping that would make it work. Next cat'd file to
raw device to wipe or corrupt the MBR. Still no joy. How in H do you get
the live image installer to find the disk you want to install to? Bye
the way this is not a new issue as we have run into this problem in the
past but never found a solution to it. We always had to go to another
install method which is very painful and time consuming.
9 years, 4 months