At Mon, 29 Oct 2001 21:16:50 +0100,
Thierry Laronde wrote:
My tests were made with 2.2.x... So it's not 2.4.x specific.
Really?! That's too bad!
I have neither no time to really dive in the code to see what the hell's
going on.
Ok. Any volunteers on this list?
Okuji
On Fri, Oct 26, 2001 at 03:18:27PM -0700, [EMAIL PROTECTED] wrote:
| dman [EMAIL PROTECTED] wrote:
| ...
| | The problems I mentioned above were with: APIC/IO-APIC use along
| | with APM, and with SMP/APIC/IO-APIC and APM, on only some machines
| | (for example, disabling the APIC for main
I installed redhat 7.2, I then downloaded a generic 2.4.13 kernel from
kernel.org
I applied some patches for ext3 and win4lin. I then added the new
kernel to the grub.conf file as below. However when I select the kernel
from the grub menu, it just reboots, and gives me the menu again. I can
Im trying to install GRUB 0.9. The machine is a dual pentium II running
Linux, kernel 2.2.17 with a SCSI disk and a eepro100 network card.
I run configure and make and make install and everything is fine.
To install grub on the hard drive, I run
grub-install --root-directory=/boot/grub /dev/sda
On Tue, 30 Oct 2001, Shashi Kanbur wrote:
I run configure and make and make install and everything is fine.
To install grub on the hard drive, I run
grub-install --root-directory=/boot/grub /dev/sda
Is it a separate partition that you're installing GRUB to? If not, don't
specify the
Try installing with grub-install --root-directory=/boot /dev/sda
This will still install in /boot/boot/grub, but at least it will
actually work. The documentation suggests making /boot/grub a symlink
to /boot/boot/grub.
I hope this helped,
Matthias
Shashi Kanbur [EMAIL PROTECTED] writes:
Im
Vesa,
I was under the impression that an initrd was not required. I had
tried previously to use mkinitrd but it did not make a difference. Is
there anything special about using the mkinitrd, do I need to mount the
image and copy stuff to it? Or can I just run the command?
Thanks
30.10.2001 21:48:19, Justin Gaither [EMAIL PROTECTED] wrote:
Vesa,
I was under the impression that an initrd was not required. I had
tried previously to use mkinitrd but it did not make a difference. Is
there anything special about using the mkinitrd, do I need to mount the
image and
I am still unable to boot my new kernel. It appears that it is not a
grub problem though, since it behaves the same if I use lilo.
Thanks for you help! I will see if I can query the patch generator
about the failure
justin
Vesa Jääskeläinen wrote:
30.10.2001 21:48:19, Justin Gaither
On Tue, 30 Oct 2001, Robert K. wrote:
Hi!
I'd like to write a standalone program for some reason.
So I compiled a test program that pokes around in the VGA-text memory. I
used the gnu c++ compiler that is included with Redhat 7.1 and compiled
like this:
gcc -nostdlib -e main -o test
Well, that was a good suggestion nevertheless! There is no problem
if we use grub 0.90.
Thanks,
--Martin
Jason Thomas wrote on Tue, 30 Oct 2001 09:12:15 +1100
--4f28nU6agdXSinmL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Greetings,
System was as follows;
PII in an Asus P2B
Disk 1 at hda
Disk 2 at hdb
CD at hdc
Disk 3 at hdd
Installed Redhat 7.2 on /dev/hda5 and grub on the MBR of disk 1. Joy all
around.:)
System currently;
PII in an Asus
Promise Ultra33
Disk 1 at hda
CD at hdc
Disk 2 at hde
Disk 3 at hdg
The
On Tuesday, October 30 2001, pa said:
System currently;
PII in an Asus
Promise Ultra33
Disk 1 at hda
CD at hdc
Disk 2 at hde
Disk 3 at hdg
The last 2 drives hanging off of the Promise Ultra33.
No go with Grub at that point, instead of the Grub menu at boot time
just a blinking
PARA SATISFACER REQUERIMIENTOS:
1).- LOS QUE QUIEREN SABER QUIENES SOMOS:
SCHETTINO, ADRIANA CAPITAL
RUMITTI, RAFAEL V. CAPITAL
UMITTI, CARLOS A.
14 matches
Mail list logo
