Fedora 10 on an HP EVO D510

[John Summerfield]

Michal Jaegermann wrote:
> On Sat, Jan 03, 2009 at 05:03:24PM +0900, John Summerfield wrote:
>> Michal Jaegermann wrote:
>>> Not entirely true but indeed a default way to do that is through
>>> a NetworkManager (a.k.a. NetworkMangler) and that assumes a graphic
>>> environment.  It is always possible to bring wireless up using
>>> iwconfig and/or wpa_supplicant but this is relatively "low level".
>>>
>>>> Note, I've not seen any documentation of how to do this for Fedora,
>>> 'man iwconfig' (with a section "SEE ALSO") and 'man wpa_supplicant'.
>> I'm well versed in those, but that's not an acceptable way for general use.
> 
> I am not sure what is "an acceptable way" according to your criteria
> but I thought that you wanted a wireless connection while in a text
> mode and before fixing other issues.  Adding wpa_supplicant.conf
> entries is not exactly a black magic.

A long-term acceptable way to do it has to be no harder than it is on 
Windows and Linux. No geek required.

> 
> Once you will have X sorted out then NM should be operational.

CentOS5 is fine, now I've killed off kudzu.

> 
>>>> I was quite surprised though to find it's eth0 in F10 (at least some of 
>>>> the time), it used to be eth1
>>> Something else already took eth0.  Do you have a wired interface
>>> on this board?  Names and assignments can be changed but they are
>>> written "automagically" in udev rules and kept for later.  Dig a bit
>>> in files in /etc/udev/rules.d/ and you will find that out.
>> You misunderstood me. The wireless came up as eth0.
> 
> And?  Something enumerated it first.  If you dislike it then edit that
> in /etc/udev/rules.d/70-persistent-net.rules. A comment there says
> "# You can modify it, as long as you keep each rule on a single line".

"no geek required."

Users get upset when things change for no apparent reason. People 
objected loudly when 2.6 kernels renamed their ethernet interfaces: 
suddenly eth0 was connected to a different network, as were eth1 and 
eth2, with resultant chaos in DHCP server settings, firewalls and so on. 
It caused grief for me, and for quite a few others.

> 
>> ... or ath0 or 
>> something depending on the author's inclination.
> 
> "ath" prefix is used for Atheros driver handled interfaces.  These
> names are really conventional anyway (although I did not experiment
> to see if NM will not choke on something "unusual").  Check
> 'man ifrename' even if udev rules really overtook it.

I understand that, atheros have been my preferred chips for a while now. 
I think other writers use other names. It's a bit like having (ATA) 
drives at hd{a,b,c,d} and then having a few more appearing at 
disk{0,1,2,3} because some writer thought it cool to use different names 
for his ATA device driver.


> 
> It appears that all your troubles with F10 really boil down to a bug
> in an X driver for Intel chipsets.  Why this was released that way I
> have no idea; especially that this used to work fine in the past.  A
> significant number of machines already was or will be hit by that.

There's a different bug hits the graphics in my Tosh Satellite 1400 
(Trident I think). It hangs when the screensaver kicks in. I gave up on 
that, Mrs S says it's too slow with F10 anyway.

> 
>    Michal

My third (and last) F10 is supposed to he hosting virtual test machines. 
With no xen host support, and KVM not working satisfactorily, I've 
settled on doing it in Windows.



-- 

Cheers
John

-- spambait
1aaaaaaa at coco.merseine.nu  Z1aaaaaaa at coco.merseine.nu
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375

You cannot reply off-list:-)