Wireless, which worked in FC6 but not previously in F7, now works. This means that once the Emacs problem is fixed, I should be able to switch to F7 without regressions. Yeah!
I especially like being able to switch back and forth between internal and external monitor, which means I can now boot in run-level 5, rather than 3 and then manually start X.
There are still problems with suspend and hibernate, but I've never been able to use those before, so this isn't a regression. Suspend doesn't work at all, and when waking up from hibernate (after pm-hibernate) it seems unable to detect a wireless signal.
Still, top of my wishlist for F8 is reliable (and preferably fast) suspend *or* hibernate.
(I'm also hoping for a nice xrandr GUI integrated into the Screen Resolution control, perhaps inspired by Apple's.)
Thanks for all the great work!
(This is on a Dell Inspiron R1405 laptop with Intel wireless and graphics.)
On Sun, 2007-05-13 at 13:08 -0700, Per Bothner wrote:
Wireless, which worked in FC6 but not previously in F7, now works. This means that once the Emacs problem is fixed, I should be able to switch to F7 without regressions. Yeah!
I especially like being able to switch back and forth between internal and external monitor, which means I can now boot in run-level 5, rather than 3 and then manually start X.
There are still problems with suspend and hibernate, but I've never been able to use those before, so this isn't a regression. Suspend doesn't work at all, and when waking up from hibernate (after pm-hibernate) it seems unable to detect a wireless signal.
FWIW I had my fair share of issues with not resuming properly on an Acer Ferrari 4005 and Acer TM6364. What solved it for me is simply blacklisting or disabling every module I don't use. On FC6 & both laptops suspend/hibernate/resume now works most of the time.
Hope this helps.
Regards, Patrick
Per Bothner wrote:
Wireless, which worked in FC6 but not previously in F7, now works. This means that once the Emacs problem is fixed, I should be able to switch to F7 without regressions. Yeah!
emacs problem? What emacs problem?
FWIW, I'm using emacs GNU Emacs 23.0.0.1 built with ./configure --with-gtk --enable-font-backend --with-xft --prefix=/usr --libdir=/usr/lib64 --enable-locallisppath=/usr/share/emacs/site-lisp
and it works great.
On Mon, May 14, 2007 at 08:16:55AM -0400, Neal Becker wrote:
Per Bothner wrote:
This means that once the Emacs problem is fixed, I should be able to switch to F7 without regressions. Yeah!
emacs problem? What emacs problem?
That one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239344
Michal
Michal Jaegermann wrote:
On Mon, May 14, 2007 at 08:16:55AM -0400, Neal Becker wrote:
Per Bothner wrote:
This means that once the Emacs problem is fixed, I should be able to switch to F7 without regressions. Yeah!
emacs problem? What emacs problem?
That one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=239344
Michal
Same fix works for GNU Emacs 23.0.0.1.
On 5/13/07, Per Bothner per@bothner.com wrote:
Wireless, which worked in FC6 but not previously in F7, now works. This means that once the Emacs problem is fixed, I should be able to switch to F7 without regressions. Yeah!
I especially like being able to switch back and forth between internal and external monitor, which means I can now boot in run-level 5, rather than 3 and then manually start X.
There are still problems with suspend and hibernate, but I've never been able to use those before, so this isn't a regression. Suspend doesn't work at all, and when waking up from hibernate (after pm-hibernate) it seems unable to detect a wireless signal.
Still, top of my wishlist for F8 is reliable (and preferably fast) suspend *or* hibernate.
(I'm also hoping for a nice xrandr GUI integrated into the Screen Resolution control, perhaps inspired by Apple's.)
Thanks for all the great work!
(This is on a Dell Inspiron R1405 laptop with Intel wireless and graphics.) -- --Per Bothner per@bothner.com http://per.bothner.com/
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Which wireless adapter do you have?
Justin Conover wrote:
Which wireless adapter do you have?
According to lspci:
Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
On 5/14/07, Per Bothner per@bothner.com wrote:
Justin Conover wrote:
Which wireless adapter do you have?
According to lspci:
Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
--Per Bothner
per@bothner.com http://per.bothner.com/
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
Nice, I'll test it when I get home.
On Monday 2007-05-14 18:46:12 Per Bothner wrote:
Justin Conover wrote:
Which wireless adapter do you have?
According to lspci:
Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
I have exactly the same. Can you test it to ping the AP for 2-3 minutes and see if it is regularly dropping packets every 30 or so seconds?
Doncho N. Gunchev wrote:
I have exactly the same. Can you test it to ping the AP for 2-3 minutes and see if it is regularly dropping packets every 30 or so seconds?
Seems to work ok. There was a spot where the ping time went up to about 1s, men now it's been single-digit ms for a while - except for on 567ms packet.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 2007-05-16 03:53:28 Per Bothner wrote:
Doncho N. Gunchev wrote:
I have exactly the same. Can you test it to ping the AP for 2-3 minutes and see if it is regularly dropping packets every 30 or so seconds?
Seems to work ok. There was a spot where the ping time went up to about 1s, men now it's been single-digit ms for a while - except for on 567ms packet.
Strange, happends to me every time... (2.6.21-1.3149 btw), With FC6 - no problems (ipw3945).
05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) (lspci -n = 8086:4222)
- -- Regards, Doncho N. Gunchev, GPG key ID: 0EF40B9E, Key server: pgp.mit.edu
Doncho N. Gunchev wrote:
Strange, happends to me every time... (2.6.21-1.3149 btw), With FC6 - no problems (ipw3945).
05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) (lspci -n = 8086:4222)
I have no joy with wireless, this is what happens when i try to activate the interface in system-config-network:
Determining IP information for wmaster0... SIOCSIFFLAGS: Operation not supported SIOCSIFFLAGS: Operation not supported
Latest updates of course, 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) On a Dell Inspiron 640m.
On Thursday 2007-05-17 09:30:01 Dylan Graham wrote:
Doncho N. Gunchev wrote:
Strange, happends to me every time... (2.6.21-1.3149 btw), With FC6 - no problems (ipw3945).
05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) (lspci -n = 8086:4222)
I have no joy with wireless, this is what happens when i try to activate the interface in system-config-network:
Determining IP information for wmaster0... SIOCSIFFLAGS: Operation not supported SIOCSIFFLAGS: Operation not supported
Latest updates of course, 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) On a Dell Inspiron 640m.
I have never tried configuring wireless with system-config-network. Try yum install NetworkManager; chkconfig NetworkManager on; service ... start
Dylan Graham wrote:
Doncho N. Gunchev wrote:
I have never tried configuring wireless with system-config-network. Try yum install NetworkManager; chkconfig NetworkManager on; service ... start
Ah, it works perfectly. Thanks.
I assume NetworkManager will be enabled by default in the final release?
In the live images, yes but not in the regular "Fedora" spin. That is planned for Fedora 8.
http://fedoraproject.org/wiki/Releases/8/FeatureList
Rahul