April 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 471741] Installation Fails with DVD Read Error Despite Physical Media Being Perfectly Good
by bugzilla_noreply＠novell.com 02 Apr '09

02 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=471741 User alpha096(a)virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=471741#c21 --- Comment #21 from Scott Couston <alpha096(a)virginbroadband.com.au> 2009-04-01 22:10:37 MDT --- Additional info - The Factory Suse DVD has no issue with any such problems. Its only every DVD from supplier that I have got from them since 10.3. In the case I only use the DVD supplier I copy the contents of the DVD to an Install Server - all O.K Then I download and burn my own ISO Network Installation from suse.de. IF I use the DVD from the supplier to start the Network Install, it fails as it is unable to mount the Installation Repository from DVD due a very log error string - but summarised as a read/possibly verify reason. I thought I was just getting bad CD in the past and then Bad DVD now - But there must be so much more in it that that - The media is fine -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 488490] domUloader.py can't handle block device names with :
by bugzilla_noreply＠novell.com 02 Apr '09

02 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=488490 User jfehlig(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=488490#c4 --- Comment #4 from James Fehlig <jfehlig(a)novell.com> 2009-04-01 21:49:10 MDT --- (In reply to comment #3) > The updated domUloader seems to seems to work. However, you might want to > change it to .split(' : ') just in case the volume name ends with a : Agreed - that is safer with current output of 'kpartx -l'. I don't particularly like screen-scraping these commands ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 490770] crash @ pci passthrough of pci/sata device to DomU
by bugzilla_noreply＠novell.com 02 Apr '09

02 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=490770 User pgnet.trash(a)gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=490770#c4 pgnet _ <pgnet.trash(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash(a)gmail.com | --- Comment #4 from pgnet _ <pgnet.trash(a)gmail.com> 2009-04-01 20:11:56 MDT --- Created an attachment (id=283569) --> (http://bugzilla.novell.com/attachment.cgi?id=283569) logs etc from various cases, as described jan, i've tried to add your suggestions as well as simplify a bit, and provide what i think is helpful; of course, let me know if/what else you specifically need. booted Dom0 to, title Xen (symlink) NORMAL root (hd0,0) kernel /xen.gz dom0_mem=768M loglvl=all loglvl_guest=all vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1 swiotlb=256 module /vmlinuz-xen root=/dev/VG_Dom0/LV_ROOT resume=/dev/VG_Swap/LV_SWAP showopts splash=silent vga=0x31a console=tty0 console=xvc0,57600 elevator=cfq max_loop=64 pci_devs_to_hide=(04:07.0)(04:08.0) reassigndev=0000:04:07.0,0000:04:08.0 module /initrd-xen w/ egrep "install|04" /etc/modprobe.conf.local options pciback hide=(0000:04:07.0)(0000:04:08.0) install sata_sil24 /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install sata_sil24 install ohci1394 /sbin/modprobe pciback ; /sbin/modprobe --first-time --ignore-install ohci1394 uname -ri 2.6.27.19-3.2-xen x86_64 and verifying, dmesg | egrep seiz pciback 0000:04:07.0: seizing device pciback 0000:04:08.0: seizing device 3 cases, (1) sata-sil24 drives attached & ON, passthrough OFF in xen config -> boots OK grep pci nas_init.cfg, # pci = [ '04:07.0', '04:08.0' ] attachments: case1_console_Dom0_pass_OFF.txt case1_xenlogs_Dom0_pass_OFF.txt case1_bootmsg_DomU_pass_OFF.txt (2) sata-sil24 drives attached & ON, passthrough ON in xen config -> CRASH grep pci nas_init.cfg, pci = [ '04:07.0', '04:08.0' ] attachments: case2_console_Dom0_pass_ON.txt case2_xenlogs_Dom0_pass_ON.txt (2) sata-sil24 drives attached & OFF, passthrough ON in xen config -> boots OK grep pci nas_init.cfg, pci = [ '04:07.0', '04:08.0' ] @ DomU uname -ri 2.6.27.19-3.2-xen x86_64 lspci 00:00.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02) 00:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0) attachments: case3_console_Dom0_pass_ON.txt case3_xenlogs_Dom0_pass_ON.txt case3_bootmsg_DomU_pass_ON.txt so, it seems, passthrough works -- as long as the drives themselves are OFF :-/. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 481299] Yast Scanner Model and Driver Devours system resources at the expense of basic O/S
by bugzilla_noreply＠novell.com 02 Apr '09

02 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=481299 User alpha096(a)virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=481299#c23 Scott Couston <alpha096(a)virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|alpha096(a)virginbroadband.co | |m.au | --- Comment #23 from Scott Couston <alpha096(a)virginbroadband.com.au> 2009-04-01 19:16:49 MDT --- Before I get to logs - I assume the normal Yast logs? Also some question on how Linux responds to some Hardware variables and this may answer why when I insert a new USB device into a New BUS ID the boot process is halted - no time out after 30 mins and no further than boot detecting new USB device. Q. With X_64 AMD we have the option to run in cool and quiet mode or not. Most of us choose disable as the CPU starts at very low frequency and is pathetically slow to up to nominal CPU clock frequency - so most of us leave it disabled to enjoy the performance benefits. 1. Benefits of Disable are CPU clock remains constant, however All ACPI, _PCC, _PSS, _PCT calls are rejected from the O/S and Bios Manages the cooling Policy. 2. Benefits of Enable is that the above O/S calls are not ignored, BUT the CPU clock start at minimum and is so very very very late in placing the CPU clock to its normal frequency and the O/S has to demand CPU performance for quite a long while. Other BIOS Questions related are Plug and Play device can only be set to O/S or BIOS - which do you wish -does it matter. Is legacy support for USB required or will support for V1.1 and V2.0 all o.k? Do I need to enable ACPI SRAT Table Y/N Can you get back to me on the above and I will assume logs are normal Yast Logs. By supplying this info you may well have solved USB device issues!? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 449083] radeon: ati rs4xx (0x5974) vga: monitor claims out of sync.
by bugzilla_noreply＠novell.com 02 Apr '09

02 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=449083 User sndirsch(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=449083#c30 --- Comment #30 from Stefan Dirsch <sndirsch(a)novell.com> 2009-04-01 18:55:04 MDT --- On 11.1 we still had 6.9.0 radeon driver. There has been various fixes for RS4xx afterwards, so that there is still some hope that the issue will be fixed with a newer driver release. Candidates: commit 33f88f7fc90d9d93fdcbba9ad59dd70a6596bc3f Author: Alex Deucher <alexdeucher(a)gmail.com> Date: Thu Aug 7 17:57:07 2008 -0400 RS4xx DDC fixes take 3 commit df0d1ef53100f0a19c5b5fdc349f5186c8d9bd87 Author: Alex Deucher <alexdeucher(a)gmail.com> Date: Wed Aug 6 19:13:56 2008 -0400 RS4xx: Fix up ddc gpio - I mixed up the regs previously commit eb65ddf70d182b6457e1ef5ebb820456039e8f6d Author: Alex Deucher <alexdeucher(a)gmail.com> Date: Tue Aug 5 15:01:33 2008 -0400 IGP: attempt to get external TMDS working RS4xx chips have a tmds init table in the mobile info table commit 8b8990917809b9a35c6e9c1b9e3b12ff81c6dbb3 Author: Alex Deucher <alexdeucher(a)gmail.com> Date: Tue Aug 5 12:16:06 2008 -0400 IGP: Updated quirk handling - Hopefully finally fix DDC on RS4xx chips - RS3xx/RS4xx do not have internal TMDS - general quirk handling cleanup - we don't currently support mm gpio for external TMDS so return false. commit 72992668ca96717bf69bcea95a5deeaf7c57e826 Author: Alex Deucher <alex(a)botchco.com> Date: Mon Jun 30 14:09:09 2008 -0400 RS4xx: enable the DRI by default on all variants Some RS4xx chips had the DRI disabled by default. With the recent drm and ddx changes these chips have been reported to work now with the DRI. Unfortunately the hardware we once had for testing somewhat vanished. This makes testing for ourselves impossible. The best would be to find someone affected by this and who is familiar with building a driver from git to check, if the issue is already fixed and if that's true to bisect the driver to figure out, which commmit fixed it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 489591] KControl error on selecting Keyboard Shortcuts: No such object path '/KdedGlobalAccel' Error: org.freedesktop.DBus.Error.UnknownObject
by bugzilla_noreply＠novell.com 02 Apr '09

02 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=489591 User hedgehogshiatus(a)gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=489591#c1 --- Comment #1 from Hedge Hog <hedgehogshiatus(a)gmail.com> 2009-04-01 18:23:04 MDT --- Replaced kde3 repos with the STABLE for KDE 4.1.3.Ran: sudo zypper dup It appears that kcontrol/kde4 is no longer installed from the 11.0 STABLE KDE repos. Open systemsettings: Keyboard & Mouse>>Keyboard Shortcuts>>KDE Component:KWin Both the Desktop Screeshot and Windows Screen shot shortcuts are correctly set. Neither shortcuts work, /var/log/messages shows errors. KDE Menu Editor [(KDE 4.1.3) "release 75.2"] shows the ksnapshot shortcut key is unset. So the bug seems to be that the KDE menu Editor in 4.1.3 does not know about the 4.1.3 system settings? # systemsettings --version Qt: 4.4.3 KDE: 4.1.3 (KDE 4.1.3) "release 75.2" System Settings: 4.1.3 (KDE 4.1.3) "release 75.2" Correct? Finally starting system settings from the command line, as root, opens without any error dialogs, but at the command line: # systemsettings findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found findServiceByDesktopPath: not found /var/log/messages shows no errors. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 491124] ntpd host name not found during system startup
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=491124 User lmuelle(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=491124#c1 --- Comment #1 from Lars Müller <lmuelle(a)novell.com> 2009-04-01 16:53:38 MDT --- http://lists.opensuse.org/opensuse/2009-03/msg02078.html was the starting point of the discussion on the openSUSE ML. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 488490] domUloader.py can't handle block device names with :
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=488490 User kamil(a)zymeworks.com added comment http://bugzilla.novell.com/show_bug.cgi?id=488490#c3 --- Comment #3 from Kamil Kisiel <kamil(a)zymeworks.com> 2009-04-01 16:41:01 MDT --- Hi James, The updated domUloader seems to seems to work. However, you might want to change it to .split(' : ') just in case the volume name ends with a : -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 488490] domUloader.py can't handle block device names with :
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=488490 User jfehlig(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=488490#c2 James Fehlig <jfehlig(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |kamil(a)zymeworks.com --- Comment #2 from James Fehlig <jfehlig(a)novell.com> 2009-04-01 16:23:28 MDT --- Kamil, Can you try the updated domUloader in comment #1 and report back? Thanks! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 488490] domUloader.py can't handle block device names with :
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

http://bugzilla.novell.com/show_bug.cgi?id=488490 User jfehlig(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=488490#c1 --- Comment #1 from James Fehlig <jfehlig(a)novell.com> 2009-04-01 16:22:13 MDT --- Created an attachment (id=283552) --> (http://bugzilla.novell.com/attachment.cgi?id=283552) updated domUloader.py Replace /usr/lib/xen/boot/domUloader.py with this update. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0