wireless on an old Thinkpad 600

Hi to everyone !

I would like to install wireless facilities on my old Thinkpad. It has a
300 Mhz processor, 128 MB of RAM, and 4.1 GB of space on hard disk. It
used to run on RedHat 7.2, which stayed there for about six years without
any problem. Since I have been unable to get wireless working on it using
pcmcia IBM 'EtherJet' card and a router in client mode 'FON2200' (the so
called Fonera), I installed Debian Sarge instead of RedHat 7.2.

This Debian system still did not acknowledge the EtherJet card, but it
accepted an Ethernet pcmcia 'D-Link 660' card, and gave
me a good fast 1 MB DSL connexion. Now, my purpose is to have a wireless
connexion to my DSL
modem/router (as well as connexions to hotels wireless facilities etc..).
I thought that I could achieve this with the router Fonera, but, even
though I have tested this with Microsoft Windows 98, I can't get it
working on Linux.

My first question concerns the cable connexion between the router Fonera
and my pcmcia Ethernet cards. My first Ethernet card, the IBM 'EtherJet'
gets connected with four plugs : five pins, six pins, then a sort of a
hook in the center, then again six pins, then five pins. It seems rather
weird as a plugging system. This, as I said, goes into the pcmcia
EtherJet card ; in the other end of the cable there is something that
looks like a standard network plug ; it is supposed to get plugged into
the router Fonera. This EtherJet card, with this special cable does
provide a connexion with the router under Microsoft Windows. But, as I
said before, this EtherJet card is not being reckognized on my Debian
system (or I have not been able to get it to work on it). On the contrary,
the D-Link Ethernet card is being reckognized under Debian... but it does
not provide the same plugging system as the other card... Instead of that
weird 4 plugs system, it takes only one central plug with I can't count
how many pins, which central plug is connected to a converting cord which
other end has a female outlet in which any network cable can be inserted.
This system does work for Ethernet either on MS Windows or on Linux, but I
have not been able to get it to connect to the router Fonera in either
system. I mean : the plugging is feasable as far as plugs and converters
are concerned, but, once done, the Fonera does not respond to calls to its
addresses 169.254.255.1 and 192.168.1.1, while it does with the other
plugging system, at least under Windows. Is this normal, or have I missed
something ? In any case, how can I solve this problem ? which Ethernet
pcmcia card will have the same plugging system as the EtherJet card as
well as being workable under Linux ? From the above report of trials, I
am unable to know whether the fact that I cannot run this system under
Linux is due to this system or to the connection mode...

Thanks in advance for any useful tips or information.




--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

Hi Bernard,

On Wed, 29 Oct 2008 00:44:04 +0100
Bernard <bdebreil@teaser.fr> wrote:
[color=blue]
> This Debian system still did not acknowledge the EtherJet card, but it
> accepted an Ethernet pcmcia 'D-Link 660' card, and gave
> me a good fast 1 MB DSL connexion. Now, my purpose is to have a[/color]

Having seen it work in one environment, you now know the Ethernet pcmcia
'D-Link 660' card works with Debian.
[color=blue]
> wireless connexion to my DSL
> modem/router (as well as connexions to hotels wireless facilities
> etc..). I thought that I could achieve this with the router Fonera,
> but, even though I have tested this with Microsoft Windows 98, I
> can't get it working on Linux.[/color]

If you saw a particular wireless card connect successfully to a wireless
network using Microsoft Windows 98, you now know that that wireless
card has working hardware. There is no guarantee, however, that Debian
has a software driver that will talk to the card. What I do personally,
when I need a wireless card, is I go to the local second-hand computer
gear market with my laptop and physically test *any* PCMCIA card
(wireless or otherwise) to verify it works with Debian before I buy it.
Depending on where you live, that may or may not be easy. This is the
list of wireless cards I have right now:
[url]http://blog.langex.net/index.cgi/xHW/wirelessCards/index[/url]
[color=blue]
> My first question concerns the cable connexion between the router
> Fonera and my pcmcia Ethernet cards. My first Ethernet card, the IBM[/color]

Do not worry (much) about the cable that comes with a particular
Ethernet card. If the plug fits in the socket, and you can make the
card work in any environment using any OS, you know the card and the
cable are good. Then if you trouble in a different environment, the
problem probably lies with either the network configuration of your OS
or the router you are trying to connect to.
[color=blue]
> converters are concerned, but, once done, the Fonera does not respond
> to calls to its addresses 169.254.255.1 and 192.168.1.1, while it
> does with the other plugging system, at least under Windows. Is this
> normal, or have I missed something ? In any case, how can I solve[/color]

If you successfully connected to the Fonera with this same card using a
Windows system, then there is no problem with card or Fonera.
Networking is not properly configured on your Debian system.
[color=blue]
> this problem ? which Ethernet pcmcia card will have the same
> plugging system as the EtherJet card as well as being workable under
> Linux ? From the above report of trials, I am unable to know whether
> the fact that I cannot run this system under Linux is due to this
> system or to the connection mode...[/color]

Again, do not worry about what the cable looks like, as long as you know
the cable works. I think this is the chapter of the manual that you are
looking for:
[url]http://www.debian.org/doc/manuals/reference/ch-gateway.en.html#s-net-high[/url]
I don't know anything about Fonera's, but most routers by default run
DHCP networks, so you *probably* need to to configure your ethernet
interface for DHCP, ie. if your card is eth0, make
sure /etc/network/interfaces contains this line:

iface eth0 inet dhcp

then as root in a terminal, execute these two commands:

ifdown eth0
ifup eth0

If it works, you will see an IP address assigned in your terminal.

Clayton


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

Hello,

On Wed, 2008-10-29 at 00:44 +0100, Bernard wrote:[color=blue]
>
> I would like to install wireless facilities on my old Thinkpad. It has
> a 300 Mhz processor, 128 MB of RAM, and 4.1 GB of space on hard disk.
> It used to run on RedHat 7.2, which stayed there for about six years
> without any problem. Since I have been unable to get wireless working
> on it using pcmcia IBM 'EtherJet' card and a router in client mode
> 'FON2200' (the so called Fonera), I installed Debian Sarge instead of
> RedHat 7.2.[/color]

