[Bug 1734474] Re: Maemo does not boot on emulated N800

2020-11-09 Thread MVoloshin
It's available here: https://4pda.ru/forum/index.php?showtopic=870847 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1734474 Title: Maemo does not boot on emulated N800 Status in QEMU: New Bug d

[Qemu-devel] [Bug 1743441] Re: OS/2 Warp 4.52 OS2LVM failure

2018-12-10 Thread MVoloshin
As far as I know it has never worked. I have checked it on version 2.11 and attached a link to my disk image. I used qemu-system-i386w -cpu pentium3 -m 128 -hda c.img -boot c -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bug

[Qemu-devel] [Bug 1743337] Re: OS/2 Warp 4 HPFS corruption

2018-01-15 Thread MVoloshin
** Description changed: How to reproduce: Install OS/2 Warp 4 onto HPFS-formatted partition. After reboot there will be messages about "missing" files and OS2.INI not found. Chkdsk C: complains about FS corruption. Nothing changes even after fixing errors and next reboot. If you install OS/

[Qemu-devel] [Bug 1743337] Re: OS/2 Warp 4 HPFS corruption

2018-01-15 Thread MVoloshin
** Attachment added: "warp4_2.PNG" https://bugs.launchpad.net/qemu/+bug/1743337/+attachment/5037538/+files/warp4_2.PNG -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1743337 Title: OS/2 Warp 4 H

[Qemu-devel] [Bug 1743337] Re: OS/2 Warp 4 HPFS corruption

2018-01-15 Thread MVoloshin
** Attachment added: "warp4_3.PNG" https://bugs.launchpad.net/qemu/+bug/1743337/+attachment/5037539/+files/warp4_3.PNG -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1743337 Title: OS/2 Warp 4 H

[Qemu-devel] [Bug 1743337] Re: OS/2 Warp 4 HPFS corruption

2018-01-15 Thread MVoloshin
** Attachment added: "warp4.PNG" https://bugs.launchpad.net/qemu/+bug/1743337/+attachment/5037537/+files/warp4.PNG -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1743337 Title: OS/2 Warp 4 HPFS

[Qemu-devel] [Bug 1743441] Re: OS/2 Warp 4.52 OS2LVM failure

2018-01-15 Thread MVoloshin
** Description changed: - When I try to boot OS/2 Warp 4.51 (Merlin), 4.52 (Aurora) or eCS 1.2.5, etc. I always get an exception in OS2LVM (TRAP 000E). You can reproduce the bug using this disk image: https://drive.google.com/open?id=1zzjs9hTS0TK-Xb5hnon8SQ-2C1EmlYfy + When I try to boot OS/2 W

[Qemu-devel] [Bug 1743441] [NEW] OS/2 Warp 4.52 OS2LVM failure

2018-01-15 Thread MVoloshin
Public bug reported: When I try to boot OS/2 Warp 4.51 (Merlin), 4.52 (Aurora) or eCS 1.2.5, etc. I always get an exception in OS2LVM (TRAP 000E). You can reproduce the bug using this disk image: https://drive.google.com/open?id=1zzjs9hTS0TK-Xb5hnon8SQ-2C1EmlYfy P.S. OS/2 Warp 4.0 boots OK (if

[Qemu-devel] [Bug 1743337] [NEW] OS/2 Warp 4 HPFS corruption

2018-01-15 Thread MVoloshin
Public bug reported: How to reproduce: Install OS/2 Warp 4 onto HPFS-formatted partition. After reboot there will be messages about "missing" files and OS2.INI not found. Chkdsk C: complains about FS corruption. Nothing changes even after fixing errors and next reboot. If you install OS/2 onto

[Qemu-devel] [Bug 1743214] Re: OS/2 Warp 3 support broken in 2.11

2018-01-14 Thread MVoloshin
It looks like this bug affects only QEMU for Windows. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1743214 Title: OS/2 Warp 3 support broken in 2.11 Status in QEMU: New Bug description: Hell

[Qemu-devel] [Bug 1743214] Re: OS/2 Warp 3 support broken in 2.11

2018-01-14 Thread MVoloshin
I used QEMU 2.11 for Windows from Stephan Weil (http://qemu.weilnetz.de/). I have Windows 10 (v1709) x64. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1743214 Title: OS/2 Warp 3 support broken in

[Qemu-devel] [Bug 1743214] [NEW] OS/2 Warp 3 support broken in 2.11

2018-01-14 Thread MVoloshin
Public bug reported: Hello, I used to run OS/2 Warp 3 on QEMU with the following command line: qemu-system-i386 -vga cirrus -soundhw sb16 -hda os2warp3v2.img -boot c. It runs OK on QEMU 2.10, but immediately gives TRAP 0006 (invalid opcode?) on QEMU 2.11 (see screenshot). If it is important I h

[Qemu-devel] [Bug 1737883] [NEW] Cannot boot FreeBSD on versatilepb machine

2017-12-12 Thread MVoloshin
Public bug reported: I know some years ago it was possible to boot FreeBSD in QEMU versatilepb machine https://kernelnomicon.org/?p=229 (you can download image and kernel using web.archive.org) Now when I try to do that I get only black screen with no output even in QEMU console. I also added -

[Qemu-devel] [Bug 1737882] [NEW] QEMU Zaurus cannot boot 2.4.x kernels

2017-12-12 Thread MVoloshin
Public bug reported: I tried akita and spitz machines. 4.x, 3.x and 2.6.x kernels boot OK, but when I try to pass any 2.4.x, qemu crashes with "Trying to execute code outside RAM or ROM at 0x0080". ** Affects: qemu Importance: Undecided Status: New ** Tags: akita kernel linux

[Qemu-devel] [Bug 1734474] Re: Maemo does not boot on emulated N800

2017-11-25 Thread MVoloshin
UPD: Maemo will boot on the second attempt if I reset the emulator manually. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1734474 Title: Maemo does not boot on emulated N800 Status in QEMU: New

[Qemu-devel] [Bug 1734474] [NEW] Maemo does not boot on emulated N800

2017-11-25 Thread MVoloshin
Public bug reported: I start QEMU with qemu-system-arm-m 130 -M n800 -kernel zImage.1 -mtdblock maemo.img -append "root=/dev/mtdblock3 rootfstype=jffs2" On QEMU 1.2.0 see "NOKIA" logo and then desktop appears, but on 1.5.0 and newer (including latest versions) I see only white screen and no sign