I have ended up going back to 11.4 from M2 as the new aaa base packages result in a crash message if a kde3 programme is ran from kde4. Although I use kde4 I still prefer the odd kde3 programme version like kaffine and k3b.
I booted the 32-bit openSUSE-12.1 Milestone2 Gnome liveCD, and also later the KDE liveCD on my ‘linux killer’ Fujitsu Amilo 7400M laptop with the i855GM graphics.
The Gnome boot was slow but progressed without noticeable glitch until I obtained an error that 'Gnome 3 failed to start properly and started in a ‘fallback mode’, with this most likely due to the graphics hardware or driver is not capable of delivering the Gnome 3 experience. Given the difficulty (since the 2.6.27 kernel) of all new GNU/Linux kernels in handling the i855GM graphics, that was no surprise. I have an ‘out of focus’ pix of the error here:
http://thumbnails51.imagebam.com/13803/a25157138028986.jpg](http://www.imagebam.com/image/a25157138028986)
[click on pix for larger view]
After this Gnome proceed to boot ok and I reached a version of Gnome that I was not familiar with. I launched a terminal and did somethings with the terminal, and I was left with an impression that ansi was not working properly in the terminal. I did manage to connect to our home LAN with the wireless. It appears to me that Gnome STILL has an advantage over KDE when it comes to configuring wireless (as my later experience would show).
The wireless details from dmesg were interesting:
44.630503] libipw: 802.11 data/management/control stack, git-1.1.13
44.630641] libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
46.492913] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
46.493054] ipw2100: Copyright(c) 2003-2006 Intel Corporation
46.517683] ipw2100 0000:02:06.0: PCI INT A -> Link[LNKG] -> GSI 10 (level, low) -> IRQ 10
46.518615] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
50.848298] ipw2100 0000:02:06.0: eth1: Features changed: 0x00004800 -> 0x00004000
During the boot there was about a 90 second pause after this ‘Features changed’ message.
The wireless on this laptop:
02:06.0 Network controller [0280]: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter [8086:1043] (rev 04)
Subsystem: Intel Corporation MIM2000/Centrino [8086:2527]
Kernel driver in use: ipw2100
I note Gnome booted with the i915 Intel driver to a 1024x768 resolution, which is typical for this laptop.
This laptop’s graphic hardware:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02)
Subsystem: Fujitsu Technology Solutions Device [1734:1033]
Kernel driver in use: i915
Some more details on this laptop’s hardware when running the liveCD with inxi (which I had to rebuild to obtain):
linux@linux:~> inxi -v 6
System: Host linux.site Kernel 2.6.39-2-default i686 (32 bit gcc 4.6.0)
Desktop Gnome Distro openSUSE 12.1 Milestone 2 (i586) VERSION = 12.1 CODENAME = Asparagus
Machine: System FUJITSU SIEMENS (portable) product AMILO M version -1
Mobo FUJITSU SIEMENS model AMILO M version Rev.A Bios Phoenix version R01-S0Z date 12/28/04
CPU: Single core Intel Pentium M (-UP-) cache 1024 KB flags (sse sse2) bmips 2799.71 clocked at 1400.00 MHz
Graphics: Card: Intel 82852/855GM Integrated Graphics Device bus-ID: 00:02.0
X.Org 1.9.3 drivers intel unloaded: fbdev,vesa Resolution 1024x768@60.0hz
GLX Renderer Mesa DRI Intel 852GM/855GM x86/MMX/SSE2 GLX Version 1.3 Mesa 7.10.2 Direct Rendering Yes
Audio: Card Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller driver Intel ICH ports 1c00 18c0 bus-ID: 00:1f.5
Sound: Advanced Linux Sound Architecture v: 1.0.24
Network: Card-1 Broadcom BCM4401 100Base-T driver b44 v: 2.0 bus-ID: 02:05.0
IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
Card-2 Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter driver ipw2100 v: git-1.2.2 bus-ID: 02:06.0
IF: eth1 state: up mac: 00:04:23:82:12:4b
Drives: HDD Total Size: 76.2GB (3.4% used) 1: /dev/sda IC25N060ATMR04 60.0GB
2: /dev/sdb Name n/a 16.2GB
Optical: /dev/sr0 model: HL-DT-ST DVD+RW GCA-4040N rev: 1.02 dev-links: cdrom,cdrw,dvd,scd0
Features: speed: 24x multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw state: running
Partition: ID:/ size: 3.2G used: 2.5G (80%) fs: rootfs dev: /dev/loop0 label: N/A uuid: 030799ed-b95c-468a-82c6-b2ec60b0cf84
ID:/ size: 3.2G used: 2.5G (80%) fs: ext4 dev: /dev/loop0 label: N/A uuid: 030799ed-b95c-468a-82c6-b2ec60b0cf84
ID:/media/91DC-8EF7 size: 16G used: 2.5G (17%) fs: vfat dev: /dev/sdb1 label: N/A uuid: 91DC-8EF7
Unmounted: ID: /dev/sda1 size: 23.31G label: N/A uuid: 307CE3797CE3386C
ID: /dev/sda2 size: 1.04G label: N/A uuid: N/A
ID: /dev/sda3 size: 14.68G label: N/A uuid: 05462b88-f2fb-4b90-805b-fad7fd9e7d28
ID: /dev/sda5 size: 20.97G label: DATA uuid: 40DE-FE7D
Sensors: Error: You do not have the sensors app installed.
Info: Processes 123 Uptime 0:19 Memory 474.4/1246.0MB Runlevel 5 Client Shell inxi 1.7.9
linux@linux:~>
I played with this Gnome fall back mode for a while. Unfortunately the terminal not properly displaying ansi and coloured text was a serious limitation, I knew I could never use this Gnome fall back implementation.
= = = = =
I decided then to try the 32-bit openSUSE-12.1 milestone2 KDE liveCD. When I booted to that the liveCD appeared to freeze, with a much long pause at the line than I recall seeing with Gnome:
ipw2100 0000:02:06: eth1: Featues changed : 0x00004800 -> 0x00004000
and there was a another long pause at ‘starting MD Raid’ (this ancient laptop has no Raid device).
KDE then partly came up and froze. Nothing. So after 5 minutes I simply restarted by holding down the power button, and switching back on. The mouse moved but no other response. This was the classic i855GM crash seen in many other older kernels (due to kernel/intel driver implementation - crash does not happen with older/basic FBDEV drivers).
Again similar boot behaviour, except this time the PC booted all the way to X. The KDE4 screen was flickering badly, so I quickly disabled desktop effects, which brought stability.
But I do note hundreds of the following message in the dmesg:
419.855750] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times
indicating there are still problems …
Again same 1024x768 resolution with i915 intel driver as noted with the Gnome boot. The wireless was not functioning (possibly associated with the boot error). But I had the wired plugged in and I had internet access from that. Sound worked in Firefox.
Again the same sort of hardware output as I noted with Gnome:
linux@linux:/media/91DC-8EF7/fujitsu/kde> inxi -v 6
System: Host linux.site Kernel 2.6.39-2-default i686 (32 bit gcc 4.6.0)
Desktop KDE 4.6.4 (Qt 4.7.3) Distro openSUSE 12.1 Milestone 2 (i586) VERSION = 12.1 CODENAME = Asparagus
Machine: System FUJITSU SIEMENS (portable) product AMILO M version -1
Mobo FUJITSU SIEMENS model AMILO M version Rev.A Bios Phoenix version R01-S0Z date 12/28/04
CPU: Single core Intel Pentium M (-UP-) cache 1024 KB flags (sse sse2) bmips 2800.18 clocked at 1400.00 MHz
Graphics: Card: Intel 82852/855GM Integrated Graphics Device bus-ID: 00:02.0
X.Org 1.9.3 drivers intel unloaded: fbdev,vesa Resolution 1024x768@60.0hz
GLX Renderer Mesa DRI Intel 852GM/855GM x86/MMX/SSE2 GLX Version 1.3 Mesa 7.10.2 Direct Rendering Yes
Audio: Card Intel 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller driver Intel ICH ports 1c00 18c0 bus-ID: 00:1f.5
Sound: Advanced Linux Sound Architecture v: 1.0.24
Network: Card-1 Broadcom BCM4401 100Base-T driver b44 v: 2.0 bus-ID: 02:05.0
IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A
Card-2 Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter driver ipw2100 v: git-1.2.2 bus-ID: 02:06.0
IF: eth1 state: dormant mac: 00:04:23:82:12:4b
Overall I can see I won’t be able to run 12.1 M2 on this laptop with the intel i915 driver. I probably need to try with the FBDEV driver, but it appears KDE (because of its wireless) won’t be an option, and the Gnome3 desktop appears it will have problems with this old hardware. BUT I am hopefully LXDE with the FBDEV driver might work on this laptop, as it uses the same network manager as Gnome.
Unfortunately having to resort to the FBDEV with 12.1 is a disappointment, just like it was with 11.4, 11.3, and 11.2. openSUSE-11.1 was the last openSUSE version to run well on this laptop. Unfortunately Evergreen has moved to a new kernel than the 2.6.27 so the current GNU/Linux software can no longer fully use this laptop’s older hardware.
There’s something that’s partially broken with the plasmoid-networkmanagement. This may be a contributing factor to the wireless problem.
Hardware Detection
I finding that the hardware detection is slow and sometimes missing some hardware.
Any thoughts?
#oldcpu
Check the earlier posts in this thread. The fall back to a “classic Gnome” format has nothing to do with graphics drivers - it’s just that “gnome-shell” was not packaged in the LiveCD (I’m sure there was an excellent reason for that omission). Manually installing “gnome-shell” and its extensions (except the “xrandr” one, which is broken) fixes that. For M2, you’ll also need to install “libgnomesu” and its dependencies in order to launch “yast2”. Both, obviously, are specific problems for the Gnome version, which do not affect the KDE version - which has, as you observe, some compensating disadvantages. Ah, the joys of alpha testing!
Mind you, I now have a stable, pleasant openSUSE Gnome M2 system - my remaining issues with which really belong upstream, since Gnome3 is still a work in progress.
Thanks for that info. I’m not particularly keen on installing 12.1 M2 on this old Fujitsu-Siemens laptop (I’ll wait for 12.1 GM before any install, if I do install). I suspect to load ‘gnome-shell’ and its extensions ‘might’ push the amount of RAM this old laptop has when running from the Gnome 12.1 M2 liveCD. Presumably one has to then restart X by an init 3 to run level 3, followed by an init 5 back to run level 5 (when booting from the liveCD). … I might try that later. 
I booted the 64-bit openSUSE-12.1 Milestone2 KDE liveCD to my main PC, which runs a Core i7 920 with nVidia GTX260 graphics (more detail on the hardware later).
X booted fine into KDE at 1920x1200 resolution using the nouveau graphic driver.
Sound did not immediately work, which was no surprise as I saw identical behaviour with openSUSE-11.4. The problem here is this computer’s webcam is identified as sound device-0 and the mother-board audio card identified as sound device-1. Hence no sound as sound by default will play from card-0.
The way to get it working is this: If I go to YaST, configure the audio card, set it as primary, enable pulse, then close YaST and with root permissions run ‘rcalsasound restart’ the motherboard sound device is then reconfigured as the primary sound card and then sound properly works. 
Of course if I boot the liveCD without the webcam plugged in, sound ‘just works’ .
Some details on this initial sound misconfiguration where the primary sound card should be card-0 (note there is no card-0 below):
**When sound NOT working:
**
First from ’ aplay -l ’
**** List of PLAYBACK Hardware Devices ****
card 1: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
… note the sound device is card-1 (and not card-0) and note that upon first booting the liveCD there is no /etc/modprobe.d/50-sound.conf file.
Here is the alsa-info.sh script file when sound is not working on 1st boot: http://www.alsa-project.org/db/?f=f2aa52deed778f520515876923fe6d36da36c1a3
Possibly the output of amixer (run immediately after boot) makes this most clear where there is only the webcam USB mic and no mother board sound device showing:
Simple mixer control 'Mic',0
Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
Capture channels: Mono
Limits: Capture 0 - 52
Mono: Capture 28 [54%] -43.00dB] [on]
**When sound working:
**
Then after reconfiguring the motherboard sound device so that it now works with ’ aplay -l ’ :
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: AD198x Digital [AD198x Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
Note motherboard sound is now sound card-0 (and NOT sound card-1).
amixer is too big to repeat here, and one can see it now in the diagnostic script : http://www.alsa-project.org/db/?f=c7ae379ea744a6508046ffa7c7d63cae70de563e
and finally YaST created a 50-sound.conf file:
options snd slots=snd-hda-intel
# u1Nb.8NnaCbrSEoE:82801JI (ICH10 Family) HD Audio Controller
alias snd-card-0 snd-hda-intel
It was a revelation finally nailing down what was happening here! … and of course once one knows what is happening its very easy to address !
**OTHER
**
Some more detail on 12.1 M2 on this PC … here is the graphic card:
07:00.0 VGA compatible controller [0300]: nVidia Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:82cf]
Kernel driver in use: nouveau
where the graphics work fine.
In fact all appears to work ok now that I have sound sorted. Here is the output of inxi (custom rebuilt for 12.1 M2):
linux@linux:/usr/src/packages/RPMS/noarch> inxi -v 6
System: Host linux.site Kernel 2.6.39-2-desktop x86_64 (64 bit gcc 4.6.0)
Desktop KDE 4.6.4 (Qt 4.7.3) Distro openSUSE 12.1 Milestone 2 (x86_64) VERSION = 12.1 CODENAME = Asparagus
Machine: Mobo ASUSTeK model P6T DELUXE V2 version Rev 1.xx Bios American Megatrends version 0504 date 05/19/2009
CPU: Quad core Intel Core i7 CPU 920 (-HT-MCP-) cache 8192 KB flags (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips 21381.9
Clock Speeds: (1) 1600.00 MHz (2) 1600.00 MHz (3) 1600.00 MHz (4) 1600.00 MHz (5) 1600.00 MHz (6) 1600.00 MHz (7) 2668.00 MHz (8) 1600.00 MHz
Graphics: Card: nVidia GT200 [GeForce GTX 260] bus-ID: 07:00.0
X.Org 1.9.3 drivers nouveau unloaded: vesa,fbdev,nv Resolution 1920x1200@60.0hz
GLX Renderer Rasterizer GLX Version 2.1 Mesa 7.10.2 Direct Rendering Yes
Audio: Card Intel 82801JI (ICH10 Family) HD Audio Controller driver HDA Intel bus-ID: 00:1b.0 Sound: ALSA v: 1.0.24
Network: Card-1 Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver sky2 v: 1.28 port b800 bus-ID: 09:00.0
IF: eth1 state: down speed: 65535 Mbps duplex: full mac: 00:24:8c:7e:ee:38
Card-2 Marvell 88E8056 PCI-E Gigabit Ethernet Controller driver sky2 v: 1.28 port d800 bus-ID: 0b:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 00:24:8c:7e:ee:39
Drives: HDD Total Size: 1500.3GB (-) 1: /dev/sda ST31500341AS 1500.3GB
Optical-1: /dev/sr0 model: TSST DVD-ROM SH-D163B rev: SB02 dev-links: cdrom,dvd,scd0
Features: speed: 48x multisession: yes audio: yes dvd: yes rw: none state: running
Optical-2: /dev/sr1 model: HP DVD Writer 1270d rev: GH23 dev-links: cdrom1,cdrw1,dvd1,dvdrw1,scd1
Features: speed: 48x multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID:/ size: 6.3G used: 2.7G (43%) fs: rootfs dev: /dev/loop0 label: N/A uuid: 51dba482-46b4-40af-8bd2-68d1cd53f20e
ID:/ size: 6.3G used: 2.7G (43%) fs: ext4 dev: /dev/loop0 label: N/A uuid: 51dba482-46b4-40af-8bd2-68d1cd53f20e
Unmounted: ID: /dev/sda1 size: 104.86G label: N/A uuid: AEFC5830FC57F0D7
ID: /dev/sda2 size: 31.45G label: main-root uuid: 21f939b4-f9cb-4d80-885c-3f4f37ff52bf
ID: /dev/sda3 size: 15.73G label: N/A uuid: b55b0f38-695b-4a9d-b0ab-ed0268da5a0c
ID: /dev/sda5 size: 6.82G label: swap uuid: 8cb7467f-355d-4564-9df1-0f37b2a9f3b5
ID: /dev/sda6 size: 36.70G label: sandboxhome uuid: 2425b453-e9f7-48e6-b102-ee979331c2d7
ID: /dev/sda7 size: 1304.75G label: N/A uuid: 4a1afa51-0c42-4f9f-81a2-0bf43fc86fb5
Sensors: Error: You do not have the sensors app installed.
Info: Processes 173 Uptime 0:28 Memory 1075.1/5972.4MB Runlevel 5 Client Shell inxi 1.7.9
My impression is 12.1 M2 is better than many past GM releases. Installed on an SLED certified Athlonx X2 box. Ancient Toshiba laptop with Intel graphics failed (as did 11.4), had to work hard & round things to get 11.3 running on that one so no suprise there.
An SSD only recognised by 11.4 after kernel updates was found by installation, however an error occured and it’s partitions became unavailable. Something to do with the SSD & chipset combo, it runs well under Win 7. Unfortunately no notification of error, or inability to edit partition usage in partitioner was reported, needed to look round at logging on other consoles to suss this out.
Most of my bug reports so far are relatively cosmetic minor things, the Installation could be clearer described (as noted frequently by openSUSE reviwers). In general was happy working with it, graphics, sound was running, some self made video in AVI format to.
Trying eventually to Leave KDE & “Restart Computer” resulted in dim screen, rather than countdown menu & non-reactive KDE window management.
un 26 14:35:01 fir kcheckpass[5314]: Authentication failure for ladm (invoked by uid 1000)
Jun 26 14:35:25 fir su: (to root) ladm on /dev/pts/0
Jun 26 14:35:25 fir su: pam_apparmor(su-l:session): Unknown error occurred changing to root hat: Operation not permitted
Jun 26 14:35:40 fir kdm[30026]: Cannot execute ‘grub-set-default’: not in $PATH.
Jun 26 14:35:44 fir pulseaudio[32079]: ratelimit.c: 249 events suppressed
Looks like minor authentication problem to set UID root to invoke reboot, don’t know why it’s not a null OP though when it fails.
On 06/26/2011 10:06 AM, robopensuse wrote:
>
> My impression is 12.1 M2 is better than many past GM releases.
> Installed on an SLED certified Athlonx X2 box. Ancient Toshiba laptop
> with Intel graphics failed (as did 11.4), had to work hard& round
> things to get 11.3 running on that one so no suprise there.
My first impressions are quite different. I used the NET install CD to upgrade a
VirtualBox VM from 12.1 MS1 to 12.1 MS2. At first everything went well, then it
all fell apart and the KDE desktop would not respond to any mouse clicks. I
ended up having to use the KDE Live CD to reinstall. That one is working so far
other than you cannot shutdown from the desktop.
Is that the same bug as I reported for KDE Leave -> Restart Computer? Bug #702220 - KDE leave Reboot Fails Leaving Dim Screen & Useless Desktop; I’m kind of glad if it is not just me as I’ve had trouble reproducing KDE post-install bugs in past, of kind that leave a bad impression on new users.
I used Net Install CD to, but it was a clean install; I did chose some specialist filesystem options like ext4 without journal, and it was I try and test on real hardware not a VM with Live CD as those are very popular for application try outs.
Will try it out on some older hardware and see if I can raise some kernel driver regression issues, which (hopefully) will get fixed before Novemember & the GM release. The objective should be finding bugs early to raise quality, rather than worry about the distro being broken, like you would on production versions like 11.4 or Tumbleweed.
On 06/26/2011 03:06 PM, robopensuse wrote:
> Is that the same bug as I reported for KDE Leave -> Restart Computer?
> 'Bug #702220 - KDE leave Reboot Fails Leaving Dim Screen& Useless
> Desktop ’ (https://bugzilla.novell.com/show_bug.cgi?id=702220); I’m kind
> of glad if it is not just me as I’ve had trouble reproducing KDE
> post-install bugs in past, of kind that leave a bad impression on new
> users.
I think that is the same bug.
> I used Net Install CD to, but it was a clean install; I did chose some
> specialist filesystem options like ext4 without journal, and it was I
> try and test on real hardware not a VM with Live CD as those are very
> popular for application try outs.
>
> Will try it out on some older hardware and see if I can raise some
> kernel driver regression issues, which (hopefully) will get fixed before
> Novemember& the GM release. The objective should be finding bugs early
> to raise quality, rather than worry about the distro being broken, like
> you would on production versions like 11.4 or Tumbleweed.
Checking the drivers for older hardware is a good idea; however, you could do
the same by installing kernel 2.6.39 in openSUSE 11.4. BTW, I have no driver
issues with that kernel on a wide variety of hardware. As for testing kernels
for oS 12.1, mainline is now at 3.0-rc4 and the final 3.0 will be released in
less than one month. I expect oS 12.1 will come with that kernel. It will be
doubly important to test when that switch happens.
One thing to remember is that a lot of people are testing kernels. It is the
distro-specific things that need the most testing by us.
Hence running install for real.
I’ve had issues in past that showed fixes had been included by another distro, or some change in openSUSE.
Already have 1 machine where 11.4 & 12.1 M2 won’t boot, my impression is those installing & testing vanilla kernels are heavily weighted in favour of recent hardware, many casual users try things but give up, rather than perservere with bug reports.
Hi,
I am using openSUSE 12.1 M2 64-bit KDE. Installation via Live Installer of the Live CD.
The font in YAST is too small, so I logged into the terminal as root and run qtconfig to increase the font size from default 9 to 14.
Established wired and wireless connection via ifup in YAST. Only wired connection works. System tray still shows a red X for Network Management icon. Network Management settings only show VPN tab, but the Wired and Wireless connection tabs are grayed out.
How do I “update”? Because “zypper up” reports “nothing to do”.
On 06/26/2011 07:36 PM, robopensuse wrote:
>
> lwfinger;2358506 Wrote:
>> Checking the drivers for older hardware is a good idea; however, you
>> could do
>> the same by installing kernel 2.6.39 in openSUSE 11.4.
>> …
>> One thing to remember is that a lot of people are testing kernels. It
>> is the
>> distro-specific things that need the most testing by us.
> Hence running install for real.
>
> I’ve had issues in past that showed fixes had been included by another
> distro, or some change in openSUSE.
> Already have 1 machine where 11.4& 12.1 M2 won’t boot, my impression
> is those installing& testing vanilla kernels are heavily weighted in
> favour of recent hardware, many casual users try things but give up,
> rather than perservere with bug reports.
Granted, the primary kernel developers have some of the latest and greatest
hardware, but there are a lot of us that keep old hardware around just for
testing that new kernels will boot and work correctly. I start my testing with
the -rc1 version of every kernel. I do persevere with bug reports. In addition,
I find the whole kernel culture to be very diligent in fixing bugs, particularly
those that are regressions.
Thank you Dale and Larry for the NM workaround via network-manager-gnome.
Hi again,
I still have no icon for NM after reboot. I did the following:
-
Install NetWorkManager-gnome v. 0.8.999-1.1
-
Uninstall plasmoid-networkmanagement 0.9.1git20110503-2.1
-
Uninstall NetworkManager-kde4-libs
-
Made nm-applet autostart upon login:
$ ln -s /usr/bin/nm-applet ~/.kde4/Autostart/nm-applet-link
My oxygen-gtk is >1.0.3 i.e. 1.0.5-4.1, but I cannot add the repo called:
http://download.opensuse.org/repositories/KDE/UpdatedApps/openSUSE_12.1kua, because it does not exist yet.
I followed the direction from GNOME NetworkManager Applet in KDE in openSUSE 11.4, which is at the bottom of /forums.opensuse.org/english/get-technical-help-here/wireless/456231-gave-up-knetworkmanager-made-networkmanager-gnome-work-kde4.html
Any suggestions?
Hi,
Just to clarify. First I tried the workaround by installing NetworkManager-Gnome but this did not work for me. Then I tried the more elaborate procedure above (Gnome NetworkManager Applet in KDE in openSUSE 11.4).
Any suggestions?
What you’re doing is great and I try it is worthwhile for others to do similar, so regressions are caught early, rather than late.
In past new releases of compilers have caused issues on real hardware, or changes to configuration of system; and when you do find those kind of bugs, they often take a while to sort; sometimes I’ve had fixes and a kernel maintainer still threw the mod oout (because the documentation said different & the change did what the old driver actually had done, rather than what the “specs” said). More users saying they had same breakage and the fix was a fix, would have helped. Everyone hammering the same stuff in Virtualbox or VMware has the danger that applications are tested much better than distro support for new kernel features & problems arising. A recent example might be KMS, where without other upgrades, you ran the kernel effectively in a compatability mode.
A quick report.
I tried the live KDE. I used the 32 bit version, since all of my machines can handle that. Thus far, I have tried it (several boots) on a 2004 Toshiba laptop, and a 2010 Dell laptop.
The KDE network manager doesn’t work (as reported by others). However, the main NetworkManager daemon is making wired connections, as long as I plug in a live ethernet.
On the 2004 Toshiba (radeon graphics): With 11.4, there was a very noticable screen flicker every few seconds. With M2, that flicker is gone. That looks like a good change.
On the 2010 Dell:
(1) The broadcom WiFi card seems to be recognized, using only the provided open source drivers. I tested this with “iwlist”, which was able to see several networks. I didn’t try connecting, due to the KDE network manager problems.
(2) Thus far, the touchpad has always been recognized. With 11.4, that was iffy. It always worked in 11.4, but sometimes it appears to have been recognized as if a regular mouse instead of as a touchpad. WIth M2, it has been recognized as a touchpad every time.
(3) I still get occasional freezes, presumably problems with the Intel graphics driver.
I guess 2 out of 3 is pretty good.
On 06/22/2011 02:06 PM, oldcpu wrote:
>
> I did not see an openSUSE-12.1 milestone-2 thread, so I thought that I
> would start one.
…]
DVD 64-bit KDE install.
I downloaded ‘fluxbox’ from “‘factory’ X11:windowmanagers” repo.
From a terminal,I could not launch ‘Dolphin’ or ‘Konqueror’: something
about dbus. At the suggestion from Networkmanager (?), I tried on the
command-line:
export $(dbus-launch).
After that, dolphin/konqueror worked.