Re: [gentoo-user] [OT] test, if module was loaded with module option?

2008-12-31 Thread Christian Franke
On 12/29/2008 02:32 PM, Marc Blumentritt wrote:
 is there a general way to test, if a kernel module was loaded with a
 module option and which module options were used?

There is at least /sys/module/modulname/parameters/parametername
If there is nothing else, one could at least compare each parameter to
its default value or something like that. Attention, not everything in
/sys/module _is_ a module, seems more like everything that is or _could_
be a module is there.

If the moduleoption was set when booting, one could of course use
/proc/cmdline, but I think that might be not exactly what you want.

-cf



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-user] [OT] test, if module was loaded with module option?

2008-12-31 Thread Julien Porschen
2008/12/31 Christian Franke cfchr...@yahoo.de:
 On 12/29/2008 02:32 PM, Marc Blumentritt wrote:
 is there a general way to test, if a kernel module was loaded with a
 module option and which module options were used?

 There is at least /sys/module/modulname/parameters/parametername
 If there is nothing else, one could at least compare each parameter to
 its default value or something like that. Attention, not everything in
 /sys/module _is_ a module, seems more like everything that is or _could_
 be a module is there.

 If the moduleoption was set when booting, one could of course use
 /proc/cmdline, but I think that might be not exactly what you want.

 -cf





-- 
Julien Porschen



Re: [gentoo-user] Suspend to ram: correct behavior?

2008-12-31 Thread damian
Hi Daniel,

Thanks for your response. I'll try to make some time to test your tips.

 You can also try booting a Fedora/Ubuntu/SuSE LiveCD, and see if with
 their kernel the same happens (given that suspend works on their
 LiveCD). If they manage to switch off the power to your USB-ports, that
 can give us a hint.
That I can try, I still keep the Ubuntu (shame on me! :P) which I used
to install Gentoo.

Best regards,
Damian.



Re: [gentoo-user] Suspend to ram: correct behavior?

2008-12-31 Thread damian
 LiveCD). If they manage to switch off the power to your USB-ports, that
 can give us a hint.
 That I can try, I still keep the Ubuntu (shame on me! :P) which I used
 to install Gentoo.
Nope. I've booted with Ubuntu (damn it boots slow! :P) and after
suspending the usb port was still yielding power. I guess it's better
for me to find out if there actually is a way to prevent this.


 Best regards,
 Damian.




Re: [gentoo-user] emerge svgalib (1.9.25) fails with gentoo-sources-2.6.28

2008-12-31 Thread Thanasis
OK, this seems to be an already filed bug:

http://bugs.gentoo.org/show_bug.cgi?id=252614



[gentoo-user] [OT] High-pitched sound from inside the PC when opening menus

2008-12-31 Thread Nikos Chantziaras
This is a question that is off topic of course, but I'm not sure *where* 
it would be on-topic.  Considering that Gentoo users are also often 
so-called enthusiasts, I'll drop the question here ;)


In KDE (3), when enabling the fade effect for menus, clicking on a 
menu results in a faint, high-pitched tone coming from somewhere inside 
the PC case.  The tone lasts for the duration of the fade effect (should 
about 0.2 seconds).  This is happening on more than one machines.  You 
have to listen carefully to make out the sound, but it's there.


So the question is simple: where does the sound come from and why?




Re: [gentoo-user] [OT] High-pitched sound from inside the PC when opening menus

2008-12-31 Thread Matt Harrison

Nikos Chantziaras wrote:
This is a question that is off topic of course, but I'm not sure *where* 
it would be on-topic.  Considering that Gentoo users are also often 
so-called enthusiasts, I'll drop the question here ;)


In KDE (3), when enabling the fade effect for menus, clicking on a 
menu results in a faint, high-pitched tone coming from somewhere inside 
the PC case.  The tone lasts for the duration of the fade effect (should 
about 0.2 seconds).  This is happening on more than one machines.  You 
have to listen carefully to make out the sound, but it's there.


So the question is simple: where does the sound come from and why?




I get something  very similar when using any 3d application. I was 
thinking it is interference from the graphics device seeping into the 
sound card.


Do you have sound card and speakers connected, if so, does it come out 
of the speakers or is it internal to the case?


Not being an electronics engineer, i don't want to start taking my 
hardware to pieces and re-shield it all. It seems like I'm going to have 
to replace my old SB Audigy that's served me so well for years.


I know it's not a definitive answer but it might point to the right 
direction.


BTW, this happens in both gentoo and windows xp for me.

Matt



Re: [gentoo-user] Open Source Family Tree software?

2008-12-31 Thread David Relson
On Sat, 29 Nov 2008 16:05:48 -0800
Mark Knecht wrote:

 On Sat, Nov 29, 2008 at 3:45 PM, Daniel Pielmeier
 daniel.pielme...@googlemail.com wrote:
  Mark Knecht schrieb am 30.11.2008 00:29:
 
  It seems that
  gramps is doing something sort of like this but one wonders just
  how large their database is. Also, I'd hate for my wife to do a
  lot of work entering a few hundred people only to find she cannot
  use the gramps data with anything but gramps.
 
  Gramps has support for the GEDCOM format, which I remember was also
  used by another program I tried some years ago. GEDCOM is according
  to the gramps homepage an industry standard, so it should be
  possible to exchange your data with all other programs supporting
  this standard.
 
  http://gramps-project.org/wiki/index.php?title=Features
 
 
 
 Cool. thanks.
 
 I suppose she can try entering just a few names and then see if she
 can talk to FTM.
 
 I'm not sure any of this is important to her. Just trying to get a
 bit ahead.
 
 Thanks,
 Mark

As stated by others, gramps is in portage.  It's a python app and
works well with adequate hardware.  (On a 500mhz geode with 256mb
it's rather slow.  On an AMD-64 with 4gb it's pleasantly fast).

The newest (experimental) version is 3.0.4 which is working well for me.
The previous version, 3.0.3, had some expectations about BerkeleyDB
which could cause an unhandled exception.

I'm not sure about exporting to FTM, but I was able to import
without problems from FTM (which I used several years ago).  I've also
been able to transfer between Gramps and PAF using the GEDCOM format.
(Note:  PAF requires WINE).

HTH,

David



[gentoo-user] Re: [OT] High-pitched sound from inside the PC when opening menus

2008-12-31 Thread Nikos Chantziaras

Matt Harrison wrote:

Nikos Chantziaras wrote:
This is a question that is off topic of course, but I'm not sure 
*where* it would be on-topic.  Considering that Gentoo users are also 
often so-called enthusiasts, I'll drop the question here ;)


In KDE (3), when enabling the fade effect for menus, clicking on a 
menu results in a faint, high-pitched tone coming from somewhere 
inside the PC case.  The tone lasts for the duration of the fade 
effect (should about 0.2 seconds).  This is happening on more than one 
machines.  You have to listen carefully to make out the sound, but 
it's there.


So the question is simple: where does the sound come from and why?


I get something  very similar when using any 3d application. I was 
thinking it is interference from the graphics device seeping into the 
sound card.


I also get this in some 3D apps, especially benchmarks.


Do you have sound card and speakers connected, if so, does it come out 
of the speakers or is it internal to the case?


It's coming from the case, not the speakers.



BTW, this happens in both gentoo and windows xp for me.


Same here.  The sound is loudest when running the Mother Nature test 
of 3DMark 03.  Happening with every card I ever tried (an old Radeon 
9800, an X1950XT and my current HD4870).  Could be the graphics cards 
then.  But it would be interesting to know why this is happening.





Re: [gentoo-user] Suspend to ram: correct behavior?

2008-12-31 Thread Robert Bridge
On Wed, 31 Dec 2008 11:42:54 +0100
damian damian.o...@gmail.com wrote:

  LiveCD). If they manage to switch off the power to your USB-ports,
  that can give us a hint.
  That I can try, I still keep the Ubuntu (shame on me! :P) which I
  used to install Gentoo.
 Nope. I've booted with Ubuntu (damn it boots slow! :P) and after
 suspending the usb port was still yielding power. I guess it's better
 for me to find out if there actually is a way to prevent this.
 
 
  Best regards,
  Damian.

I think USB ports normally give power even without the appropriate
driver loaded. I know I have seen old computers used to charge USB
devices they couldn't communicate with...


signature.asc
Description: PGP signature


[gentoo-user] KVM recognition changes in recent kernels

2008-12-31 Thread Harry Putnam
kernel 2.6.27-r7 and 2.6.28 and several other earlier kenels

Summary:
Anyone here know more details about the kernel settings and KVM
switching? 

Details: (and inlined dmesg)
I'm not exactly sure when or what kernel was in use when this change
in behavior started but its been at least 2 mnths ago.

Phenomena:
  I've used kvm switching for several yrs... Usually trouble free.
  I have 4 machines running thru a KVM switch including my main
  desktop running 2008 gentoo.
  The others are winXP
  I don't have the kvm model to hand but it is an IOGEAR 4 port USB

I've noticed a change in recent mnths where until bootup is complete
the kvm switch is not recogized.  I see that thru several kernel
upgrades and various kernel builds.

I have to have a second keyboard connected direct if I want to mess
around with grub or something... while testing kernels.  But once
bootup reaches the login prompt the KVM is in the loop, and I can use
the kvm connected keyboard.

In kernels somewhere back down the road the KVM was in the loop right
from the start.

Diagnosing is made harder by the fact that I've changed KVM  switches
twice in that time.

However, with the current KVM there was a point where it was
recognized immediately and available even at the grub screens.
Unfortunately I didn't document any of this at the time.

It appears the kernel has to have some of the `hid' settings enabled
for the KVM to work at all so I'm wondering if some special setting is
what is responsible for the change.

I've found in recent experiments with 2.6.28 that at least these two
settings must be set `y' or `m' in order for the KVM to work at all

   CONFIG_HIDRAW=y   # near line 1269 (2.6.27-r7 .config)
   CONFIG_USB_HID=m  # near line 1274 (2.6.27-r7 .config)

It gets pretty complicated beyond those two trying to see if anything
else will allow the KVM to be seen immediately.

==

I'm probably just not sharp eyed enough but I don't see anything
relating to KVM in particular.

The kvm works in this case but only after bootup completes.

dmesg following recent boot of 2.6.28

BIOS EBDA/lowmem at: 0009fc00/0009fc00
Linux version 2.6.28-gentoo-hp (r...@reader) (gcc version 4.3.2 (Gentoo 
4.3.2-r2 p1.5, pie-10.1.4) ) #5 Tue Dec 30 23:32:16 CST 2008
KERNEL supported cpus:
  Intel GenuineIntel
  AMD AuthenticAMD
  NSC Geode by NSC
  Cyrix CyrixInstead
  Centaur CentaurHauls
  Transmeta GenuineTMx86
  Transmeta TransmetaCPU
  UMC UMC UMC UMC
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0009fc00 - 000a (reserved)
 BIOS-e820: 000f - 0010 (reserved)
 BIOS-e820: 0010 - 7fff (usable)
 BIOS-e820: 7fff - 7fff8000 (ACPI data)
 BIOS-e820: 7fff8000 - 8000 (ACPI NVS)
 BIOS-e820: fec0 - fec01000 (reserved)
 BIOS-e820: fee0 - fee01000 (reserved)
 BIOS-e820: fff0 - 0001 (reserved)
