I installed the latest security update for squeeze. It entailed an update of the kernel. Now when it boots, it give continuous kernel error messages about "can't enumerate usb .... " I have a custom kernel compiled from source (not sure about the patch level) from the same kernel 2.6.32. It seems to work OK. Should I worry about the security of this custom kernel or should I try to recompile it? I don't really know how to do any patching of the kernel source.
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
I have a asus M51 Se that not work with 4GB of memory ram, due to a bug of bios. Only work with one slot of 2GB. I find this link https://bugs.launchpad.net/ubuntu/+s...ux/+bug/316079 that help to solve my problem. But for that I have to change a file.
My question is I need to recompile the kernel that I have? if yes, how can i make that without installing other kernel.
I tried to run some virtual machine using Virtual Machine Manager but the guest OS (windows server 2003) was not able to "see" the rest of my network. I believe VMM did some NAT-ing (192.168.122.x subnet) so i'm not able to "see" my network. I tried various network setting in VMM but couldnt get it to pull my network IP (192.168.1.x subnet).So i installed VirtualBox as a work around because i know VB work when i tried it on my windows machine. I ran into some issue getting VB to run, i think it was that i need to compile the kernel to "optimize" it for VB. I am fairly new to linux so that the impression that i get when i research for the fix to get VB working. In some of the forum post people suggest few things and it seem to me like it to compile the kernel. After a few hours of working i finally got it to compile but the computer crashed during compilation.
I am guess what happened is that i was trying to optimize the kernel for VB but the version of kernel i was using (2.6.18-164.6.1.el5xen) is already optimized for xen (VMM) so it crashed. I am looking to restore or recompile the 2.6.18-164.6.1.el5xen kernel. I am not sure if this is the right thing to do to fix it. With my limited knowledge of linux that all i can think of.
I wish to recompile serial_core module to make a change in the way ioctl works. I don't wish to rebuild the whole kernel package. Can someone point me to the proper method?? I know I will need to download the kernel headers etc. But I would like to avoid the unneeded compiles of things I don't need to recompile.
This has got me stumped. I expected to do /etc/init.d/vboxdrv setup after the upgrade from 11.3 to 11.4 but the command fails. The log is (it seems to repeat so I only quote the final bits to make it fit into the wordcount limit):
Code: make KBUILD_VERBOSE=1 -C /lib/modules/220.127.116.11-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
I am using FC9, I want to write a module that will always show current time after booting.But for that I need not only to load module using insmod/modprobe, but also to compile that module during boot time.How can I perform this 2 steps correctly.
I've been playing around in attempt to see how small a usable kernel I can build. The theory is that it should mainly be useful for preparing a recovery disk or some such thing; disk drivers and a few network drivers are what goes in.
I built the kernel with the attached config. It boots, reaches the hdd (if I specify root as /dev/sda5 manually), then dies when it tries to start Plymouth (something about catching a SEGV signal). What needs to be enabled to run Plymouth? Alternatively, has anyone managed to remove plymouth from boot on Maverick?
(That would require a modified mountall version, I know.) I'm using the mainstream kernel 18.104.22.168 sources on Maverick (yes, I know Maverick uses 2.6.35; but this does boot).
Hardware: Wireless-RTL8192SE b/g/n, uses an out-of-tree driver (r8192se_pci, from Realtek; Ubuntu builds in an older version of this driver); r8169 works for ethernet; ATI Radeon Mobility 3200 graphics, AMD Neo X2 cpu; SATA hd in AHCI mode.
I am on Squeeze I just updated with a new kernel 32-5-686. I have installed the Nvidia driver with kernel 32-3-686. After the update I can't log with kernel 32-5-686. I tried installing another Nvidia driver but I ran into some trouble. This is the first time I am doing this. how to go by and install an Nvidia driver with the new kernel. Should I remove the old driver first? If I do this I won't be able to log into the system using the old kernel from which I am typing this message.
The situation is I removed the ADSL card from my desktop as I have no use for it for the moment. I am guessing that the motherboard is still trying to detect the Sangoma ADSL card. What is the best way to resolve this problem, uninstall the drivers for the ADSL card or change the settings in the system configuration files?
The system is not affected by this removal, just get prompted regularly about this error as configured in the kerneloops client.
I have a flash drive that I regularly use on my laptop. If I unplug the flash drive without first unmounting it, I get a popup notification of a kernel failure (with diagnostics sent to kerneloops.org). Then, if I attempt to shut down the system via the console, it hangs on "The system is going down for halt/reboot NOW!" and doesn't actually shut down. Using Gnome's graphical System > Shut Down feature just logs me out and sends me to the login screen; the shutdown feature from there does nothing. I have to disconnect the power cord on the laptop in order to shut it down, and I don't like doing this.
System: 32-bit Debian Squeeze stable with kernel version 2.6.32-5-686, running Gnome 2.30.2, on an Acer Aspire 5570z.
I use Keepassx to store my passwords and keep the keyfile for my password database on the flash drive in question. I mention this just in case it helps determine what's causing the failure.
I got a rather big problem since an attempt to upgrade.My debian version is 8.0.I upgraded when apt proposed the change. I did that in two steps, with apt-get upgrade and then apt-get dist-upgrade, with the installation of a new kernel. I moved from 3.2.0-4-686-pae to 3.16.0-4-686-pae.Since the upgrade, I can't boot my system any longer.During the boot sequence, this message appears with a countdown (it's copied by hand) :
Code: Select all(1 of 4) a start job is running for dev-disk-byX2du
At the end of the countdown, the boot sequence starts again, and ends up on an invite to log in as root in rescue mode. I can't connect (maybe due to some azerty/qwerty issue, I got a French keyboard. I tried to type in "qwerty mode", with no success (the password is not prompted)).I can connect with the 3.2 kernel however, selecting it form the grub interface. I can't log in in rescue mode either, but with this kernel the boot sequence goes on and I can log as a regular user or as root, at the end of the boot sequence. There is no X, but the system seems to work.What could I do to make the system boot properly with the new kernel, or to go back to the 3.2 version ?
i'm using this guide videos - howto: debian linux kernel compilation, part 1 and the author says i need kernel 2.6.26 this version of kernel doesnt longer exist in kernel.org website and the only 2.6.26 i found is a patch here. should i use the patch? or download another version of kernel?
We have a Dell 1850 with Debian with 2.4.18 kernel running some critical applications, now the issue is we need to upgrade the memory to 8 GB but the memory is detected by the bios itself, Operating system is not able to detect it, it is showing 3096MB of memory,
After a lot of googling and the artical in linux.com/archive/articles/119287 :: Got more than a gig of RAM and 32-bit Linux? Here's how to use it i came to know the solution i.e
1)I need to install the Bigmem-kernel to detect the ram more than 4Gb,
2) or change some kernel parameters in configuration file and rebuild the kernel
Is there any another solution for this to update operating system to detect the more RAM
We have a Dell 1850 with Debian 3.0 (woody) with 2.4.18 kernel running some critical applications, now the issue is we need to upgrade the memory to 8 GB but the memory is detected by the bios itself, Operating system is not able to detect it, it is showing 3096MB of memory. i came to know the solution i.e I need to install the Bigmem-kernel to detect the ram more than 4Gb, Any another solution for this to update operating system to detect the more RAM.
recompile files into an ISO I bought a DVD of reason 4.0 (windows music program), I wanted to back it up but I didn't make an ISO I copied the files. now I have lost the DVD and I want to install reason back to my windows machine but it needs a DVD in the drive, it wont proceed. how can I recompile the files and make them a recognized ISO so my installation can continue.
At Design House I get LDAP installed and working with PHP5. Not used to rpm'ing - need to add LDAP to PHP5 hosted on SELinux on Network Solutions server and recompile. They installed an openldap but I'm not seeing PHP with it compiled.
im trying to recompile avrdude with a few new patches that will make me able to burn arduino bootloader to my 328p microprocessor. The biggest problem i have is that i need to use termcap but i cant find it in aur or anywhere else at archlinux homepage or my system. I used my google skills but failed, all i found was that it is possible to use ncurses instead of termcap but i tried and it fails and i already use ncurses :S....
i want to add a new system call.im following this guide [URL] in this step 6 he said add __NR_mycall to some number, in unistd.h. in include/asm/unistd.h there are are around 1079 calls for different hardwares. and the __NR_SYSCALLS is also defined many places. I don't know where to add my new system call. and another qn is. whether the number for syscall in unistd.h and arch/x86/syscall_32.s both should be same?or they can be different.
I recently bought scanner, the driver to which is currently in process and is not yet committed into the main repo, so I downloaded the new code and compiled it into /usr/local/ and openSUSE's YaST scanner configurer doesn't see the new versions and continues to work with the old ones.