Package: installation-reports
Booting from CD using daily builds (11Apr-200) installer, when the installer
are copying base packages, apper next meesage:
"no installable kernel was found in the defined APT Sources"
I check MD5 of my download iso and is OK, burn on CD appers OK
My system is a HP
Otavio Salvador <[EMAIL PROTECTED]> writes:
> ...
>
> I guess it was commited by mistake.
Sorry, didn't see you have reverted it already.
Thanks anyway.
--
O T A V I OS A L V A D O R
-
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Li
Joey Hess <[EMAIL PROTECTED]> writes:
> Author: joeyh
> Date: Fri Apr 11 18:29:30 2008
> New Revision: 52621
>
> Log:
> create localudebdir if it does not exist
>
> This aids building d-i from a git repo, as localudebs is not tracked by git
> due to being an empty directory.
>
>
> Modified:
>t
Here they go ...
Regards.
Facundo.
El Friday 11 April 2008 16:56:57 Frans Pop escribió:
> On Friday 11 April 2008, Facundo Ariel Perez wrote:
> > I've two disk drives :
> > - 80 gb serial ata ( initially detected as /dev/sda and after
> > installation /dev/sdb )
> > - 40 gb ata-133 ( in
On Friday 11 April 2008, Facundo Ariel Perez wrote:
> I've two disk drives :
> - 80 gb serial ata ( initially detected as /dev/sda and after
> installation /dev/sdb )
> - 40 gb ata-133 ( initially detected as /dev/hdc and after
> installation /dev/sda )
>
> Comments/Problems:
>
> The problem is tha
Your message dated Fri, 11 Apr 2008 19:52:34 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#469030: fixed in base-installer 1.76etch1
has caused the Debian Bug report #469030,
regarding debian ppc64 not booting after install
to be marked as done.
This means that you claim that the
Accepted:
partman-lvm_53etch1.dsc
to pool/main/p/partman-lvm/partman-lvm_53etch1.dsc
partman-lvm_53etch1.tar.gz
to pool/main/p/partman-lvm/partman-lvm_53etch1.tar.gz
partman-lvm_53etch1_all.udeb
to pool/main/p/partman-lvm/partman-lvm_53etch1_all.udeb
Override entries for your package:
part
Accepted:
base-installer_1.76etch1.dsc
to pool/main/b/base-installer/base-installer_1.76etch1.dsc
base-installer_1.76etch1.tar.gz
to pool/main/b/base-installer/base-installer_1.76etch1.tar.gz
base-installer_1.76etch1_amd64.udeb
to pool/main/b/base-installer/base-installer_1.76etch1_amd64.ude
On Fri, Apr 11, 2008 at 03:15:37PM -0400, Joey Hess wrote:
> Package: debian-installer
> Severity: normal
>
> The mini.iso puts all files in the root of the CD. But the
> win32-loader.ini contains:
>
> i386/linux=linux
> i386/initrd=initrd.gz
>
> That won't work..
This is correct AFAICS. "i386
Your message dated Fri, 11 Apr 2008 15:39:09 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#475581: wrong paths in win32-loader.ini on mini.iso
has caused the Debian Bug report #475581,
regarding wrong paths in win32-loader.ini on mini.iso
to be marked as done.
This means that
Jérémy Bobbio wrote:
> After fetching your SVN branch, updating the kernel version, and using
> qemu 9.1 from unstable, the menu looks good, and no framebuffer problems
> where to be found. Both with or without -std-vga.
>
> I think it would be a good addition for Etch. Maybe post-beta2, though.
Package: debian-installer
Severity: normal
The mini.iso puts all files in the root of the CD. But the
win32-loader.ini contains:
i386/linux=linux
i386/initrd=initrd.gz
That won't work..
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500
* Martin Michlmayr <[EMAIL PROTECTED]> [2008-03-31 23:29]:
> Can't open /dev/tty2: No such file or directory
> Can't open /dev/tty3: No such file or directory
> Can't open /dev/tty4: No such file or directory
waldi, can you please upload the fix for this.
Thanks.
--
Martin Michlmayr
http://www.c
On Fri, Apr 11, 2008 at 01:38:30PM +0200, Frans Pop wrote:
> I installed it without problems on my KDE desktop. It's dependencies look
> sane (did not pull in any new packages in my case) and the default
> configuration is to ask to be allowed to submit.
>
> Only remaining question is how it wor
Jérémy Bobbio <[EMAIL PROTECTED]> writes:
> On Thu, Aug 2, 2007 17:05:51 -0400, Joey Hess wrote:
>> Here's a version of d-i that uses the syslinux vesamenu, which
>> provides a nice menu of boot options.
>>
>> svn://svn.debian.org/d-i/people/joeyh/vesamenu/
>> http://kitenet.net/~joey/tmp/mini.is
Package: installation-reports
Boot method: CD
Image version:
http://cdimage.debian.org/cdimage/daily-builds/daily/20080410-2/i386/iso-cd/debian-testing-i386-netinst.iso
Date: Apr 11 2008 01:00 UTC
Machine: Pc clon
Processor: PIV 2.4 ghz
Memory: 1 gb
Partitions:
/dev/sda1jfsmounted as /
On Friday 11 April 2008, Paul Civati wrote:
> I suppose what I'm asking really is, how do I build a udeb with
> my module, what additional files are needed in the image, and
> then, can I preseed that additional image?
>
> That seems an appropriate solution?
It seems overly complex to me.
Why not
On Friday 11 April 2008, Per Olofsson wrote:
> Joey Hess wrote:
> > Per Olofsson wrote:
> >> The default is to ask the user for permission before submitting
> >> anything. This is done by kerneloops-applet apparently. See
> >> /etc/kerneloops.conf.
> >
> > Does that only work in gnome? What about k
I looked at the cd-drivers.img, net-drivers-1.img, net-drivers-2.img
images and I see that there are udeb packages, plus some additional
files to indicate what the modules are, PCI device IDs and the like.
I suppose what I'm asking really is, how do I build a udeb with
my module, what additional f
Frans Pop <[EMAIL PROTECTED]> wrote:
> Basically you need to build your driver module against the kernel headers
> for the same kernel the installer uses (which is the -486 flavor of the
> i386 kernel) and make sure the ABI matches. So, if 'uname -a' in the
> installer gives you 2.6.18-6-486, you
Geert Stappers <[EMAIL PROTECTED]> wrote:
> > I need to use a kernel module at install time and thereafter,
> > for a RAID card that isn't supported in the standard kernels.
>
> Please spent effort in a dialog with the manufacturer of the RAID card.
> Explain them that you what to use their prod
On Wednesday 09 April 2008, Paul Civati wrote:
> I could build a custom installer/kernel, but I'd really like
> to only install the driver module so that the system can still
> make use of the standard updated kernels. Presuming that any
> apt upgraded kernels would not wipe out my custom driver.
On Thu, Aug 2, 2007 17:05:51 -0400, Joey Hess wrote:
> Here's a version of d-i that uses the syslinux vesamenu, which
> provides a nice menu of boot options.
>
> svn://svn.debian.org/d-i/people/joeyh/vesamenu/
> http://kitenet.net/~joey/tmp/mini.iso
>
> I think all the image types are fully workin
Op 09-04-2008 om 13:54 schreef Paul Civati:
> I need to use a kernel module at install time and thereafter,
> for a RAID card that isn't supported in the standard kernels.
Please spent effort in a dialog with the manufacturer of the RAID card.
Explain them that you what to use their product with
Joey Hess wrote:
> Per Olofsson wrote:
>> The default is to ask the user for permission before submitting anything.
>> This
>> is done by kerneloops-applet apparently. See /etc/kerneloops.conf.
>
> Does that only work in gnome? What about kde/xfce?
I think it should work in all desktop environme
25 matches
Mail list logo
