openSUSErs,
I'm confused about splash screens during boot. I come from older openSUSE
and not really accustomed to kms (if that has anything to do with it at
all.
My aim is to have a very short timeout on grub2 and then have a customized
boot splash screen visible up to auto-login of some user. I'm using a
"Minimal X Window" and a "standrd KDE" openSUSE 11.3 installation with
standard 2.6.34-12-desktop kernel.
Any advice on how to achieve that goal very much appreciated.
Below find some additional info.
What I see upon boot is
BIOS
GRUB
kernel/init text messages
[flickering]
kernel/init text messages (the same as previsously)
[flickering]
some text message about "fast boot" shows short
plenty of console text messages for the booting
xdm or KDE login
My hardware is
hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer
[Created at bios.459]
Unique ID: rdCR.il6towt04X5
Hardware Class: framebuffer
Model: "Intel(r) 82945GM Chipset Family Graphics Controller"
Vendor: "Intel Corporation"
Device: "Intel(r) 82945GM Chipset Family Graphics Controller"
SubVendor: "Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS"
SubDevice:
Revision: "Hardware Version 0.0"
Memory Size: 7 MB + 704 kB
Memory Range: 0xd0000000-0xd07affff (rw)
Mode 0x0305: 1024x768 (+1024), 8 bits
Mode 0x0317: 1024x768 (+2048), 16 bits
Mode 0x0318: 1024x768 (+4096), 24 bits
Mode 0x0312: 640x480 (+2560), 24 bits
Mode 0x0314: 800x600 (+1600), 16 bits
Mode 0x0315: 800x600 (+3200), 24 bits
Mode 0x0301: 640x480 (+640), 8 bits
Mode 0x0303: 800x600 (+832), 8 bits
Mode 0x0311: 640x480 (+1280), 16 bits
Config Status: cfg=new, avail=yes, need=no, active=unknown
hwinfo --gfxcard
10: PCI 02.0: 0300 VGA compatible controller (VGA)
[Created at pci.318]
Unique ID: _Znp.u0hotzOT3DB
SysFS ID: /devices/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: graphics card
Model: "Intel 945 GM"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x27a2 "945 GM"
SubVendor: pci 0x8086 "Intel Corporation"
SubDevice: pci 0x27a2
Revision: 0x03
Driver: "i915"
Driver Modules: "drm"
Memory Range: 0xfdf00000-0xfdf7ffff (rw,non-prefetchable)
I/O Ports: 0xff00-0xff07 (rw)
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
Memory Range: 0xfdf80000-0xfdfbffff (rw,non-prefetchable)
IRQ: 16 (50 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00008086d000027A2sv00008086sd000027A2bc03sc00i00"
Driver Info #0:
XFree86 v4 Server Module: intel
Driver Info #1:
XFree86 v4 Server Module: intel
3D Support: yes
Extensions: dri
Config Status: cfg=new, avail=yes, need=no, active=unknown
I do find openSUSE theme files in /etc/bootsplash/themes and
/etc/sysconfig/bootsplash says
SPLASH="yes"
THEME="openSUSE"
I've tried the following in menu.lst of grub with and without
",theme:openSUSE"
title mypc
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 splash=silent,theme:openSUSE quiet showopts
initrd /boot/initrd
and also vga=791 as kernel option. Without success.
It appear to me from
http://sinujohn.wordpress.com/http://www.novellshareware.com/news/netbooks-with-small-screens-create-a-sp…
that there should indeed be a splash screen ... when running a live
openSUSE 11.3 CD I think indeed there is a splash after kernel load and
before the KDE login appears. But then again it seems that the live CD is
kiwi based.
Thanks Mads Jeppe
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I was wondering if Opensuse will be implementing ksplice anytime soon
now that Fedora has?
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I'm trying to setup ldap authentication to eDirectory. I'm actually
doing it on SLES11, but hoping someone here can give me a hand. I'm
getting an error when I try to ssh as a user that only exists in ldap,
not locally. I've found a lot of references to this error, but have not
found a solution that works for my situation.
First, the error I see in the log is:
pam_ldap: error trying to bind as user "cn=myid,ou=my ou,o=root" (Invalid credentials)
I can successfully bind to ldap using ldapsearch and ldapbrowser from
sles11, so I know my credentials are correct.
Connection to ldap is not encrypted so I've captured all three logins
using wireshark. The authentication value for the simple bind matches
for ldapsearch and ldapbrowser, but is different coming from pam_ldap.
So it seems like pam_ldap is sending the password different, maybe it's
encrypting or something, don't know.
In /etc/ldap.conf I've set:
host 192.168.100.21
base o=root
bind_policy soft
pam_lookup_policy yes
pam_password nds
nss_initgroups_ignoreusers root,ldap
nss_schema rfc2307bis
I also tried pam_password clear.
Anyone have any suggestions? Maybe I'm just overlooking something very basic.
The complete output from the log is:
Aug 31 13:48:32 sles11 sshd[19756]: Invalid user myid from 192.168.100.24
Aug 31 13:48:39 sles11 sshd[19761]: pam_ldap: error trying to bind as user "cn=myid,ou=my ou,o=root" (Invalid credentials)
Aug 31 13:48:39 sles11 sshd[19761]: pam_unix(sshd:auth): check pass; user unknown
Aug 31 13:48:39 sles11 sshd[19761]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.100.24
Aug 31 13:48:41 sles11 sshd[19756]: error: PAM: User not known to the underlying authentication module for illegal user myid from 192.168.100.24
Aug 31 13:48:41 sles11 sshd[19756]: Failed keyboard-interactive/pam for invalid user myid from 192.168.100.24 port 38256 ssh2
Aug 31 13:50:32 sles11 sshd[19762]: error: ssh_msg_send: write
Aug 31 13:50:32 sles11 sshd[19762]: pam_unix(sshd:auth): conversation failed
Aug 31 13:50:32 sles11 sshd[19762]: pam_unix(sshd:auth): auth could not identify password for [myid]
Aug 31 13:50:32 sles11 sshd[19762]: error: ssh_msg_send: write
Thanks,
James
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
Guys,
Though I often knock kde4 and all isn't perfect, 4.5.1-1 is looking much
better. We are starting to see some of the 'smartness' and 'efficiency' that
made kde3 such a great desktop creep into kde4. Case-in-point, simple things
like changing the background in kde4 sucked largely because you were limited to
a single column of thumbnails to choose from that was slow as hell to scroll
through (especially if you have 100+ wallpapers in the search path.
After upgrade to 4.5.1-1, I was surprised to see a clean 3-column selection now
that triples the amount of data you have at a glance and greatly speeds
transitioning the list of wallpapers. (it could have been there a version ago
and I'm just seeing it now)
I'm glad to see some of the highly visible sore thumbs of k4 are being
addressed. Why it has taken 2+ years from the official June, 2008 release date
to get here still has never been adequately explained, but for those who know
open-source, you know why.
So the purpose of the email is to tell Will, Sven and the rest of the tireless
k4 devs on this list - great job, Your work and effort is highly visible and
well appreciated.
(Will, now if I can just get you in an advisory role on the Pearson project to
preserve k3 as a 'choice' for the future, we will really have made progress on
two fronts. I'll follow up privately later)
Second, just as this example shows, it is the lack of the simple efficiencies
in k4 that have caused serious acceptance problems for k4. Slow scrolling,
inefficient lists, whack-a-mole focus handling, file managers that can't
remember what they looked like the last time they were closed or remember what
file or directory they were just in/on when pressing the (back) button while in
preview in tree mode are apparently the things that were/are low-priority fixes
that are being addressed last. This approach is completely backwards for a
successful major version jump and the historical trouble k4 has had with
acceptance bears that out.
Things like this are often the first things people see in k4 and, it is true,
you only get one chance to make a good first impression (hopefully that is a
lesson learned for k5) Make sure the first things people see and use most work
out of the gate -- not 2 years later.
But regardless of the history, the successes and missteps, kde4 is looking very
good in 4.5.1-1. Great job kde4 devs!
P.S. Now, I'll go try the back button in nested tree mode in konqueror while
previewing a wallpaper and report back :p
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I've been looking into some computer forensics and learning some new
things, and until now I haven't heard of an openSUSE based distro:
http://netsecl.com/
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
I run openSuSE 11.3.
I have installed kedtoys4, and then I recognized, that also a new NVIDIA
driver was installed.
After the update I recognized, that my desktop looks like this:
http://www.urbakken.dk/desktop.jpg
This means, that all what was located in the panel before the update,
now is spread all around the desktop.
What can I do, to get rid of that ?.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
On Tue, 2010-08-31 at 18:11 +0200, Martin Schlander wrote:
> Tirsdag den 31. august 2010 15:45:32 skrev John G Walker:
> > I've been running KDE4 with Suse 11.2 for some months now, with
> > no problems. Yesterday, the background to my screen suddenly went
> > black. Open windows were unaffected, but I could see my theme, the task
> > manager, etc. I couldn't open any programs other than the ones already
> > open (and ones that they launch).
>
> > Anyone got any ideas? This is making things extremely difficult for me,
> > to say the least. Rapid responses would be highly welcome!
>
> Clearly plasma-desktop isn't running. Maybe it crashed. You can prolly try to
> restart 'plasma-desktop' by pressing Alt+F2 - which should also let you start
> other stuff, even though plasma-desktop is down.
>
> Normally the recommendation would be to 'rm .kde4/share/config/plasma*' to
> "reset" plasma.
I will try the Alt-F2 and then deleting the files and get back to the
list. The system is in another town and the guy pressing the buttons is
not in yet.
> But since your problem is apparently systemwide, it'd be interesting to know
> if you're using the official 11.2 KDE (4.3.5), or some other unsupported
> version from the OBS.
It is the KDE on the 11.2 install media. As I wrote, there have been no
updates. Not even the one that the install offers to do (I will verify
this last point). No repos other than what the install adds are
defined.
System-wide yes. Oddly, root no. You would think there was a clue here.
But I never could see what it was.
What confuses me is that we are doing out-of-the-box installs on new
systems running on every day nvidia cards with common displays. I just
cannot believe that we are the only ones seeing this. I could see if we
were doing something odd. But these are just simple installs. It has
happened at least 50% of the time. Can't see any common link in
hardware. The systems are not exactly the same. But the problem is.
I can attach a few small screen dumps if no one objects.
--
Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org
On Tue, 2010-08-31 at 20:49 +0100, John G Walker wrote:
>
> On Tue, 31 Aug 2010 19:44:48 +0200 Martin Schlander
> <martin.schlander(a)gmail.com> wrote:
>
> > The search box also lets you launch apps and run commands.. such as
> > 'konsole'.
>
>
> Thanks for this piece of information, it was useful. I didn't know that
> before.
>
> In fact, the problem turned out to have been caused by inadvertently
> writing to the root filesystem and filling it up. Once the files were
> identified and deleted, everything worked,
So your black screen went away when you sorted out disk space? Humm. I
should have GBs free everywhere. When possible, that will be checked.
--
Roger Oberholtzer
OPQ Systems / Ramböll RST
Ramböll Sverige AB
Krukmakargatan 21
P.O. Box 17009
SE-104 62 Stockholm, Sweden
Office: Int +46 10-615 60 20
Mobile: Int +46 70-815 1696
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse+help(a)opensuse.org