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've just installed 100+meg of updates and rebooted only to find that when I login the desktop fails to boot. Opening a root-console, I killed Compiz which dropped me back to the login screen where I logged-in again with the desktop starting successfully. From there I disabled Compiz and have no problem starting the desktop now. But that's not really a solution.Even stranger, if I now try logging in with and older kernel version and with Compiz off - if I try enabling Compix now, the desktop just freezes - it also fails to complete loading the desktop. So both the current-kernel/Compiz seem to be linked to the problem in some way!Has anyone else experienced this, and is there a solution? I miss my desktop-effects!
After updating Squeeze (i386) on my Via C7 laptop with the Via Openchrome video driver vlc video ouput shows only alternating white/green grainy vertical bars. I tried changing the video output driver to x11 and sdl without success. I'll be trying to find a fix and if successful I'll post back. For the rest of you just beware of the latest upgrades. More information - My AMD/ATI desktop also running Squeeze (amd64) updated fine. It has the onboard ATI 2400 video driver.
I received an update yesterday and now my analog clock plasmoid is no longer functional. It's strange too because when I change a setting in the plasmoid, it'll magically come to life. I ran plasma-desktop in terminal to catch an error output, but nothing came up.
Useful info: Running KDE 4.4.0 release 223 Opensuse 11.2
Running 12.2 on fluxbox, it seems the latest pidgin update has messed with my dock icon- it's no longer the pidgin icon, now I believe it's a generic one. It's not REALLY a big deal, but it kind of bugs me...
This is old P4 laptop, Intel845G graphics (which I know is very troublesome).However, it works fine with the 126.96.36.199, but the update to 188.8.131.52 kills X during the boot process. Everything else works fine.Anyone else experiencing any difficulty with X and this kernel update?
I'm running Hardy 8.04 LTS 64bit. The Update Manager updated the kernel and then asked if I wanted to use the local version of the grub menu. The boot menu was getting so long I edited it to shorten it. Other options were also offered, like the builder's version, but I chose the local version and since then the new kernel doesn't show up in the boot menu. Sudo update-grub doesn't restore it to the menu.
How do I undo the local version of the boot menu so I can see the newest kernel?
I can't go into text mode after latest kernel update. CTRL-ALT-F1 doesn't work. Actually, all CTRL-ALT-F1 to F7 work very strange. For example... When I click CTRL-ALT-F2, it close all my windows and screen flash
I am running Maverick via Wubi. I just completed a Kernel upgrade and when I restart into Ubuntu it just goes to a Bash prompt. I am not sure exactly what version I updated to so I haven't logged a bug report yet.
I have noticed that my battery-status applet icon, which appears next to the wireless symbol in the notification applet on the menu bar at the top of the screen, only appears for a second or two when I plug in my notebook and then disappears. It does not appear at all when the notebook is unplugged. just noticed this behaviorafter restarting with the new kernel
I can't access my grub menu (by pressing space bar on boot) to select a kernel to boot from, and I need to boot into 2.6.31 to fix an intel chip issue. How can I replace the current 2.6.32x kernel with 2.6.31, so it is the ONLY option grub can boot up with?
I have a Macbook Pro 5,5. I had Fedora 14 installed on it, updated to the latest version. I updated the kernel, and performed an update. Now, every time my system starts, it loads up the startup fedora bar, and it gets stuck at the bar being loaded 100%.I press ESC to see what is going on behind the scenes, and I notice that the problem is that atd cannot start up.
Dual Boot: Fedora 12 and XP Dell 505I've had trouble with the latest kernel update.I updated a bunch of packages recently (including Xorg and kernel), and noticed a severe flickering after the update on my center monitor (Samsung T260 - the laptop display did not exhibit the flickering behavior). I backed out all the changes and started updating package by package. After I updated the kernel (again) I rebooted and here's where the fun part is -
I no longer get anything, except the cursor. No grub menu, no grub prompt. I rebooted and ran the rescue disk and followed the procedurery and point grub at the right boot partition - see here. However (obviously or I wouldn't be posting) that failed to work. I still get a blinking cursor and dead system on boot up.
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
opensuse v11.2linux 184.108.40.206-0.1-desktop x86_64The kernel symbol file is still at 220.127.116.11. Apparently the symbol file did not get updated with the rest of the kernel development files. At least one program does not build because of that
I recently updated my kernel and now can no longer tether my iphone to my openSUSE11.3(x64) laptop. Before the update I could tether.Same machine dual boots to Win7-64bit and can tether just fine.I re-installed the libimobile packages, but my linux no longer recognizes the iphone as a network device.t DOES pop-up some boxes asking if I want to play the media, or view the photos on the iPhone - so that part is working
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?
I seem unable to get an nvidia driver working properly after upgrading to the latest kernel with Fedora 11.Here is my laptop and its specs: http://h10025.www1.hp.com/ewfrf/wc/d...reg_R1002_USEN[URL]I've tried both the kmod and akmod unsuccessfully. Everytime it gives me a black screen on boot, I can fix the problem by popping in the LiveCD, and changing the xorg.conf file back to the backup.Here are the errors/warnings from my boot.log file:
Code: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Checking for module nvidia.ko: [60G[[0;31mFAILED[0;39m]
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 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.