t the firmware available to the module before it performed hardware
detection, because otherwise the installer hangs.
Perhaps that information is useful to you to understand the problem?
Perhaps it is useful to other users who encounter this bug.
I'm not trying to tell you what the fix is, I&#
Jamie Wilkinson (2023-03-07):
> I think I've figured out why we see these errors.
I don't think you did.
> So I think the problem here is that the firmware udebs are not
> unpacked before hardware detection starts.
Those are firmware debs, not firmware udebs. And no, they sh
firmware udebs are not
unpacked before hardware detection starts.
Your message dated Mon, 04 May 2015 01:35:21 +0100
with message-id <1430699721.4113.129.ca...@decadent.org.uk>
and subject line Re: installation report: IBM Thinkpad X23
has caused the Debian Bug report #230552,
regarding should explain that discover and hotplug are used for hardware
detect
Your message dated Mon, 28 Feb 2011 23:46:40 +
with message-id <201102282346.40342.el...@debianpt.org>
and subject line
has caused the Debian Bug report #200467,
regarding debian-installer: Hardware detection should not fail when all
required modules are included in kernel
to be mar
Processing commands for cont...@bugs.debian.org:
> reassign 607906 linux-2.6
Bug #607906 [debian-installer] debian-installer: oops and panic after hardware
detection
Bug reassigned from package 'debian-installer' to 'linux-2.6'.
> thanks
Stopping processing here.
Ple
reassign 607906 linux-2.6
thanks
I reproduced the panic with the daily installer (first attachment). By
stopping before disk-detect and using a shell I could narrow this down
to the "modprobe mptspi" command (second attachment). It takes quite
some time to hit the BUG, which is then sooner or la
Package: debian-installer
Version: squeeze beta2 netinst started from HDD by grub
Severity: normal
Hi,
On an IBM x345 I reliably get a longish hang during
"Detecting disks and all other hardware", then a BUG and a resulting
panic. The BUG isn't always the same, as the two attached console
logs s
Your message dated Fri, 10 Sep 2010 17:49:11 +
with message-id
and subject line Closing oldbug report against debian-installer #542448
has caused the Debian Bug report #542448,
regarding debian-installer: stops during boot on usb/scsi hardware detection
to be marked as done.
This means that
Your message dated Wed, 08 Sep 2010 03:58:36 +
with message-id
and subject line Closing old installation report #248075
has caused the Debian Bug report #248075,
regarding [i386] [unknown] [netinst] hardware detection problems
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 08 Sep 2010 03:58:34 +
with message-id
and subject line Closing old installation report #243233
has caused the Debian Bug report #243233,
regarding [i386] [20040408] [CD] hardware detection issues, partman comments,
more
to be marked as done.
This means that you
Your message dated Wed, 08 Sep 2010 03:57:32 +
with message-id
and subject line Closing old installation report #416455
has caused the Debian Bug report #416455,
regarding installation: Debian Etch NETINST has broken hardware detection
to be marked as done.
This means that you claim that the
Your message dated Wed, 08 Sep 2010 03:57:51 +
with message-id
and subject line Closing old installation report #287610
has caused the Debian Bug report #287610,
regarding Installation failed at hardware detection (module ide-disk hangs
system)
to be marked as done.
This means that you
Package: debian-installer
Severity: critical
Tags: patch
Justification: breaks the whole system
Machine: Dell D630
Processor: T7300
Memory: 4GB
During boot of the installer, it hangs when showing:
usb 7-1.2: O2Micro CCID SC Reader
usb 7-1.2: Manufacturer: O2
usb 7-1.2: configuration #1 chosen f
Hello,
I can't install or boot debian lenny on a laptop I'm using.
The installer hangs on initial hardware detection it just hangs when it
loads sdhci module when detecting mmc0 (card reader).
I installed lenny on another pc copied the files on this averatec laptop
still the init
On Mon, Aug 06, 2007 at 06:39:06PM +0200, Petter Reinholdtsen wrote:
> Today I made a small step further on my plan for better hardware
> support in Debian. I added support in discover version 2.1.2-1 for
> calling module-assistant in discover-pkginstall, and fixed a few
> long-standing bugs in th
[Jérémy Bobbio]
> Will that work for madwifi (Wi-Fi cards based on the Atheros
> chipset)?
If there are source packages with this driver in Debian, and someone
get the required information into discover-data, yes.
> On a closely related matter, could your infrastructure install
> bcm43xx-fwcutte
On Mon, Aug 06, 2007 at 06:39:06PM +0200, Petter Reinholdtsen wrote:
> Today I made a small step further on my plan for better hardware
> support in Debian. I added support in discover version 2.1.2-1 for
> calling module-assistant in discover-pkginstall, and fixed a few
> long-standing bugs in th
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Otavio Salvador]
>> Can you please elaborate a little more how do you intend to do that?
>> I personally wouldn't like to have my system with gcc and like,
>> needed to build the module, so would be nice if we might purge those
>> packages after b
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> [Otavio Salvador]
>> I think it can be improved. Let me explain my idea:
>>
>> If we build the module that we want to add on the database and write a
>> small script that uses modules.alias file updated with it we can write
>> the database will ful
[Otavio Salvador]
> I think it can be improved. Let me explain my idea:
>
> If we build the module that we want to add on the database and write a
> small script that uses modules.alias file updated with it we can write
> the database will full module knownledge available. This would all
> make po
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> Not very many kernel module source packages are recognized by the
> discover-data package at the moment. Two devices using the
> qla2x00-source package is all there is at the moment. The problem
> with maintaining the mapping from hardware to deb
Today I made a small step further on my plan for better hardware
support in Debian. I added support in discover version 2.1.2-1 for
calling module-assistant in discover-pkginstall, and fixed a few
long-standing bugs in the debconf handling in that script.
With this change in place, calling disco
> I suspect the discover v2 package might be a good base to implement
> this, as it already support mapping from various hardware types to
> kernel module, X driver and Debian package. The missing parts are
AIUI the X Strikeforce plans to stop using discover for hardware detection
someti
[Geert Stappers]
> That automatic build of driver source into kernel module,
> how automatic will that be?
>
> What will the effect on the boot time?
Not sure. I see two options, to make sure the kernel modules are
still available:
- compile the source with the new kernel when the new kernel is
Op 21-04-2007 om 12:56 schreef Petter Reinholdtsen:
>
> During installation, and afterwards, there are a few things that could
> be improved regarding hardware detection. Here are some ideas I have
> on the topic.
This comment is only on one idea.
> Third, some hardware is supp
Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
[...]
> Hardware (PCI, DMI, CPU, USB, etc) mapped do one or more of
> - Kernel module name
> - X driver name
About X driver would be nice to have fallback options. For example, if
the user has the non-free driver for nvidia this should be
During installation, and afterwards, there are a few things that could
be improved regarding hardware detection. Here are some ideas I have
on the topic.
At the moment, we have a system in place to load kernel modules
depending on the PCI (and USB) hardware detected during installation
and boot
Op 13-04-2007 om 08:31 schreef Renato S. Yamane:
> Hi Geert,
> I found another bug report about "CD ROM / HD not recognized" in Debian 4.0:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418972
With this message to both bugreports are they crosslinked
http://bugs.debian.org/cgi-bin/bugreport.c
On Wed, 29 Dec 2004 20:05:20 +1100, Janeene Webb <[EMAIL PROTECTED]>
wrote:
>The machine cannot boot from CD, so cannot try the CD installers.
Smart Boot Manager (http://btmgr.sourceforge.net/) can be started from
floppy and allows some older computers to boot from CD. That's how I
loaded my fire
On Wed, 2004-12-29 at 08:43 +0100, Christian Perrier wrote:
> Quoting Janeene Webb ([EMAIL PROTECTED]):
>
> > Installation progresses to the point of loading the module ide-disk, and
> > then
> > consistently hangs/hard locks. No keyboard, no error message if load by
> > 'modprobe -v ide-disk'
Quoting Janeene Webb ([EMAIL PROTECTED]):
> Installation progresses to the point of loading the module ide-disk, and then
> consistently hangs/hard locks. No keyboard, no error message if load by
> 'modprobe -v ide-disk'
> on a console in medium/expert install, no difference when passing ide=nodm
Package: installation-reports
Debian-installer-version: tried rc2 and "current" floppy images,
and netboot 2.4 and 2.6 rc2 images.
uname -a:
Date: 28th/29th Dec, 2004
Method: Machine doesn't boot from CD, so tried both floppy and netboot
from hd as per section 5.
[EMAIL PROTECTED] (Geert Stappers) writes:
> On Wed, Dec 22, 2004 at 09:55:01PM +0100, Felix Natter wrote:
>
>> This is the output of lspci:
>
>> :00:0e.0 Network controller: AVM Audiovisuelles MKTG & Computer System
>> GmbH A1 ISDN [Fritz] (rev 02)
>
> And what is the output of
>
>
On Wed, Dec 22, 2004 at 09:55:01PM +0100, Felix Natter wrote:
> This is the output of lspci:
> :00:0e.0 Network controller: AVM Audiovisuelles MKTG & Computer System
> GmbH A1 ISDN [Fritz] (rev 02)
And what is the output of
( lspci ; lspci -n ) | grep :00:0e.0
?
/me
signat
On Wednesday 22 December 2004 21:55, Felix Natter wrote:
> Although this seems right when looking at "make menuconfig" in a 2.6
> kernel (it says "AVM Fritz!Card PCI/PCIv2/PnP support (EXPERIMENTAL)"),
> it will not work with my card. I had to use only the hisax module with
> the parameters (type=2
Package: debian-installer
Version: 1.2?? (from Debian GNU/Linux testing _Sarge_ - Official Snapshot i386
Binary-1 (20041211))
d-i loads the hisax_fcpcipnp module for my "AVM Fritzcard PCI" (not "AVM
Fritzcard PCI 2.0"!)
Although this seems right when looking at "make menuconfig" in a 2.6
kernel
Paul Telford wrote:
> On Nov 30, 2004, at 6:50 PM, Joey Hess wrote:
> >
> >It's very wrong on at least my a500, causes a crash with the 2.4 kernel
> >after base install. See bug #282814.
>
> I've seen it I reported it. ;)
283754 rather
> FWIW, CONFIG_DE4X5 does seem to be available in 2.6 s
On Nov 30, 2004, at 6:50 PM, Joey Hess wrote:
It's very wrong on at least my a500, causes a crash with the 2.4 kernel
after base install. See bug #282814.
I've seen it I reported it. ;)
Did the system you installed with 2.6 boot up ok? Was de4x5 loaded by
discover then, or is the module not a
Paul Telford wrote:
> On Tue, 30 Nov 2004, Joey Hess wrote:
>
> > Paul Telford wrote:
> > > :00:14.0 Ethernet controller: Digital Equipment Corporation DECchip
> > > 21142/43 (rev 30)
> > > :00:14.0 0200: 1011:0019 (rev 30)
> >
> > discover1 wants to load de4x5 for this. Is that wrong?
>
On Tue, 30 Nov 2004, Joey Hess wrote:
> Paul Telford wrote:
> > :00:14.0 Ethernet controller: Digital Equipment Corporation DECchip
> > 21142/43 (rev 30)
> > :00:14.0 0200: 1011:0019 (rev 30)
>
> discover1 wants to load de4x5 for this. Is that wrong?
I don't know. I do know that it didn'
Paul Telford wrote:
> :00:14.0 Ethernet controller: Digital Equipment Corporation DECchip
> 21142/43 (rev 30)
> :00:14.0 0200: 1011:0019 (rev 30)
discover1 wants to load de4x5 for this. Is that wrong?
--
see shy jo
signature.asc
Description: Digital signature
On Fri, 26 Nov 2004, Joey Hess wrote:
> AIUI, the 2.4 hppa kernel has almost everything built in, while the 2.6
> kernel is more modular. Proably we're missing an item in discover for
> this card, which I assume is a pci card? Can you send lspci and lspci -n
> output for this machine so we can add
More info on the partitioning problem: I did a manual install and
selected the "all files in one partition" pre-defined recipe. Machine
locked up during filesystem creation of /boot (status bar shows 37% done
if that means anything)
Paul.
--
Paul Telford | 1024D/431B38BA | [EMAIL PROTECTE
Paul Telford wrote:
> Using the mini.iso image retrieved from
> http://people.debian.org/~jbailey/d-i/hppa/daily/2.6/ today, the system
> failed to autodetect my NIC (tulip). This works reliably with the 2.4
> image.
AIUI, the 2.4 hppa kernel has almost everything built in, while the 2.6
kernel i
Package: installation-reports
Severity: normal
Machine is an HP C200 workstation with 128M ram, internal SCSI disk.
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked:[O]
Configure network HW: [E]
Config network:
Your message dated 04 Oct 2004 22:22:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line is this bug fixed?
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 responsibility to re
Bug Tracking System <[EMAIL PROTECTED]>
Subject: boot-floppies: Hardware detection fails to find my disk drive
X-Mailer: reportbug 1.50
Date: Sat, 10 May 2003 22:23:02 +
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-3.8 required=4.0
tests=BA
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 230552 should explain that discover and hotplug are used for hardware
> detection on installed system, and how to turn that off
Bug#230552: installation re
ED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: installation-reports: can't mount the CD after hardware detection
X-Mailer: reportbug 2.62
Date: Tue, 29 Jun 2004 21:58:42 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Sebastien Bacher <[EMAIL PROTECTED]>
, 6 Feb 2004 09:50:04 +0100
Subject: hang at hardware detection. pcmcia related
From: Jerome Lacoste <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature";
boundary="=-dGi1bjEboy
reassign 256374 kernel
retitle 256374 CD problems under 2.6, not under 2.4
thanks
* Robin Blondon <[EMAIL PROTECTED]> [2004-07-01 10:29]:
> I finally got 2.4 to install (with a few PCMCIA/networking snags) and
> was able to upgrade to the kernel package kernel-image-2.6.6-1-386.
> After rebootin
Processing commands for [EMAIL PROTECTED]:
> reassign 256374 kernel
Bug#256374: Installation hangs on Compaq Presario 1220 while loading module 'ide-cd'
during hardware detection for the CD-ROM drive (beta4, i386, linux26)
Bug reassigned from package `installation-report
Martin Michlmayr wrote:
* Robin Blondon <[EMAIL PROTECTED]> [2004-06-26 15:18]:
Do you mean to upgrade the kernel to 2.6 or to try to reinstall Sarge
using the linux26 option?
No, you can simply install the 2.6 kernel package after completing the
installation.
I still need to figure out
Per Olofsson wrote:
On Sun, Jun 27, 2004 at 19:54 -0300, Robin Blondon wrote:
In the installer, I found that instead of ejecting and reinserting the
card I can go into the shell and kill and restart cardmgr. The
intstaller then detected the card after choosing to detect network
hardware from
Package: installation-reports
Version: daily iso, 2004-06-29
Severity: important
Tags: d-i
I've just tried an install with the daily iso (2004-06-29) and no way to mount
the CD after the hardware detection (2.4 or 2.6 kernels).
After the "Detecting hardware" phase I got a :
&q
On Sun, Jun 27, 2004 at 19:54 -0300, Robin Blondon wrote:
> In the installer, I found that instead of ejecting and reinserting the
> card I can go into the shell and kill and restart cardmgr. The
> intstaller then detected the card after choosing to detect network
> hardware from the installer m
Per Olofsson wrote:
On Sat, Jun 26, 2004 at 16:46 -0300, Robin Blondon wrote:
I found in bug #250596, the person had to eject and reinsert his
wireless card for it to be detected. I tried this and it worked. Is the
system supposed to be able to detect the card without needing to
reinsert the
On Sat, Jun 26, 2004 at 16:46 -0300, Robin Blondon wrote:
> I found in bug #250596, the person had to eject and reinsert his
> wireless card for it to be detected. I tried this and it worked. Is the
> system supposed to be able to detect the card without needing to
> reinsert the card?
Yes, you
Per Olofsson wrote:
On Sat, Jun 26, 2004 at 15:18 -0300, Robin Blondon wrote:
I still need to figure out how to complete the installation with 2.4. It
has a PCMCIA wireless LAN card (a Linksys WPC11) that I need to figure
out how to get the installer to recognize.
It should be recognised
On Sat, Jun 26, 2004 at 15:18 -0300, Robin Blondon wrote:
> I still need to figure out how to complete the installation with 2.4. It
> has a PCMCIA wireless LAN card (a Linksys WPC11) that I need to figure
> out how to get the installer to recognize.
It should be recognised automatically. Could
* Robin Blondon <[EMAIL PROTECTED]> [2004-06-26 15:18]:
> Do you mean to upgrade the kernel to 2.6 or to try to reinstall Sarge
> using the linux26 option?
No, you can simply install the 2.6 kernel package after completing the
installation.
> I still need to figure out how to complete the instal
Martin Michlmayr wrote:
* Robin Blondon <[EMAIL PROTECTED]> [2004-06-26 12:47]:
This problem did not appear when trying to install using the Linux 2.4
kernel.
After you've made an installation with 2.4, can you install the 2.6
package and check if you see similar problems?
Do you mean to
* Robin Blondon <[EMAIL PROTECTED]> [2004-06-26 12:47]:
> This problem did not appear when trying to install using the Linux 2.4
> kernel.
After you've made an installation with 2.4, can you install the 2.6
package and check if you see similar problems?
--
Martin Michlmayr
[EMAIL PROTECTED]
--
ernel, the installation
hangs during the hardware detection to find CD-ROM drives. The last
message is
"Loading module 'ide-cd' for 'Linux ATAPI CD-ROM' ...". If I switch to
a console and do a 'dmesg', the last few lines are:
ide-cd: cmd 0x5a timed out
hdc:
On Tue, 2004-05-25 at 12:04, Martin Michlmayr wrote:
> * Jerome Lacoste <[EMAIL PROTECTED]> [2004-02-06 09:50]:
> > System hangs at boot. PCMCIA related
> >
> > Reinstalling system on new disk (other died). I kewn PCMCIA was
> > problematic from my former installation (which I had done from boot
>
* Jerome Lacoste <[EMAIL PROTECTED]> [2004-02-06 09:50]:
> System hangs at boot. PCMCIA related
>
> Reinstalling system on new disk (other died). I kewn PCMCIA was
> problematic from my former installation (which I had done from boot
> floppies). E.g. see
> http://www.trenkamp.org/i8k-installation
id 4E48B1C167D6; Sun, 21 Mar 2004 11:07:45 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Sebastien <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: debian-installer: multiple ha
new, so i
guess it is natural for floppy detection to fail. Nevertheless, i failed
to circumvent the hardware detection mechanism freezing upon ide-floppy
probing on second try.
Finally, i tried knoppix 3.2, which worked fine :-(
--
Sayan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Processing commands for [EMAIL PROTECTED]:
> severity 239172 important
Bug#239172: debian-installer: multiple hardware detection forgets parameters
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
severity 239172 important
thanks
On Sun, Mar 21, 2004 at 11:07:45AM +0100, Sebastien wrote:
> I tried installing debian sarge beta 3 yesterday on a targa Visionary XP-210
> laptop computer with first cd installer and net installer. Both failed
> during ide-floppy modprobing, as can be expected bec
laptop lacks a
floppy drive.
To solve the problem, i tried disabling ide-floppy probing in expert mode.
This time, the installer passed the first hardware detection phase. However,
just before installing base system, the installer probes hardware again, and
freezes upon probing ide-floppy. This
On Wed, Feb 11, 2004 at 03:41:36PM +0100, Nikolai Prokoschenko wrote:
> 1. Something in the installer should automagically install appropriate
>drivers, if a "proprietary" video card is detected. A good approach
>found to the archives newly in form of nvidia-kernel-2.4.24-1-*
>packages.
Hello!
A friend of mine approached me a couple of days ago and asked whether
the new Debian installer will be able to detect his NVidia graphic
card. I really didn't know what to reply, as I know discover1/2 will
certainly be able to detect it, but this wouldn't yield any
XFree86 configuration, as
Package: installation-reports
Debian-installer-version: sarge beta2 netinst
uname -a: can't
Date: 05 Feb 2004 8:00 GMT
Method: from CD
Machine: Dell Inspiron 8100
Processor: Pentium III 1200 MHz
Memory: 512 Mo
Root Device: IDE 60 Go Hitachi 5400 rpm (didn't boot it yet, don't know model)
Root Si
Am Mit, den 10.12.2003 schrieb Barrie James um 23:34:
> Suggestions : I'm surprised the network config is split into 2 sections, dhcp
> and static. I would have thought that this would be 2 options in a single
> section, maybe with dial-up as a further option as a lot of Debian users will
> have
x27;t say I particularly liked the
installer. The hardware detection is certainly improved and is a very
positive aspect, but the way that a couple of specific steps tried to prevent
me leaving them was a negative. I doubt that a newbie would have a happy time
with the installer on my box.
Sugge
[Branden Robinson]
> If Discover excites you as well, we cordially invite you to
> participate in Progeny's open development initiative.
Very good. Here is a patch for discover-data which would be applied
to the subversion repository.
http://lists.debian.org/debian-boot/2003/debian-boot-200310/m
iscover was
released with Debian 3.0 ("woody") to a very positive response, and was
promptly adopted as the hardware-detection technology of choice by the
Debian-Installer team, who are reimplementing Debian's installer technology
in a highly modular and flexible fashion that will also be
ts,
be Red Hat's guest. I have noticed that Klaus draws in Red Hat Linux for
his hardware detection in Knoppix 3.1.
Ah, it just said:
Running anaconda, the Red Hat Linux system installer - please wait...
Probing for video card: ATI Mach64 3D Rage IIC
Probing for monitor type: Hitachi
* Martin Sjögren
| I have no idea if this can/will work out in practice. It's a hack, but
| I'm not sure if it's a big ugly hack or a nice, neat hack. ;)
[...]
| So, what did I miss? Will this work or not? If it works, is it feasible?
| The Provides line can be auto-generated and stuff so that
I have no idea if this can/will work out in practice. It's a hack, but
I'm not sure if it's a big ugly hack or a nice, neat hack. ;)
a. Let every udeb with kernel modules provide virtual packages named
after the modules. So if we have the hypothetical package
weird-nic-drivers-udeb with modules fo
On Thu, 2002-02-14 at 12:30, Karl M. Hegbloom wrote:
> Any reason not to put hardware detection into the boot-floppies?
As far as I know, this feature is going to be part of debian-installer,
but not boot-floppies.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
#include
Karl M. Hegbloom wrote on Thu Feb 14, 2002 um 09:30:50AM:
> Any reason not to put hardware detection into the boot-floppies?
a) Disk space. The boot floppies are full.
b) Do you volunteer to implement this support?
> "libdetect" works fairly well on each of the thr
Any reason not to put hardware detection into the boot-floppies?
"libdetect" works fairly well on each of the three machines I've
tried it on.
Note that in the case of a USB keyboard and mouse, you'll want to
load the HID stuff right away, even before they try to type
On Wed, Oct 24, 2001 at 03:04:36PM -0700, David Kimdon wrote:
> partition_config.c : If there is only one drive, assume that is the drive we
> want to partition. FIXME: do we like this?
I think I would definitely blink if zapped into cfdisk without having
explicitly selected the drive. Currentl
On Wed, Oct 24, 2001 at 04:50:33PM -0700, Christoph Lameter wrote:
> Then we would probably need arch specific default partitioning strings.
>
> Do all arches support fdisk? Then we could simply have different schemes
> depending on arch.
no, macs must use mac-fdisk, m68K uses pmac-fdisk iirc (t
Then we would probably need arch specific default partitioning strings.
Do all arches support fdisk? Then we could simply have different schemes
depending on arch.
On Wed, 24 Oct 2001, Ethan Benson wrote:
> On Wed, Oct 24, 2001 at 03:04:36PM -0700, David Kimdon wrote:
>
> > partition_config.c :
On Wed, Oct 24, 2001 at 03:04:36PM -0700, David Kimdon wrote:
> partition_config.c : If there is only one drive, assume that is the drive we
> want to partition. FIXME: do we like this?
> Ask the user if they want to auto partition the drive. If so then take the first
> drive and divide it int
Looks fine to me. Selective comments below.
On Wed, 24 Oct 2001, David Kimdon wrote:
> 4. I reworked the choose_medium.c patch so now we verify that it is the right
> cdrom. (see choose_medium.c and util.[ch]). I don't have a cdrom to test with, and
> I'm not sure if that is the right way to te
Hi Christophe,
Thanks for the patch. I've gone through and made a few little changes that I'd
like you to ok. Once you are happy, I'm happy, and it would be great if you
just commit this to cvs.
Changes/Notes/Todo/Etc.
1. the libfdisk and the select_not_mounted.c change were more or less
stan
Tue, Oct 23, 2001 at 08:15:27PM -0700 wrote:
> On Sun, 21 Oct 2001, David Kimdon wrote:
>
> > Cool. It is probably best if I leave you to work through these. At
> > the moment there are other important b-f issues that I need to look
> > into. I definately like the direction you went with these
On Sun, 21 Oct 2001, David Kimdon wrote:
> Cool. It is probably best if I leave you to work through these. At
> the moment there are other important b-f issues that I need to look
> into. I definately like the direction you went with these. I
> especially like that you added a lot of function
On Fri, Jul 20, 2001 at 02:08:28PM +0200, Raphael Hertzog wrote:
> Le Thu, Jul 19, 2001 at 07:21:36AM -0700, David Kimdon écrivait:
> > This idea for d-i is that the first disk (i386 only at the moment) does
> > hardware detection of ethernet modules. After that the rest of the
&
Le Thu, Jul 19, 2001 at 07:21:36AM -0700, David Kimdon écrivait:
> This idea for d-i is that the first disk (i386 only at the moment) does
> hardware detection of ethernet modules. After that the rest of the
> installer is downloaded over the ethernet and the installer can proce
On Thu, Jul 19, 2001 at 04:48:24PM -0700, David Whedon wrote:
>
> > I don't want to do something on my own, and do want to work with others. The
> > only problem is that I have some deadlines at work, and that I try to both
> > develop for a general purpose (d-i), and to address more peculiar and
On Fri, Jul 20, 2001 at 10:14:50AM +1000, Glenn wrote:
> On Thu, 19 Jul 2001 17:00:41 +0200
> "Thierry Laronde" <[EMAIL PROTECTED]> wrote:
>
> > I'm trying to write a "general purpose" script to build a general database
> > from the Linux kernel sources. But there will be some particular problems
> supplementary resources via the device --- network fs). The trick is in fact
> to try to have the smallest bootstrapping procedure and there seems to be
> already a large part of the work done.
> The last time I checked for libdetect it was such a huge beast and decided
> to find another way to
On Fri, Jul 20, 2001 at 08:13:19AM +1000, Glenn wrote:
> On Thu, 19 Jul 2001 14:30:41 +0200
> "Thierry Laronde" <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > Just a summary of the principles I plan to use for, at least, my own stuff
> > and that can be of some use for others too.
> >
> > The
On Thu, 19 Jul 2001 17:00:41 +0200
"Thierry Laronde" <[EMAIL PROTECTED]> wrote:
> I'm trying to write a "general purpose" script to build a general database
> from the Linux kernel sources. But there will be some particular problems
> (exemple: when the *_pci_tbl is put in a file "main.c" and tha
1 - 100 of 139 matches
Mail list logo