DMI 2.3 present.
AMI BIOS detected: BIOS may corrupt low RAM, working it around.
last_pfn = 0x7fff0 max_arch_pfn = 0x10
kernel direct mapping tables up to 377fe000 @ 1-16000
ACPI: RSDP 000FA3A0, 0014 (r0 AMI   )
ACPI: RSDT 7FFF, 002C (r1 AMIINT INTEL865   10 MSFT   97)
ACPI: FACP 7FFF0030, 0081 (r1 AMIINT INTEL865   11 MSFT   97)
ACPI: DSDT 7FFF0120, 37D5 (r1  INTELI865G 1000 MSFT  10D)
ACPI: FACS 7FFF8000, 0040
ACPI: APIC 7FFF00C0, 005C (r1 AMIINT INTEL8659 MSFT   97)
1159MB HIGHMEM available.
887MB LOWMEM available.
  mapped low ram: 0 - 377fe000
  low ram:  - 377fe000
  bootmap 00012000 - 00018f00
(6 early reservations) == bootmem [00 - 00377fe000]
  #0 [00 - 001000]   BIOS data page == [00 - 001000]
  #1 [10 - 4ce398]TEXT DATA BSS == [10 - 4ce398]
  #2 [4cf000 - 4d2000]INIT_PG_TABLE == [4cf000 - 4d2000]
  #3 [09fc00 - 10]BIOS reserved == [09fc00 - 10]
  #4 [01 - 012000]  PGTABLE == [01 - 012000]
  #5 [012000 - 019000]  BOOTMAP == [012000 - 019000]
Zone PFN ranges:
  DMA  0x0010 - 0x1000
  Normal   0x1000 - 0x000377fe
  HighMem  0x000377fe - 0x0007fff0
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x0010 - 0x009f
0: 0x0100 - 0x0007fff0
On node 0 totalpages: 524159
free_area_init_node: node 0, pgdat c045b544, node_mem_map c1000200
  DMA zone: 32 pages used for memmap
  DMA zone: 0 pages reserved
  DMA zone: 3951 pages, LIFO batch:0
  Normal zone: 1744 pages used for memmap
  Normal zone: 221486 pages, LIFO batch:31
  HighMem zone: 2320 pages used for memmap
  HighMem zone: 294626 pages, LIFO batch:31
  Movable zone: 0 pages used for memmap
ACPI: PM-Timer IO Port: 0x808
Allocating PCI resources starting at 8800 (gap: 

Re: [gentoo-user] Re: [OT] High-pitched sound from inside the PC when opening menus

2008-12-31 Thread Etaoin Shrdlu
On Wednesday 31 December 2008, 15:56, Nikos Chantziaras wrote:

 It's coming from the case, not the speakers.

  BTW, this happens in both gentoo and windows xp for me.

 Same here.  The sound is loudest when running the Mother Nature test
 of 3DMark 03.  Happening with every card I ever tried (an old Radeon
 9800, an X1950XT and my current HD4870).  Could be the graphics cards
 then.  But it would be interesting to know why this is happening.

Google for coil whine or coil noise and see if it applies to your 
case. I had one Abit motherboard replaced because the noise it did was 
really unbearable, although hearing it change pitch depending on what 
you were doing was kind of cool.



Re: [gentoo-user] Re: [OT] High-pitched sound from inside the PC when opening menus

2008-12-31 Thread Matt Harrison

Etaoin Shrdlu wrote:

On Wednesday 31 December 2008, 15:56, Nikos Chantziaras wrote:


It's coming from the case, not the speakers.


BTW, this happens in both gentoo and windows xp for me.

Same here.  The sound is loudest when running the Mother Nature test
of 3DMark 03.  Happening with every card I ever tried (an old Radeon
9800, an X1950XT and my current HD4870).  Could be the graphics cards
then.  But it would be interesting to know why this is happening.


Google for coil whine or coil noise and see if it applies to your 
case. I had one Abit motherboard replaced because the noise it did was 
really unbearable, although hearing it change pitch depending on what 
you were doing was kind of cool.




I will investigate now I know what I can search for, and yes the pitch 
change was interesting. I once played a game for an hour before I notice 
d the sound was interference and not dark, moody music :D


Thanks

Matt



Re: [gentoo-user] [OT] High-pitched sound from inside the PC when opening menus

2008-12-31 Thread Paul Hartman
On Wed, Dec 31, 2008 at 8:02 AM, Nikos Chantziaras rea...@arcor.de wrote:
 This is a question that is off topic of course, but I'm not sure *where* it
 would be on-topic.  Considering that Gentoo users are also often so-called
 enthusiasts, I'll drop the question here ;)

 In KDE (3), when enabling the fade effect for menus, clicking on a menu
 results in a faint, high-pitched tone coming from somewhere inside the PC
 case.  The tone lasts for the duration of the fade effect (should about 0.2
 seconds).  This is happening on more than one machines.  You have to listen
 carefully to make out the sound, but it's there.

 So the question is simple: where does the sound come from and why?

I have a Core 2 Duo E6600, with Abit In9-32X Max motherboard and I get
the loud hissing noise. It seems to basically happen during CPU load
that is not balanced between the two cores. In other words, if both
cores are idle or both cores are busy, there is no noise, but if only
one core is busy it makes a loud hissing sound.

I've heard a similar noise coming from the video card (I've assumed)
on an IBM laptop. Whenever there is heavy video I/O it makes a hissing
sound.

