General :: Debian 686 Kernel Total Networking Failure On IbmX60 But 486 Kernel Works
Feb 11, 2011
The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.
I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.
Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?
Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:
I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.
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'd be interested in your views on this. Background: After many hours of trying to configure a particularly recalcitrant graphics card as posted here, I eventually resorted to trying Mandriva 2009, which, with the 2.6.27-desktop 586-0.rc8.2mnb kernel, solved the terrible problem of slow, hit-and-miss booting with Debian and also random freezes with Ubuntu.However, when updating to Mandriva 2010, the problems with booting, and also a wrong screen resolution were back so, for the time being, I settled for the 2009 release.
My question is: Having found out that the Mandriva kernel worked, does anyone know if would it be possible to finally bring this laptop to heel with Debian + a 2.6.27 kernel and following the time-honoured adage of "if it ain't broke, don't fix it" leave such a kernel in place without updating to a newer one?
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?
i just updated my mainboard, because of a failure in the grafic chip. Now I have a icore 7-2600K CPU with 16GB memory.The system will not boot with the latest kernel version Kernel 2.6.38.11 - Kernel 2.6.38.10 . It crashed and resets the system.
But when I am using Kernel 2.6.35.30, then it works, as you can see. As well the kubuntu 64bit CDROM does not work. Crashed as well.
Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
Debian 5.0. Lately after login following warning popup;Your system had a kernel failure
There is diagnostic information availiable for this failure. Do you want to submit this infomation to the www.kerneloops.org
-> Yes
$ uname -aLinux vm0.debian50 2.6.26-2-686 #1 SMP Wed May 12 21:56:10 UTC 2010 i686 GNU/Linux
Reboot to old kernel 2.6.26-1 the said warning doesn't popup. Reboot again to kernel 2.6.26-2 and after login no kernel failure warning popup. I did it twice. IIRC I encountered this problem before.
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 just installed the lenny (amd64) on my new core i7 870 computer (with netinst), but the kernel failure message appeared everytime I booted into gnome. I don't know how to solve this problem. Sorry I don't have much experience with installing linux, though I have been its user for a few years.
I have just done a fresh install of 10.10 (full updates) with my new HD 4870, downloaded the last catalyst 11.6 from AMD, I have done the normal procedure of the driver installation, Ubuntu booted correctly, i changed some options in CCC, one of them the "video tearing option" after that X crashed, rebooted the machine, but it stays that way, before the login screen, the X crashes (corrupted image) only reset button restarts the machine.
I removed the installed driver, purged the configurations and started all over using the deb package creation procedure of the driver and also the manual script installation, but it stays the same way, removed again the driver, installed the OSS driver, it logins correctly, tested also with the restricted driver of the Ubuntu repository, it works, but no "video tearing option".
Done a new fresh install of 10.10 (no updates), installed the driver and enabled the "video tearing option", everything is ok, but if I upgrade the kernel the problem returns (if "video tearing option" is enable), i managed to overcome the video tearing option by always enabling VSYNC. After all this, my question is how can I reset CCC settings via command line, the aticonf --initial dont work in this case, CCC is keeping the settings in some config file (I think) that I dont know the location. I want to do some testing, and its annoying to remove, install , reinstall the driver when the X enters this crash loop.
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.
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
As a follow-on to something Telemachos said in another post:
Quote:
Originally Posted by Telemachos
You can see what kernels you have installed - to check if you have a virtual kernel and to clean up - by running this command:
Code:
If you've been installing kernel-headers along with the kernels (say to build modules for graphics or wireless), you should remove those when you remove the corresponding kernel. The command to search for those is parallel:
Code:
I would have thought that removing a given kernel package would trigger the removal of the older kernel headers. Can someone confirm that is, or is not, the behavior? I ask this because it seemed to me that the older kernel header packages were indeed removed when I removed some older kernel packages.
For example, the linux kernels I have installed are:
Code:
Also, the linux-headers packages I have installed are:
Code:
So, when I get around to removing the linux-image-2.6.25-2-amd64 package like this:
Code:
I would expect apt-get to automatically also remove linux-headers-2.6.25-2-amd64 and linux-headers-2.6.25-2-common. Is that what will happen, or do I need to explicitly state all three packages on the apt-get remove command?
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
I have a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I would like to update my kernel to version 2.6.32 to see if it solves my tv-tuner card issues (not being recognized by the kernel Lenny uses 2.6.26-2 x64). What steps should I follow to accomplish this upgrade?
I'm trying to run extract-ikconfig because I've mistakenly deleted an old kernel config that I'd like to recover. However, when running the script from the latest (2.6.32.5) tree I run into this error:
Quote:
ERROR: Unable to extract kernel configuration information.
This kernel image may not have the config info.
Coincidentally, this happens with all of my kernel images. Is it a fixable problem? I should really set CONFIG_IKCONFIG_PROC next time..
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.
Kernel Output:
Code:
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.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel. Red Hat nash version 4.2.1.13 starting sda: assuming drive cache: write through sda: assuming drive cache: write through mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd-dev failed: 2 Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info: Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I have just installed Fedora 11 to my laptop and it appears I am in trouble. I have received two kernel failure messages, which I post below. What are the consequences of these issues and how can I solve them ?
I just installed OpenSUSE 11.4 x64 as a fresh full-install last week. Seems to be running great, up until the last couple days when I installed AVG. Every time I do a avgscan, it runs for 20 to 60 min, and then causes the PC to reboot. The only thing I can find is the following event in the /var/log/messages:
Code: May 1 11:45:01 linuxbox sntp[7653]: Started sntp May 1 11:45:59 linuxbox kernel: [38429.349995] iTCO_wdt: Unexpected close, not stopping watchdog! May 1 11:46:00 linuxbox kernel: [38430.111688] PM: Marking nosave pages: 000000000009d000 - 0000000000100000
[Code].....
I get this result every time I try to do a virus scan. I also have seen this result once when doing a large scp transfer from another Suse box. The AVG log just terminates and gives no warnings as to what's going wrong.
Are there any other logs I can check out to try to troubleshoot this further???
I'm running the 64 bit version of Ubuntu 9.10 on an AMD64 dual core platform with all the most recent upgrades installed. After the most recent Kernel upgrade version 2.6.31.20 the computer failed to boot correctly. Extremely slow getting to the desktop and a general failure to preload any programs that I load on boot. I had to uninstall and revert back to the previous Linux headers which solved the problem. If it makes any difference I have the machine setup as an apache2 server along with my standard desktop environment.
I have just updated my kernel and immediately struck trouble. The kernel update is marked as security update. When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).
I am getting a problem when login into FC10. It boots correctly an shows the login screen; then, when typing my user and passwd goes to the desktop and shows a KERNEL FAILURE. At this moment, most of the times the PC is blocked and doesnt works any more. One time has continued working without problems.
After the las failure, my system log has this info:
Code:
I have checked my hard disks (fsck) y every thing looks fine. However, i dont know how to fsck the VolGroup0. I cant'get it unmounted.
Is there a way to get the matching Linux kernel headers automatic on a regular kernel update via the Ubuntu packed manager? Every time I get a new kernel I must do an aptitude install linux-headers-`uname -r`
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
