Re: [SLE] Sound problems in 9.3

From: Stan Glasoe (SRGlasoe_at_comcast.net)
Date: 04/23/05

  • Next message: Pieter Hulshoff: "Re: [SLE] Please help: SuSE 9.1 lockups during high CPU/disk activity" 
    To: suse-linux-e@suse.com
Date: Fri, 22 Apr 2005 17:23:32 -0500

    On Friday 22 April 2005 4:30 pm, Sunny wrote:
    > On Friday 22 April 2005 15:54, Stan Glasoe wrote:
    > > My main system has this capability and I always forget about it until
    > > the next upgrade... maybe not this time though. My choice of DHCP
    > > client fixed my NIC not being found on warm reboots in the past.
    > >
    > > Stan
    >
    > Stan,
    > can you elaborate more on this? I have the same problem. From time to
    > time on a "warm" reboot, my NIC does not get DHCP info, and I need to
    > ifdown/ifup after that in order to have network. I use 9.1. And it
    > happens even between "warm" reboot SuSE-SuSE, without messing up with XP.
    >
    > Sunny
    >

    This started either in the 8.0 or 8.1 release. Back then I was rebooting to
    Windows often enough that it was a problem to fix. I ended up switching to
    the ISC DHCP client (dhcp-client) for several releases and then about 9.1
    or 9.2 the default DHCP client (dhcpd) was fixed. Or whatever was the
    problem was fixed; kernel parameter or other driver?

    In this machine I use 2 different Compaq branded Intel 10/100 cards that use
    the e100 driver. I tried different ethernet card(s), cables, different PCI
    slots, different 10/100 switches, etc. Finally saw someone else on this
    list mention that switching dhcp client software fixed similar problems
    they were having. Worked for me too! I haven't seen this on any other
    10/100 card I tried in this system; they weren't as efficient or reliable
    as the Intels though.

    There wasn't any firmware update for these cards either so they are at the
    latest version level. Ancient cards by todays standards but they keep
    working. My mainboard was/is at the latest BIOS version too. Not much else
    to change to isolate the problem at the time.

    What worked reliably to get the NICs recognized in Linux was to hit the
    reset button or do the full power off/on at the power supply via switch or
    power cord. Windows versions were 98SE, Win2k Pro and AS with various patch
    levels and SPs applied. It always worked in Windows. :( :( :(

    I don't even think about it now because whatever was not right has been
    fixed. It wasn't the change from 2.4.x to 2.6.x kernels either. Does that
    also rule out a kernel parameter or other driver getting fixed? Hmmm...

    Stan 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Pieter Hulshoff: "Re: [SLE] Please help: SuSE 9.1 lockups during high CPU/disk activity"