War Story: HP 2000 Laptop

Christopher Browne cbbrowne-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Thu Mar 7 15:59:54 UTC 2013


On Thu, Mar 7, 2013 at 9:52 AM, Lennart Sorensen
<lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org> wrote:
> On Wed, Mar 06, 2013 at 09:33:46PM -0500, Christopher Browne wrote:
>> A bit more targeted is thus...
>>
>> root at hpaq:~# lspci | egrep '(Network|Realtek)'
>> 01:00.0 Network controller: Ralink corp. Device 539b
>> 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
>> RTS5229 PCI Express Card Reader (rev 01)
>> 08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
>>
>> That validates Lennart's speculation, yes, indeed, Ralink Wifi.
>
> commit 2aed691540661e9cf6dac5dd2bd8742b9d68399d
> Author: Zero.Lin <Zero.Lin-NuS5LvNUpcJWk0Htik3J/w at public.gmane.org>
> Date:   Thu May 10 10:06:31 2012 +0800
>
>     rt2x00:Add RT539b chipset support
>
>     Signed-off-by: Zero.Lin <Zero.Lin-NuS5LvNUpcJWk0Htik3J/w at public.gmane.org>
>     Acked-by: Gertjan van Wingerde <gwingerde-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org>
>     Signed-off-by: John W. Linville <linville-2XuSBdqkA4R54TAoqtyWWQ at public.gmane.org>
>
> diff --git a/drivers/net/wireless/rt2x00/rt2800pci.c b/drivers/net/wireless/rt2x00/rt2800pci.c
> index 931331d..cad25bf 100644
> --- a/drivers/net/wireless/rt2x00/rt2800pci.c
> +++ b/drivers/net/wireless/rt2x00/rt2800pci.c
> @@ -1192,6 +1192,7 @@ static DEFINE_PCI_DEVICE_TABLE(rt2800pci_device_table) = {
>         { PCI_DEVICE(0x1814, 0x5390) },
>         { PCI_DEVICE(0x1814, 0x5392) },
>         { PCI_DEVICE(0x1814, 0x539a) },
> +       { PCI_DEVICE(0x1814, 0x539b) },
>         { PCI_DEVICE(0x1814, 0x539f) },
>  #endif
>         { 0, }
>
> So you will need kernel version 3.5 or higher to use wifi.
>
> in the case of debian that's tricky.  You would have to install wheezy or
> sid and use the experimental branch to get the 3.7 kernel.  Once wheezy is
> released, there should be a backports version of a new enough kernel too.

Slightly scarily, I tried out the 3.2.0-4 kernel (in testing) last
night, and that
turned out strangely badly, where very shortly after the kernel started, the
screen blanked, and there was no indication of further activity of the system.
Possibly just a screen confusion; I didn't check further.  Too many things
*useful* to do to the system.

Adding in a 3.7+ kernel looks not too troublesome; I suppose that I add in
   deb http://ftp.debian.org/debian/ experimental main contrib non-free
and some pin rules, such as:
cbbrowne at cbbrowne ~/firefox> cat /etc/apt/preferences.d/simple
Package: *
Pin: release a=stable
Pin-Priority: 700

Package: *
Pin: release a=testing
Pin-Priority: 650

Package: *
Pin: release a=unstable
Pin-Priority: 600

Package: *
Pin: release a=experimental
Pin-Priority: 100

The other little entertainment was that I had to work a little harder than
expected to get Firefox going.
- The built-in iceweasel is a rather too elderly version.
- The tarball that comes from a "default" download from Mozilla
  is a 32 bit build, and my system hasn't 32 bit libs.  Installing
  32 bit libraries seemed a bit of a pain, so I went with...
- Pulling a specifically-64-bit Firefox tarball.
-- 
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list