[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel versus broadcom wlan



On Thu, Jan 31, 2008 at 20:58:32 -0700, wauhugo AT yahoo DOT com wrote:
> Celejar wrote:

[...]

> Thank you.
> According to this post  
> https://lists.berlios.de/pipermail/bcm43xx-dev/2008-January/006622.html
> did I fetch the patch from  
> http://linuxwireless.org/download/b43/patch_2.6.24_for_4311_2
> and copied the file to /usr/src/
>
> then followed these actions to build the kernel from debian 2.6.24  
> source with these patches:
> # ln -s linux-source-2.6.24 /usr/src/linux
> # cp /boot/config-2.6.24-1-amd64 /usr/src/linux/.config
> # cd /usr/src/linux
> # patch -p1 <patch_2.6.24_for_4311_2
> # make clean
> # make xconfig
> # make-kpkg clean
> # fakeroot make-kpkg --initrd --append-to-version=-b43 kernel_image  
> kernel_headers
> # cd ..
> # sudo dpkg -i linux-headers-2.6.24-b43_2.6.24-b43-10.00.Custom_amd64.deb
> # sudo dpkg -i linux-image-2.6.24-b43_2.6.24-b43-10.00.Custom_amd64.deb
> (these lines are handwriting and may have typos)
>
> The installation runs finally into this error:
> [...]
> Setting up linux-image-2.6.24-b43 (2.6.24-b43-10.00.Custom) ...
> Running depmod.
> Finding valid ramdisk creators.
> Using mkinitrd.yaird to build the ramdisk.
> yaird error: unrecognised device: /sys/devices/LNXSYSTM:00

[...]

> yaird error: there were errors in this run, aborting now without output  
> (fatal)
> mkinitrd.yaird failed to create initrd image.
> Failed to create initrd image.
> dpkg: error processing linux-image-2.6.24-b43 (--install):
> [...]
>
> What can I do, to bypass this error during installation on the debian  
> sid system?

You could try to switch to mkinitrd (from the initrd-tools package) for
the generation of the initrd. You can specify your preferred initrd
creator in /etc/kernel-img.conf with the "ramdisk" option; see the
manpage of kernel-img.conf. Then run the "dpkg -i linux-image-..."
command again.

-- 
Regards,            | http://users.icfo.es/Florian.Kulzer
          Florian   |


Reply to: