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??
View 14 RepliesI 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.
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 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.
Code:
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 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]....
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 attempted to upgrade a Slackware 13.0 fresh install to current. First I updated 13.0 by running:
Code:
slackpkg update
slackpkg upgrade-all
I then amended the mirror to current and ran the following commands
Code:
slackpkg update
slackpkg upgrade-all
[Code]...
I just upgraded my Slackware64-current version to the latest kernel 2.6.32.3. 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?
so, I compiled the 2.6.35.7 kernel yesterday and used the config from 2.6.35.6 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 2.6.35.6 config Has anyone else had issues with 2.6.35.7 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.
Lost my wireless keyboard and mouse upgrading slackware current.Boot seems to be normal.I just can't login, cause have no keyboard.
View 2 Replies View Relatedslackware-current kernel 2.6.35.10-smp for instance if i just want to connect to wep ap. i done
[code]...
it says waiting for carrier and it just time out, im wondering why i read somwhere that its not working good with slackware 13.1
I recently upgraded to slackware-current from Slackware 13 via slackroll, and have only encountered one problem. My file manager no longer thumbnails images, and icons (mostly PNG) aren't appearing no matter what GTK theme is set. Running from the command line produces no errors, and when brought up in something else (say feh /path/to/icon.png) it works perfectly. This is the only hitch I have encountered so far. The same thing happens with emoticons in Pidgin. Does anyone know of a fix?
View 5 Replies View RelatedFirst time I've done this in awhile Upgrading my Slackware64 -current VM, following the standard routine that has always worked in the past -
Code:
slackpkg clean-system
slackpkg install-new
The clean-system removed 2 packages -
util-linux-ng
eggdbus
Installpkg will no longer work, complaining that the rev command is not found. The problem hit with the removal of util-linux-ng. I cp'd util-linux to ~/. Extracted with tar and executed the doinstall. Fixed.
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
[Code]....
This happened with generic stock kernel and is also happening with 2.6.36.2 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?
View 6 Replies View Relatedafter update to slackware current 4 days ago i cant get sound working in wine in starcraf 2 i mean i got sound in instalation but not in game and i get error when i wanna configure sound in winecfg
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find '{PCM,Line} Playback Volume' element
err:alsa:wine_snd_pcm_recover underrun occurred
err:alsa:wine_snd_pcm_recover underrun occurred
in game i dont got that error but sound dont work btw my sound card is asus xonar essence stx
I've upgraded Slackware-13.1 I had installed to Slackware-Current using a local tree I had download with mirror-slackware-current.sh script, but when I rebooted I could not get the graphics to load. I think it's because I've also modified /etc/groups and add an username after audio: and video: group, but I forgot that and had to remove slackware from the machine.
View 4 Replies View RelatedI've tried a few different ways to install the ATI graphics driver "fglrx" to get 3D acceleration.If I try to install using the standard file "ati-driver-installer-10-4-x86.x86_64.run" from the ATI web site it appears to work but then I discover it actually got an error.I saw a reference to ATI requiring 32-bit libraries to install their 64-bit driver. Is there a link or post that explains how to add the 32-bit libraries. Will that solve the problem, or will I just waste more time trying that?
View 6 Replies View RelatedI use Alien Bob's mirror-slackware-current.sh with an excludes.txt to only download the parts of current that I want. Unfortunately it is not working for part of the exclude.txt file and I am at a loss to know why.
The excludes.txt is
Quote:
slackware64/e
slackware64/f
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txt
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txz
[code]...
This ignores e/ f/ y/ testing/ pasture/ source/ and usb-and-pxe-installers/ It also ignores most of kdei/ and /extra It is meant to ignore most of extra/source and just download the source for flash-player-plugin, but it is ignoring all of extra/source/, however the same syntax is working for kdei/ and extra/.
I have been using slackware since version 10.1 and really like it. I have never had a problem until lately, version 13.1 has been stable as a rock for me. The first 2 or 3 updates to current ran well but then the problem started. After installation Slackware would get to the splash screen and bring up the first picture of a disk drive then just hang and never go any further. I do have a good burn on the dvd, have checked the md5 and burned at 4x. then slack 13.37 does the same thing. this is on 4 different computers with several different video boards.
View 8 Replies View RelatedThis is not an earth-shattering issue, but, something I've recently noticed with the Chatzilla add-on for Seamonkey in Slackware-current. Maybe it is just my problem.If I add Chatzilla to FF 4.0 everything works as expected, that is, when I launch Chatzilla the default start-up window shows up with a list of IRC servers to click on (freenode being my favourite).
However,when I click on Chatzilla in Seamonkey I get a blank window that shows up, there is no server list. I noticed that the window in Chatzilla went blank for Seamonkey recently after a -current update (maybe a library issue?)
I'm very keen on getting Mumble installed on my slackware -current 64 bit install. I found a slackbuild script for 12.2 here, but changing the version number resulted in failure. I also tried following the build instructions on the Mumble website, which failed with the following.
Code:
neil@slackbox:~/Downloads/mumble/mumble-1.2.2$ qmake -recursive main.pro
Reading /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
WARNING: /home/neil/Downloads/mumble/mumble-1.2.2/src/mumble11x/mumble11x.pro:33: Variable LIBPATH is deprecated; use QMAKE_LIBDIR instead.
[Code]...
I wish to do a fresh install of Slackware without KDE. I could use my Slackware 13.1 DVD but I thought, why not give -current at try? Is there a -current ISO or must I install 13.1, without KDE, and then upgrade to -current? Or, is it possible to remove 'all things KDE' and then upgrade to -current?
View 8 Replies View Relatedi just updated my slackware to current, and every time i try to log in in my kde session my desktop is upside down.i mean literally everything is upside down, the only way i can have a usable desktop is with the "fail-safe session" of kde option on kdm which is what i'm using right now.does anybody know how can i solve this?i would post a snapshot of the upside down desktop but i can't do anything when i'm using it. fonts, windows, panels, icons everything is upside down..i solved this, just reinstalled the nvidia drivers and everything is goood again
View 1 Replies View RelatedI'm running slackware-current in a virtual machine on virtualbox 4, 512 mb ram, 1gb swap.Everything works fine, except the x11 mouse. Xfce will start up fine, and show the 'tips and tricks' dialog, and then freeze. I can't change to a TTY, or click. The mouse moves, but doesn't click.
View 13 Replies View RelatedAfter 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 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.
Is there any way to install "VirtualBox-3.2.12-68302" in the "slackware64-current" (Kernel 2.6.38.7) ?
I have problems with the 4.0.x version of VB!
The version "VirtualBox-3.2.12-68302" works fine with my hardware!
I tested using "VB 3.2.12" and Slackware64-13.37 (kernel 2.6.37.6).
I get the warning when I try to install a guest OS in "VB 3.2.12" running slackware64-current ...
Quote:
There is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
As root. Users of Ubuntu, Fedora or Mandriva should install the DKMS package first.
This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary"
And still
Quote:
Failed to open a session for the virtual machine Slackware12.0.
The virtual machine 'Slackware12.0' has terminated unexpectedly during startup with exit code 1.
Result Code:
Got an Asus eeepc 900a. Runs Intel 915 graphics. Upgraded to slackware current last week. X would not start. Based on info here, I reverted back to earlier libdrm and xf86-video-intel. That got it working again.
Updated Slackware current again today. I think I got a new kernel. Now, halfway through boot time, the screen goes blank, then comes back and the font is tiny. Gone into framebuffer mode. If I start X, it just freezes. Nothing but a reboot will get out of it.
I have vga=normal in lilo.conf, but I read that this is no longer used. I can find no way to turn off framebuffer mode. From other threads here, I have tried append="i915.modeset=1" in lilo.conf. Has no effect.
I could revert Slackware to 13.0 from current, and that would make the eeepc useful again. Is there anything else I should try?