Text 5554, 95 rader
Skriven 2006-03-24 16:17:00 av James Bradley (1:134/77.0)
     Kommentar till en text av Maurice Kinal
Ärende: 802.11g, eth0/1, dhcpcd.
================================
Maurice Kinal wrote James Bradley on 03-23-06 21:03

 MK> /etc telling my root account not to edit them.
 MK> Okay.  Hm.  'rm' seems to work on them fine so I
 MK> guess it must be okay to safely delete them.

And, nobody told you *not* to bit-bucket 'em? <L>

 MK> Errrr ... you may not wish to follow my lead ...
 MK> I am a trained Slackware professional.

Ya, I do have to watch how much I bite off, or else I might not be able to
chew. I think I'll replace the dual boot RH with Slack, so I can test the
waters there. 

 MK> Looks to be a bad network card/chip or you don't
 MK> have that make/model in the kernel.

It did appear to be fine, besides not having the right protocol (READ: any
protocol) prior to eth1 insertion.

eth0      Link encap:Ethernet  HWaddr 00:D0:B7:26:87:94  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
...   [No IRQ/I-O]
eth1      Link encap:Ethernet  HWaddr 00:80:C8:D6:44:A1  
          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
...       Interrupt:5 Base address:0x240 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
...       RX bytes:3888 (3.7 Kb)  TX bytes:3888 (3.7 Kb)


 JB> I just bought two 19" flat screen Dell CRT monitors at
 JB> Sure glad AB has a recycling program in effect. <EG>

 MK> Didn't they work?  Around here it is tough to
 MK> get rid of monitors (recycle).  Have to take
 MK> them to Duncan now that the place in Nanaimo
 MK> closed, which was closer.

That's where the excitement comes in. I haven't plugged either in, nor did I to
see if they even power up. Doing the math, I'd probably need an eight-hour
shift to test the stuff I was prepared to bid on. The volume there *is* rather
large.

I bought these two, specifically because I have a working tube to the same
model, but the H-sync seems to have a harmonic problem. I now have - at the
very least - one known working tube, with a hopefully fixable support circuit,
plus two rolls of the dice in the kitty. Just one of those needs to work, so I
can demote this one, and I still have one more kick at the cat, and one
replacement tube at a minimum. 

Ralphie Klein (Our fearless leader in Alberta, Canada.) actually has a bent for
recycling. (Might have something to do with his drinking problem.) He
instituted a levy on new CRTs. (READ: Doesn't affect me.) With the extra $5
that one pays on a piece, you are encouraged to drop off the piece you
replaced. (READ: Stress was easily released via the old Zenith and a "heave_ho"
as you say. =B-)

 JB> Well, that's what kinda surprised me here. Both docs told me to use
 JB> static addressing,

 MK> That *should* work as long as you have the right
 MK> network address.  The default address of
 MK> wireless routers is usually 192.168.2.1 with
 MK> 192.168.2.255 as the broadcast address and
 MK> 255.255.255.0 as the netmask.  Give your machine
 MK> the address of 192.168.2.2 and the same
 MK> broadcast and netmask, possibly putting
 MK> 192.168.2.1 as the gateway if that matters to
 MK> you.

192.168. :
 0.30  = bridge->11g Address from:
 0.2 Given *only* as an example. 
 1.254 = router->11g Address from:
 1.1 to ...253 Definitive.

I set the two NICs at .1.1, and .1.2, just for 'fun'. When I first plugged the
router into eth0, it acknowledged, and communicated. I installed eth1, and
communication was lost between eth0->router. eth1->router; fine. The static
address even brought up the setup page in links2. The bridge; just accepts a
different static address no doubt.

 JB> reached. Back to DHCP, and both were found.
 MK> What information do they give about the wireless
 MK> router?

Define: They. <G+D>

 
___ MultiMail/Linux v0.47

--- Maximus 3.01
 * Origin: -=-= Calgary Organization CDN (403) 242-3221 (1:134/77)