ConectivaThis forum is for the discussion of Conectiva Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a two disk system. The first (60GB) has XP installed and 12GB free space, which I thought would be OK for trying Conectiva 10 beta1. The other (120GB) has a couple of versions of Knoppix installed, and lots of free space.
The 10 beta1 interactive installation starts OK, I select English, Norwegian keyboard, etc, and eventually reach the partition section.. Conectiva will not accept/use my 12GB free space!
My question is, should I partition the 12GB first, or should Conectiva handle it? If I must partition first, is it enough to make one ext3 partition and a linux swap partition?
When you say, "12GB free space", do you mean that the 60GB drive consists of a 48GB partition and has either 12GB unpartitioned space, or an "extra" 12GB partition that you intend to reformat to a Linux filesystem (which is what you want), or that the drive has one 60 GB partition of which only 48GB is actually used (which is not helpful in this situation)?
I doubt that Connectiva can resize an NTFS partition (the native filesystem of Windows XP) for you (very few Linux distributions can do this). So you need to make the so-called "free space" into real free space yourself. This is best anyway, if you intend to resize a Windows partition, as that way you can defrag it first.
Ultimately what you want to do is resize the 60GB partition that I suspect you have, into a 48GB partition and leave the 12GB of unpartitioned space after it. You may be able to do this via Windows itself (Administrative Tools=>Computer Management=>Disk Management), and can definitely do it via third party tools such as Partition Magic or any other partitioning program you may have.
Then when you restart the Connectiva install, it will recognize that free space and do its thing.
Originally posted by motub When you say, "12GB free space", do you mean that the 60GB drive consists of a 48GB partition and has either 12GB unpartitioned space, or an "extra" 12GB partition that you intend to reformat to a Linux filesystem (which is what you want), or that the drive has one 60 GB partition of which only 48GB is actually used (which is not helpful in this situation)?
I doubt that Connectiva can resize an NTFS partition (the native filesystem of Windows XP) for you (very few Linux distributions can do this). So you need to make the so-called "free space" into real free space yourself. This is best anyway, if you intend to resize a Windows partition, as that way you can defrag it first.
Ultimately what you want to do is resize the 60GB partition that I suspect you have, into a 48GB partition and leave the 12GB of unpartitioned space after it. You may be able to do this via Windows itself (Administrative Tools=>Computer Management=>Disk Management), and can definitely do it via third party tools such as Partition Magic or any other partitioning program you may have.
Then when you restart the Connectiva install, it will recognize that free space and do its thing.
Hope this helps.
Thanks for your reply.. I tried the 12GB as pure free space, and as ext3 partitioned, both without luck. Once I got to the partitioning section of the install process, pointed at hda7 as the partition to use, I got a message "you must create a boot partition first". After some head scratching and looking at the various options in front of me I tried the Edit button, selected / and away it went.
I was able to complete a most impressive installation process. Made my boot floppy (luckily, as my XP boot manager - OS Selector - didn't find Conectiva), and in a very optimistic mood rebooted...
I wish I could say I was sitting here enjoying what I know is going to be a great experience, but reboot took me quickly to "Kernel panic: VFS: unable to mount root fs on hda7".
Should I have chosen /boot instead of / in the partition Edit section above? If you have any ideas I will happily try them..
It would seem that Connectiva's installer does not have the facility to automatically make the necessary partitions for you like some others. Normally, saying "use this space" would enable the installer to repartition the space as necessary-- otherwise you are taken to a partition tool such as fdisk or cfdisk to do the partitioning yourself. In that case, it's possible that you have not used that tool correctly, or at all.
What I also find odd is that the distro seems to require a separate boot partition-- most cases I've seen, if you don't make one the /boot folder will be put in the / (root) tree and that is not a problem.
So annoying as this is, I'm going to suggest that you repartition the 12GB into 3 partitions, by whatever means:
10 or 15MB partition to use for /boot (formatted as linux (ext2), filetype 83)
512MB partition to use for /swap (formatted as linux swap, filetype 82)
the rest for the / partition (formatted as linux (ext2), filetype 83)
Then run the install again, selecting each of the partitions to be mounted and initialized for the appropriate function/mount point.
It is also possible that your bootloader is improperly configured, but fixing that is even more complex than just reformatting and starting over, since you haven't got anything on the Connectiva system anyway.
It it would help, here are a couple of links discussing partitioning issues under Linux:
If you're not using the RAID controller, perhaps you could disable it in the BIOS. No point in making the kernel search for modules for unused hardware, and RAID support may not be compiled into your kernel in the first place, which would be one explanation of why it hangs.
Originally posted by motub If you're not using the RAID controller, perhaps you could disable it in the BIOS. No point in making the kernel search for modules for unused hardware, and RAID support may not be compiled into your kernel in the first place, which would be one explanation of why it hangs.
I wish I could do more, but RAID on my Asus P4PE board IS disabled in the BIOS - Linux installers all seem to check for RAID devices regardless.
btw I do have a syslog from the above troubles, which I found in the MI folder, in case anyone at Conectiva is interested in looking at it?
I believe its early days yet ref sorting out new kernel problems. Another 2.6 distro I tried today, loaded OK, but had numerous errors when trying to use various apps.
Hopefully Knoppix 3.4 will have sorted most of them out when its released in the near future :-)
keep me in touch, knoppix 3.4 doing same thing...gotta be ludicrous that this is to blame, the /boot and root thing...nahh
installer basically same for 3.3 which ive installed over and over. Are you using 2.6 kernel; if you are, then indeed we have the same issue. Even tried overclockix 3.4...same thing...something not there for 2.6
then tried to boot into old kernel, linuxOLD...same thing...that's 2.4.X kernel...anyway keep me in touch for i need to understand why me from scratch debian system at 2.6 gives both my ethernets the same irq...screws up networking and gives me that spurious 8259 irq message
my 2.4.18 doesnt do that nor knoppix 3.3 or 3.4 in live cd...mmmm.
Well, this time I did manage to install Beta2 OK, a couple of snags though..
First, although my isdn (HFC-PCI) card is seen OK ref /proc/pci - isdn is not loaded when booting.
Could this be because I selected 'No Network' during installation, thinking this referred to local network rather than Internet?
Would I need to do a complete new install to add Network or is it possible to do it more simply?
Another thing I have never seen before - when I looked at /proc/pci my isdn card has a 3-digit IRQ, rather than the usual IRQ9... is this normal with the 2.6 kernel??
Otherwise, I blew the MRB, and am writing this with the aid of Knoppix, so its back to solving that this Easter! :-)
Hopefully someone can give me an answer to the above..
My irq mistake was not configuring isa and simply checking the isa pnp in my kernel configuration. Stuff works now without dropping ethernet and other stuff. Tried lspci -v and noticed there was and isa bridge on board...believe to control or allow interrupt assignment. Whew!
Still no luck with knoppix3.4 or overclockix 3.4, dont care...debian's up w/ apt-get. A lil buggy with Sid here and there but have been able to track all problems down with exception of kde3.2 not adding debian menu items, and update-menus has no effect.
What's an MRB? Not familiar with Conn...
Anyway if you mean the mbr, use knoppix (havent myself) to replace the loader. I use straight debian woody r1 to do it when i replace partitions with ghosted images. All my OS's including multiple windows xp are added to their own partitions with their respective nt loader or lilo in the /root partition. It much easier to fix. Also bootmagic handles the grand loading though not necessary once you get the loader down.
At this point doing more than experimenting and have progressed to get rid of it, but as long as windows around, much easier to make changes too. Only use the lilo stuff and grub for boot splashing and letting me select different kernels (have a dockable laptop whose station has scsi). Anyway I know this doesnt help, but it lets me keep seeing this thread if something neat or informative comes around.
Right, I meant mbr.. have just this instant used mbrwiz to restore mbr.dat from 14th March on my XP disk. That found a hidden copy of OS Selector and got XP back on the air, phew!! Booting SuSE on the same disk is next on the list.
Grub gives error 17 but the info looks right to me. I do want SuSE back on the air, I spent 4 hours or more upgrading to KDE 3.2 yesterday evening, and it handles ISDN very well. Will probably make it my #1 Linux distro when 9.1 comes out...
In the mean time I hope to get an answer on installing network/isdn on Conectiva from someone, and hear if anyone knows the answer to the 3-digit IRQ question.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.