F13 Sadly Unusable

[Brian C. Huffman]

I upgraded to F13 on my Dell Latitude D630
* Wireless doesn't work - the laptop only gets a multicast address, not
a valid unicast address
* Bluetooth DUN still doesn't work.
* So I go to my docking station so that I can get *some* network, and X
comes up with the *closed* laptop lid as the primary monitor in a dual
monitor setup...so I can't see any windows

Wow.  Impressive.

-b

[Jerry Feldman]

On 06/05/2010 10:48 AM, Brian C. Huffman wrote:
>  On Sat, 2010-06-05 at 17:33 +0300, Gilboa Davara wrote:
>
>    
> > I wonder, what was your intention sending this email?
> > Blowing off steam? Reporting bugs?
> >
> > You are aware that this is random noise that will be simply ignored,
> > right? (Unless you take the time to report bugs, and help the developers
> > debug the problems)
> >
> >     
>  Last ditch effort?  Motivate someone (out of anger at me) to help?  I've
>  done what you said. Take a look at the date on this bug report and see
>  where it's gotten me:
>
>  https://bugzilla.redhat.com/show_bug.cgi?id=591489
>
>
>
>
>     
Dell laptops tend to use Broadcom cards for wireless. If you look at
dmesg it may tell  you you need some firmware. You should install
b43-fwcutter. Take a look at this website for further instructions.
http://linuxwireless.org/en/users/Drivers/b43. While my laptop is
running Ubuntu, it has run SuSE and Fedora.

-- 
Jerry Feldman <gaf(a)blu.org&gt;
Boston Linux and Unix
PGP key id: 537C5846
PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846

[Timothy Murphy]

Brian C. Huffman wrote:

>  I upgraded to F13 on my Dell Latitude D630
>  * Wireless doesn't work - the laptop only gets a multicast address, not
>  a valid unicast address 
I'm not sure what that means.
But if NetworkManager is not working I would try the network service:
"sudo chkconfig network on" and re-boot.

-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

[Alan Cox]

On Sat, 5 Jun 2010 09:37:52 -0400
"Brian C. Huffman" <bhuffman(a)graze.net&gt; wrote:

>  I upgraded to F13 on my Dell Latitude D630
>  * Wireless doesn't work - the laptop only gets a multicast address, not
>  a valid unicast address
>  * Bluetooth DUN still doesn't work.
>  * So I go to my docking station so that I can get *some* network, and X
>  comes up with the *closed* laptop lid as the primary monitor in a dual
>  monitor setup...so I can't see any windows
>  
>  Wow.  Impressive. 
File bugs.

One for the wireless (include the information on what card it is etc and
what is in 'dmesg')
One for the bluetooth (and if things other than DUN work probably start
against NetworkMangler
One for the video (against X giving your video info)

There are always going to be some systems a release breaks - with any OS.
It's not possible to test every combination of hardware on the planet.

Alan

[Gene Heskett]

On Saturday 05 June 2010, Brian C. Huffman wrote:
> On Sat, 2010-06-05 at 17:33 +0300, Gilboa Davara wrote:
> > I wonder, what was your intention sending this email?
> > Blowing off steam? Reporting bugs?
> >
> > You are aware that this is random noise that will be simply ignored,
> > right? (Unless you take the time to report bugs, and help the developers
> > debug the problems)
>
> Last ditch effort?  Motivate someone (out of anger at me) to help?  I've
> done what you said. Take a look at the date on this bug report and see
> where it's gotten me:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=591489
>  
Brian, as one who has also been burnt on bad BT hardware, I will concur that 
it is 200% buyer beware on that stuff.  I got burnt on a pair that weren't 
even given a MAC address in their firmware, so they defaulted to 
11.11.11.11.11.11 and refused to talk to each other from 3 feet.  So it cost 
me $40 USD twice to get two dongles that worked.  Possibly bluez may be able 
to deal with such a device today, but back about December of last year it 
was helpless, incapable of assigning a BDADDR to a device without one.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The naked truth of it is, I have no shirt.
		-- William Shakespeare, "Love's Labour's Lost"

[Gilboa Davara]

On Sat, 2010-06-05 at 10:48 -0400, Brian C. Huffman wrote:
>  On Sat, 2010-06-05 at 17:33 +0300, Gilboa Davara wrote:
>  
>  > I wonder, what was your intention sending this email?
>  > Blowing off steam? Reporting bugs?
>  > 
>  > You are aware that this is random noise that will be simply ignored,
>  > right? (Unless you take the time to report bugs, and help the developers
>  > debug the problems)
>  > 
>  
>  Last ditch effort?  Motivate someone (out of anger at me) to help? 
You should know better than that.
Trashing people will not motivate them. It'll simply annoy them.

>    I've
>  done what you said. Take a look at the date on this bug report and see
>  where it's gotten me:
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=591489 
OK. Please understand that kernel bugs are hard to fix, especially
hardware-related ones (And I'm speaking as a driver developer)
The kernel guys are over-swamped with open bugs (I've got at least 4 of
them open) - many of them are almost impossible to reproduce. (E.g.
requires special hardware)

So, you can either bitch about it, switch distro hoping for the best (I
doubt that it'll work, but it's a free world), or you could try and help
the developers triage and fix this bug. (E.g. by reporting it upstream
to kernel.org, etc, doing some reading about how to debug USB issues,
etc)

I doubt that posting angry messages will work.

- Gilboa

[Brian C. Huffman]

On Sat, 2010-06-05 at 17:33 +0300, Gilboa Davara wrote:

>  I wonder, what was your intention sending this email?
>  Blowing off steam? Reporting bugs?
>  
>  You are aware that this is random noise that will be simply ignored,
>  right? (Unless you take the time to report bugs, and help the developers
>  debug the problems)
>   
Last ditch effort?  Motivate someone (out of anger at me) to help?  I've
done what you said. Take a look at the date on this bug report and see
where it's gotten me:

https://bugzilla.redhat.com/show_bug.cgi?id=591489

[Gilboa Davara]

On Sat, 2010-06-05 at 09:37 -0400, Brian C. Huffman wrote:
>  I upgraded to F13 on my Dell Latitude D630
>  * Wireless doesn't work - the laptop only gets a multicast address, not
>  a valid unicast address
>  * Bluetooth DUN still doesn't work.
>  * So I go to my docking station so that I can get *some* network, and X
>  comes up with the *closed* laptop lid as the primary monitor in a dual
>  monitor setup...so I can't see any windows
>  
>  Wow.  Impressive.
>  
>  -b
>   
I wonder, what was your intention sending this email?
Blowing off steam? Reporting bugs?

You are aware that this is random noise that will be simply ignored,
right? (Unless you take the time to report bugs, and help the developers
debug the problems)

- Gilboa