Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

palica

Members
  • Posts

    294
  • Joined

  • Last visited

  • Days Won

    11

Posts posted by palica

  1. On 11.3.2016 at 1:53 AM, paddymac said:

    [    0.178812] * The chipset may have PM-Timer Bug. Due to workarounds for a bug,               
    * this clock source is slow. If you are sure your timer does not have               
    * this bug, please use "acpi_pm_good" to disable the workaround

    It means that your LPC device is old and contains a bug in the PM-Timer (most commonly known as "High Precision Event Time"). I wouldn't bother with it:

    The Low Pin Count bus, or LPC bus, is used on IBM-compatible personal computers to connect low-bandwidth devices to the CPU, such as the boot ROM and the "legacy" I/O devices (behind a super I/O chip). The "legacy" I/O devices usually include serial and parallel ports, PS/2 keyboard, PS/2 mouse, floppy disk controller and—more recently—the Trusted Platform Module (TPM). The physical wires of the LPC bus usually connect to the southbridge chip on a PC motherboard, which contains the circuit equivalents of the "legacy" onboard peripherals of the IBM PC/AT architecture, such as the two programmable interrupt controllers, the programmable interval timer, and the two ISA DMA controllers.

    Unless your TPM requires it and/or your system is giving you headaches related with any of those devices I wouldn't touch it.

     

    PS: do you still use it?

  2. installed:
    mail-filter/spamassassin-3.4.1-r20::net-kit  USE="berkdb ipv6 ssl -cron -ldap -libressl -mysql -postgres -qmail -sqlite {-test}"
    
    fun-1 ~ # /usr/sbin/spamd
    Dec 22 02:35:28.794 [3627] error: config: no rules were found! Do you need to run 'sa-update'?
    config: no rules were found!  Do you need to run 'sa-update'?
    fun-1 ~ # sa-update
    fun-1 ~ # /usr/sbin/spamd
    Dec 22 02:35:45.759 [3641] info: spamd: server started on IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783 (running version 3.4.1)
    Dec 22 02:35:45.759 [3641] info: spamd: server pid: 3641
    Dec 22 02:35:45.762 [3641] info: spamd: server successfully spawned child process, pid 3645
    Dec 22 02:35:45.764 [3641] info: spamd: server successfully spawned child process, pid 3646
    Dec 22 02:35:45.765 [3641] info: prefork: child states: IS
    Dec 22 02:35:45.766 [3641] info: prefork: child states: II
    ^CDec 22 02:35:46.484 [3641] info: spamd: server killed by SIGINT, shutting down
    fun-1 ~ # /etc/init.d/spamd start
     * Starting spamd ...                                                                                                                                                             [ ok ]
    fun-1 ~ # netstat -anlt
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State
    tcp        0      0 127.0.0.1:783           0.0.0.0:*               LISTEN
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
    tcp        0      0 10.214.101.187:34366    148.251.212.58:80       TIME_WAIT
    tcp        0      0 10.214.101.187:42150    140.211.11.105:80       TIME_WAIT
    tcp        0      0 10.214.101.187:44828    148.251.29.131:80       TIME_WAIT
    tcp        0      0 10.214.101.187:44832    148.251.29.131:80       TIME_WAIT
    tcp6       0      0 ::1:783                 :::*                    LISTEN
    tcp6       0      0 :::22                   :::*                    LISTEN
    

    do you still have trouble running it on localhost?

  3. this is and old question, do you still need help here?

    Please note that stable is no more. There is only current and current-hardened.

    Basically the warning means:

    • if you select recode you cannot select imap
    • if you select sharedmem you cannot select threads

    So you have to decide if you need recode and imap at the same tame and sharedmem and threads.

    Cheers!

  4. If you have used sandybridge stage from build.funtoo.org, then the reason it doen't work is that your processor is "crippled" by Intel and doesn't support all the instructions a sandybridge should.

    Here are the stage3 CPU_FLAGS:

    aes avx mmx mmxext popcnt sse sse2 sse3 sse4_1 sse4_2 ssse3

    Here are your flags that are supported by your lets-sell-this-as-sandybridge-processor-by-intel:

    fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm epb tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm arat pln pts

    So you are missing aes, avx, mmxext, and sse3.

    You have to possible solutions. I use generic_64 or start with generic_64 and rebuild then using your supported CPU_FLAGS.

    If this helps, please mark the question as solved. Thank you

     

×
×
  • Create New...