Kernel for base

Author: f | 2025-04-24

Initially, kernel-default-base and kernel-default were an 'additive set'. kernel-default was based on top of kernel-default-base and kernel-default did not include the content of kernel-default-base. It was not possible to use kernel-default without also having kernel-default-base installed (this was the case with SUSE Linux Enterprise Server

Bases for kernel-based spaces

Desktop Ubuntu corresponding to a number of desktop GUI preferences. All of these images are considered 'Classic' Ubuntu because they use debs as their base and may add snaps for specific packages or applications. The Ubuntu Core image is an all-snap edition of Ubuntu. It is unusual in that the base operating system itself is delivered as a snap; that makes it suitable for embedded appliances where all the possible apps that might need to be installed are available as strictly confined snaps. Ubuntu Core is an appliance or embedded oriented edition of Ubuntu, not particularly comfortable for humans but highly reliable and secure for large-scale appliance deployments such as IoT and CPE in the telco world. Canonical maintains multiple kernel packages for each LTS version of Ubuntu, which serve different purposes. Several of the kernel packages address the need for kernels with specific performance priorities, for example, the low-latency kernel package. Others are focused on optimisation for a particular hypervisor, for example, the kernel packages which are named after public clouds. You are recommended to use the detailed Ubuntu kernel guide to select the best Ubuntu kernel for your application. In general, all of the LTS kernel packages will use the same base version of the Linux kernel, for example, Ubuntu 20.04 LTS kernels typically used the 5.4 upstream Linux kernel as a base. Some cloud-specific kernels may use a newer version in order to benefit from improved mechanisms in performance or security that are material to that cloud.

Kernel for BASE - Kernel Data Recovery

Compiler Collection (base package)ii gcc-9-arm-linux-gnueabihf 9.3.0-17ubuntu1~20.04cross2 amd64 GNU C compiler (cross compiler for armhf architecture)ii gcc-9-arm-linux-gnueabihf-base:amd64 9.3.0-17ubuntu1~20.04cross2 amd64 GCC, the GNU Compiler Collection (base package)ii gcc-aarch64-linux-gnu 4:9.3.0-1ubuntu2 amd64 GNU C compiler for the arm64 architectureii gcc-arm-linux-gnueabihf 4:9.3.0-1ubuntu2 amd64 GNU C compiler for the armhf architectureii linux-base 4.5ubuntu3.7 all Linux image base packageii linux-firmware 1.187.26 all Firmware for Linux kernel driversii linux-generic-hwe-20.04 5.13.0.30.33~20.04.17 amd64 Complete Generic Linux kernel and headersii linux-headers-5.11.0-27-generic 5.11.0-27.29~20.04.1 amd64 Linux kernel headers for version 5.11.0 on 64 bit x86 SMPii linux-headers-5.11.0-46-generic 5.11.0-46.51~20.04.1 amd64 Linux kernel headers for version 5.11.0 on 64 bit x86 SMPii linux-headers-5.13.0-28-generic 5.13.0-28.31~20.04.1 amd64 Linux kernel headers for version 5.13.0 on 64 bit x86 SMPii linux-headers-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Linux kernel headers for version 5.13.0 on 64 bit x86 SMPii linux-headers-5.8.0-63-generic 5.8.0-63.71~20.04.1 amd64 Linux kernel headers for version 5.8.0 on 64 bit x86 SMPii linux-headers-generic-hwe-20.04 5.13.0.30.33~20.04.17 amd64 Generic Linux kernel headersii linux-hwe-5.11-headers-5.11.0-27 5.11.0-27.29~20.04.1 all Header files related to Linux kernel version 5.11.0ii linux-hwe-5.11-headers-5.11.0-46 5.11.0-46.51~20.04.1 all Header files related to Linux kernel version 5.11.0ii linux-hwe-5.13-headers-5.13.0-28 5.13.0-28.31~20.04.1 all Header files related to Linux kernel version 5.13.0ii linux-hwe-5.13-headers-5.13.0-30 5.13.0-30.33~20.04.1 all Header files related to Linux kernel version 5.13.0ii linux-hwe-5.8-headers-5.8.0-63 5.8.0-63.71~20.04.1 all Header files related to Linux kernel version 5.8.0rc linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 amd64 Signed kernel image genericii linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 amd64 Signed kernel image genericrc linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 amd64 Signed kernel image genericrc linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1 amd64 Signed kernel image genericrc linux-image-5.11.0-37-generic 5.11.0-37.41~20.04.2 amd64 Signed kernel image genericrc linux-image-5.11.0-38-generic 5.11.0-38.42~20.04.1 amd64 Signed kernel image genericrc linux-image-5.11.0-40-generic 5.11.0-40.44~20.04.2 amd64 Signed kernel image genericrc linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 amd64 Signed kernel image genericrc linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2 amd64 Signed kernel image genericrc linux-image-5.11.0-44-generic 5.11.0-44.48~20.04.2 amd64 Signed kernel image genericrc linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 amd64 Signed kernel image genericrc linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 amd64 Signed kernel image genericii linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 amd64 Signed kernel image genericii linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Signed kernel image genericrc linux-image-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64 Signed kernel image genericrc linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 amd64 Signed kernel image genericrc linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 amd64 Signed kernel image genericrc linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 amd64 Signed kernel image genericrc linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 amd64 Signed kernel image genericrc linux-image-5.8.0-63-generic 5.8.0-63.71~20.04.1 amd64 Signed kernel image genericii linux-image-generic-hwe-20.04 5.13.0.30.33~20.04.17 amd64 Generic Linux kernel imagerc linux-image-unsigned-5.11.1-051101-generic 5.11.1-051101.202103031212

Bases for kernel-based spaces - ScienceDirect

Part. This also ensures that you get the full benefit from any hybrid fixes, which as mentioned above require updates in both the kernel and application to function fully.Examples:Application buildKernel buildSupported?5.0.593.0 (AX2009 RTM)5.0.1500.6491 (AX 2009 SP1 RU8)NO (the application build is for RTM, whereas the kernel is for SP1)6.2.1000.4051 (AX2012 R2 CU7)6.2.1000.1437 (AX2012 R2 CU6)YES…but not recommended!(The kernel build is lower than the application build)6.3.164.0 (AX2012 R3 base)6.3.1000.930 (AX2012 R3 latest kernel*)YES (the kernel build is higher than the application build but both are for AX 2012 R3 with no service pack)* True at the time of writing. See Q10 below for ways to find the latest kernel.Q9: Is it supported to have different kernel builds for different AX components in the same environment?NO it is NOT supported. Customers should always apply the kernel fix to every AX component in the same environment. It’s possible that unexpected behaviour could result from a kernel mismatch. In the latest versions of AX, the AOS throws a warning message to the event logs (event 151) if a client tries to connect to it and has a different kernel version.The screenshot below is taken from the AX hotfix installer when applying a kernel fix for AX 2012 R2. It shows a list of all AX components that require updating (NOTE: ignore the checkboxes – only a few AX components were installed on my system, so some of the checkboxes were automatically disabled): Q10: I have found a hotfix for my issue, should I install the specific hotfix referenced by the KB article?Not always – if you are experiencing an issue that has been fixed in the AX kernel then download and install the very latest, kernel hotfix available for your product version and service pack.As mentioned above, kernel hotfixes are cumulative so it normally. Initially, kernel-default-base and kernel-default were an 'additive set'. kernel-default was based on top of kernel-default-base and kernel-default did not include the content of kernel-default-base. It was not possible to use kernel-default without also having kernel-default-base installed (this was the case with SUSE Linux Enterprise Server Download kernel-compute-base packages for openSUSE. kernel-compute-base latest versions: 6.4.0, . kernel-compute-base architectures: x86_64. kernel-compute-base linux packages: rpm

Tuning Kernel - KVM - Kernel-based Virtual Machine

The correct base image is loaded later (this procedure is called “Deferred application”.)The operations that are performed by the engine for applying a patch are described by an array of hotpatch descriptors. A hotpatch descriptor tells the engine what type of patch each record specifies (function patch, global symbol patch, indirect call, CFG call target and so on...). It is composed of a header and one or more hotpatch records. Each record specifies the patch’s parameters that depend on the type of the descriptor, like the source and target function’s RVA, and the original opcodes bytes.The Hotpatch engine is implemented in various parts of the operating system, mostly in the NT and Secure kernel. The engine, as introduced in the previous paragraph, supports different kinds of images: Hypervisor, Secure Kernel and its modules, NT Kernel drivers and User-mode processes. The hotpatch engine requires the Secure Kernel to be running.For applying a patch to an image, the NT kernel takes several steps that start in the MiLoadHotPatch internal function, which temporarily maps the patch image in the system address space and performs the initial analysis with the goal to search and verify the hotpatch information contained in the PE data structures (showed in Figure 1). After the checksum and timestamp of the target image for which the patch has been designed are located, the NT kernel determines whether the corresponding base image is loaded in the system (the base image can also be a secure image, like the Hypervisor or the Secure Kernel, so this step also needs to invoke the secure kernel).When a compatible image is detected, the NT kernel begins to apply the patch to the target base image using a procedure that is a bit different depending on the type of the base image (user-mode library or process, kernel driver or a secure image). In general, the hotpatch engine maps the patch image in the same address space as the base image (as showed in Figure 2): for user-mode patches, the patch image will be mapped in each process that has the base image loaded.Note that the hotpatch engine also supports session drivers. A session driver is a driver that lives in a kernel-mode address space that is tied to the user logon session (note that the session address space is generated by one particular root page table entry, which is switched on demand by the Memory manager depending on the active session). This means that a particular session can have a driver mapped which does not exist in another session. The Hotpatch engine is able to attach to all sessions in the system thanks to the “HotPatch” process created in phase 1 of the NT Kernel initialization. This minimal process has the characteristic to not belong to any session. The hotpatch engine can thus use that process to temporarily attach to any session in the system and perform the patch application only to the sessions where the driver is currently loaded.Figure 2. Various address spaces supported by

A pre-selecting base kernel method in multiple kernel learning

The kernel this is IO remapped in kernel space (which will have different address). so if you want to print the values of address (0x44e10620) from userspace you can used dev2mem. Hope this clears your doubts!! Cheers, --Prabhakar Lad Hi,Could you please let me know how the register base address & offset can be printed using printk, the above gives only the suggestions of printing the register contents, Am trying to print the register base addressYou can use "__raw_readl" API to print the contents of register at kernel code or as Prabhakar said, you can use "devmem2" command to see the content of register at user space.You have to add the OFFSET with BASE address of particular USB address to get physical address of that USB register say, status register(connectivity,error status etc.,) Dear Bin Liu,Thanks a lot for all your quick responses & really appreciate the same, I understand from all your suggestions that physical address in kernel cannot be directly printed in kernelSorry for my poor understanding, Is my understanding is correct???Could you please let me know how physical address can be converted & printed interms of logical address in kernel space using printkCould any body please demonstrate for printing logical address (corresponding to physical address) using printkfor example could you show me for: usb_ctrl1 register address using printkKindly do the needful as early as possibleOnce again many thanks in advanceMany Thanks in advance Hi Srini,Tell us which exact USB register do you want to read ?Purpose of reading

PS5-4.03-Kernel-Exploit: An experimental webkit-based kernel

Hotpatching on Windows.Once the hotpatch image is mapped, the patch engine within the kernel starts to apply the patch by performing Backward patch application as described by the hotpatch records:Patches all callees of patched functions in the patch image to jump to the corresponding functions in the base image. The reason for this is to ensure that all the unpatched code executes from the original base image. For example, if function A calls function B in the original base image and the patch image patches function A but not function B, then the patch engine will update function B in the patch image to jump to function B in the original base image.Patches the necessary references to global variables in hotpatch functions to point to the corresponding global variables in the original base image.Patches the necessary import address table (IAT) references in the hotpatch image by copying the corresponding IAT entries from the original base image.It then performs the Forward patch application by patching the necessary functions in the original base image to jump to the corresponding functions in the patch image. Once this is done for any given function in the original base image, all new invocations of that function will execute the new patched function code from the hotpatch image. Once the hotpatched function returns, it will return to the caller of the original function.The described procedure, which, for kernel drivers, is executed by the Secure Kernel, has been highly simplified. Note that the hotpatching process requires proper synchronization: no processor should be able to execute original instructions while undergoing a patch application. Note that the Secure Kernel is able also to interact with Hyperguard. This allows protected Patchguard images to be correctly patched.When applying a patch to a function, the Hotpatch engine should be able to store the trampoline needed for transferring the code execution from the base to the patched function. The trampoline can’t be stored in the old un-patched function for various reasons: currently running code may hit invalid instructions and there is also no guarantee that enough space exists in the old function’s code. Furthermore, the patch engine supports both the application and the revert (undo) of a patch, which means that the original replaced bytes would have to be stored somewhere. Trampoline code to transfer execution to the target function is placed in the Hotpatch Address table code page (abbreviated as HPAT).When the system initially boots, the Windows loader determines the size of the HPAT area, which is composed of a combination of data and code pages (to support ARM64 and scenarios where Retpoline is enabled on x64). When HotPatch is enabled, each boot driver is loaded in memory by reserving the HPAT pages at the end of PE image (before the Retpoline code page. Further information about Retpoline on Windows are available here: Mitigating Spectre variant 2 with Retpoline on Windows - Microsoft Tech Community). Note that the term “reserved” means that no actual physical memory is consumed. This is handled similarly

Linux kernel based on the mainline 5.17.5 kernel for BananaPi M2

Nvidia modules for version 5.11.0-37rc linux-modules-nvidia-460-5.11.0-38-generic 5.11.0-38.42~20.04.1 amd64 Linux kernel nvidia modules for version 5.11.0-38rc linux-modules-nvidia-460-5.8.0-43-generic 5.8.0-43.49~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-43rc linux-modules-nvidia-460-5.8.0-50-generic 5.8.0-50.56~20.04.1+1 amd64 Linux kernel nvidia modules for version 5.8.0-50rc linux-modules-nvidia-460-5.8.0-53-generic 5.8.0-53.60~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-53rc linux-modules-nvidia-460-5.8.0-55-generic 5.8.0-55.62~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-55rc linux-modules-nvidia-460-5.8.0-59-generic 5.8.0-59.66~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-59ii linux-modules-nvidia-510-5.13.0-28-generic 5.13.0-28.31~20.04.1+2 amd64 Linux kernel nvidia modules for version 5.13.0-28ii linux-modules-nvidia-510-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Linux kernel nvidia modules for version 5.13.0-30ii linux-modules-nvidia-510-generic-hwe-20.04 5.13.0-30.33~20.04.1 amd64 Extra drivers for nvidia-510 for the generic-hwe-20.04 flavourrc linux-objects-nvidia-460-5.11.0-25-generic 5.11.0-25.27~20.04.1+3 amd64 Linux kernel nvidia modules for version 5.11.0-25 (objects)rc linux-objects-nvidia-460-5.11.0-27-generic 5.11.0-27.29~20.04.1 amd64 Linux kernel nvidia modules for version 5.11.0-27 (objects)rc linux-objects-nvidia-460-5.11.0-34-generic 5.11.0-34.36~20.04.1 amd64 Linux kernel nvidia modules for version 5.11.0-34 (objects)rc linux-objects-nvidia-460-5.11.0-36-generic 5.11.0-36.40~20.04.1 amd64 Linux kernel nvidia modules for version 5.11.0-36 (objects)rc linux-objects-nvidia-460-5.11.0-37-generic 5.11.0-37.41~20.04.2 amd64 Linux kernel nvidia modules for version 5.11.0-37 (objects)rc linux-objects-nvidia-460-5.11.0-38-generic 5.11.0-38.42~20.04.1 amd64 Linux kernel nvidia modules for version 5.11.0-38 (objects)rc linux-objects-nvidia-460-5.8.0-50-generic 5.8.0-50.56~20.04.1+1 amd64 Linux kernel nvidia modules for version 5.8.0-50 (objects)rc linux-objects-nvidia-460-5.8.0-53-generic 5.8.0-53.60~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-53 (objects)rc linux-objects-nvidia-460-5.8.0-55-generic 5.8.0-55.62~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-55 (objects)rc linux-objects-nvidia-460-5.8.0-59-generic 5.8.0-59.66~20.04.1 amd64 Linux kernel nvidia modules for version 5.8.0-59 (objects)rc linux-objects-nvidia-470-5.11.0-40-generic 5.11.0-40.44~20.04.2+1 amd64 Linux kernel nvidia modules for version 5.11.0-40 (objects)ii linux-objects-nvidia-470-5.13.0-28-generic 5.13.0-28.31~20.04.1+2 amd64 Linux kernel nvidia modules for version 5.13.0-28 (objects)ii linux-objects-nvidia-510-5.13.0-28-generic 5.13.0-28.31~20.04.1+2 amd64 Linux kernel nvidia modules for version 5.13.0-28 (objects)ii linux-objects-nvidia-510-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Linux kernel nvidia modules for version 5.13.0-30 (objects)ii linux-signatures-nvidia-5.13.0-28-generic 5.13.0-28.31~20.04.1+2 amd64 Linux kernel signatures for nvidia modules for version 5.13.0-28-genericii linux-signatures-nvidia-5.13.0-30-generic 5.13.0-30.33~20.04.1 amd64 Linux kernel signatures for nvidia modules for version 5.13.0-30-genericii linux-sound-base 1.0.25+dfsg-0ubuntu5 all base package for ALSA and OSS sound systemsii nsight-graphics-for-embeddedlinux-2021.2.1 2021.2.1 amd64 NVIDIA Nsight Graphics is a standalone application for the debugging, profiling, and analysis of graphics applications.ii syslinux-common 3:6.04~git20190206.bf6db5b4+dfsg1-2 all collection of bootloaders (common)ii syslinux-legacy 2:3.63+dfsg-2ubuntu9 amd64 Bootloader for Linux/i386 using MS-DOS floppies. Initially, kernel-default-base and kernel-default were an 'additive set'. kernel-default was based on top of kernel-default-base and kernel-default did not include the content of kernel-default-base. It was not possible to use kernel-default without also having kernel-default-base installed (this was the case with SUSE Linux Enterprise Server Download kernel-compute-base packages for openSUSE. kernel-compute-base latest versions: 6.4.0, . kernel-compute-base architectures: x86_64. kernel-compute-base linux packages: rpm

Choose the right kvm kernel version - KVM - Kernel-based

When you compile a custom kernel module such as a device driver on a CentOS system, you need to have kernel header files installed on the system, which include the C header files for the Linux kernel. Kernel header files provide different kinds of function and structure definitions required when installing or compiling any code that interfaces with the kernel.When you install Kernel Headers, make sure it matches with the currently installed kernel version on the system. If your Kernel version comes with the default distribution installation or you have upgraded your Kernel using yum package manager from system base repositories, then you must install matching kernel headers using package manager only. If you’ve compiled Kernel from sources, you can install kernel headers from sources only.Read Also: How to Install Kernel Headers in Ubuntu and DebianIn this article, we will explain how to install Kernel Headers in CentOS/RHEL 7 and Fedora distributions using default package manager.Install Kernel Headers in CentOS 7First confirm that the matching kernel headers are already installed under /usr/src/kernels/ location on your system using following commands.# cd /usr/src/kernels/# ls -lCheck Kernel Headers in CentOS 7If no matching kernel headers are located in the /usr/src/kernels/ directory, go ahead and install kernel headers, which is provided by the kernel-devel package that can be installed using default package manager as shown.# yum install kernel-devel [On CentOS/RHEL 7]# dnf install kernel-devel [On Fedora 22+]Install Kernel Headers in CentOS 7After installing the kernel-devel package, you can find all the kernel headers files

AUTOSAR Architecture Based Kernel Development for

You are using an out of date browser. It may not display this or other websites correctly.You should upgrade or use an alternative browser. #1 Purpose:Tutorial to describe how to install and configure an OpenVPN client on a rooted Epic 4G Touch. This "how to" assumes you know what OpenVPN is and have a verified working OpenVPN server. Client Requirements:Rooted Epic 4G Touch with either: A kernel with built-in tun support (stock kernel) A kernel with a seperate tun.ko module (Rogue Desperado).Tested Rom/Kernel Combinations:Blazer 1.2 ROM (EG30 Base) with included Kernel : Blazer 1.2 ROM (EG30 Base) with Rogue v1.3.0 "Desperado" Kernel (comes with seperate tun.ko module)Tested Server Configurations:Windows OpenVPN server (Bridged mode UDP). Windows OpenVPN server (Bridged mode TCP). Asus RT-N16 router running DD-WRT v24-sp2 (06/14/11) mega - build 17201 (Bridged mode TCP)Install BusyBox:If you already have BusyBox this step may be unnecessary, if you do have it BusyBox Installer should tell you where. On your device download and install "BusyBox Installer" (by JRummy16): Run the BusyBox Installer and accept the default version (BusyBox v1.19.3) and location (/system/xbin/) Scroll down to the bottom and press the "Install" button. Install OpenVPN Installer:When I first installed OpenVPN I used Freidrich Schäuffelhut's installer which let me connect, however the client never got an IP address from the OpenVPN DHCP server. I had to go through the manual step of opening a terminal window on my device after I connected and typing the command "netcfg tap0 dhcp". This is due to Schäuffelhut's installer putting an OpenVPN binary that's not fully compatible with BusyBox, this can fixed by using Sascha Volkenandt's installer instead. On your device download "OpenVPN Installer" (from Sascha Volkenandt NOT Friedrich Schäuffelhut): Run the installer, keep the default path values (OpenVPN Targe Location: /system/xbin, Busybox Install Path: /system/xbin), unless you have. Initially, kernel-default-base and kernel-default were an 'additive set'. kernel-default was based on top of kernel-default-base and kernel-default did not include the content of kernel-default-base. It was not possible to use kernel-default without also having kernel-default-base installed (this was the case with SUSE Linux Enterprise Server Download kernel-compute-base packages for openSUSE. kernel-compute-base latest versions: 6.4.0, . kernel-compute-base architectures: x86_64. kernel-compute-base linux packages: rpm

Kernel for Base Download from LisiSoft

The register that reg etc., ?If you print the content of USB base address you would get value of USB "REVISION"If you want to read USB0 Control register then do the following:USB0 CONTROL reg offset -> 0x620 (please refer to the page no CONTROL MODULE base address -> 0x44E10000PHYSICAL address of USB0 control register -> 0x44E10620Ex:static void __iomem *base; base = ioremap( 0x44E10000, SZ_4K); printk("USB0 Control reg = %x\n",__raw_readl(base+0x620));Actually, if you want to see the content of USB control register value, also you can put the following line at line no 85 at "drivers/usb/phy/phy-am335x-control.cprintk("USB0 control value 0x%x\n",val);Just now seen the following post, Pavel given almost all possibilities, still any problem?e2e.ti.com/.../386669 Sorry for such a silly question Titus,Ex:static void __iomem *base;base = ioremap( 0x44E10000, SZ_4K);Could you please let me know what is this SZ_4K?? what is its value??? why it is always SZ_4K??Could you please let me know how this base variable can be printed is it possible to print using "%p" format specifier or should I use "%x" format specifier using printk???Is it possible to print using printk("%p", base); does this work ????Kindly do the needful as early as possibleMany Thanks in advance again Thanks a lot for your time Titus & for your explanation , Once again many thanks Titus, Pavel , Prabhakar & Bin LiuNow my doubts are clearedThanks a lot once again to all Srini said:I understand from all your suggestions that physical address in kernel cannot be directly printed in kernel Sorry for my poor understanding,