Bug#1035327: installation-reports: Cannot boot installer with grub2: out of memory

Package: installation-reports Severity: important Tags: d-i X-Debbugs-Cc: jamu...@debian.org (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: USB Image version: https://cdimage.debian.org/cdi

WG: Cannot boot //Questions //Where else can I ask? Part III

Von: Schwibinger Michael Gesendet: Samstag, 23. April 2022 12:37 An: Andrew M.A. Cater Betreff: AW: Cannot boot //Questions //Where else can I ask? Part III Hello Andrew! What did I do wrong. This email came: You have added to the subscriber list of

AW: Cannot boot //Questions //Where else can I ask? Part III

Erzeugung von Paketdepots sowie zu deren Benutzerkonfiguration finden Sie in der Handbuchseite apt-secure(8). Von: Andrew M.A. Cater Gesendet: Samstag, 23. April 2022 10:19 An: Schwibinger Michael Betreff: Re: Cannot boot //Questions //Where else

AW: Cannot boot //Questions //Where else can I ask?

Von: Schwibinger Michael Gesendet: Donnerstag, 21. April 2022 13:16 An: Andrew M.A. Cater Betreff: AW: Cannot boot //Questions Hello Andrew Thank You Can You help me. I did update Debian from 9 to 10. Now I can only boot in recovery mode. What did I do. I

Re: Cannot boot

On Thu, Apr 21, 2022 at 06:34:45AM +, Schwibinger Michael wrote: > Hello Group > We did update Debian LXDE 32 > and now we cannot boot. > Can somebody help? > Regards > Sophie Hello Sophie, You may find it easier to ask this question on the Debian user mailing list. Which

Cannot boot

Hello Group We did update Debian LXDE 32 and now we cannot boot. Can somebody help? Regards Sophie

Bug#1002921: marked as done (installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can)

Your message dated Sun, 02 Jan 2022 09:51:54 +0100 with message-id <2c19e32c-fcd0-46ef-8591-8e28d423c...@mailbox.org> and subject line Re: Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can has caused the Debian Bug report #1002921, reg

Re: Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

On Sun, Jan 2, 2022, 00:39 john doe wrote: > On 1/2/2022 1:20 AM, D.J.J. Ring, Jr. wrote: > > I made a new partition for /home and I reinstalled Debian, this time I > > could lot in to MATE and I could log into the CLI. > > > > But the issue remains of after the Installation disk detects my sound

Re: Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

On 1/2/2022 1:20 AM, D.J.J. Ring, Jr. wrote: I made a new partition for /home and I reinstalled Debian, this time I could lot in to MATE and I could log into the CLI. But the issue remains of after the Installation disk detects my sound card, it seems to find my sound card, but immediately after

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

I made a new partition for /home and I reinstalled Debian, this time I could lot in to MATE and I could log into the CLI. But the issue remains of after the Installation disk detects my sound card, it seems to find my sound card, but immediately after finding it, no further sound is heard. This r

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

I don't know why when using the installer, not hearring espeak in console isn't a installer issue. I believe I have already done what you are speaking of. I have /home/djringjr. At first I reused this, the installer permits NOT formatting a separate /home partition. That's what I did. I had pr

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

> I can install the last version of the previous Debian before Bullseye > perfectly with my current /home folder. > > Best wishes, > > David > > Regards, > > > > On Sat, Jan 1, 2022, 14:39 Holger Wansing wrote: > >> Hi, >> >> "D.J.J. Rin

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

ds, On Sat, Jan 1, 2022, 14:39 Holger Wansing wrote: > Hi, > > "D.J.J. Ring, Jr." wrote (Sat, 1 Jan 2022 13:37:20 -0500): > > 1. Cannot boot into MATE GUI means that I cannot boot into the MATE > > Graphical User Interface with the user account - which

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

Hello Holger Wansing, Thanks for helping me with these problems. Here are my answers to my best ability to answer them. 1. Cannot boot into MATE GUI means that I cannot boot into the MATE Graphical User Interface with the user account - which is what is expected to happen after a normal

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

Also I just used systemctl set-default multi-user.target to change to a console log in. I cannot log in as user, only as root. GUI can also only be started as root. Have espeakup in console by as soon as log into Mate using root account, no sound, Orca setup has no speech settings. Regards, Davi

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

Package: installation-reports Severity: important X-Debbugs-Cc: n...@arrl.net (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: USB Image version: Image version: firmware-11.2.0-amd64-DVD-1.iso

Bug#822941: marked as done (debian-installer: cannot boot installed on VirtualBox with EFI-enabled)

Your message dated Tue, 13 Apr 2021 16:02:14 +0200 (CEST) with message-id and subject line UEFI install on Virtual Box should be fixed with VB 6.1 has caused the Debian Bug report #822941, regarding debian-installer: cannot boot installed on VirtualBox with EFI-enabled to be marked as done. This

Bug#911810: debian-installer: cannot boot installed on EFI with single xfs root

Package: debian-installer Severity: important I found with the lastest weekly iso (found in debian-cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso) installing with xfs+uefi lead to a non-bootable system due to grub not being able to find the xfs module, without any notice or wa

Bug#823020: Bug#823500: cannot boot from ext4

Hi Thierry, Thierry Reding (2017-02-27): > On Fri, May 06, 2016 at 02:20:45AM +0200, Cyril Brulebois wrote: > > Cyril Brulebois (2016-05-06): > > > Anyway, we could probably implement the change globally regardless, just > > > to make it possible to check the hypothesis on a wide range of device

Bug#823020: Bug#823500: cannot boot from ext4

On Fri, May 06, 2016 at 02:20:45AM +0200, Cyril Brulebois wrote: > Cyril Brulebois (2016-05-06): > > Anyway, we could probably implement the change globally regardless, just > > to make it possible to check the hypothesis on a wide range of devices, > > and only figure out later how to fix this in

Bug#822941: debian-installer: cannot boot installed on

On Wed, Aug 24, 2016 at 09:30:15AM +0200, Philipp Kern wrote: > I agree. Especially keying off the vendor name here when the expectation is > that they fix the bug (in which case the workaround should not be applied > anymore). However, has a bug actually been filed with VirtualBox about this > beh

Bug#822941: debian-installer: cannot boot installed on

On 2016-08-19 15:54, Steve McIntyre wrote: Adding a hacky workaround for broken initial UEFI support in a virtualistion platform is ludicrous here - if you're using VirtualBox then install without UEFI, or if you must use the *experimental support* for EFI in VirtualBox [1] use the documented opt

Processed: Re: Bug#822941: debian-installer: cannot boot installed on

Processing control commands: > tag -1 +wontfix Bug #822941 [debian-installer] debian-installer: cannot boot installed on VirtualBox with EFI-enabled Added tag(s) wontfix. -- 822941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822941 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#822941: debian-installer: cannot boot installed on

Control: tag -1 +wontfix On Fri, Aug 19, 2016 at 07:12:17AM +0900, Hideki Yamane wrote: >control: reopen -1 >control: tag -1 -moreinfo > >On Wed, 17 Aug 2016 17:17:49 +0100 >Steve McIntyre wrote: > >> > Probably VirtualBox UEFI seeks /boot/efi/EFI/BOOT, not >> > /boot/efi/EFI/${distro}. >> > I

Processed: Re: Bug#822941: debian-installer: cannot boot installed on

Processing control commands: > reopen -1 Bug #822941 {Done: Steve McIntyre } [debian-installer] debian-installer: cannot boot installed on VirtualBox with EFI-enabled Bug reopened Ignoring request to alter fixed versions of bug #822941 to the same values previously set > tag -1 -morein

Bug#822941: debian-installer: cannot boot installed on

ng UEFI installation) Debian : cannot boot Ubuntu : cannot boot As specification, just installing /boot/efi/EFI/BOOT/*.efi is NOT good. However, from users' view, it prefer Fedora/CentOS/openSUSE behavior to Debian and Ubuntu. This is because "install and just boot" is expecte

Bug#822941: marked as done (debian-installer: cannot boot installed on VirtualBox with EFI-enabled)

Your message dated Wed, 17 Aug 2016 17:17:49 +0100 with message-id <20160817161749.ga8...@einval.com> and subject line Re: Bug#822941: debian-installer: cannot boot installed on has caused the Debian Bug report #822941, regarding debian-installer: cannot boot installed on VirtualBox wi

Bug#822941: debian-installer: cannot boot installed on

VirtualBox with EFI-enabled Message-Id: <20160818003938.a21a906e15d2a2e67bdf4...@debian.or.jp> In-Reply-To: <20160429231623.gu5...@einval.com> Organization: Debian JP Project X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.30; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII C

Bug#823020: Bug#823500: cannot boot from ext4

Cyril Brulebois (2016-05-06): > Anyway, we could probably implement the change globally regardless, just > to make it possible to check the hypothesis on a wide range of devices, > and only figure out later how to fix this in a better way? > > Vagrant, what do you think? I've pushed a pu/disable

Bug#823020: Bug#823500: cannot boot from ext4

Cyril Brulebois (2016-05-06): > Strange, vagrant said partitioning from jessie worked fine? > > Anyway, we could try passing the mentioned option to mkfs.ext* to make > sure it doesn't get in the way, and see how it goes? > > I suppose we're interested in patching commit.d/format_ext3 from > src

Bug#823020: Bug#823500: cannot boot from ext4

Heinrich Schuchardt (2016-05-05): > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The problem occurs with ext4 partitions created with either of Jessie > or Stretch when the partition is created with > > sudo mkfs.ext4 /dev/mmcblk0p1 Strange, vagrant said partitioning from jessie worke

Bug#823020: Bug#823500: cannot boot from ext4

I had no problems booting form a ext3 partition. So at least there seems to be an option to have journaling enabled.

Bug#823020: Bug#823500: cannot boot from ext4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The problem occurs with ext4 partitions created with either of Jessie or Stretch when the partition is created with sudo mkfs.ext4 /dev/mmcblk0p1 -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJXK3PkAAoJEMSB27wsBRrEJI0P+wcRzCLunMoY

Processed: Re: Bug#823500: cannot boot from ext4

set > tags 823500 confirmed Bug #823500 [u-boot-imx] cannot boot from ext4 Ignoring request to alter tags of bug #823500 to the same tags previously set -- 823020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823020 823500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823500 Debian Bug Tr

Processed: Re: Bug#823500: cannot boot from ext4

u-boot-imx] cannot boot from ext4 Added tag(s) confirmed. -- 823020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823020 823500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#823020: Bug#823500: cannot boot from ext4

Control: block 823020 by 823500 Control: tags 823500 confirmed On 2016-05-05, Heinrich Schuchardt wrote: > u-boot-imx fails to read file > /dtbs/4.5.0-1-armmp/imx6q-wandboard-revb1.dtb > from an ext4 partition though the file exists. > > lsext4 mmc 0 dtbs > does not show the subdirectories in the

Processed: Re: Bug#823500: cannot boot from ext4

set > tags 823500 confirmed Bug #823500 [u-boot-imx] cannot boot from ext4 Ignoring request to alter tags of bug #823500 to the same tags previously set -- 823020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823020 823500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823500 Debian Bug Tr

Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

On Sat, 30 Apr 2016 00:16:23 +0100 Steve McIntyre wrote: > Do we know what version of Virtualbox? That could be a major factor > here. I've just a test installation using the UEFI support in the > virtualbox package in Jessie (4.3.36), which is labelled as > "experimental support". VirtualBox ve

Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

Control: tag -1 moreinfo On Fri, Apr 29, 2016 at 05:33:47PM +0900, Hideki Yamane wrote: >Package: debian-installer >Severity: important > >Dear Maintainer, > > I found user notes Debian on VBox with EFI enabled environment cannot > boot, see http://qiita.com/zakuro9715/items

Processed: Re: Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

Processing control commands: > tag -1 moreinfo Bug #822941 [debian-installer] debian-installer: cannot boot installed on VirtualBox with EFI-enabled Added tag(s) moreinfo. -- 822941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822941 Debian Bug Tracking System Contact

Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

Dear Yamane-san, Thanks for your report! On Fri, Apr 29, 2016 at 5:33 PM, Hideki Yamane wrote: > Package: debian-installer > Severity: important > > Dear Maintainer, > > I found user notes Debian on VBox with EFI enabled environment cannot > boot, see http://qiita

Bug#822941: debian-installer: cannot boot installed on VirtualBox with EFI-enabled

Package: debian-installer Severity: important Dear Maintainer, I found user notes Debian on VBox with EFI enabled environment cannot boot, see http://qiita.com/zakuro9715/items/45e82473ce39914e04ed (in Japanese) I've confirmed it with d-i9 alpha5. And, it doesn't happen with Fedor

Bug#806574: debian-installer: Cannot boot from ISCSI target after successful installation

Package: debian-installer Version: stable Severity: normal Tags: d-i Dear Maintainer, installed to an ISCSI target with the Jessie installer (netboot). The machine has one hard disc reported as sda. Chose Manual Partitioning, ISCSI, selected the target as sdb, created a partition sdb1 for /boot,

Bug#698103: marked as done (debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM)

Your message dated Mon, 11 Feb 2013 23:47:47 + with message-id and subject line Bug#696786: fixed in debian-installer 20130211 has caused the Debian Bug report #696786, regarding debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM to be marked as done. This

Bug#698103: marked as done (debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM)

Your message dated Sun, 10 Feb 2013 16:35:58 + with message-id <5117cc6e.2090...@pyro.eu.org> and subject line Re: Bug#696786: please adjust MFSROOT_LIMIT; adjust lowmem thresholds has caused the Debian Bug report #696786, regarding debian-installer-7.0-netboot-kfreebsd-amd64: cannot b

Processed: Re: Bug#698103: debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM

3 [debian-installer-7.0-netboot-kfreebsd-amd64] debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM Bug reassigned from package 'debian-installer-7.0-netboot-kfreebsd-amd64' to 'src:debian-installer'. Ignoring request to alter found versions of b

Bug#698103: debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM

user debian-...@lists.debian.org usertags 698103 kfreebsd reassign 698103 src:debian-installer tags 698103 = patch pending sid wheezy severity 696786 important merge 696786 698103 thanks Hi Michael, On 14/01/13 04:16, Michael Tsang wrote: > Package: debian-installer-7.0-netboot-kfreebsd-amd64 [..

Bug#698103: debian-installer-7.0-netboot-kfreebsd-amd64: cannot boot on system with 128MB RAM

Package: debian-installer-7.0-netboot-kfreebsd-amd64 Severity: important Dear Maintainer, I got http://opensource.nchc.org.tw/debian/dists/wheezy/main/installer- kfreebsd-amd64/current/images/netboot-9/mini.iso and tried to boot it in a VirtualBox VM with 128 MB RAM and it does not load. When I i

Bug#327287: marked as done (Cannot boot Sarge boot disk on Proliant 1500)

Your message dated Wed, 08 Sep 2010 03:58:04 + with message-id and subject line Closing old installation report #327287 has caused the Debian Bug report #327287, regarding Cannot boot Sarge boot disk on Proliant 1500 to be marked as done. This means that you claim that the problem has been

Bug#248800: marked as done (installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk))

Your message dated Wed, 08 Sep 2010 03:58:37 + with message-id and subject line Closing old installation report #248800 has caused the Debian Bug report #248800, regarding installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk) to be marked as done

Bug#537222: marked as done (cannot boot with Debian 5.0.2 ia64 - DVD made from iso)

Your message dated Thu, 16 Jul 2009 02:40:22 -0700 with message-id <20090716094022.ga4...@dario.dodds.net> and subject line Re: Bug#537222: cannot boot with Debian 5.0.2 ia64 - DVD made from iso has caused the Debian Bug report #537222, regarding cannot boot with Debian 5.0.2 ia64 - DV

Bug#537222: cannot boot with Debian 5.0.2 ia64 - DVD made from iso

loaded this file 2 times and burned this iso twice using 2 different systems with the same results. I have burned this iso successfully with no write errors. I cannot boot from the burn disk. I have burned this image with a windows mac mini , and a 2nd time with a mac pro. booth burns are identic

Bug#358153: testing (etch): cannot boot on software raid

Package: installation-reports Boot method: CD Image version: netinst CD image from Mar 17 2006 Date: Mar 17 2006 Machine: - Processor: 2.66MHz Intel P. Memory: 512 Partitions: Disk /dev/hdc: 80.0 GB, 80060424192 bytes 255 heads, 63 sectors/track, 9733 cylinders Units = cylinders of 16065 * 512

Processed: Re: Bug#358153: testing (etch): cannot boot on software raid

Processing commands for [EMAIL PROTECTED]: > reassign 358153 initramfs-tools Bug#358153: testing (etch): cannot boot on software raid Bug reassigned from package `installation-reports' to `initramfs-tools'. > thanks Stopping processing here. Please contact me if you need assista

Bug#352672: marked as done (debian-installer: cannot boot installation media on ppc ibm B50)

B SCSI HDD Architecture is CHRP. ps/2 keyboard+mouse S3 pci video. While trying to install debian on an ibm rs6000 B50 (i have 4 i want to use!) i want to report the problems i have. First, i downloaded the sarge boot image (speaking of the 'netboot' minicd iso image) and i cannot boot

Cannot boot on HP ZD7000 notebook with kernel 2.6.8, hang on ip1394 and parport

Hi, Any help will be highly appreciated! I just bought a HP ZD7260us notebook with a P4 3.2GHz/HT CPU and without floppy drive, and tried to installl Sarge using Debian-Installer pre-rc2 and the latest /pub/cdimage-testing/daily/i386/20041020/sarge-i386-netinst.iso. I started the installer with

Bug#252177: Cannot boot m68k d-i, due to the lack of pm2fb driver

On Tue, Jun 01, 2004 at 06:15:04PM -0300, Martin Michlmayr wrote: > reassign 252177 kernel-image-2.4.25-amiga > retitle 252177 please include pm2fb driver > severity 252177 normal > thanks > > * Margarita Manterola <[EMAIL PROTECTED]> [2004-06-01 17:47]: > > Package: installation-reports > > Sever

Bug#252177: Cannot boot m68k d-i, due to the lack of pm2fb driver

reassign 252177 kernel-image-2.4.25-amiga retitle 252177 please include pm2fb driver severity 252177 normal thanks * Margarita Manterola <[EMAIL PROTECTED]> [2004-06-01 17:47]: > Package: installation-reports > Severity: grave > > I was trying to install Simon Richter's Amiga computer, and we cou

Processed: Re: Bug#252177: Cannot boot m68k d-i, due to the lack of pm2fb driver

Processing commands for [EMAIL PROTECTED]: > reassign 252177 kernel-image-2.4.25-amiga Bug#252177: Cannot boot m68k d-i, due to the lack of pm2fb driver Bug reassigned from package `installation-reports' to `kernel-image-2.4.25-amiga'. > retitle 252177 please include pm2fb d

Bug#252177: Cannot boot m68k d-i, due to the lack of pm2fb driver

Package: installation-reports Severity: grave I was trying to install Simon Richter's Amiga computer, and we couldn't even boot up the kernel, due to the lack of the pm2fb video driver. Can it be included ASAP, so that we can test it before the end of the debconf, pretty please? -- Love, Marga.

Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

> * Adam Lydick <[EMAIL PROTECTED]> [2004-05-13 21:20]: > > That sounds good to me. Can fdisk be exposed in an "expert mode"? I > > miss it. On Fri, 2004-05-14 at 14:08 +0100, Martin Michlmayr wrote: > I don't know... maybe we could include fdisk on the images where we > have enough space, but not

Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

Martin Michlmayr wrote: > I don't know... maybe we could include fdisk on the images where we > have enough space, but not show it in the menu at all. This way, > experts could run fdisk manually on the 2nd virtual console. We already have eg, cfdisk like that on i386. A menu item might be nice,

Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

On Thu, 2004-05-13 at 15:46 +0100, Martin Michlmayr wrote: > * Adam Lydick <[EMAIL PROTECTED]> [2004-05-12 21:32]: > > Partitioning -- Not really an error, but I found it difficult to > > "discover" how to create a swap partition. It would be easier to > > find if the actions available were all sho

Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

* Adam Lydick <[EMAIL PROTECTED]> [2004-05-13 21:20]: > That sounds good to me. Can fdisk be exposed in an "expert mode"? I > miss it. I don't know... maybe we could include fdisk on the images where we have enough space, but not show it in the menu at all. This way, experts could run fdisk manua

Bug#248800: Acknowledgement (installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk))

> * Adam Lydick <[EMAIL PROTECTED]> [2004-05-12 23:16]: > > When I repartitioned, the "active" boot partition flag was removed from > > the XP partition. I restored it in the partitioning tool and that > > allowed me to boot into XP again. > > Can you check whether this is the same as: >#24850

Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

clone 248800 -1 reassign -1 partman retitle -1 Have a "swap" option in the list of to be formated filesystems severity -1 wishlist thanks * Adam Lydick <[EMAIL PROTECTED]> [2004-05-12 21:32]: > Partitioning -- Not really an error, but I found it difficult to > "discover" how to create a swap parti

Bug#248800: Acknowledgement (installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk))

clone 248800 -1 reassign -1 partman retitle -1 partman should warn about errors earlier severity -1 wishlist thanks * Adam Lydick <[EMAIL PROTECTED]> [2004-05-12 23:16]: > When I repartitioned, the "active" boot partition flag was removed from > the XP partition. I restored it in the partitioning

Processed: Re: Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

Processing commands for [EMAIL PROTECTED]: > clone 248800 -1 Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk) Bug 248800 cloned as bug 248874. > reassign -1 partman Bug#248874: installer beta 4 installation report (mbr damaged

Processed: Re: Bug#248800: Acknowledgement (installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk))

Processing commands for [EMAIL PROTECTED]: > clone 248800 -1 Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk) Bug 248800 cloned as bug 248873. > reassign -1 partman Bug#248873: installer beta 4 installation report (mbr damaged

Bug#248800: Acknowledgement (installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk))

Additional info: I think my guess about MBR damage was a false alarm. (but I've ruined the evidence by this point). When I repartitioned, the "active" boot partition flag was removed from the XP partition. I restored it in the partitioning tool and that allowed me to boot into XP again. Partiti

Bug#248800: installer beta 4 installation report (mbr damaged, grub misdetection, cannot boot from rescue disk)

Package: installation-reports Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/beta4/sarge-i386-netinst.iso uname -a: unable to boot installed system. installer: Linux (none) 2.4.25-1-386 #2 (date) i686 unknown Date: 2004-05-12 Method: boot and install off c

Bug#220048: marked as done (Cannot boot from CD)

Your message dated Sun, 18 Jan 2004 14:06:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Can now boot from CD :-) has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Re: Bug#220048: 220048:Cannot boot from CD

On 2003-11-17, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: >> >> I'am afraid it is not that problem, as I can boot both ISOLINUX and >> SYSLINUX CD's correctly, but not beta-1 sarge-i386-netinst. > > Syslinux is the more robust of the two and was just asking for a test > to make sure it does

Re: Bug#220048: 220048:Cannot boot from CD

Miernik <[EMAIL PROTECTED]> writes: > On 2003-11-16, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > > > > The first CD is isolinux based, all the other CDs in the set are > > syslinux based. > > > > It would show if you can boot syslinux without problems. > > I'am afraid it is not that problem

Re: Bug#220048: 220048:Cannot boot from CD

On 2003-11-16, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > > The first CD is isolinux based, all the other CDs in the set are > syslinux based. > > It would show if you can boot syslinux without problems. I'am afraid it is not that problem, as I can boot both ISOLINUX and SYSLINUX CD's corr

Bug#220048: 220048:Cannot boot from CD

Klaus Pedersen <[EMAIL PROTECTED]> writes: > Goswin von Brederlow wrote: >> Klaus Pedersen <[EMAIL PROTECTED]> writes: >> I have no problem booting other distributions like: >> - debian-30r1-i386-binary-1_NONUS.iso >> That should be isolinux too, just an older

Bug#220048: 220048:Cannot boot from CD

Klaus Pedersen <[EMAIL PROTECTED]> writes: > Hi, > > I have the same problem with my new PC. I thought that it was a bad disk and > then a bad CRRW drive - but no - I have burned the disk 3 times now. > > - AMD Barton XP 2500+ > - MSI Nforce2 motherboard > - Phoenix Award bios, V5.1 041803 18:12

Bug#220048: 220048:Cannot boot from CD

Hi, I have the same problem with my new PC. I thought that it was a bad disk and then a bad CRRW drive - but no - I have burned the disk 3 times now. - AMD Barton XP 2500+ - MSI Nforce2 motherboard - Phoenix Award bios, V5.1 041803 18:12:13 - LG DVD/CDRW combo - no floppy. I have no problem bootin

Re: Cannot boot sarge distribution

[Paul Galbraith] > This still happens...I don't know if the module is correct for my > controller or not, can you point me in the right direction to find > out? Not really. Try to boot knoppix, and see if that work. Extract the output from 'lspci -t -v; lspci -n', and try to check if the PCI id

Re: Cannot boot sarge distribution

ssage - From: "Petter Reinholdtsen" <[EMAIL PROTECTED]> To: "Paul Galbraith" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Saturday, August 30, 2003 5:28 AM Subject: Re: Cannot boot sarge distribution > [Paul Galbraith] > > I just downloaded the lat

Re: Cannot boot sarge distribution

[Sven Luther] > BTW, i tried booting the cdrom initrd with a kernel i usually use, > which has most of the stuff built-in, and d-i complained loudly > about all those missing modules. Yes. It is annoying. Is there any way for hw-detect to find out if the module is compiled into the kernel, or to

Re: Cannot boot sarge distribution

On Sat, Aug 30, 2003 at 11:28:53AM +0200, Petter Reinholdtsen wrote: > [Paul Galbraith] > > I just downloaded the latest sarge snapshot cd from > > http://gluck.debian.org/cdimage/testing/netinst/i386/ and tried > > installing, but had two separate (I think) problem. I used the > > vanilla linux k

Re: Cannot boot sarge distribution

[Paul Galbraith] > I just downloaded the latest sarge snapshot cd from > http://gluck.debian.org/cdimage/testing/netinst/i386/ and tried > installing, but had two separate (I think) problem. I used the > vanilla linux kernel provided, presumably knowing the right > paramters to use can alleviate t

Cannot boot sarge distribution

I just downloaded the latest sarge snapshot cd from http://gluck.debian.org/cdimage/testing/netinst/i386/ and tried installing, but had two separate (I think) problem.  I used the vanilla linux kernel provided, presumably knowing the right paramters to use can alleviate the problems, but I d

Re: cannot boot to install woody

#include * Fabio Calefato [Thu, Feb 06 2003, 07:46:06PM]: > anyway, boot hangs. i've tried re-writing it twice again, but noway. > so i switched from root.bin to other img, till i succeded in booting > with the rescue.bin img file. After uncompressing the img and detecting > my hw, i got a kern

cannot boot to install woody

Hi, this is the first time i install a debian linux. i've downloaded the 1st cd image from internet. Since i have a non-bootable scsi cd-rom, i had to create a boot floppy. i thought not to have problem 'cause i thought it should've been much like installing a suse, red-hat or mandrke. i wrote the

Bug#77040: marked as done ([ppc] cannot boot from CD or new system)

Your message dated Sat, 10 Nov 2001 04:59:17 -0700 with message-id <2000045917.F200@Obsession> and subject line Bug#77040: Tried later version of debian? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Re: Cannot boot debian 2.2r2

Sante Gnerre <[EMAIL PROTECTED]> writes: > I have an hung-up when I try to boot debian 2.2r2. > The problem: > I put cd1 in the cd tray and I boot from it. Try booting from the 2nd CD. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED]

Re: Cannot boot debian 2.2r2

IIRC, sym53c416.c is a scsi driver. On Fri, Feb 09, 2001 at 09:06:20AM -0800, Sante Gnerre wrote: > > Hello there, > > I have an hung-up when I try to boot debian 2.2r2. > > Hardware: > P-120 motherboard - American Megatrend P5STE (AMIBIOS) > 16M RAM > cd (Atapi, it's an old 4x NEC) > Max

Cannot boot debian 2.2r2

Hello there, I have an hung-up when I try to boot debian 2.2r2. Hardware: P-120 motherboard - American Megatrend P5STE (AMIBIOS) 16M RAM cd (Atapi, it's an old 4x NEC) Maxtor 30 Giga HD ATI Rage 128 video card with 16M ethernet card (I don't remember the model) Sound Blaster 16 No flopp

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

Sorry for taking time to reply -- been on vacation ... On 26 Aug 2000 19:46:42 -0400, Adam Di Carlo <[EMAIL PROTECTED]> wrote: > era eriksson <[EMAIL PROTECTED]> writes: >> The instructions in the installation manual specifically say to >> submit a bug report against boot-floppies if you can't

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

era eriksson <[EMAIL PROTECTED]> writes: > The instructions in the installation manual specifically say to submit > a bug report against boot-floppies if you can't manage to get it running. > > Sure. But

Bug#69793: marked as done (IBM PC Server 320 (MCA/PCI Pentium) cannot boot)

ontent-Transfer-Encoding: 7bit Message-ID: <[EMAIL PROTECTED]> Date: Wed, 23 Aug 2000 16:45:37 +0300 (EET DST) To: [EMAIL PROTECTED] Subject: IBM PC Server 320 (MCA/PCI Pentium) cannot boot X-Mailer: VM 6.72 under Emacs 19.34.1 From: era eriksson <[EMAIL PROTECTED]> X-Pgp-Fingerprint: 85 40 A8

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

Good news: I'm happily running Potato on this monster now. I'm sending this only to tie up some loose ends. Upgrading the Flash BIOS to the latest version (29A) fixed everything. An update disk is available for download from IBM's site. (The exact location was

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

era eriksson <[EMAIL PROTECTED]> writes: > > I mean, if you can't boot linux you can't boot and there's probably > > littel we can do. > > Your installation manual requests that I submit a bug report if I > can't get it to work. It's not like I'm demanding that you fix this. > (And I'm sorry i

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

On 23 Aug 2000 22:06:04 -0400, Adam Di Carlo <[EMAIL PROTECTED]> wrote: > era eriksson <[EMAIL PROTECTED]> writes: > Unable to handle kernel paging request at virtual address daf1 > current-> tss.cr3 = 00101000, %cr3 = 00101000 > *pde = > Oops: > CPU:0 > EIP:0010:[

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

era eriksson <[EMAIL PROTECTED]> writes: > The 256KB cache is enabled, Hmmm. You might *try* turning that off. > the PCI slot interrupts (#1 and #2) are > set up on "auto-select" (should I do this by hand? I get to choose the > IRQs myself if I want to) I doublt that's the problem. > and I've

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

On Wed, 23 Aug 2000 09:54:53 -0500, Nathan E Norman <[EMAIL PROTECTED]> wrote: > On Wed, Aug 23, 2000 at 04:45:37PM +0300, era eriksson wrote: > [ snip ] >> Package: boot-floppies >> Version: (potato >> >> architecture: i386 >> model:IBM PC Server 320 >> memory: 48MB > Conf

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

On Wed, Aug 23, 2000 at 04:45:37PM +0300, era eriksson wrote: [ snip ] > Package: boot-floppies > Version: (potato > > architecture: i386 > model:IBM PC Server 320 > memory: 48MB Configured how? > scsi: AIC-7870 > cd-rom: ... it just says IBM CDRM0103 or something li

Bug#69793: IBM PC Server 320 (MCA/PCI Pentium) cannot boot

Package: boot-floppies Version: (potato architecture: i386 model:IBM PC Server 320 memory: 48MB scsi: AIC-7870 cd-rom: ... it just says IBM CDRM0103 or something like that (SCSI #6) network card: (yes; dunno exactly) pcmcia: N/A video:Cirrus Logic GD-54xx

  1   2   >