ATA2:00: link is slow to respond....
by Angelo Moreschini
Hi,
my computer boot only in emergency mode ...
Looking the journalctl (command journalctl -xb), I found (in thejournalctl
) these lines in red color :
ATA2:00: link is slow to respond....
(and after..)
ATA200: SRST failed (erro 16)
That seem indicate that it is a problem to access the HDs..
I found a possible solution to the problem in this post:
http://codeverge.com/opensuse.org.help.install/-solved-ata1-srst-failed-e...
There is wrote that :...the problem can depend by the physic set up of the
HD (as "master", "slave", "single drive", ...): this set up can be done by
changing the position of a jumper on the HD...
I know that, in the past time, the HDs had to be set physically in this
way.., but recently I never heart anymore that the modern HD need this
operation..
So actually I don't care anymore of the configuration of the HDs
(my HD is Toshiba 1 TB that I bought few mounts ago).
I would like to have a confirmation that what I read in the post is only an
obsolete information and, in any case, I would like to know also what I can
do to go around in my problem..
>From the command line: ls /dev/sd* I get:
give me this input :
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5 /dev/sdb /dev/sdb1
/dev/sdb2
Thank you
regards
Angelo
2 years
nc missing option -z
by Suvayu Ali
Hi,
I used to use netcat to check if a particular host is up or if I have
internet connection before I run a few scripts. I would use the -z
option in particular. But now I see that has been removed:
$ nc -z imap.gmail.com 993 && sync-my-email.sh
ncat: invalid option -- 'z'
Here is the excerpt from the old manual page:
-z Specifies that nc should just scan for listening daemons, without
sending any data to them. It is an error to use this option in
conjunction with the -l option.
Any ideas what happened to it? What can I use as replacement?
Thanks for any ideas.
--
Suvayu
Open source is the future. It sets us free.
2 years, 4 months
install f22 into btrfs subvolume won't boot
by Neal Becker
I tried it. It was not easy to figure out how to use anaconda gui to setup
install into a subvolume - but I got it done. I now have 3 subvolumes:
sudo btrfs subvolume list /
[sudo] password for nbecker:
ID 256 gen 1818627 top level 5 path home
ID 259 gen 1818478 top level 5 path root
ID 487 gen 1818625 top level 5 path root00
But if I try to boot with 1st grub entry, I get:
dracut-initqueue warning could not boot
starting dracut emergency shell
If I try to boot off the grub entry labeled 'rescue', it boots OK.
dracut says something about fixing initramfs.
--
Those who fail to understand recursion are doomed to repeat it
3 years, 8 months
BTRFS Question
by Javier Perez
Hi
I am just learning about btrfs on my home system.
How do I know what kind of options where used to create a BTRFS filesystem?
I installed F21 from scratch and I created a BTRFS filesystem on a HDD.
I think I created it with the "single" option.
Now I read that that is dangerous, I should have created it as one of the
raids if I want to have data redundancy and protection vs bit rot (which is
what I was looking forward to).
How can I verify it? Also, If I want to change it, can I do it IN-PLACE or
do I have to reformat/recreate the filesystem?
Thanks for whatever help/illumination you might provide. I am catching up
on btrfs, but I am not there yet.
JP
--
------------------------------
/\_/\
|O O| pepebuho(a)gmail.com
~~~~ Javier Perez
~~~~ While the night runs
~~~~ toward the day...
m m Pepebuho watches
from his high perch.
3 years, 8 months
RFC: Multiboot Guide
by Pete Travis
Hi All,
There's regularly questions here, and around the internet (ie ask.fp.o)
about dual booting Fedora with Windows systems, or other Linux systems,
or OSX. To address the more common questions, the Fedora Docs team has
written a Multiboot Guide[1].
The guide is intended to help set up a multiboot system in a functional
way, or to help get to a more functional state if needed. For the most
part, we've tried not to make it intimidatingly complex, and I hope that
it will aid you in most multibooting situations.
As with all of Fedora's documentation, feedback from readers is crucial
to ensuring the quality of the work. Please use the guide, and if you
find questions unanswered or answers unclear, reply here or use the
'multiboot-guide' component of the Fedora Documentation product on
https://bugzilla.redhat.com .
[1]
http://docs.fedoraproject.org/en-US/Fedora/22/html/Multiboot_Guide/index....
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
3 years, 8 months
Biting the bullet?
by Rolf Turner
I have finally reached a stage where I may have to bite the bullet,
grasp the nettle, screw my courage to the sticking place .... and
upgrade my Fedora version.
I am currently running Fedora 17. Which is of course antediluvian. But
everything I have seen on this list with respect to upgrading terrifies
me. Disasters seem to lurk everywhere and I haven't the skills to cope
with disasters. Nor do I have access to any support in respect of Fedora.
So, if you will bear with me, I'd like to start off with a preliminary
question:
The seeming necessity for upgrading arises from a pressing need to
upgrade "R" to version 3.2.0. When I try to build this version I get a
load of error messages (basically coming from gcc I think) like unto:
> connections.o: In function `gzcon_write':
> /home/rolf/Desktop/Rinst/R-3.2.0/src/main/connections.c:5469: undefined reference to `deflate'
There were also complaints about undefined references to inflate, crc32,
deflateEnd, inflateEnd, inflateReset, inflateInit2_, deflateInit2_,
compress, uncompress, and zlibVersion, many of which were issued
repeatedly. It finally gave up, saying:
> collect2: error: ld returned 1 exit status
People from the R-help mailing list said that the problem lies in some
"compression related" libs --- zlib, bzlib, liblzma.
I tried installing zlib and zlib-devel (using yum install) and was told
in both cases that my system was up-to-date. I tried installing bzlib
and was told there was nothing by that name. I then installed lzma and
lzma-devel (*that* seemed to work) but it didn't help. Same undefined
references problems as before.
It was also suggested that I try building R-patched. So I tried; no
help there either.
So: Can anyone suggest what I can or should do to overcome this problem
*without* having to upgrade?
Given that the answer to my preliminary question is "No", can anyone be
so kind as to provide me with a *recipe* for upgrading, expressed in
simple-minded terms that I can understand? Something of the form:
(1) First, do this.
(2) Second, do something else.
(3) Third .....
You get the idea. I'm afraid vague generalities would be of no help to
me, since I am a bear of very little brain and long words bother me.
(I know that step (0) is to make a backup of all my user files. Which I
know how to do and will do.)
A specific question, I guess, is: Do I use yum for such an upgrade?
(And if so, what is the syntax?) Or do I use fedup? (And likewise, what
is the syntax?)
If no-one wants to write out a set of instructions for me (and
admittedly I can see that they may well not want to) can someone point
me at such a set of instructions somewhere on the web? Again, they
would have to be expressed in a very simple-minded way. ("Upgrading
Fedora for Dummies".)
Everlastingly grateful for any help that anyone can extend.
cheers,
Rolf Turner
-
Technical Editor ANZJS
Department of Statistics
University of Auckland
Phone: +64-9-373-7599 ext. 88276
Home phone: +64-9-480-4619
3 years, 9 months
C/C++ Compiler Invalidly Turning Warnings into Errors?
by Stephen Morris
I have a driver for a wifi usb device that I need to compile because
there are no drivers in the kernel, which has been obtained from the
vendor of the device. When I attempt to compile the code the compile
fails on the grounds that some warnings are being translated into
errors. From my perspective these errors should not be happening
because, when a debugging module wants to time stamp the build, that is
not an error and is perfectly acceptable. How do I get the compiler to
stop producing these errors. The messages I get are listed below.
Authentication requested [root] for make driver:
make ARCH=x86_64 CROSS_COMPILE= -C
/lib/modules/3.17.8-300.fc21.x86_64/build
M=/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411
modules
make[1]: Entering directory '/usr/src/kernels/3.17.8-300.fc21.x86_64'
CC [M]
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_cmd.o
CC [M]
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_security.o
CC [M]
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:
In function ‘dump_drv_version’:
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:64:
error: macro "__DATE__" might prevent reproducible builds
[-Werror=date-time]
DBG_871X_SEL_NL(sel, "build time: %s %s\n", __DATE__, __TIME__);
^
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1:
error: macro "__TIME__" might prevent reproducible builds
[-Werror=date-time]
DBG_871X_SEL_NL(sel, "build time: %s %s\n", __DATE__, __TIME__);
^
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1:
error: macro "__DATE__" might prevent reproducible builds
[-Werror=date-time]
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1:
error: macro "__TIME__" might prevent reproducible builds
[-Werror=date-time]
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1:
error: macro "__DATE__" might prevent reproducible builds
[-Werror=date-time]
/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.c:66:1:
error: macro "__TIME__" might prevent reproducible builds
[-Werror=date-time]
cc1: some warnings being treated as errors
scripts/Makefile.build:257: recipe for target
'/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o'
failed
make[2]: ***
[/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411/core/rtw_debug.o]
Error 1
Makefile:1377: recipe for target
'_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411'
failed
make[1]: ***
[_module_/usr/local/downloads/dlink/RTL8812AU_linux_v4.3.2_11100.20140411/driver/rtl8812AU_linux_v4.3.2_11100.20140411]
Error 2
make[1]: Leaving directory '/usr/src/kernels/3.17.8-300.fc21.x86_64'
Makefile:1350: recipe for target 'modules' failed
make: *** [modules] Error 2
##################################################
Compile make driver error: 2
Please check error Mesg
##################################################
3 years, 9 months
F22 KDE How To Remove "Software Updates" Widget?
by Christopher Ross
In the Fedora 22 / KDE 5 task bar there is a "Software Updates" widget.
Where is the setting to remove that? It's inappropriate for arbitrary
end users to be be updating the system software on shared machines.
Many thanks,
Chris R.
3 years, 9 months
Re: Fedora 22 is here!
by Suvayu Ali
Hi Matthew,
Looking forward to this release. I haven't read the release notes yet,
however I have a few questions or comments. If "read the release notes"
is the best answer, please feel free to say so :).
On Tue, May 26, 2015 at 09:49:49AM -0400, Matthew Miller wrote:
>
> * Atomic Improvements – Fedora 22 Atomic Host includes a number of
> interesting improvements, including the Atomic command, updated
> Docker, Kubernetes, Flannel, and rpm-ostree packages.
>
> * Dockerfiles – Fedora 22 also includes a fedora-dockerfiles
> package (and up-to-date git repository) for building applications
> with the base Fedora 22 Dockerfile and additional packages.
I'm interested in running SLC containers on Fedora hosts. Does any of
these packages facilitate that? What I understood so far is, it allows
me to run the latest Fedora containers in other places easily. Where
would one go looking for info for a need like mine?
> * Cockpit will be compatible between OS releases -- Cockpit is a
> server manager that makes it easy to administer your GNU/Linux
> servers via a web browser.
>
> - Easy to use. Cockpit is perfect for new sysadmins, allowing
> them to easily perform simple tasks such as storage
> administration, inspecting journals and starting and stopping
> services.
>
> - No interference. Jumping between the terminal and the web
> tool is no problem. A service started via Cockpit can be
> stopped via the terminal. Likewise, if an error occurs in the
> terminal, it can be seen in the Cockpit journal interface.
>
> - Multi-server. You can monitor and administer several servers
> at the same time.
I tried this a bit already, I like the convenience of having everything
aggregated together, however I'm a bit uneasy that a browser is the
interface. After all it is the most vulnerable application on most
machines. Are there other (safer) interfaces I can try, preferably on
the CLI? Am I being unreasonably paranoid? I'm really interested in
trying the multi-server bits. Any pointers?
> * Better notifications.
[...chomp...chomp...chomp...]
> details. And if you're a serious Terminal user, longer background
> jobs now notify you when they're done, so you can get on with
> other work and pick up the results when you're ready.
Is this desktop agnostic? I use XFCE. I'm guessing it's some kind of
DBUS magic?
> Fedora Labs
> -----------
>
> We also have a new site, presenting functional bundles of software
> which were previously also collected as Spins. Visit
> https://labs.fedoraproject.org/ for collections focusing on gaming,
> audio production, robotics, security, and more.
Collecting all the resources on RTD is a great initiative. Wonderful!
> GNU Compiler Collection 5
> -------------------------
>
> Fedora 22 comes with GCC 5.1 as the primary compiler suite.
This question is probably off-topic here, but I'll ask anyway :-p. Does
this make a significant difference during development when I want my
projects to also compile with older GCC like 4.[89]?
> Fedora's FedUp utility enables an easy upgrade to Fedora 22 from
> previous releases. See the FedUp page on the Fedora wiki for more
> information:
This question is not exactly about FedUp. I find it strange that no
release so far has supported yum (or dnf now) as one of the upgrade
methods. And yet, I have had the most reliable upgrade experiences with
it since F12 or so! Any reason why this is the case? I think it is the
method that allows for the shortest of downtimes.
Thanks for the release. Looking forward to trying it!
Cheers,
--
Suvayu
Open source is the future. It sets us free.
3 years, 9 months
