Re: /boot partition size

2025-04-07 Thread Pascal Hambourg
On 07/04/2025 at 09:23, Jen K wrote: I've been reading the official Debian install document, and I can't find an answer when it comes to partitioning how big the /boot should actually be. FWIW the /boot size has been raised to 768-1024 MB in Debian installer guided partitioning. Same with the

Re: /boot partition size

2025-04-07 Thread Cyril Brulebois
Lennart Sorensen (2025-04-07): > Looking at my system, I am seeing initrd sizes of 130MB. Add in another > 10MB for the kernel, and you can not fit two kermels in 250MB. Try 500MB > if you want to be sure to be able to fit two or three kernels at a time > for a while yet. Of course better yet i

Re: /boot partition size

2025-04-07 Thread Lennart Sorensen
On Mon, Apr 07, 2025 at 06:08:22PM +0700, Andika Triwidada wrote: > Not sure if this is the correct list to ask that question. > But anyway, you need space for at least three sets of unpacked kernel images > including generated initrd. For current x86 kernels, one set is roughly 75 > MB. > So 250 M

Re: /boot partition size

2025-04-07 Thread Andika Triwidada
On Mon, Apr 7, 2025 at 2:42 PM Jen K wrote: > I've been reading the official Debian install document, and I can't find > an answer when it comes to partitioning how big the /boot should actually > be. While there are recommendations for /var, /tmp, /root and /home > Hi Jen, Not sure if this is

Re: boot-installer accessability: edit in installation-guide

2021-12-26 Thread Samuel Thibault
Holger Wansing, le dim. 26 déc. 2021 14:07:37 +0100, a ecrit: > I still wonder, if it's correct to format a combination of keys as > " - "? > > From my memory I thought we have a format like "+" for that? > (the plus sign as an incarnation of what to do: press both keys at the same > time) I don'

Re: boot-installer accessability: edit in installation-guide

2021-12-26 Thread Holger Wansing
Hi, Samuel Thibault wrote (Sun, 26 Dec 2021 11:55:22 +0100): > Hello, > > Holger Wansing, le dim. 26 déc. 2021 11:39:44 +0100, a ecrit: > > I would like to recommend some proofreading for your latest > > installation-guide > > commit. > > Thanks for proofreading :) > > > I have added some for

Re: boot-installer accessability: edit in installation-guide

2021-12-26 Thread Samuel Thibault
Hello, Holger Wansing, le dim. 26 déc. 2021 11:39:44 +0100, a ecrit: > I would like to recommend some proofreading for your latest installation-guide > commit. Thanks for proofreading :) > I have added some formatting tags (like &enterkey;) for the > keystrokes They are already in the common e

Re: boot-time accessibility issues

2020-04-05 Thread Jude DaShiell
since several different kinds of accessibility can be provided, which kind of accessibility is needed also needs sorting out. Apple in 10.4 Tiger had things set up such that if the computer was completely hooked up including a set of speakers a question as to which language a user needed came up o

Re: boot-time accessibility issues

2020-04-05 Thread Rich Morin
I've been musing about a comment Samuel Thibault made a while back: > On Mar 2, 2020, at 07:57, Samuel Thibault wrote: > > Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit: >> ... More generally, is there a better way to provide accessibility at boot >> time? > > The question is how to

Re: boot-time accessibility issues

2020-03-15 Thread Samuel Thibault
Hello, Rich Morin, le jeu. 12 mars 2020 09:28:49 -0700, a ecrit: > The idea of detecting the presence (or absence) of a blind-related device > seems worth pursuing, even if there are some issues to be resolved. The Debian Installer detects the presence of a braille device and then enables access

Re: boot-time accessibility issues

2020-03-12 Thread Jude DaShiell
9 > From: Rich Morin > To: debian-boot@lists.debian.org > Cc: debian-accessibil...@lists.debian.org > Subject: Re: boot-time accessibility issues > Resent-Date: Thu, 12 Mar 2020 16:29:21 + (UTC) > Resent-From: debian-accessibil...@lists.debian.org > > The idea of detectin

Re: boot-time accessibility issues

2020-03-12 Thread Rich Morin
The idea of detecting the presence (or absence) of a blind-related device seems worth pursuing, even if there are some issues to be resolved. For example, following Jude's notion of checking for a monitor, maybe Avahi and SSH could be enabled whenever a monitor isn't found. For that matter, ena

Re: boot-time accessibility issues

2020-03-12 Thread Devin Prater
gt; To: debian-boot@lists.debian.org >> Cc: debian-accessibil...@lists.debian.org >> Subject: Re: boot-time accessibility issues >> Resent-Date: Thu, 12 Mar 2020 02:07:16 + (UTC) >> Resent-From: debian-accessibil...@lists.debian.org >> >> Jude DaShiell said: >

Re: boot-time accessibility issues

2020-03-11 Thread Jude DaShiell
full circle, solutions zero. On Thu, 5 Mar 2020, Rich Morin wrote: > Date: Thu, 5 Mar 2020 23:54:14 > From: Rich Morin > To: debian-boot@lists.debian.org > Cc: debian-accessibil...@lists.debian.org > Subject: Re: boot-time accessibility issues > Resent-Date: Thu, 12 Mar 2020 0

Re: boot-time accessibility issues

2020-03-11 Thread Rich Morin
Jude DaShiell said: > If dummy was used for monitor type, the screen reader could come up talking > without any monitor attached. ... I can think of a couple of issues with this approach. First, there are various reasons for leaving a monitor off a system. For example, if a RasPi is being us

Re: boot-time accessibility issues

2020-03-05 Thread Rich Morin
> On Mar 5, 2020, at 03:30, Samuel Thibault wrote: > > One thing I am missing in your description is: how is the system getting > installed in your use case? Is it installed by the blind user himself, > or by somebody else? Ideally, the system hardware and software could be installed and config

Re: boot-time accessibility issues

2020-03-05 Thread Ben Hutchings
On Thu, 2020-03-05 at 07:16 -0500, Jude DaShiell wrote: > If dummy was used for monitor type, the screen reader could come up > talking without any monitor attached. Many linux distros including > debian can get a monitor turned on and off during operation and don't > let a screen reader know now

Re: boot-time accessibility issues

2020-03-05 Thread Jude DaShiell
al could have been run on boot to eliminate the firmware complaint. On Thu, 5 Mar 2020, Rich Morin wrote: > Date: Thu, 5 Mar 2020 03:53:30 > From: Rich Morin > To: debian-boot@lists.debian.org > Cc: debian-accessibil...@lists.debian.org > Subject: Re: boot-time accessibility issues

Re: boot-time accessibility issues

2020-03-05 Thread Samuel Thibault
Hello, Rich Morin, le jeu. 05 mars 2020 02:53:30 -0600, a ecrit: > I don't know all the ins and outs of preseeding, etc. So, I'll talk about > use cases. I'm mostly looking for a way to make freshly installed systems > (e.g., PC, RasPi) accessible in two situations: One thing I am missing in

Re: boot-time accessibility issues

2020-03-05 Thread Rich Morin
Thanks to everyone for considering these questions, offering suggestions, etc. Here are some comments and clarifications. I don't know all the ins and outs of preseeding, etc. So, I'll talk about use cases. I'm mostly looking for a way to make freshly installed systems (e.g., PC, RasPi) acce

Re: boot-time accessibility issues

2020-03-02 Thread Samuel Thibault
john doe, le lun. 02 mars 2020 19:33:22 +0100, a ecrit: > Actually, creating a new cd iso that would have accessibility in mind > could be one option. > > EG: > > debian-10.3-accessibility-netinst.iso Yes, but I don't think it is a good option. For most impact, it's better to make the standard

Re: boot-time accessibility issues

2020-03-02 Thread john doe
On 3/2/2020 5:35 PM, Samuel Thibault wrote: > john doe, le lun. 02 mars 2020 17:24:48 +0100, a ecrit: >> On 3/2/2020 5:13 PM, Samuel Thibault wrote: >>> john doe, le lun. 02 mars 2020 17:02:49 +0100, a ecrit: Prompting the user with a question asking if accessibility is desired would go a

Re: boot-time accessibility issues

2020-03-02 Thread Steve McIntyre
On Mon, Mar 02, 2020 at 12:24:05PM -0500, Jude DaShiell wrote: >Another possibility could be to have the installer check for a monitor >and if no monitor is connected, turn on a screen reader. That's not a valid assumption necessarily - what about on machines where a serial console is the default

Re: boot-time accessibility issues

2020-03-02 Thread Jude DaShiell
n-accessibil...@lists.debian.org > Subject: Re: boot-time accessibility issues > Resent-Date: Mon, 2 Mar 2020 16:26:05 + (UTC) > Resent-From: debian-accessibil...@lists.debian.org > > On 3/2/2020 5:13 PM, Samuel Thibault wrote: > > john doe, le lun. 02 mars 2020 17:02:49 +0100, a ec

Re: boot-time accessibility issues

2020-03-02 Thread Mewtamer
I know this should probably be discussed on the Official Raspberry Foundation mailing list if such a thing exists, but a few thoughts: 1. At present, Raspbian enables ssh by creating a blank file called ssh in the boot partition and then booting the card. Could a similar method be used for enablin

Re: boot-time accessibility issues

