Your message dated Sat, 30 Oct 2021 18:30:54 +0200
with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org>
and subject line Mass-closing old grub-installer bugs
has caused the Debian Bug report #611713,
regarding installation-reports: Installation issue grub mixup between sat
Hi,
Is there a possibility of the Debian installation with the wired
network connection in your unit?
If yes, try this way & when asked for uploading any additional drivers
say 'no' to it. You should be able to finish up your installation this
way and then you may add any missing drivers for your w
Thank you very much Samuel, I really didn’t know about Debian Boot. I asked on
the Debian User list instead, and a few very nice people kindly sent me
suggestions which finally allowed me to finish the installation.
I’d like to apologise once more for not knowing about the impressive number o
Hello,
Vlad Dragomir, le mar. 14 juil. 2020 21:11:59 +0200, a ecrit:
> First I'd like to apologise for asking this here. It's not strictly related
> to accessibility, but since I'm using the accessible Speakup driven
> installer, I thought it might be easier for members of this list to guide me
Hi Ian,
Ian Kester-Haney (2019-06-28):
> I just installed the RC2 build yesterday. The installer correctly
> identified the efi partition. There was no option to reformat this
> partition. The boot loader section if the install failed to work and
> listed the options to enter at the grub comm
I just installed the RC2 build yesterday. The installer correctly
identified the efi partition. There was no option to reformat this
partition. The boot loader section if the install failed to work and
listed the options to enter at the grub command line. Booting via the grub
cmd worked and th
On 10/01/2017 03:55 PM, Samuel Thibault wrote:
> Ok, but are no there other, released, archs which also by default put
> the kernel console on ttyS0 like sparc64?
I'm not sure whether it's arch-specific, I would rather guess it depends
on the type of hardware used. On SPARC machines it happens, be
John Paul Adrian Glaubitz, on dim. 01 oct. 2017 15:30:58 +0200, wrote:
> > And if you want something to be backported to older releases (version
> > tracking, etc.), entries in the BTS are more than welcome.
>
> A backport isn't necessary in this case, I think, as we currently
> only provide unst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi!
On 10/01/2017 03:28 PM, Cyril Brulebois wrote:
> Samuel Thibault (2017-10-01):
>> Ok, then that's indeed what is special about sparc64, and then AIUI your
>> patch is welcome :)
>>
>> (and ideally should be backported to previous releases of
Hi,
Samuel Thibault (2017-10-01):
> Ok, then that's indeed what is special about sparc64, and then AIUI
> your patch is welcome :)
>
> (and ideally should be backported to previous releases of Debian as
> needed)
Just a quick comment:
Having a bug report with all relevant information (what wor
John Paul Adrian Glaubitz, on dim. 01 oct. 2017 13:09:02 +0200, wrote:
> >> There is nothing special about sparc64 in this regard.
> >
> > Perhaps that "enabled by default" thing.
>
> The difference would be that d-i is not booting with console=ttyS0
> but it's still using the serial console on s
On 10/01/2017 12:54 PM, Samuel Thibault wrote:
>> But is that information available in finish-installation.d/90console?
>
> The point is: it doesn't need to be. We need 90console for non-systemd
> systems because sysvinit etc. are not able to automatically get the
> console configuration from the
John Paul Adrian Glaubitz, on dim. 01 oct. 2017 12:49:25 +0200, wrote:
> On 10/01/2017 12:33 PM, Samuel Thibault wrote:
> >> Yes, I'm aware of that and that's what people usually use to enable the
> >> serial
> >> console post installation. However, it's most likely not what we would
> >> want to
On 10/01/2017 12:33 PM, Samuel Thibault wrote:
>> Yes, I'm aware of that and that's what people usually use to enable the
>> serial
>> console post installation. However, it's most likely not what we would want
>> to
>> use as adding it to the kernel command line assumes that you know what type
>
Hello,
John Paul Adrian Glaubitz, on sam. 30 sept. 2017 20:17:19 +0200, wrote:
> On 09/30/2017 07:19 PM, Frank Scheiner wrote:
> > Not sure, but [1] says that it should be sufficient to add all console
> > devices
> > to the kernel command line for systemd to detect and activate them, e.g.
> > `c
On 09/30/2017 10:47 PM, John Paul Adrian Glaubitz wrote:
We might not need to adjust the baud rate as systemd calls agetty with:
ExecStart=-/sbin/agetty --keep-baud 115200,38400,9600 %I $TERM
and from the agetty manpage:
baud_rate,...
A comma-separated list of one or mor
On 09/30/2017 08:17 PM, John Paul Adrian Glaubitz wrote:
On 09/30/2017 07:19 PM, Frank Scheiner wrote:
Not sure, but [1] says that it should be sufficient to add all console devices
to the kernel command line for systemd to detect and activate them, e.g.
`console=ttyS0,9600n8` - which includes p
On 09/30/2017 10:37 PM, Frank Scheiner wrote:
>> Yes, I'm aware of that and that's what people usually use to enable the
>> serial
>> console post installation. However, it's most likely not what we would want
>> to
>> use as adding it to the kernel command line assumes that you know what type
>>
On 09/30/2017 08:17 PM, John Paul Adrian Glaubitz wrote:
> Please be aware that I am not talking about just fixing the serial console
> issue
> on SPARC machines but on all architectures supported by Debian. Hence, I want
> to use a generic and robust solution, not a quick hack.
I have quickly dis
On 09/30/2017 07:19 PM, Frank Scheiner wrote:
> Not sure, but [1] says that it should be sufficient to add all console devices
> to the kernel command line for systemd to detect and activate them, e.g.
> `console=ttyS0,9600n8` - which includes port and configuration.
Yes, I'm aware of that and tha
Hi
On 09/30/2017 10:54 AM, John Paul Adrian Glaubitz wrote:
Some users of Linux on sparc64 have noticed that the serial console is not
working
directly after installation. This is because systemd does not enable the serial
console by default.
[...]
Does anyone have a suggestion for a patch? I'd
Hi!
Some users of Linux on sparc64 have noticed that the serial console is not
working
directly after installation. This is because systemd does not enable the serial
console by default.
To address this issue, all that is needed is to enable the serial console in the
"finishinstall" step of debi
Thank you for your efforts,
I made it past the portion of install to connect to my home WiFi, wlan0, and it
succesfully connected using my WPA2 security code but then.
I was not able to get past the "hostname and domain name" requirement for
installation on my first 3 attempts to install
PRETT
Package: installation-reports
Severity: important
Tags: d-i
Box has one pata drive, master on primary ide controller, one sata drive.
Installed Squeeze to pata drive, not sure of the desigation by the installer
first drive in the list. When asked to installl grub okayed the installation to
the mbr
Your message dated Wed, 08 Sep 2010 03:58:18 +
with message-id
and subject line Closing old installation report #387215
has caused the Debian Bug report #387215,
regarding installation issue, can't install
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for [EMAIL PROTECTED]:
> reassign 469030 installation-reports
Bug#469030: debian ppc64 not booting after install
Bug reassigned from package `linux-2.6' to `installation-reports'.
>
End of message, stopping processing here.
Please contact me if you need assistance.
Debian bu
Julien BLACHE wrote:
> "\"Félix" Guerrero" <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>> Image version: debian 4.0 r0 ia64
>
> Apple machines aren't ia64, they're i386/amd64 machines.
>
> So, you used the wrong architecture, grab an i386 or amd64
> installation media instead.
Maybe we could add a wa
"\"Félix" Guerrero" <[EMAIL PROTECTED]> wrote:
Hi,
> Image version: debian 4.0 r0 ia64
Apple machines aren't ia64, they're i386/amd64 machines.
So, you used the wrong architecture, grab an i386 or amd64
installation media instead.
JB.
--
Julien BLACHE - Debian & GNU/Linux Developer - <[EMAI
Your message dated Sat, 28 Apr 2007 12:23:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421338: macbook pro installation issue
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
Package: installation-reports
Boot method: DVD
Image version: debian 4.0 r0 ia64
Date: 22:10 04-27-2007
Machine: Macbook Pro 15.4''
Processor: Intel Core 2 Duo @2.16Ghz
Memory: 1Gb
Partitions:
Output of lspci -nn and lspci -vnn:
Base System Installation Checklist:
[O] = OK, [E] = Error (plea
Your message dated Sat, 21 Apr 2007 18:14:12 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#420244: Installation Issue submit
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
Package: installation-reports
Boot method: CD
Image version: Debian GNU/Linux testing "Lenny" - Official Snapshot
amd64 CD Binary-1 20070416-03:45
Date: Sat Apr 21, 00:25
Machine: AMD 64 Athlon clon desktop (Gigabyte motherboard)
Processor: AMD 64 Athlon
Memory: 1GB
Partitions:
FilesystemTyp
* Anders Andersen <[EMAIL PROTECTED]> [2007-03-22 08:01]:
> I have done this 3 times and got the same error every time... I will
> try again tonight, I think it might be the Debian mirror I'm using?!
> Which mirror is preferred?
Can you try ftp.nl.debian.org or ftp.uk.debian.org?
--
Martin Michlm
Hi,
I have done this 3 times and got the same error every time... I will
try again tonight, I think it might be the Debian mirror I'm using?!
Which mirror is preferred?
Kind regards,
Anders Andersen
On 3/22/07, Martin Michlmayr <[EMAIL PROTECTED]> wrote:
* Anders Andersen <[EMAIL PROTECTED]>
* Anders Andersen <[EMAIL PROTECTED]> [2007-03-21 22:13]:
> I have an issue with the RC2 installer on my NSLU2 + 4 GB flash disk.
> I get an error saying:
> "The debootstrap program exited with an error (return value 1)."
Can you do another installation to see if you get the same error? It
looks
Hi,
Thanks much for the help. I was able to complete the
installation with linux26. And of course I encountered
the problem with the installation hanging after "Real
Time Clock Driver v1.12". But after I modified the
hwclock as mentioned in the resolution for bug
#277298, everything went through
On Sat, Jan 01, 2005 at 10:36:40AM -0800, Asirvatham Kripps wrote:
> --- Geert Stappers <[EMAIL PROTECTED]> wrote:
>
> > On Sat, Jan 01, 2005 at 03:31:20AM +0100, Frans Pop
> > wrote:
> > > On Saturday 01 January 2005 03:21, Asirvatham Kripps wrote:
> > > Try booting with 'linux26'.
> > That w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 01 January 2005 19:36, Asirvatham Kripps wrote:
> I'm a newbie on installing Debian, so I'm assuming
> Sarge has linux26.
Sarge does have linux26, but the default is 2.4!!!
So you have to boot the installation system with 'linux26'.
Plea
Hi,
The Dell SC-420 is a new machine with nothing on it
and I'm trying to install Debian from scratch. And I'm
not sure how I can use the "277298.sh" patch, since
I'm stuck in the installation process.
More info:
1. The problem of "No partitionable media were found"
was on the latest version of
On Sat, Jan 01, 2005 at 03:31:20AM +0100, Frans Pop wrote:
> On Saturday 01 January 2005 03:21, Asirvatham Kripps wrote:
> > I just bought a Dell poweredge SC-420 system with a 80
^^
mmm, another candidate for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 01 January 2005 03:21, Asirvatham Kripps wrote:
> I just bought a Dell poweredge SC-420 system with a 80
> GB SATA hard drive. When trying to install Debian
> linux, I get a message saying "no partitionable media
> found".
>
> I called Dell
Hi,
I just bought a Dell poweredge SC-420 system with a 80
GB SATA hard drive. When trying to install Debian
linux, I get a message saying "no partitionable media
found".
I called Dell support and they say that Debian linux
doesn't support the hard drive and Red Hat Enterprise
version does. I h
)
id 965D425F063; Sat, 11 Sep 2004 16:51:01 +1000 (EST)
Date: Sat, 11 Sep 2004 16:51:01 +1000
To: [EMAIL PROTECTED]
Subject: debian-installer: Installation issue with "Installing Base System" and
mdadm
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipa
Package: debian-installer
Severity: normal
Doing an installation using a daily netboot image from last week, using
a kernel2.6 with /boot on raid1 and / et al on lvm2 on another raid1, I
hit a problem with "Installing the Base System".
It would get to 85% (Creating Device Nodes) and then fail. As
44 matches
Mail list logo
