Slackware :: Udev Start In Current Provokes Kernel Crash Because - Wrong - Boot Option
Dec 24, 2010
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
Where do I change the option to have samba start during the boot process? I've googled and I've found old posts that say it's a line in /etc/rc.d/rc.inet2 but in my semi-current box, I don't see the part about starting stopping the samba server.
After the bunch of updates with current, my custom kernel (2.6.33) can't boot.
The error is: /sbin/e2fsck: No such file or directory while trying to open /dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
The /dev/sda6 is ext4 and is ok since it can boot with official huge smp kernel 2.6.33.
My custom kernel can boot before this bunch of updates in current. What i missing in kernel?
I'm writing for my brother who was running Karmic on a Microtel desktop.He'd been having trouble with blank cds (data cds and dvds didn't cause this problem) crashing his box so he uninstalled and then installed udev package.Now when he tries to boot the box goes into a memory test and then reboots into the memory test over and over. He tried to check the installed kernels to choose one that might boot but there are none listed (he pressed "esc" to see the list-it's empty).He tried booting from a live cd and that won't work either. The cd drive spins but nothing else.
I'm running Scientific Linux 5.5 (equivalent to CentOS 5.5), and over the past two weeks, I have had a problem with my root partition filling up, preventing anyone from logging into the server.After searching for large files, and finding none, I was mystified when du told me that the root partition had only 660 MB of disk space used, whilst df showed it full. The problem was this: the /var/crash directory had been filled up by an 8GB crash file. Now, I'm a 'proper' sysadmin and make sure that /var has its own mount point, so the crash should not have touched the root partition at all. Except it did - instead of writing to /var/crash on /dev/mapper/VolGroup00-LogVol04 which is mounted as /var, it wrote the file to /dev/md0 directly, so when all the file systems were mounted, those files were hidden under the mounted /var.
Is there any Slackware-current or Slackware64-current users in the LQ Slackware forum experiencing lags or slowdown on Dolphin file manager on KDE 4.5.1? I experienced this first on KDE 4.5.0, after the current update KDE to 4.5.1 I still have this problem.
Hovering mouse on a file can take a while, opening a text file with kwrite took several seconds and dolphin window will appear blank (like hang). Sometimes Dolphin crashed when opening file, changing directory or hovering mouse on a file.
Quick googling points to this discussion at http://dot.kde.org/2010/08/31/kde-releases-451 which suggest a bug in libdbus.
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 126.96.36.199 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
I just installed Slackware 13.1 x86 on a new laptop (you probably remember me from my audio post). I am having one other issue. My root file system is formatted as EXT4. When my computer boots, it tries to mount it as EXT3 then EXT2, fails both types and then tries EXT4. Here are the messages.
Code: EXT3-fs (sda2): error: couldn't mount because of unsupported optional features (240) EXT2-fs (sda2): error: couldn't mount because of unsupported optional features (240) EXT4-fs (sda2): mounted filesystem with ordered data mode So, eventually / is mounted correctly, but I think this is slowing down my boot time. Does anyone know how to fix this.
I'm trying to configure gpsd 2.96 to start automatically from udev rule on a Slack 13.37 box.1. I've compiled and installed gpsd from sources and made sure it starts manually.2. I've copied the /lib/udev/gpsd.hotplug and /lib/udev/gpsd.hotplug.wrapper scripts in their places from the source tree and made them executable.3. I've copied the gpsd.rules file from sources into /etc/udev/rules.d4. I renamed it 99-persistent-gpsd.rules to run late in the bootup process.5. I've copied the /etc/default/gpsd file from sources and made sure it has the right settings inside.
Now, for the results. If I plug the gps usb dongle in while the system runs, it starts gpsd if it is not started, and it connects to it just as it should. But if I start the system with the dongle in, gpsd doesn't get started during boot. I can't find any relevant message in /var/log/syslog or /var/log/messages for boot time. There is stuff there from when I plug the dongle in while the system is running though. It's like udev ignores the rules for it at boot time.Is there something in the Slackware boot scripts that would prevent running those scriptssd.hotplug.wrapper which in turn runs /lib/udev/gpsd.hotplug which is a Python script)?Here is the contents of 99-persistent-gpsd.rules (ignore the comments referring to Debian, it was meant for a Debian box). My usb gps adapter is the first one - the Prolific chipset one:
I have just installed slack-13.1 on an acer aspire one netbook from a usb stick by booting the install kernel with noudev. I was able to do a complete install including lilo but upon rebooting my boot hangs when encountering my webcam.I see enough info to note the id as 0c45:62c0. This is a microdia webcam which I may be able to do something about later but in the first instance I'd like to be able to boot my system. The bios is very basic and there is no way to disable devices.
I just upgraded my Slackware64-current version to the latest kernel 188.8.131.52. Almost everything works just fine, except that I have no sound on the command line and in web browsers, anymore. I don't get any sound out of the command line program play and Flash.
For example, I have a few .wav files, that I can play with Kaffeine and Amarok, but when I try to play them with play on the command line, the program runs and displays that it plays the file, but I don't hear any sound. The same happens with XMMS, too: It displays the usual graphics showing the dynamics and the progress, but my speakers remain silent.
Also, alsaconf doesn't detect my audio hardware, anymore. I have onboard sound and a Creative X-Fi PCI card. Usually both were "seen" by alsaconf. Now it tells me, that it can't identify any audio cards.
On the other hand, when I go into the multimedia section of the KDE system settings, I can "Test" the audio hardware, and the onboard sound works great and I can hear the KDE welcome sound. I have already remove all packages withe 'alsa' in their name and re-installed them, including their compat32 peers, and rebooted several times. Up to now to no avail. Does anyone have a clue, what the problem is caused by?
After a fresh install of Slackware64-current could not get X to start correctly with the nouveau driver. When ever X started display was scrambled. Only kde would partially work with desktop effects enabled, but very slow. Without desktop effects enable kde was also scrambled. After trying several things and googling came up with the following. To get X to work created a nouveau-kms.conf file in /etc/modprobe.d with the following text.
Code: options nouveau noaccel=1 The one draw back to this solution is that Kde will not start with desktop effects enabled. Hopefully this will help someone else with similar problems. Maybe someone else has a better solution. video card: Nvidia Geforce 6150se nForce430
so, I compiled the 184.108.40.206 kernel yesterday and used the config from 220.127.116.11 doing make oldconfig,etc
its the vanilla kernel with BFS, BFQ[*], Tuxonice, aufs2, & squashfs-lzma patches after compiling and rebooting I have noticed that the mouse freezes whenever the pc cpu is running high cpu % this didnt happen before with any other kernel and as I said, I used the 18.104.22.168 config Has anyone else had issues with 22.214.171.124 kernel? hardware is amd athlon64 3300+ 2.4ghz 1GB RAM, on 32bit Slackware -current I am going to compile the vanilla kernel now and see what happens.
I put my slackpkg on the Current mirror, to install all the new sofware, including the new kernel... Now I tried to reboot the system and verify the speed of the all new packages, but KDM don't start! When I call KDM, it shines a little, show the mouse pointer and backs to term. When I call the XDM its a little different, it let me put my user and password, but after back to term too...
I am running Slackware64-current(multi-lib) and I have stumbled across something that I don't fully understand.I have read that the kernel-headers should not be updated as glibc is compiled against them and therefore requires that set of kernel headers. Recently the kernel version has been bumped a couple of times but glibc has stayed the same.Should glibc be re-compiled each time there is a kernel update?
Perhaps someone can explain, in very simple terms, the relationship between the kernel, the kernel headers, the kernel modules and glibc.
I installed Jolicloud in a new partition to give it a try. It's pretty nice. Anyway, it took over my bootloader, which didn't really bother me.
Now my kernel has automatically been updated to 2.6.35-22.41 or something. The option to boot from the new kernel does not appear. As you might imagine, I want to do that. My old bootloader updated this stuff automatically.
have just installed Ubuntu alongside Windows 7. I just went along with the manual set-up all through the install. I was expecting to see an obvious option on starting up my computer as to whether to run Ubuntu or Windows but it just goes right ahead and runs windows exactly as it did before the install.
I was installed linux mint in windows 7 using option "Install inside windows"... I got trouble with windows7 so i reinstalled it... but now there is no option to select OS at the start up... But i have the drive where i installed mint and all other files.. Is there any way to get it back.. Because i dont have time to reinstall mint...
I have just updated current to get the new kernel and things seem to have gone just a little wrong.After upgrading i edited lilo.conf and ran all seemed fine so i rebooted to find my pc wont boot it cannot find modules and there will be trouble ahead it think it says (will check the error and add it).So i thought no problem i can just boot from an old disk i have laying around and fix it from there. I only had the 12.2 install disk or ubuntu 8.10 live cd neither of witch support ext4 which i stupidly decided to format my drives in.
Anyways i now have a ubuntu 9.10 disk and have booted and try to fix things but am miffed at whats going on. If i chroot into my slack root and look in my /boot there is only the old files before the update, but if i mount the drive in ubuntu there are the new files from after the update.What has happened and how can i fix it? It has just occurred to me i could use a tmp dir and copy the correct /boot files there then in the chroot copy them to /boot may work ?
i upgraded my netbook to slack-current (32bit) and now When booting up dmesg shows these errors:
Code: [ 10.770199] [drm] detected 63M stolen memory, trimming to 32M [ 10.770267] i915 0000:00:02.0: irq 43 for MSI/MSI-X [ 10.770280] [drm] set up 32M of stolen space [ 10.770468] [drm:init_ring_common] *ERROR* render ring head not reset to zero ctl 00000000 head 02001000 tail 00000000 start 02001000
This happened with generic stock kernel and is also happening with 126.96.36.199 zen kernel. Is it something serious? Kde compositing still works, except it locked up few times when i was testing how windows wobble in kde, but not recently.
I was updating slackware-current via slackpkg and while it was downloading/installing latest kernel (and other apps) my battery went off and now the system can't boot. I was thinking to boot through a live cd and through chroot command to re-install all the new packages. Would it work?
I'm trying to take my current windows7 (x64) setup and make it into a dual-boot setup with slackware 13.0 (x32) and am hitting a brickwall. I guess I would like to know if I can salvage the situation without formating my windows drive. I fully intend to, but I had hoped to not do it this month. I'd like to get dual boot going so I can master it and acquire all the files/drivers I'll want and then format and do it 100% right next time.
Currently I have windows setup on a 3x 500gb Raid0 onboard array which itself has been flawless. After I shrunk my current partition size to give me about 25gb of free space I proceeded to setup Linux, and I was unable to perform the cfdisk portion for partitioning the array for Linux.
I tried using cfdisk: /dev/hdx (a1-a3,b1-b3) /dev/sdx (a1-a3,b1-b3)
I even attempted to locate with: cat proc/partition and tried using cfdisk on every device it located. It always said it was either an unknown partition table and should I start at zero, or bad partition. I was of course too concerned over my windows setup (which has almost 1tb of stuff I have not backed up) to go any further into the unknown.
PS: I have used Slackware before, back at 8.1, 10, and even a very brief interlude at 12.0, this is my first attempt on this computer however with 13.0, it is currently running fine on my laptop and my PS3 (Laptop is even dual booting 7/Slack13. Albeit without raid)
Phenom 9850 M2N-SLI Deluxe (Nvidia AM2) 4x1gb of 1066 kingston hyperX 3x500gb WD Caviar Black Sata2 3.0
I'm running Squeeze and I've been running into the r8169 hang problem (see [url]for example). A temporary (until the driver foibles in the kernel are resolved) solution that seems to be working for many people is passing the boot option "pcie_aspm=off" to the kernel.
Apparently, either I don't understand grub2 at all or my kernel doesn't like me very much. I put the option in grub.cfg like so:
However, it appears that the kernel, for whatever reason, is either not being given this boot option or it's not interpreting it correctly. When I run lspci -vv I get this for my r8169 ethernet card:
The relevant section is LnkCtl: ASPM L0s L1 Enabled; indicating that ASPM is still on.
After the updates galore of yesterday in -current, I began to update my system using slackpkg. However, after upgrading the kernel packages, I had a power problem and the system went down. (I had run lilo first, before the blackout happened) Upon powering it on again, my system won't boot. The kernel loads, and then init takes control, but when it comes to the regular fsck, the boot halts with a big, scary warning message that the filesystem might have an error and libblkid.so.1 is missing.
Be advised that the packages in the big update of yesterday were installed on alphabetical order. An inspection on the Jan 25-updated version of Slackware-current on my laptop reveals that the library in question is part of e2fsprogs. That's odd; if there was an update for it, it should already have been installed, but the system complains that a file from that package is missing, anyway. All this boils down to: my system is now unusable, unable to boot, and I really don't have a clue on what to do.
I need to install any version of Debian with the Debian Kernel version 2.6.22-3-686. I don't mind what version of Debian it is, I just need it to have this specific kernel! Debian Etch comes with 2.6.18-4-686 and Lenny comes with 2.6.26-2-686 so the kernel I need is obviously somewhere in between.
I have tried using the following commands to see if kernel 2.6.22-3-686 is available for download via the apt-get method in both Debian Etch and Lenny but it is not...
So does anyone know where/how I can download specific kernels and install them for use? I have a computer sitting next to me that has multiple kernels as an option on boot, and they all boot into the same system, however I do not know the person who set up the computer so cannot ask them how they did it