Differences between standard and rescue kernels
by Alex
Hi,
I installed fedora21 on an AMD x86_64 box then moved it to an Intel
x86_64 box and it would no longer boot. It would get to the following:
Switched to clocksource tsc
then just sit there. Booting from the rescue kernel worked properly.
What is the difference between the standard default kernel and the
rescue kernel?
# grep ^menuentry /etc/grub2.cfg
menuentry 'Fedora, with Linux 3.19.7-200.fc21.x86_64' --class fedora
--class gnu-linux --class gnu --class os --unrestricted
..
menuentry 'Fedora, with Linux 0-rescue-1b5a0c2dfaca499c98f601585417d143'
--class fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-0-rescue-1b5a0c2dfaca499c98f601585417d143-advanced-a76c8f65-ff02-470b-b087-453fc8b6275e'
Also, what is this new initrd16 and linux16 grub2 options?
Do I need to rebuild the initrd to support the AMD processor on the new
machine? I believe I use dracut for that?
Thanks,
Alex
8 years, 11 months
unable to run e2fsck
by Angelo Moreschini
Hi,
I have problem to run fsck on the root directory.
I know that ( in order that the root directory is not mounted) I need to
boot the computer in rescue mode.
So I boot the computer by the CD of the installation.
This CD (that come me with a book of Prentice Hall) don't give me directly
the prompt.
...Before I get a window from what I choose "troubleshooting" and after I
get another window where I can chose:
- Continue : to attempt to mount the file system under the directory
/mnt/sysmag
- read only : to do the same, but only in read mode..
- skip : to boot the computer skipping the mounting of the
filesystem
I choose skip (in order to avoid to mount the file system) but (also in
this way) the command e2fsck -yvf /dev/sda2 fails...
This because the drive /dev/sda2 result to be mounted...
So* what I can do to run fsck on /dev/sda2 (where is mounted the root
directory)?*
thank you
regards
Angelo
8 years, 11 months
MTP vs gvfs?
by Aleksandar Kostadinov
Hello
I installed the proper MTP gvfs backend and now I see phone in nautilus
and thunar (I'm using XFCE). I can browse device, copy files, etc.
Problem comes when I try to open a photo or another file in a viewer or
firefox (e.g. to attach file). It just fails without an obvious reason.
If I copy the file to `/tmp` then I can open but it is stupid that one
cannot open directly from the phone.
Any ideas what's wrong?
btw it seems google stopped supporting openid 2 auth and now I'm locked
out of ask.fedoraproject.org
Any idea how to recover my account is welcome as I tried to no avail.
Thank you,
Aleksandar
8 years, 11 months
Cockpit error
by arnaud gaboury
When connecting to cockpit, from Firefox or chromium, I get this error
when looking at the JS console:
TypeError: l.GetUnitFileState is not a function1 shell.js:38:3271
TypeError: c.Subscribe is not a function1 bundle.js:2:8289
I can still browse and see pages.
Any idea why and how to fix it ?
Thank you
google.com/+arnaudgabourygabx
8 years, 11 months
SD cafd read only -
by Bob Goodwin
I have an micro SD card that has turned read only. I have been trying
everything I can find to clear it for several hours.
[root@box10 ~]# dd if=/dev/zero of=/dev/sdh bs=1M
dd: error writing ‘/dev/sdh’: No space left on device
3726+0 records in
3725+0 records out
3906453504 bytes (3.9 GB) copied, 4.48747 s, 871 MB/s
It's a 16GB device and was working normally until I tried to clear it a
few hours ago, fdisk and gparted also show it as 3.9 GB.
What am I doing wrong?
Bob
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-22b/64bit LINUX XFCE
8 years, 11 months
/boot on RAID1 with fedora21
by Alex
Hi,
What is the level of support for RAID1 on /boot? Is it now fully
supported with fedora21?
In the past, it's had a tendency to always put /boot only on /dev/sda,
meaning if the first disk dies, the system becomes unable to boot.
Forcing it to be on /dev/md0 or other RAID device has always been
problematic.
Thanks,
Alex
8 years, 11 months
Touchpad stops working after suspend/resume
by Marcos Paulo de Souza
Hi guys,
after a suspend/resume of my Asus laptop, my touchpad stops working. I
saw some ACPI warnings when the system starts:
[marcos@xfiles ~]$ dmesg | grep "\] ACPI Warning"
[ 1.557666] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 1.557724] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 7.736403] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 7.736764] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 12.295625] ACPI Warning: SystemIO range
0x000000000000f040-0x000000000000f05f conflicts with OpRegion
0x000000000000f040-0x000000000000f04f (\SMB0) (20141107/utaddress-258)
[ 12.295630] ACPI Warning: SystemIO range
0x000000000000f040-0x000000000000f05f conflicts with OpRegion
0x000000000000f040-0x000000000000f04f (\_SB_.PCI0.SBUS.SMBI)
(20141107/utaddress-258)
[ 21.846813] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 21.847175] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 39.746391] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 39.747146] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 215.456511] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
[ 215.456881] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20141107/nsarguments-95)
Have you ever had this kind of problem?
Thank you,
Marcos
8 years, 11 months
gnome (move right)
by Patrick Dupre
Hello,
Before fc21, I was able to move pads to any workspace by keying right.
In fc21, I only have the option to move up (and down) when doing the same
thing!
Am I missing some thing?
I have 8 workspaces.
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
8 years, 11 months
Re: SD cafd read only
by Peter Skensved
>
>
> On 16/05/15 17:36, Joe Zeff wrote:
> >>
> >> I really believe this thing has failed.
> >
> > You're probably right. Still, before tossing it, if toss it you must,
> > what do you get from this:
> >
> > fdisk -l /dev/sdh
> >
> > Does that show the full size, or just the 3.9GB? If nothing else, we
> > might learn something about the card's failure modes.
> > --
> .
> [root@box10 /]# fdisk -l /dev/sdh
> Disk /dev/sdh: 3.7 GiB, 3906453504 bytes, 7629792 sectors
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
>
> Just the 3.9GB, the other 12 is not accessible.
>
Are you sure this is really a 16GB card ? Lots SD cards and USB cards ( even
branded ones ) are fake and do not hold anywhere near the stated capacity. You
may want to try to run f3write / f3read ( from http://oss.digirati.com.br/f3/ )
on it to see what the actual capacity is.
With a fake card everytig works well until the real capacity is filled at which
point it just keeps overwriting itself until completely scrambled.
The kernel will usually react to this by remounting it read only.
peter
8 years, 11 months