Keep in mind that Debian Sarge was discontinued since March 2008 [1].[color=blue]
>From your point of view, this mainly means that it has no security[/color]
update.
Debian Sarge[2a], Etch[2b] and Lenny[2c] seems to have the same RAM
requirements. You might want to install XFCE desktop rather that the
default desktop (gnome) as explained in [2c].

Franklin

[1] [url]http://www.debian.org/News/2008/20080229[/url]
[2a] [url]http://www.debian.org/releases/sarge/i386/ch03s04.html[/url]
[2b] [url]http://www.debian.org/releases/etch/i386/ch03s04.html[/url]
[2c] [url]http://www.debian.org/releases/lenny/i386/ch03s04.html[/url]


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Wed, 29 Oct 2008 08:15:14 +0100
Frank Lin PIAT <fpiat@klabs.be> wrote:
[color=blue]
> Hello,
>
> On Wed, 2008-10-29 at 00:44 +0100, Bernard wrote:[color=green]
> >
> > router in client mode 'FON2200' (the so called Fonera), I installed
> > Debian Sarge instead of RedHat 7.2.[/color]
>
> Keep in mind that Debian Sarge was discontinued since March 2008 [1].
> From your point of view, this mainly means that it has no security
> update.
> Debian Sarge[2a], Etch[2b] and Lenny[2c] seems to have the same RAM
> requirements. You might want to install XFCE desktop rather that the
> default desktop (gnome) as explained in [2c].[/color]

All good advice, but.... to add some bad news, support for older
hardware sometimes seems to be going more then it is coming lately. I
also have a Thinkpad 600e, as well as, for the record, a Pentium III
Thinkpad a21m. Both have the misfortune to have sound cards that the
Debian project has declared "evil" and blacklisted, apparently because
of non-open firmware issues. The snd_cs46xx driver has been booted out
of the kernel [3a], and both of these machines are now without sound (I
am guessing if I rolled my own kernel.org kernel, it would work, but I
have not tried):

Thinkpad 600e:
00:06.0 Multimedia audio controller: Cirrus Logic CS 4610/11
[CrystalClear SoundFusion Audio Accelerator] (rev 01)

Thinkpad a21m
00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30
[CrystalClear SoundFusion Audio Accelerator] (rev 01)

To add to the mayhem, I also have a Pentium III Thinkpad i1300, and the
current Debian kernel linux-image-2.6.26-1-686 panics on boot, every
time[3b]. Hopefully this will go away soon, meanwhile I use older
kernels, but.... This same Thinkpad i1300 had Xorg stop working more
then a year ago[3c]. I have not actually tried (it is currently doing
duty as a server) but if I wanted it fully functional, I would probably
have to downgrade to at least Etch.

Perhaps this is not a trend and I am just extraordinarily unlucky....

So I would also advise the original poster to upgrade to Lenny, just
be aware that you may have to run an older kernel, or build your own
kernel.org kernel, if you want the on-board sound card to work.
Personally, I just use USB sound.

Clayton

[3a] [url]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462035[/url]
[3b] [url]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=501118[/url]
[3c] [url]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428711[/url]


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Wed, Oct 29, 2008 at 09:29:08PM +0800, Clayton wrote:[color=blue]
> On Wed, 29 Oct 2008 08:15:14 +0100
> Frank Lin PIAT <fpiat@klabs.be> wrote:
>
> ...
>
> All good advice, but.... to add some bad news, support for older
> hardware sometimes seems to be going more then it is coming lately. I
> also have a Thinkpad 600e, as well as, for the record, a Pentium III
> Thinkpad a21m. Both have the misfortune to have sound cards that the
> Debian project has declared "evil" and blacklisted, apparently because
> of non-open firmware issues. The snd_cs46xx driver has been booted out[/color]

I have a 600E and had no end of trouble with the sound card. I posted
questions to this list a long time ago and the one suggestion that
worked was to compile a kernel without the cs46xx driver.

It appears that the kernel insisted on loading this in preference to
other drivers and the sound hardware didn't work, even when I
blacklisted it and forcefully inserted the proper one. I presume that
by that time the resources had been marked as used, or initialized in
some way that made them unusable.
[color=blue]
> of the kernel [3a], and both of these machines are now without sound (I
> am guessing if I rolled my own kernel.org kernel, it would work, but I
> have not tried):[/color]

Since I had that issue, I compiled a debian kernel (2.6.18), the debian
way with the debian tools, without the cs46xx driver, but with the cs4231
driver. The sound card works just fine.
[color=blue]
> Thinkpad 600e:
> 00:06.0 Multimedia audio controller: Cirrus Logic CS 4610/11
> [CrystalClear SoundFusion Audio Accelerator] (rev 01)[/color]

That's the exact one I have.
[color=blue]
> Thinkpad a21m
> 00:05.0 Multimedia audio controller: Cirrus Logic CS 4614/22/24/30
> [CrystalClear SoundFusion Audio Accelerator] (rev 01)[/color]

I wouldn't be surprised if the same driver (cs4231) would work on this
machine. Maybe at least a subset of features?
[color=blue]
> To add to the mayhem, I also have a Pentium III Thinkpad i1300, and the
> ...[/color]

Can't offer any specific help about the other problems...

A.


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

A. F. Cano wrote:[color=blue]
> I have a 600E and had no end of trouble with the sound card. I posted
> questions to this list a long time ago and the one suggestion that
> worked was to compile a kernel without the cs46xx driver.
>
> It appears that the kernel insisted on loading this in preference to
> other drivers and the sound hardware didn't work, even when I
> blacklisted it and forcefully inserted the proper one. I presume that
> by that time the resources had been marked as used, or initialized in
> some way that made them unusable.[/color]

One option that has worked for me in other similar but different
situations is to move/remove the module from the filesystem. With it
gone from the disk the kernel couldn't load it. That worked for me
without needing to recompile the kernel without the module.

Bob

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJCQmi0pRcO8E2ULYRAoFYAJwMSvuwBY38JBKPpEZDevq8KegxIgCfS/nk
5oLLv2dTclQ2SzuU5kaDI/s=
=Q+p4
-----END PGP SIGNATURE-----

On Wed, Oct 29, 2008 at 11:10 PM, Bob Proulx <bob@proulx.com> wrote:
[color=blue]
> One option that has worked for me in other similar but different
> situations is to move/remove the module from the filesystem. With it
> gone from the disk the kernel couldn't load it. That worked for me
> without needing to recompile the kernel without the module.
>[/color]

Why not put a blacklist entry in /etc/modprobe.d? Use as a model
entries already there.

--
A. C. Censi
accensi [em] gmail [ponto] com
accensi [em] montreal [ponto] com [ponto] br


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

A. C. Censi wrote:[color=blue]
> Bob Proulx wrote:[color=green]
> > One option that has worked for me in other similar but different
> > situations is to move/remove the module from the filesystem. With it
> > gone from the disk the kernel couldn't load it. That worked for me
> > without needing to recompile the kernel without the module.[/color]
>
> Why not put a blacklist entry in /etc/modprobe.d? Use as a model
> entries already there.[/color]

The answer to this question was in the part I quoted from and was
responding to:

A. F. Cano wrote:[color=blue]
> It appears that the kernel insisted on loading this in preference to
> other drivers and the sound hardware didn't work, even when I
> blacklisted it and forcefully inserted the proper one. I presume that
> by that time the resources had been marked as used, or initialized in
> some way that made them unusable.[/color]

As you can see I was well aware of the module blacklist functionality.
It was used but did not prevent the problem.

I can only add to the fud here by saying I have seen similar problems
in the past. Even though the module was blacklisted this didn't seem
to be enough to avoid the problem. Only by making sure that it was
not possible to load the module could I avoid the problem. It appears
by A. F. Cano's posting that I was not the only one with that issue.

I do not know because I was not able to debug this to root cause but I
will guess that there were scripts where the loading of the module was
hard coded. I will guess that these scripts did not consult the
blacklist.

Again I do not know if any of those problems historically seen are
still active today. Time goes by, old bugs are fixed, new bugs are
created, and the world doesn't stay the same. I am not currently
having any problems of this type but have moved on to more mainstream
hardware too.

Bob

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJCd9X0pRcO8E2ULYRAiwmAJwPwH0exckNAjjMuZNwvxGzvf9GPwCfT9h+
3yapr480D1OXDNxEPjo7U60=
=P6c/
-----END PGP SIGNATURE-----

The problem with sound on 600E is I understand a Historical one. I
owned the 600E for sometime and had faced this problem.
I remember that the problem is the fact that though the 600E sound
chip is of a particular make, it is detected as something else.

I remember solving it by uninstalling discover and a combination of
blacklisting and modprobing the right drivers(not sure though)
Its been years since I parted with the 600E.

thinkwiki describes this problem:

[url]http://www.thinkwiki.org/wiki/Problem_with_broken_sound_on_ThinkPad_600[/url]

And am sure there would a a lot and lot of google hits for the same,
because like I mentioned it is a very well known problem.



On Thu, Oct 30, 2008 at 9:52 PM, Bob Proulx <bob@proulx.com> wrote:[color=blue]
> A. C. Censi wrote:[color=green]
>> Bob Proulx wrote:[color=darkred]
>> > One option that has worked for me in other similar but different
>> > situations is to move/remove the module from the filesystem. With it
>> > gone from the disk the kernel couldn't load it. That worked for me
>> > without needing to recompile the kernel without the module.[/color]
>>
>> Why not put a blacklist entry in /etc/modprobe.d? Use as a model
>> entries already there.[/color]
>
> The answer to this question was in the part I quoted from and was
> responding to:
>
> A. F. Cano wrote:[color=green]
>> It appears that the kernel insisted on loading this in preference to
>> other drivers and the sound hardware didn't work, even when I
>> blacklisted it and forcefully inserted the proper one. I presume that
>> by that time the resources had been marked as used, or initialized in
>> some way that made them unusable.[/color]
>
> As you can see I was well aware of the module blacklist functionality.
> It was used but did not prevent the problem.
>
> I can only add to the fud here by saying I have seen similar problems
> in the past. Even though the module was blacklisted this didn't seem
> to be enough to avoid the problem. Only by making sure that it was
> not possible to load the module could I avoid the problem. It appears
> by A. F. Cano's posting that I was not the only one with that issue.
>
> I do not know because I was not able to debug this to root cause but I
> will guess that there were scripts where the loading of the module was
> hard coded. I will guess that these scripts did not consult the
> blacklist.
>
> Again I do not know if any of those problems historically seen are
> still active today. Time goes by, old bugs are fixed, new bugs are
> created, and the world doesn't stay the same. I am not currently
> having any problems of this type but have moved on to more mainstream
> hardware too.
>
> Bob
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFJCd9X0pRcO8E2ULYRAiwmAJwPwH0exckNAjjMuZNwvxGzvf9GPwCfT9h+
> 3yapr480D1OXDNxEPjo7U60=
> =P6c/
> -----END PGP SIGNATURE-----
>
>[/color]


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

Hi Clayton, Hi to everyone,

Le Wed, 29 Oct 2008 07:40:07 +0100, Clayton a écrit*:
[color=blue]
> Hi Bernard,
>[/color]
[color=blue]
>[color=green]
>> My first question concerns the cable connexion between the router
>> Fonera and my pcmcia Ethernet cards. My first Ethernet card, the IBM[/color]
>
> Do not worry (much) about the cable that comes with a particular
> Ethernet card. If the plug fits in the socket, and you can make the
> card work in any environment using any OS, you know the card and the
> cable are good. Then if you trouble in a different environment, the
> problem probably lies with either the network configuration of your OS
> or the router you are trying to connect to.
>
>
> If you successfully connected to the Fonera with this same card using a
> Windows system, then there is no problem with card or Fonera.
> Networking is not properly configured on your Debian system.
>[color=green]
>> this problem ? which Ethernet pcmcia card will have the same
>> plugging system as the EtherJet card as well as being workable under
>> Linux ? From the above report of trials, I am unable to know whether
>> the fact that I cannot run this system under Linux is due to this
>> system or to the connection mode...[/color]
>
> Again, do not worry about what the cable looks like, as long as you know
> the cable works. I think this is the chapter of the manual that you are
> looking for:
> [url]http://www.debian.org/doc/manuals/reference/ch-gateway.en.html#s-net-high[/url][/color]


