jo / ak <[EMAIL PROTECTED]> writes:
> it shows hda/hda1, no hdc
Hm. That means the driver did load.
> You were right, there is an error earlier, in PIIX4.
Just a warning, I think.
> loading ide-generic
[snip]
> ide 0 at 0x1f0-0x1f7, 0x3f6 on irq 14
> ide 1 at 0x170-0x177, 0x376 on irq 15
H
Zitat von "Patrick J. LoPresti" <[EMAIL PROTECTED]>:
> Does "ls /sys/block" show any hdX directories?
it shows hda/hda1, no hdc
You were right, there is an error earlier, in PIIX4. But I don't
understand what's going on:
loading ide-generic
[...]
ide: Assuming 33MHz system bus speed for PIO mode
jo / ak <[EMAIL PROTECTED]> writes:
> Now I get another error later on:
>
> Bios EDD Facility v0.16 2004-Jun-25, 1 devices found
> ..done loading edd
> *** ...and locate the boot device
> *** find-boot-device failed
> *** Dropping to shell
>
> # with 1 Maxtor 2B020H1 IDE HD and 1 CD-Drive
This
It works great - the "illegal instruction" is gone! Thank you
very much!!
Now I get another error later on:
Bios EDD Facility v0.16 2004-Jun-25, 1 devices found
..done loading edd
*** ...and locate the boot device
*** find-boot-device failed
*** Dropping to shell
# with 1 Maxtor 2B020H1 IDE HD a
On Sun, Aug 29, 2004 at 09:50:46AM -0400, Patrick J. LoPresti wrote:
> Wim Vandersmissen <[EMAIL PROTECTED]> writes:
>
> > I think the problem lays with the fact that bash is compiled for
> > i686 and you're using an AMD box.
>
> Ah, good thinking, Wim! I would have missed it.
>
> It is not jus
The new image also gets an "illegal instruction". Maybe the
reason is elsewhere? (the CPU is a Intel Pentium-S 200 Mhz)
Regards, Jo
Zitat von Wim Vandersmissen <[EMAIL PROTECTED]>:
> Ok, try again, another image is ready.
> I think the problem lays with the fact that bash is compiled
> for i686
hm...I tried the new ISO-Image and it still doesn't work (same errors). :-(
thanks
trust
--
Supergünstige DSL-Tarife + WLAN-Router für 0,- EUR*
Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl
---
This SF.Net email is sponsored
On Sun, Aug 29, 2004 at 09:50:46AM -0400, Patrick J. LoPresti wrote:
> Wim Vandersmissen <[EMAIL PROTECTED]> writes:
>
> > I think the problem lays with the fact that bash is compiled for
> > i686 and you're using an AMD box.
>
> Ah, good thinking, Wim! I would have missed it.
>
> It is not jus
Wim Vandersmissen <[EMAIL PROTECTED]> writes:
> I think the problem lays with the fact that bash is compiled for
> i686 and you're using an AMD box.
Ah, good thinking, Wim! I would have missed it.
It is not just bash, though. *Everything* has to be compiled for the
right CPU architecture, incl
Ok, try again, another image is ready.
I think the problem lays with the fact that bash is compiled for i686 and
you're using an AMD box.
The bash in the new iso I just put up is compiled for i386, which should give
no problems.
Could you try again? (http://bofh.be/unattended/linuxboot.iso)
--Wi
Unfortunately, it doesn't work either (same messages) - so the
question is open again.
Thanks, Jo
Zitat von Wim Vandersmissen <[EMAIL PROTECTED]>:
> Could you try this bootdisk on
> http://bofh.be/unattended/linuxboot.iso
> and let me know if you also get the illegal instruction
I have the same problem with two different PCs (both
comparatively old, with Asus P/I P55T2P4 and Asus TXP4
Mainboards). Version is 4.4b.
For me, the sequence is:
..
WELCOME!
Illegal Instruction!
Illegal Instruction!
Illegal Instruction!
Illegal Instruction!
Hm, may be we are on a serial console.
12 matches
Mail list logo