Re: Compiling 2.4.18 kernel for U1

2002-08-07 Thread Stuart Yarrow
>Disable USB and the Input interfaces. Make sure you disable IEEE1394
>aswell.

disabling the input interfaces solved my problems. the kernel package I am
using is available here, in case anyone with an Ultra 1 (or possibly 2)
finds it useful.  it has no Creator support, as mine is a plain U1.

http://www.outpost.org.uk/linux/





Compiling 2.4.18 kernel for U1

2002-07-31 Thread Stuart Yarrow
Hi

Having had problems installing Woody on my U1 (possibly due to unnecessary
drivers compiled into the kernel) I have been trying to compile a more
stripped down version (minus PCI, IDE, etc).  I am running a fairly minimal
install of Potato while I'm trying to do this.

The compile fails with:

in function 'emulate_raw'
undefined reference to 'handle_scancode'

in function 'keybdev_init'
undefined reference to 'kbd_ledfunc'

I found a reference on another list that suggested it could be a USB issue,
but all the USB options in menuconfig seem to be inactive.  I am new to
kernel compiling, but I am reasonably sure I have set everything up
properly; kernel-package and so on.

...appreciate any advice

-Stu




Woody/U1 installation problems

2002-07-24 Thread Stuart Yarrow
Hello again :-)

Installing Woody on an Ultra 1 via RARP/TFTP/HTTP using standard files from
a mirror...

Immediately before it enters the kernel module installation menu,

cannot create /proc/sys/kernel/modprobe: directory nonexistant

appears on the background of the display. I'm not sure whether this is a
problem...

If I try to create a boot disk, the machine hangs as soon as I press enter,
and does not respond to Stop-a.  The floppy spins in the drive, but there is
no head movement.  This appears to be the same problem as I wrote about
before when booting from floppies.

Assuming that I skip the boot disk creation, all is well until I reboot from
the hard disk for the first time, when I get all the way to the first
dialogue box saying 'Congratulations, you have successfully installed
Debian!' etc, but when I hit enter to continue the machine crashes with a
long series of dumps.

I also noticed that, as someone else mentioned, it can't read the hardware
clock as it is booting...am I right in thinking that the next stage of the
configuration would be setting up the time zone? Is it possible that this
crash is due to the clock not being set?

again, any advice very much appreciated

cheers

-Stu



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]