2020-03-02 Thread Samuel Thibault
Mewtamer, le lun. 02 mars 2020 16:36:02 +, a ecrit: > 1. At present, Raspbian enables ssh by creating a blank file called > ssh in the boot partition and then booting the card. Could a similar > method be used for enabling accessibility? Probably. The details are probably to be seen with them

Re: boot-time accessibility issues

2020-03-02 Thread Jude DaShiell
s.debian.org > Subject: Re: boot-time accessibility issues > Resent-Date: Mon, 2 Mar 2020 15:57:33 + (UTC) > Resent-From: debian-accessibil...@lists.debian.org > > Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit: > > In another forum, I've been told tha

Re: boot-time accessibility issues

2020-03-02 Thread Samuel Thibault
john doe, le lun. 02 mars 2020 17:24:48 +0100, a ecrit: > On 3/2/2020 5:13 PM, Samuel Thibault wrote: > > john doe, le lun. 02 mars 2020 17:02:49 +0100, a ecrit: > >> Prompting the user with a question asking if accessibility is desired > >> would go a lon way. > > > > But we don't necessarily want

Re: boot-time accessibility issues

2020-03-02 Thread john doe
On 3/2/2020 5:13 PM, Samuel Thibault wrote: > john doe, le lun. 02 mars 2020 17:02:49 +0100, a ecrit: >> Prompting the user with a question asking if accessibility is desired >> would go a lon way. > > But we don't necessarily want to ask the question on all Debian systems > at all boot. > > I'm no

Re: boot-time accessibility issues

2020-03-02 Thread Samuel Thibault
john doe, le lun. 02 mars 2020 17:02:49 +0100, a ecrit: > Prompting the user with a question asking if accessibility is desired > would go a lon way. But we don't necessarily want to ask the question on all Debian systems at all boot. I'm not saying that there is no solution. I'm saying that it's

Re: boot-time accessibility issues

2020-03-02 Thread Samuel Thibault
Jude DaShiell, le lun. 02 mars 2020 11:03:28 -0500, a ecrit: > Apple solved this problem back in 2006. On the desktop, yes. Here we are talking about an embedded device. > That was when Mac OS Tiger 10.4 > became available. What Apple did was to put a message asking for > language to be used on

Re: boot-time accessibility issues

2020-03-02 Thread john doe
On 3/2/2020 4:57 PM, Samuel Thibault wrote: > Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit: >> In another forum, I've been told that Orca is a rather heavyweight solution >> for providing boot-time speech generation. It was recommended that I >> consider Fenrir, instead. > > Fenrir i

Re: boot-time accessibility issues

2020-03-02 Thread Samuel Thibault
Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit: > In another forum, I've been told that Orca is a rather heavyweight solution > for providing boot-time speech generation. It was recommended that I > consider Fenrir, instead. Fenrir is also quite heavy-weight, since it brings python. B

Re: boot-time accessibility issues

2020-03-02 Thread Rich Morin
In another forum, I've been told that Orca is a rather heavyweight solution for providing boot-time speech generation. It was recommended that I consider Fenrir, instead. So, recasting my question, what would it take to make these changes to the default Debian installation? - include Fenrir,

Re: boot-time accessibility issues

2020-03-01 Thread Samuel Thibault
Hello, Cyril Brulebois, le dim. 01 mars 2020 18:15:58 +0100, a ecrit: > Rich Morin (2020-02-29): > > As I understand it, Orca is generally installed as a dependency of a > > desktop. This makes me wonder whether a server system would (or > > should) have it. This isn't an idle question: Ubuntu

Re: boot-time accessibility issues

2020-03-01 Thread Cyril Brulebois
Hi Rich, Rich Morin (2020-02-29): > At Samuel Thibault's suggestion, I'm bringing some boot-time > accessibility issues to this list. Please excuse any naivete on my > part; I'm not an expert on many of these topics. Fine questions, don't worry. And adding -accessibility instead of just Samuel

Re: Boot Order

2018-02-28 Thread Dan Norton
On Wed, 28 Feb 2018 11:41:30 -0500 lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote: > On Tue, Feb 27, 2018 at 09:01:18PM -0500, Dan Norton wrote: > > Why insert itself anywhere in the first place? The machine booted > > before the installation. To start installing, the installation > > mediu

Re: Boot Order

2018-02-28 Thread Lennart Sorensen
On Tue, Feb 27, 2018 at 09:01:18PM -0500, Dan Norton wrote: > Why insert itself anywhere in the first place? The machine booted > before the installation. To start installing, the installation medium > is placed in a CD drive or USB port and the machine is rebooted. During > installation, other OSs

Re: Boot Order

2018-02-28 Thread Ian Campbell
On Wed, 2018-02-28 at 02:16 +, Steve McIntyre wrote: > On Tue, Feb 27, 2018 at 09:01:18PM -0500, Dan Norton wrote: > > On Mon, 26 Feb 2018 10:40:20 -0500 > > lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote: > > > > > > With UEFI, adding an entry to the boot meny is what you do when > > >

Re: Boot Order

2018-02-27 Thread Steve McIntyre
On Tue, Feb 27, 2018 at 09:01:18PM -0500, Dan Norton wrote: >On Mon, 26 Feb 2018 10:40:20 -0500 >lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote: >> >> With UEFI, adding an entry to the boot meny is what you do when you >> install an OS you want to be able to boot. UEFI does not rely on the

Re: Boot Order

2018-02-27 Thread Dan Norton
On Mon, 26 Feb 2018 10:40:20 -0500 lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote: > On Fri, Feb 23, 2018 at 10:18:00PM -0500, Dan Norton wrote: > > Installing either stretch or buster via netinst results in changes > > to the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is >

Re: Boot Order

2018-02-27 Thread Lennart Sorensen
On Mon, Feb 26, 2018 at 05:42:36PM -0500, Dan Norton wrote: > I would hate to have to do something because windows does it :-) > > No one's yet mentioned secure boot as a justification. AIUI some > manufacturers are making it so that you can't even disable secure boot. > How will you multi-boot li

Re: Boot Order

2018-02-26 Thread Geert Stappers
On Mon, Feb 26, 2018 at 05:42:36PM -0500, Dan Norton wrote: > No one's yet mentioned secure boot as a justification. AIUI some > manufacturers are making it so that you can't even disable secure boot. > How will you multi-boot linux and windows, or replace windows entirely > with such a machine? T

Re: Boot Order

2018-02-26 Thread Dan Norton
On Mon, 26 Feb 2018 10:40:20 -0500 lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote: > On Fri, Feb 23, 2018 at 10:18:00PM -0500, Dan Norton wrote: > > Installing either stretch or buster via netinst results in changes > > to the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is >

Re: Boot Order

2018-02-26 Thread Dan Norton
On Mon, 26 Feb 2018 16:54:22 + Steve McIntyre wrote: > It seems Dan Norton has decided to selfishly make *his* spam problem > into everybody else's spam problem, and I've just had a bounce message > in response to my mail below, saying I have to ask to be added to his > list of allowed sender

Re: Boot Order

2018-02-26 Thread Ian Campbell
On Mon, 2018-02-26 at 16:54 +, Steve McIntyre wrote: > It seems Dan Norton has decided to selfishly make *his* spam problem > into everybody else's spam problem, and I've just had a bounce > message > in response to my mail below, saying I have to ask to be added to his > list of allowed sender

Re: Boot Order

2018-02-26 Thread Steve McIntyre
It seems Dan Norton has decided to selfishly make *his* spam problem into everybody else's spam problem, and I've just had a bounce message in response to my mail below, saying I have to ask to be added to his list of allowed senders. I refuse to pander to this - I guess he will have to do without

Re: Boot Order

2018-02-26 Thread Steve McIntyre
On Sat, Feb 24, 2018 at 02:59:44PM -0500, Dan Norton wrote: > >After installing stretch, it changed to: > >UEFI Boot Sources > debian > ATAPI CD/DVD Drive > USB Floppy/CD > USB Hard Drive >Legacy Boot Sources > [...] > >If done by firmware, wouldn't grub or the installer have to tell >the firm

Re: Boot Order

2018-02-26 Thread Steve McIntyre
On Mon, Feb 26, 2018 at 10:40:20AM -0500, Lennart Sorensen wrote: >On Fri, Feb 23, 2018 at 10:18:00PM -0500, Dan Norton wrote: >> Installing either stretch or buster via netinst results in changes to >> the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is >> replaced with "debian" and

Re: Boot Order

2018-02-26 Thread Lennart Sorensen
On Fri, Feb 23, 2018 at 10:18:00PM -0500, Dan Norton wrote: > Installing either stretch or buster via netinst results in changes to > the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is > replaced with "debian" and this entry is put first in the boot order. > > The PC is: > Hewlett-P

Re: Boot Order

2018-02-26 Thread Ian Campbell
On Sun, 2018-02-25 at 17:03 -0500, Dan Norton wrote: > On Sat, 24 Feb 2018 14:59:44 -0500 > Dan Norton wrote: > > > On Sat, 24 Feb 2018 18:37:02 +0100 > > Ben Hutchings wrote: > > > > > On Fri, 2018-02-23 at 22:18 -0500, Dan Norton wrote: > > > > Installing either stretch or buster via netins

Re: Boot Order

2018-02-25 Thread Dan Norton
On Sat, 24 Feb 2018 14:59:44 -0500 Dan Norton wrote: > On Sat, 24 Feb 2018 18:37:02 +0100 > Ben Hutchings wrote: > > > On Fri, 2018-02-23 at 22:18 -0500, Dan Norton wrote: > > > Installing either stretch or buster via netinst results in changes > > > to the bios menu. Under "UEFI Boot Sources

Re: Boot Order

2018-02-25 Thread Richard Owlett
On 02/25/2018 02:35 AM, Ian Campbell wrote: On Sat, 2018-02-24 at 14:18 -0600, Richard Owlett wrote: On 02/24/2018 01:59 PM, Dan Norton wrote: [snip] In my case, there are multiple debian installations and the installer positions the last installation at the top of the *grub* menu. This make

Re: Boot Order

2018-02-25 Thread Ian Campbell
On Sat, 2018-02-24 at 14:18 -0600, Richard Owlett wrote: > On 02/24/2018 01:59 PM, Dan Norton wrote: > > [snip] > > > > In my case, there are multiple debian installations and the > installer > > positions the last installation at the top of the *grub* menu. This > > makes sense. > > Not always.

Re: Boot Order

2018-02-24 Thread Richard Owlett
On 02/24/2018 06:49 PM, Dan Norton wrote: On Sat, 24 Feb 2018 14:18:13 -0600 Richard Owlett wrote: On 02/24/2018 01:59 PM, Dan Norton wrote: [snip] In my case, there are multiple debian installations and the installer positions the last installation at the top of the *grub* menu. This makes

Re: Boot Order

2018-02-24 Thread Dan Norton
On Sat, 24 Feb 2018 14:18:13 -0600 Richard Owlett wrote: > On 02/24/2018 01:59 PM, Dan Norton wrote: > > [snip] > > > > In my case, there are multiple debian installations and the > > installer positions the last installation at the top of the *grub* > > menu. This makes sense. > > Not always

Re: Boot Order

2018-02-24 Thread Richard Owlett
On 02/24/2018 01:59 PM, Dan Norton wrote: [snip] In my case, there are multiple debian installations and the installer positions the last installation at the top of the *grub* menu. This makes sense. Not always. I'm continually doing installs, tweaking them in one way or another. The last ins

Re: Boot Order

2018-02-24 Thread Dan Norton
On Sat, 24 Feb 2018 18:37:02 +0100 Ben Hutchings wrote: > On Fri, 2018-02-23 at 22:18 -0500, Dan Norton wrote: > > Installing either stretch or buster via netinst results in changes > > to the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is > > replaced with "debian" and this entry

Re: Boot Order

2018-02-24 Thread Ben Hutchings
On Fri, 2018-02-23 at 22:18 -0500, Dan Norton wrote: > Installing either stretch or buster via netinst results in changes to > the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is > replaced with "debian" and this entry is put first in the boot order. > > The PC is: > Hewlett-Packard

Re: Boot Order

2018-02-23 Thread Geert Stappers
On Fri, Feb 23, 2018 at 10:18:00PM -0500, Dan Norton wrote: > Installing either stretch or buster via netinst results in changes to > the bios menu. Under "UEFI Boot Sources" the term "Hard Drive" is > replaced with "debian" and this entry is put first in the boot order. > > The PC is: > Hewlett-P

Re: Boot broken on latest debian iso's?