I can't remember the exact reasoning, but I do recall being told it's
normal and that it varies from one system to another, even with the
same hardware. I think it's related to capacitors or voltage regulator
or something like that. (I am not an electrical engineer)

When trying KDE4 with all the desktop effects, it was really annoying,
everything I did would cause the hissing noise, presumably because
it's using more CPU load to do basic things.

So, in other words, it's normal. :)

Paul



Re: [gentoo-user] KVM recognition changes in recent kernels

2008-12-31 Thread Neil Walker

Harry Putnam wrote:

I have to have a second keyboard connected direct if I want to mess
around with grub or something... while testing kernels.


The kernel isn't even loaded at that point so how can you blame it? It 
looks like a hardware/BIOS problem to me from what you have said. FWIW, 
I am currently running Kernel 2.6.28 on 8 machines through a Starview 8 
port KVM without any problems.


Be lucky,

Neil





[gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread Dale
Hi,

I recently stole me a Motorola Razr phone and it didn't come with the
manual.  I downloaded it off the Motorola website and was reading, or
attempting to read, it when Kpdf crashed.  It does this when I scroll
down to about page 30 or so.  It's a pretty large document since it has
both English and Spanish. 

I did re-emerge Kpdf, both versions of qt that I have on here and even
glibc.  Those are the things mentioned in the crash report.  It still
crashes.  Could this be something besides Kpdf?  Anybody else see
something in the crash log?

Here is the crash log:

(no debugging symbols found)
Using host libthread_db library /lib/libthread_db.so.1.
(no debugging symbols found)

SNIP 

[Thread debugging using libthread_db enabled]
[New Thread 0xb697e6d0 (LWP 25418)]
[New Thread 0xb5c3db90 (LWP 25485)]
(no debugging symbols found)
(no debugging symbols found)

 SNIP 

0xb716a568 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#0  0xb716a568 in QObject::activate_signal () from
/usr/qt/3/lib/libqt-mt.so.3
#1  0xb74955bc in QApplication::guiThreadAwake ()
   from /usr/qt/3/lib/libqt-mt.so.3
#2  0xb70bac22 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#3  0xb71210f0 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#4  0xb7120f76 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#5  0xb710a4af in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#6  0x0805005c in ?? ()
#7  0xbfc8ff50 in ?? ()
#8  0xbfc90050 in ?? ()
#9  0x in ?? ()

I snipped out the repeating stuff.  Thoughts?

Thanks.

Dale

:-)  :-) 

P.S.  I bought the phone really cheap.  I just feel like I stole it. 
LOL 



[gentoo-user] Re: Kpdf crashes with large documents.

2008-12-31 Thread James
Dale rdalek1967 at gmail.com writes:


 attempting to read, it when Kpdf crashed. 


tried acroread?


works great for me.

ymmv,


James







[gentoo-user] Re: Thanks and bye for now

2008-12-31 Thread James
Nikos Chantziaras realnc at arcor.de writes:


  Then something is wrong with your box or it isn't powerful enough.

 It isn't.
 
  Works perfectly in mine.

 Same here (at home.)



Nikos,

I had a problem with a dual (amd) machine once. I dropped

MAKEOPTS=-j3
to -j1

for a while and the workstation was fine. After some months
I rebuild every thing and it was then fine. to use -j2.

I'd  be curious to see how it affect your problem with
-j1 set?


James







Re: [gentoo-user] Re: Kpdf crashes with large documents.

2008-12-31 Thread Dale
James wrote:
 Dale rdalek1967 at gmail.com writes:


   
 attempting to read, it when Kpdf crashed. 
 


 tried acroread?


 works great for me.

 ymmv,


 James


   

I did use something else to finish reading my manual but I prefer to use
Kpdf since I am accustomed to it already.  I just want to try and get it
fixed for next time plus, it may be a bug that needs some Raid sprayed
on it.

Dale

:-)  :-) 




[gentoo-user] Re: Kpdf crashes with large documents.

2008-12-31 Thread James
Dale rdalek1967 at gmail.com writes:


 I did use something else to finish reading my manual but I prefer to use
 Kpdf since I am accustomed to it already.  I just want to try and get it
 fixed for next time plus, it may be a bug that needs some Raid sprayed
 on it.


All of the open source *pdf readers have had  problems
over the years. Sporadic and hard to find, in my
experiences. The more sophisticated pdf files especially.


good luck.


James







Re: [gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread Matt Causey
You wanna post the PDF?  I'd be curious to see if it crashes kpdf on
my system...


--
Matt

On Wed, Dec 31, 2008 at 6:59 PM, Dale rdalek1...@gmail.com wrote:
 Hi,

 I recently stole me a Motorola Razr phone and it didn't come with the
 manual.  I downloaded it off the Motorola website and was reading, or
 attempting to read, it when Kpdf crashed.  It does this when I scroll
 down to about page 30 or so.  It's a pretty large document since it has
 both English and Spanish.

 I did re-emerge Kpdf, both versions of qt that I have on here and even
 glibc.  Those are the things mentioned in the crash report.  It still
 crashes.  Could this be something besides Kpdf?  Anybody else see
 something in the crash log?

 Here is the crash log:

 (no debugging symbols found)
 Using host libthread_db library /lib/libthread_db.so.1.
 (no debugging symbols found)

 SNIP 

 [Thread debugging using libthread_db enabled]
 [New Thread 0xb697e6d0 (LWP 25418)]
 [New Thread 0xb5c3db90 (LWP 25485)]
 (no debugging symbols found)
 (no debugging symbols found)

  SNIP 

 0xb716a568 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
 #0  0xb716a568 in QObject::activate_signal () from
 /usr/qt/3/lib/libqt-mt.so.3
 #1  0xb74955bc in QApplication::guiThreadAwake ()
   from /usr/qt/3/lib/libqt-mt.so.3
 #2  0xb70bac22 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
 #3  0xb71210f0 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
 #4  0xb7120f76 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
 #5  0xb710a4af in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
 #6  0x0805005c in ?? ()
 #7  0xbfc8ff50 in ?? ()
 #8  0xbfc90050 in ?? ()
 #9  0x in ?? ()

 I snipped out the repeating stuff.  Thoughts?

 Thanks.

 Dale

 :-)  :-)

 P.S.  I bought the phone really cheap.  I just feel like I stole it.
 LOL





