"Upgraded" to the 2.6.38.4 kernel this morning and now Truecyrpt fails to mount encyprted files and returns the message:
Quote:
failed to setup loop device, pathtofile
As Truecyprt worked just prior to installing 2.6.38.4, would it be safe to assume there is some sort of conflict?
I have Slackware 13.0 installed with the newest stable kernel (2.6.32.3) on an hp notebook with ati hd3200 igp. What happens is that when I try to buildpkg the catalyst drivers, it fails on the new kernel but not on the original one. I've been searching for a solution for a few days now. found a few that involved patching some files, but none seem to work or I can't make them work. I could probably use the binary installer but I would prefer not to.
Here's the output:
Code:
sh ./ati-driver-installer-9-11-x86.x86_64.run --buildpkg Slackware/Only_Module
Created directory fglrx-install.hokais
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.672......
ATI Technologies Linux Driver Installer/Packager
Generating package: Slackware/Only_Module .....
I'm trying to compile a newer version of devicekit-power (currently I have 009) so maybe I can suspend/hibernate my laptop again, after I updated the kernel. I installed every package "./configure" asked, so it made a Makefile. When I use "make", it builds a few files, then I get this error:
[code]...
Also, is upower-0.90/91 the same thing but newer?
I had an issue with the module build for vbox 3.1.2 breaking on the latest kernel ( /etc/rc.d/rc.vboxdrv setup ). Apparently the issue is that a kernel header (autoconf.h ) has changed its location in the module tree and hence the issue.
2 options:
1. upgrade to 3.1.4
2. create a symlink as follows
cd /usr/src/linux/include/linux
ln -s ../generated/autoconf.h autoconf.h
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
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 2.6.32.2 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
[code]....
it's possible to compile the 2.6.37 kernel patched with the autogroup patch on a Slackware 13.1 system running 2.6.33.4-smp with 2.6.33.4 headers? I just compiled and installed the 2.6.37-autogroup kernel from AUR on my ARCH setup and I like it especially when using firefox with lots of tabs open and other background apps also running. I did notice a speed and smothness difference in my ARCH testing setup with this kernel patch and I can get same results in 13.1??
View 1 Replies View RelatedI'm trying to bring my Slackware system back to life as my XP HDD is dying... I've got everything working except for my audio. I got a new motherboard (ASRock P43DE3) and it has a VIA VT1708S as the onboard audio. Is there any way I can get this working without rebuilding the kernel?
View 5 Replies View RelatedI 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??
View 14 Replies View RelatedI'm currently trying to install unRaid on Slackware following this tutorial :[URL].. I'm new to Linux and after many hours, i finally managed to build the new kernel for unRAID (2.6.32.9). But audio on HDMI port doesn't work I tried alsaconf without success. HDMI sound works when i boot into the old kernel.
My codecs are :
Code:
root@unraid:~# cat /proc/asound/Intel/code* | grep Codec
Codec: Realtek ALC888
Codec: Intel G45 DEVIBX
Code:
lspci -v:
[Code]...
Fresh and Full install: Slackware 13.37 64-bit x86_64. What is the correct procedure to switch from huge kernel to 2.6.38.4 kernel?
View 6 Replies View RelatedAs the post title says I have attempted to move my FC11 from a 120 gig ide drive to a 250 gig sata drive. I have tried all of the following with the same result listed below: Basic setup is as folows:
old hdd /dev/sda1 (boot) /dev/sda2(swap) /dev/sda3 (/)
attempt 1- boot fc11 live cd with old drive detected as sda and nwe drive detected as sdb.
dd if=/dev/sda of=/dev/sdb bs=512
attempt 2 - boot into fc11 live cd fdisk remove old partitionon /dev/sdb and create exact copy of partition table on /dev/sda on /dev/sdb - mark /sdb1 as bootable and copy /dev/sda1 + /dev/sda3 to /dev/sdb1 and /dev/sdb3
dd if=/dev/sda* of=/dev/sdb* bs=512 (* denotes 1 or 3 respectively)
attempt 3 boot linux rescue cd based on debian
run gparted to remove old partitions on /dev/sdb
use gparted to copy partitions from /dev/sda to /dev/sdb
All of the above result in the following (as best as I can describe it)
system self checks OK
system loads GRUB menu -OK
system appears to load kernel and then hangs after outputting device information regarding my USB keyboard and mouse.
Is there some magic that I am missing? system.map perhaps? Additonal info: grub.conf looks like:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
[code]....
The boot process fails using; 2.6.30.9-96.fc11.x86_64. I am able to successfully boot by selecting 2.6.30.5-43.fc11.x86_64 from GRUB. The last few messages I receive when booting using 2.6.30.9-96.fc11.x86_64;
ADDRCONF (NETDEV_UP): eth0: link is not ready
Sky2 eth0 link is up at 100 mps, full duplex flow control rx
ADDRCONF (NETDEV_CHANGE):eth0: link becomes ready
audit (1257757711.701:20095): auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 op=remove role key=null list=2 res=0
audit (1257757711.701:20096): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1
After updating my kernel from 2.6.34.7-56.fc13.i686 to 2.6.34.7-61.fc13.i686 I can't boot anymore. The error message says: "No root device found Boot has failed, sleeping forever."
I'm booting from 2.6.34.7-56.fc13.i686 now but I would like to sort this thing out. What should I do? File a bug? I never did that, so I don't know where to go.
New kernel Fails to boot. video driver is current and I tried reinstall . The .19 Kernel works fine
View 2 Replies View RelatedSo I just finished doing a Hardy based LiveCD. I made an installation in VirtualBox, installed some packages, and then compiled a totally new kernel, 2.6.35, actually this one: [URL] I compiled squashfs support in the kernel naturally Everything seems to be fine, the system boots up normally etc. But here comes the trouble: I make the iso file with remasterys (2.0.12-latest for Hardy) but this iso isn't able to boot.
It drops to busybox shell, casper.log says: /init: 1 /dev/sr0: no such file or directory Unable to find medium with the livesystem. My /dev folder is totally empty, it contains only the shells (8 pieces of tty). I don't know what's wrong...my rootfs is surely mounted, mount shows rootfs rw /
Update to 5.3 went OK a few days ago.Today there is updated kernel packages available but it fails dependencies on ecryptfs-utils.
View 3 Replies View RelatedI have dist-upgrade from Wheezy to Jessie, however it randomly freezes. Everything was okay with kernel 3.2, but when I run several applications kernel 3.16 fails.
At below you can see the dmesg output of Jessie:
Code: Select all[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09)
[Code] ....
I'm having problems with resume after suspend to RAM. The machine starts to wake up, but the screens (multi mon VGA and DVI setup) are black and the keyboard doesn't light up. After ~20 seconds there's some brief disk activity and then the computer reboots. 100% repeatable with affected kernel versions. My test method is simple, I boot the machine on the kernel's recovery option, log on as root and run "PM_DEBUG=1 pm-suspend". I haven't found anything in the logs after a failed resume.
Here's the situation:
I have a SSD disk. To get TRIM support I have to use kernel 2.6.33 or later, which means that the standard kernel in Squeeze is too old.I have Nvidia graphics, and there was a change in 2.6.34 that breaks older versions of xserver-xorg-video-nouveau (version 0.0.15, used in Squeeze), I can't use Debian Squeeze with a kernel newer than 2.6.33.x.My machine (XFX GeForce 9300 motherboard) won't resume from suspend to RAM if I use a kernel newer than 2.6.36. There are no BIOS updates available.
My options:
Install newer kernel from Squeeze backports (2.6.38.2 last time I tried). <--- Not doable b/c of resume problems. Upgrade to Wheezy, which uses kernel 3.0.x. <--- Not doable b/c of resume problems.Compile a vanilla kernel. So basically I'm forced to compile my own vanilla kernel, 2.6.33.x on Squeeze or 2.6.35.x on Wheezy. I won't be stuck with an unsupported kernel version in the near future, but so far I've failed miserably.
I know that the latest kernel version where everything works is 2.6.36.x (no longer maintained), 2.6.37.0 and later cause resume problems (I've tried 2.6.37, 38, 39 and 3.0.0, .0.1). I've tried doing a git bisect on the kernel, but didn't succeed, ended up on 2.6.36-rc5 which is weird considering that 2.6.36.4 works. There may be several suspend/resume bugs in different kernel versions that messed up the bisecting results.
I have upgraded at lucid from karmic.I have a little peculiar setup. My root partition is on sda3 and I mount the following:/usr -> /dev/sdb1/var ->/dev/sdb2/home -> /dev/sdb3(sdb isn't really a SATA disk but a PATA).When I boot with the new kernel 2.6.32-22 mountall stops with error messages that /dev/sdb2 and /dev/sdb1 are not ext2 file systems(this message comes from fsck.ext4??-It's using a ext4 program to check for ext2??)and cannot be mounted.Of cource those are normal ext4 filesystems which are being mounted without any problems with the last karmic kernel 2.6.31-21 which is what I am using)
View 2 Replies View RelatedI recently got the Message, that i should do a partial System Upgrade. It included an update to Kernel 2.6.34. Since this update, i cannot boot with this kernel:
Code:
Mounting none on /dev/ failed...
i can still boot with older kernels, but many drivers including wifi and graphics drivers dont work there anymore.
I've had this problem two times before and solved it once by following a guide, the other time by formatting. It always happens when it fails to wake up from suspend. Usually I am unable to even mount the drive or access the files. This one is different in that now I can actually access my files for the most part but this comes up on boot. I backed up most of my files (except it still says I don't have permission to access some of them) but I would like to get it back up and running without formatting. If I boot in recovery mode it stops at this. I took a picture but I rewrote some of it here.
Firewire_core: created device fw0: GUID 00016c000061b4b4. S4???
in/sh: cannot open ro
Kernel panic - not syncing: attempted to kill init!
Call Trace:
[<c05c8283>] ? printk+0x2d/0x32
etc
Image posted here: [URL]
on ecs gf8100vm-m5 motherboards (which have gf8200 chipset) hardware is detected ok. result from lspi|grep Audio gives
Code:
00:07.0 Audio device: nVidia Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio (rev a1)
[code]...
using slakware64 13.1 modified sbo slackbuild for latest version..
View 7 Replies View RelatedI have the latest fbreader.Slackbuild via sbopkg. The compilation steps seem to run OK until, if I understand this correctly, it starts work on libzlcore, at which point things go wrong :
Code:
OK
The README says I will need liblinebreak, which I "Slackbuilt" with no problems.
Quote:
Trying to build ffmpeg in 13.37 but it fails with the rror above.
I'm trying to build/install KDE 4.5.4, but I run into problems with the bindings package. Build fails with the following:
[Code]....
I'm building using the KDE slackbuild from sources dir, with the new KDE packages. edit: Well I decided to just take the risk of a not working KDE and commented out the bindings package. All other packages build fine. After this I crossed my fingers and rebooted, KDE loaded up. I gave the bindings package another go, and to my surprise it did build now. Got KDE up to date and it seems to be running fine.
here is the output:
[code]...
NVIDIA x86-256.44 fails to build against 2.6.36
I think there is a problem with the sox package that comes with Slackware 13.1.I would appreciate any advice. I'm using the same file, 1.wav, in both cases. The output of file 1.wav is1.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 HzOn 12.1, I can runsox 1.wav -e stat 2> /tmp/stat.txt
bash-3.1$ cat /tmp/stat.txt
Samples read: 37096920
Length (seconds): 420.600000
[code]....
I know this is probably simple, but I have been trying to upgrade to the latest release of Opera, downloaded the Bz2 file, and when running source to package it fails with this error. Opera seems to be the only app this fails with. I got the same error on the previous release as well, so I just gave up and waited until Slackpackage.org finally got that release.
I searched here and the net, and did in fact find a previous post about this, but, truthfully, I didn't understand the explanation at all.
Anyone have any idea how to handle this error?