6:25 a.m.
Hi All,
Been running FC5/rawhide for ages and absolutely love it but I have a
couple of queries wrt to various laptop support.
Firstly with NetworkManager do we still need to run the network
scripts. The reason I ask with my laptop at work I have wired, and
home wireless and as a result it takes ages to time out on alternate
interfaces and increases boot time greatly. Or can I run the network
script with the 2 interfaces disabled for boot time (so just
localhost) and let NM deal with what ever interface is up.
Similarly what's the status of docking stations support? With my Dell
Latitude when ever I undock then redock the wired network interface
(tg3) doesn't work and it takes a reboot to fix. I think its to do
with routing of the physical output to either the local port or dock
port. Same with suspending it within the dock.
Otherwise this is a rocking release. Well done!
Pete
7:22 a.m.
Peter Robinson wrote:
Similarly what's the status of docking stations support? With my
Dell
Latitude when ever I undock then redock the wired network interface
(tg3) doesn't work and it takes a reboot to fix.
I have a Latitude D800, which gets used in various configutations
depending where I vsisit
1) undocked with just internal LCD
2) docked to d/port with just external DVI LCD
3) docked to ad/dock with internal LCD and external VGA LCD
My X config is for 1280x800 which is the internal LCD, when I dock I get
centered or stretched displays on the external monitor(s) it would be
nice to switch to different display/head configurations, does hotplug
"notice" docking events?
11:19 a.m.
On Thu, 2006-04-06 at 12:25 +0100, Peter Robinson wrote:
Hi All,
Been running FC5/rawhide for ages and absolutely love it but I have a
couple of queries wrt to various laptop support.
There is also
http://www.redhat.com/mailman/listinfo/fedora-laptop-list
Firstly with NetworkManager do we still need to run the network
scripts. The reason I ask with my laptop at work I have wired, and
home wireless and as a result it takes ages to time out on alternate
interfaces and increases boot time greatly. Or can I run the network
script with the 2 interfaces disabled for boot time (so just
localhost) and let NM deal with what ever interface is up.
Ideally NM will get into shape so we don't need two network
configuration stacks [1]. Either does something the other doesn't (NM
does VPN very nicely, legacy scripts does things like interface bonding
etc.)
[1] : especially the way the old scripts rename networking networking
interfaces coupled with how the kernel announces this back to user space
is at best very broken wrt HAL/NetworkManager
Similarly what's the status of docking stations support? With my
Dell
Latitude when ever I undock then redock the wired network interface
(tg3) doesn't work and it takes a reboot to fix. I think its to do
with routing of the physical output to either the local port or dock
port. Same with suspending it within the dock.
I'm not sure about docking stations, sorry.
Otherwise this is a rocking release. Well done!
Thanks :-)
David
11:35 a.m.
On Thu, 2006-04-06 at 12:19 -0400, David Zeuthen wrote:
I'm not sure about docking stations, sorry.
Why not expose the docking status in HAL so that g-p-m and n-m can find
out what's going on and modify policy accordingly?
I don't have a fancy laptop that can dock, but I'm sure someone that
does could take the code for the vendor specific set-lcd and get-lcd
code and scripts and make this "just work".
I think this is very vendor specific on how to get the docked status.
Richard.
2:25 p.m.
On Thu, 2006-04-06 at 17:35 +0100, Richard Hughes wrote:
On Thu, 2006-04-06 at 12:19 -0400, David Zeuthen wrote:
> I'm not sure about docking stations, sorry.
Why not expose the docking status in HAL so that g-p-m and n-m can find
out what's going on and modify policy accordingly?
Ideally we would. And we would export a D-BUS interface with an
EjectDockingStation() method and make the System menu in GNOME use this
through a pretty icon or something. Or maybe if the docking station is
hot-pluggable we wouldn't need this.
I don't have a fancy laptop that can dock, but I'm sure
someone that
does could take the code for the vendor specific set-lcd and get-lcd
code and scripts and make this "just work".
I think this is very vendor specific on how to get the docked status.
Most if it is ACPI nowadays I think. From time to other I do try out my
docking station for my T41 and the result varies.
It would probably be useful to start a thread about this on the new
fedora-laptop-list - I'm just not sure all the people we want on this
list (including pjones, davej, Alan Cox) is on it yet.
I would start by collecting data about docking stations; ask people how
it works under Windows etc etc.
David
10:57 a.m.
On Thu, 2006-04-06 at 15:25 -0400, David Zeuthen wrote:
It would probably be useful to start a thread about this on the new
fedora-laptop-list - I'm just not sure all the people we want on this
list (including pjones, davej, Alan Cox) is on it yet.
I'm still not sure why we've got another list for this, but sure, why
not...
I would start by collecting data about docking stations; ask people
how
it works under Windows etc etc.
Can I borrow your t41 dock for a couple of days sometime?
--
Peter
11:23 a.m.
On Fri, 2006-04-07 at 17:17 +0100, Andy Burns wrote:
Peter Jones wrote:
> I'm still not sure why we've got another list for this, but sure, why
> not...
The list seems to have had zero activity ....
Thats because it was only recently created. A dead list like say fedora-
config-list is sometimes better than all the activity thats going on the
list which is usually no better than background noise.
Rahul
4:04 p.m.
On Thu, 2006-04-06 at 12:19 -0400, David Zeuthen wrote:
Ideally NM will get into shape so we don't need two network
configuration stacks [1]. Either does something the other doesn't (NM
does VPN very nicely, legacy scripts does things like interface
bonding etc.)
That and bridges, bluetooth, IPv6, DSL, correct handling of system WEP
keys which the user isn't allowed to know, etc...
--
dwmw2
4:40 p.m.
On Thu, 2006-04-06 at 22:04 +0100, David Woodhouse wrote:
That and bridges, bluetooth, IPv6, DSL, correct handling of system
WEP
keys which the user isn't allowed to know, etc...
Yup. And it's only going to take longer as long as people like yourself
only sends patches for Bluetooth stuff etc. to the legacy scripts
instead of NetworkManager.
David
5:45 p.m.
On Thu, 2006-04-06 at 17:40 -0400, David Zeuthen wrote:
Yup. And it's only going to take longer as long as people like
yourself
only sends patches for Bluetooth stuff etc. to the legacy scripts
instead of NetworkManager.
I _was_ sending patches for NetworkManager at one point -- it didn't
even work with IPv6 until I fixed it, which was fairly surprising. You
might need a $30 budget to test Bluetooth, but IPv6 is free.
Fixing NM to support Bluetooth PAN has been on my TODO list for a while,
but of _course_ the standard initscripts were far more of a priority.
--
dwmw2
6617
days inactive
6618
days old
10 comments
7 participants
participants (7)
-
Andy Burns -
David Woodhouse -
David Zeuthen -
Peter Jones -
Peter Robinson -
Rahul Sundaram -
Richard Hughes