[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mandrake-cooker
Subject:    [Cooker] [Bug 18454] [drakxtools] NEEDINFO: harddrake kills network connection when hardware is dete
From:       "doktor5000 () arcor ! de" <bugzilla () qa ! mandrivalinux ! com>
Date:       2006-07-31 21:54:04
Message-ID: bug18454.20060731215404.816170 () qa ! mandriva ! com
[Download RAW message or body]

User ID: 77229, 2 bugs reported (0 fixed, 0 duplicate, 0 invalid), 8 comments.

http://qa.mandriva.com/show_bug.cgi?id=18454





------- Comment #14 from doktor5000@arcor.de  2006-07-31 23:54 -------
Sorry for the misunderstanding. I ran hwdb_add_system seperately from console,
but i think this is the same error occuring within harddrake hitting me when
trying to upload my whole system in the end. 

"...500 Can't connect to hwdb.mandriva.com:80 (Bad hostname
'hwdb.mandriva.com')..."

So to make this clearer: The disconnect happens in both cases, when running
harddrake2 or hwdb_add_system. Also it doesn't matter if run from console or
within control-center. It seems it is not the same thing my WLAN receiver
suffers from but a really similar behaviour.

Today i removed ndiswrapper, i want to see if the commercial version called
DriverLoader works more stable or if it produces same results.


-- 
Configure bugmail: http://qa.mandriva.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


------- Reminder: -------
assigned_to: install@mandriva.com
status: NEEDINFO
distribution: 10.2-official
creation_date: 
description: 
The description of this problem is simple: If i start harddrake from within MCC
or from console, it kills my internet connection, but i cannot specify what
happens exactly, because i don't know where to look except for dmesg.
I'm running 2005LE Official with all updates since beginning, doesn't matter
which kernel or which driver version i'm using. This also applies to 2005LE
Community, which i also tested thoroughly.
My box is a 2 GHz P4 with 1GB of RAM, and i use driverloader for my
WLAN-USB-receiver, network runs on eth0 and gets auto-loaded & activated during
boot sequence.
Please tell me what informations you need for looking further into this sort-of-bug.

PS: my workaround ATM is "service network restart"
[prev in list] [next in list] [prev in thread] [next in thread]