Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1214504 > unrolled thread
| Started by | Arun Mani J <j.arunmani@proton.me> |
|---|---|
| First post | 2024-09-28 11:10 +0200 |
| Last post | 2024-10-20 22:00 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.bugs.dist
Bug#1082917: bochsbios: Physical memory read error with BIOS-bochs-latest Arun Mani J <j.arunmani@proton.me> - 2024-09-28 11:10 +0200
Bug#1082917: bochsbios: Physical memory read error with BIOS-bochs-latest Stephen Kitt <skitt@debian.org> - 2024-10-20 22:00 +0200
| From | Arun Mani J <j.arunmani@proton.me> |
|---|---|
| Date | 2024-09-28 11:10 +0200 |
| Subject | Bug#1082917: bochsbios: Physical memory read error with BIOS-bochs-latest |
| Message-ID | <JrBCF-fp3Z-5@gated-at.bofh.it> |
Package: bochsbios Version: 2.8+dfsg-1 Severity: important X-Debbugs-Cc: j.arunmani@proton.me The default BIOS-bochs-latest image shipped with Debian seems to be buggy. To reproduce: Try running Bochs with the pre-installed disk images, like this one - https://bochs.sourceforge.io/guestos/linux-img.tar.gz. When you do: bochs -f bochsrc and then press C, this is seen on screen: bx_dbg_read_linear: physical memory read error (phy=0x0000322f3130, lin=0x00000000322f3130) To fix it, if we use the BIOS-bochs-legacy image, then it works fine. Or if we use the BIOS-bochs-latest image found in the upstream's RPM package, then that also works - https://sourceforge.net/projects/bochs/files/bochs/2.7/. Encountered this error while trying LittleOS book - https://github.com/OrdoFlammae/littleosbook/discussions/20 Someone else also has faced the issue - https://askubuntu.com/questions/1521719/bochs-cant-access-bootloader-address-0x7c00-error-physical-memory-read-error Sorry if it is duplicate. Happy to help by providing more details. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.10.9-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
[toc] | [next] | [standalone]
| From | Stephen Kitt <skitt@debian.org> |
|---|---|
| Date | 2024-10-20 22:00 +0200 |
| Message-ID | <JzKfL-353v-5@gated-at.bofh.it> |
| In reply to | #1214504 |
[Multipart message — attachments visible in raw view] — view raw
Hi, On Sat, Sep 28, 2024 at 02:36:08PM +0530, Arun Mani J wrote: > The default BIOS-bochs-latest image shipped with Debian seems to be buggy. > To reproduce: > Try running Bochs with the pre-installed disk images, like this one - > https://bochs.sourceforge.io/guestos/linux-img.tar.gz. > > When you do: bochs -f bochsrc and then press C, this is > seen on screen: > bx_dbg_read_linear: physical memory read error (phy=0x0000322f3130, lin=0x00000000322f3130) > > To fix it, if we use the BIOS-bochs-legacy image, then it works fine. > Or if we use the BIOS-bochs-latest image found in the upstream's RPM package, > then that also works - https://sourceforge.net/projects/bochs/files/bochs/2.7/. > > Encountered this error while trying LittleOS book - https://github.com/OrdoFlammae/littleosbook/discussions/20 > Someone else also has faced the issue - https://askubuntu.com/questions/1521719/bochs-cant-access-bootloader-address-0x7c00-error-physical-memory-read-error > > Sorry if it is duplicate. Happy to help by providing more details. This should now be fixed in testing (in version 2.8+dfsg-2 of the package). Would you mind checking that the issue is fixed for you? If it is, provide the same fix in Debian 12 (which is also affected). Regards, Stephen
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web