June 2006 - openSUSE Users - openSUSE Mailing Lists

[SLE] Having a /data partition
by mlist＠safenet-inc.com 02 Jun '06

02 Jun '06

I wanna make a /data partition to house all the stuff that I currently keep in /home, so that I can blow away my /home for the 10.1 installation. I don't want to have any lingering config or profile stuff that might conflict in any way with the new install, so I'd format even /home. So tell me... does this sound like the simplest strategy: 1) Back up everything useful (of course) 2) Plug in the 10.1 DVD and start installing. 3) When I get the option to partition, I just change the mount name of my current /home to /data 4) Allocate the rest of the drives in whatever way seems pleasing, but carve off a small corner of one to become the new /home. 5) Everything except /home-renamed-to-/data gets formatted Reiserfs. 6) Finish up the rest of the installation and enjoy unadulterated 10.1 setup with no held-over baggage. Unless I'm overlooking something, that seems like less trouble than logging in at run-level 3 and re-partitioning before doing the Install. Am I overlooking something? Is any of this a bad idea? Kevin The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

8 11

[SLE] 10.1 installed. Not too bad...
by Lew Wolfgang 02 Jun '06

02 Jun '06

Hi Folks, I know that things have been rather contentious around here lately. For my part, I'd like to thank the SuSE folks who listen here for taking our guff. It's remarkable that SuSE has been offering these mailing lists for years now, and that real SuSE people are listening and providing info. I can't think of any other manufacturer-provided venue where employees are allowed to mingle with the public. Thanks SuSE, and Novell! I just managed to install 10.1 on a PIII with 512-MB of ram. Except for some long pauses now and again, things went ok. Yast Update didn't find anything to update until I performed the first reboot and did the Update Configuration and Update Settings things. The Online Updater even works, if you wait long enough. I was also able to add Packman to the Installation Source thing. However, I can't find dvgrab or GNU FORTRAN anywhere. Do I need the boxed distro for those? This install was just a proof-of-concept for me. I now feel confident enough to purchase a few of the boxes when they're available here and try to install on more challenging platforms, including dual Opterons. That being said, it certainly "seems" like a PHB (Pointy-Haired Boss) has been mucking around here lately. But I'm willing to stick it out, I'm sure that the kinks will be straightened. Thanks! Lew Wolfgang -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

6 11

Re: [SLE] Re: And another 10.1 showstopper
by Kai Ponte 02 Jun '06

02 Jun '06

> On Wednesday 31 May 2006 00:02, Ken Schneider wrote: > > > Now this idea of removing all this non-GPL stuff.... what was gained by > > > that? And that is a Novell-only decision, right? > > > > Actually it was the kernel devs that dictated it, they didn't ask it to > > be so they made it mandatory. > > Then how in heck is Linux ever going to become a mainstream operating system > when the kernel can't have proprietary code hung off of it and the vendors > aren't that interested in developing proprietary code to begin with? Where > do they think this is going to lead? Very interesting - and scary - developments. I had read about how Novell was planning on de-coupling the non-GPL kernel-level drivers from the system and wondered what effect this would have. I honestly don't see where in the GPL that having a non OSS chunk compiled in is a violation. From what I've understood, the GPL simply states that one can't take a GPL'd piece of code and make it non-GPL. It would seem to me that Novell, RedHat, Ubuntu and Joe's Cool Distro would have the freedom to put whatever driver they want in their distro as long as copyright laws aren't broken. I've read that Fedora 5 - which I haven't installed - has the same issue with their unhooking of the drivers. I'm wondering why RedHat and Novell didn't simply wait a few releases until a better solution was worked out before decoupling the drivers. That would have made much more sense that pissing of hundreds or thousands of end users. From what I understand - in addition to not being shipped with the distros, the drivers will now break every time a kernel update is performed. It would seem that some solution where the kernel simply hooks to a vendor-supplied driver would be preferable. That driver could be VGA or ATI or Nvidia or whatever. Isn't that what a HAL is for? So essentially we have two choices - either Novell and RedHat and Ubuntu and whomever decide how to put working Non-GPL drivers into the distribution so that we can have our eye-candy or Linux will be forever relegated to the server farm. This sucks. (Yes folks, that is my highly-academic evaluation of the situation.) > > DLL's anyone? w00t! Visual C++ for Linux using the MFC! Let me break out my Visual Studio 6.0 CD and fire it up. Im thinking maybe if we have a small kernel lets call it kernel386.exe and then a HAL for the hardware well call it hal.dll we should get something going. If I then put a posix-compliant subsystem on top of it, I should then name it win32k.sys. Hmmmaybe I have something here.Im going to name the new OS Scenery. -- kai

10 15

Re: [SLE] can I run two X server on one single host?
by Zhang Weiwu 02 Jun '06

02 Jun '06

On Fri, 2 Jun 2006, Zhang Weiwu wrote: > Just curious, is it possible to run two X server on one single host with two > seperate video card? Perhaps this question is not particular to SuSE but to > any linux as well. I am thinking if I plug another set of USB keyboard and > mouse, I can let my nephew play computer games (mostly emulated XMAME games) > on my old CRT screen and leaving me using the main keyboard/screen to work > on my OOO documents without having to getting him another computer. This > computer happen to have two video card, the onboard card is currently not > used because in order to play game we bought another better 3D card. > I thought the second card is a good 3D card but actually it is an old SIS card sitting on PCI, that doesn't matter, I don't need good card. Looking into xorg.conf the structure is pretty clear and simple. There was two Screen and Device section, the person installed SuSE for me commented out the Screen/Device section related to the PCI vga card, I removed the comments and issued X :1.0 -screen 'Screen[1]' That gives a lot of error message, most importantly is 'Requesting insufficient memory window!'. The error log is attached at the end of this email. Has anyone tried and succeeded in this way of running two X server on separate video cards? X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: SuSE Linux [ELF] SuSE Current Operating System: Linux joe 2.6.16.13-4-default #1 Wed May 3 04:53:23 UTC 2006 i686 Build Date: 02 May 2006 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.0.log", Time: Fri Jun 2 14:15:58 2006 (==) Using config file: "/etc/X11/xorg.conf" (++) |-->Screen "Screen[1]" (0) (**) | |-->Monitor "Monitor[0]" (**) | |-->Device "Device[1]" (==) |-->Input Device "Mouse[1]" (==) |-->Input Device "Keyboard[0]" (WW) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (WW) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (WW) The directory "/usr/X11R6/lib/X11/fonts/Speedo" does not exist. Entry deleted from font path. [snip] (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) Input device list set to "/dev/gpmdata,/dev/input/mice" (==) ModulePath set to "/usr/X11R6/lib/modules/updates,/usr/X11R6/lib/modules" (**) Option "AllowMouseOpenFail" "on" (II) Open ACPI successful (/var/run/acpid.socket) (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) using VT number 8 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2560 card 8086,2560 rev 01 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2562 card 8086,5641 rev 01 class 03,00,00 hdr 00 (II) PCI: 00:1d:0: chip 8086,24c2 card 8086,5641 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 8086,5641 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 8086,5641 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 8086,5641 rev 01 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card 0000,0000 rev 81 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card 0000,0000 rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 8086,5641 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 8086,5641 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 8086,0208 rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1039,0300 card a0a0,001f rev 90 class 03,00,00 hdr 00 (II) PCI: 01:08:0: chip 8086,1039 card 8086,3048 rev 81 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x0206 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0x0000d000 - 0x0000d0ff (0x100) IX[B] [1] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B] [2] -1 0 0x0000d800 - 0x0000d8ff (0x100) IX[B] [3] -1 0 0x0000dc00 - 0x0000dcff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xff800000 - 0xff8fffff (0x100000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xd6a00000 - 0xe6afffff (0x10100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device rev 1, Mem @ 0xf0000000/27, 0xffa80000/19 (--) PCI: (1:0:0) Silicon Integrated Systems [SiS] 300/305 PCI/AGP VGA Display Adapter rev 144, Mem @ 0xd8000000/27, I/O @ 0xd000/7 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xf8000000 from 0xfbfffff0 to 0xf7ffffff (II) Active PCI resource ranges: [0] -1 0 0xff8ff000 - 0xff8ffff0 (0xff1) MX[B] [1] -1 0 0xffa7f400 - 0xffa7f4f0 (0xf1) MX[B] [2] -1 0 0xffa7f800 - 0xffa7f9f0 (0x1f1) MX[B] [3] -1 0 0x40000000 - 0x400003f0 (0x3f1) MX[B] [4] -1 0 0xffa7fc00 - 0xffa7fff0 (0x3f1) MX[B] [5] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O [6] -1 0 0xffa80000 - 0xffaffff0 (0x7fff1) MX[B](B) [7] -1 0 0xf0000000 - 0xf7fffff0 (0x7fffff1) MX[B](B) [8] -1 0 0x0000dc00 - 0x0000dc30 (0x31) IX[B] [9] -1 0 0x0000e080 - 0x0000e0b0 (0x31) IX[B] [10] -1 0 0x0000e400 - 0x0000e4f0 (0xf1) IX[B] [11] -1 0 0x0000e000 - 0x0000e010 (0x11) IX[B] [12] -1 0 0x0000ffa0 - 0x0000ffa0 (0x1) IX[B] [13] -1 0 0x0000ec00 - 0x0000ec10 (0x11) IX[B] [14] -1 0 0x0000e880 - 0x0000e890 (0x11) IX[B] [15] -1 0 0x0000e800 - 0x0000e810 (0x11) IX[B] (II) Inactive PCI resource ranges: [0] -1 0 0xd8000000 - 0xdffffff0 (0x7fffff1) MX[B](B) [1] -1 0 0x0000d000 - 0x0000d070 (0x71) IX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xff8ff000 - 0xff8ffff0 (0xff1) MX[B] [1] -1 0 0xffa7f400 - 0xffa7f4f0 (0xf1) MX[B] [2] -1 0 0xffa7f800 - 0xffa7f9f0 (0x1f1) MX[B] [3] -1 0 0x40000000 - 0x400003f0 (0x3f1) MX[B] [4] -1 0 0xffa7fc00 - 0xffa7fff0 (0x3f1) MX[B] [5] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O [6] -1 0 0xffa80000 - 0xffaffff0 (0x7fff1) MX[B](B) [7] -1 0 0xf0000000 - 0xf7fffff0 (0x7fffff1) MX[B](B) [8] -1 0 0x0000dc00 - 0x0000dc30 (0x31) IX[B] [9] -1 0 0x0000e080 - 0x0000e0b0 (0x31) IX[B] [10] -1 0 0x0000e400 - 0x0000e4f0 (0xf1) IX[B] [11] -1 0 0x0000e000 - 0x0000e010 (0x11) IX[B] [12] -1 0 0x0000ffa0 - 0x0000ffa0 (0x1) IX[B] [13] -1 0 0x0000ec00 - 0x0000ec10 (0x11) IX[B] [14] -1 0 0x0000e880 - 0x0000e890 (0x11) IX[B] [15] -1 0 0x0000e800 - 0x0000e810 (0x11) IX[B] (II) Inactive PCI resource ranges after removing overlaps: [0] -1 0 0xd8000000 - 0xdffffff0 (0x7fffff1) MX[B](B) [1] -1 0 0x0000d000 - 0x0000d070 (0x71) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xff8ff000 - 0xff8ffff0 (0xff1) MX[B] [6] -1 0 0xffa7f400 - 0xffa7f4f0 (0xf1) MX[B] [7] -1 0 0xffa7f800 - 0xffa7f9f0 (0x1f1) MX[B] [8] -1 0 0x40000000 - 0x400003f0 (0x3f1) MX[B] [9] -1 0 0xffa7fc00 - 0xffa7fff0 (0x3f1) MX[B] [10] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O [11] -1 0 0xffa80000 - 0xffaffff0 (0x7fff1) MX[B](B) [12] -1 0 0xf0000000 - 0xf7fffff0 (0x7fffff1) MX[B](B) [13] -1 0 0xd8000000 - 0xdffffff0 (0x7fffff1) MX[B](B) [14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [16] -1 0 0x0000dc00 - 0x0000dc30 (0x31) IX[B] [17] -1 0 0x0000e080 - 0x0000e0b0 (0x31) IX[B] [18] -1 0 0x0000e400 - 0x0000e4f0 (0xf1) IX[B] [19] -1 0 0x0000e000 - 0x0000e010 (0x11) IX[B] [20] -1 0 0x0000ffa0 - 0x0000ffa0 (0x1) IX[B] [21] -1 0 0x0000ec00 - 0x0000ec10 (0x11) IX[B] [22] -1 0 0x0000e880 - 0x0000e890 (0x11) IX[B] [23] -1 0 0x0000e800 - 0x0000e810 (0x11) IX[B] [24] -1 0 0x0000d000 - 0x0000d070 (0x71) IX[B](B) (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "dbe" (II) Loading /usr/X11R6/lib/modules/extensions/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.9.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font FreeType (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6/lib/modules/extensions/libGLcore.so (II) Module GLcore: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Server Extension, version 0.2 (II) Loading extension GLX (II) LoadModule: "v4l" (II) Loading /usr/X11R6/lib/modules/drivers/v4l_drv.so (II) Module v4l: vendor="X.Org Foundation" compiled for 6.9.0, module version = 0.0.1 ABI class: X.Org Video Driver, version 0.8 (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "sis" (II) Loading /usr/X11R6/lib/modules/drivers/sis_drv.so (II) Module sis: vendor="X.Org Foundation" compiled for 6.9.0, module version = 0.8.1 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.8 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.3 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.5 (II) LoadModule: "kbd" (II) Loading /usr/X11R6/lib/modules/input/kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.5 (II) v4l driver for Video4Linux (II) SIS: driver for SiS chipsets: SIS5597/5598, SIS530/620, SIS6326/AGP/DVD, SIS300/305, SIS630/730, SIS540, SIS315, SIS315H, SIS315PRO/E, SIS550, SIS650/M650/651/740, SIS330(Xabre), SIS660/[M]661[F|M]X/[M]670/[M]741[GX]/[M]760[GX]/[M]761[GX]/[M]770[GX], SIS340 (II) SIS: driver for XGI chipsets: Volari Z7 (XG20), Volari V3XT/V5/V8/Duo (XG40) (II) Primary Device is: PCI 00:02:0 (--) Chipset SIS300/305 found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xff8ff000 - 0xff8ffff0 (0xff1) MX[B] [6] -1 0 0xffa7f400 - 0xffa7f4f0 (0xf1) MX[B] [7] -1 0 0xffa7f800 - 0xffa7f9f0 (0x1f1) MX[B] [8] -1 0 0x40000000 - 0x400003f0 (0x3f1) MX[B] [9] -1 0 0xffa7fc00 - 0xffa7fff0 (0x3f1) MX[B] [10] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O [11] -1 0 0xffa80000 - 0xffaffff0 (0x7fff1) MX[B](B) [12] -1 0 0xf0000000 - 0xf7fffff0 (0x7fffff1) MX[B](B) [13] -1 0 0xd8000000 - 0xdffffff0 (0x7fffff1) MX[B](B) [14] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [15] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [16] -1 0 0x0000dc00 - 0x0000dc30 (0x31) IX[B] [17] -1 0 0x0000e080 - 0x0000e0b0 (0x31) IX[B] [18] -1 0 0x0000e400 - 0x0000e4f0 (0xf1) IX[B] [19] -1 0 0x0000e000 - 0x0000e010 (0x11) IX[B] [20] -1 0 0x0000ffa0 - 0x0000ffa0 (0x1) IX[B] [21] -1 0 0x0000ec00 - 0x0000ec10 (0x11) IX[B] [22] -1 0 0x0000e880 - 0x0000e890 (0x11) IX[B] [23] -1 0 0x0000e800 - 0x0000e810 (0x11) IX[B] [24] -1 0 0x0000d000 - 0x0000d070 (0x71) IX[B](B) (WW) ****INVALID MEM ALLOCATION**** b: 0xfffe0000 e: 0xfffffff0 correcting (II) NonSys [0] -1 0 0xff8ff000 - 0xff8ffff0 (0xff1) MX[B] [1] -1 0 0xffa7f400 - 0xffa7f4f0 (0xf1) MX[B] [2] -1 0 0xffa7f800 - 0xffa7f9f0 (0x1f1) MX[B] [3] -1 0 0x40000000 - 0x400003f0 (0x3f1) MX[B] [4] -1 0 0xffa7fc00 - 0xffa7fff0 (0x3f1) MX[B] [5] -1 0 0xf8000000 - 0xfbfffff0 (0x3fffff1) MX[B] [6] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [7] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [8] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [9] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [10] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [11] -1 0 0x0000dc00 - 0x0000dc30 (0x31) IX[B] [12] -1 0 0x0000e080 - 0x0000e0b0 (0x31) IX[B] [13] -1 0 0x0000e400 - 0x0000e4f0 (0xf1) IX[B] [14] -1 0 0x0000e000 - 0x0000e010 (0x11) IX[B] [15] -1 0 0x0000ffa0 - 0x0000ffa0 (0x1) IX[B] [16] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [17] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [18] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [19] -1 0 0x00000000 - 0x00000000 (0x1) IX[B] [20] -1 0 0x0000ec00 - 0x0000ec10 (0x11) IX[B] [21] -1 0 0x0000e880 - 0x0000e890 (0x11) IX[B] [22] -1 0 0x0000e800 - 0x0000e810 (0x11) IX[B] [23] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [24] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) window: [0] -1 0 0xff800000 - 0xff8fffff (0x100000) MX[B] (II) resSize: [0] -1 0 0x00000000 - 0xfffffff0 (0xfffffff1) MX[B] (II) window fixed: [0] -1 0 0xff800000 - 0xff8fffff (0x100000) MX[B] (II) resource ranges after probing: [0] -1 0 0xff800000 - 0xff81ffff (0x20000) MX[B](B) [1] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xff8ff000 - 0xff8ffff0 (0xff1) MX[B] [7] -1 0 0xffa7f400 - 0xffa7f4f0 (0xf1) MX[B] [8] -1 0 0xffa7f800 - 0xffa7f9f0 (0x1f1) MX[B] [9] -1 0 0x40000000 - 0x400003f0 (0x3f1) MX[B] [10] -1 0 0xffa7fc00 - 0xffa7fff0 (0x3f1) MX[B] [11] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O [12] -1 0 0xffa80000 - 0xffaffff0 (0x7fff1) MX[B](B) [13] -1 0 0xf0000000 - 0xf7fffff0 (0x7fffff1) MX[B](B) [14] -1 0 0xd8000000 - 0xdffffff0 (0x7fffff1) MX[B](B) [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x0000dc00 - 0x0000dc30 (0x31) IX[B] [21] -1 0 0x0000e080 - 0x0000e0b0 (0x31) IX[B] [22] -1 0 0x0000e400 - 0x0000e4f0 (0xf1) IX[B] [23] -1 0 0x0000e000 - 0x0000e010 (0x11) IX[B] [24] -1 0 0x0000ffa0 - 0x0000ffa0 (0x1) IX[B] [25] -1 0 0x0000ec00 - 0x0000ec10 (0x11) IX[B] [26] -1 0 0x0000e880 - 0x0000e890 (0x11) IX[B] [27] -1 0 0x0000e800 - 0x0000e810 (0x11) IX[B] [28] -1 0 0x0000d000 - 0x0000d070 (0x71) IX[B](B) [29] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [30] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) SIS(0): SiS driver (2005/09/20-1, compiled for X.org 6.9.0.0) (II) SIS(0): Copyright (C) 2001-2005 Thomas Winischhofer <thomas(a)winischhofer.net> and others (II) SIS(0): *** See http://www.winischhofer.at/linuxsisvga.shtml (II) SIS(0): *** for documentation and updates. (--) SIS(0): X.org assumes this adapter to be secondary (--) SIS(0): sisfb not found (II) SIS(0): Initializing adapter through int10 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/linux/libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 Requesting insufficient memory window!: start: 0xff800000 end: 0xff8fffff size 0x8000000 (EE) Cannot find empty range to map base to (EE) SIS(0): Cannot read V_BIOS (--) SIS(0): Relocated I/O registers at 0xD000 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.so (II) Module ramdac: vendor="X.Org Foundation" compiled for 6.9.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.8 (**) SIS(0): Depth 24, (--) framebuffer bpp 32 (==) SIS(0): RGB weight 888 (==) SIS(0): Default visual is TrueColor Requesting insufficient memory window!: start: 0xff800000 end: 0xff8fffff size 0x8000000 (EE) Cannot find empty range to map base to (WW) SIS(0): Could not find/read video BIOS (**) SIS(0): Option "EnableSiSCtrl" "on" (==) SIS(0): Using XAA acceleration architecture (==) SIS(0): Using HW cursor (==) SIS(0): Color HW cursor is disabled (==) SIS(0): TurboQueue enabled (==) SIS(0): Hotkey display switching is disabled (**) SIS(0): SiSCtrl utility interface is enabled (==) SIS(0): DRI enabled (--) SIS(0): DRAM type: SDR SDRAM (--) SIS(0): Memory clock: 83.521 MHz (--) SIS(0): (Adapter assumes MCLK being 125 Mhz) (--) SIS(0): DRAM bus width: 32 bit (--) SIS(0): Linear framebuffer at 0xD8000000 (--) SIS(0): MMIO registers at 0xFF800000 (size 64K) (--) SIS(0): VideoRAM: 1024 KB (II) SIS(0): Using 508K of framebuffer memory at offset 0K (--) SIS(0): Hardware supports two video overlays (EE) SIS(0): Detected unknown bridge type (6) (==) SIS(0): Using gamma correction (1.0, 1.0, 1.0) (II) SIS(0): Gamma correction is enabled (--) SIS(0): Memory bandwidth at 32 bpp is 83.521 MHz (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.so (II) Module ddc: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) SIS(0): CRT1 DDC supported (--) SIS(0): CRT1 DDC level: 2 (--) SIS(0): CRT1 DDC monitor info: ******************************************* (II) SIS(0): Manufacturer: VSC Model: 3319 Serial#: 16843009 (II) SIS(0): Year: 2005 Week: 13 (II) SIS(0): EDID Version: 1.3 (II) SIS(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V (II) SIS(0): Sync: Separate (II) SIS(0): Max H-Image Size [cm]: horiz.: 30 vert.: 23 (II) SIS(0): Gamma: 2.20 (II) SIS(0): DPMS capabilities: Off; RGB/Color Display (II) SIS(0): Default color space is primary color space (II) SIS(0): First detailed timing is preferred mode (II) SIS(0): redX: 0.631 redY: 0.347 greenX: 0.309 greenY: 0.583 (II) SIS(0): blueX: 0.150 blueY: 0.088 whiteX: 0.313 whiteY: 0.329 (II) SIS(0): Supported VESA Video Modes: (II) SIS(0): 720x400@70Hz (II) SIS(0): 640x480@60Hz (II) SIS(0): 640x480@67Hz (II) SIS(0): 640x480@72Hz (II) SIS(0): 640x480@75Hz (II) SIS(0): 800x600@56Hz (II) SIS(0): 800x600@60Hz (II) SIS(0): 800x600@72Hz (II) SIS(0): 800x600@75Hz (II) SIS(0): 832x624@75Hz (II) SIS(0): 1024x768@60Hz (II) SIS(0): 1024x768@70Hz (II) SIS(0): 1024x768@75Hz (II) SIS(0): Manufacturer's mask: 0 (II) SIS(0): Supported Future Video Modes: (II) SIS(0): #0: hsize: 800 vsize 600 refresh: 85 vid: 22853 (II) SIS(0): #1: hsize: 640 vsize 480 refresh: 85 vid: 22833 (II) SIS(0): Supported additional Video Mode: (II) SIS(0): clock: 65.0 MHz Image Size: 304 x 228 mm (II) SIS(0): h_active: 1024 h_sync: 1048 h_sync_end 1184 h_blank_end 1344 h_border: 0 (II) SIS(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 806 v_border: 0 (II) SIS(0): Serial No: P1H0513Q1557 (II) SIS(0): Ranges: V min: 50 V max: 85 Hz, H min: 30 H max: 62 kHz, PixClock max 80 MHz (II) SIS(0): Monitor name: VE510b (--) SIS(0): End of CRT1 DDC monitor info ************************************* (==) SIS(0): Min pixel clock is 10 MHz (--) SIS(0): Max pixel clock is 69 MHz (II) SIS(0): Replaced default mode list with built-in modes (II) SIS(0): "Unknown reason" in the following list means that the mode (II) SIS(0): is not supported on the chipset/bridge/current output device. (WW) SIS(0): config file vrefresh range 43-61Hz not within DDC vrefresh ranges. (II) SIS(0): Monitor[0]: Using hsync range of 30.00-48.00 kHz (II) SIS(0): Monitor[0]: Using vrefresh range of 43.00-61.00 Hz (II) SIS(0): Clock range: 10.00 to 69.60 MHz (II) SIS(0): Not using mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "640x400" (vrefresh out of range) (II) SIS(0): Not using default mode "720x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "720x576" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x1024" (insufficient memory for mode) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "1600x1200" (insufficient memory for mode) (II) SIS(0): Not using default mode "320x200" (vrefresh out of range) (II) SIS(0): Not using default mode "1920x1440" (insufficient memory for mode) (II) SIS(0): Not using default mode "2048x1536" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x960" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x960" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x600" (insufficient memory for mode) (II) SIS(0): Not using default mode "1152x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "800x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x576" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x576" (insufficient memory for mode) (II) SIS(0): Not using default mode "1024x576" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x720" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x720" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x720" (insufficient memory for mode) (II) SIS(0): Not using default mode "1152x864" (insufficient memory for mode) (II) SIS(0): Not using default mode "1152x864" (insufficient memory for mode) (II) SIS(0): Not using default mode "1152x864" (insufficient memory for mode) (II) SIS(0): Not using default mode "848x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "848x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "856x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "856x480" (insufficient memory for mode) (II) SIS(0): Not using default mode "1360x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "1280x768" (insufficient memory for mode) (II) SIS(0): Not using default mode "768x576" (insufficient memory for mode) (II) SIS(0): Not using default mode "1360x1024" (insufficient memory for mode) (II) SIS(0): Not using mode "1024x768" (no mode of this name) (EE) SIS(0): ************************************************** (EE) SIS(0): ERROR: (EE) SIS(0): Virtual screen too big for memory; 768K needed, 508K available (EE) SIS(0): END OF MESSAGE (EE) SIS(0): ************************************************** (II) UnloadModule: "sis" (II) UnloadModule: "ddc" (II) Unloading /usr/X11R6/lib/modules/libddc.so (II) UnloadModule: "ramdac" (II) Unloading /usr/X11R6/lib/modules/libramdac.so (II) UnloadModule: "int10" (II) Unloading /usr/X11R6/lib/modules/linux/libint10.so (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found Please consult the The X.Org Foundation support at http://wiki.X.Org for help. Please also check the log file at "/var/log/Xorg.1.0.log" for additional information. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

2 1

[SLE] can I run two X server on one single host?
by Zhang Weiwu 02 Jun '06

02 Jun '06

Just curious, is it possible to run two X server on one single host with two seperate video card? Perhaps this question is not particular to SuSE but to any linux as well. I am thinking if I plug another set of USB keyboard and mouse, I can let my nephew play computer games (mostly emulated XMAME games) on my old CRT screen and leaving me using the main keyboard/screen to work on my OOO documents without having to getting him another computer. This computer happen to have two video card, the onboard card is currently not used because in order to play game we bought another better 3D card. -- Zhang Weiwu Real Softservice International business: http://www.realss.com International sales: 0086 10 84606011 Inland business: http://www.realss.cn Inland sales call: 0086 592 2099987 Sent from Pine: http://www.washington.edu/pine/ -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

2 1

[SLE] Hauppauge Win-TV PVR 150 on Open SUSE 10.1 (AMD 64)
by Schultz 2005 02 Jun '06

02 Jun '06

Can someone help me with installation? I can not find ivtv packages on installation DVD. Which driver version and firmware should I install on my machine? Acording to documentation success is version dependent. Links? Install guide? Thank you! Greetings,

2 2

info for suse slick
by Ian House 02 Jun '06

02 Jun '06

Could someone please tell me if this is the right list for Suse Slick. -- Cheers, Ian...

10 20

Re: [SLE] Sending Email
by John 02 Jun '06

02 Jun '06

Joe Zitnik wrote: > If you're talking strictly mail terms, correct, to your ISP, it's just > packets at that point. Remember, however, that all traffic is logged > somewhere. > > >>> On 6/2/2006 at 6:02 AM, John <John(a)DMJ-Consultancy.co.uk> wrote: > Can someone please clarify the following: > > If I use my ISP to send email, they log it and keep the record for years. > > If I elect to use my server with its DNS capability to send the mail > 'direct', even though I still need the ISP to give me an internet > connection, they have nothing to log. > > Is my understanding correct? > > Many thanks > > John > > > -- > Check the headers for your unsubscription address > For additional commands send e-mail to suse-linux-e-help(a)suse.com > Also check the archives at http://lists.suse.com <http://lists.suse.com/> > Please read the FAQs: suse-linux-e-faq(a)suse.com > > Yup, I guess Big Brother has much to answer for! J -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

1 0

no xpm since KDE 3.5.1
by Daniel Bauer 02 Jun '06

02 Jun '06

Hello everybody I just updated KDE to 3.5.1 with Yast and since then xpm images are not displayed anymore, konqueror cannot show them anymore and so some icons on my dektop, the minimize, close etc. buttons in the windows are not visable anymore and in Yast the icons for "installed", "update" etc. don't show... What have I broken / missed? can you help me, please? Daniel -- Daniel Bauer photographer Basel Switzerland professional photography: http://www.daniel-bauer.com special interest site: http://www.bauer-nudes.com

4 17

[SLE] missing "status box" in yast
by António Rodrigues Tomé 02 Jun '06

02 Jun '06

Hi, in spite of the problems on the yast at suse10.1 I'm being able to work with it (spending a lot of time, now and then). Nevertheless, after update the KDE packages with the new build service KDE:KDE3 KDE:Backports yast didn't loose neither improve performance (it was not expected too, obviously) but the little box at the left of packages names with a thick if the package was installed or selected to install, a lock for protected packages, etc., has disappeared!!! I still can see the install package status by moving the mouse pointer to the box previous location and get tooltips (Protect -- do not modify, Do not Install, Keep, etc). This behavior makes yast a little/lot more unfriendly for packages management, but obviously yast is much more than that and I do not considered stop using it ! I'm posting this mail to ask if someone has experienced the same or if it could be some specific thing of my system (it happens in two computers) best regards, -- António Rodrigues Tomé http://www.dfisica.ubi.pt/~artome -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq(a)suse.com

3 4