Is the standard Arch kernel preemtible?

Hi,
in the process of reporting a bug I posted a uname -a which included the text PREEMPT and was then asked if I was "running with CONFIG_PREEMPT (Preemptible Kernel)". I am using the standard Arch kernel, is it a preemtible kernel?
Thanks, Jamie

[dieter@gibran ~]$ zgrep CONFIG_PREEMPT /proc/config.gz
CONFIG_PREEMPT_NOTIFIERS=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y
# CONFIG_PREEMPT_TRACER is not set
Next!

Similar Messages

Can't boot standard Arch Kernel (root btrfs partition)

For a long time I using linux-mainline from AUR. Unfortunately Docker don't work on it. I tried to boot standard Arch kernel 3.17 from testing but i have got:
:: running early hook [udev]
Warning: /lib/modules/3.17.0-1-ARCH/modules.devname not found - ignoring
:: running hook [udev]
:: Triggering uevents..
Scanning for Btrfs filesystems
Waiting 10 seconds for device /dev/disk/by-uuid/(uuid)
ERROR: device 'UUID=(uuid)' not found. Skipping
ERROR: Unable to find root device 'UUID=(uuid)' .
I am using rEFInd to boot. This is config file of kernel:
"Boot with defaults" "root=UUID=3c5d33c2-1d2f-4c57-b226-ad7ecc51be00 rootfstype=btrfs rw"
"Boot to text mode" "root=UUID=3c5d33c2-1d2f-4c57-b226-ad7ecc51be00 rootfstype=btrfs rw systemd.unit=multi-user.target"
I tied to downgrade kernel to last stable version but it not helped.
Last edited by portals (2014-10-07 12:06:08)

I uncommented the testing repo and pacman -Syu. i tried downgrade to standard repo but it did not help. I have not used standard kernel for more then half year.

TRIM command (as it applies to SSD) and the vanilla arch kernel

According to this wikipedia article, the TRIM command has been implemented in Linux since kernel version 2.6.28. I'm wondering if the vanilla Arch kernel (x86_64) has support for this compiled in and if so which module would one need to modprobe to use it?
Thanks!

graysky wrote:hmmmm... is NOMMU_INITIAL_TRIM_EXCESS the so-called "TRIM" support in the kernel?
I don't think so, that seems to be memory (ram) related (NOMMU.... MMU is related to memory access as far as I know).
All I could find with a quick google search were a few posts saying there are submitted patches and some scripts .... nothing too certain.
As always things seem to be going at the windows development speed instead of the pace technology could go, also it seems that the spec for the trim command is/was still being finalized.
http://www.linuxquestions.org/questions … ux-713006/
http://marc.info/?l=linux-kernel&m=124169431911648&w=2
http://forum.soft32.com/linux/Linux-ATA … 83626.html
http://www.ocztechnologyforum.com/forum … fb&t=60882

Modifying the stock arch linux kernel and kernel timer frequency

so if i understand correctly, if we want to modify the stock arch linux kernel, we have to pull it off of abs. ie "ABSROOT=. abs core/linux" then modify the pkgbuild, uncommenting out make menuconfig and setting the pkgbase name to something different than stock. ie, "linux-custom" then update the checksums followed by importing the gpg keys, ie "gpg --recv-keys 79BE3E4300411886 and gpg --recv-keys 38DBBDC86092693E" for the kernel and patches. then run makepkg -s.
we can't just run make menuconfig on the current kernel that's installed?
and if we pull the linux kernel from abs to customize, does it already come preconfigured with all the arch changes and settings? like its no different than the current one installed?
i just ask because for the most part, i like the current arch kernel, there are just a few minor things i want to change but kept everything else the same as stock arch linux kernel.
also, i herd arch uses 300hz for its timer. whats the benefits and disadvantage of using 300hz over 1000hz for a desktop system?

orlfman wrote:we can't just run make menuconfig on the current kernel that's installed?
No you can't, because the kernel then has to be compiled so the kernel will run with the different tick rate.
orlfman wrote:
and if we pull the linux kernel from abs to customize, does it already come preconfigured with all the arch changes and settings? like its no different than the current one installed?
i just ask because for the most part, i like the current arch kernel, there are just a few minor things i want to change but kept everything else the same as stock arch linux kernel.
As I understand it from the Wiki, the ABS pulls the PKGBUILD and other arch-specific sources from the ArchLinux script server. However, I don't use the ABS, but pull the files I need directly from the ArchLinux SVN and build using makepkg[1] after making the necessary changes.
orlfman wrote:Also, I heard arch uses 300hz for its timer. whats the benefits and disadvantage of using 300hz over 1000hz for a desktop system?
You're in for a technical discussion here. This has a reasonably friendly discussion on kernel tick rates.
Basically, higher tick rates = a higher level of timing precision & higher processor load, lower tick rates = lower level of timing precision & lower processor load.
[1] Technically, I use the clean chroot manager package, which is a wrapper for makechrootpkg (which in turn is a wrapper for running makepkg in a clean chroot if I'm not mistaken).

Why no bootsplash or fbsplash in arch kernel?

I'm not begging for a feature, if I wanted it I'd compile it myself, but I was genuinely wondering, why no bootsplash or fbsplash patches applied to the default arch kernel?
If a splash patch is included in the kernel, it doesn't have to be used if the user doesn't want, right? And bootsplash has been around for quite some time, and every time I used it it felt like stable software (as in, I had no problems with it). Now I never tried fbsplash, but why not include one of them?
I'm sure there's a good reason not to have arch patch the default kernel with either patch, I was just wondering what it is.

Amazingly, people use Arch on their laptops too.
IE Me, So I am constantly rebooting, software suspend isnt worth the effort when I boot up in under a minute.
bootsplash is also nice when you want to do some console based work, or operate entirely from the console.
As has been said, bootsplash isnt included because of Arch's keep it simple philosophy, developers only patch the kernel with what they need, no more.
Another reason, could well be that the patches are not well maintained, take a look at bootsplash.org, no recent kernels have patches. Sure bootsplash.de have them, but they always arent out until even a few weeks after the kernel.
And finally, compiling the kernel with either bootsplash or fbsplash would stop a user from having a choice between the two.
iphitus

[SOLVED] How to view the *exact* name of the currently running kernel?

Perhaps this question will seem dumb, but here goes : I have two kernels installed :
[ruben@arch ~]$ yaourt -Q linux
core/linux 3.2.9-1 (base)
[ruben@arch ~]$ yaourt -Q linux-ck-kx
repo-ck/linux-ck-kx 3.2.11-1 (ck-kx)
Grub’s menu.lst is configured to boot linux-ck-kx :
# general configuration:
timeout 5
default 2
color light-blue/black light-cyan/blue
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/archroot ro
initrd /boot/kernel26.img
# (1) Arch Linux Fallback
title Arch Linux Fallback
root (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-label/archroot ro
initrd /boot/kernel26-fallback.img
# (2) Arch Linux CK-KX
title Arch Linux CK-KX
root (hd0,0)
kernel /boot/vmlinuz-linux-ck root=/dev/disk/by-label/archroot ro
initrd /boot/initramfs-linux-ck.img
# (3) Arch Linux CK-KX Fallback
title Arch Linux CK-KX Fallback
root (hd0,0)
kernel /boot/vmlinuz-linux-ck root=/dev/disk/by-label/archroot ro
initrd /boot/initramfs-linux-ck-fallback.img
And yet, I see no mention of *-ck-kx when issuing this comand :
[ruben@arch ~]$ uname -a
Linux arch 3.2.9-1-ARCH #1 SMP PREEMPT Thu Mar 1 09:31:13 CET 2012 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
It does not matter whether I change the default kernel line in /boot/grub/menu.lst : I can set it to “ 0 ” or “ 2 ” and reboot, and the output of “ uname -a ” will always be exactly the same as above ; no mention of *ck-kx even though I know it is running.
I searched the web on how to view the name of the running kernel, all results I found said to use uname, so is there another command I am missing here ? Or is it normal that both my kernels yield the same uname output ?
Just curious, because I was playing around with kexec, and when doing “ fake ” reboots, I was alternating between the normal ARCH-kernel and the ck-kx*kernel, and I wanted to be sure that it actually worked, so I checked everytime with uname, and since I saw no difference in the outputs, I assumed kexec wasn’t working like it should, so I did a “ real ” reboot, but same uname outputs… So I must be missing something…
Here are the kexec commands I used, just to be sure I am doing this properly :
[ruben@arch ~]$ sudo kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initramfs-linux-ck.img /boot/vmlinuz-linux-ck
[ruben@arch ~]$ sudo init 6
and :
[ruben@arch ~]$ sudo kexec -l --append="`cat /proc/cmdline`" --initrd=/boot/initramfs-linux.img /boot/vmlinuz-linux
[ruben@arch ~]$ sudo init 6
Thoughts ?
Last edited by Montague (2012-03-15 22:00:02)

litemotiv wrote:
Hmm worksforme:
$ uname -r
3.2.11-1-ck
One question for you litemotiv : do you have two kernels currently installed on your system, like I do, or did you uninstall the ARCH-kernel ? I ask because I might try this :
$ sudo pacman -Rns linux
and reboot, and see what happens…
But before I do that, might as well try to debug it ;
t1nk3r3r wrote:I would point the finger at GRUB, or something occuring near boot-time.
https://wiki.archlinux.org/index.php/Boot_Debugging
So I tried the “ Heavy Debug ” option, rebooted, then issued “ dmesg > dmesg.txt ” ; here are the first few lines of that file :
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.2.9-1-ARCH (tobias@T-POWA-LX) (gcc version 4.6.2 20120120 (prerelease) (GCC) ) #1 SMP PREEMPT Thu Mar 1 09:31:13 CET 2012
[ 0.000000] Command line: root=/dev/disk/by-label/archroot ro
and the complete dmesg output is here. I am no expert at reading debuggin output, but from the above, it seems like the default ARCH-kernel is being booted, even though my menu.lst hasn’t changed from my previous post (exept for the debugging options) :
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# (0) Arch Linux CK-KX
title Arch Linux CK-KX
root (hd0,0)
kernel /boot/vmlinuz-linux-ck root=/dev/disk/by-label/archroot ro rootdelay=5 panic=10 debug ignore_loglevel
initrd /boot/initramfs-linux-ck.img
# (1) Arch Linux CK-KX Fallback
title Arch Linux CK-KX Fallback
root (hd0,0)
kernel /boot/vmlinuz-linux-ck root=/dev/disk/by-label/archroot ro
initrd /boot/initramfs-linux-ck-fallback.img
I want the ck-kernel to boot, what it going on here ? Any more thoughts ?

Arch kernel with PAE

I asked some times ago about including PAE (HIGHMEM) in the offical Arch Kernel in x86 and i was said no beceause it is slower and when i want more than 4gb memory i should use x86_64
now i seen. 32bit is not slower with PAE. Only the stuff over 3GB is slower than with 64bit.
So the argoument PAE is slower is nonsense beceause the memory which is accessed slower is not existing without PAE so we have the choose between
No Memory over 3GB
Slow Memory over 3GB or lemme say not fast as it can be
the first 3GB are the same speed with and without PAE so maybe we should re-think about this
Last edited by Vamp898 (2009-10-20 00:32:29)

Allan wrote:
That is very strange (and dare I say wrong) given how PAE works... it is not as if it uses it memory mapping only when needing greater than 3Gb of memory, it needs to use it all the time: http://en.wikipedia.org/wiki/Physical_Address_Extension
And here is the only real attempt at benchmarks I have seen. Although it is a bit old...
http://people.redhat.com/nmurray/RHEL-2.1-VM-whitepaper.pdf wrote:The performance impact is highly workload dependent, but on a fairly typical kernel
compile, the PAE penalty works out to be around a 1% performance hit on Red
Hat's test boxes. Testing with various other workload mixes has given performance
hits ranging from 0% to 10%.
wow its really a bit old and i dont know how it was tested
is there a really good way to benchmark it?
i just written a bash skript which pumped up the memory and taked the time until it needed to reach 3,8GB
Last edited by Vamp898 (2009-10-20 02:30:17)

[SOLVED] Where can I browse the Arch kernel source?

I tried to look for the kernel source code under /usr/src/linux-3.4.9-1-ARCH but there's only a binary file (an image?) vmlinuz in there. I wanted to look for drivers concerning usb for fun, but I can't seem to find the excact location of the kernel source code.
Last edited by burninate (2012-08-25 09:48:56)

Sure you can, but it'll pretty much be the same as if you downloaded the code from kernel.org. You can use makepkg and the ABS to easily get the source and Arch's patch(es) on your computer.
Edit: If you have linux-headers installed, then the path HalosGhost refers to has the headers, not the full source
Last edited by SidK (2012-08-22 19:29:08)

Paragon's NTFS (ufsd) and the 3.14.3-2-ARCH kernel

So I was hoping to try out the ufsd module to compare it against ntfs-3g (which is being slow, as always) and it looks like it doesn't compile with the current kernel. Last working kernel reported on the AUR page is 3.12, so I had to edit the PKGFILE to allow <3.15 to test it, and if fails:
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/home/user/Downloads/ufsd-module/src//ifslinux/ufsdvfs.c:4059:42: error: invalid operands to binary != (have ‘kuid_t’ and ‘kuid_t’)
if ( (ia_valid & ATTR_UID) && i->i_uid != attr->ia_uid ) {
^
/home/user/Downloads/ufsd-module/src//ifslinux/ufsdvfs.c:4064:42: error: invalid operands to binary != (have ‘kgid_t’ and ‘kgid_t’)
if ( (ia_valid & ATTR_GID) && i->i_gid != attr->ia_gid ) {
/home/user/Downloads/ufsd-module/src//ifslinux/ufsdvfs.c:4734:11: error: too many arguments to function ‘posix_acl_chmod’
err = posix_acl_chmod( &acl, GFP_KERNEL, i->i_mode );
/home/user/Downloads/ufsd-module/src//ifslinux/ufsdvfs.c:580:49: error: invalid operands to binary == (have ‘kuid_t’ and ‘kuid_t’)
#define is_owner_or_cap(i) ( (current_fsuid() == (i)->i_uid) || capable(CAP_FOWNER) )
There are a lot more of them. I'm assuming it's because the package needs to be modified for the current kernel, but just in case, does it compile for anyone else?
Seeing as the package is an orphan, I guess not =/

IMHO, yes. it is worth if you are transferring multi GiB files daily and are fed up with the slowness and high cpu usage of the fuse alternative.
I found this post where somebody ports it to 3.13 and i updated the patch to work on 3.14.5 (the current kernel):
--- ifslinux/ufsdvfs.c 2013-10-17 09:51:32.000000000 -0400
+++ src/ifslinux/ufsdvfs.c 2014-06-08 10:56:36.084222623 -0400
@@ -577,7 +577,7 @@
#endif
#ifndef is_owner_or_cap
- #define is_owner_or_cap(i) ( (current_fsuid() == (i)->i_uid) || capable(CAP_FOWNER) )
+ #define is_owner_or_cap(i) ( (uid_eq(current_fsuid(), (i)->i_uid)) || capable(CAP_FOWNER) )
#endif
@@ -3894,7 +3894,7 @@
unsigned int ia_valid = attr->ia_valid;
DebugTrace(+1, Dbg, ("setattr(%x): r=%lx, uid=%d,gid=%d,m=%o,sz=%llx,%llx\n",
- ia_valid, i->i_ino, i->i_uid, i->i_gid, i->i_mode,
+ ia_valid, i->i_ino, __kuid_val(i->i_uid), __kgid_val(i->i_gid), i->i_mode,
u->mmu, (UINT64)i_size_read(i) ));
err = inode_change_ok( i, attr );
@@ -4056,12 +4056,12 @@
// Do smart setattr_copy
- if ( (ia_valid & ATTR_UID) && i->i_uid != attr->ia_uid ) {
+ if ( (ia_valid & ATTR_UID) && !uid_eq(i->i_uid, attr->ia_uid) ) {
dirty = 1;
i->i_uid = attr->ia_uid;
u->set_mode = 1;
- if ( (ia_valid & ATTR_GID) && i->i_gid != attr->ia_gid ) {
+ if ( (ia_valid & ATTR_GID) && !gid_eq(i->i_gid, attr->ia_gid) ) {
dirty = 1;
i->i_gid = attr->ia_gid;
u->set_mode = 1;
@@ -4102,7 +4102,7 @@
mark_inode_dirty( i );
DebugTrace(-1, Dbg, ("setattr -> %d, uid=%d,gid=%d,m=%o,sz=%llx,%llx%s\n", err,
- i->i_uid, i->i_gid, i->i_mode,
+ __kuid_val(i->i_uid), __kgid_val(i->i_gid), i->i_mode,
u->mmu, (UINT64)i_size_read(i), FlagOn(i->i_state, I_DIRTY)?",d":"" ));
return err;
@@ -4731,7 +4731,7 @@
err = PTR_ERR(acl);
else {
#if defined HAVE_DECL_POSIX_ACL_CHMOD && HAVE_DECL_POSIX_ACL_CHMOD
- err = posix_acl_chmod( &acl, GFP_KERNEL, i->i_mode );
+ err = __posix_acl_chmod( &acl, GFP_KERNEL, i->i_mode );
if ( err )
return err;
err = ufsd_set_acl( i, ACL_TYPE_ACCESS, acl );
@@ -9083,8 +9083,8 @@
// Setup 'uid' and 'gid'
- i->i_uid = unlikely(sbi->options.uid)? sbi->options.fs_uid : cr? cr->uid : p->Info.is_ugm? p->Info.uid : sbi->options.fs_uid;
- i->i_gid = unlikely(sbi->options.gid)? sbi->options.fs_gid : cr? cr->gid : p->Info.is_ugm? p->Info.gid : sbi->options.fs_gid;
+ i->i_uid = KUIDT_INIT(unlikely(sbi->options.uid)? sbi->options.fs_uid : cr? cr->uid : p->Info.is_ugm? p->Info.uid : sbi->options.fs_uid);
+ i->i_gid = KGIDT_INIT(unlikely(sbi->options.gid)? sbi->options.fs_gid : cr? cr->gid : p->Info.is_ugm? p->Info.gid : sbi->options.fs_gid);
// Setup 'mode'
@@ -9256,11 +9256,11 @@
if ( NULL != cr ) {
- cr->uid = current_fsuid();
+ cr->uid = __kuid_val(current_fsuid());
if ( !(dir->i_mode & S_ISGID) )
- cr->gid = current_fsgid();
+ cr->gid = __kgid_val(current_fsgid());
else {
- cr->gid = dir->i_gid;
+ cr->gid = __kgid_val(dir->i_gid);
if ( S_ISDIR(cr->mode) )
cr->mode |= S_ISGID;
@@ -9359,7 +9359,7 @@
posix_acl_mode mode;
if ( !S_ISDIR( i->i_mode ) || 0 == ( err = ufsd_set_acl( i, ACL_TYPE_DEFAULT, acl ) ) ) {
#if defined HAVE_DECL_POSIX_ACL_CREATE && HAVE_DECL_POSIX_ACL_CREATE
- err = posix_acl_create( &acl, GFP_KERNEL, &mode );
+ err = __posix_acl_create( &acl, GFP_KERNEL, &mode );
if ( err >= 0 ) {
i->i_mode = mode;
if ( err > 0 )
@@ -10260,7 +10260,7 @@
TIMESPEC_SECONDS( &i->i_atime ) == u->atime? NULL : &i->i_atime,
TIMESPEC_SECONDS( &i->i_mtime ) == u->mtime? NULL : &i->i_mtime,
TIMESPEC_SECONDS( &i->i_ctime ) == u->ctime? NULL : &i->i_ctime,
- &i->i_gid, &i->i_uid, u->set_mode? &i->i_mode : NULL );
+ &i->i_gid.val, &i->i_uid.val, u->set_mode? &i->i_mode : NULL );
u->atime = TIMESPEC_SECONDS( &i->i_atime );
u->mtime = TIMESPEC_SECONDS( &i->i_mtime );
u->ctime = TIMESPEC_SECONDS( &i->i_ctime );
@@ -11638,8 +11638,8 @@
assert( NULL != current->fs );
- opts->fs_uid = current_uid();
- opts->fs_gid = current_gid();
+ opts->fs_uid = __kuid_val(current_uid());
+ opts->fs_gid = __kgid_val(current_gid());
opts->fs_fmask = opts->fs_dmask = NULL == current->fs
? -1
@@ -12255,7 +12255,7 @@
// Done.
DebugTrace(-1, Dbg, ("read_super(%s), %u -> sb=%p,i=%p,r=%lx,uid=%d,gid=%d,m=%o\n", DevName, jiffies_to_msecs(jiffies-StartJiffies), sb, i,
- i->i_ino, i->i_uid, i->i_gid, i->i_mode ));
+ i->i_ino, __kuid_val(i->i_uid), __kgid_val(i->i_gid), i->i_mode ));
return 0;
Compiles fine and can load the ufsd module and mount a partition. Haven't done real world testing as i am investigating on how to make it the default on KDE (it uses ntfs-3g or the old ntfs kernel module).
Last edited by codestation (2014-06-08 16:43:09)

How to upgrade a custom built kernel to the main arch linux package?

How do you upgrade from a custom built kernel from the abs to the current release kernel from a package ? I have tried to do pacman -S linux linux-headers linux-firmware but still keep getting the old kernel i built my self.
[root@HLA boot]# pacman -S linux linux-firmware linux-api-headers linux-headers
warning: linux-3.14.6-1 is up to date -- reinstalling
warning: linux-firmware-20140316.dec41bc-1 is up to date -- reinstalling
warning: linux-api-headers-3.14.1-1 is up to date -- reinstalling
warning: linux-headers-3.14.6-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (4): linux-3.14.6-1 linux-api-headers-3.14.1-1
linux-firmware-20140316.dec41bc-1 linux-headers-3.14.6-1

It says it is reinstalling them. Doesn't it say it ? or am I missing something ? (no I'm not trying to sound sarcastic, honestly)
warning: linux-3.14.6-1 is up to date -- reinstalling
warning: linux-firmware-20140316.dec41bc-1 is up to date -- reinstalling
warning: linux-api-headers-3.14.1-1 is up to date -- reinstalling
warning: linux-headers-3.14.6-1 is up to date -- reinstalling
Total Installed Size: 167.78 MiB
Net Upgrade Size: 0.00 MiB
[root@HLA boot]# pacman -S linux linux-firmware linux-api-headers linux-headers
warning: linux-3.14.6-1 is up to date -- reinstalling
warning: linux-firmware-20140316.dec41bc-1 is up to date -- reinstalling
warning: linux-api-headers-3.14.1-1 is up to date -- reinstalling
warning: linux-headers-3.14.6-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Packages (4): linux-3.14.6-1 linux-api-headers-3.14.1-1
linux-firmware-20140316.dec41bc-1 linux-headers-3.14.6-1
Total Installed Size: 167.78 MiB
Net Upgrade Size: 0.00 MiB
Last edited by dslink (2014-06-22 03:30:28)

[SOLVED] Arch Kernel causes problems

Since my very first time installing Arch, i was getting some errors like
Cannot parse block device ids for /dev/sdb2
Cannot find root device /dev/sdb2
and eventually i had found a work-around, by taking the kernel and initramfs files (both 2.6.25.20-114) from another Linux, and also the corresponding modules directory. (Works perfect, using Firefox on it at the moment.)
Now i want to upgrade my kernel eventually (don't have to actually, but i want to, and the problem should not happen anyway) and still, after retrieving the new kernel through pacman (creating the vmlinuz26 and kernel26.img files in /boot, as well as the modules directory) and using it, i get the SAME problem.
The Arch kernels just won't work for me...
Does anyone have an idea what it could be?
(And is there any way to copy the exact error-output i get while trying to boot?)
Thanks.
Last edited by TaylanUB (2009-10-18 03:23:36)

I'm using ext2 on the second partition (first being FAT32) of a Lexar USB Flash Stick.
# lspci
00:00.0 Host bridge: nVidia Corporation nForce2 IGP2 (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation MCP2A ISA bridge (rev a3)
00:01.1 SMBus: nVidia Corporation MCP2A SMBus (rev a1)
00:02.0 USB Controller: nVidia Corporation MCP2A USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation MCP2A USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation MCP2A USB Controller (rev a2)
00:04.0 Bridge: nVidia Corporation MCP2A Ethernet Controller (rev a3)
00:06.0 Multimedia audio controller: nVidia Corporation MCP2S AC'97 Audio Controller (rev a1)
00:08.0 PCI bridge: nVidia Corporation MCP2A PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation MCP2A IDE (rev a3)
00:0b.0 IDE interface: nVidia Corporation nForce2 Serial ATA Controller (rev a3)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9550]
01:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)
02:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev 46)
# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 05dc:a781 Lexar Media, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Last edited by TaylanUB (2009-10-17 11:47:41)

How to set the default boot kernel in /etc/default/grub or /etc/grub.d

and without messing with /boot/grub/grub.cfg ?
I need this so that new kernels show up but do not change the default boot kernel
Is there a way to do it by file name instead of position within the menuentry / submenu list?
I found some ubuntu and fedora sugestions but all by position, none by name
AND how to set the kdump kernel as the default?
Arch is putting this kernel under a submenu - would this pose problems for setting it as the default?
Last edited by Sanjeev K Sharma (2015-04-06 12:59:22)

Sanjeev K Sharma wrote:
and without messing with /boot/grub/grub.cfg ?
I need this so that new kernels show up but do not change the default boot kernel
Is there a way to do it by file name instead of position within the menuentry / submenu list?
I found some ubuntu and fedora sugestions but all by position, none by name
AND how to set the kdump kernel as the default?
Arch is putting this kernel under a submenu - would this pose problems for setting it as the default?
In /etc/default/grub you can use the name of your entry you wish to use as default
GRUB_DEFAULT='Arch Linux, with Linux core repo kernel'
You can tell grub to stop using submenus by doing:
GRUB_DISABLE_SUBMENU=y
Or you can just make a purely custom menuentry in /etc/grub.d/40_custom if you'd like:
menuentry "Other Linux" {
linux <KERNEL IMAGE HERE>
initrd <INITRD IMAGE HERE>
EDIT: /etc/grub/default -> /etc/default/grub
Last edited by Slabity (2015-04-07 11:16:22)

[SOLVED] Can't build fglrx module for 3.4.5-1-ARCH kernel

Hello everyone!
I updated my system using
pacman -Syu --ignore glibc
everything was good, I rebooted and my fglrx module isn't working!
I tried:
sudo catalyst_build_module
Building fglrx module for 3.4.5-1-ARCH kernel ...
Failed!!! Check out log: /var/log/catalyst-install.log
Here is log
Here is quote from it: Kernel header files are absent: directory /lib/modules/3.3.4-1-ARCH/build doesn't exist! Game over
But I have the latest versions linux and linux-headers packages.
Help please. Thanks.
Last edited by metalex (2012-07-20 14:53:37)

Yes, this is my problem, I did all from here, but I still can't update glibc.
grep '^lib/' /var/lib/pacman/local/*/files
output:
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/ld-linux-x86-64.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libBrokenLocale.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libSegFault.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libanl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libc.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcidn.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libcrypt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libdl.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libm.so.6
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libmemusage.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnsl.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_compat.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_db.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_dns.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_files.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_hesiod.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nis.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libnss_nisplus.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpcprofile.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libpthread.so.0
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libresolv.so.2
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/librt.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db-1.0.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libthread_db.so.1
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil-2.16.so
/var/lib/pacman/local/glibc-2.16.0-1/files:lib/libutil.so.1
/var/lib/pacman/local/lib32-glibc-2.15-10/files:lib/
/var/lib/pacman/local/lib32-glibc-2.15-10/files:lib/ld-linux.so.2
I don't know what to do with lib32-glibc...

[SOLVED] Building fglrx module for 3.11.3-1-ARCH kernel error

I got this error today:
2013-09-28 14:07:59
Building fglrx module for 3.11.2-1-ARCH kernel ...
OsVersion says: SMP=1
file /proc/kallsyms says: SMP=1
file /usr/lib/modules/3.11.2-1-ARCH/build/include/generated/autoconf.h says: SMP=1
file /usr/lib/modules/3.11.2-1-ARCH/build/include/generated/autoconf.h says: MODVERSIONS=1
file /usr/lib/modules/3.11.2-1-ARCH/build/arch/x86/include/asm/compat.h says: COMPAT_ALLOC_USER_SPACE=arch_compat_alloc_user_space
make: Entering directory `/usr/src/linux-3.11.2-1-ARCH'
CC [M] /tmp/catalyst.aHP3fa/firegl_public.o
CC [M] /tmp/catalyst.aHP3fa/kcl_acpi.o
CC [M] /tmp/catalyst.aHP3fa/kcl_agp.o
CC [M] /tmp/catalyst.aHP3fa/kcl_debug.o
CC [M] /tmp/catalyst.aHP3fa/kcl_ioctl.o
CC [M] /tmp/catalyst.aHP3fa/kcl_io.o
CC [M] /tmp/catalyst.aHP3fa/kcl_pci.o
CC [M] /tmp/catalyst.aHP3fa/kcl_str.o
CC [M] /tmp/catalyst.aHP3fa/kcl_iommu.o
CC [M] /tmp/catalyst.aHP3fa/kcl.o
CC [M] /tmp/catalyst.aHP3fa/kcl_wait.o
LD [M] /tmp/catalyst.aHP3fa/fglrx.o
Building modules, stage 2.
MODPOST 1 modules
CC /tmp/catalyst.aHP3fa/fglrx.mod.o
LD [M] /tmp/catalyst.aHP3fa/fglrx.ko
make: Leaving directory `/usr/src/linux-3.11.2-1-ARCH'
Ok.
2013-10-05 14:20:34
Building fglrx module for 3.11.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.11.3-1-ARCH/build doesn't exist! Game over
2013-10-05 14:20:41
Building fglrx module for 3.11.3-1-ARCH kernel ...
Kernel header files are absent: directory /usr/lib/modules/3.11.3-1-ARCH/build doesn't exist! Game over
I don't know why, and I do not know if I care.
Last edited by patrickmaciel (2013-10-06 19:31:53)

fazo96 wrote:I think it's because of the new kernel. Reinstalling is not a solution, it's avoiding the problem ;D
Instead, I switched to catalyst-hook (I used catalyst) and upgraded to kernel 3.11.4, the latest version of xorg (there was a new one), gnome 3.10 and the module compiled perfectly, so now everything works on my system
You right, but you know... I have a lot projects in queue and not have time to search and test evertying
But, now... catalyst has installed successfully, but, I think isn't working 100%, because, when I click (for example), in a Google Chrome tab, and move to left/right, all tabs disappear or are blurry.
Anyway, thanks.

[SOLVED] Arch Kernel Configuration

Hi, I'd like to compile recompile the Kernel but I would like to know wich are the default configuration settings that the compiled kernel26 of the core repository has. I would like to tweak some things but starting from that configuration not from the defaul Kernel configuration found in www.kernel.org.
I would like to know it ABS could be used to do it, or if I can get a configuration file somewhere and use it with ABS.
Thank you very much.
Last edited by KaoDome (2009-01-14 00:24:56)

KaoDome wrote:
Ok thank you very much! I've found the configuration within the ABS package. The I can edit it running make menuconfig (or the GUI configurator) and then save the edited file as config (in my case, if it was a x84_64 it would be config.x86_64.
I had to change the checksum for that file in the PKGBUILD file in order to it to work.
It's now compiling!
Another question... Does it uses the CFLAGS defined in /etc/makepkg.conf when compiling the Kernel? I hope so...
Once more, thank you very much for all!
You can also use the ABS PKGBUILD, and add the "make menuconfig" option to be able to change the -ARCH settings.... then when you press exit it will save (and use) your newly created .config.
# load configuration
make menuconfig
# build!
So it will load the default -ARCH generic setup and then you can modify to your hardware specs.
My AMD64 300HZ -Os Low-Latency kernel:
$ uname -osrpmi
Linux 2.6.28-ARCHtestAMD x86_64 AMD Turion(tm) 64 X2 Mobile Technology TL-60 AuthenticAMD GNU/Linux
Last edited by methuselah (2009-01-14 18:58:30)

Is the standard Arch kernel preemtible?

Similar Messages

Maybe you are looking for