Do I need to add any special options to mkinitrd for AHCI configuration?
mkinitrd -c -k 2.6.37.6-smp -m ext4
Does it know I'm not in legacy PATA mode or do I have to add something to load AHCI module with it?
since an update to the latest -current version, it comes to an error inside the init script from the initrd.gz on my system, shortly behind the scan for encrpyted devices inside lvm containers.
The message is
Code:
mdadm: No arrays found in config file
1 logical volume(s) in volume group "vg" now activeash: missing ] mount: mounting crypt-vg-root on /mnt/failed: No such file or directory ERROR: No /sbin/init found on rootdev (or not mounted). Trouble ahead. You can try to fix it. Type "exit" when things are done. If i then unlock the crypted root device within the lvm, boot continues. I think this is a bug, because configuration did not change, and it worked before the update.
I'm doing a clean install on a new machine, and when I tried to boot the install DVD, ISOLinux gave me the following error:
Code:
Could not find kernel image: linux After some experimentation, I found that switching the SATA mode in the BIOS from AHCI to Native IDE solved the problem and installation is proceeding normally.
However, I want AHCI enabled. (I think, unless someone has a compelling reason why I shouldn't.) My web-searching suggests that if the system is installed in IDE mode, it won't boot if I switch to AHCI afterwards. Is this a common problem? Is there a workaround? Is it a motherboard issue?
Make the code work when RESUMEDEV is a symbolic link which has a relative path.
[Code]....
After installing Slack 13.37 on one of my systems while using my own (non-standard) kernel it refused to boot as the harddisk couldn't be found anymore. Investigation yielded that the ahci.ko driver wasn't loaded (but libahci.ko was). However I listed both ahci.ko and libahci.ko in the mkinitrd -m parameter so there had to be an error in the new /sbin/mkinitrd script. It turned out that a grep at the end of the script weeded out my ahci.ko module as the searchterm "ahci.ko" was already detected in the modprobe line for libahci.ko.
I decided to fix it in an easy way : I just prepend a "space" in front of the module name at the line where the grep is called :
[Code]....
I used mkinitrd to build an initrd from the slackware 2.6.37.6 sources. Lilo throws the following: "Warning: The initial RAM disk is too big to fit between the kernel a the 15M-16M memory hole. It will be loaded in the highest memory as though the configuration file specified "large-memory" and it will be assumed that the BIOS supports memory moves above 16M."
Also, I am running swap, / and home on an encrypted volume group. When the initrd boots (but prior to mounting the encrypted vg) I get a message saying that no modules are found-sounds like a daft question but is this expected? I expect that this is because initrd is looking for modules, but can't find them because the relevant partition isn't mounted.
I'd like to use a keymap not present in slackware "fr-dvorak-bepo" with mkinitrd because my root partition is encrypted by luks. So how can I generate a .bmap file from a classic .map file for mkinitrd ?
View 2 Replies View RelatedI'm installing Slackware 13.1 on a Samsung N150 netbook and am stuck trying to make the special keys do their normal functions when using a virtual terminal, that is not under X. Under X + Xfce it can be done via Menu->Settings->Keyboard->"Application Shortcuts".
In essence the question is how to make a special key (example Fn+Up to increase screen brightness) run a command in the background.
Changed title and text to make clear that the command should not run in a virtual terminal but while the display is being used for a virtual terminal, that is after Ctrl+Alt+F2 for example.
I've recently installed an internal optical drive (Blu-Ray RW: LG WH10LS30) into my dual boot system. The Windows partition had no trouble with this. However, ubuntu began taking ~30 extra seconds to boot. Once ubuntu finally gets running, the drive is not detected at all. dmesg showed the following:
Code:
$ sudo dmesg | grep -i 'ata2'
[ 1.430315] ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf098 irq 15
[ 2.777449] ata2.01: failed to resume link (SControl 0)
[ 2.933509] ata2.00: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.933521] ata2.01: SATA link down (SStatus 4 SControl 0)
[ 2.933531] ata2.01: link offline, clearing class 3 to NONE
[Code]...
Further investigation revealed that changing my BIOS settings for SATA from IDE to AHCI fixed this problem entirely. The ubuntu partition boots fast again, the drive is working. Except, this causes the Windows partition to fail completely. I'm wondering, what is the best way to fix this? Hopefully without a complete reinstall. Is there a GRUB command that could apply AHCI to only the optical drive during ubuntu boot?
Newbie here. I'm thinking about going from Ubuntu to Slackware and I just saw on Wikipedia that there is a number of projects that maintain GNOME binaries especially for Slack. So that made me wonder, why is that needed? What if I download a bare version of Slack and then build the standard GNOME version from source? Would that produce problems?
View 3 Replies View RelatedSlackware 12.2 has the unkind habit of deleting all the /dev/fd?u* floppy special files upon boot-up. I have to make another directory (I use /floppy) to contain these files so I don't have to keep copying them from an earlier distribution (12.1) Now, for example, to format a 1743 kilobyte floppy, I do fdformat /floppy/fd0u1743 mformat a:If I copy these special files to /dev (where they belong) then some part of Slackware Linux 12.2 deletes the special files when I power down and power up the machine.Slackware 12.1 and earlier leave floppy special files severely alone upon shutdown/startup.I cannot seem to "grep" a reference to /dev/fd anywhere in /etc/rc.d or its subdirectories. Why is Slackware 12.2 deleting them?
View 1 Replies View RelatedI am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/2.6.33.4-smp kernel modules tree found for kernel "2.6.33.4-smp"
I tried to look into the directory and there was only modules under 2.6.44.3. So I tried to change the command into: Quote: mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
[Code]....
What are the standard, common PHP extensions that should be enabled when configuring a new php installation? I need ldap so I know I should include that, but what do most LAMP servers configure with their PHP installs?
View 2 Replies View RelatedI am trying to build minimal php and mysql binaries. While doing so, I realize that there is no documentaries to state whether does compiling straight from the source without any configurations options set, ensure an optimized yet minimal build? I am trying out for my own personal website which will be powered by Wordpress 3. The previous method I used was using the package manager: "apt-get install php-cgi php5-cgi php5-cli php5-mysql mysqld mysql-server mysql mysql-client". I am trying out to mimic the binaries installed by the package manager through building from the sources instead. How do I know what configuration options did those repositories developers used? Is there any special configuration options used for those minimal yet optimized binaries? Does doing the following ensure a minimal build?:
1) ./configure
2) make
3) install
I figured since I did not use any configuration options, therefore it should be a minimal build right (Meaning the bare-bones)?
I just installed slackware 13.1 and my KDE is version 4.4.3, I want to upgrade to version 4.6.1 or at least 4.6.0. I have used alien repository and download KDE 4.6.1 but it doesn't work.
Are they any options to upgrade my KDE to 4.6.1 or not?
I made a mistake in Gnome Disk utility tool. Instead of changing the options for a USB key, I changed the options of the root partition.
In Initial state, automatic options were desactivated. I just activated them. And after desactivacting them, I realized my mistake and switched back to "non automatic options".
By doing this, I suppose that defaults values were used since now, the system starts in command line mode and no more in graphic interface mode.
When I try the "startx" command, I get a "read-only" error.
With the command "sudo mount -o rw,remount /" the graphic interface is started.
Below is the configuration of the partition under the gnome disk utility tool :
"Mount at startup" is checked
"Show in user inteface" and "Require additional authorization to mount" are unchecked
Mount options : nosuid,nodev,nofail,x-gvfs-show
Mount point : /mnt/eb11d4d6-75db-XXXx-XXXx
Identify as : /dev/disk/by-uuid/eb11d4d6-75db-XXXx-XXXx
Filesystem type : auto
I do not want to change anything that could leat to a critical error. So what do you think I should do ?
I'm running Testing and need to pass some parameters to my bttv tv tunner card, for this reason I created the following file /etc/modprobe.d/kozumi.conf with this content:
alias char-major-81 videodev
alias char-major-81-0 bttv
options pll=1 radio=1 bttv_verbose=1 card=151 tuner=38 gbuffers=4
The problem is that for some reason this options aren't properly set after booting the computer, I've tried different combinations for line 1 and 2 without success.
I'm used to rmmod the bttv driver and modprobe manually with those settings but I'd like to automate the process.
I'm having some trouble understanding the smartd configuration options which go in /etc/smartd.conf. I've had smartd running for close to a year now, and read the manual page for smartd and smartd.conf several times, and I still can't get my head around it properly. This is what I use in smartd.conf:
/dev/sda -H -f -S on -o on -n standby,q
-s (O/../.././(00|06|12|18)|S/../.././11|L/../../(3|6)/21)
-m <nomailer> -M exec /usr/sbin/smartd_mailer
The above works fine (I use a custom script because I use exim). However, I had two failing hard-disks on two different machines (sector pending attribute) - but I would only receive warning emails if I restarted the machines - not when the periodic tests were being performed. I have a number of questions, if any of you would like to share some light on this:
1. It is not clear from the manual page how the monitoring and alerting mode works. Do I get an initial email when I start smartd if something is wrong, and then no other warning email after each scan, even if there is a fault, unless the fault goes worse?
2. Can I force it to send me warning emails after each test (offline, online, short, long etc.) if the fault condition is still there, even if it hasn't gotten worse?
3. There seem to be a variety of parameters monitored. I was thinking that if I monitor bad sectors, and the hdd temperature - it should be enough to warn me when the hard-disk is failing? Would the -a switch in smartd.conf cover these?
4. I don't understand the difference between monitoring and logging in relation to alerts? Do I get alerts only if I log things?
5. Do I understand correctly that the -p and -u switch would warn me of *any* changes in SMART attributes, even if they don't represent risk of failure?
6. Is there a way of finding out if the scheduled tests (offline, long, short etc.) have been performed?
I have slackware 13.0 on my HP 520 laptop.My machine is connected to the internet and it also act as a gateway for other machine of mine.
I want to use mac filtering options of iptables.But i am getting following error
iptables v1.4.3.2: Couldn't load match `ac-source':/usr/libexec/xtables/libipt_ac-source.so: cannot open shared object file: No such file or directory
I've been googling and reading up on how to set build optimizations for my system, and after consulting the Arch Wiki, old threads here, and some mailing lists, I've concluded that the way to set CFLAGS, etc. is by putting this in /etc/profile:
Code:
export CHOST="x86_64-unknown-linux-gnu"
export CFLAGS="-march=native -O2 -pipe"
[code]....
I recently tried to upgrade my Slackware server's sendmail software from 8.14.3 to 8.14.4 and ran into a problem. In a nutshell all outbound non local mail is routed through a smart host requiring authentication. As a result I use a modified version of the "sendmail-slackware-tls-sasl-clamav.mc" to build the sendmail.cf. However, when I tried to run sendmail 8.14.4 with my newly created sendmail.cf I was greeted with the following.
Warning: Option: AuthMechanisms requires SASL support (-DSASL)
Warning: Option: AuthOptions requires SASL support (-DSASL)
Warning: Option: CACertPath requires TLS support
Warning: Option: CACertFile requires TLS support
[Code]....
Apparently SSLv2 is now considered weak and the directive is a good idea, but at present this directive is not supported by the sendmail in this package.
I need to add an option to my xorg.conf to enable "backing store", like this:
Section "Device"
Identifier "Miserable Old SVGA"
Driver "miserable"
Option"BackingStore""True"
EndSection
But I don't have an xorg.conf file in Natty. There are several conf files in /usr/share/X11/xorg.conf.d/, but I'm not sure which one to add it too (I can't find the Device section in any of them). I guess I don't even know if the "BackingStore" option is valid in the latext Xserver.
What is "--installdirs site" options in cpan configuration?
View 1 Replies View RelatedI'm currently upgrading my clients' CentOS 5 installation to use httpd-2.2.14 as we need it for the server to past some of the Hardware checks used in the PCI [Payment Card Industry] security test. I was basically wondering if anyone had the standard CentOS 'configure options' for building httpd/Apache so I could copy them to ensure it is a straight replacement for my existing 2.2.3?
[Code]...
I want to compile a kernel to add a few options that are not enabled in the huge-smp-2.6.29.6 that comes with slackware. specifically, i want to add TASK_DELAY_ACCT and TASK_IO_ACCOUNTING so that I can use iotop. I just want to add those 2 options to the new kernel, everything else I'd like to keep the way it is as the system has been running just fine. Will running 'make menuconfig' in /usr/src/linux default to the options that are used in the stock kernel?
View 3 Replies View RelatedI used btrfs, but my Slackware root is really a subvolume named system and not the root of btrfs. I do a similar setup of having the OS's root in it's own filesystem on FreeBSD+ZFS.Anyways, my problem lies in mkinitrd. There's no way to enter extra boot options, as I require subvol=system to be added to mount -o ro -t $ROOTFS $ROOTDEV /mnt.in the init script of /boot/initrd.gz. I don't reboot often and it's easy to manually remount /mnt with the correct options, however, is there another way of passing boot options to mkinitrd?
I see Patrick is the author of mkinitrd, so maybe this kind of option could, or maybe should, be added? I'm sure most people wouldn't make a subvolume for the OS's root, but I've been use to it with ZFS and prefer it for some reason.
I had some issues with my system hanging on the automatic configuration of the install so I searched the web for the issue. After reading this thread: Hangs at end of SuSe 11 install I used acpi=off apm=off nolapci as the install options and it worked. My question is, do I need to add those options to the /grub/menu.lst or will the install do that?
View 9 Replies View RelatedI need to enlarge the root file system on a Slackware 13.0 32-bit system; it's in a simple logical partition (/dev/sda6) -- no LVM, mirroring etc. This might be a good opportunity to change from ext4 to jfs, too.Routine procedure, no? No!First off I booted Knoppix 5.31 but found it doesn't have ext4 support (no efs2ck and running fsck results in "fsck.ext4: not found").So I booted Slackware 13.0 32-bit CD-1 only to get the same as with Knoppix.I do have a GParted-liveCD 0.3.4-11 but have had mixed experiences with it so am reluctant, despite having backups.
View 11 Replies View RelatedI noticed that there is a 1.0.1 version of xfce4-power-manager, so I tried it out last night. Note: It requires libxfce4ui >= 4.7. I compiled it using the same SlackBuild script as the one in Slackware 13.1. It compiled and installed just fine. However, when I logged out of XFCE and logged back in, I could only set a few options, and battery options were completely non-existant.
I double-checked, and my user account in in the power group. Has anyone else had a similar problem? In the meantime, I've downgraded back to the 0.8.5 version that Slackware ships with.
I'm familiar with editing Grub's "menu.lst" file to add additional OS's to the boot list. Does Slackwares Lilo have a similar config file ? I need to add a second physical drive with Windows 7 on it to the boot options in Lilo. If it's not a config file, how do I add a second os to it ? Slack and Windows are both already installed on two different physical drives so I won't be installing, I just need to add the Windows drive to Lilo.
View 5 Replies View Related
