Slackware :: How To Start KDM At Boot
Jun 5, 2010Is there a way I can tell the system to boot up KDM when the system is booted up completely?
View 1 RepliesIs there a way I can tell the system to boot up KDM when the system is booted up completely?
View 1 RepliesI'm loging my slackware as a simple user After each reboot I need to start cupsd for my printer nfsd and mountd to export my shared directories I use init 4 for my desktop I would like these services to start always without the konsol and the command lines.
View 8 Replies View RelatedI installed Slackware 13.1 a little bit ago, played around with it, performed an upgrade with Slackpkg, messed around with some settings, and chose a new theme. I had set the runlevel to 4 and when I rebooted after choosing a new login theme the screen just went black at the point where the login prompt should have appeared. I couldn't even get into the CLI. Using a LiveCD, I set the run level to 3 again and was able to log in, but when I try to start X the screen goes black and freezes again, so I believe my new login theme is the culprit. Is there a way to change to the default login theme from the CLI?
View 14 Replies View Related2nd and 3rd might be linux kernel problems but may help someone else so I included here.1st -- run level 4, /etc/rc.d/rc.4 and xdm -nodaemonJust installed 13.1 on an odd system, including building a new kernel.One thing I do is have the system boot to a command prompt and then run /etc/rc.d/rc.4 to start XBut I found that the rc.4 uses xdm -nodaemon flag and it was causing problems so I removed and all is pretty good. I still see some odd behavior with the virtual ttys sometimes.2nd -- when building a new kernel, I found I need the device-mapper butcouldn't tell if that was a linux kernel issue or something to do with lilo, I didn't want and don't need multiple disk devices like for LVM or MD so I didn't plan to have this enabled.3rd -- CONFIG_EXT4_USE_FOR_EXT23 When that kernel config option was selected and I have only an EXT4 filesystem, the filesystem was mounted as an EXT2, even though the kernel had no EXT2 feature. /etc/fstab specified EXT4 but the mount command showed EXT2. A silent problem that could leave an unpleasant surprise since EXT2 hos no journaling.4th -- I had to run lilo -C by hand in a virtual tty before finishing the install. This was what I had to do when installing 13.0 on different hardware. It seems that the lilo part of the install needs some sorting out.
View 9 Replies View RelatedWhere 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.
View 5 Replies View RelatedI 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?
So I got slackware 13 from the website and created 4 partitions (primary) and left some (100GB) space as I planned to install windows 7 in that. After installing slack, when I booted from windows DVD (rtm) in partition section it said I already have 4 primary partition so windows cannot used the rest of space despite the fact that it was free (windows even grayed all options like new partition and format etc. for that space). So I thought I'd create 2-3 primary partition for linux (slackware) so that windows can use the free space and make it a primary partition.
So, Next I formatted with slack (3 partition, 2 Primary, 1 extended, total space for slack 50GB) and after its installation I worked my way with windows, but it just created one partition of 100Gb, won't let me create any saying all primary partitions are created. Anyway, I created that partition and installed windows 7. But it messed up my lilo (slack won't show in boot menu) neither can I create any new partition.
After all I reformatted again created 2 partitions for windows (that actually became 3 as windows 7 create 100Mb separate partition for system). Installed windows correctly. Then I booted with slack , which allowed only creating 1 partition as 3 were already there. So I created 1 extended partition, in which I created 4 partition 1 to mount for /boot (100M), 1 for /swap (3G), 1 for home (10G), 1 for / (35G) everything worked fine till I reached last point to install lilo. At that point it said cannot install Lilo (I tried all options simple, expert, install to MBR etc.) but it just won't install. Anyway, after that it said you can install it manually so I clicked OK. Then it said setup complete, remove disk and press alt+ctrl+del to reboot, which I did. But there is just windows 7, no slack ?
I try to install Slackware to my IDE hard drive and boot first from Slackware DVD. After I loaded huge.s kernel, and tried to partition the hard drive using fdisk by entering "fdisk /dev/hda", I found out that the partition size is max to 3 Gigs instead of 80 Gigs.
I think the kernel is looking at my boot disk, which is around 3 Gigs. How can I make so that it looks at my IDE drive instead at my boot drive? Is there any manual that shows me how to install Linux from scratch this means I want to wipe out all my hard disk and install Slackware Linux there?
I'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
I installed Slackware 13.1 and Windows server 2008, I also installed LILO in MBR, I Found I can boot into slackware, but can't boot into Server 2008. then I use command bootsect/fixmbr. now I can boot into server 2008, but the problem is I can't boot into slackware. I try to install lilo to supper sector. it's not works. I only can boot my slackware by a USB stick.who can help me to solve this problem? I really need these two systems.
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 just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?)
I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
[Code]...
I've a multiboot machine and I recently installed Slackware64-13.1 on sda33. I added menu entry in SUSE boot loader and configured menu list as per [URL].. it returns GrUB error 15. Here is my menu list entry for Slackware -
Code:
###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
root (hd0,32)
kernel /boot/vmlinuz root=/dev/sda33 ro hdd=scsi
savedefault
[Code]...
My new job requires I use Windows and as such I put a second HDD in my laptop for the purposes of Window/Work The issue is that Windows will not install on this second disc (Windows cannot create partition or install to disc). I got around this by installing Windows to the first disc, then the second then putting Slackware back on the first but then I suffer the "Bootmgr cannot be found, press ctrl + alt + delete to restart".
I am using Lilo and I have never really had an issue dual booting them on the same disc (Admittedly over a year ago) but it is of the utmost important I have them on separate Discs. Has anyone encountered this and/or know a way around?
I've installed Ubuntu on my new desktop alongside Windows 7 (each OS is on a separate drive), I seem to have run into a small problem. Let me start with what I did:
- Unplugged 1TB drive from the PSU, BIOS was not seeing my formatted (and thus empty) 500GB drive and I couldn't put it into the boot order at all with the 1TB turned on.
- Loaded up the boot CD and was able to install Ubuntu 10.1 on my 500GB drive.
- Did a bit of configuring, shut my PC off and plugged my 1TB (with Windows 7) drive back in. I tried to see if I could now see my Ubuntu drive in BIOS but nothing is there - just the Windows drive is in the list of available drives to boot from (along with DVD-ROM and USB).
This is where I've run into my problem. What I want is to have a nice GRUB boot menu at the start like any other dual-boot system but just have the two operating systems on separate drives altogether.I did it this way because I was having issues with the advanced partition menu on the boot CD so just went ahead and followed the KISS method by unplugging the Windows drive.
I was told by a friend that if I put my Ubuntu drive into the first position in my boot order and the Windows drive in the second, then I could boot into Ubuntu and run a GRUB update command (he told me to google it) and that would create the necessary GRUB that had the entries for Windows 7 and Ubuntu.Both operating systems are 64-bit, I imagine that might make a difference in whatever help you guys can offer me. I love the hell out of both OS's and want to be able to use them interchangeably.
KDM does not start after upgrading my Slackware-current 32bit to KDE 4.4 using Alien Bob's packages.
In syslog I get:
Code:
What am I missing? (I used the exact same procedure on a 64bit Slackware-current installation and everything works beautifully)
A friend of mine threw me an OLPC (original model with 1GB of storage) that he was trying to put slackware in. He managed to install a minimal installation, but now it asks for the e2fstools (the stuff to run fsck on ext(2/3/4) partitions) which he didn't install (he formatted the "disk" as a single jfs partition). Is there any reason why it would want to have those tools given that there are no ext(2/3/4) type filesystems in that machine? And is there any specific init script (or udev rule) that can be edited to make it not try and check ext(2/3/4) partitions?
View 4 Replies View RelatedI successfully managed to install slackware on a laptop with a broken optical drive, no floppy drive and no option to boot from USB stick, with the invaluable help of AlienBOB's guide: some of the packages could not be installed during the installation. The fatal errors seems to occur randomly and the packages that I later had to install by hand were the following:-git-java (can't recall exactly what it was about)-linux-howtos-kdebase-workspace
View 4 Replies View RelatedI have, for awhile, had Ubuntu 10.04 as my main OS. I decided to go back to SW13.1, and added it in as dual-boot, with grub2 as my bootloader.
grub sees/boots SW fine.
But SW boots in 640x480, and is fugly, to say the least.
How do I change this? Grub currently runs at 1024x768. And in lilo, it's easy as pie to change the kernel boot resolution.
How do I do this in grub2? (Notice I said grub2, because it's MUCH different than grub, as far as config files and the like)
Actually, Slack64 runs just fine under VirtualBox on my old HP under WinXP, But the installer for Slack86 won't boot under VirtualBox on my Toshiba Netbook under Win7 starter. I tried updating the 13.1 install I have on there, but I get the same kernel panic when I try to reboot that. It always bails just as it is switching over to the new kernel. The dump fills my screen so I can't see the actual error. How can I capture that initial startup log? Slack86 runs just fine on my old Compac Armada 1700 (266PII 92M/12G), but that's a very different environment.
View 10 Replies View RelatedSlackware vers: 13.1
Netbeans vers: 6.9.1
JDK version: 1.6.0_24
Code:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb2d772fd, pid=2766, tid=2953837424
#
# JRE version: 6.0_24-b07
[code]....
I tried reinstalling both JDK and Netbeans to no avail.
After I upgrade my slackware to current(kernel 2.6.35.11),X could not start.My video card is ATI Radeon HD 4570.and I do reinstall fglrx like old ways :
Code:
./ati-driver-installer-11-2-x86.x86_64.run --buildpkg
and
Code:
installpkg fglrx-*******.tgz
But after restart, X could not start,and Keyboard does not respond. Also ,when I try init 3 and remove xorg.conf,The X can start with a low resolution(1024X768).In console mode,I got a high resolution(1366X768). So,is there a confict between fglrx and new kernel or What have I done Wrong?
Kde does not start after slackware 13.0 instalation. Mouse just stop and the computer freeze. When I type startx Kde try to start, but everything stop. Does anybody know what could be this ? What log should I look ?
View 3 Replies View RelatedI have upgraded from 13.1 to 13.37 on three PCs. No problems on 2 of these (home server and laptop), but on the third machine (main Desktop, where most KDE customisation had been done of course), KDE refuses to start for the main user (me). It will start OK for root and xfce will start OK for me, so X is OK with the updated NVIDIA driver that I have also installed. The KDE splash screen starts up and four of the five splash icons come into focus, but the fifth one never does. Some disk rattling goes on for a while but then ceases.
I have tried renaming the .kde folder and .kderc but this has not helped. Are there other KDE config files that I could try renaming / removing? Or are there log files / error messages somewhere that I should consult.
Obviously I am not in a position to change any KDE system settings from the KDE application.
Just tried KDE with a newly-created user and it's the same as with my user - no desktop. So KDE is only starting for root.
Hardware - Compaq615, video - radeon hd 3200 After clean installation of 13.37 x64, proprietary ati driver, multilib. xfce.
All was o.k., video rendering was direct etc., etc. then i rebooted, and system freeze at startx. Ctrl-Alt-Backspace not working, hard reset needed. I tried xorgconfig, Xorg -configure, aticinfig --initial, deleting /etc/X11/xorg.conf with no result at all. /var/log/Xorg.0.log empty. When i do startx from root - all is o.k, writing from root now.
I normally boot into runlevel 3. KDE is my default DE. I use
Code:
To open KDE. I would like to give the other DE's (full install of Slackware current) a fair try, but I am having trouble starting the other DE's from the command line. They all work from runlevel 4 using the kdm chooser, but that's just a hassle and in all honesty will likely irritate my lazy-bone to the point of not using them on a regular basis.
Booting into runlevel 4 isn't a good option because I am frequently experimenting and booting to the command line makes troubleshooting easier. What do I need to do to be able to start the other DE's in runlevel 3?
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
View 1 Replies View RelatedI can only start my Internet connection from the root bash. If i type pppoe-start/pppoe-stop in my user's shell it just says "command not found".
Any way to permit the users to bring the ppp connection up and down ?
I installed Netbeans 6.9.1 with JDK bundle, I have installed jdk in /usr/local/jdk1.6.0_2 but when I try to start Netbeans I get error
Quote:
which: no javac in (/usr/local/jdk1.6.0_2/bin:/usr/local/jdk1.6.0_2:/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)
which: no java in (/usr/local/jdk1.6.0_2/bin:/usr/local/jdk1.6.0_2:/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)
Cannot find java. Please use the --jdkhome switch.
I have javac in /usr/local/jdk1.6.0_2/bin, I looked. I installed last time and it have worked fine. What is wrong now ?
I've just install Slack 13 and had been looking into the website for configure info. What is my problem is the #xorgconfig does not start on my system. It says command not found. I had searched for answer on the web and found no answer so I post here for help. Is there anything else I need to install to get my intel graphic card display more then 1024 resolution?
View 7 Replies View Related