* Denis Barbier [2004-07-05 00:13:55+0200]
> On Sun, Jul 04, 2004 at 12:13:10PM +0300, Recai Oktas wrote:
> > Hi,
> >
> > After getting success reports from Christian (French keyboard) and
> > Eugeniy (Ukrainian keyboard), I prepared a single patch which applies
> > cleanly to the current kbd-ch
A build of the Debian Installer Manual was triggered by an update to SVN.
There were no errors during the build process.
The new version of the manual has been uploaded successfully.
A log of the build is available at:
- http://home.tiscali.nl/isildur/d-i/log/en.log
===
If you would prefer this
On Sat, Jul 03, 2004 at 12:34:40PM +0200, C. Gatzemeier wrote:
>
> Hi *!
>
> Another idea I'd like to throw in is to also keep an eye on m23 and coordinate
> ideas.
> m23 offers a complete software distribution system for debian.
Notice that neither m23 nor FAI, both projects that where suggest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(I am sending this to -boot per tbm's suggestion).
Hi,
Since I am in the process of moving out to my own flat, I'm trying
to figure out what I actually need to take with me...
So I have this old-world PowerMac clone (Umax Apus 2000, same as an
Sup
On Sun, Jul 04, 2004 at 06:34:41PM -0700, Karl Hegbloom wrote:
> Has anyone created a udeb that will install the base system from a tar
> file?
It sounds like it would be a fairly small modification to
base-installer, although I don't know where you'd ask the question.
--
Colin Watson
Karl Hegbloom написав:
> package: partman-lvm
> severity: normal
>
> There should be a check that / is not a logical volume since the
> mkinitrd does not support that.
initrd-tools should support root on lvm. What version of installer do
you use?
> Grub probably doesn't either, right?
>
Grub doe
On Sun, Jul 04, 2004 at 10:40:14PM -0700, Karl Hegbloom wrote:
> package: partman-lvm
> severity: normal
>
> There should be a check that / is not a logical volume since the
> mkinitrd does not support that.
Are you sure that this is still a problem?
base-installer (0.085) unstable; urgency=low
Spam detection software, running on the system "murphy.debian.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email. If you have any questions, see
the administrator of that sys
Spam detection software, running on the system "murphy.debian.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or block
similar future email. If you have any questions, see
the administrator of that sys
Package: rootskel
Severity: grave
Version: 0.79
rootskel v0.79 is broken for i386.
This package misses
/lib/debian-installer.d/S33framebuffer-module-linux-i386, this file is
key component for i386 i18n installer.
I found tiny (but grave) mistake in Makefile and commited already.
Please upload v0.
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 257687 pending
Bug#257687: rootskel: Missing S33framebuffer-module-linux-i386
There were no tags set.
Tags added: pending
>
End of message, stopping processing here.
Please c
Package: netcfg
Version: 0.71
Severity: normal
If the debconf priority is critical and multiple interfaces are
available, netcfg only asks which interface to use at high priority, so
it fails. Trying again works fine, as the error causes the priority to
be dropped.
There may be other instances of
Package: debconf
Version: 1.4.29
Severity: wishlist
I'm sorry for bring up again about priority issue.
This wishlist is similar with #228839, but JoeyH looks don't
want to provide priority question in base-config.
After test and test, and as user's view, I think it is better that
debconf uses 'hi
Quoting Kenshi Muto ([EMAIL PROTECTED]):
> Package: debconf
> Version: 1.4.29
> Severity: wishlist
>
> I'm sorry for bring up again about priority issue.
> This wishlist is similar with #228839, but JoeyH looks don't
> want to provide priority question in base-config.
I think we could have a quit
As already pre-announced by Joey Hess in debian-boot, an opened
meeting of the Debian Installer "team" ("team" is very vague here,
everyone can attend of course) will happen on IRC.
Servers: freenode.net (just point your client to irc.debian.org)
Channel: #debian-boot
Time : Tuesday July 6th, 20
From a previous discussion – attached below…
Given that the error can be hunted down and corrected, what
is a person to do with a computer that apparently won’t boot from HDD,
floppy or CD?
It seems I’m stuck here with a failed installation!
Help!!
(Please cc: this email address
rootskel_0.80_powerpc.changes uploaded successfully to localhost
along with the files:
rootskel_0.80.dsc
rootskel_0.80.tar.gz
rootskel_0.80_powerpc.udeb
rootskel-bootfloppy_0.80_powerpc.udeb
rootskel-locale_0.80_powerpc.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRI
Kenshi Muto wrote:
> I'm sorry for bring up again about priority issue.
> This wishlist is similar with #228839, but JoeyH looks don't
> want to provide priority question in base-config.
I do plan to change debconf's default priority, but not until after the
sarge release. I know that there are va
Your message dated Mon, 05 Jul 2004 11:32:07 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257687: fixed in rootskel 0.80
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
Accepted:
rootskel-bootfloppy_0.80_powerpc.udeb
to pool/main/r/rootskel/rootskel-bootfloppy_0.80_powerpc.udeb
rootskel-locale_0.80_powerpc.udeb
to pool/main/r/rootskel/rootskel-locale_0.80_powerpc.udeb
rootskel_0.80.dsc
to pool/main/r/rootskel/rootskel_0.80.dsc
rootskel_0.80.tar.gz
to pool
On Mon, Jul 05, 2004 at 10:52:04AM -0400, J. Richard Miller wrote:
> >From a previous discussion - attached below.
>
> Given that the error can be hunted down and corrected, what is a person to
> do with a computer that apparently won't boot from HDD, floppy or CD?
What model again is your pmac
On Mon, May 10, 2004 at 05:01:57PM +0100, Colin Watson wrote:
> I noticed your commit of an updated sq.po to yaboot-installer. Thanks
> for the translation! However, could you please not edit debian/changelog
> when committing updated translations in the debian-installer repository?
> We update the
base-installer_0.088_powerpc.changes uploaded successfully to localhost
along with the files:
base-installer_0.088.dsc
base-installer_0.088.tar.gz
base-installer_0.088_powerpc.udeb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Accepted:
base-installer_0.088.dsc
to pool/main/b/base-installer/base-installer_0.088.dsc
base-installer_0.088.tar.gz
to pool/main/b/base-installer/base-installer_0.088.tar.gz
base-installer_0.088_powerpc.udeb
to pool/main/b/base-installer/base-installer_0.088_powerpc.udeb
Announcing to [EMA
On Mon, 2004-07-05 at 12:43 +0300, Eugeniy Meshcheryakov wrote:
> Karl Hegbloom написав:
> > package: partman-lvm
> > severity: normal
> >
> > There should be a check that / is not a logical volume since the
> > mkinitrd does not support that.
> initrd-tools should support root on lvm. What versio
Your message dated Mon, 05 Jul 2004 13:17:03 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#257301: fixed in base-installer 0.088
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 n
vxyayfx
Name Brand Software at Wholesale price.
50-60 USD:
Windows XP Professional
Microsoft Office 2003 Professional
Adobe Photoshop
MacroMedia Studio MX
MS SQL Server 2000 Enterprise
Save your company thousands of dollars when it needs software
That promotion just got closer...
wait there i
* Recai Oktas [2004-07-05 10:16:30+0300]
[...]
> > Index: packages/kbd-chooser/getfd.c
> > ===
> > --- packages/kbd-chooser/getfd.c(revision 17443)
> > +++ packages/kbd-chooser/getfd.c(working copy)
> > @@ -45,7 +45,9 @@
> > }
Package: installation-reports
Version: 20040704
I used
http://gluck.debian.org/cdimage/testing/sid_d-i/powerpc/20040704/sarge-powerpc-netinst.iso
and booted with install-power4-2.6
The kernel initializes (penguin screen) until i see the line:
Loading AT keyboard module
where it freezes.
--
Accepted:
debian-installer-manual_20040701_i386.deb
to pool/main/d/debian-installer/debian-installer-manual_20040701_i386.deb
debian-installer_20040701.dsc
to pool/main/d/debian-installer/debian-installer_20040701.dsc
debian-installer_20040701.tar.gz
to pool/main/d/debian-installer/debian-in
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 230436 atmelwlandriver-sources
Bug#230436: FWD: installing Sarge with F5D6050
Warning: Unknown package 'atmelwlandriver-sources'
Bug reassigned from package `installation-r
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 256389 normal
Bug#256389: installation-reports: loading scsi drivers during netboot
Severity set to `normal'.
> tags 256389 moreinfo
Bug#256389: installation-reports: load
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 234162 moreinfo
Bug#234162: INSTALL REPORT
There were no tags set.
Tags added: moreinfo
>
End of message, stopping processing here.
Please contact me if you need assistance.
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 229772 moreinfo
Bug#229772: install report on powerbook 12"
There were no tags set.
Tags added: moreinfo
>
End of message, stopping processing here.
Please contact me if you
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 231432 hw-detect
Bug#231432: debian-installer-demo: Installer doesn't detect my IDE drive anymore
Bug reassigned from package `installation-reports' to `hw-detect'.
>
End
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 234605 moreinfo
Bug#234605: Package: installation-reports
Tags were: moreinfo
Tags added: moreinfo
>
End of message, stopping processing here.
Please contact me if you need a
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 257743 kernel-image-2.4.25-power4-pmac
Bug#257743: install on G5 fails at Loading AT Keyboard
Bug reassigned from package `installation-reports' to
`kernel-image-2.4.25-po
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 230552 debian-installer-manual
Bug#230552: installation report: IBM Thinkpad X23
Bug reassigned from package `installation-reports' to `debian-installer-manual'.
> tags 23
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 233540 d-i
Bug#233540: Installer report and trashing of existing install
There were no tags set.
Tags added: d-i
> reassign 233540 main-menu
Bug#233540: Installer report and t
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> severity 256905 normal
Bug#256905: installation-reports: can't mount the CD after hardware detection
Severity set to `normal'.
>
End of message, stopping processing here.
Please c
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 234506 moreinfo
Bug#234506: Package: installation-reports
There were no tags set.
Tags added: moreinfo
>
End of message, stopping processing here.
Please contact me if you ne
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 232116 kbd-chooser
Bug#232116: success, but a partitioning problem (and some Dutch translation remarks)
Bug reassigned from package `installation-reports' to `kbd-chooser'.
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 231836 netcfg
Bug#231836: regression with plip
Bug reassigned from package `installation-reports' to `netcfg'.
> tags 231836 d-i
Bug#231836: regression with plip
There wer
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 235096 install to blank disk failed partitioning
Bug#235096: Package: installation-reports
Changed Bug title.
> tags 235096 moreinfo
Bug#235096: install to blank disk faile
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> clone 233864 -1
Bug#233864: kbd-chooser crash - man-db error
Bug 233864 cloned as bug 257748.
> reassign -1 man-db
Bug#257748: kbd-chooser crash - man-db error
Bug reassigned from
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 234887 grub-installer
Bug#234887: Net install over HP ProLiant DL360 G3
Bug reassigned from package `installation-reports' to `grub-installer'.
> retitle 234887 crash inst
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 236293 aic7xxx problem
Bug#236293: unresolved symbols when insmod 8390
Changed Bug title.
>
End of message, stopping processing here.
Please contact me if you need assista
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 231836 moreinfo
Bug#231836: regression with plip
Tags were: d-i
Tags added: moreinfo
>
End of message, stopping processing here.
Please contact me if you need assistance.
De
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 235418 moreinfo
Bug#235418: Various blocking problems installing on a RAID server -- d-i snapshot of
23/02/2004
There were no tags set.
Tags added: moreinfo
>
End of message,
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> retitle 236142 Swedish translation problems
Bug#236142:
Changed Bug title.
> tags 236142 moreinfo
Bug#236142: Swedish translation problems
There were no tags set.
Tags added: more
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 227917 moreinfo
Bug#227917: Boot fails on Alpha DS 10 with illegal instruction
There were no tags set.
Tags added: moreinfo
>
End of message, stopping processing here.
Please
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> submitter 230445 Markus Amersdorfer <[EMAIL PROTECTED]>
Bug#230445: FWD: "INSTALL REPORT" d-i
Changed Bug submitter from Joey Hess <[EMAIL PROTECTED]> to Markus Amersdorfer <[EMAIL
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> reassign 231949 netcfg
Bug#231949: Debian Installation Report
Bug reassigned from package `installation-reports' to `netcfg'.
> tags 231949 d-i moreinfo
Bug#231949: Debian Installa
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 230977 unreproducible moreinfo
Bug#230977: installation-reports
Tags were: moreinfo
Tags added: unreproducible, moreinfo
>
End of message, stopping processing here.
Please co
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 231086 moreinfo
Bug#231086: Could not get sarge installer to boot on a TOSHIBA TECRA 8200
There were no tags set.
Tags added: moreinfo
> retitle 231086 network config failure
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 230630 moreinfo
Bug#230630: SCSI HD, installation with bootfloppy and usb flash stick, i386
There were no tags set.
Tags added: moreinfo
>
End of message, stopping processing
Your message dated Mon, 5 Jul 2004 14:29:05 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:27:31 -0400
with message-id <[EMAIL PROTECTED]>
and subject line I am closing this bug report, because it has been fixed. By the way,
email has a subject field, and a body. You're not supposed to put the entire email in
the subject field, because that looks s
Your message dated Mon, 5 Jul 2004 14:46:57 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing old report
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 t
Your message dated Mon, 5 Jul 2004 14:42:01 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing report
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
Your message dated Mon, 5 Jul 2004 14:40:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:39:16 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:34:40 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:24:58 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:33:08 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing successful report
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
Your message dated Mon, 5 Jul 2004 14:14:18 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:15:24 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:10:17 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closed
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 reopen the
Your message dated Mon, 5 Jul 2004 14:02:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:06:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:01:03 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:00:00 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing report
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
Your message dated Mon, 5 Jul 2004 13:57:04 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:59:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:49:38 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:46:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line 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 reopen the
Your message dated Mon, 5 Jul 2004 13:39:27 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:23:45 -0400
with message-id <[EMAIL PROTECTED]>
and subject line close
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 reopen the
Your message dated Mon, 5 Jul 2004 13:28:15 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:29:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:19:09 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing old report
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 t
Your message dated Mon, 5 Jul 2004 14:23:14 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing this report
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
Your message dated Mon, 5 Jul 2004 13:50:51 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:19:21 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Since you reported this problem with your sparc being unable to boot the
sid_d-i netinst, I know some things have changed with silo and the
installer. Can you try again with the current version?
--
see shy jo
signature.asc
Description: Digital signature
This January, you reported some problems with the debian installer on
your HP Pavilion. I think all of them are fixed, except possibly the
VIA-Rhine-II NIC not working. Can you try again with a current version
of the debian installer, and see if it works? You don't need to complete
the install, jus
You reported an illegal instruction and kernel panic on boot with the
debian installer. Could you please retry with the lastest images?
If this bug still exists with current d-i images, it should probably be
reassigned to the appropriate kernel package.
--
see shy jo
signature.asc
Description:
In January you reported problems installing on your powerbook with the
debian installer. Could you please retry with the current images, and
verify that all the problems you encountered have been fixed? It seems
quite likely to me that they have been, so if we don't hear back from
you, I'll close t
I've verified (by inspection) that current discover1-data loads the
correct dmfe driver for the PCI id of the davicom network card. I don't
know about the rest, we need followup from the bug submitter.
--
see shy jo
signature.asc
Description: Digital signature
I think that this is a documentation problem. There should be somesthing
in the installation manual that explains that the installer system is
set up to use discover and hotplug for automatic hardware detection, and
that if intermediate users don't like all these "useless" modules to be
loaded, the
> attempt to access beyond end of devive
> 16:40: rw=0, want=899731, limit=899698
> isofs_fill_super: bread failed, ...
There are only a few things this could be. It's best to assume it's not
a kernel problem until you've checked basic things like whether you
downloaded the complete iso, whether i
You don't say what version of the installer you were using (the url it
was downloaded from). Probably you're using beta4 or something, that has
a mismatch with the kernel modules currently available on the mirrors.
When operating properly, the netboot installer downloads additional
kernel modules f
Your message dated Mon, 5 Jul 2004 13:12:33 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:30:35 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:35:34 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 14:03:40 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:55:01 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:52:42 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
Your message dated Mon, 5 Jul 2004 13:41:09 -0400
with message-id <[EMAIL PROTECTED]>
and subject line no response from submitter
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 responsi
Your message dated Mon, 5 Jul 2004 13:58:20 -0400
with message-id <[EMAIL PROTECTED]>
and subject line closing
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 reopen th
1 - 100 of 137 matches
Mail list logo