2013-04-18 Thread Didier 'OdyX' Raboud
Le jeudi, 18 avril 2013 09.01:21, Godwin Monis a écrit : > Hi, > > I have downloaded the latest debian squeeze 6.0.7 DVD iso's from > http://cdimage.debian.org/debian-cd/6.0.7/ia64/iso-dvd/. After downloading > the ISO's I checked the md5 for debian-6.0.7-ia64-DVD-1.iso. This md5sum > (7fb1cb78f8d

Re: boot parameter libata.force=1.5Gbps not recognized

2012-10-08 Thread Selim T. Erdogan
Selim T. Erdogan, 3.10.2012: > > Adding "libata.force=1.5Gbps" to the boot parameters for the installer > doesn't work. It leads to a message saying "unknown parameter 5Gbps". > (Trying 3.0Gbps leads to "unknown parameter 0Gbps" so it looks like it > could be a parsing issue.) > > Details: >

Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2012-08-04 Thread Jonathan Nieder
Hi Miguel, Miguel Figueiredo wrote: > i would like to see this tested in with daily images, expert mode > using sid to see if the updated grub makes any difference. > Can you test it and give feedback? What change was made in grub? If it is one that directly addressed the problem described here

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-14 Thread Qin Bo
2010/12/13 Jon Ander Ortiz > I've suffered the same issue in some netcards (nexcom and portwell HW). > The usleep of netcfg.c is not enought to up the interface and detect the > link up in auto mode (buggy driver or buggy hardware?? :-/). > > In my case the sleep goes to some seconds (4-5 secs.).

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-13 Thread Lennart Sorensen
On Mon, Dec 13, 2010 at 11:15:46AM +0800, Qin Bo wrote: > How can i find the bnx2 problem? I had set netcfg/dhcp_timeout=60 as boot > parameter, the problem still reproduce. > But I still think the netcfg didn't got the correct interface, then couldn't > get the IP address from dhcp server. > Beca

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-13 Thread Jon Ander Ortiz
I've suffered the same issue in some netcards (nexcom and portwell HW). The usleep of netcfg.c is not enought to up the interface and detect the link up in auto mode (buggy driver or buggy hardware?? :-/). In my case the sleep goes to some seconds (4-5 secs.). BR 2010/12/13 Floris Bos > Hi, >

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-12 Thread Floris Bos
Hi, On Monday, December 13, 2010 04:15:46 am Qin Bo wrote: > 2010/12/10 Lennart Sorensen > > > Is this another case of a driver/NIC taking longer to get link up after > > being enabled than the installer is willing to wait? I seem to recall > > a bnx2 user a few days ago reporting a similar pro

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-12 Thread Qin Bo
2010/12/10 Lennart Sorensen > > > Is this another case of a driver/NIC taking longer to get link up after > being enabled than the installer is willing to wait? I seem to recall > a bnx2 user a few days ago reporting a similar problem. > > How can i find the bnx2 problem? I had set netcfg/dhcp_t

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-10 Thread Ferenc Wagner
lsore...@csclub.uwaterloo.ca (Lennart Sorensen) writes: > On Fri, Dec 10, 2010 at 05:45:30PM +0800, Qin Bo wrote: >> Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is disconnected. (MII) >> Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is not a wireless interface. >> Continuing. >> Dec 10 10:49:14 netcfg[391

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-10 Thread Lennart Sorensen
On Fri, Dec 10, 2010 at 05:45:30PM +0800, Qin Bo wrote: > Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is disconnected. (MII) > Dec 10 10:49:14 netcfg[3916]: INFO: eth0 is not a wireless interface. > Continuing. > Dec 10 10:49:14 netcfg[3916]: INFO: eth1 is disconnected. (MII) > Dec 10 10:49:14 netcfg[

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-10 Thread Qin Bo
2010/12/10 Christian PERRIER > Quoting Qin Bo (kinbos...@gmail.com): > > hi all: > >I use squeeze Nov 6 build iso to install, i had three network > > interface card, a onboard NIC and two stand alone NIC is intel e1000, > >and e1000 1st(eth1) is plug a cable, e1000 2nd(eth2) and >

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-10 Thread Christian PERRIER
Quoting Qin Bo (kinbos...@gmail.com): > hi all: >I use squeeze Nov 6 build iso to install, i had three network > interface card, a onboard NIC and two stand alone NIC is intel e1000, >and e1000 1st(eth1) is plug a cable, e1000 2nd(eth2) and > onboard(eth0) is not, i want to auto con

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-29 Thread Lukasz Szybalski
On Fri, Oct 29, 2010 at 12:01 PM, Lennart Sorensen wrote: > On Fri, Oct 29, 2010 at 11:08:59AM -0500, Lukasz Szybalski wrote: >> It seems like Grub.cfg is also using proper drive by UUID. >> >> menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian >> --class gnu-linux --class gnu

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-29 Thread Lennart Sorensen
On Fri, Oct 29, 2010 at 11:08:59AM -0500, Lukasz Szybalski wrote: > It seems like Grub.cfg is also using proper drive by UUID. > > menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian > --class gnu-linux --class gnu --class os { > insmod part_msdos > insmod ext2 >

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-29 Thread Lukasz Szybalski
It seems like Grub.cfg is also using proper drive by UUID. menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os { insmod part_msdos insmod ext2 set root='(hd0,msdos5)' search --no-floppy --fs-uuid --set dec7

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-29 Thread Lukasz Szybalski
What I don't understand is that in squezze the fstab shows: /etc/fstab # /boot was on /dev/sda5 during installation UUID=dec79ed9-b96a-47e4-81f0-7e32735b5057 /boot ext2 defaults0 2 # /boot2 was on /dev/sdb1 during installation UUID=bb0512c5-6de6-4164-a7af-4312a4718ce3 /boo

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-28 Thread Lukasz Szybalski
On Thu, Oct 28, 2010 at 7:41 PM, Samuel Thibault wrote: > Lukasz Szybalski, le Thu 28 Oct 2010 19:31:51 -0500, a écrit : >> There was no changes to the bios system. The system was installed then >> rebooted. > > Ok. > It may just be a difference between the order in which modules get > loaded fro

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-28 Thread Samuel Thibault
Lukasz Szybalski, le Thu 28 Oct 2010 19:31:51 -0500, a écrit : > There was no changes to the bios system. The system was installed then > rebooted. Ok. It may just be a difference between the order in which modules get loaded from initrd at reboot and modules get loaded by d-i. But in principle f

Re: Bug#601721: installation-reports: Build w/ /boot partition succeeds, but re-boot fails in fsck 445148

2010-10-28 Thread Samuel Thibault
Lukasz Szybalski, le Thu 28 Oct 2010 17:39:59 -0500, a écrit : > 3. Can someone explain why installer mounts sda as my 1GB and sdb as > 1.7TB, but after re-boot system swaps them and uses 1.7TB as /sda and > 1Gb as sdb? It looks like a hardware detection order issue. Do you modi

Re: boot problem after installation - device names changed

2010-05-13 Thread Martin Minka
Hello Martin, does it mean I should follow your installation instruction and choose expert mode installer and choose debian version squeeze ? Will that work ? Thank you for you repeating help. On 13. 5. 2010 15:16, Martin Michlmayr wrote: * Martin Minka [2010-05-13 14:37]: Unfortunately

Re: boot problem after installation - device names changed

2010-05-13 Thread Martin Michlmayr
* Martin Minka [2010-05-13 15:27]: > does it mean I should follow your installation instruction and choose > expert mode installer and choose debian version squeeze ? > Will that work ? No, the lenny installer won't do UUIDs. You have to use the squeeze installer: http://ftp.fr.debian.org/debian

Re: boot problem after installation - device names changed

2010-05-13 Thread Martin Michlmayr
* Martin Minka [2010-05-13 14:37]: > Unfortunately I don't see the UBoot output, but when I try boot with > rescue image or start installation again I see the the /dev/sda1 is > swap and not /boot, so the order of disks changed. > > Is this change of disk order the problem why system is not booti

Re: Boot problem in squeeze, hang after Booting the kernel

2010-02-15 Thread Lars Segerlund
Part of the problem found ! I can now get console ouptup from 2.6.32 in the same way as 2.6.30-8 ... the thing is that I found some bad RAM. However the last thing I see is unpacking initrd something After that it dies in the kernel, ( I have the debug flag on ) ... it ends up in the ke

Re: Boot problem in squeeze, hang after Booting the kernel

2010-02-15 Thread Lars Segerlund
I tried the 2.6.30 kernel you suggested, now it tries to boot, but I get a kernel panik after trying to mount the root. I cannot make out too much but I have console output which I do not have with the regular 2.6.32 kernel. I suspect they hang at the same place though, with the difference of th

Re: Boot problem in squeeze, hang after Booting the kernel

2010-02-14 Thread Lars Segerlund
Should I create a bug & bugreport ? I was not sure until I checked with the list ? regards, Lars Segerlund On Feb 14, 2010 7:40 p.m., "Frans Pop" wrote: On Friday 12 February 2010, Lars Segerlund wrote: > I have a Sony Vaio TX3 ( VGN-TX3XT ) , which ru... So the installer boots and works corre

Re: Boot problem in squeeze, hang after Booting the kernel

2010-02-14 Thread Lars Segerlund
Hello and thanks, I will install 2.6.30 from stable tonight, I have tried 2.6.30 from squeeze both 486 & 686 ... none boots. I tried debian live ( standard ) yesterday with a 2.6.26 and it boots fine. I have alredy removed the 'quiet' option it still stops at "Booting the kernel" , I think I hav

Re: Boot problem in squeeze, hang after Booting the kernel

2010-02-14 Thread Frans Pop
On Friday 12 February 2010, Lars Segerlund wrote: > I have a Sony Vaio TX3 ( VGN-TX3XT ) , which runs a on an intel > celeron ULW, and has a i945g graphics chip. > > I have reinstalled with the squeeze install cd, but cannot boot the > kernels on the machine. So the installer boots and works cor

Re: Boot d-i and install Debian in the same HD

2009-03-18 Thread MaTa
Good idea. I will try. Thanks for all :D 2009/3/18 Otavio Salvador : > On Wed, Mar 18, 2009 at 12:00 PM, MaTa wrote: >> 2009/3/18, Otavio Salvador : >>> MaTa writes: >>>  But this doesn't document every module but how they "integrate" into the >>>  installer. >>> >>>  You'll need to look at mod

Re: Boot d-i and install Debian in the same HD

2009-03-18 Thread Otavio Salvador
On Wed, Mar 18, 2009 at 12:00 PM, MaTa wrote: > 2009/3/18, Otavio Salvador : >> MaTa writes: >>  But this doesn't document every module but how they "integrate" into the >>  installer. >> >>  You'll need to look at module package description and source to get a >>  better view of what each does.

Re: Boot d-i and install Debian in the same HD

2009-03-18 Thread MaTa
2009/3/18, Otavio Salvador : > MaTa writes: > > > My tests for now I get a error if I execute a preconfigured (with > > preseed.cfg and recipe files) file. > > > > 2009/3/18 Otavio Salvador : > >> On Tue, Mar 17, 2009 at 6:36 PM, MaTa > wrote: > > > [...] > > > >>> How I can modify the ude

Re: Boot d-i and install Debian in the same HD

2009-03-18 Thread Otavio Salvador
MaTa writes: > My tests for now I get a error if I execute a preconfigured (with > preseed.cfg and recipe files) file. > > 2009/3/18 Otavio Salvador : >> On Tue, Mar 17, 2009 at 6:36 PM, MaTa wrote: [...] >>> How I can modify the udebs needed to complete the installation? >> >> What kind of mo

Re: Boot d-i and install Debian in the same HD

2009-03-18 Thread MaTa
My tests for now I get a error if I execute a preconfigured (with preseed.cfg and recipe files) file. 2009/3/18 Otavio Salvador : > On Tue, Mar 17, 2009 at 6:36 PM, MaTa wrote: >> Hi >> >> I'm Oriol Matavacas, a Computer Systems Degree Student. First, Sorry >> for my English, I'm from Barcelona.

Re: Boot d-i and install Debian in the same HD

2009-03-17 Thread Otavio Salvador
On Tue, Mar 17, 2009 at 6:36 PM, MaTa wrote: > Hi > > I'm Oriol Matavacas, a Computer Systems Degree Student. First, Sorry > for my English, I'm from Barcelona. > > I'm testing a new type of installation. Please I need your help. > Can I boot the Debian installer images (through GRUB + initrd.gz,

Re: Boot parameter and blacklisting

2009-03-12 Thread Fabien Boucher
On Wed, 11 Mar 2009 13:43:21 +0100 Frans Pop wrote: > On Wednesday 11 March 2009, Fabien Boucher wrote: > > The entry is correctly add in /etc/modprobe/blacklist.local but the > > module is loaded ... > > > > So it seems that udev doesn't take care of > > /etc/modprobe/blacklist.local. > > I tes

Re: Boot parameter and blacklisting

2009-03-11 Thread Frans Pop
On Wednesday 11 March 2009, Fabien Boucher wrote: > The entry is correctly add in /etc/modprobe/blacklist.local but the > module is loaded ... > > So it seems that udev doesn't take care of > /etc/modprobe/blacklist.local. I tested this a few days ago in VirtualBox for the pcnet32 driver and the

Re: Boot parameter and blacklisting

2009-03-11 Thread Fabien Boucher
On Wed, 18 Feb 2009 22:22:12 +0100 Arnaud wrote: > > Hi, > > first, Congratulations on the recent release of Debian Lenny. :) > > i'm trying to boot in pxe with this parameter > > LABEL 2 >kernel linux-20090216 > append auto DEBCONF_PRIORITY=critical DEBIAN_FRONTEND=text > locale=en_U

Bug#456154: marked as done (debian-installer: amd64 re-boot fails due to missing /etc/crypttab)

2008-08-05 Thread Debian Bug Tracking System
Your message dated Tue, 05 Aug 2008 17:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#393728: fixed in partman-md 42 has caused the Debian Bug report #393728, regarding debian-installer: amd64 re-boot fails due to missing /etc/crypttab to be marked as done. This mean

Bug#486168: Lenny Beta2 Kernel Panic - fails to re-boot on HP Netserver E60

2008-06-17 Thread Frans Pop
reassign 486168 linux-2.6 2.6.24-7 thanks On Friday 13 June 2008, Chris Bell wrote: > Comments/Problems: > On re-boot the A channel is identified, but kernel panic while checking > the B channel. > > scsi 0 : adaptec AIC 7xxx EISA/VLB/PCI SCSI HBA Driver, Rev 7.0 >

Processed: Re: Bug#486168: Lenny Beta2 Kernel Panic - fails to re-boot on HP Netserver E60

2008-06-17 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 486168 linux-2.6 2.6.24-7 Bug#486168: Lenny Beta2 Kernel Panic - fails to re-boot on HP Netserver E60 Bug reassigned from package `installation-reports' to `linux-2.6'. > thanks Stopping processing here. Please contac

Bug#486168: Lenny Beta2 Kernel Panic - fails to re-boot on HP Netserver E60

2008-06-13 Thread Chris Bell
t set to default configuration, but Knoppix 5.1.1 CD reports that it is BIOS disabled, and simply assumes the default parameters. On re-boot the A channel is identified, but kernel panic while checking the B channel scsi 0 : adaptec AIC 7xxx EISA/VLB/PCI SCSI HBA Driver, Re

  1   2   3   4   5   6   >