Re: [gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread Dale
Matt Causey wrote:
 You wanna post the PDF?  I'd be curious to see if it crashes kpdf on
 my system...


 --
 Matt

 On Wed, Dec 31, 2008 at 6:59 PM, Dale rdalek1...@gmail.com wrote:
   
 Hi,

 I recently stole me a Motorola Razr phone and it didn't come with the
 manual.  I downloaded it off the Motorola website and was reading, or
 attempting to read, it when Kpdf crashed.  It does this when I scroll
 down to about page 30 or so.  It's a pretty large document since it has
 both English and Spanish.

 I did re-emerge Kpdf, both versions of qt that I have on here and even
 glibc.  Those are the things mentioned in the crash report.  It still
 crashes.  Could this be something besides Kpdf?  Anybody else see
 something in the crash log?

 Here is the crash log:

 (no debugging symbols found)
 Using host libthread_db library /lib/libthread_db.so.1.
 (no debugging symbols found)

 SNIP 

 [Thread debugging using libthread_db enabled]
 [New Thread 0xb697e6d0 (LWP 25418)]
 [New Thread 0xb5c3db90 (LWP 25485)]
 (no debugging symbols found)
 (no debugging symbols found)

  SNIP 

 0xb716a568 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
 #0  0xb716a568 in QObject::activate_signal () from
 /usr/qt/3/lib/libqt-mt.so.3
 #1  0xb74955bc in QApplication::guiThreadAwake ()
   from /usr/qt/3/lib/libqt-mt.so.3
 #2  0xb70bac22 in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
 #3  0xb71210f0 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
 #4  0xb7120f76 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
 #5  0xb710a4af in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
 #6  0x0805005c in ?? ()
 #7  0xbfc8ff50 in ?? ()
 #8  0xbfc90050 in ?? ()
 #9  0x in ?? ()

 I snipped out the repeating stuff.  Thoughts?

 Thanks.

 Dale

 :-)  :-)

 P.S.  I bought the phone really cheap.  I just feel like I stole it.
 LOL


 

It is pretty big so I'll post a link. 

http://www.phonedog.com/cell-phone-research/motorola-razr-v3i_user-manual.aspx

Just click on the link to download the manual.  I think it is about 4 or
5Mbs or so.  I'm on dialup so it takes me a little while.

This may also be a bas download.  In my searches on google, someone
mentioned a bad/missing font could cause that but I got a lot of fonts
installed on here.

Thanks

Dale

:-)  :-) 



Re: [gentoo-user] Re: Kpdf crashes with large documents.

2008-12-31 Thread Dale
James wrote:
 Dale rdalek1967 at gmail.com writes:


   
 I did use something else to finish reading my manual but I prefer to use
 Kpdf since I am accustomed to it already.  I just want to try and get it
 fixed for next time plus, it may be a bug that needs some Raid sprayed
 on it.
 


 All of the open source *pdf readers have had  problems
 over the years. Sporadic and hard to find, in my
 experiences. The more sophisticated pdf files especially.


 good luck.


 James


   

This is the first time I have had trouble with it crashing like this.  I
don't use one enough to try to learn another one tho.  Plus, that would
be one more package to keep up to date. 

Dale

:-)  :-)



Re: [gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread darren kirby
quoth the Dale:
 Matt Causey wrote:
  You wanna post the PDF?  I'd be curious to see if it crashes kpdf on
  my system...
 
 
  --
  Matt
 
  On Wed, Dec 31, 2008 at 6:59 PM, Dale rdalek1...@gmail.com wrote:
  Hi,
 
  I recently stole me a Motorola Razr phone and it didn't come with the
  manual.  I downloaded it off the Motorola website and was reading, or
  attempting to read, it when Kpdf crashed.  It does this when I scroll
  down to about page 30 or so.  It's a pretty large document since it has
  both English and Spanish.
 
  I did re-emerge Kpdf, both versions of qt that I have on here and even
  glibc.  Those are the things mentioned in the crash report.  It still
  crashes.  Could this be something besides Kpdf?  Anybody else see
  something in the crash log?
 
  Here is the crash log:
 
  (no debugging symbols found)
  Using host libthread_db library /lib/libthread_db.so.1.
  (no debugging symbols found)
 
  SNIP 
 
  [Thread debugging using libthread_db enabled]
  [New Thread 0xb697e6d0 (LWP 25418)]
  [New Thread 0xb5c3db90 (LWP 25485)]
  (no debugging symbols found)
  (no debugging symbols found)
 
   SNIP 
 
  0xb716a568 in QObject::activate_signal () from
  /usr/qt/3/lib/libqt-mt.so.3 #0  0xb716a568 in QObject::activate_signal
  () from
  /usr/qt/3/lib/libqt-mt.so.3
  #1  0xb74955bc in QApplication::guiThreadAwake ()
from /usr/qt/3/lib/libqt-mt.so.3
  #2  0xb70bac22 in QEventLoop::processEvents ()
from /usr/qt/3/lib/libqt-mt.so.3
  #3  0xb71210f0 in QEventLoop::enterLoop () from
  /usr/qt/3/lib/libqt-mt.so.3 #4  0xb7120f76 in QEventLoop::exec () from
  /usr/qt/3/lib/libqt-mt.so.3 #5  0xb710a4af in QApplication::exec () from
  /usr/qt/3/lib/libqt-mt.so.3 #6  0x0805005c in ?? ()
  #7  0xbfc8ff50 in ?? ()
  #8  0xbfc90050 in ?? ()
  #9  0x in ?? ()
 
  I snipped out the repeating stuff.  Thoughts?
 
  Thanks.
 
  Dale
 
  :-)  :-)
 
  P.S.  I bought the phone really cheap.  I just feel like I stole it.
  LOL

 It is pretty big so I'll post a link.

 http://www.phonedog.com/cell-phone-research/motorola-razr-v3i_user-manual.a
spx

 Just click on the link to download the manual.  I think it is about 4 or
 5Mbs or so.  I'm on dialup so it takes me a little while.

Sorry to rub it in Dale, but it took 12 seconds to download here. And yes, it 
crashed my kpdf ... and my xpdf.

Oddly, KGhostView renders it fine. Something fishy...


 Thanks

 Dale

 :-)  :-)

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
...the number of UNIX installations has grown to 10, with more expected...
- Dennis Ritchie and Ken Thompson, June 1972



Re: [gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread Matt Causey
Well...I've seen more than one dodgy PDF document crash readers
before.  Seems that there must be features or fonts (as mentioned
earlier...) which can crash readers that were not written by Adobe...

On Wed, Dec 31, 2008 at 10:44 PM, darren kirby bulli...@badcomputer.org wrote:
 quoth the Dale:
 Matt Causey wrote:
  You wanna post the PDF?  I'd be curious to see if it crashes kpdf on
  my system...
 
 
  --
  Matt
 
  On Wed, Dec 31, 2008 at 6:59 PM, Dale rdalek1...@gmail.com wrote:
  Hi,
 
  I recently stole me a Motorola Razr phone and it didn't come with the
  manual.  I downloaded it off the Motorola website and was reading, or
  attempting to read, it when Kpdf crashed.  It does this when I scroll
  down to about page 30 or so.  It's a pretty large document since it has
  both English and Spanish.
 
  I did re-emerge Kpdf, both versions of qt that I have on here and even
  glibc.  Those are the things mentioned in the crash report.  It still
  crashes.  Could this be something besides Kpdf?  Anybody else see
  something in the crash log?
 
  Here is the crash log:
 
  (no debugging symbols found)
  Using host libthread_db library /lib/libthread_db.so.1.
  (no debugging symbols found)
 
  SNIP 
 
  [Thread debugging using libthread_db enabled]
  [New Thread 0xb697e6d0 (LWP 25418)]
  [New Thread 0xb5c3db90 (LWP 25485)]
  (no debugging symbols found)
  (no debugging symbols found)
 
   SNIP 
 
  0xb716a568 in QObject::activate_signal () from
  /usr/qt/3/lib/libqt-mt.so.3 #0  0xb716a568 in QObject::activate_signal
  () from
  /usr/qt/3/lib/libqt-mt.so.3
  #1  0xb74955bc in QApplication::guiThreadAwake ()
from /usr/qt/3/lib/libqt-mt.so.3
  #2  0xb70bac22 in QEventLoop::processEvents ()
from /usr/qt/3/lib/libqt-mt.so.3
  #3  0xb71210f0 in QEventLoop::enterLoop () from
  /usr/qt/3/lib/libqt-mt.so.3 #4  0xb7120f76 in QEventLoop::exec () from
  /usr/qt/3/lib/libqt-mt.so.3 #5  0xb710a4af in QApplication::exec () from
  /usr/qt/3/lib/libqt-mt.so.3 #6  0x0805005c in ?? ()
  #7  0xbfc8ff50 in ?? ()
  #8  0xbfc90050 in ?? ()
  #9  0x in ?? ()
 
  I snipped out the repeating stuff.  Thoughts?
 
  Thanks.
 
  Dale
 
  :-)  :-)
 
  P.S.  I bought the phone really cheap.  I just feel like I stole it.
  LOL

 It is pretty big so I'll post a link.

 http://www.phonedog.com/cell-phone-research/motorola-razr-v3i_user-manual.a
spx

 Just click on the link to download the manual.  I think it is about 4 or
 5Mbs or so.  I'm on dialup so it takes me a little while.

 Sorry to rub it in Dale, but it took 12 seconds to download here. And yes, it
 crashed my kpdf ... and my xpdf.

 Oddly, KGhostView renders it fine. Something fishy...


 Thanks

 Dale

 :-)  :-)

 -d
 --
 darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
 ...the number of UNIX installations has grown to 10, with more expected...
 - Dennis Ritchie and Ken Thompson, June 1972





Re: [gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread Dale
darren kirby wrote:
 quoth the Dale:
   


 It is pretty big so I'll post a link.

 http://www.phonedog.com/cell-phone-research/motorola-razr-v3i_user-manual.a
 spx

 Just click on the link to download the manual.  I think it is about 4 or
 5Mbs or so.  I'm on dialup so it takes me a little while.
 

 Sorry to rub it in Dale, but it took 12 seconds to download here. And yes, it 
 crashed my kpdf ... and my xpdf.

 Oddly, KGhostView renders it fine. Something fishy...

   
 Thanks

 Dale

 :-)  :-)
 

 -d
   

