Fedora 12 new updated kernel won't boot
by barry yu
Fedora 12 32bit version, after updated by yum for all, when rebooted to
GRUB menu, selected the new kernel 2.6.31.12-174.2.22.fc12.i686.PAE,
won't boot, reboot system back to grub menu and chose previous kernel
2.6.31.12-174.2.3.fc12.i686.PAE to start f12, still works, is there any
fix available or have to wait for f13
14 years, 2 months
Fwd: Re: Fedora 12 new updated kernel won't boot
by barry yu
-------- Original Message --------
Subject: Re: Fedora 12 new updated kernel won't boot
Date: Sun, 28 Feb 2010 18:40:03 -0800
From: Barry Yu <barry10280(a)gmail.com>
To: kari.somby(a)gmail.com, Community support for Fedora users
<users(a)lists.fedoraproject.org>
On 02/28/2010 10:53 AM, Kari Somby wrote:
> On sunnuntai, 28. helmikuuta 2010 18:30:06 Barry Yu wrote:
>
>> Fedora 12 32bit version, after updated by yum for all, when rebooted to
>> GRUB menu, selected the new kernel 2.6.31.12-174.2.22.fc12.i686.PAE,
>> won't boot, reboot system back to grub menu and chose previous kernel
>> 2.6.31.12-174.2.3.fc12.i686.PAE to start f12, still works, is there any
>> fix available or have to wait for f13
>>
> Hi
> Could you add some more info.
> - When does it "freeze" (if not sure, just some explanation what happens)
> - Your system processor
> - output of #df
> - your /etc/grub.conf -file info
> - output of command #ls -la /boot/
>
> Kapi
>
During the startup, when I chose the top line (updated kernel version)
on the grub menu and then hit return, the round thing at center begins
the progress indication of booting into login window, then then window
is black out in text mode the frozen with the cursor blinking,
completely locked up.
The processor is Intel Core2Duo E6750 2.66Ghz
Out put of #df;
[root@cts-home1 ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda10 52055064 6565172 42845596 14% /
tmpfs 2021732 340 2021392 1% /dev/shm
/dev/sda8 303344 44371 243312 16% /boot
/dev/sdb1 732572000 599620656 132951344 82%
/media/EXT_700_Data_NTFS
/dev/sdc1 976760000 575901492 400858508 59%
/media/EXT_1T_Data_NTFS_BAK
Output of /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,7)
# kernel /vmlinuz-version ro root=/dev/sda10
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=2
timeout=-1
splashimage=(hd0,7)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.12-174.2.22.fc12.i686.PAE)
root (hd0,7)
kernel /vmlinuz-2.6.31.12-174.2.22.fc12.i686.PAE ro
root=UUID=53830302-bee4-48dd-88c4-bc7eaae75454 LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.12-174.2.22.fc12.i686.PAE.img
title Fedora 12 (2.6.31.12-174.2.3.fc12.i686.PAE)
root (hd0,7)
kernel /vmlinuz-2.6.31.12-174.2.3.fc12.i686.PAE ro
root=UUID=53830302-bee4-48dd-88c4-bc7eaae75454 LANG=en_US.UTF-8
SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.12-174.2.3.fc12.i686.PAE.img
title Windows
rootnoverify (hd0,0)
chainloader +1
~
~
Output of ls -la /boot/;
[root@cts-home1 ~]# ls -la /boot/
total 33626
dr-xr-xr-x 5 root root 1024 2010-02-28 18:36 .
dr-xr-xr-x 25 root root 4096 2010-02-28 18:17 ..
-rw-r--r-- 1 root root 103729 2010-02-19 11:22
config-2.6.31.12-174.2.22.fc12.i686.PAE
-rw-r--r-- 1 root root 103728 2010-01-18 12:19
config-2.6.31.12-174.2.3.fc12.i686.PAE
drwxr-xr-x 3 root root 1024 2010-01-28 22:28 efi
drwxr-xr-x 2 root root 1024 2010-02-28 18:38 grub
-rw-r--r-- 1 root root 12109220 2010-02-27 08:38
initramfs-2.6.31.12-174.2.22.fc12.i686.PAE.img
-rw-r--r-- 1 root root 12030120 2010-01-28 23:10
initramfs-2.6.31.12-174.2.3.fc12.i686.PAE.img
drwx------ 2 root root 12288 2010-01-28 21:08 lost+found
-rw-r--r-- 1 root root 1488800 2010-02-19 11:22
System.map-2.6.31.12-174.2.22.fc12.i686.PAE
-rw-r--r-- 1 root root 1488919 2010-01-18 12:19
System.map-2.6.31.12-174.2.3.fc12.i686.PAE
-rwxr-xr-x 1 root root 3461664 2010-02-19 11:22
vmlinuz-2.6.31.12-174.2.22.fc12.i686.PAE
-rwxr-xr-x 1 root root 3461952 2010-01-18 12:19
vmlinuz-2.6.31.12-174.2.3.fc12.i686.PAE
14 years, 2 months
FC12 udev rules
by Terry Horsnell
Hi all,
I need to set up a custom rule to give me mode 666 on a custom USB device
(or on all the otherwise un-handled USB devices).
I used to do this (in FC9) by modifying ruleset 50-udev-default.rules at
the libusb entry (I know this was not the 'correct' way, but I could never
understand udev enough to work out what *was* the correct way).
Now that I've moved to FC12, this 50- rulest doesnt exist, and I cant find
where the libusb stuff is now handled. Can someone please tell me how to
correctly add a custom rule. Presumably I have to use a filename which causes
it to be executed in the right order. Does udev stop processing subsequent
rules files when it hits a rule which matches?
In ruleset 50-udev-default.rules I used to have:
###SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644"
SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0666"
Thanks,
Terry
14 years, 2 months
X without -nolisten tcp
by Boggiano
Hi all,
f11 and kde 4.4, here.
How I can start X without the -nolisten tcp option ?
I like to give to my second personality :) the right to exec apps.
From old days I remember:
xhost +127.0.0.1
su - mike
kwrite (with mike's rights)
How can I archive it ?
Thanks
Alessandro
14 years, 2 months
User to set CPU scaling?
by Chris Smart
Is there a way for non-root users to be able to administer CPU
scaling? Currently the interfaces are all owned by root:root and short
of a hack to change their permissions on boot, I'm wondering if
there's a "proper" way to do it?
Thanks,
-c
14 years, 2 months
Dump/Restore Errors
by Dr J Austin
Hi
I have been following recent threads about the best way to clone/backup
disks.
"Risks of backing up live mounted filesystems using dump(8)"
I have just tested dump/restore using a System Rescue CD
using dump 0.4b42
The source /dev/sda7 is a fully working updated F12 / partition
(including /boot)
The destination is a similar partition on the same disk /dev/sda9
mkfs -t ext3 /dev/sda9
mkdir /mnt/out
mount /dev/sda9 /mnt/out
dump 0f - /dev/sda7 | (cd /mnt/out; restore -rf -)
40GB dump/restore took 46 minutes
I received 9 errors of the type
resync restore, skipped 1 blocks
error in EA block 1
magic = 0
Google tells me that dump saves as is
and that restore is finding an error in an Attribute Block
(maybe/sometimes associated with NFS)
I have not been able to find definitive answers to some obvious
questions.
1. Are these fatal for the file concerned hence invalidating the clone/backup?
I am unsure how to interpret the error message
2. Why are they present in the first place?
3. How can I find which files they are caused by?
4. Can I correct the errors, do I need to?
Grateful for any help
Regards
John
14 years, 2 months
F12-i386-DVD iso won't burn properly -- SOLVED
by Andre Robatino
Tony Nelson wrote:
> That test often fails due to a kernel issue, making good media seem
> bad. I prefer to compare the bits with:
> # cmp /dev/dvd /path/to/iso
> If the dvd matches the iso: if there is no kernel issue there will
> be no output; else it will complain about eof on the iso file. If
> the dvd does not match the iso, there will be a specific complaint
> about the first mismatch.
Reading /dev/dvd in general is not reliable since depending on the
hardware, it may not read exactly the right number of bytes (hopefully,
it will at least read >= the right number, which means your command
would either give an EOF error if the number was greater, or say the
files are identical if it's the same).
I use the rawread script from
http://www.troubleshooters.com/linux/coasterless.htm#rawread
which automatically reads the correct size of the ISO, and runs a dd
command reading exactly that much off the disc. This way I can just
check the hash directly, like this:
rawread /dev/dvd | sha256sum
which only requires reading the optical disc.
To deal with the linux readahead bug, the ISO must be zero-padded before
burning. Cdrecord/wodim has such an option (see the above page).
Instead, I use the isopad script at
http://ftp.cs.utoronto.ca/pub/hugh/isopad
I put both the rawread and isopad scripts in ~/bin with execute
permissions so they're available as regular commands. My burning
procedure is:
1) Download DVD ISO, check its hash.
2) Pad the ISO with "isopad + dvd.iso".
3) Burn with command
growisofs -dvd-compat -speed=1 -Z /dev/dvd=dvd.iso
(preferably as root on an unloaded machine to give it every advantage).
4) Verify the burn with "rawread /dev/dvd | sha256sum" (should give the
hash of the UNpadded ISO), or do a mediacheck.
14 years, 2 months
Re: Kde4 question re desktop menu items.
by George R Goffe
Kevin,
I must apologize for not responding to your earlier post in a timely manor, I had system problems on a different system with the radeon driver which is still broken for me.
With kde 3 I was able to define the right button in the desktop to bring up the desktop menu where I put "save session" for example, and the middle button in the desktop to bring up the application menu; the left button in the desktop was a no-op. This was in effect for all desktops; I usually have 6 or more configured. It looks like kde4 has enabled each desktop it's own config options. There's no global setting available?
I'm in the middle of configuring kde4 now and am quite lost but making some progress. RTFM if you will. It's slow and not at all intuitive based on kde 3 that I'm more familiar with. Sigh.
Is there a document somewhere that maps what you could do with kde 3 to where it is now in kde 4 by any chance?
Regards,
George...
"It's not what you know that hurts you, It's what you know that ain't so." Wil Rogers
14 years, 2 months
Sound lockup if gdm pulseaudio enabled
by Neil Bird
I've been having various issues with pulseaudio since upgrading my F10
box to F12 recently (it was previously working fine).
The core issue seems to have been worked around my my disabling gdm
puleeaudio (via root's gconf-editor, as mentioned on a blog somewhere).
I'm concerned, though, that that's just masking the real issue.
Essentially, the issue is that, with gdm audio enabled, any normal user's
app. will hang when trying to generate sound. This made my login nearly
impossible as I have a couple of applets that 'tone' when logging in, and
this seemed (via the gnome panel?) to near-enough hang my entire session.
Is there something in particular I should be looking at, maybe
permissions-wise?
I did try running pulseadio with '-vvv' as recommended to see what was
what, but the only relevant thing I saw were timeout messages. The one
error I did see once was being unable to open a device via /dev, but the odd
code it was using as a filename didn't match what was there.
That may have been exacerbated by the fact that my wife was logged in at
the same time, and I seemed to find that when I restarted my pulse-audio
daemon, hers seemed to take over (even though not the active console) and
mine fell back to 'dummy output'. I had to log her out to get my audio
working OK (and then, oddly, logging in as her still let her use audio OK).
I haven't experimented to see if that oddity is still the case now I've
disabled gdm-audio, but it does all smack of off permissions to me.
--
[neil@fnx ~]# rm -f .signature
[neil@fnx ~]# ls -l .signature
ls: .signature: No such file or directory
[neil@fnx ~]# exit
14 years, 2 months
To F12 or not to F12
by Temlakos
Don Quixote de la Mancha wrote (in another thread, which I am trying to
break away from):
> On Tue, Mar 2, 2010 at 3:55 PM, John Mellor <john.mellor(a)gmail.com> wrote:
>
>> I think its all part of the insufficient testing problem that has dogged
>> F12 ever since it was released without being stabilized. Hopefully the
>> revised F13 qa automation and fixing of blocker anaconda bugs so that
>> testers can actually install the beta can resolve some of this...
>>
>
> When I upgraded from F10 to F11, I had a couple of significant
> problems. I don't recall now what they were, but they were very
> common problems whose solutions were well documented in the mailing
> lists.
>
> I have remained at F11 in part because it is working well, so I'm
> reluctant to risk screwing it up, and in part because I have gotten
> the general impression, by reading this very list, that F12 is screwed
> up in so many ways.
>
> I haven't made any effort to track that in a statistically sensible
> way. It's just that I read so many complaints about F12 being borked
> this way and that, that I have always felt it wise not to open that
> particular can of worms.
>
> What is your take - given F12's state of fixedness *right now* am I
> better off staying with F11, or upgrading to F12?
>
> When F13 comes out, would I be able to upgrade directly from F11 to
> F13, or will I have to pass through F12 on the way?
>
> In principle, I ought to be able to copy my whole F11 installation
> into a VirtualBox virtual hard disk, then try upgrading that just to
> see if it would work. I've actually been considering doing so,
> because I have so very many packages installed now, that if there was
> still any kind of pervasive brokenness, attempting to upgrade would
> screw the pooch but good.
>
> Thank You For Any Insight You Can Give Me,
>
> Don Quixote
>
Well, I might be the best person to ask, because as I see it, I have no
choice: I stopped at FC6, and I now realize that my hardware is
hopelessly obsolete and can't handle the ever-more-complex Javascript
that is a part of half the Web these days, especially the social sites
Digg.com, Propeller.com, Buzz.Yahoo.com, and, of course, the
incomparable Twitter.com. (Not to mention Examiner.com, where I write
regularly, and where I am informed that I am using a version of Firefox
that is long since obsolete, and have found that I cannot upgrade it
effectively without upgrading my OS.)
So I have to go to F12--happily, with new hardware, so that I can keep
the old setup around as a backstop. I would, of course, be pulling in
the most current versions of all the packages, and that would help. But
the main thing is that I would start relatively "clean." I also
appreciate having a live CD to work with.
Now what I really would appreciate is a place to go to learn how to use
the one thing that would allow me to use a handful of tiny Windows
freeware apps that I have acquired along the way--i.e., WINE.
Temlakos
14 years, 2 months