Mailinglist Archive: opensuse (6210 mails)

["Greg Wallace" <jgregw@xxxxxxxxxxxxx>]

On Sunday, October 16, 2005 @ 10:07 PM, Toshi wrote:

>On Sunday 16 October 2005 06:46 pm, Toshi Esumi wrote:
>> On Sun, 2005-10-16 at 17:39 -0400, Bruce Marshall wrote:
>> > > > You should start writing these questions down so you can provide
the
>> > > > information without people having to ask.
>> > >
>> > > Just what I need. Attitude. No problem. I'm going back to 9.3, which
>> > > works, and let you smart guys figure this out. I wasted enough time
>> > > trying to fix a broken distribution.
>> >
>> > Hey....   I'm ready to give up too if you continue using  100.1
>> > addresses....    :-)
>> >
>> > Oh...  I see you already gave up.     Ok...
>>
>> That's too sad ;( If you don't see "eth0" in ifconfig, there may be a
>> compatibility issue between SuSE 10.0 and the PCMCIA NIC.

>I have had issues with eth0/eth1 assignment in my desktop with 10.0. In my 
>case a perfectly good eth config through yast ends up with a "nonexistent 
>device" error when eth0 is looked up for energization, leaving only lo and 
>vmnet1 in the ifconfig listing ( i run vmware) . I am convinced it's a bug,

>everything works great in the same machine when running under 9.3. Have
>filed 
>it as bug #120332 in  Bugzilla. For me it looks like 10.0 will stay in the 
>"play" partition for a while yet...
>demitri

I once had a device problem where I had a kernel module being loaded that
shouldn't have been.  The solution was to do a modprobe -r so that the
kernel wouldn't load that module.  I'm wondering if you might have just the
opposite problem; I, e, a kernel module that should be getting loaded but
isn't.  I'm way out of my league here, but since you've pretty much given up
on this, I thought I'd throw this out as a WAG.  I may be completely off in
left field here (wouldn't be the first time) but maybe someone with better
kernel knowledge could step in and say it this is a possibility.

>
> If you want to set up a static IP on one of your PCs(like the laptop) in
> the future, pick one of IPs within 192.168.1.52-192.168.1.254 because
> you said you assigned 50 IPs for DHCP at the Linksys
> (192.168.1.2-192.168.1.51).
> For example,
> -Linksys: 192.168.1.1/24 (DHCP server)
> -PC-1   : 192.168.1.2(via DHCP)
> -PC-2   : 192.168.1.3(via DHCP)
> -PC-3   : 192.168.1.4(via DHCP)
> -Laptop : 192.168.1.52(static)
>
> This is the way to keep all devices happy campers.
>
>
> Toshi
Greg Wallace