About the broadband.  :-P   LOL

I used Kghostview here and it worked fine.  I even printed it with it. 
No problem there. 

Anybody think of anything else I can re-emerge that may help?  Here is
my current emerge and USE flags:

r...@smoker / # emerge -pv glibc =x11-libs/qt-3.3.8-r4
=x11-libs/qt-4.3.3 kpdf

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] x11-libs/qt-3.3.8-r4  USE=cups gif ipv6 opengl sqlite
-debug -doc -examples -firebird -immqt -immqt-bc -mysql -nas -nis -odbc
-postgres -xinerama 0 kB
[ebuild   R   ] sys-libs/glibc-2.6.1  USE=-debug -gd -glibc-omitfp
(-hardened) (-multilib) -nls -profile (-selinux) -vanilla 0 kB
[ebuild   R   ] x11-libs/qt-4.3.3  USE=accessibility cups dbus gif jpeg
opengl png qt3support sqlite ssl tiff zlib -debug -doc -examples
-firebird -glib -mng -mysql -nas -nis -odbc -pch -postgres -sqlite3
-xinerama INPUT_DEVICES=-wacom 0 kB
[ebuild   R   ] kde-base/kpdf-3.5.10  USE=-debug 0 kB

Total: 4 packages (4 reinstalls), Size of downloads: 0 kB
r...@smoker / #

I'm clueless. 

Dale

:-)  :-) 




[gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Michael P. Soulier
So, like a good gentoo user I'm emerging some updates available for my system.

To my surprise when I happen to look at the screen (as it's taking some time
to build and I'm obviously not watching the entire time), I see this:


 * * WARNING *
 * 
 * You are currently installing a version of nvidia-drivers that is
 * known not to work with a video card you have installed on your
 * system. If this is intentional, please ignore this. If it is not
 * please perform the following steps:
 * 
 * Add the following mask entry to /etc/portage/package.mask by
 * echo =x11-drivers/nvidia-drivers-177.0.0  /etc/portage/package.mask
 * 
 * Failure to perform the steps above could result in a non-working
 * X setup.
 * 
 * For more information please read:
 * http://www.nvidia.com/object/IO_32667.html
 * You must be in the video group to use the NVIDIA device
 * For more info, read the docs at
 * http://www.gentoo.org/doc/en/nvidia-guide.xml#doc_chap3_sect6
 * 
 * This ebuild installs a kernel module and X driver. Both must
 * match explicitly in their version. This means, if you restart
 * X, you most modprobe -r nvidia before starting it back up
 * 
 * To use the NVIDIA GLX, run eselect opengl set nvidia
 * 
 * nVidia has requested that any bug reports submitted have the
 * output of /usr/bin/nvidia-bug-report.sh included.
 * 
 * To work with compiz, you must enable the AddARGBGLXVisuals option.
 * 
 * If you are having resolution problems, try disabling DynamicTwinView.

Sure enough, X no longer works. I'm following the instructions now, but...
Don't you think the default action here should be to do nothing instead of
breaking my system?

Not impressed. Hopefully this critical message would be summarized at the end
of the build too. Kind of important. I got lucky and happened to see it...

Thanks,
Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein


pgpf78ENYCqG9.pgp
Description: PGP signature


[gentoo-user] pre-emerge steps

2008-12-31 Thread Michael P. Soulier
Having just been bitten by some of my hardware being abandoned with the latest
version of a software package I am left to question the entire philosophy in
gentoo of always running bleeding edge. Not touching a system that's working
is becoming far more tempting, and I'm curious as to what others here have to
say about that.

Part of the point of running Linux for me is to save money and run older
hardware, but that doesn't work if the latest versions of the software that I
like to use abandons that hardware.

What do the rest of you do in preparation for regular upgrades? On BSD there
was a /usr/ports/UPDATING file that I should check for notes on potential
problems with upgrades before performing them. What's the best way to check if
picking up a newer package could break my system? Ideally a way that isn't
prohibitively time-consuming...

Thanks,
Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein


pgpNVj2zf9YMf.pgp
Description: PGP signature


Re: [gentoo-user] Kpdf crashes with large documents.

2008-12-31 Thread Philip Webb
081231 darren kirby wrote:
 On Wed, Dec 31, 2008 at 6:59 PM, Dale rdalek1...@gmail.com wrote:
 I recently stole a Motorola Razr phone which didn't come with manual.
 I downloaded it off the Motorola website and was attempting to read,
 when Kpdf crashed.  It does this when I scroll down to about page 30 .
   
 http://www.phonedog.com/cell-phone-research/motorola-razr-v3i_user-manual.aspx
 it crashed my kpdf and my xpdf.
 Oddly, KGhostView renders it fine. Something fishy...

Same here on a generally stable Gentoo on which Kpdf  Xpdf are reliable.
IIRC i've seen rare cases of this before, when KGV saved the day.
The problem here happens with certain pages in the file, eg  p 10 ;
some later pages, eg  pp 11-12 , are ok.
There must be something in a few pages which is not correct PDF format.
Has anyone searched Gentoo Forum/Bugs or KDE bugs ?
Anyway, it's clearly a bug in Kpdf, which sb reported.

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] KVM recognition changes in recent kernels

2008-12-31 Thread Stroller


On 31 Dec 2008, at 06:44, Harry Putnam wrote:

...
I've noticed a change in recent mnths where until bootup is complete
the kvm switch is not recogized.  I see that thru several kernel
upgrades and various kernel builds.


Please confirm that you are able to enter the BIOS using the KVM  the  
usual keyboard shortcut key (ESC, f2, f10, whatever).



I don't have the kvm model to hand but it is an IOGEAR 4 port USB
...
I have to have a second keyboard connected direct if I want to mess
around with grub or something... while testing kernels.  But once
bootup reaches the login prompt the KVM is in the loop, and I can use
the kvm connected keyboard.


Some (many?) BIOS have settings for support of USB keyboard, HID / 
or legacy USB. If your KVM is connecting to the PC by USB then you  
may wish to check these.


Stroller.



Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Stroller


On 31 Dec 2008, at 23:33, Michael P. Soulier wrote:

...
Don't you think the default action here should be to do nothing  
instead of

breaking my system?



  That proposal is ludicrous and completely counter to the Unix
   way of doing things.

Not my opinion, just quoting.

Stroller.



Re: [gentoo-user] pre-emerge steps

2008-12-31 Thread Stroller


On 31 Dec 2008, at 23:51, Michael P. Soulier wrote:
Having just been bitten by some of my hardware being abandoned with  
the latest
version of a software package I am left to question the entire  
philosophy in
gentoo of always running bleeding edge. Not touching a system that's  
working
is becoming far more tempting, and I'm curious as to what others  
here have to

say about that.


I think what you should be asking is why upstream have stopped  
supporting your hardware. Hopefully they'll be able to give a good  
reason for doing so.


IMO the Gentoo philosophy is not to run bleeding edge, but just to  
install from upstream, keeping it as pure and unchanged as possible.


Stroller.




Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Graham Murray
Michael P. Soulier msoul...@digitaltorque.ca writes:

 Sure enough, X no longer works. I'm following the instructions now, but...
 Don't you think the default action here should be to do nothing instead of
 breaking my system?

I think that the default action should be that such 'breakages' should
be checked during the dependency building phase, a message displayed and
the emerge stop[0]. Then you could either mask the offending package or
issue a special flag[1] to emerge to acknowledge the 'problem' but
install/upgrade the package anyway.

[0] As with package blockers.

[1] A new flag, something like '--unsafe'



Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Volker Armin Hemmann
On Donnerstag 01 Januar 2009, Michael P. Soulier wrote:


 Not impressed. Hopefully this critical message would be summarized at the
 end of the build too. Kind of important. I got lucky and happened to see
 it...

it was. Also:
elog
and
elogv

the tools are there. It is your fault of not using them.



Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Michael P. Soulier
On 01/01/09 Volker Armin Hemmann said:

 it was. Also:
 elog
 and
 elogv
 
 the tools are there. It is your fault of not using them.

Great, please demonstrate how I was to know about this breakage before it
happened, and I'll change how I use the tools. 

Cheers,
Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein


pgpxV9iiQAqAl.pgp
Description: PGP signature


Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Michael P. Soulier
On 01/01/09 Graham Murray said:

 I think that the default action should be that such 'breakages' should
 be checked during the dependency building phase, a message displayed and
 the emerge stop[0]. Then you could either mask the offending package or
 issue a special flag[1] to emerge to acknowledge the 'problem' but
 install/upgrade the package anyway.
 
 [0] As with package blockers.
 
 [1] A new flag, something like '--unsafe'

I completely agree.

Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein


pgpeepqUcOO6E.pgp
Description: PGP signature


Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Volker Armin Hemmann
On Donnerstag 01 Januar 2009, Michael P. Soulier wrote:
 On 01/01/09 Volker Armin Hemmann said:
  it was. Also:
  elog
  and
  elogv
 
  the tools are there. It is your fault of not using them.

 Great, please demonstrate how I was to know about this breakage before it
 happened, and I'll change how I use the tools.

 Cheers,
 Mike

after the emerge you read the messages with elogv and downgrade. No harm done.




Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Michael P. Soulier
On 01/01/09 Volker Armin Hemmann said:

 after the emerge you read the messages with elogv and downgrade. No harm done.

I'll be sure to try that, thank you. However, would not avoiding a bad upgrade
in the first place be a better-behaved tool? Especially when the package in
question knew that it was likely incompatible?

I'm not saying that this could not be avoided with more work, I'm saying that
I shouldn't have to if the tools were better behaved.

Cheers,
Mike
-- 
Michael P. Soulier msoul...@digitaltorque.ca
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
--Albert Einstein


pgpvQiiWRZS2y.pgp
Description: PGP signature


Re: [gentoo-user] nvidia warning comes a tad late

2008-12-31 Thread Volker Armin Hemmann
On Donnerstag 01 Januar 2009, Michael P. Soulier wrote:
 On 01/01/09 Volker Armin Hemmann said:
  after the emerge you read the messages with elogv and downgrade. No harm
  done.

 I'll be sure to try that, thank you. However, would not avoiding a bad
 upgrade in the first place be a better-behaved tool? Especially when the
 package in question knew that it was likely incompatible?

 I'm not saying that this could not be avoided with more work, I'm saying
 that I shouldn't have to if the tools were better behaved.

 Cheers,
 Mike

how should 'the tool' know what card you are using? and even if portage could 
parse lspci output - why make it slower and more easily to break if all 
breakage can be avoided by simply reading first - then upgrading? Do you 
always install the latest drivers without reading up on them first?
Nvidia's 'deprecation' strategy is a pain in the ass and they are doing it for 
a long time now. So this time it bit you. Next time it will be 6XXX card 
users, then 7XXX card users and so on. That is why you have to go to nvnews 
first and then upgrade. Not the other way round.