Some additional info. On the kde desktop icon flashing issue. I moved some files into folders on the desktop, and that seemed to fix the flashing. Some of these files couldn't find there associated graphics (i.e a .pdf file may or may not look like a pdf icon). So this may well be a non-issue, or probably NOT a Mandrake issue.
HOWEVER: After rebooting the laptop without the pcmcia network card inserted, and then inserting it watching on a root tty.....well as I suspected this mimmicks the pcmcia network card issues that plagued the 8.x releases and I think got fixed shortly before 9.1 was released. The scripts are clearly hanging. As I recall there was much discussion of this in the past. SO this must just be a case of deja-vu !! Thanks for the attention. Bob Finch p.s. .... The fix for me was script in rc.local to take care of this. Prolly going to have to that again. No big deal just wanted to get this "on the record". On Friday 18 July 2003 11:17 am, w9ya wrote: > Hey Gang; > > Earlier this week, after a urpmi.update -a && urmpi --auto-select --auto, > the eth0 interface seemed to be set up just fine after a reboot. *However* > logging into kde via kdm (not mdkkdm) oddly caused the routing and ifconfig > for eth0 to "disappear". The modules for the pcmcia card were still loaded > so a simple dhcpcd from a root prompt fixed it all up. This was only for > the first kdm login after a reboot as subsequent logins via kdm were fine. > > *NOW* (after just now running the urmpi script above) only the lo interface > is being setup after a reboot. As before the pcmcia card's modules are > being loaded during the reboot and running dhcpcd from a root prompt after > the reboot completes works fine. Now kdm logins no longer appear to be > causing any issues in this area. > > Additionally the kde desktop is having problems since the earlier urpmi > updates. Desktop icons are flashing after kdm completes placing said icons > after a (kdm) login. The operational fix is to select icon alignment, > however this has to be done each time a user logs in. > > Obviously this may not be a Mandrake specific problem in either case (kde > or dhcpcd). But in past experience with at least the dhcpcd issue (yes this > is NOT the first time) it has been a Mandrake scripting error. > > Thanks for the attention. > > Bob Finch
