Re: Solution for issue with PicassoII and flickering pixels
On 04.02.2006, Christian Steigies wrote:
> On Sat, Feb 04, 2006 at 08:05:50PM -0500, Peter Krummrich wrote:
>>
>> I would highly appreciate if the code in the main debian source
>> repository was adapted to the new values. By doing so, owners of the
>> PicassoII board will get a much better display with future kernel
>> versions.
>
> Please send me a unified diff (diff -u) and I will include it. However,
> there wont be many new releases for 2.4 kernels, and it will be difficult
> to get this change included officially in sarge.
>
> It would be good if you could check if the problem also appears with
> linux-2.6. I just uploaded 2.6.15, it will probably take a few days until
> it appears in the archive. I put a copy here:
>
> http://people.debian.org/~cts/debian-m68k/linux-image/
>
> You will also need yaird for the initrd (even though you probably do not
> need it for booting). The package you find there should be installable on
> sarge. See aso
>
> http://wiki.debian.org/DebianM68kKernel
>
> I also built an updated package for amiga (-4.1) which has a fix for the
> buddha IDE driver (catweasel, x-surf). If you have another IDE controller
> (gayle), it might need a similar fix and the kernel will probably not boot
> on your machine.
>
> Christian
>
I loaded the kernel image archive and the yaird archive, installed yaird
directly from the .deb-file using dpkg, got error messages stating that
yaird depends on dash, libhtml-template-perl, and libparse-recdescent-perl,
installed these three packages from my Sarge 3.1r1 CD set using aptitude.
When installing the kernel-image from the .deb-file using dpkg, I got an
error message that dpkg is not able to set-up the package.
As the image file was unpacked and copied to /boot, I wanted to give it a
try. I copied it to my Amiga disk, rebooted and tried to boot the new 2.6
kernel from the amiga side using amiboot-5.6. The Debian-Installer stopped
with an error message "Compressed image too large! Aborting."
Log of Debian Installer:
Found 5 AutoConfig Devices
Device 0: addr = 0x00ea0000
Device 1: addr = 0x00e90000
Device 2: addr = 0x00200000
Device 3: addr = 0x00ec0000
Device 4: addr = 0x00ed0000
Found 1 Block of Memory
Block 0: 0x08000000 to 0x0bf80000 (65024K)
1024K of CHIP memory
The kernel will be located at 0x08000000
Kernel is compressed
Uncompressing kernel image
................................................................
Compressed image too large! Aborting.
Are there any other tricks necessary to boot a 2.6 kernel image?
Best Regards,
Peter
Reply to: