WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: firmware/driver for wifi  (Read 3891 times)

Offline PIRAT507

  • Newbie
  • *
  • Posts: 22
firmware/driver for wifi
« on: October 15, 2010, 05:29:23 PM »
Tinycore: Wonderful distro

Now I want to use my wireless USB device. In Debian the firmware is in ralink-firmware.deb.
Called rt2870.bin. It is placed in /lib/firmware. It works.
How to integrate such firmware in tiny/microcore?
Thanks!

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: firmware/driver for wifi
« Reply #1 on: October 15, 2010, 05:49:04 PM »
You can use AppsBrowser to see what provides that.

AppsBrowser->Connect->toggle Search to Provides
type rt2870 to see results of
firmware.tcz
rt2870-2.6.33-tinycore.tcz

Click on firmware and select files tab to see that there it is!

With wireless you will likely need
wireless-2.6.33.3-tinycore.tcz
wireless_tools.tcz
firmware.tcz

and/or perhaps the rt2870-2.6.33-tinycore.tcz use files tab to see what it provides.
10+ Years Contributing to Linux Open Source Projects.

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: firmware/driver for wifi
« Reply #2 on: October 15, 2010, 06:01:21 PM »
You could just install the 'firmware.tcz' extension, as the file you mentioned is included in it.

Otherwise if you already have the file at hand, you could create your very own private extension: You need the 'squashfs-tools-4.x.tcz' extension, and then perform something like:
    mkdir -p /tmp/my_ext/usr/local/lib/firmware
    sudo chown -R root:root /tmp/my_ext/
    sudo cp -p rt2870.bin /tmp/my_ext/usr/local/lib/firmware
    mksquashfs /tmp/my_ext my_ext.tcz

Then ensure that 'my_ext.tcz' is copied to your extensions directory (e.g. via cp my_ext.tcz $( cat /opt/.tce_dir)/optional) and included in the extension list for boot time (e.g. via echo my_ext.tcz >> $( cat /opt/.tce_dir)/onboot.lst)

Offline PIRAT507

  • Newbie
  • *
  • Posts: 22
Re: firmware/driver for wifi
« Reply #3 on: October 15, 2010, 06:19:03 PM »
Thanks!
I learned from your answers.
It didn't work, then I saw the device was not connected ;-).
Now I'm trying to get this driver running after reboot.
Reboot is FAST ;-)
« Last Edit: October 15, 2010, 06:27:35 PM by PIRAT507 »