3.1.6 and 3.1.7 CDs and real hardware

[Evgeniy Ivanov]

Hello,

I have a problem with r6084 or r6433 or r6438 CDs. Or my old PC
(i845e-max, ATA hard drive) used for Minix I can't boot (but >= 3.1.6
worked fine, when I just updated from some revision of 3.1.5). The
only thing I see is blinking cursor at the left top of display. On my
laptop booting is toooooo looong, but it's ok in VMWare.

What can I do? I need to install 3.1.6 or later, so I can update to
trunk. I tried to update from few 3.1.5 revisions, but I can't build
trunk (need to update some utilities before and too many commits
between).

--
Evgeniy Ivanov

[Roman Ignatov]

Hi,

I have the same problem.
I wrote about it: http://groups.google.com/group/minix3/browse_thread/thread/5ed4a97addc6cc3a

Have you 2 cards Ethernet?

[Evgeniy Ivanov]

On Fri, Mar 19, 2010 at 8:37 AM, Roman Ignatov <ign...@minix3.ru> wrote:
> Hi,
>
> I have the same problem.
> I wrote about it: http://groups.google.com/group/minix3/browse_thread/thread/5ed4a97addc6cc3a

I thought you have problem during booting and not with bootloder, like
me (I don't get any prompt, thus probably bootloader is not loaded at
all).

> Have you 2 cards Ethernet?
>

No, just one (rtl8139).

--
Evgeniy Ivanov

[Alexander A. Gorodnev]

Hello, i have the same problem on two computers. All what i see is a
blank screen and blinking cursor.

lspci no.1:

00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory
Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ
Integrated Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High
Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 2 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB
UHCI Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2
EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC
Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE
Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family)
SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 SCSI storage controller: DTC Technology Corp. Domex 536
01:01.0 Ethernet controller: Hewlett-Packard Company J2585B HP
10/100VG PCI LAN Adapter
02:00.0 Ethernet controller: Attansic Technology Corp. L1 Gigabit
Ethernet Adapter (rev b0)

Yes, and i have 2 cards Ethernet.Minix version: minix_R3.1.6-r6084

Thanks.

[Evgeniy Ivanov]

I've installed 3.1.7 (r6438) on my hdd using VMWare. Boot monitor
works fine, but system fails right before "Multiuser startup is
progress" and after sometime it prints "newroot: mount failed: Invalid
argument". No serial output at all (doubt it even works, since my
Linux box doesn't get boot monitor's prompt). In VMWare it boots
normally from real disk.

--
Evgeniy Ivanov

[Gautam BT]

lspci on my comp has the same output (I seem to have the same motherboard) except for the network card (I have an onboard Intel Pro 100 VE card and a realtex 8139 based pci card). So I am guessing your network cards are responsible for your problems.

--
Gautam

[Gautam BT]

This happened to me earlier. In my case I had inserted a partition after installing minix and some where during the boot the wrong partition number was being used. You can type 'set' at the boot prompt and check the value of rootdev. Setting it to the right value solved my problem.

If I remember right this also happens if you try booting minix through a non IDE disk. If this is the case, you can solve it by setting the drive configuration in your bios to emulate Legacy/IDE (or whatever it is called in your bios).

--
Gautam

[Evgeniy Ivanov]

Hello again,

I've noticed, that minicom was connected to the wrong device (sorry I
had to check it when I opened this thread). I get either this:

APIC disabled, using legacy PIC

MINIX 3.1.6. (branch-R3.1.6-r6084)
Copyright 2010, Vrije Universiteit, Amsterdam, The Netherlands
MINIX is open source software, see http://www.minix3.org
Initiating legacy i8253 timer
PCI: IRQ 4 is assigned, but device 3.5.0 does not need it
2.5.0: unknown header type 3

or this:
...
Initiating legacy i8253 timer
PCI: IRQ 4 is assigned, but device 3.5.0 does not need it
2.5.0: unknown header type 3

--
Evgeniy Ivanov

[Evgeniy Ivanov]

My lspci (doubt it's useful, but who knows):

00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset
Host Bridge (rev 11)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset
AGP Bridge (rev 11)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M)

USB2 EHCI Controller (rev 01)

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC
Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX
5200] (rev a1)
03:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
03:05.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
03:05.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
03:05.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
03:05.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)

[Antoine Leca]

Evgeniy Ivanov wrote:
> I've installed 3.1.7 (r6438) on my hdd using VMWare. Boot monitor
> works fine, but system fails right before "Multiuser startup is
> progress" and after sometime it prints "newroot: mount failed: Invalid
> argument".

FYI: you are inside the image ramdisk, executing the first /etc/rc
(source is in src/drivers/memory/ramdisk/rc); around the end...

What is the value of rootdev from the boot monitor? bin_img?
Does it match the *sub*partition where you installed Minix to (on the
virtual HDD)? Beware if partitions are not in order...

You could start another copy of Minix with that VHDD mounted (the CD
image you used to install should work); then, fsck the file system
/dev/$rootdev
If you can mount it, then sometimes very strange is hapenning...

> No serial output at all (doubt it even works, since my
> Linux box doesn't get boot monitor's prompt).

Sorry, no idea about how to set up serial devices on Linux' VMWare.
Should be a googable topic, though.

Antoine

[Evgeniy Ivanov]

On Mon, Mar 22, 2010 at 7:22 PM, Antoine Leca <Antoine...@gmail.com> wrote:
> Evgeniy Ivanov wrote:
>> I've installed 3.1.7 (r6438) on my hdd using VMWare. Boot monitor
>> works fine, but system fails right before "Multiuser startup is
>> progress" and after sometime it prints "newroot: mount failed: Invalid
>> argument".
>
> FYI: you are inside the image ramdisk, executing the first /etc/rc
> (source is in src/drivers/memory/ramdisk/rc); around the end...
>
>
> What is the value of rootdev from the boot monitor? bin_img?
> Does it match the *sub*partition where you installed Minix to (on the
> virtual HDD)? Beware if partitions are not in order...
>
> You could start another copy of Minix with that VHDD mounted (the CD
> image you used to install should work); then, fsck the file system
> /dev/$rootdev
> If you can mount it, then sometimes very strange is hapenning...

All these things are fine. Sorry didn't make clear, that after
installing Minix on hdd using VMWare I tried to boot on real hardware.
In VMWare same installation works fine.

>
>> No serial output at all (doubt it even works, since my
>> Linux box doesn't get boot monitor's prompt).
>
> Sorry, no idea about how to set up serial devices on Linux' VMWare.
> Should be a googable topic, though.

I didn't even try it :) Now I have output from real hardware, it's in
my previous message.

--
Evgeniy Ivanov

[Antoine Leca]

Evgeniy Ivanov wrote:

> On Mon, Mar 22, 2010 at 7:22 PM, Antoine Leca wrote:
>> Evgeniy Ivanov wrote:
>>> I've installed 3.1.7 (r6438) on my hdd using VMWare. Boot monitor
>>> works fine, but system fails right before "Multiuser startup is
>>> progress" and after sometime it prints "newroot: mount failed: Invalid
>>> argument".
>> FYI: you are inside the image ramdisk, executing the first /etc/rc
>> (source is in src/drivers/memory/ramdisk/rc); around the end...
>

> All these things are fine. Sorry didn't make clear, that after
> installing Minix on hdd using VMWare I tried to boot on real hardware.
> In VMWare same installation works fine.

Sorry I do not understand: I got that with the same (real) HDD, one of
VMWare and bare-hardware is working and the other doesn't. Correct?

Something I made working earlier, and which may be useful, is to insert
intr sh
[ it is the real effect of "single-user mode booting", boot -s ]
in the middle of the src/drivers/memory/ramdisk/rc script: this gave me
a prompt while being still with /dev/imgrd as only fs; of course, since
very few commands are on the memory/ramdisk, not much can be done; but
if you add an /usr directory to src/drivers/memory/ramdisk/proto and
also put mount in /bin, now you could mount a known-working /usr...
I guess this should give you more ideas.

Antoine

[Evgeniy Ivanov]

On Mon, Mar 22, 2010 at 9:16 PM, Antoine Leca <Antoine...@gmail.com> wrote:
> Evgeniy Ivanov wrote:
>> On Mon, Mar 22, 2010 at 7:22 PM, Antoine Leca wrote:
>>> Evgeniy Ivanov wrote:
>>>> I've installed 3.1.7 (r6438) on my hdd using VMWare. Boot monitor
>>>> works fine, but system fails right before "Multiuser startup is
>>>> progress" and after sometime it prints "newroot: mount failed: Invalid
>>>> argument".
>>> FYI: you are inside the image ramdisk, executing the first /etc/rc
>>> (source is in src/drivers/memory/ramdisk/rc); around the end...
>>
>> All these things are fine. Sorry didn't make clear, that after
>> installing Minix on hdd using VMWare I tried to boot on real hardware.
>> In VMWare same installation works fine.
>
> Sorry I do not understand: I got that with the same (real) HDD, one of
> VMWare and bare-hardware is working and the other doesn't. Correct?

VMWare (workstation) has an ability to install guest OS on real HDD.
Since CD didn't boot, I used VMWare to boot it and install or real
HDD, then I tried to boot newly installed Minix both from in VMWare
and real hardware. It works in VMWare, but fails on real hardware with
serial output I listed earlier. For now I will use VMWare, anyway in
some cases it's more convenient.

> Something I made working earlier, and which may be useful, is to insert
>        intr sh
> [ it is the real effect of "single-user mode booting", boot -s ]
> in the middle of the src/drivers/memory/ramdisk/rc script: this gave me
> a prompt while being still with /dev/imgrd as only fs; of course, since
> very few commands are on the memory/ramdisk, not much can be done; but
> if you add an /usr directory to src/drivers/memory/ramdisk/proto and
> also put mount in /bin, now you could mount a known-working /usr...
> I guess this should give you more ideas.

I'll try, thanks.

--
Evgeniy Ivanov