I have a windows xp and i wanted to install slackware 13.0, i specified the partitions in cfdisk, and when i tried to write the partitions in the disk, the error came as "THE DOS MBR CANNOT BOOT TWO PRIMARY PARTTIONS" I already have windows xp installed in my laptop. What could be the reason..?
View 1 RepliesI managed to do something that takes real talent to do: I broke my Slackware. I was chowning something for a user and, as I was really sleepy, accidentally entered "chown -R user /". It really didn't break, but it started to get glitchy because I couldn't fix it well enough. Then I rage-quit the game and wiped my whole drive except for my personal files. So now I'm here to learn how to properly install Slackware64 current out of the box and hear suggestions regarding partitioning schemes. First of all, I'm aware Alien Bob has a script to help automate the upgrading of the system. Is it the mirror-slackware-current.sh? Then what should I do? Install Slack and run the script or can I download things from another distro (I have Arch installed - love LXDE!) and use the Slack DVD to boot and choose it as the source?
If the suggested method is to install Slack first and go from there, I should upgrade slackpkg first, right? My other question is regarding partitioning schemes. I have an 160GB hdd and I used to follow this format: a small (200MB) primary /boot, a primary 20-30GB /, a primary 100GB (give or take) /home and the rest as an extended distro-hopping partition (at the moment I'm building LFS) plus swap. The thing is that I've been noticing a big inconvenience in this method. I have around 40GB left and sometimes I get curious about distro x or y and want to install it so I have to change the logical partitions and my swap gets renamed, which makes me have to edit my fstab. I already changed this setting sda1 to be swap. I'll be installing in a desktop personal computer. Some college work, but nothing too hardcore.
I'm slack 13.1, I am trying to install it, but always gives an error. I type cfdisk and appears this error:
Fatal error: bad primary partition 2: Partition ends in the final partial cylinde Press any key to exit cfdisk
I get this error:
Error: requested datatype primary not available
# rpm -q centos-release
centos-release-5-3.el5.centos.1
None of the following actions fixed the error.
# yum clean all
# rm -f /var/lib/rpm/__db*
# rpm --rebuilddb
[Code]....
I've just seen a strange set of error code during my boot sequence:
WARNING: at mm/page_alloc.c:1813 __alloc_pages_nodemask+0x5ce/0x6c0()
Hardware name: MS-7250
Modules linked in: lp fuse nvidia(P) joydev snd_cmipci gameport rtc_cmos rtc_core thermal processor snd_pcm snd_page_alloc snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore thermal_sys i2c_nforce2 rtc_lib button agpgart k8temp hwmon psmouse sg i2c_core ppdev parport_pc parport forcedeth serio_raw evdev
Pid: 1543, comm: mount Tainted: P 2.6.33 #2
Call Trace: .....
The machine appears to run normally otherwise.
One question:An OS only can boot from primary partition, not in an extended partition ?
grub 0.97
So I was creating a bootable USB stick with Unetbootin and accidentally selected my hard drive instead of the flash drive. My system is still running but I'm pretty sure I hosed it and it's not going to boot again if I restart. When I run cfdisk on my boot drive it says "FATAL ERROR: Cannot open disk drive". When I run cfdisk without a drive specification it says "FATAL ERROR: Bad primary partition 2: Partition ends in the final partial cylinder". I think this problem is probably not specific to OpenSUSE but I figured this is as good a place to start as any.
View 4 Replies View RelatedI want to install Ubuntu 10.04 on a second HDD than my windows xp installation. The second drive is on the same ide ribbon as the primary HDD (xp) and is set to slave. When i installed ubuntu on the second HDD it corrupted my primary drives MBR. It was an easy fix but every attempt i make ends in the same result. I also have another HDD that is sata and the sata controller is a via pci expansion card. Installation of ubuntu to this drive as well also corrupts my primary HDD MBR. But when I install to the same HDD the dual boot works fine.
I was thinking of unplugging the power cable from the primary HDD, then installing ubuntu to one of the separate HDDs. Would i still be able to dual boot. And which drive would be optimal for a dual boot installation in this configuration.
Should I first partition my HDD using partitioning software (Gparted ETC.)? I have Win7 as my primary but I just want some sort of linux OS on my laptop. I only want to give it 30GB, and I checked the partitioning helper that ubuntu 10.10 has on its installer and quite frankly, it sucks.
View 1 Replies View RelatedI'm having some issues upgrading my F9 to F12 using 'preupgrade' so I'm looking for anybody who has ever been able to complete a preupgrade from F9 x86_64 to F12. The error message I receive is TypeError: Parsing primary.xml error: attributes construct error. To my knowledge this has been reported as a bug in F10 which was resolved by a yum update to version 3.2.24.
For F9 the latest yum version is 3.2.21 which has this Parsing error bug that prevents the preupgarde to continue. Interesting enough that the preupgarde lets me select Fedora 12 and progresses with all the preupgrade steps properly until the parsing error occur. How to fix this Parsing error on a F9 x86_64 system.
I was unsatisfied with the 40second boot time of lucid and was searching for a solution for a while but didn't find anything yet. But today I found a way to boot 10seconds quicker.Lucid is installed here as suggested by the installer:
Primary rootpartition (/dev/sda1)
Logical partition (/dev/sda4)
swap (/dev/sda5)
[code]....
A bad install of linux gave me a grub that won't go away. My only hope of restoring my Windows XP and retrieving the data that was backed up (most wasn't) is to somehow access the recovery partition. That's still there. The primary partition was wiped out. This is a remanufactured system: I -don't- have a Windows CD. I -don't- have fdisk. I -don't- have any of the utility disks I'd normally use (they're 300 miles away, buried in snow and ice right now).
I do have a disk and a thumb drive with the Windows boot files on it, but grub doesn't recognize these. If I could just get rid of that grub file, I think I could boot from either the thumb drive or the cd, or even the partition with the recovery files on it, but I can't get rid of grub. I think even if I could get fdisk on either a cd or thumb drive, grub would override it. Any one know how to kill that file WITHOUT fdisk and WITHOUT the Windows CD? I have live Linux disks, Ubuntu 8.10 and 10.10 have been the most promising, but still can't do this.
When I run lilo (/sbin/lilo), it messes up my /boot partition. Next time I try to mount it after running lilo, I get an error: "mount: Stale NFS file handle" (I define -t ext2). My /boot partition is ext2, mounted locally, and not nfs. Then I do fsck /dev/sda1, and I get several: Free blocks count wrong for group #0 (7665, counted=5063). Fix<y>? I say yes to all and it works normally afterwards. This happens only after I run lilo. Lilo is installed in MBR.
Here is relevant configuration:
Code:
root@darwin:/home/cabrilo# cat /etc/lilo.conf
append=" vt.default_utf8=0"
boot = /dev/sda
bitmap = /boot/slack.bmp
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
prompt
timeout = 30
change-rules
reset
vga = normal
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
read-only
This is my partition table:
Code:
root@darwin:/home/cabrilo# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x8f800200
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 144 1052257+ 82 Linux swap
/dev/sda3 145 3432 26410860 83 Linux
/dev/sda4 3433 19457 128720812+ 83 Linux
And this is my fstab:
Code:
root@darwin:/home/cabrilo# cat /etc/fstab
/dev/sda2 swap swap defaults 0 0
/dev/sda3 / ext4 defaults 1 1
/dev/sda1 /boot ext2 defaults 1 2
/dev/sda4 /home ext4 defaults 1 2
#/dev/cdrom /mnt/cdrom auto noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
tmpfs /dev/shm tmpfs defaults 0 0
On a certain computer, I had four primary partitions. The person who installed the Windows 7 on the computer made two partitions for the Windows (sda1 and sda2). Then I made another two primary partitions (sda3 and sda4). sda3 was empty. sda4 is an extended partition that contained the /swap, and /.According to someone else, some viruses get in on the Windows partitions and can then get over to the Linux partitions if they are primary and right after the Windows partitions, or something like that. This person suggested that I create sda3 when I install Linux(SLES 10), but to install Linux on sda4. Then later I can change sda3 to secondary.So I tried this, and the Linux installation went fine.
I decided to change sda3 before I load the application software onto the computer.So I put the GParted CD in, but to my surprise I realised that the harddisk was actually 1 TB, and not 500 GB as I thought. So I had extra space to the right of sda4. I wasn't quite sure what to do with sda3. I thought that perhaps it would be better to unallocate sda3, move the current sda4 to the left, and then make another primary partition on the right of sda4, or just stretch sda4 both ways.Anycase, I unallocated sda3, and just left sda4 as it was.Hm, perhaps you can anticipate the end of the story. I removed the GParted CD, and restarted the computer, but now the computer doesn't let me choose whether I want to boot into Linux or Windows. Um, it doesn't boot at all from the harddisk.
I know it's dangerous to play with partitions, but sometimes the job won't be done if you are too afraid of doing anything, and I dare say you won't learn anything either. There was nothing on sda3, so I didn't think it would have nasty after effects. There isn't any important data on this computer yet, it was two new installations of Windows and Linux. So I guess I could format the harddisk and just reinstall everything, but I would like to learn what goes on underneath the surface.
I'm setting up my laptop to dual boot (default Vista installation and Ubuntu). There's also a possibility I may add XP later as a triple boot.
My laptop came with two partitions already, the second one labelled "Recovery". I was planning on adding three partitions, one for the Ubuntu installation, one for Swap, and one for storing my files (accessible to both OSs). However, this would be five partitions (or six, if I add XP later).
I've never had to deal with this many partitions before and just learned about the maximum of four primary partitions.
Six months ago I installed Ubuntu 10.04 to my otherwise Win XP work laptop. I decided to continue to use Windows' boot loader as primary: I told the Ubuntu installer to put grub2 onto a separate partition, then used dd to copy the first 512 bytes into a file in my Windows C partition, then edited boot.ini to link to it - its a common technique that is described in many support forums and blogs. This worked fine, and continued to work until a few weeks ago. One day I chose the Ubuntu option at the Windows boot loader and got a blinking cursor at top left of screen and no grub2 menu. I was able to use SuperGrub2Disk to discover and boot from my grub2 install - so that didn't appear to be broken. I finally fixed it by dd'ing a fresh copy of the first 512 bytes of my /boot partition over to the Windows C partition. So somehow the Windows boot loader decided it no longer liked my original dd'ed file.
The only things I can think of that might have changed and caused this to happen are (on Ubuntu) an update to security packages using the graphical update manager that pops up (I rarely do a command line apt-get upgrade/dist-upgrade and certainly not in this time frame) and (on Windows) a Windows Update - as it is a work laptop I tend to take whatever essential updates it suggests. As you can see I managed to fix the problem. However does anybody have any similar experience or any explanation why this may have happened? Could an over-zealous Windows Update have caused it?
I have this old box that I used at school that I wanted to re-purpose and use. So i decided to that I wanted to run xp, ubuntu studio and slackware so I can learn about linux and do some other things with xp. I think I got through the installatiosa all fine and dandy, and I installed grub for my boot loader, I can boot into studio and xp, but I cant get into slackware. the grub boot menu is sorta funky too, it shows a generic and recovery mode for studio which is fine, and then another option for xp, some memory test boot option, but then for slackware it shows "Slackware Linux (Slackware 13.1.0) (on /dev/sda4) four times in a row. If I select any of them they all end up with some error; the third SW [slackware] option down the list of the repeated 4 allows me to sign into root, but when I type "startx" i get :
(EE) intel(0): No kernel modesetting driver detected
(EE) Screen(s) found, but none have a usable configuration
Fatal server error: no screens found
but thats with a lot of other text above that. if you need any more details, please dont hesitate to request for them. I'm going to take some time and cool down. I'm trying to get these three OSes running from one HD. I've partitioned the 80 gig drive as follows
Primary 40 G NTSF for XP
Primary 2G Linux Swap
Primary 16G Slackware
Primary 18 U Studio
Primary
I wanted to use a USB drive to boot slackware because I do not have a blank CD or DVD. So I went to [URL] first, but I couldn't get dd and syslinux to install on windows 7. So then I brought out my trusty puppy linux USB stick, and copied the file onto puppy. Then I typed in dd if=/(desktop directory)/usbboot.img of=dev/sdd1 bs=512 but when I booted my computer up with the usb stick I get the message "boot error"
View 3 Replies View Relatedafter install slackware with gnome using gnome slack build it is work fine Except some thing :-
the volume it is not work and get this error ((The volume control did not find any elements and/or devices to control. This means either that you don't have the right GStreamer plugins installed, or that you don't have a sound card configured. You can remove the volume control from the panel by right-clicking the speaker icon on the panel and selecting "Remove From Panel" from the menu.
No volume control GStreamer plugins and/or devices found.)) and the System Monitor give me this error when i want check the state of memory and processor ((There was an error executing 'gnome-system-monitor': Failed to execute child process "gnome-system-monitor" (No such file or directory)) and the memory flash not work and give me this error ((Error org.freedesktop.DBus.Error.AccessDenied.))
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 ?
pls delete this post if I should not do this as it is included in [URL]..How do I recover from the 99 error when I start my system? I can only get to my Slackware by booting into it from the Slackware DVD.I have re-run lilo but I keep getting the 99 error on start up.
View 10 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 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 just install qemu-kvm from [URL]
I run modprobe kvm and modprobe kvm-intel to load the modules, but the second command won't work.
It gives the following error -
Code:
root@mika:/home/mika# modprobe kvm-intel
FATAL: Error inserting kvm_intel (/lib/modules/2.6.33.4/kernel/arch/x86/kvm/kvm-intel.ko): Operation not supported