On Friday 04 April 2008, Paul Wise wrote:
> I couldn't see any obvious way to configure d-i to use my serial
> mouse, nor any way to find out what mouse it was currently using.
This is now supported, though still not in an "obvious" way [1]. It would be
great if you could test that it works using
On Sun, 2008-04-20 at 20:02 +0200, Robert Millan wrote:
> > > choose en_AU as an additional language - seems that en_AU.iso88591 got
> > > preseeded from debian.exe?
> >
> > If that is true, it would IMO be a pretty serious bug in win32-loader as
> > Debian is supposed to be installed using UTF-
On Fri, Apr 04, 2008 at 03:29:59PM +0800, Paul Wise wrote:
> get to nice blue grub2 splash - shouldn't the bootloader and d-i use
> consistent themes?
> [...]
> hmm, no splashy
> gdm comes up - again theme consistency would be good
> [...]
> again the blue theme, perhaps d-i needs changing to use
On Sun, Apr 20, 2008 at 06:41:44PM +0200, Frans Pop wrote:
> On Friday 04 April 2008, Paul Wise wrote:
> > There are some other minor issues below though:
> >
> > goodbye-microsoft.com
> > wait for grub2 (seems slower than grub1)
>
> Yes, I've seen that too in Virtualbox. It takes a huge amount of
reassign 473364 win32-loader
retitle 473364 Should not preseed legacy encodings
severity 473364 important
thanks
(Omitting issues previously answered.)
On Friday 04 April 2008, Paul Wise wrote:
> There are some other minor issues below though:
>
> goodbye-microsoft.com
> wait for grub2 (seems slo
Processing commands for [EMAIL PROTECTED]:
> reassign 473364 win32-loader
Bug#473364: installation-report: some install glitches (grub2, tasksel, serial
mouse)
Bug reassigned from package `installation-reports' to `win32-loader'.
> retitle 473364 Should not preseed legacy enco
On Fri, 2008-04-04 at 21:00 +0200, Frans Pop wrote:
> > Do you know if directfb can switch to a different mouse after g-i is
> > already started?
>
> Well, we do a keymap switch, which is somewhat similar.
> Not sure if this will work, but could you try the following just to check:
> - boot the i
Processing commands for [EMAIL PROTECTED]:
> clone 473364 -1
Bug#473364: installation-report: some install glitches (grub2, tasksel, serial
mouse)
Bug 473364 cloned as bug 474296.
> reassign -1 rootskel-gtk
Bug#474296: installation-report: some install glitches (grub2, tasksel, serial
clone 473364 -1
reassign -1 rootskel-gtk
retitle -1 Support configuring mouse port (serial) and protocol
severity -1 wishlist
thanks
On Friday 04 April 2008, Paul Wise wrote:
> It worked when I added mouse-source=/dev/ttyS1 and mouse-protocol=MS
> to /etc/directfbrc since I have a 2 button Microso
clone 473364 -1
reassign -1 cdebconf-gtk-udeb
severity -1 minor
retitle -1 cdebconf-gtk-udeb: segfaults after SIGTERM during reboot
thanks
On Friday 04 April 2008, Paul Wise wrote:
> reboot
> see debconf segfault on console just before the reboot happens
I've noticed that as well, but so far not
Processing commands for [EMAIL PROTECTED]:
> clone 473364 -1
Bug#473364: installation-report: some install glitches (grub2, tasksel, serial
mouse)
Bug 473364 cloned as bug 474286.
> reassign -1 cdebconf-gtk-udeb
Bug#474286: installation-report: some install glitches (grub2, tasksel,
On Fri, 2008-04-04 at 18:14 +0200, Frans Pop wrote:
> For the installation a serial mouse can probably be made working. Please try
> the following:
>
> - boot the installer with installgui BOOT_DEBUG=3
> - in the debug shell, edit /etc/directfbrc and add the following line:
> mouse-source=
>
On Sunday 30 March 2008, Paul Wise wrote:
> Thirdly my mouse is a serial mouse and there didn't seem to be any
> obvious way to use it. The computer has a PS2 mouse port, but I don't
> have a PS2 mouse for this computer. It is on /dev/ttyS1 rather than S0
> due to the positions of cables, usb socke
On Thu, 2008-04-03 at 15:12 -0400, Joey Hess wrote:
> Paul Wise wrote:
> > The /etc/grub.d/30_otheros that was generated did not allow me to boot
> > Windows. Simply changing (hd0,0) to (hd0,1) fixed this. Looks like grub2
> > uses 1-based partition indexes instead of 0-based ones like grub1 did.
Paul Wise wrote:
> The /etc/grub.d/30_otheros that was generated did not allow me to boot
> Windows. Simply changing (hd0,0) to (hd0,1) fixed this. Looks like grub2
> uses 1-based partition indexes instead of 0-based ones like grub1 did.
AFAIK we're still not installing grub2 by default, are we?
15 matches
Mail list logo
