On Tue, Aug 10, 2004 at 12:14:39AM +0200, Wouter Verhelst wrote:
> Yes, I know that. But the userdevfs-dev.txt file is used to generate the
> ext2 filesystem, so that creates the device nodes which are on the
> initrd even before it boots.
Only for userdevfs formatted initrd's (those destined fo
On Tue, Aug 10, 2004 at 01:30:23AM +0200, Petr Stehlik wrote:
> Real disappointed by the kernel 2.4.26 that allocates the videoram
> randomly and often completely out of 24-bit VIDEL range I have given
> last try with the 2.2.x kernel. And what a surprise - at the moment
> where kernel 2.4.x turned
V Út, 10. 08. 2004 v 01:41, Stephen R Marenka píše:
> > console=tty0
> > in bootargs (kernel parameters) fixes it and the d-i boots
> Well I think it's required for any machine using a serial console.
I am not using a serial console. I have just added debug=ser, that's
all. I hope the debug=ser w
On Mon, Aug 09, 2004 at 11:38:10PM +0200, Wouter Verhelst wrote:
> [EMAIL PROTECTED]:~/debian/debian-installer$ svn diff -r18429:18430
> Index: installer/build/userdevfs-dev.txt
> ===
> --- installer/build/userdevfs-dev.txt (revisio
On Mon, Aug 09, 2004 at 10:58:24PM +0200, Petr Stehlik wrote:
> Hi,
>
> after long debugging of the suspicious Warning: unable to open an
> initial console that turned out to be actually fatal for d-i installer
> (because it starts with busybox init /dev/console and so
> missing /dev/console kills
Real disappointed by the kernel 2.4.26 that allocates the videoram
randomly and often completely out of 24-bit VIDEL range I have given
last try with the 2.2.x kernel. And what a surprise - at the moment
where kernel 2.4.x turned font colors to red and got stuck the 2.2.x
cleared the screen and off
V Út, 10. 08. 2004 v 00:14, Wouter Verhelst píše:
> > well, your patch makes sense but the Warning is printed by kernel
> > itself, probably before the userdevfs is activated.
>
> Yes, I know that. But the userdevfs-dev.txt file is used to generate the
> ext2 filesystem, so that creates the device
On Tue, Aug 10, 2004 at 12:07:07AM +0200, Petr Stehlik wrote:
> V Po, 09. 08. 2004 v 23:38, Wouter Verhelst pÃÅe:
> > > console=tty0
> > >
> > In that case, the bug isn't in the kernel, but in debian-installer:
>
> well, your patch makes sense but the Warning is printed by kernel
> itself, probab
V Po, 09. 08. 2004 v 23:38, Wouter Verhelst píše:
> > console=tty0
> >
> In that case, the bug isn't in the kernel, but in debian-installer:
well, your patch makes sense but the Warning is printed by kernel
itself, probably before the userdevfs is activated.
> > The d-i doesn't work yet, it stop
On Mon, Aug 09, 2004 at 10:58:24PM +0200, Petr Stehlik wrote:
> Hi,
>
> after long debugging of the suspicious Warning: unable to open an
> initial console that turned out to be actually fatal for d-i installer
> (because it starts with busybox init /dev/console and so
> missing /dev/console kills
Hi,
after long debugging of the suspicious Warning: unable to open an
initial console that turned out to be actually fatal for d-i installer
(because it starts with busybox init /dev/console and so
missing /dev/console kills it) I have just found out that simple
console=tty0
in bootargs (kernel
On Mon, Aug 09, 2004 at 10:24:31AM +0100, Joe wrote:
> Doesn't seem to matter whether mode32 is in use or not?
The only thing it could affect is Penguin. All mode32 does is patch
the MacOS to properly support 32 bit addressing. Several of the early
68020 and 68030 boxes shipped with ROM code that
It finally installed... 8mb RAM meant it took 8 days but it
got there in the end and boots fine.
Doesn't seem to matter whether mode32 is in use or
not?
- Joe
Hi,
I just uploaded some 2.6.7 kernel-images to
http://people.debian.org/~cts/debian-m68k/kernel-image/
They were cross-compiled and I did not test any of them yet. But if you are
interested in 2.6 kernel-images for m68k, please go ahead, test, and report
back. They will probably not work yet on m
14 matches
Mail list logo
