The help screen of the install script says it will use ext2 by
default, but then creates an ext3 filesystem.
It ends with error:
P: Configuring package debian-archive-keyring
P: Configuring package apt
P: Configuring helper cdebootstrap-helper-apt
E: Internal error: install
r...@om-gta02:~#
On Sun, Jul 26, 2009 at 01:18:24PM +0200, Lionel Elie Mamane wrote:
The help screen of the install script says it will use ext2 by
default, but then creates an ext3 filesystem.
It gets actually mounted as ext2, though.
--
Lionel
___
I (and Joachim Breitner) find the default call volume rather low in
zhone. This patch sets it to maximum, which I still find good only for
rather quiet situations. Is the hardware just limited that way, or
does anybody know of another of the 100+ ALSA settings that would
help?
--
Lionel
diff
Lionel Elie Mamane lio...@mamane.lu writes:
I (and Joachim Breitner) find the default call volume rather low in
zhone. This patch sets it to maximum, which I still find good only for
rather quiet situations. Is the hardware just limited that way, or
does anybody know of another of the 100+
Hi,
Am Sonntag, den 26.07.2009, 23:12 +0400 schrieb Paul Fertser:
Lionel Elie Mamane lio...@mamane.lu writes:
I (and Joachim Breitner) find the default call volume rather low in
zhone. This patch sets it to maximum, which I still find good only for
rather quiet situations. Is the hardware
On Sun, Jul 26, 2009 at 01:18:24PM +0200, Lionel Elie Mamane wrote:
After using configure-uboot.sh, the first boot did not work
(openmoko logo staying). I went into the NAND boot manager, selected
boot, I got an error message I could not read, selected boot
again and it worked.
This is
Joachim Breitner m...@joachim-breitner.de writes:
Am Sonntag, den 26.07.2009, 23:12 +0400 schrieb Paul Fertser:
Lionel Elie Mamane lio...@mamane.lu writes:
I (and Joachim Breitner) find the default call volume rather low in
zhone. This patch sets it to maximum, which I still find good only
Hi,
Am Sonntag, den 26.07.2009, 23:47 +0200 schrieb Lionel Elie Mamane:
On Sun, Jul 26, 2009 at 01:18:24PM +0200, Lionel Elie Mamane wrote:
After using configure-uboot.sh, the first boot did not work
(openmoko logo staying). I went into the NAND boot manager, selected
boot, I got an
