Lately when Fedora 12 updates the kernel it defaults to the last kernel entry and not the newest one. However I set grub to boot entry 0 as the default which is allways the new kernel. It runs like this fine until the kernel updates then it seems to change from 0 to 1 on its own is this a new planned aspect of the new kernel being installed?
View 14 RepliesI have manually added an entry for Ubuntu in my grub menu, using Yast. But every time the kernel is updated, this entry disappears. On the other hand, the one for Windows, that was added during OpenSuse's installation, is still there. So how can I keep this entry for Ubuntu ?
Edit : when I save the menu configuration in Yast, I get the following message :
Code:
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...
kbuildsycoca4 running...
[Code]...
I want to avoid kernel id in Grub entry. I have searched before and one poster (can't find it again) posted a very simple Fedora Grub entry that just pointed to Fedoara's menu.lst. which worked.
For Suse I use:
title openSUSE 11.1 (on /dev/sda7) by symlinks
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 splash=silent showopts vga=0x31a
initrd /boot/initrd
savedefault
boot
I nave tried:
title Fedora
root (hd0,4)
rootnoverify (hd0,4)
chainloader +1
Where Fedora is on sda5 but, doesn't work for some reason.
i think i have found a bug in the unix ACL permissions. I tested this problem in the Ubuntu 9.10 and in SLES 10 and 11, all of them with setfacl 2.2.47.
Well, I have done the following test:
1) Create a folder and set some named user, and set the same ACL entry for the Default ACL, like the following example:
Code:
mkdir dir1
setfacl -m u:rodrigo:rwx dir1/
setfacl -d -m u:rodrigo:rwx dir1/
getfacl dir1/
# file: dir1/
[Code].....
Note that some permissions are different from the ones in the Default ACL in the dir1/
why the file1's permissions are diferrent from the dir1's default ACL entries? Is this a bug?
is it possible in grub2, that a temporary default entry. For example i have 2 menuentry in grub.cfg 0 & 1. my default is 0 but i want to automatically boot once to 1 and it changes back to 0.
View 4 Replies View RelatedFrom F12 to F13. Is there anything I should remove before updating? I have few programs isntalled from source/binary installers in /usr for example. Would it cause problems?
And is there any chance to be able to switch from a 32 bit kernel to 64 bit kernel during the update? The hardware is capable of this.
I recently upgraded grub -> grub2 on my karmic box. Grub2 worked when chainloaded from legacy grub, and also the first time I tried it standalone. Both times the grub2 menu came up.
I ran vbeinfo at a grub2 command prompt, and found my monitor's native res listed - 1280x1024. I added that to my /etc/defaults/grub and then ran update-grub, and rebooted. This time no menu appeared and the default entry booted straight away. I suspected that the resolution was not supported for some reason or that the way I entered it in the config file was wrong, so I commented it out again in /etc/default/grub, and ran update-grub again - to no avail.
I have since tried lots of different formats for the GRUB_GFXMODE, such as 1280x1024@24, 1280x1024x24, and the normal 640x480, but none of them give me a grub menu. I have even tried using GRUB_TERMINAL=console, to no avail. I have checked the /boot/grub/grub.cfg file each time to make sure my changes were put there correctly by update-grub. I have also made sure that timeout was set to 10, and the hidden timeout was set to 0. My GRUB_CMDLINE_LINUX_DEFAULT="quiet".
I have reinstalled grub2, grub-pc, and grub-common, and I have dpkg-reconfigured them all too. I have no idea what to do to get my grub menu showing up again.
I just want to know what is the default Fedora 32 bit kernel - does it support more than 4G memory. I would like to save myself from compiling custom kernel and all following fiddling (nvidia drivers, virtualisation software etc) and 64bit OS is not for me - too many apps that I need are missing, of poor quality or need more manual intervention. Actually if bigmem / whatever it is called is configured in the default kernel, this may be the reason to switch. I intend to use 4 to 8 GB memory and it's a desktop, so server builds (like Ubuntu) are not for my taste.
View 2 Replies View RelatedWhen I boot Ubuntu 10.04 then at first the login screen appears with the main user
"Peter"
and
"other..."
In 99% of the cases I use "Peter" and have explicitely to click on Peter. Only then the password entry field appears and I can enter it.
This is somehow user unfriendly. Can I define somehow a default user (here: Peter) and show immediately the password entry field (and place the cursor inside)?
I have to add a new interrupt framework to the kernel (INT 81h). To add the interface descriptor to INT 81h I have to write to the IDT entry 81h. There are some functions of the kernel that can do this task but they can not be used in a module. So I will now do a patch to the kernel and don't know where to start.
Where is INT 80h interface descriptor written to the IDT? - So I could write it maybe the same way in the same function. Which GTD entry is used to write to the IDT (1, 2, 3 or ...) ? - So I can do some debugging.
I've just downloaded F11 i386 installation DVD. I installed it on my laptop and just now noticed that PAE kernel got installed. Isn't PAE for systems with RAM >3.2 GB? It's a pretty old laptop (P3, 256MB ram). So, is PAE kernel ok for me or should I reinstall from scratch and use some specific switches in the installer to get non-PAE kernel? I've also read that Yum doesn't recognize PAE packages dependencies and will install non-PAE kernel modules if I try to install let's say Nvidia driver or so.
View 11 Replies View RelatedI have a question about the Fedora 12 default kernel: Is it monolitic or is it a modular kernel? And how do I know witch none is it?
View 6 Replies View RelatedI have looked at the GNU GRUB Manual 1.99 at [URL] but I cannot find an explanation of what the kernel entry / command in the grub.conf file means. I get what's the meaning of that entry but where is described what it actually is and what are proper.
I suppose this entry / command was actual in GRUB Legacy, but I cannot find where it is described...
I have a sata card in my RHEL5 server that is not working. It has a 1.5tb hard drive attached to it that I would like to use. It seems that the 2.6.18 kernel did not detect and use it by default. I was able to find some info about the
lspci | grep VIA
03:06.0 RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID Controller (rev 50)
my own fault really,just dived in to do the update and did not back everything up. I have three disks in my machine one winxp for games , one was suse 11.2 and added lately one for ubuntu. added the ubuntu disk installed and this replaced the grub loader, still gave me all my previous options but does not look as nice as the suse one.so I did update on 11.2 and thought would give me the nice one back and still have all my entries. Er no. entry for win and 11.3 but no ubuntu.
View 7 Replies View RelatedI am running ubuntu 10.04 on an emac powerpc. I go to the update manager and click on 'Update to Ubuntu 10.10', and then it starts the update and everything goes well until step 2 which is setting new software channels. It displays the error message:
W: Failed to fetch httports.ubuntu.com/ubuntu-ports/dists/maverick/Release
Unable to find expected entry partner/binary-powerpc/Packages in Meta-index file (malformed Release file?)
,E:Some index files failed to download, they have been ignored, or old ones used instead.
Ubuntu's update manager recently updated the Grub menu.lst file. It let me decide if I wanted to keep my old menu.lst or the new one. After deciding that I was fine with the new one, I found out that I can no longer boot into Windows 7. I had previously edited menu.lst so that Windows would be at the top of the list, however, I didn't notice that this had put it into the automagic update area, and I realize now that I should have just edited what the default number was instead of moving around the entries.
Anyways, I can no longer access my Windows 7 OS via Grub, and I was wondering what sort of fix I can have for this. I've tried running update-grub, but it hasn't fixed the problem. The Windows bootloader is on the first partition of the only hard drive, as far as I can remember.
differences between Kernel Default and Kernel Desktop? I've found some past threads like this link and this other link, and some other google info, which suggest the only difference would be the io scheduler. Also, I see the default grub choice is "Desktop" and not "Default", so I take this as a suggestion to prefer one over the other.
However, my broadcom 4312 wireless only works on the "default" and not on the "desktop" kernel, so I guess there must be other differences. I just want to evaluate which one is the less long-term risk option to go.
I am receiving a transaction error when I try to update to a newer kernel, the error is:
Test Transaction Errors: installing package kernel-debug-2.6.32.16-150.fc12.i686 needs 519KB on the /boot filesystem If I run disk usage I get:
# du -h /boot
217K/boot/efi/EFI/redhat
219K/boot/efi/EFI
[code]....
System monitor shows I have 56% free in /boot. So where can I get the extra free space or force yum to recognize there is enough in that directory?
I'm using F13 and I would like to update my computer using yum update.
I did this a few weeks ago and yum update downloaded and installed
Quote:
kernel i686 2.6.34.7-61.fc13
After a reboot I got
Quote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
To get around this I did a ctrl + s and booted to an earlier kernel. Once in I deleted the latest kernel using
Quote:
rpm -q kernel
to list the available kernels and
Quote:
rpm -e kernel-version
to delete the latest kernel. Once deleted my computer starts up perfectly.
How do I run yum update without reinstalling the bad kernel?
I do not understand this problem. I am using kernel 2.6.35.10-74.fc14.i686.PAE and while that works fine I know new kernels makes things work better. As such, every time a kernel update comes along just like all other updates, I perform a yum update. But for some unknown reason, I am successfully updating everything except the kernel.
I have attempted updates with 2.6.35.11-83.fc14.i686.PAE, 88, and 12-90 and at the very beginning of the boot I always get the same panic error and boot freeze. The message is ALWAYS as foolow. The only part of the message that changes is the kernel numbers.
[I did my best at hand writing the error message.]
I hope this makes sense to someone.
MESSAGE:
Traceback (most recent call last):
File "/init" , line 157 , in <modules>
if _name_ == ' _main_ ' : main()
[Code]....
Does any of the above make any sense?? I cannot even figure how I am supposed to fix anything since the computer completely freezes at that point! I am, of course, able to hard reboot. The I switch back to the previous kernel and everything is fine but why does everything EXCEPT the kernel update?
I attempted to install the new kernel 2.6.29.6-217.2.3.fc11 (x86-64) A depsolv message appears:
Quote:
ERROR with rpm_check_debug vs depsolve:
kernel-uname-r = 2.6.27.19-170.2.35.fc10.x86_64 is needed by (installed) kmod-wl-2.6.27.19-170.2.35.fc10.x86_64-5.10.79.10-1.fc10.x86_64
kernel-uname-r = 2.6.27.21-170.2.56.fc10.x86_64 is needed by (installed) kmod-wl-2.6.27.21-170.2.56.fc10.x86_64-5.10.79.10-2.fc10.x86_64
[Code].....
I upgraded from fc10; there was a residue of four fc10 2.27 kernels in /lib/modules from my fc10->fc11 upgrade; I moved them to a new subdirectory /usr/oldmodules, but the yum update command still produces the same failure message.
even from a terminal it wouldn't update? Maybe because I put my bootsector as ro ?
I don't know here is the message:
When yum updates the kernel it keeps the last 3 versions; the older kernels are deleted. Is there a way to keep more than 3 versions?
I presently have one working version and two which are not compatible with my machine. One more bad version and my system will be toast. (I would like to keep the "bad" versions for testing.)
Last Saturday, I ran an update on my laptop using F12 and received a new kernel. As of this morning, the new kernel hasn't shown up on my desktop, using f 11. (Yes, I check every day.) Currently, my uptime is 34 days, so you can see how long it's been since the last kernel update for F11. Does anybody know why there'd be an update for one version and not for another? In case anybody's wondering:
[joe@khorlia ~]$ uname -r
2.6.30.10-105.2.23.fc11.i586
I'm using F13 64bit with the proprietary nvidea driver. From yesterday's software update, a new kernel was installed:
old kernel: vmlinuz-2.6.33.5-112.fc13.x86_64
old initramfs: initramfs-2.6.33.5-112.fc13.x86_64.img
new kernel: vmlinuz-2.6.33.5-124.fc13.x86_64
new initramfs: initramfs-2.6.33.5-124.fc13.x86_64.img
I load grub from another distro partition. After the update, I changed the two lines in menu.lst, as per the above mentioned, to match the new kernel.
The problem now is that after booting F13, my monitor displays a warning saying "video mode not supported".
These two files are now at /etc/x11:
xorg.conf.livna-config-backup:
# Xorg configuration created by livna-config-display
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
EndSection
[Code].....
I'm not sure if it's exactly the same issue as mine. In case it is, it looks like that all I have to do is:
1 - boot from the previous kernel, and
2 - code: "yum install akmod-nvidia"
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
View 5 Replies View Relatedwondering if fedora 15 users will get kernel 3.0 by update,, or is that a typicall update for FC16??
View 5 Replies View RelatedKeep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
I just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.
What can I do?