This is an interresting document for me. I read it and bookmarked it,
since I am sure that I will soon get back to it. Still, at this stage, I
can't figure how I am going to get on the way with this router
"fonera". I got something new though. At first, I must point out that I
have installed ETCH instead of the Sarge that I had. The problems that I
had encountered with X environment have been mostly solved to a point that
I now get a workable environment. On that ETCH system, when the router
FONERA is cabled to the pcmcia D-Link Ethernet card, 'ifconfig' gives me
this :

#ifconfig
eth0 Encap link:Ethernet HWaddr 00:80:.....
UP BROADCAST RUNNING...
..............
etc..

eth0:3 Encap link: Ethernet HWadr 00:80:..... (same address as above)
inet adr:169.254.12.9 Broadcast:169.254.255.255 netmask:255.255.0.0
UP BROADCASST RUNNING MULTICAST MTU:1500 ...
Interruption: 3 Base address:0x300

lo Encap link: Local loop
inet adr:127.0.0.1
UP LOOPBACK RUNNING ...
.........
etc..

eth0:3 ?? What on Earth is this ? I have never seen anything like
this... this eth0:3 only appears after a few 2-3 minutes. The IP address
that it bears (169.254.12.9) is of the same domain as that of the given
address of the 'FONERA' (169.254.255.1)

If the ifconfig test is being done
right after boot, eth0:3 does not show. Furthermore, after another while
(or after the call of another function, I can't remember for sure),
iwconfig mentions, besides 'lo', 'eth0' and 'irda0', something else that
is called 'sit0'.

I have not so far been able to 'enter' this router using Firefox/Iceweasel
by any of the addresses that worked under Microsoft Windows :
169.254.255.1, and, since I switched it into "client" mode :
192.168.1.1.

So far, I really don't know what I should try next, and how am I going to
use this router in client mode as a medium to get Wireless connexion to
my DSL router and, from there, to the Internet.

Thanks in advance for more hints.





[color=blue]
> I don't know anything about Fonera's, but most routers[/color]
by default run[color=blue]
> DHCP networks, so you *probably* need to to configure your ethernet
> interface for DHCP, ie. if your card is eth0, make sure
> /etc/network/interfaces contains this line:
>
> iface eth0 inet dhcp
>
> then as root in a terminal, execute these two commands:
>
> ifdown eth0
> ifup eth0
>
> If it works, you will see an IP address assigned in your terminal.[/color]

Yes, this works all right with my DSL box/router whenever the appropriate
cable is there, as my /etc/network/interfaces file does contain 'iface
eth0 inet dhcp', but I don't know how to get my other router 'FONERA' to
work and wirelessly connect to said DSL/router.

When the cable links the Fonera instead of the DSL box/router, the 'ifup
eth0' command shows repeated attempts :

DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
.....
No DHCPOFFERS received
No working leases in persistent database - sleeping


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Fri, 31 Oct 2008 00:47:19 +0100
Bernard <bdebreil@teaser.fr> wrote:
[color=blue]
> Hi Clayton, Hi to everyone,
>
> Le Wed, 29 Oct 2008 07:40:07 +0100, Clayton a écrit*:
>
> router "fonera". I got something new though. At first, I must point
> out that I have installed ETCH instead of the Sarge that I had. The
> problems that I had encountered with X environment have been mostly
> solved to a point that I now get a workable environment. On that ETCH
> system, when the router FONERA is cabled to the pcmcia D-Link
> Ethernet card, 'ifconfig' gives me this :
>
> #ifconfig
> eth0 Encap link:Ethernet HWaddr 00:80:.....
> UP BROADCAST RUNNING...
> ..............
> etc..
>
> eth0:3 Encap link: Ethernet HWadr 00:80:..... (same address as
> above) inet adr:169.254.12.9 Broadcast:169.254.255.255
> netmask:255.255.0.0 UP BROADCASST RUNNING MULTICAST MTU:1500 ...
> Interruption: 3 Base address:0x300
>
> lo Encap link: Local loop
> inet adr:127.0.0.1
> UP LOOPBACK RUNNING ...
> .........
> etc..
>
> eth0:3 ?? What on Earth is this ? I have never seen anything like
> this... this eth0:3 only appears after a few 2-3 minutes. The IP
> address that it bears (169.254.12.9) is of the same domain as that of
> the given address of the 'FONERA' (169.254.255.1)[/color]

I am far from an expert on networking, but your "eth0:3" looks like a
virtual interface: [url]http://handsonhowto.com/virt.html[/url]

This should not appear spontaneously, perhaps grep /etc for "eth0:3"
and see what might be causing this? Maybe try
deleting /etc/udev/rules.d/70-persistent-net.rules and reboot? (I am
grasping at straws, but I am recalling having a major headache
with that persistent-net.rules during a past upgrade.....)
[color=blue]
> If the ifconfig test is being done
> right after boot, eth0:3 does not show. Furthermore, after another
> while (or after the call of another function, I can't remember for
> sure), iwconfig mentions, besides 'lo', 'eth0' and 'irda0', something
> else that is called 'sit0'.
>
> I have not so far been able to 'enter' this router using
> Firefox/Iceweasel by any of the addresses that worked under Microsoft
> Windows : 169.254.255.1, and, since I switched it into "client" mode :
> 192.168.1.1.
>
> So far, I really don't know what I should try next, and how am I
> going to use this router in client mode as a medium to get Wireless
> connexion to my DSL router and, from there, to the Internet.[/color]

I think you need to figure out where it is coming from / get rid of that
eth0:3 thing before worrying about networking. This is totally
non-standard behavior, and I too have never seen that happen before....
[color=blue][color=green]
> > I don't know anything about Fonera's, but most routers[/color]
> by default run[color=green]
> > DHCP networks, so you *probably* need to to configure your ethernet
> > interface for DHCP, ie. if your card is eth0, make sure
> > /etc/network/interfaces contains this line:
> >
> > iface eth0 inet dhcp
> >
> > then as root in a terminal, execute these two commands:
> >
> > ifdown eth0
> > ifup eth0
> >
> > If it works, you will see an IP address assigned in your terminal.[/color]
>
> Yes, this works all right with my DSL box/router whenever the
> appropriate cable is there, as my /etc/network/interfaces file does
> contain 'iface eth0 inet dhcp', but I don't know how to get my other
> router 'FONERA' to work and wirelessly connect to said DSL/router.
>
> When the cable links the Fonera instead of the DSL box/router, the
> 'ifup eth0' command shows repeated attempts :
>
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
> ....
> No DHCPOFFERS received
> No working leases in persistent database - sleeping[/color]

ifconfig lists all active ("up") network interfaces.
"ifconfig -a" lists all installed network interfaces, whether they are
active or not.

The one you want to use (eth0, eth1, eth2, ...., wlan0, maybe even
eth0:3) should be represented in the /etc/network/interfaces file per
above. As long as you are doing ifup on the right one, it should work
if there is nothing wrong with your router (unlikely since Windows
works?) or there is something more subtle wrong on your end. Try ifup
on eth0:3. Try to get rid of eth0:3 because it is muddying the water.

Clayton


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

Le Fri, 31 Oct 2008 06:00:12 +0100, Clayton a écrit:
[color=blue]
> On Fri, 31 Oct 2008 00:47:19 +0100
> Bernard <bdebreil@teaser.fr> wrote:
>[color=green]
>> Hi Clayton, Hi to everyone,
>>
>> Le Wed, 29 Oct 2008 07:40:07 +0100, Clayton a écritÂ*:
>>
>>
>>
>>[/color]
>
> This should not appear spontaneously, perhaps grep /etc for "eth0:3"
> and see what might be causing this? Maybe try
> deleting /etc/udev/rules.d/70-persistent-net.rules and reboot? (I am
> grasping at straws, but I am recalling having a major headache
> with that persistent-net.rules during a past upgrade.....)[/color]

I have searched and not found any track of "eth0:3". There may be a
misunderstanding about what it really means. Now that I have installed PAN
on that Thinkpad 600, it becomes feasable to use copy/paste, so, here is
what I get, WHILE MY PCMCIA ETHERNET CARD IS CABLED TO MY DSL BOX/ROUTER :

begin copy/paste *******************
localhost:/home/bd# ifconfig
eth0 Lien encap:Ethernet HWaddr 00:80:C8:B9:FD:C5
inet adr:192.168.1.11 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::280:c8ff:feb9:fdc5/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14341 errors:0 dropped:0 overruns:0 frame:0
TX packets:8987 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:19481548 (18.5 MiB) TX bytes:778010 (759.7 KiB)
Interruption:3 Adresse de base:0x300

lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

localhost:/home/bd# iwconfig

lo no wireless extensions.

irda0 no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

end copy/paste ******************************


Funny enough this 'sit0'. I don't now what it is ; it appears sometimes, I
thought it did happen only when the FONERA router was cabled in, but this
is not the case for now.

now, here were the contents of /etc/network/interfaces :

begin copy/paste ************

This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

localhost:/home/bd#

end copy/paste ********************

Now I just carried a new test. I unplugged the cable coming from the DSL
box/router that provides my internet connexion ; instead I plugged the
cable coming from the FONERA/routeur, that is, I plugged it onto the
pcmcia ethernet card slot. I changed the /etc/network/interfaces file,
which I made as follows :

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 169.254.255.1
netmask 255.255.0.0
gateway 169.254.255.1

end copy/paste ******************

This being done, I launched a network restart:

/etc/init.d/networking restart :

localhost:/etc/network# /etc/init.d/networking restart
Reconfiguring network interfaces...done.

OK

Now : ifup eth0. No reply, just the shell back, which means 'OK'

Why 'ifup', not 'ifconfig' ? I have read a bit more of the document you
pointed to me yesterday. Amongst a lot of other things, it is being said
that it is unwise to play both with 'low level network configuration
tools' and 'high level tools', since several bugs may show, for instance
if you have configured once with ifconfig and then change something else
using ifup ou ifdown, the proper config files may have not been updated
allright and your system may show something that is gone or vice versa.
The 'eth0:3' may be due to such kind of messing around. So, from now on, I
still use 'ifconfig' with no argument so as to see what it says, but for
anything else I use 'ifupdown'. So, here is what I get with 'ifconfig'
alone :

start copy/paste ***************

localhost:/etc/network# ifconfig
eth0 Lien encap:Ethernet HWaddr 00:80:C8:B9:FD:C5
inet adr:169.254.255.1 Bcast:169.254.255.255 Masque:255.255.0.0
adr inet6: fe80::280:c8ff:feb9:fdc5/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14415 errors:0 dropped:0 overruns:0 frame:0


localhost:/etc/network# iwconfig
lo no wireless extensions.

irda0 no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.


localhost:/etc/network# ifconfig -a
eth0 Lien encap:Ethernet HWaddr 00:80:C8:B9:FD:C5
inet adr:169.254.255.1 Bcast:169.254.255.255 Masque:255.255.0.0
adr inet6: fe80::280:c8ff:feb9:fdc5/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14415 errors:0 dropped:0 overruns:0 frame:0
TX packets:9193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:19491975 (18.5 MiB) TX bytes:793654 (775.0 KiB)
Interruption:3 Adresse de base:0x300

irda0 Lien encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:8
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3412 (3.3 KiB) TX bytes:3412 (3.3 KiB)

sit0 Lien encap:IPv6-dans-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

localhost:/etc/network#

end copy/paste *******************

Now, in this state, that is, with eth0 configured with the FONERA address,
what should I do so as to go further, I mean, to make sure that this
address - that pings all-right - really comes from the FONERA, and how can
I get that FONERA to wireless connect to my DSL box/router and bring an
internet connexion up ?
[color=blue]
>[/color]


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

From: bernard <bdebreil@teaser.fr>
Subject: Re: wireless on an old Thinkpad 600
Newsgroups: linux.debian.laptop
References: <bs613-4hg-19@gated-at.bofh.it> <bscSP-4wf-5@gated-at.bofh.it>
<bsPKu-4lv-3@gated-at.bofh.it> <bsUhd-1rI-5@gated-at.bofh.it>
X-Draft-Attribution: Le Fri, 31 Oct 2008 06:00:12 +0100, Clayton a écrit:
X-Draft-Attribution-Author: Clayton <ckoeni@gmail.com>
X-Draft-Attribution-Date: Fri, 31 Oct 2008 06:00:12 +0100
X-Draft-Attribution-Id: [email]bsUhd-1rI-5@gated-at.bofh.it[/email]
User-Agent: pan 0.119 (Karma Hunters)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le Fri, 31 Oct 2008 06:00:12 +0100, Clayton a écrit:
[color=blue]
> On Fri, 31 Oct 2008 00:47:19 +0100
> Bernard <bdebreil@teaser.fr> wrote:
>[color=green]
>> Hi Clayton, Hi to everyone,
>>
>> Le Wed, 29 Oct 2008 07:40:07 +0100, Clayton a écritÂ*:
>>
>>
>>
>>[/color]
>
> This should not appear spontaneously, perhaps grep /etc for "eth0:3"
> and see what might be causing this? Maybe try
> deleting /etc/udev/rules.d/70-persistent-net.rules and reboot? (I am
> grasping at straws, but I am recalling having a major headache
> with that persistent-net.rules during a past upgrade.....)[/color]

I have searched and not found any track of "eth0:3". There may be a
misunderstanding about what it really means. Now that I have installed PAN
on that Thinkpad 600, it becomes feasable to use copy/paste, so, here is
what I get, WHILE MY PCMCIA ETHERNET CARD IS CABLED TO MY DSL BOX/ROUTER :

begin copy/paste *******************
localhost:/home/bd# ifconfig
eth0 Lien encap:Ethernet HWaddr 00:80:...
inet adr:192.168.1.11 Bcast:192.168.1.255 Masque:255.255.255.0
adr inet6: fe80::280:c8ff:feb9:fdc5/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14341 errors:0 dropped:0 overruns:0 frame:0
TX packets:8987 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:19481548 (18.5 MiB) TX bytes:778010 (759.7 KiB)
Interruption:3 Adresse de base:0x300

lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

localhost:/home/bd# iwconfig

lo no wireless extensions.

irda0 no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.

end copy/paste ******************************


Funny enough this 'sit0'. I don't now what it is ; it appears sometimes, I
thought it did happen only when the FONERA router was cabled in, but this
is not the case for now.

now, here were the contents of /etc/network/interfaces :

begin copy/paste ************

This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

localhost:/home/bd#

end copy/paste ********************

Now I just carried a new test. I unplugged the cable coming from the DSL
box/router that provides my internet connexion ; instead I plugged the
cable coming from the FONERA/routeur, that is, I plugged it onto the
pcmcia ethernet card slot. I changed the /etc/network/interfaces file,
which I made as follows :

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 169.254.255.1
netmask 255.255.0.0
gateway 169.254.255.1

end copy/paste ******************

This being done, I launched a network restart:

/etc/init.d/networking restart :

localhost:/etc/network# /etc/init.d/networking restart
Reconfiguring network interfaces...done.

OK

Now : ifup eth0. No reply, just the shell back, which means 'OK'

Why 'ifup', not 'ifconfig' ? I have read a bit more of the document you
pointed to me yesterday. Amongst a lot of other things, it is being said
that it is unwise to play both with 'low level network configuration
tools' and 'high level tools', since several bugs may show, for instance
if you have configured once with ifconfig and then change something else
using ifup ou ifdown, the proper config files may have not been updated
allright and your system may show something that is gone or vice versa.
The 'eth0:3' may be due to such kind of messing around. So, from now on, I
still use 'ifconfig' with no argument so as to see what it says, but for
anything else I use 'ifupdown'. So, here is what I get with 'ifconfig'
alone :

start copy/paste ***************

localhost:/etc/network# ifconfig
eth0 Lien encap:Ethernet HWaddr 00:80:C8:B9:FD:C5
inet adr:169.254.255.1 Bcast:169.254.255.255 Masque:255.255.0.0
adr inet6: fe80::280:c8ff:feb9:fdc5/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14415 errors:0 dropped:0 overruns:0 frame:0


localhost:/etc/network# iwconfig
lo no wireless extensions.

irda0 no wireless extensions.

eth0 no wireless extensions.

sit0 no wireless extensions.


localhost:/etc/network# ifconfig -a
eth0 Lien encap:Ethernet HWaddr 00:80:C8:B9:FD:C5
inet adr:169.254.255.1 Bcast:169.254.255.255 Masque:255.255.0.0
adr inet6: fe80::280:c8ff:feb9:fdc5/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14415 errors:0 dropped:0 overruns:0 frame:0
TX packets:9193 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:19491975 (18.5 MiB) TX bytes:793654 (775.0 KiB)
Interruption:3 Adresse de base:0x300

irda0 Lien encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:8
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:3412 (3.3 KiB) TX bytes:3412 (3.3 KiB)

sit0 Lien encap:IPv6-dans-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

localhost:/etc/network#

end copy/paste *******************

Now, in this state, that is, with eth0 configured with the FONERA address,
what should I do so as to go further, I mean, to make sure that this
address - that pings all-right - really comes from the FONERA, and how can
I get that FONERA to wireless connect to my DSL box/router and bring an
internet connexion up ?


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Thu, 30 Oct 2008 23:10:56 +0530
"justin joseph" <justinjoseph007@gmail.com> wrote:
[color=blue]
> The problem with sound on 600E is I understand a Historical one. I
> owned the 600E for sometime and had faced this problem.
> I remember that the problem is the fact that though the 600E sound
> chip is of a particular make, it is detected as something else.
>
> I remember solving it by uninstalling discover and a combination of
> blacklisting and modprobing the right drivers(not sure though)
> Its been years since I parted with the 600E.
>
> thinkwiki describes this problem:
>
> [url]http://www.thinkwiki.org/wiki/Problem_with_broken_sound_on_ThinkPad_600[/url]
>
> And am sure there would a a lot and lot of google hits for the same,
> because like I mentioned it is a very well known problem.[/color]

Indeed, there is an awful lot of advice out there about how to get the
600 / 600e's sound working, and everyone's advice seems to be a little
different. I burnt off three more hours this eve trying the above
thinkwiki suggestions for my 600e, plus various other ALSA module
blacklist / modprobe voodoo, all to no avail. Another machine that does
not work with ALSA....

Actually, the root problem is probably deeper then ALSA (IRQ conflict?)
as in its current state, not even USB audio works for me. USB audio has
*always* worked on my other machines, without exception.

Clayton


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On 31 Oct 2008 12:06:40 GMT
bernard <bdebreil@teaser.fr> wrote:
[color=blue]
> the /etc/network/interfaces file, which I made as follows :
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet static
> address 169.254.255.1
> netmask 255.255.0.0
> gateway 169.254.255.1[/color]

This looks wrong. Normally your router is at 169.254.255.1, which is
why you set "gateway 169.254.255.1". You then set your own static IP to
something higher, 169.254.255.2 for instance.
[color=blue]
> Now, in this state, that is, with eth0 configured with the FONERA
> address, what should I do so as to go further, I mean, to make sure
> that this address - that pings all-right - really comes from the
> FONERA, and how can I get that FONERA to wireless connect to my DSL
> box/router and bring an internet connexion up ?[/color]

If your router is at 169.254.255.1, and your eth0 is set to
169.254.255.2, you should be able to ping 169.254.255.1 if all is well.
Most routers provide a control interface if you point your web browser
at them, in this case, point your browser at 169.254.255.1. I don't
know anything about the Fonera, which I believe is a somewhat
non-standard router, so once you have established control of the router,
perhaps specific questions about configuration should be addressed to
their own forum: [url]http://boards.fon.com/[/url]

Clayton


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Sat, Nov 01, 2008 at 01:44:19PM +0800, Clayton wrote:[color=blue]
> On 31 Oct 2008 12:06:40 GMT
> bernard <bdebreil@teaser.fr> wrote:
>[color=green]
> > the /etc/network/interfaces file, which I made as follows :
> >
> > # The loopback network interface
> > auto lo
> > iface lo inet loopback
> >
> > # The primary network interface
> > allow-hotplug eth0
> > iface eth0 inet static
> > address 169.254.255.1
> > netmask 255.255.0.0
> > gateway 169.254.255.1[/color][/color]

you should use 169.254.1.0 to 169.254.254.255 for 'address' and 'gateway',
as 169.254.0.x and 169.254.255.x are reserved - see
[url]http://www.ietf.org/rfc/rfc3927.txt[/url]
Anyway, you shouldn't use static 169.254/16 at all:

[from RFC above]
....

1.6. Alternate Use Prohibition

Note that addresses in the 169.254/16 prefix SHOULD NOT be configured
manually or by a DHCP server. Manual or DHCP configuration may cause
a host to use an address in the 169.254/16 prefix without following
the special rules regarding duplicate detection and automatic
configuration that pertain to addresses in this prefix.
...
Administrators wishing to configure their own local addresses (using
manual configuration, a DHCP server, or any other mechanism not
described in this document) should use one of the existing private
address prefixes [RFC1918], not the 169.254/16 prefix.
....

Instead you should use an address from any of the private ranges:

Class Networks
A 10.0.0.0 through 10.255.255.255
B 172.16.0.0 through 172.31.0.0
C 192.168.0.0 through 192.168.255.0

--
paolo


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

Clayton wrote:
[color=blue]
>On 31 Oct 2008 12:06:40 GMT
>bernard <bdebreil@teaser.fr> wrote:
>
>
>[color=green]
>>the /etc/network/interfaces file, which I made as follows :
>>
>># The loopback network interface
>>auto lo
>>iface lo inet loopback
>>
>># The primary network interface
>>allow-hotplug eth0
>>iface eth0 inet static
>> address 169.254.255.1
>> netmask 255.255.0.0
>> gateway 169.254.255.1
>>
>>[/color]
>
>This looks wrong. Normally your router is at 169.254.255.1, which is
>why you set "gateway 169.254.255.1". You then set your own static IP to
>something higher, 169.254.255.2 for instance.
>
>
>[color=green]
>>Now, in this state, that is, with eth0 configured with the FONERA
>>address, what should I do so as to go further, I mean, to make sure
>>that this address - that pings all-right - really comes from the
>>FONERA, and how can I get that FONERA to wireless connect to my DSL
>>box/router and bring an internet connexion up ?
>>
>>[/color]
>
>If your router is at 169.254.255.1, and your eth0 is set to
>169.254.255.2, you should be able to ping 169.254.255.1 if all is well.
>
>[/color]

I have indeed been able to ping 169.254.255.1, and it pinged allright.
But I am not sure whether I was really pinging the Fonera or playing
virtual, since such pinging also worked when the cable to the FONERA was
being disconnected. Ping did work anytime as long as I had put said
address in the iface command of the /etc/network/interfaces file.
[color=blue]
>Most routers provide a control interface if you point your web browser
>at them, in this case, point your browser at 169.254.255.1.
>[/color]

Well, this interface I can connect to, via Internet Explorer under
Microsoft Windows. With Firefox under Debian Linux, I have been able to
connect only once ; I can't remember whether it was with my Desktop or
my laptop ; the former has a Wireless card installed, the latter does
not, which normally should not make any difference, but it may still do.
Browsing Google lead me to links and documents coming from people using
the Fonera, either under MSWIN on on various Linux distros. All of them
use that Fonera, not in a client mode as I wish to, but so as to provide
internet connexions for other PC ; therefore their Fonera is being cable
connected, not to one computer, but to their DSL box/router. So, I can't
really get much of their experience. However, as far as connecting to
the fonera interface, they mostly agree that is not very easy : Once you
have connected once, you have to keep connecting from same computer all
the time, if you try connecting from another PC, it will fail and then
you are no longer able to connect with the original computer either.
When this locking happens, you must re-initialize the internal program
of your Fonera, which is a very hazardous and complicate process : press
the underneath reset button using a pin or other tool, keep it pressed
for at least 30 seconds, or until such light comes out on your module,
then unplug the power inlet while you keep the init button pressed, keep
it that way for at least 45 seconds or until such or such light goes out
or on (can' remember exactly), then plug again and keep pressing, then
45 seconds later you release the pressure on the init button... and then
you wait at least 15 minutes before you try connecting to the internal
system with your browser... One contributor admitted that he had to
re-do that init process 6 times before he could again connect...

Well, this is it, I give up. I would have given up a lot earlier than
that, had it not be that I have seen this system working on my laptop
under Microsoft Windows 98, as a router on client mode, cabled connected
to the outlet of my EtherJet pcmcia card, getting a workable internet
wireless connexion even though I don't have a WiFi card installed on
this laptop. True enough, the only time I have seem this working on my
laptop under MSWIN was with that EtherJet card, not with the D-Link 660
card which I now use, since EtherJet is not being reckognized by my
Linux system. In order to try learning something more, I have more
recently tested that Fonera again on my desktop under Mswin XP, that is,
without pcmcia card but with a wireless card inside. It did work and i
got a wireless internet connexion through my fonera - not through my
wireless card, but this connexion was not workable. i mean that the
mswin system said that the connexion was OK, at an address compatible to
my dsl/router, that it was a good connexion with 100% packages OK etc...
but then I could not connect to anything on the Internet... Internet
Explorer said that it couldn' t resolve the address that I had requested
(but in Windows I don't know how to configure DNS, and, besides, if it
resolves OK when connected with a more classic connexion, I don't
understand why my dns would be wrong.

In any case, I can now realize that I am not going to go anywhere with
this, so I have ordered a pcmcia WiFi card for my laptop.

I'll let you know if I can get it working allright.

Thanks a lot for your help


Bernard
[color=blue]
>I don't
>know anything about the Fonera, which I believe is a somewhat
>non-standard router,
>[/color]

It surely is non standard. At first, I just wanted to wirelessly connect
to the Internet, using a wireless pcmcia card or usb system, and I asked
what card would be supported. Then someone explained that wireless cards
and usb systems where not very efficient on laptops, especially old
ones, and that it was a lot better to use a router such as Fonera. Since
he had one to sell, I bought it and here we go. True enough, it was very
cheap, but I am sorry that I have spent so much time on it, especially
since it was helpless to ask questions to the man who sold that fonera,
because he didn't know anything about Linux.
[color=blue]
>so once you have established control of the router,
>perhaps specific questions about configuration should be addressed to
>their own forum: [url]http://boards.fon.com/[/url]
>
>Clayton
>
>
>
>[/color]


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Sun, 02 Nov 2008 23:17:47 +0100
Bernard <bdebreil@teaser.fr> wrote:
[color=blue]
> Clayton wrote:
>[color=green]
> >On 31 Oct 2008 12:06:40 GMT
> >bernard <bdebreil@teaser.fr> wrote:[/color][/color]
[color=blue][color=green][color=darkred]
> >>iface eth0 inet static
> >> address 169.254.255.1
> >> netmask 255.255.0.0
> >> gateway 169.254.255.1[/color][/color]
>
> I have indeed been able to ping 169.254.255.1, and it pinged
> allright. But I am not sure whether I was really pinging the Fonera
> or playing virtual, since such pinging also worked when the cable to
> the FONERA was being disconnected. Ping did work anytime as long as I
> had put said address in the iface command of
> the /etc/network/interfaces file.[/color]

With the above setting, ping would work with or without a cable,
because you have set your own computer's eth0 to 169.254.255.1. So when
you ping 169.254.255.1 you are pinging your own computer, which will
always work.
[color=blue]
> locking happens, you must re-initialize the internal program of your
> Fonera, which is a very hazardous and complicate process : press the
> underneath reset button using a pin or other tool, keep it pressed
> for at least 30 seconds, or until such light comes out on your
> module, then unplug the power inlet while you keep the init button
> pressed, keep it that way for at least 45 seconds or until such or
> such light goes out or on (can' remember exactly), then plug again
> and keep pressing, then 45 seconds later you release the pressure on
> the init button... and then you wait at least 15 minutes before you
> try connecting to the internal system with your browser... One
> contributor admitted that he had to re-do that init process 6 times
> before he could again connect...[/color]

Except for the final "wait 15 minutes" part, this is not so unusual.
Most routers have a similar, somewhat painful "reset to factory
defaults" process. I doubt it is actually dangerous in any way, it is
just irritating because it can be difficult to get right, and it is
hard to be sure whether one was successful on any given attempt.
Honestly, for this and other reasons, I don't much like commercial
routers. I have taken to building and using my own routers out of old
Debian-equipped laptops (a Pentium One with two PCMCIA slots will do
just fine) whenever possible. It is actually not that difficult. And
that way I can see what is going on, and control what is installed.
[color=blue]
> In any case, I can now realize that I am not going to go anywhere
> with this, so I have ordered a pcmcia WiFi card for my laptop.[/color]

Indeed, some battles just are not worth continuing, and it can be very
fruitful to try to solve the problem in a different way.
[color=blue]
> I'll let you know if I can get it working alright.
> Thanks a lot for your help[/color]

Your welcome, and good luck.
Clayton


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]

On Fri, Oct 31, 2008 at 10:42:26PM +0800, Clayton wrote:[color=blue]
> On Thu, 30 Oct 2008 23:10:56 +0530
> "justin joseph" <justinjoseph007@gmail.com> wrote:
>[color=green]
> > ...
> > [url]http://www.thinkwiki.org/wiki/Problem_with_broken_sound_on_ThinkPad_600[/url]
> >
> > And am sure there would a a lot and lot of google hits for the same,
> > because like I mentioned it is a very well known problem.[/color]
>
> Indeed, there is an awful lot of advice out there about how to get the
> 600 / 600e's sound working, and everyone's advice seems to be a little
> different. I burnt off three more hours this eve trying the above
> thinkwiki suggestions for my 600e, plus various other ALSA module
> blacklist / modprobe voodoo, all to no avail. Another machine that does
> not work with ALSA....
>
> Actually, the root problem is probably deeper then ALSA (IRQ conflict?)
> as in its current state, not even USB audio works for me. USB audio has
> *always* worked on my other machines, without exception.[/color]

Maybe this can help. A few days ago, the cmos battery died (at power
up, the bios was asking me for date and time). I bought a new one from
ebay and installed it. Now the computer remembered the date and time,
and everything was back to normal, except that the %&*@# sound system
again didn't work. The driver got into a loop when loaded, it was not
possible to unload it or kill it and cpu utilization went to 100%.

Luckily I took good notes when I got it to work. The devices got
disabled when the cmos battery died. Doing this re-enabled them:

# echo 'activate' > /sys/devices/pnp0/00:06/resources
# echo 'activate' > /sys/devices/pnp0/00:07/resources

After that, the sound driver (snd-cs4231) loads just fine and sound is
back to normal.

# cat /sys/devices/pnp0/00:06/resources
state = active
io 0x538-0x53f

# cat /sys/devices/pnp0/00:07/resources
state = active
io 0x388-0x38b
io 0x220-0x233
io 0x530-0x537
irq 5
dma 1
dma 0

Before the re-activation, "disabled" was returned.

A.


--
To UNSUBSCRIBE, email to [email]debian-laptop-REQUEST@lists.debian.org[/email]
with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]