[okl4-developer] okl4 off the disk

[Ashish Bijlani]

I'm using a laptop, does it mean there are chances that the keyboard
is connected using USB?

On Wed, May 28, 2008 at 8:56 AM, Geoffrey Lee <glee at ok-labs.com> wrote:
> On Wed, May 28, 2008 at 08:16:08AM -0500, Ashish Bijlani wrote:
>> I added the required PCI ID to drivers/ata/ata_piix.c and the kernel
>> is able to mount the root file system residing on /dev/sda5. However,
>> it fails when it goes further and tries mounting udev; says  - no
>> space left on device. Also, the keyboard doesn't work with the booted
>> kernel. If I skip all the services by passing "init=/bin/bash"
>> argument to the kernel command line, I see bash shell after VFS mounts
>> the root file system (/dev/sda5). However, keyboard doesn't work. Any
>> suggestions? Thanks.
>
> Is your keyboard plugged on USB?  Assuming it is, then again this
> could be because your device is too new and the pci id and / or extra
> code to support your device is missing.
>
> We have not tested OK Linux with your version of Ubuntu and it is
> possible that the OK Linux kernel is too old or incompatible with
> your version of Ubuntu in some way.  The last Ubuntu we got running is 7.10.
>
>
>        -gl
>
>>
>> On Tue, May 27, 2008 at 6:53 PM, Geoffrey Lee <glee at ok-labs.com> wrote:
>> > On Tue, May 27, 2008 at 11:48:24AM -0500, Ashish Bijlani wrote:
>> >> The PCI ID according to lspci -vvnb is (8086, 2289), which is not
>> >> supported in oklinux/wombat
>> >> 00:1f.2 0106: 8086:2829 (rev 03) (prog-if 01 [AHCI 1.0])
>> >>
>> >> Can I make it work just by adding the relevant PCI ID in drivers/ata/ata_piix.c?
>> >>
>> >
>> > Sometimes to support a new device you just need to add a the
>> > PCI ID.  If it is more than that you will need to take a look at the
>> > changes required to support your drivers and port those changes
>> > to the ata_piix driver.
>> >
>> >
>> >> Also, I created /dev/console (MAJ=5, MIN=1) in the rootfs package by
>> >> adding the following lines in "linux/rootfs-2.6.23-v2/etc/init.d/rcS"
>> >>
>> >>    mknod /dev/console c 5 1
>> >>
>> >> Upon booting in qemu, I can verify the existence of device
>> >>
>> >> BusyBox v1.00 (2008.05.27-15:41+0000) Built-in shell (ash)
>> >> Enter 'help' for a list of built-in commands.
>> >>
>> >> / #
>> >> / # ls -l /dev/console
>> >> crw-r--r--    1 root     root       5,   1 Jan  1 00:00 /dev/console
>> >> / #
>> >>
>> >>
>> >> However, it doesn't help in getting msgs on the actual hardware. Any
>> >> suggestions? Thanks,
>> >>
>> >
>> > I've booted something very close to the 2.1 release for another
>> > project and can verify that the VGA should work.  There might be still
>> > some outstanding issues with VGA support though, we only test QEMU
>> > and the one or two pieces of hardware we have access to.
>> >
>> >        -gl
>> >
>>
>
> --
>
>