Slackware :: Not Booting After Latest Update?
May 15, 2010after update to tle latest -current using slackpkg my slackware not boot. After hit enter after bootprompt the pc restart.
View 14 Repliesafter update to tle latest -current using slackpkg my slackware not boot. After hit enter after bootprompt the pc restart.
View 14 RepliesHave similar issues with Slackware, since the latest Xorg updates I cant run KDE anymore. I am using VBox 3.2.10, so thats not the issue, i suppose.
Here is the error from kdm.log:
Code:
Backtrace:
Fatal server error:
Also when the system is booting I get a warning like this:
Code:
What a difference, using fglrx, this is like a new computer with this latest update. It runs a bit colder, flashplayer video actually goes all the way to the edge in fullscreen mode and no hardlocks yet (the kind with a blinking capslock light). Maybe fglrx isn't the only bad app in the village after all.
View 7 Replies View RelatedRunning 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...
Where is this set/how do I go about fixing it?
As the title says i updated my system which then needed a reboot. I also installed Mixxx djing software to try it out. So i thought id just restart the system. Usually when i boot into my desktop wireless automatically can connect to my router but not this time, wired only for now... i know theres tons of wireless issue threads but some more experienced users will be able to get straight to the point and run through some diagnostics with me.
View 1 Replies View RelatedIs there a script which will take the patches subdirectory of the latest Slackware distribution tree, and substitute the new patch txz files for the ones in the slackware subdirectory so that during an ISO install, the latest txz will be used, instead, and the ISO will be minimized by not having the older ones?
View 6 Replies View RelatedWhen I try to update the latest from Update Manager I get this message:
Please insert the disk labeled: Ubuntu 10.04.1 LTS _Lucid Lynx_ - Release i386 (20100816.1) in drive /cdrom/
I'm running 9.10. I don't know why I'm getting this message, does anyone here know why this is happening?
So, it's 2010 and I already though I got rid of coding my own drivers & compiling my own kernel in normal use... After installing latest Fedora 14 updates, my system won't boot anymore into fedora. Just continuous loop no matter if I select previous kernel system won't boot.
Anyone any ideas? I think it might be ATI driver but not 100% sure since I didn't see any D/A related or Kernel updates wasn't upcoming...
Anyways I will figure out this sooner or later but this kind of updates sucks a bit that your system goes suddenly totally unuseable or system won't reboot, sooo , time to move on with an another distro or is Fedora just RedHat's playaground?
I just did the latest upgrade in 9.10 via the update manager and it required a reboot. When I rebooted Ubuntu failed to load. In recovery mode it fails saying that it can't find my root device and has some suggestions about what might be wrong. I looked at the file it listed in /proc/something and the devices available by uuid in /dev/ and what's listed in /proc/something isn't in dev. I haven't made any changes yet for fear of causing worse damage. The shell it bumps to is ASH and it doesn't look to have much editor support to make changes to the proc file(ECHO > ?). Is there a safer way to get my system back online?
I'm running 9.10 AMD64 on a Dell Inspiron laptop with a dual boot to Windows 7 (For browser testing web apps/sites)
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd
0801 47428608 sda1 <-- this is my Windows partition
0802 30719552 sda2 <-- this is my Linux partition
0b00 1048575 sr0 driver:sr
0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp
#mount /dev/device /slacktemp
#chroot /slacktemp
#cd /slacktemp/etc <-- for me it told me that doesn't exist
#vi lilo.conf <-- couldn't do nothing and was frozen
#lilo -v -t -b /dev/device
#lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I'm in the process of installing Slackware 13.1 on my old IBM A22m laptop.Since version 12, I've used WPA_supplicant and the Madwifi drive to set up my wireless connection (using a PCMCIA D-Link card). It has worked great all along, up through Slackware 13.However, I've noticed that Alien Bob's Madwifi instructions and repository do not have builds or packages for Madwifi beyond Slackware 12.2.
I think I simply built the drive in 13 by modifying the slackbuild for 12.2.Anyway, what's the latest/best way to set up wireless with an Atheros chipset? Are there Madwifi packages available for Slackware 13.1?
I juset reinstalled my ubuntu and i can't update to the latest kernel. I'm stuck at 2.6.31-15. Also my grub is v1.94 Beta4 and can't upgrade it to grub2.
View 7 Replies View RelatedI've searched a dozen or more threads, some say there is no such thing as rolling back an update, others say it can be done, but I can't find one that outlines how to do it.
View 2 Replies View RelatedThis is old P4 laptop, Intel845G graphics (which I know is very troublesome).However, it works fine with the 2.6.35.22, but the update to 2.6.35.23 kills X during the boot process. Everything else works fine.Anyone else experiencing any difficulty with X and this kernel update?
View 3 Replies View RelatedI did installed LMMS [URL] in Ubuntu 10.10, but it did installed the 0.4.5 version which is not very stable, I wanted to install the latest 0.4.9 (which in the Windows version is much better than the 0.4.5).
View 4 Replies View RelatedEclipse no longer works in 10.10 desktop 64bit, latest update.
The error:
The program 'Eclipse' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
(Details: serial 10174 error_code 8 request_code 153 minor_code 4)
[Code]....
I'm getting exception 13 when trying to use the latest qemu-kvm-0.12.3 on slackware 12.2 w/ stock 2.6.27.7 kernel:
Code:
exception 13 (6b)
rax 0000000000000010 rbx 0000000000008c00 rcx 0000000000006ebe rdx 00000000000c8c00
rsi 00000000f2010000 rdi 00000000000c0000 rsp 0000000000006eb4 rbp 00000000f2010000
[code]....
Google says this has something to do with Intel hardware and the way it handles real mode. run it with -no-kvm, but that's not much of a fix really.. so in the mean time I reverted to using qemu-kvm-devel-88 which works well, but is pretty old.
It seems today's kernel update has given a few people some difficulty - but my symptoms seem pretty unique.
* I go through GRUB normally. I 'esc' out of plymouth, and watch my services start. I get message 'mdadm: No arrays found in config file'. Don't remember seeing this before, don't have any RAID devices.
* Next, my file-system gets re-mounted in read-write mode (don't know if this is normal or not). Then, my services begin to start-up. My last service is 'crond'. All services start normally. When it gets to 'crond' the [OK] status is never reported. Visually, the screen flickers a few times, stops, then nothing happens. I can type characters though, and they do show up.
* If I then shutdown my computer by pressing the power button, the shutdown procedure begins. 'crond' shuts down successfully (indicating it started just fine), and the computer goes down normally.
* I don't believe this is an NVIDIA issue. I rescue-moded and changed my XORG.conf to the basic VESA driver to eliminate this possibility.
* Worst of all -- No older kernels work now either. They behave in the same way. When I try to boot to other run-levels, no luck either. This tempts me to think the problem might be file-system related and the re-generation of grub.conf threw something off?
found this in my boot log nvidia.ko for kernel 2.6.31.12-174.2.22.fc12.x86_64 was not found. and the driver is disabled and X is not working correctly. I tried removing the driver "yum remove kmod-nvidia "
then re-installing and rebooting. same issue I went to the fusion site and followed there install guide again same issue. made sure the free driver is blacklisted in grub.conf kernel lines
I updated this morning to the latest bugfixes for F13. For some reason, networking has become un-available after the required re-start. I am using a fixed IP. Tried to add eth0 DHCP, which initially worked, but became unavailable after a few minutes as well. I suspect there may be an issue with the card's MAC address which may or may not be detected correctly.. Has Networking been updated somehow in this bugfix release?
View 2 Replies View RelatedI updated Firefox 4 beta to the latest version, and now all my bookmarks are gone. Thanks to x-marks and other means I have backups, but I'm not able to restore them to the updated browser.
View 5 Replies View Relatedsudo yum update
Loaded plugins: fastestmirror, presto, refresh-packagekit
Loading mirror speeds from cached hostfile
* fedora: ftp.linux.org.tr
* livna: rpm.livna.org
[code].....
Just last week I upgraded to F14. Just today I did the latest yum upgrade, and it included an update on Open Office. (1) I now have Open Office 3.3.0 OOO330m14 (Build:9542). According to the OO Web site, version 3.3.0 is still beta!!! 3.2.1 is still the stable release for download. What is Fedora doing? But that's just a general question; here are some specifics. Printing is virtually broken.
(2) Just opening the File -> Print window takes almost 5 seconds. The blue bar along the bottom of the window shoots across 8 times!! I'm hoping this is not the price paid for the new feature of having an unreadable copy of page 1 appear on the left side of the "Print" window!
(3) The "Properties" button is definitely broken. Click it and select the "Device" tab. I set "Printer Quality" to "Draft Grayscale." Then suppose I print 5 pages. Then I want to print the next 5 pages. The Print Quality is back to Normal! And that's without even closing the document, much less closing OO. Closing OO should save the printer settings for a document. But printing two times in a row without closing the document should definitely preserve the settings I make. It doesn't.
(4) Under System -> Administration -> Printing, I set the print quality for the printer to Draft. That also is completely ignored by OO.
(5) In OO Tool -> Options -> Load/Save I have checked "Load printer settings with the document." That should surely imply that when you save a document, the printer settings are saved with it. They either are not or they are not loaded or they are ignored.
(6) When I select the page numbers to print, that is so slow, the numbers don't even appear the instant I type them. That blue bar across the bottom of the window keeps shooting across until all the numbers finally appear.
(7) Under System -> Administration -> Printing there are two driver choices for HP Officejet 5600: hpijs and hpcups. Neither makes any difference for this behavior.
(8) I have several printers. Not even the printer I selected for doing the printing is preserved from one set of 5 pages to the next.
Who has ruined everything? Fedora or Open Office? On a more practical level, any ideas? Am I missing something? I've used OO with Fedora for years. None of this ever happened before. I NEVER had to select the printer and reset printer quality EVERY TIME I printed without closing a document. Plus, for any new document, the printer quality options in OO would be set to what I specified in System -> Administration -> Printing.
Update last night brought in streamtuner2 and it seems to be working fine so far.
View 2 Replies View RelatedI 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.
View 2 Replies View RelatedI'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!
View 2 Replies View RelatedHow do I update to the latest java version?
View 9 Replies View RelatedCreating a new thread for the specific chipset. Laptop is an Acer 5534 with the Atheros chipset. Normally uses the Ath9k driver. To get it to work originally I had to download, compile and install the latest compat_wireless drivers. See post here: {URL] I did the update that came through today and after the reboot there was no wireless internet. It alternates between reboots between having no wireless networks at all detected to never connection to the [AUTO] network previously defined. To fix the problem, I downloaded the latest compat_wireless, compat-wireless-2009-12-11.tar.bz2, and followed the same procedure. I did not do a make clean. To solve the problem temporarily, I edited the grub config and set default to 2 instead of 0 (1 would be 0 in recovery mode).
View 1 Replies View RelatedI'm running 10.10 on a Lenovo x200. I have been running, happily, with 10.10. Yesterday, the update manager installed:
PHP Code:
After this update I am unable to Suspend. The screen goes black, the harddisk spins, the moon blinks a couple of time and then I'm presented with the Lock Screen.
I have:
Kernel Linux 2.6.35-25-generic-pae
3.6 Gib of Memory
Availabe disk space of 75.6 GB
Update to latest kernel 2.6.38?
Code:
paneas@paneasbox:~$ uname -a
Linux paneasbox 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:46 UTC 2011 x86_64 GNU/Linux
I want to update my kernel to the latest version from kernel.org, which is the mainline 2.6.38-rc8 .
EDIT: I found this guide [URL].. and I will give it a try