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 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'm trying to install a BCM 4312 wireless driver following the Centos howto. Howtos>Laptops>Witeless>Broadcom
On step 3, compiling ... module.I get No rule to make target `build' Stop.When I go to the /lib/modules/188.8.131.52.3.1.el5 directory, the Build file link is broken.If i go to the link source /usr/src/kernels/2.6 ...x86_64 does not exist. The /kernels folder is empty.I think I need to reinstall the identified kernel in that directory and reestablish a link to it. but am not savy enough to do that on my own.
I am currently working to get to a stable dual boot Win7/CentOS 5.5 configuration on a Dell Latitude E6510 with the Intel 82577LM chipset. I haven't gotten the Centrino N WiFI chipset working yet, but the Eth0 device was working just fine.However, yesterday I did a system update. I did not pay close attention, but I believe the update did mention networking, because I thought it might help me get my wireless going. Now, Eth0 fails with the message, "Determining IP information for eth0... failed; no link present. Check cable?" It does this at boot up and if we try reactivating it once the system is up. We have tried unstalling and re-installing the driver.The Window 7 boot sees the adapter and runs just fine. I was at a different site location yesterday when everything was working, but my co-workers and I can't help but think it might be related to the update yesterday, since everything worked prior to the update and Windoze 7 works fine with the adapter.
I have not been able to mount my NTFS harddrive on the CentOS side, despite installing fuse, and I don't have wireless, which makes it difficult to get access to new drivers. I also have a FAT32 partition that would be great to share between the boots for passing info, but I haven't found a way to mount a FAT32 partition in CentOS.
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/184.108.40.206-1.2-desktop/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
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 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 need to downgrade glibc due to a broken kernel after a libc6 upgrade attempt. See:[URL]..Especially with the reduced capabilities I have right now (few if any programs are working), how might I go about downgrading glibc to 2.6?
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 220.127.116.11 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 have recompiled MONO 2.4 RPM's from the OpenSuSE buildservice. I need it for Monodevelop and some .NET stuff So i need to recompile the package gtk-sharp2 LANG=C rpmbuild --rebuild /home/darko/Desktop/gtk-sharp2-2.10.0-6.el5.centos.src.rpm
I have recently updated my ubuntu kernel to version 2.6.35-25 and its seems that broke my graphics. On login i cant see anything but some messy graphics. tryed to login with the old kernel and everything seems to work fine and also it works ok with the fglrx. The conflict seems to be beween the ATI open source drivers and the new kernel
So I know I should have known better then to turn my updates back on after the 15 and 16 kernel updates crashed ubuntu and grub but I did anyway and once again after a new kernel gets installed I'm stuck at the grub sh prompt.
Been down the road before... tried using linux /boot/vml....... root=/dev/sda1 loop=/ubuntu/disks/root.disk ro When I use the 16 or 17 kernel I get an error stating "invalid imaginary number"...
So I use the 14 kernal and enter initrd /boot/initrd..... boot
And it boots like it did the last time this crashed. I went to the terminal and entered sudo apt-get install grub 2 sudo update-grub2
And then rebooted like I did last time expecting the problem to be fixed and at least be able to boot up the 14-generic. It didn't fixed this time. So now what do I do to fix grub and what do I do about having 2 unbootable kernals??
After updating to version 2.6.31-20-generic, my desktop computer with an ATi HD4850 graphics card, using the fglrx driver, now won't boot to X. It goes through the boot process and displays the splash screen, but after that there is nothing on the screen. Choosing an older kernel version from GRUB doesn't make a difference. I don't even know how to diagnose the problem properly. I can boot into recovery mode and get to the command line, however, starting x from there only leaves me with a blank screen.
so the source of the problem is that I had installed the catalyst driver from amd.com, which needs to be reinstalled with every kernel update. I didn't know this in advance, so now I'd like a way to revert back to fglrx from the repos. Sadly, the community docs only seem to cover the graphical way of doing this, which is kind of useless to me at the moment.The ATi driver docs gave me a way to uninstall the catalyst driver using only the command line. So now I've booted back into Ubuntu and selected to install the fglrx driver from System → Hardware Drivers. However, now when I boot up, I get the message: "(EE) Unable to initialize PCS database
Ubuntu 10.10 latest kernel 2.6.35-28.49 update is broken. update just stalls when it gets to this.Quote:
Sub-process /usr/bin/dpkg returned an error code (1)...generating grub.cfg I have tried the following to no avail..Quote: sudo apt-get install -f sudo dpkg --configure -a sudo apt-get update && sudo apt-get upgrade
I use Arch Linux and the kernel got upgraded, and it broke VirtualBox. It says to run "/etc/init.d/vboxdrv setup", but such a file does not exist. The Arch Wiki says "/etc/rc.d/rc.vboxdrv setup", but that doesn't exist either. What should I do?
And is it possible to write a script that runs on startup that automatically fixes VirtualBox whenever the kernel is upgraded?
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 ?
Having installed the 2.6.32 backport for Lenny, I have suddenly noticed that my Gkrellm doesn't display CPU and MB temperature anymore. Also, the smart sensors are inaccessible. Smartctl cannot access the readings even when run manually in a root terminal. I tried reinstalling lm-sensors and running sensor-detect again but it didn't help. What else needs to be updated to let the backported kernel see the hardware sensors?
The kernel-PAE-18.104.22.168-43 upgrade will not boot on my Dell 1545 notebook. The initialization stops and the systems freezes right at the point that the login prompt should appear. I do not have invidia drivers. I have Intel video drivers. Also there is a loud 'pop' in the sound system early in the initialization sequence. For the time being, I have removed the 22.214.171.124-43 upgrade via yum.
I was doing a kernel update and can no longer boot into 11.3. I am dual booting with XP. I get Grub screen but no longer see Suse as a boot option, only Windows. I have tried to reinstall, but for some reason I can't get it to boot with DVD. So, is there a way that I can repair my computer without doing a reinstall?
I just upgraded the kernel on my Ubuntu laptop from 2.6.32-24-generic to 2.6.32-25-generic (using the update manager under gnome). After the update, the wireless network controller shows up as UNCLAIMED when I do lshw -C network.When I try to install the driver with the commands sudo modprobe lib80211 sudo insmod wl.ko
i get this error message: insmod: error inserting 'wl.ko': -1 Invalid module format
I have compiled the driver using the 2.6.32-24 kernel. Do I have to re-compile with the new kernel?I'm a unix user, but not a kernel hacker, so I'm wondering if I will run into problems every time I get a kernel update? Or is this problem an exception?