LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-16-2009, 09:25 PM   #1
silverdrgn
Member
 
Registered: Mar 2005
Location: Texas
Distribution: slackware, slackware
Posts: 41

Rep: Reputation: 15
Dual Boot Slackware 12.2 and XP64 Trying to do it right having problems


Hello all, old Newb back here again trying to get slackware running on my system. So far this is what I have done.

1)= Formatted System new install of XP-64. Windows is now setup and running.

2)= Put in slackware 12.2 cd1,# fdisk -l to see my drives
All drives there check.

Using a lone drive to install slack, not the first sata drive /dev/sda. It is the second sata drive installed on my machine so I type in:
/dev/sdb "enter"

Get my first error.
"The number of cylinders for this disk is set to 30515. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1)old versions of LILO 2) booting and partitioning software from other OSs"

I would very much like to get past this and need to know if I should just continue or try to do something to my drive to make this error go away. Any and all help is appreciated. I have tried to read on it some but I am comingup empty. Seen one guy not mention the error and continue but he was doing a server setup. my machine is just gonna me a desktop/workstation setup. lots of big files will be on it.
 
Old 08-16-2009, 09:34 PM   #2
Uncle_Theodore
Member
 
Registered: Dec 2007
Location: Charleston WV, USA
Distribution: Slackware 12.2, Arch Linux Amd64
Posts: 896

Rep: Reputation: 60
You should just continue with install. Not that this message means nothing, but in your particular setup it's irrelevant with 99% probability...
 
Old 08-16-2009, 09:39 PM   #3
silverdrgn
Member
 
Registered: Mar 2005
Location: Texas
Distribution: slackware, slackware
Posts: 41

Original Poster
Rep: Reputation: 15
Thanks Uncle. I will continue and edit this post to show how goes it for others that may need to see.

Updated below on post #7

Last edited by silverdrgn; 08-16-2009 at 10:39 PM. Reason: update
 
Old 08-16-2009, 10:09 PM   #4
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,541
Blog Entries: 23

Rep: Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943
Hi,

Welcome back to LQ & Slackware!

Quote:
excerpt from 'man fdisk';

On Intel compatible hardware, the BIOS that boots the system can often only access the first 1024 cylinders of the disk. For this reason people with large disks often create a third partition, just a few MB large, typically mounted on /boot, to store the kernel image and a few auxiliary files needed at boot time, so as to make sure that this stuff is accessible to the BIOS. There may be reasons of security, ease of administration and backup, or testing, to use more than the minimum number of partitions.
As indicated by your 'fdisk /dev/sdb' it would be a potential problem. You can just ignore this as GNU/Linux won't have these restrictions. If you want then a '/boot' partition of sufficient size could be used but for other reasons. One if you ever plan on using 'GRUB2' then a '/boot' will have to be provided with it's own partition. The standard install of the Slackware will not need the '/boot' as a separate partition. But some people have reasons for a partition for '/boot'.
 
Old 08-16-2009, 10:16 PM   #5
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Honestly, I did not know that XP was available in 64 bit not that it matters to me: just a curiousity.. Interesting.

Sasha
 
Old 08-16-2009, 10:22 PM   #6
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 12,541
Blog Entries: 23

Rep: Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943Reputation: 1943
Hi,

Yes, M$ WinXP64 has been available for a long time, around 05. I've got both versions of it but just for client support. I try to steer people away from it but some people just can't see beyond M$ spin.
 
Old 08-16-2009, 10:29 PM   #7
silverdrgn
Member
 
Registered: Mar 2005
Location: Texas
Distribution: slackware, slackware
Posts: 41

Original Poster
Rep: Reputation: 15
Thanks onebuck, I cam across that exact statement in a "how to" linked on another thread. SO far that explanation covers it well. The "how to" is only for a simple plain install but I think it will get me to where I need to go.

Grapefruitgirl, lol yeah XP does have a 64 bit version. Pretty much the same as regular xp with some 64 bit support not super impressive.

In the selection process of my install. had one bump. Cd-rom was not detected on "source" option so system could not see the drive where the disk was so rebooted and used the "huge.s" kernel instead, saw it no problem. now at selection option. Just a lil question should I go ahead and install all options? it says if you have the space to go for it and I do but will this slow down the system at all?

Spoke too soon:

I choose to install all the options at the "selection" section since I have the space available and I get a menu prompt that states " Cannot install software yet" it tells me to:

"1. select your media source" I thought I did
"2. Set up your target Linux partition(s)." thought I did that too
"3. Select which software categories to install." I just did that... the mystery continues...

will try to reboot and start at selection screen.

Last edited by silverdrgn; 08-16-2009 at 10:38 PM. Reason: update
 
Old 08-16-2009, 10:35 PM   #8
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Installing the full meal deal will not slow down the system at all. Just use what you like, or don't use what you don't like.
And either way, you can later remove stuff easily if you find the HDD or whatever to be crowded

Sasha
 
Old 08-16-2009, 10:53 PM   #9
silverdrgn
Member
 
Registered: Mar 2005
Location: Texas
Distribution: slackware, slackware
Posts: 41

Original Poster
Rep: Reputation: 15
Thanks Grapefruitgirl. I will do the whole meal deal thing. BTW what filesystem did you choose? I went with reiserFS but then I think I will go back and setup with ext2 the default. I am not sure if going with ext2 is best. I will have lots of small files but also lots of big ones. hmm... at a crossroads i guess. What did you do?
 
Old 08-16-2009, 10:57 PM   #10
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Prior to my switching to Slack64-current, I've always used Ext2 and have no complaints about it. Ext2 is well tested and very stable. It's been about 3yrs now for me with Ext2.

Plus, Ext2 can be upgraded (there are conditions, but not major ones) to Ext3 (and maybe even Ext4) if you like, later on (it adds journaling for files/inodes created after the upgrade).

Currently (with Slack64 -current) I'm using Ext4.

I've never run Slack 12.x as I went from 11 to 64-current, but this shouldn't matter for the sake of this discussion.

For the record, I have zero experience with ReiserFS.

Sasha
 
Old 08-16-2009, 11:00 PM   #11
silverdrgn
Member
 
Registered: Mar 2005
Location: Texas
Distribution: slackware, slackware
Posts: 41

Original Poster
Rep: Reputation: 15
good deal, ext 2 it is. I was thinking of doing slack 64. I have a quad core system on the machine i'm trying to put Slack 12.2 on. I had contemplated slack 64 but just went ahead with the 12.2. What was your primary reason for slack 64 if you dont mind me asking?

Went back and deleted all the stuff I had done previously. Redid everything the same way, except this time it saw cd rom for install, I used filesystem ext2 for my partitions and viola in process of doing install now. Choose to do the full install, only 4.8 GB accordingto prompt.

Last edited by silverdrgn; 08-16-2009 at 11:15 PM. Reason: update
 
Old 08-16-2009, 11:14 PM   #12
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by silverdrgn View Post
good deal, ext 2 it is. I was thinking of doing slack 64. I have a quad core system on the machine i'm trying to put Slack 12.2 on. I had contemplated slack 64 but just went ahead with the 12.2. What was your primary reason for slack 64 if you dont mind me asking?
Nope, I don't mind at all!

Basically, I've got a 64bit machine (currently a Core2 CPU in it but it'll take a 4-core too-- maybe one day ) and have always been running 32bit OS on it (Slack 11).

I have for a while wanted to use (or be *able* to use if need be) the full potential of the machine, and had been pondering what 64 bit OS to consider for this purpose.

I did try BlueWhite64 way back (version 12.1 IIRC) because it was basically a clone of Slackware, but in 64 bit, but wasn't happy with it. It wasn't Slackware!

I only switched to Linux for the first time just under 3 yrs ago, but very near the beginning I became a die-hard Slacker and remain so.

So, when finally/suddenly/by-surprise Slack64-current was released for testing, I was delighted and here I am!

Sasha
 
Old 08-16-2009, 11:20 PM   #13
silverdrgn
Member
 
Registered: Mar 2005
Location: Texas
Distribution: slackware, slackware
Posts: 41

Original Poster
Rep: Reputation: 15
Awesome, I started slack about 5 yrs ago but only had it running very shortly. A friend helped me install it and he was die-hard linux fan. We set it up worked flawlessly but the windows xp I was runing started messing up. He had moved away and I am not saavy enough to do it on my own so I formatted all drive lost slack and was not able to get a good running install ever again. I just recently reformatted windows again and decided that no matter what i am gonna get it back running strong and fast. hell that processor was a 900 Mhz and it was screaming. I can imagine what the q6600 will do with it. lol, glad to have you here grapefruitgirl, your really helpin me out alot by giving me your insight and suggestions, it is exactly what I need to get me through this install.
 
Old 08-16-2009, 11:22 PM   #14
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
PS - if you're new to Slack, then something stable like 12.x is a very good place to start. -Current is not generally recommended for new Slackers, as it may have weird bugs and/or changes on a daily basis, until the official release (Slack 13) is released.

At that point, maybe you'll consider switching to 64.

NOTE: If I remember right, according to the latest ChangeLog and/or Changes&Hints file(s) with Slack-current, upgrading from Slack32 to Slack64 is not supported/recommended, so it'd be a fresh install for you. Not a big deal really, especially if you have a separate /home partition (though unless you changed filesystems, even the /home folder would remain intact even if you installed right on top of the existing OS, but a lot of configuration stuff, like KDE especially, would probably be borky; so best to install fresh if going from 32 to 64...)

Sasha

Last edited by GrapefruiTgirl; 08-16-2009 at 11:25 PM.
 
Old 08-16-2009, 11:37 PM   #15
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Much as I'd like to stay and chat, it's half past midnight here, so I'll leave you with a tip, in case you get to this state next:

Slackware will boot up to the console when freshly installed. This means no Desktop will appear. Also, you'll have no user account except root. So you'll want to do a couple things:

1-- Create yourself a user account (try the man pages for the `adduser` or `useradd` command for instructions if you do this via console). I usually cheat, by starting X as root the first time, and using Kuser to make my user account, then log out from root, reboot or start X the proper way and log in as your new user.

2-- As mentioned, it will boot to the console. To make Slack boot to the Desktop (the GUI login actually) you need to edit the file /etc/inittab. There's a line reading something like:

id:3:initdefault:

where you will need to change the 3 to a 4 to get the GUI login.

What I do is comment out the whole line; this makes INIT ask during boot which run level you would like. 4=GUI Login, 3=non-GUI-Login, and 1=single user (maintenance mode). Read the file for full details. I like it to ask me, because if I want to for example install my nVidia driver, I need Level 3, and it's faster/easier to press '3' and 'Enter' during boot, than it is to boot to the GUI Login, kill X, and switch to init 3 and log in again.

Anyhow, best of success with your install. I'll be sure to check in on this thread tomorrow and see what's up; but rest assured, there are LOTS of experienced & helpful Slackers here on LQ who will be happy to help you in my absence, no question.

Cheers!
Sasha
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Monitor problems with dual boot slackware and winxp Kelean Slackware 6 10-06-2007 07:42 PM
Triple Boot with XP and XP64 dms05 Linux - Newbie 2 05-18-2006 08:43 AM
Slackware 10.2 + XP Dual Boot Problems dave`2005 Slackware 12 03-31-2006 06:52 PM
Link - Problems in dual boot between SuSe and Slackware stevesk SUSE / openSUSE 0 12-08-2004 09:31 PM


All times are GMT -5. The time now is 11:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration