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

Re: Laptop wireless problem - very slight tangent



On Tue 05 Jul 2016 at 16:12:58 (+0100), Lisi Reisz wrote:
> On Tuesday 05 July 2016 16:02:52 David Wright wrote:
> > It would be nice to know what the "it" is that chooses that default.
> > I have a laptop with the same IPW2200 wireless, and it has always
> > defaulted to eth1 in the same way as Lisi's did.
> >
> > If it's a "default", that would imply that there's some way to choose
> > an alternative like wlan0 (which is indeed what, say, wicd will think
> > the interface ought to be named). How would I go about making this choice?
> 
> After these agonising hours I can answer that:
> 
> Edit /etc/udev/rules.d/70-persistent-net.rules. 
> 
> Just cross your fingers, hold your breath, and follow the instructions at the 
> top of the file.  In case of disaster, it seems it regenerate quite happily.  
> (No, I didn't have a disaster - but deloptes' first suggestion was to comment 
> out the eth1 line and reboot to give it the chance to generate wlan0.  But it 
> didn't, it regenerated eth1.

This is my point. Your *system* regenerated eth1. My *installer* generated eth1.
When I install, I have set
language
keyboard
locale
and I have provided a USB stick with the tg3 and ipw2200 firmware.
Nothing else.

I might look around and find a /etc/udev/rules.d/70-persistent-net.rules
file, but persist it will not! The only thing that persists at this
stage is /target, and that's barely begun construction at this step
in the installation. I think fiddling at that point is beyond even
an "expert" install.

So what I want to know from deloptes (or anyone else) is:

Why does this system (and yours) default to eth1, and
How can it be changed *at this point in the install*, if it
really is just a "default".

> So I left my commented out line just in case, 
> and edited the new eth1 line.  I have now deleted the commented out line and 
> just have:
> 
> sarah@debian-wheezy:~$ cat /etc/udev/rules.d/70-persistent-net.rules
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
> 
> # PCI device 0x14e4:/sys/devices/pci0000:00/0000:00:1e.0/0000:03:00.0/ssb0:0 
> (b44)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="00:14:22:e7:6f:21", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
> KERNEL=="eth*", NAME="eth0"
> 
> # PCI device 0x8086:0x4220 (ipw2200)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", 
> ATTR{address}=="00:16:6f:00:3a:b3", ATTR{dev_id}=="0x0", ATTR{type}=="1", 
> KERNEL=="eth*", NAME="wlan0"
> sarah@debian-wheezy:~$ 

Agreed. I could do all this, but it would gain me nothing as
eth1 works perfectly ok.

I have a suspicion that, at some time in the past, not every kernel's
ipw2200 module has worked properly (even with the firmware apparently
correctly loaded). However, I have no evidence, and it's water under
the bridge. It could have been finger trouble on my part.

Cheers,
David.


Reply to: