Re: Yoper? Any difference?
From: David Wright (david_c_wright_at_hotmail.com)
Date: 10/07/04
- Next message: Whitey Johnson: "Re: Monitor Icon Gone"
- Previous message: BearItAll: "Re: Suse 9.0 and DSL"
- In reply to: BearItAll: "Re: Yoper? Any difference?"
- Next in thread: BearItAll: "Re: Yoper? Any difference?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 07 Oct 2004 16:43:22 +0200
(sorry for tabulated lines from df -a and fstab which are longer than 80
chars.)
BearItAll wrote:
>>>
>>
>> 2.1 won't boot here :-(
>>
>> When it reboots after the install, I get a grub prompt, but it won't
>> boot, tells me I need to load a kernel first, but as I have no idea what
>> the kernel is called or where it is, it leaves me a little stumped...
>> After the graphical front end to grub under SuSE where I select SuSE or
>> Windows to boot and that's it, Yoper looks very primitive in comparison.
>> I re-installed and said to install Lilo instead, but on re-boot it still
>> goes into the grub command line!
>
> This problem is just to do with the location of /boot
>
> When you come to the part of the install for disc partitioning, ensure
> that you put /boot first, it doesn't need to be very large, see the table
> for this portable PC below.
>
> A typical partition table might look like this,
>
> /dev/hda1 201M 38M 163M 19% /boot
> /dev/hda2 301M 177M 124M 59% /
> /dev/hda9 4.4G 199M 4.2G 5% /home
> /dev/hda7 801M 557M 244M 70% /opt
> /dev/hda8 101M 33M 68M 33% /tmp
> /dev/hda5 3.1G 1021M 2.1G 34% /usr
> /dev/hda6 401M 99M 302M 25% /var
> /swap is 350MB
>
> Notice that I have put /boot on hda. You can also see that I have left
> quite a lot of space in /boot, this is so that I can upgrade to new boot
> images without losing my older ones (just in case they don't work). Also
> note that Suse makes more use of the /opt than most distros, though it is
> unlikely to grow very much once you have your main packages installed.
>
> I know what you are thinking 'Why didn't Suse do that for me' and this is
> where it gets a bit tricky.
>
> What Suse loader is not very good at is deleting partitons that it
> believes are owned by MS, in particular the hidden partition that is
> normally the recovery area. Some new hard drives already come with that
> partition in place, I had to use a Redhat rescue disk to get the tools to
> delete it on my main PC because until Suse can mount it's own volumes you
> can not get access to the tools to manually delete it (chicken and egg).
SuSE was on the machine before I just replaced the SuSE partition with
Yoper. The configuration, which was (and is again) running fine with SuSE
is:
/dev/hda1 1GB Swap
/dev/hda2 55GB NTFS C:
/dev/hda3 55GB ext3 /
Under this scheme with SuSE, I get a graphical Grub which automatically
configures for loading SuSE, Windows or SuSE Recovery. Installing Yoper, it
asks for 2 (3) partitions, swap and root (and optionally home).
> So, first you should try the install as normal, but at the drive partition
> select for manual set up. Go for a setup similar to the above. I also
> suggest minimum graphical install, for the sake of speed while you ensure
> this solves your problem.
Yoper only provides a manual set-up.
> If this works then you could go back and do a fuller install, or just use
> the package manager to install the extras.
>
> If it doesn't work, then I bet you my socks that /boot is still too high,
> which means that something is in the way (as I mentioned above). However,
> your system may still be able to chain boot via the install disc. It gives
> the option of booting the installed system.
OK, I'll look at that. But Yoper doesn't give an option to register a /boot
partition...
> Now you have the chance to delete that rogue partition.
>
> I'm wary of telling you how because I don't want you accidentally deleting
> a partition that might be needed in a dual boot situation.
There isn't a rogue partition to delete ;-)
> Instead I would suggest that you post the results of this command
>
> df -a
OK, SuSE is re-installed on the test machine, and Grub works normally again.
It is something about the Yoper install which messed up Grub, SuSE
automatically re-wrote the correct entries upon re-installing...
Dateisystem 1K-Blöcke Benutzt Verfügbar Ben% Eingehängt auf
/dev/hda3 53301984 4122232 49179752 8% /
tmpfs 518320 12 518308 1% /dev/shm
/dev/hda2 62918572 10890184 52028388 18% /windows/C
(OK, abbreviated, have removed proc, usbfs and hdc and hdd.)
> Also
>
> more /etc/fstab
/dev/hda3 / reiserfs acl,user_xattr 1 1
/dev/hda2 /windows/C ntfs ro,users,gid=users,umask=ßß ß2,nls=utf8 0 0
/dev/hda1 swap swap pri=42 0 0
(Again, non hda entries removed for brevity.)
> Just so that we can see the rogue partition to advise you better.
>
> If you have access to one of the disk partitioning programs for windows
> they are very good these days, including the ability to section off and
> prepare partitions for your linux. I haven't used one of those myself so
> can't really say which one.
>
>
As I say, this configuration works fine under SuSE (is the default scheme it
comes up with), but Yoper won't get past the GRUB> boot prompt...
Dave
- Next message: Whitey Johnson: "Re: Monitor Icon Gone"
- Previous message: BearItAll: "Re: Suse 9.0 and DSL"
- In reply to: BearItAll: "Re: Yoper? Any difference?"
- Next in thread: BearItAll: "Re: Yoper? Any difference?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
