[opensuse] Problems with HP Pavilion DV6000
I just Installed opensuse 10.2 on a new HP Pavilion DV6000 laptop. intel duo core CPU intel wireless network intel graphics I'm seeing a disparity between gnome and kde functionality - #1 - wireless connections via network manager: In gnome, I can connect to the secure wireless networks in my house, but with kde network manager I can't connect to either of them. The gnome applet allows me to choose all the correct parameters, while the kde applet allows fewer options, and does not allow me to enter e.g. the correct the key type as in gnome. If only the kde network manager applet provided all the functionality of the gnome one, we'd be set. #2 - laptop buttons (volume, dvd, etc) In kde, the laptop buttons surprisingly work, but in gnome there is no response to any of the buttons. If the buttons would work under gnome, we could just run gnome and be happy. #3 - display problems - Despite the fact that this is an intel 945 graphics chipset with 100% FOSS drivers, I can't get anything more than 1024x768 resolution, although it's capable of 1440x900. Any attempt to set a higher resolution than 1024x768 gets a corrupted xmd screen, and I have to fall back to the basic 1024x768 to get up and running again. Anybody had any luck with linux (any distro) on an HP DV6000? Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 05 February 2007 04:20, J Sloan said:
#1 - wireless connections via network manager: In gnome, I can connect to the secure wireless networks in my house, but with kde network manager I can't connect to either of them. The gnome applet allows me to choose all the correct parameters, while the kde applet allows fewer options, and does not allow me to enter e.g. the correct the key type as in gnome. If only the kde network manager applet provided all the functionality of the gnome one, we'd be set.
There's not a lot to go on here. Speaking as one of the knetworkmanager authors, I thought we had parity with nm-applet. We need to know exactly which options are missing, for which type of wireless encryption/authentioncation, and what the network hardware in the dv6000 actually is. Please report these in a bug at bugzilla.novell.com.
#3 - display problems - Despite the fact that this is an intel 945 graphics chipset with 100% FOSS drivers, I can't get anything more than 1024x768 resolution, although it's capable of 1440x900. Any attempt to set a higher resolution than 1024x768 gets a corrupted xmd screen, and I have to fall back to the basic 1024x768 to get up and running again.
Sounds like you need to use 915resolution to patch the video bios so that it reports that it's capable of 1440x900. There's plenty of info on the web on how this works, and the readme in our 915resolution package (rpm -ql 915resolution) is quite helpful, but note that we now provide /etc/sysconfig/videobios where you can add the right parameters so that 915resolution is run on boot. HTH Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Will Stephenson wrote:
On Monday 05 February 2007 04:20, J Sloan said:
#1 - wireless connections via network manager: In gnome, I can connect to the secure wireless networks in my house, but with kde network manager I can't connect to either of them. The gnome applet allows me to choose all the correct parameters, while the kde applet allows fewer options, and does not allow me to enter e.g. the correct the key type as in gnome. If only the kde network manager applet provided all the functionality of the gnome one, we'd be set.
There's not a lot to go on here. Speaking as one of the knetworkmanager authors, I thought we had parity with nm-applet. We need to know exactly which options are missing, for which type of wireless encryption/authentioncation, and what the network hardware in the dv6000 actually is. Please report these in a bug at bugzilla.novell.com.
Actually, I was able, after several trials, to get knetworkmanager to connect to the wireless access points. I had to make some guesses (for instance, where kde says "40 bit key" it really means 64 bits) and it was less intuitive than the gnome version, but I must admit that it was possible after all to connect.
#3 - display problems - Despite the fact that this is an intel 945 graphics chipset with 100% FOSS drivers, I can't get anything more than 1024x768 resolution, although it's capable of 1440x900. Any attempt to set a higher resolution than 1024x768 gets a corrupted xmd screen, and I have to fall back to the basic 1024x768 to get up and running again.
Sounds like you need to use 915resolution to patch the video bios so that it reports that it's capable of 1440x900. There's plenty of info on the web on how this works, and the readme in our 915resolution package (rpm -ql 915resolution) is quite helpful, but note that we now provide /etc/sysconfig/videobios where you can add the right parameters so that 915resolution is run on boot.
Yep, the 915resolution package did the trick, with a 1-line modification to /etc/sysconfig/videobios as you suggested. So, the non-working function keys in gnome are now a non-issue, since everything works in kde, and that's all I need. Thanks for the tips - Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 February 2007 07:48, J Sloan said:
Actually, I was able, after several trials, to get knetworkmanager to connect to the wireless access points. I had to make some guesses (for instance, where kde says "40 bit key" it really means 64 bits) and it was less intuitive than the gnome version, but I must admit that it was possible after all to connect.
We are going to change the "40 bit" label since it's caused plenty of confusion. What you call a 64 bit key is a 40 bit key with 24 bits of padding, likewise the 104 bit key is aka 128 bit encryption, and when we wrote knetworkmanager we just took the IEEE802.11 internal names for the encryption types. Anyway, I'm happy to have kept you on KDE :). Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 06 February 2007, Will Stephenson wrote:
On Tuesday 06 February 2007 07:48, J Sloan said:
Actually, I was able, after several trials, to get knetworkmanager to connect to the wireless access points. I had to make some guesses (for instance, where kde says "40 bit key" it really means 64 bits) and it was less intuitive than the gnome version, but I must admit that it was possible after all to connect.
We are going to change the "40 bit" label since it's caused plenty of confusion. What you call a 64 bit key is a 40 bit key with 24 bits of padding, likewise the 104 bit key is aka 128 bit encryption, and when we wrote knetworkmanager we just took the IEEE802.11 internal names for the encryption types.
Anyway, I'm happy to have kept you on KDE :).
Will
While you are fixing that, how bout taking a look as to why ifup/ifdown can not be used in parallel with knetworkmanager . I don't think its a good idea to disable standard tools this way. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Will Stephenson wrote:
On Tuesday 06 February 2007 07:48, J Sloan said:
Actually, I was able, after several trials, to get knetworkmanager to connect to the wireless access points. I had to make some guesses (for instance, where kde says "40 bit key" it really means 64 bits) and it was less intuitive than the gnome version, but I must admit that it was possible after all to connect.
We are going to change the "40 bit" label since it's caused plenty of confusion. What you call a 64 bit key is a 40 bit key with 24 bits of padding, likewise the 104 bit key is aka 128 bit encryption, and when we wrote knetworkmanager we just took the IEEE802.11 internal names for the encryption types.
Ah, and I was wondering if you guys were just using hexadecimal to confuse us - Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
J Sloan wrote:
Will Stephenson wrote:
...
#3 - display problems - Despite the fact that this is an intel 945 graphics chipset with 100% FOSS drivers, I can't get anything more than 1024x768 resolution, although it's capable of 1440x900. Any attempt to set a higher resolution than 1024x768 gets a corrupted xmd screen, and I have to fall back to the basic 1024x768 to get up and running again. Sounds like you need to use 915resolution to patch the video bios so that it reports that it's capable of 1440x900. There's plenty of info on the web on how this works, and the readme in our 915resolution package (rpm -ql 915resolution) is quite helpful, but note that we now provide /etc/sysconfig/videobios where you can add the right parameters so that 915resolution is run on boot.
Yep, the 915resolution package did the trick, with a 1-line modification to /etc/sysconfig/videobios as you suggested.
Did the trick for me, too. I've been looking at a distorted 1024X768 screen for months, now, and the suggestions from my query on 12/14/06 didn't help. Thanks! -- John Perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
J Sloan -
John Andersen -
John E. Perry -
Will Stephenson