LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-09-2011, 03:08 PM   #61
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled

Yes I have the driver installed and I'm back to yesterday...

I am just having a frustration day... sometimes it happens! Here are the problems that remain to be fixed:
-overscan compensation problem
-the suspend script
-alsa does not detect my nvidia card so no sound through HDMI
-vlc built from alienbob's script now crash or simply no longer start
-If I can get these issues out of the way I will be back on track.

You might be right, opening a new thread about this htpc might be worthwhile, but really I is difficult => the suspend script is "part" of my htpc and if I open a new thread, I will just duplicate the progress and info..

I need to get the supend script running and then I will attack the HDMI sound problem. I know I am not the only one with that problem, but everybody are using ubuntu and with a few simple commands, they get the thing fixed... apt-get.... apt-install... so on...

Whatever happens, I will not give up. I never gave up before so I dont see why i should start today. Plus, I am learning linux/slackware at the same time, so I guess the learning factor doesnt help either.

Last edited by lpallard; 01-09-2011 at 03:10 PM.
 
Old 01-09-2011, 03:20 PM   #62
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
OK back to the suspend problem

Quote:
The config file for the syslogger should be /etc/syslog.conf - so make sure it's set up appropriately.
TO be honest, you are probably light years ahead of me in linux... my syslog.conf contains:

Quote:
# /etc/syslog.conf
# For info about the format of this file, see "man syslog.conf"
# and /usr/doc/sysklogd/README.linux. Note the '-' prefixing some
# of these entries; this omits syncing the file after every logging.
# In the event of a crash, some log information might be lost, so
# if this is a concern to you then you might want to remove the '-'.
# Be advised this will cause a performation loss if you're using
# programs that do heavy logging.

# Uncomment this to see kernel messages on the console.
#kern.* /dev/console

# Log anything 'info' or higher, but lower than 'warn'.
# Exclude authpriv, cron, mail, and news. These are logged elsewhere.
*.info;*.!warn;\
authpriv.none;cron.none;mail.none;news.none -/var/log/messages

# Log anything 'warn' or higher.
# Exclude authpriv, cron, mail, and news. These are logged elsewhere.
*.warn;\
authpriv.none;cron.none;mail.none;news.none -/var/log/syslog

# Debugging information is logged here.
*.=debug -/var/log/debug

# Private authentication message logging:
authpriv.* -/var/log/secure

# Cron related logs:
cron.* -/var/log/cron

# Mail related logs:
mail.* -/var/log/maillog

# Emergency level messages go to all users:
*.emerg *

# This log is for news and uucp errors:
uucp,news.crit -/var/log/spooler

# Uncomment these if you'd like INN to keep logs on everything.
# You won't need this if you don't run INN (the InterNetNews daemon).
#news.=crit -/var/log/news/news.crit
#news.=err -/var/log/news/news.err
#news.notice -/var/log/news/news.notice
Do you understand something in that? I dont!

Regarding the kernel.log file, I understand, if syslog does not create it at first, no way it will collect info lkater on...

Quote:
your kernel must already have the "Enable PM Debug" feature enabled in its compilation, or you can't debug power management. "PM Debug" is a compile-time kernel build option. I'm not sure if it can be enabled via a boot-line switch - I doubt it - you likely would need to rebuild your kernel to enable it.
I'll look at the link you provided. Is it complicated? Any risk to fry the whole machine?

Last edited by lpallard; 01-09-2011 at 03:27 PM.
 
Old 01-09-2011, 05:18 PM   #63
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Code:
#kern.* /dev/console
Change the above line to read:
Code:
kern.* /var/log/kernel
Then restart your syslogger or reboot.

Quote:
I'll look at the link you provided. Is it complicated?
Well, you decide if it's complicated, after reading the other thread.
How complicated it is, is subjective. I think it is not complicated, but you may find quite the opposite. The important thing is to understand what you are doing, before beginning. There are LOADS of instructions here-there-everywhere about how to rebuild your kernel. LQ is chock full of such threads.
Quote:
Any risk to fry the whole machine?
Ehh.. It is possible to make it so it doesn't boot next reboot, but if you read & follow a good reliable set of instructions for rebuilding your Slack kernel, that should not happen. The instructions I gave in post #38 in that other thread I linked to, look to be still accurate and fairly comprehensive. So, read & understand what's going on in those instructions, and if necessary, ask for clarification on anything. I know that for someone who has never thought about building their kernel, it sounds daunting; I can still remember my first attempt, which failed. But after a few attempts, it becomes much more clear. Most important thing: never remove or delete your original kernel, either from your /boot folder, or from the lilo.conf file. That will ensure that even if your new custom kernel is borked, you can still reboot your original working kernel.
 
Old 01-09-2011, 05:36 PM   #64
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
So the /var/log/kernel now had this in it:

Code:
Jan  9 17:31:01 htpc kernel: klogd 1.4.1, log source = /proc/kmsg started.
Jan  9 17:31:01 htpc kernel: 0xfceff8ff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:12.2: supports D1 D2
Jan  9 17:31:01 htpc kernel: pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot
Jan  9 17:31:01 htpc kernel: pci 0000:00:12.2: PME# disabled
Jan  9 17:31:01 htpc kernel: pci 0000:00:13.0: reg 10: [mem 0xfcefc000-0xfcefcfff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:13.1: reg 10: [mem 0xfcefb000-0xfcefbfff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:13.2: reg 10: [mem 0xfceff400-0xfceff4ff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:13.2: supports D1 D2
Jan  9 17:31:01 htpc kernel: pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot
Jan  9 17:31:01 htpc kernel: pci 0000:00:13.2: PME# disabled
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.1: reg 10: [io  0x0000-0x0007]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.1: reg 14: [io  0x0000-0x0003]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.1: reg 18: [io  0x0000-0x0007]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.1: reg 1c: [io  0x0000-0x0003]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.1: reg 20: [io  0xff00-0xff0f]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.2: reg 10: [mem 0xfcef4000-0xfcef7fff 64bit]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.2: PME# disabled
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.5: reg 10: [mem 0xfcefa000-0xfcefafff]
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.0: reg 10: [mem 0xfd000000-0xfdffffff]
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.0: reg 14: [mem 0xf0000000-0xf7ffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.0: reg 1c: [mem 0xf8000000-0xf9ffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.0: reg 24: [io  0xdc00-0xdc7f]
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.0: reg 30: [mem 0xfcf80000-0xfcffffff pref]
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.1: reg 10: [mem 0xfcf7c000-0xfcf7ffff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0: PCI bridge to [bus 01-01]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0:   bridge window [io  0xd000-0xdfff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0:   bridge window [mem 0xfcf00000-0xfdffffff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0:   bridge window [mem 0xf0000000-0xf9ffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:02:00.0: reg 10: [mem 0xfe400000-0xfe7fffff 64bit]
Jan  9 17:31:01 htpc kernel: pci 0000:02:00.0: reg 18: [mem 0xfe000000-0xfe3fffff 64bit]
Jan  9 17:31:01 htpc kernel: pci 0000:02:00.0: supports D1 D2
Jan  9 17:31:01 htpc kernel: pci 0000:02:00.0: PME# supported from D0 D1 D2
Jan  9 17:31:01 htpc kernel: pci 0000:02:00.0: PME# disabled
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0: PCI bridge to [bus 02-02]
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0:   bridge window [mem 0xfe000000-0xfe7fffff]
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: reg 10: [io  0xe800-0xe8ff]
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: reg 18: [mem 0xfbfff000-0xfbffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: reg 20: [mem 0xfbff8000-0xfbffbfff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: reg 30: [mem 0xfebf0000-0xfebfffff pref]
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: supports D1 D2
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot D3cold
Jan  9 17:31:01 htpc kernel: pci 0000:03:00.0: PME# disabled
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0: PCI bridge to [bus 03-03]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0:   bridge window [io  0xe000-0xefff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0:   bridge window [mem 0xfeb00000-0xfebfffff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0:   bridge window [mem 0xfbf00000-0xfbffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.4: PCI bridge to [bus 04-04] (subtractive decode)
Jan  9 17:31:01 htpc kernel: pci_bus 0000:00: on NUMA node 0
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE2._PRT]
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCE9._PRT]
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCEA._PRT]
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0PC._PRT]
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 4 7 10 *11 12 14 15)
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 4 7 10 *11 12 14 15)
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 4 7 *10 11 12 14 15)
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 4 7 *10 11 12 14 15)
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 4 7 10 11 12 14 15) *0, disabled.
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 4 7 10 11 12 14 15) *0, disabled.
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 4 7 *10 11 12 14 15)
Jan  9 17:31:01 htpc kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 4 7 10 11 12 14 15) *0, disabled.
Jan  9 17:31:01 htpc kernel: vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
Jan  9 17:31:01 htpc kernel: vgaarb: loaded
Jan  9 17:31:01 htpc kernel: SCSI subsystem initialized
Jan  9 17:31:01 htpc kernel: libata version 3.00 loaded.
Jan  9 17:31:01 htpc kernel: usbcore: registered new interface driver usbfs
Jan  9 17:31:01 htpc kernel: usbcore: registered new interface driver hub
Jan  9 17:31:01 htpc kernel: usbcore: registered new device driver usb
Jan  9 17:31:01 htpc kernel: raid6: int64x1   2570 MB/s
Jan  9 17:31:01 htpc kernel: raid6: int64x2   3519 MB/s
Jan  9 17:31:01 htpc kernel: raid6: int64x4   2691 MB/s
Jan  9 17:31:01 htpc kernel: raid6: int64x8   2343 MB/s
Jan  9 17:31:01 htpc kernel: raid6: sse2x1    4125 MB/s
Jan  9 17:31:01 htpc kernel: raid6: sse2x2    6878 MB/s
Jan  9 17:31:01 htpc kernel: raid6: sse2x4    8207 MB/s
Jan  9 17:31:01 htpc kernel: raid6: using algorithm sse2x4 (8207 MB/s)
Jan  9 17:31:01 htpc kernel: PCI: Using ACPI for IRQ routing
Jan  9 17:31:01 htpc kernel: PCI: pci_cache_line_size set to 64 bytes
Jan  9 17:31:01 htpc kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
Jan  9 17:31:01 htpc kernel: hpet0: 4 comparators, 32-bit 14.318180 MHz counter
Jan  9 17:31:01 htpc kernel: Switching to clocksource tsc
Jan  9 17:31:01 htpc kernel: pnp: PnP ACPI init
Jan  9 17:31:01 htpc kernel: ACPI: bus type pnp registered
Jan  9 17:31:01 htpc kernel: pnp: PnP ACPI: found 14 devices
Jan  9 17:31:01 htpc kernel: ACPI: ACPI bus type pnp unregistered
Jan  9 17:31:01 htpc kernel: system 00:09: [mem 0xfec00000-0xfec00fff] could not be reserved
Jan  9 17:31:01 htpc kernel: system 00:09: [mem 0xfee00000-0xfee00fff] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x04d0-0x04d1] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x040b] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x04d6] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0c00-0x0c01] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0c14] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0c50-0x0c51] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0c52] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0c6c] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0c6f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0cd0-0x0cd1] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0cd2-0x0cd3] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0cd4-0x0cd5] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0cd6-0x0cd7] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0cd8-0x0cdf] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0b00-0x0b3f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0800-0x089f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0b00-0x0b0f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0b20-0x0b3f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0900-0x090f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0x0910-0x091f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [io  0xfe00-0xfefe] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [mem 0xdff00000-0xdfffffff] could not be reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [mem 0xffb80000-0xffbfffff] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [mem 0xfec10000-0xfec1001f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0a: [mem 0xfed40000-0xfed44fff] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0b: [io  0x0230-0x023f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0b: [io  0x0290-0x029f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0b: [io  0x0300-0x030f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0b: [io  0x0a30-0x0a3f] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0c: [mem 0xe0000000-0xefffffff] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0d: [mem 0x00000000-0x0009ffff] could not be reserved
Jan  9 17:31:01 htpc kernel: system 00:0d: [mem 0x000c0000-0x000cffff] has been reserved
Jan  9 17:31:01 htpc kernel: system 00:0d: [mem 0x000e0000-0x000fffff] could not be reserved
Jan  9 17:31:01 htpc kernel: system 00:0d: [mem 0x00100000-0xdfefffff] could not be reserved
Jan  9 17:31:01 htpc kernel: system 00:0d: [mem 0xfec00000-0xffffffff] could not be reserved
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0: PCI bridge to [bus 01-01]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0:   bridge window [io  0xd000-0xdfff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0:   bridge window [mem 0xfcf00000-0xfdffffff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0:   bridge window [mem 0xf0000000-0xf9ffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0: PCI bridge to [bus 02-02]
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0:   bridge window [io  disabled]
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0:   bridge window [mem 0xfe000000-0xfe7fffff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0:   bridge window [mem pref disabled]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0: PCI bridge to [bus 03-03]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0:   bridge window [io  0xe000-0xefff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0:   bridge window [mem 0xfeb00000-0xfebfffff]
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0:   bridge window [mem 0xfbf00000-0xfbffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.4: PCI bridge to [bus 04-04]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.4:   bridge window [io  disabled]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.4:   bridge window [mem disabled]
Jan  9 17:31:01 htpc kernel: pci 0000:00:14.4:   bridge window [mem pref disabled]
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:01 htpc kernel: pci 0000:00:02.0: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan  9 17:31:01 htpc kernel: pci 0000:00:09.0: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:01 htpc kernel: pci 0000:00:0a.0: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:01: resource 0 [io  0xd000-0xdfff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:01: resource 1 [mem 0xfcf00000-0xfdffffff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:01: resource 2 [mem 0xf0000000-0xf9ffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:02: resource 1 [mem 0xfe000000-0xfe7fffff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:03: resource 0 [io  0xe000-0xefff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:03: resource 1 [mem 0xfeb00000-0xfebfffff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:03: resource 2 [mem 0xfbf00000-0xfbffffff 64bit pref]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:04: resource 3 [io  0x0000-0xffff]
Jan  9 17:31:01 htpc kernel: pci_bus 0000:04: resource 4 [mem 0x00000000-0xffffffffffffffff]
Jan  9 17:31:01 htpc kernel: NET: Registered protocol family 2
Jan  9 17:31:01 htpc kernel: IP route cache hash table entries: 131072 (order: 8, 1048576 bytes)
Jan  9 17:31:01 htpc kernel: TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
Jan  9 17:31:01 htpc kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jan  9 17:31:01 htpc kernel: TCP: Hash tables configured (established 262144 bind 65536)
Jan  9 17:31:01 htpc kernel: TCP reno registered
Jan  9 17:31:01 htpc kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
Jan  9 17:31:01 htpc kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
Jan  9 17:31:01 htpc kernel: NET: Registered protocol family 1
Jan  9 17:31:01 htpc kernel: RPC: Registered udp transport module.
Jan  9 17:31:01 htpc kernel: RPC: Registered tcp transport module.
Jan  9 17:31:01 htpc kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan  9 17:31:01 htpc kernel: pci 0000:01:00.0: Boot video device
Jan  9 17:31:01 htpc kernel: PCI: CLS 64 bytes, default 64
Jan  9 17:31:01 htpc kernel: PCI-DMA: Disabling AGP.
Jan  9 17:31:01 htpc kernel: PCI-DMA: aperture base @ 20000000 size 65536 KB
Jan  9 17:31:01 htpc kernel: PCI-DMA: using GART IOMMU.
Jan  9 17:31:01 htpc kernel: PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
Jan  9 17:31:01 htpc kernel: Intel AES-NI instructions are not detected.
Jan  9 17:31:01 htpc kernel: audit: initializing netlink socket (disabled)
Jan  9 17:31:01 htpc kernel: type=2000 audit(1294594174.203:1): initialized
Jan  9 17:31:01 htpc kernel: VFS: Disk quotas dquot_6.5.2
Jan  9 17:31:01 htpc kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jan  9 17:31:01 htpc kernel: DLM (built May 12 2010 23:08:15) installed
Jan  9 17:31:01 htpc kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Jan  9 17:31:01 htpc kernel: NTFS driver 2.1.29 [Flags: R/W].
Jan  9 17:31:01 htpc kernel: ROMFS MTD (C) 2007 Red Hat, Inc.
Jan  9 17:31:01 htpc kernel: JFS: nTxBlock = 8192, nTxLock = 65536
Jan  9 17:31:01 htpc kernel: SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
Jan  9 17:31:01 htpc kernel: SGI XFS Quota Management subsystem
Jan  9 17:31:01 htpc kernel: OCFS2 1.5.0
Jan  9 17:31:01 htpc kernel: ocfs2: Registered cluster interface o2cb
Jan  9 17:31:01 htpc kernel: ocfs2: Registered cluster interface user
Jan  9 17:31:01 htpc kernel: OCFS2 Node Manager 1.5.0
Jan  9 17:31:01 htpc kernel: OCFS2 DLM 1.5.0
Jan  9 17:31:01 htpc kernel: OCFS2 DLMFS 1.5.0
Jan  9 17:31:01 htpc kernel: OCFS2 User DLM kernel interface loaded
Jan  9 17:31:01 htpc kernel: Btrfs loaded
Jan  9 17:31:01 htpc kernel: Slow work thread pool: Starting up
Jan  9 17:31:01 htpc kernel: Slow work thread pool: Ready
Jan  9 17:31:01 htpc kernel: GFS2 (built May 12 2010 23:09:03) installed
Jan  9 17:31:01 htpc kernel: msgmni has been set to 7891
Jan  9 17:31:01 htpc kernel: alg: No test for cipher_null (cipher_null-generic)
Jan  9 17:31:01 htpc kernel: alg: No test for ecb(cipher_null) (ecb-cipher_null)
Jan  9 17:31:01 htpc kernel: alg: No test for digest_null (digest_null-generic)
Jan  9 17:31:01 htpc kernel: alg: No test for compress_null (compress_null-generic)
Jan  9 17:31:01 htpc kernel: alg: No test for fcrypt (fcrypt-generic)
Jan  9 17:31:01 htpc kernel: alg: No test for stdrng (krng)
Jan  9 17:31:01 htpc kernel: async_tx: api initialized (async)
Jan  9 17:31:01 htpc kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Jan  9 17:31:01 htpc kernel: io scheduler noop registered
Jan  9 17:31:01 htpc kernel: io scheduler deadline registered
Jan  9 17:31:01 htpc kernel: io scheduler cfq registered (default)
Jan  9 17:31:01 htpc kernel: pcieport 0000:00:02.0: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: pcieport 0000:00:02.0: irq 24 for MSI/MSI-X
Jan  9 17:31:01 htpc kernel: pcieport 0000:00:09.0: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: pcieport 0000:00:09.0: irq 25 for MSI/MSI-X
Jan  9 17:31:01 htpc kernel: pcieport 0000:00:0a.0: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: pcieport 0000:00:0a.0: irq 26 for MSI/MSI-X
Jan  9 17:31:01 htpc kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jan  9 17:31:01 htpc kernel: vesafb: framebuffer at 0xf9000000, mapped to 0xffffc90010700000, using 3072k, total 14336k
Jan  9 17:31:01 htpc kernel: vesafb: mode is 1024x768x16, linelength=2048, pages=1
Jan  9 17:31:01 htpc kernel: vesafb: scrolling: redraw
Jan  9 17:31:01 htpc kernel: vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
Jan  9 17:31:01 htpc kernel: Console: switching to colour frame buffer device 128x48
Jan  9 17:31:01 htpc kernel: fb0: VESA VGA frame buffer device
Jan  9 17:31:01 htpc kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
Jan  9 17:31:01 htpc kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Jan  9 17:31:01 htpc kernel: 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Jan  9 17:31:01 htpc kernel: floppy0: no floppy controllers found
Jan  9 17:31:01 htpc kernel: brd: module loaded
Jan  9 17:31:01 htpc kernel: loop: module loaded
Jan  9 17:31:01 htpc kernel: Compaq SMART2 Driver (v 2.6.0)
Jan  9 17:31:01 htpc kernel: HP CISS Driver (v 3.6.20)
Jan  9 17:31:01 htpc kernel: input: Macintosh mouse button emulation as /devices/virtual/input/input0
Jan  9 17:31:01 htpc kernel: Loading iSCSI transport class v2.0-870.
Jan  9 17:31:01 htpc kernel: fnic: Cisco FCoE HBA Driver, ver 1.0.0.1121
Jan  9 17:31:01 htpc kernel: Adaptec aacraid driver 1.1-5[24702]-ms
Jan  9 17:31:01 htpc kernel: aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
Jan  9 17:31:01 htpc kernel: scsi: <fdomain> Detection failed (no card)
Jan  9 17:31:01 htpc kernel: QLogic Fibre Channel HBA Driver: 8.03.01-k10
Jan  9 17:31:01 htpc kernel: iscsi: registered transport (qla4xxx)
Jan  9 17:31:01 htpc kernel: QLogic iSCSI HBA Driver
Jan  9 17:31:01 htpc kernel: Emulex LightPulse Fibre Channel SCSI driver 8.3.7
Jan  9 17:31:01 htpc kernel: Copyright(c) 2004-2009 Emulex.  All rights reserved.
Jan  9 17:31:01 htpc kernel: Brocade BFA FC/FCOE SCSI driver - version: 2.0.0.0
Jan  9 17:31:01 htpc kernel: DC390: clustering now enabled by default. If you get problems load
Jan  9 17:31:01 htpc kernel:        with "disable_clustering=1" and report to maintainers
Jan  9 17:31:01 htpc kernel: megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
Jan  9 17:31:01 htpc kernel: megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
Jan  9 17:31:01 htpc kernel: megasas: 00.00.04.12-rc1 Thu Sep. 17 11:41:51 PST 2009
Jan  9 17:31:01 htpc kernel: mpt2sas version 03.100.03.00 loaded
Jan  9 17:31:01 htpc kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.05
Jan  9 17:31:01 htpc kernel: 3ware Storage Controller device driver for Linux v1.26.02.002.
Jan  9 17:31:01 htpc kernel: 3ware 9000 Storage Controller device driver for Linux v2.26.02.013.
Jan  9 17:31:01 htpc kernel: LSI 3ware SAS/SATA-RAID Controller device driver for Linux v3.26.02.000.
Jan  9 17:31:01 htpc kernel: ipr: IBM Power RAID SCSI Device Driver version: 2.4.3 (June 10, 2009)
Jan  9 17:31:01 htpc kernel: RocketRAID 3xxx/4xxx Controller driver v1.6 (090910)
Jan  9 17:31:01 htpc kernel: stex: Promise SuperTrak EX Driver version: 4.6.0000.4
Jan  9 17:31:01 htpc kernel: st: Version 20081215, fixed bufsize 32768, s/g segs 256
Jan  9 17:31:01 htpc kernel: ahci 0000:00:11.0: version 3.0
Jan  9 17:31:01 htpc kernel: ahci 0000:00:11.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Jan  9 17:31:01 htpc kernel: ahci 0000:00:11.0: AHCI 0001.0100 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
Jan  9 17:31:01 htpc kernel: ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio slum part ccc 
Jan  9 17:31:01 htpc kernel: scsi0 : ahci
Jan  9 17:31:01 htpc kernel: scsi1 : ahci
Jan  9 17:31:01 htpc kernel: scsi2 : ahci
Jan  9 17:31:01 htpc kernel: scsi3 : ahci
Jan  9 17:31:01 htpc kernel: scsi4 : ahci
Jan  9 17:31:01 htpc kernel: scsi5 : ahci
Jan  9 17:31:01 htpc kernel: ata1: SATA max UDMA/133 abar m1024@0xfceffc00 port 0xfceffd00 irq 22
Jan  9 17:31:01 htpc kernel: ata2: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 22
Jan  9 17:31:01 htpc kernel: ata3: SATA max UDMA/133 irq_stat 0x00400000, PHY RDY changed
Jan  9 17:31:01 htpc kernel: ata4: SATA max UDMA/133 abar m1024@0xfceffc00 port 0xfceffe80 irq 22
Jan  9 17:31:01 htpc kernel: ata5: SATA max UDMA/133 abar m1024@0xfceffc00 port 0xfcefff00 irq 22
Jan  9 17:31:01 htpc kernel: ata6: SATA max UDMA/133 abar m1024@0xfceffc00 port 0xfcefff80 irq 22
Jan  9 17:31:01 htpc kernel: pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan  9 17:31:01 htpc kernel: pata_atiixp 0000:00:14.1: setting latency timer to 64
Jan  9 17:31:01 htpc kernel: scsi6 : pata_atiixp
Jan  9 17:31:01 htpc kernel: scsi7 : pata_atiixp
Jan  9 17:31:01 htpc kernel: ata7: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14
Jan  9 17:31:01 htpc kernel: ata8: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15
Jan  9 17:31:01 htpc kernel: I2O subsystem v1.325
Jan  9 17:31:01 htpc kernel: i2o: max drivers = 8
Jan  9 17:31:01 htpc kernel: I2O Configuration OSM v1.323
Jan  9 17:31:01 htpc kernel: I2O Bus Adapter OSM v1.317
Jan  9 17:31:01 htpc kernel: I2O Block Device OSM v1.325
Jan  9 17:31:01 htpc kernel: I2O SCSI Peripheral OSM v1.316
Jan  9 17:31:01 htpc kernel: I2O ProcFS OSM v1.316
Jan  9 17:31:01 htpc kernel: Fusion MPT base driver 3.04.13
Jan  9 17:31:01 htpc kernel: Copyright (c) 1999-2008 LSI Corporation
Jan  9 17:31:01 htpc kernel: Fusion MPT SPI Host driver 3.04.13
Jan  9 17:31:01 htpc kernel: Fusion MPT FC Host driver 3.04.13
Jan  9 17:31:01 htpc kernel: Fusion MPT SAS Host driver 3.04.13
Jan  9 17:31:02 htpc kernel: Fusion MPT misc device (ioctl) driver 3.04.13
Jan  9 17:31:02 htpc kernel: mptctl: Registered with Fusion MPT base driver
Jan  9 17:31:02 htpc kernel: mptctl: /dev/mptctl @ (major,minor=10,220)
Jan  9 17:31:02 htpc kernel: Fusion MPT LAN driver 3.04.13
Jan  9 17:31:02 htpc kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:12.2: EHCI Host Controller
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:12.2: new USB bus registered, assigned bus number 1
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:12.2: debug port 1
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:12.2: irq 17, io mem 0xfceff800
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:12.2: USB 2.0 started, EHCI 1.00
Jan  9 17:31:02 htpc kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jan  9 17:31:02 htpc kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb1: Product: EHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb1: Manufacturer: Linux 2.6.33.4 ehci_hcd
Jan  9 17:31:02 htpc kernel: usb usb1: SerialNumber: 0000:00:12.2
Jan  9 17:31:02 htpc kernel: hub 1-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 1-0:1.0: 6 ports detected
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:13.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:13.2: EHCI Host Controller
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 2
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:13.2: debug port 1
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:13.2: irq 19, io mem 0xfceff400
Jan  9 17:31:02 htpc kernel: ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00
Jan  9 17:31:02 htpc kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jan  9 17:31:02 htpc kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb2: Product: EHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb2: Manufacturer: Linux 2.6.33.4 ehci_hcd
Jan  9 17:31:02 htpc kernel: usb usb2: SerialNumber: 0000:00:13.2
Jan  9 17:31:02 htpc kernel: hub 2-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 2-0:1.0: 6 ports detected
Jan  9 17:31:02 htpc kernel: 116x: driver isp116x-hcd, 03 Nov 2005
Jan  9 17:31:02 htpc kernel: driver isp1362-hcd, 2005-04-04
Jan  9 17:31:02 htpc kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.0: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.0: new USB bus registered, assigned bus number 3
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.0: irq 16, io mem 0xfcefe000
Jan  9 17:31:02 htpc kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
Jan  9 17:31:02 htpc kernel: usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb3: Product: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb3: Manufacturer: Linux 2.6.33.4 ohci_hcd
Jan  9 17:31:02 htpc kernel: usb usb3: SerialNumber: 0000:00:12.0
Jan  9 17:31:02 htpc kernel: hub 3-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 3-0:1.0: 3 ports detected
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.1: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.1: new USB bus registered, assigned bus number 4
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:12.1: irq 16, io mem 0xfcefd000
Jan  9 17:31:02 htpc kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
Jan  9 17:31:02 htpc kernel: usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb4: Product: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb4: Manufacturer: Linux 2.6.33.4 ohci_hcd
Jan  9 17:31:02 htpc kernel: usb usb4: SerialNumber: 0000:00:12.1
Jan  9 17:31:02 htpc kernel: hub 4-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 4-0:1.0: 3 ports detected
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.0: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 5
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.0: irq 18, io mem 0xfcefc000
Jan  9 17:31:02 htpc kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
Jan  9 17:31:02 htpc kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb5: Product: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb5: Manufacturer: Linux 2.6.33.4 ohci_hcd
Jan  9 17:31:02 htpc kernel: usb usb5: SerialNumber: 0000:00:13.0
Jan  9 17:31:02 htpc kernel: hub 5-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 5-0:1.0: 3 ports detected
 
Old 01-09-2011, 05:37 PM   #65
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
Part 2...

Code:
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.1: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 6
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:13.1: irq 18, io mem 0xfcefb000
Jan  9 17:31:02 htpc kernel: ata5: SATA link down (SStatus 0 SControl 300)
Jan  9 17:31:02 htpc kernel: ata4: SATA link down (SStatus 0 SControl 300)
Jan  9 17:31:02 htpc kernel: ata6: SATA link down (SStatus 0 SControl 300)
Jan  9 17:31:02 htpc kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
Jan  9 17:31:02 htpc kernel: usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb6: Product: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb6: Manufacturer: Linux 2.6.33.4 ohci_hcd
Jan  9 17:31:02 htpc kernel: usb usb6: SerialNumber: 0000:00:13.1
Jan  9 17:31:02 htpc kernel: hub 6-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 6-0:1.0: 3 ports detected
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:14.5: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:14.5: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:14.5: new USB bus registered, assigned bus number 7
Jan  9 17:31:02 htpc kernel: ohci_hcd 0000:00:14.5: irq 18, io mem 0xfcefa000
Jan  9 17:31:02 htpc kernel: usb 2-2: new high speed USB device using ehci_hcd and address 2
Jan  9 17:31:02 htpc kernel: usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
Jan  9 17:31:02 htpc kernel: usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  9 17:31:02 htpc kernel: usb usb7: Product: OHCI Host Controller
Jan  9 17:31:02 htpc kernel: usb usb7: Manufacturer: Linux 2.6.33.4 ohci_hcd
Jan  9 17:31:02 htpc kernel: usb usb7: SerialNumber: 0000:00:14.5
Jan  9 17:31:02 htpc kernel: hub 7-0:1.0: USB hub found
Jan  9 17:31:02 htpc kernel: hub 7-0:1.0: 2 ports detected
Jan  9 17:31:02 htpc kernel: uhci_hcd: USB Universal Host Controller Interface driver
Jan  9 17:31:02 htpc kernel: sl811: driver sl811-hcd, 19 May 2005
Jan  9 17:31:02 htpc kernel: r8a66597_hcd: driver r8a66597_hcd, 2009-05-26
Jan  9 17:31:02 htpc kernel: Initializing USB Mass Storage driver...
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver usb-storage
Jan  9 17:31:02 htpc kernel: USB Mass Storage support registered.
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-alauda
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-cypress
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-datafab
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-freecom
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-isd200
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-jumpshot
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-karma
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-onetouch
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-sddr09
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-sddr55
Jan  9 17:31:02 htpc kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver ums-usbat
Jan  9 17:31:02 htpc kernel: PNP: No PS/2 controller found. Probing ports directly.
Jan  9 17:31:02 htpc kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jan  9 17:31:02 htpc kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jan  9 17:31:02 htpc kernel: mice: PS/2 mouse device common for all mice
Jan  9 17:31:02 htpc kernel: md: linear personality registered for level -1
Jan  9 17:31:02 htpc kernel: md: raid0 personality registered for level 0
Jan  9 17:31:02 htpc kernel: ata1.00: ATA-8: OCZ-AGILITY2, 1.23, max UDMA/133
Jan  9 17:31:02 htpc kernel: ata1.00: 78161328 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Jan  9 17:31:02 htpc kernel: md: raid1 personality registered for level 1
Jan  9 17:31:02 htpc kernel: md: raid10 personality registered for level 10
Jan  9 17:31:02 htpc kernel: md: raid6 personality registered for level 6
Jan  9 17:31:02 htpc kernel: md: raid5 personality registered for level 5
Jan  9 17:31:02 htpc kernel: md: raid4 personality registered for level 4
Jan  9 17:31:02 htpc kernel: md: multipath personality registered for level -4
Jan  9 17:31:02 htpc kernel: ata1.00: configured for UDMA/133
Jan  9 17:31:02 htpc kernel: device-mapper: uevent: version 1.0.3
Jan  9 17:31:02 htpc kernel: device-mapper: ioctl: 4.17.0-ioctl (2010-03-05) initialised: dm-devel@redhat.com
Jan  9 17:31:02 htpc kernel: cpuidle: using governor ladder
Jan  9 17:31:02 htpc kernel: cpuidle: using governor menu
Jan  9 17:31:02 htpc kernel: TCP cubic registered
Jan  9 17:31:02 htpc kernel: Initializing XFRM netlink socket
Jan  9 17:31:02 htpc kernel: NET: Registered protocol family 17
Jan  9 17:31:02 htpc kernel: scsi 0:0:0:0: Direct-Access     ATA      OCZ-AGILITY2     1.23 PQ: 0 ANSI: 5
Jan  9 17:31:02 htpc kernel: sd 0:0:0:0: [sda] 78161328 512-byte logical blocks: (40.0 GB/37.2 GiB)
Jan  9 17:31:02 htpc kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan  9 17:31:02 htpc kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan  9 17:31:02 htpc kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan  9 17:31:02 htpc kernel:  sda: sda1 sda2 sda3 < sda5 sda6 >
Jan  9 17:31:02 htpc kernel: usb 2-2: New USB device found, idVendor=058f, idProduct=6362
Jan  9 17:31:02 htpc kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  9 17:31:02 htpc kernel: sd 0:0:0:0: [sda] Attached SCSI disk
Jan  9 17:31:02 htpc kernel: usb 2-2: Product: Mass Storage Device
Jan  9 17:31:02 htpc kernel: usb 2-2: Manufacturer: Generic
Jan  9 17:31:02 htpc kernel: usb 2-2: SerialNumber: 058F312D81B1
Jan  9 17:31:02 htpc kernel: scsi8 : usb-storage 2-2:1.0
Jan  9 17:31:02 htpc kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan  9 17:31:02 htpc kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan  9 17:31:02 htpc kernel: ata3.00: ATA-8: Hitachi HDS721010CLA332, JP4OA39C, max UDMA/133
Jan  9 17:31:02 htpc kernel: ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
Jan  9 17:31:02 htpc kernel: ata3.00: configured for UDMA/133
Jan  9 17:31:02 htpc kernel: ata2.00: ATAPI: ASUS    BR-04B2T, 1.01, max UDMA/100, ATAPI AN
Jan  9 17:31:02 htpc kernel: ata2.00: configured for UDMA/100
Jan  9 17:31:02 htpc kernel: scsi 1:0:0:0: CD-ROM            ASUS     BR-04B2T         1.01 PQ: 0 ANSI: 5
Jan  9 17:31:02 htpc kernel: sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
Jan  9 17:31:02 htpc kernel: Uniform CD-ROM driver Revision: 3.20
Jan  9 17:31:02 htpc kernel: sr 1:0:0:0: Attached scsi CD-ROM sr0
Jan  9 17:31:02 htpc kernel: scsi 2:0:0:0: Direct-Access     ATA      Hitachi HDS72101 JP4O PQ: 0 ANSI: 5
Jan  9 17:31:02 htpc kernel: sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Jan  9 17:31:02 htpc kernel: sd 2:0:0:0: [sdb] Write Protect is off
Jan  9 17:31:02 htpc kernel: sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
Jan  9 17:31:02 htpc kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan  9 17:31:02 htpc kernel:  sdb: sdb1 < sdb5 >
Jan  9 17:31:02 htpc kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
Jan  9 17:31:02 htpc kernel: usb 5-3: new full speed USB device using ohci_hcd and address 2
Jan  9 17:31:02 htpc kernel: registered taskstats version 1
Jan  9 17:31:02 htpc kernel: md: Waiting for all devices to be available before autodetect
Jan  9 17:31:02 htpc kernel: md: If you don't use raid, use raid=noautodetect
Jan  9 17:31:02 htpc kernel: md: Autodetecting RAID arrays.
Jan  9 17:31:02 htpc kernel: md: Scanned 0 and added 0 devices.
Jan  9 17:31:02 htpc kernel: md: autorun ...
Jan  9 17:31:02 htpc kernel: md: ... autorun DONE.
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): found reiserfs format "3.6" with standard journal
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): using ordered data mode
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): journal params: device sda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): checking transaction log (sda5)
Jan  9 17:31:02 htpc kernel: usb 5-3: New USB device found, idVendor=0471, idProduct=060c
Jan  9 17:31:02 htpc kernel: usb 5-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  9 17:31:02 htpc kernel: usb 5-3: Product: BB+ Dongle(e.d)
Jan  9 17:31:02 htpc kernel: usb 5-3: Manufacturer:  
Jan  9 17:31:02 htpc kernel: usb 5-3: SerialNumber: AAJD
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): replayed 100 transactions in 1 seconds
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Using r5 hash to sort names
Jan  9 17:31:02 htpc kernel: VFS: Mounted root (reiserfs filesystem) readonly on device 8:5.
Jan  9 17:31:02 htpc kernel: devtmpfs: mounted
Jan  9 17:31:02 htpc kernel: Freeing unused kernel memory: 764k freed
Jan  9 17:31:02 htpc kernel: Write protecting the kernel read-only data: 16384k
Jan  9 17:31:02 htpc kernel: Freeing unused kernel memory: 2004k freed
Jan  9 17:31:02 htpc kernel: Freeing unused kernel memory: 1260k freed
Jan  9 17:31:02 htpc kernel: usb 6-2: new low speed USB device using ohci_hcd and address 2
Jan  9 17:31:02 htpc kernel: udev: starting version 153
Jan  9 17:31:02 htpc kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan  9 17:31:02 htpc kernel: sr 1:0:0:0: Attached scsi generic sg1 type 5
Jan  9 17:31:02 htpc kernel: sd 2:0:0:0: Attached scsi generic sg2 type 0
Jan  9 17:31:02 htpc kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Jan  9 17:31:02 htpc kernel: Linux agpgart interface v0.103
Jan  9 17:31:02 htpc kernel: usb 6-2: New USB device found, idVendor=046d, idProduct=c03d
Jan  9 17:31:02 htpc kernel: usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  9 17:31:02 htpc kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
Jan  9 17:31:02 htpc kernel: r8169 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:02 htpc kernel: usb 6-2: Product: USB-PS/2 Optical Mouse
Jan  9 17:31:02 htpc kernel: r8169 0000:03:00.0: setting latency timer to 64
Jan  9 17:31:02 htpc kernel: usb 6-2: Manufacturer: Logitech
Jan  9 17:31:02 htpc kernel: r8169 0000:03:00.0: irq 27 for MSI/MSI-X
Jan  9 17:31:02 htpc kernel: eth0: RTL8168d/8111d at 0xffffc90010c16000, 20:cf:30:68:d3:38, XID 083000c0 IRQ 27
Jan  9 17:31:02 htpc kernel: ACPI: Power Button [PWRB]
Jan  9 17:31:02 htpc kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Jan  9 17:31:02 htpc kernel: ACPI: Power Button [PWRF]
Jan  9 17:31:02 htpc kernel: ACPI: I/O resource piix4_smbus [0xb00-0xb07] conflicts with ACPI region SOR1 [0xb00-0xb0f]
Jan  9 17:31:02 htpc kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jan  9 17:31:02 htpc kernel: saa7164 driver loaded
Jan  9 17:31:02 htpc kernel: saa7164 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
Jan  9 17:31:02 htpc kernel: parport_pc 00:06: reported by Plug and Play ACPI
Jan  9 17:31:02 htpc kernel: CORE saa7164[0]: subsystem: 0070:8851, board: Hauppauge WinTV-HVR2250 [card=7,autodetected]
Jan  9 17:31:02 htpc kernel: saa7164[0]/0: found at 0000:02:00.0, rev: 129, irq: 17, latency: 0, mmio: 0xfe400000
Jan  9 17:31:02 htpc kernel: saa7164 0000:02:00.0: setting latency timer to 64
Jan  9 17:31:02 htpc kernel: parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
Jan  9 17:31:02 htpc kernel: ppdev: user-space parallel port driver
Jan  9 17:31:02 htpc kernel: input: PC Speaker as /devices/platform/pcspkr/input/input3
Jan  9 17:31:02 htpc kernel: nvidia: module license 'NVIDIA' taints kernel.
Jan  9 17:31:02 htpc kernel: Disabling lock debugging due to kernel taint
Jan  9 17:31:02 htpc kernel: rtc_cmos 00:03: RTC can wake from S4
Jan  9 17:31:02 htpc kernel: rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
Jan  9 17:31:02 htpc kernel: rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() no first image
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() Waiting for firmware upload (v4l-saa7164-1.0.3-3.fw)
Jan  9 17:31:02 htpc kernel: saa7164 0000:02:00.0: firmware: requesting v4l-saa7164-1.0.3-3.fw
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() firmware read 4038864 bytes.
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() firmware loaded.
Jan  9 17:31:02 htpc kernel: Firmware file header part 1:
Jan  9 17:31:02 htpc kernel:  .FirmwareSize = 0x0
Jan  9 17:31:02 htpc kernel:  .BSLSize = 0x0
Jan  9 17:31:02 htpc kernel:  .Reserved = 0x3da0d
Jan  9 17:31:02 htpc kernel:  .Version = 0x3
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() SecBootLoader.FileSize = 4038864
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() FirmwareSize = 0x1fd6
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() BSLSize = 0x0
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() Reserved = 0x0
Jan  9 17:31:02 htpc kernel: saa7164_downloadfirmware() Version = 0x1d1c
Jan  9 17:31:02 htpc kernel: usb 6-3: new low speed USB device using ohci_hcd and address 3
Jan  9 17:31:02 htpc kernel: usb 6-3: New USB device found, idVendor=049f, idProduct=0051
Jan  9 17:31:02 htpc kernel: HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Jan  9 17:31:02 htpc kernel: usb 6-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  9 17:31:02 htpc kernel: usb 6-3: Product: USB Keyboard
Jan  9 17:31:02 htpc kernel: usb 6-3: Manufacturer: Chicony 
Jan  9 17:31:02 htpc kernel: HDA Intel 0000:01:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Jan  9 17:31:02 htpc kernel: hda_intel: Disable MSI for Nvidia chipset
Jan  9 17:31:02 htpc kernel: HDA Intel 0000:01:00.1: setting latency timer to 64
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver hiddev
Jan  9 17:31:02 htpc kernel: input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.1/usb6/6-2/6-2:1.0/input/input4
Jan  9 17:31:02 htpc kernel: generic-usb 0003:046D:C03D.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.1-2/input0
Jan  9 17:31:02 htpc kernel: input: Chicony  USB Keyboard as /devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.0/input/input5
Jan  9 17:31:02 htpc kernel: generic-usb 0003:049F:0051.0002: input,hidraw1: USB HID v1.00 Keyboard [Chicony  USB Keyboard] on usb-0000:00:13.1-3/input0
Jan  9 17:31:02 htpc kernel: input: Chicony  USB Keyboard as /devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.1/input/input6
Jan  9 17:31:02 htpc kernel: generic-usb 0003:049F:0051.0003: input,hiddev96,hidraw2: USB HID v1.00 Device [Chicony  USB Keyboard] on usb-0000:00:13.1-3/input1
Jan  9 17:31:02 htpc kernel: usbcore: registered new interface driver usbhid
Jan  9 17:31:02 htpc kernel: usbhid: USB HID core driver
Jan  9 17:31:02 htpc kernel: nvidia 0000:01:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Jan  9 17:31:02 htpc kernel: nvidia 0000:01:00.0: setting latency timer to 64
Jan  9 17:31:02 htpc kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
Jan  9 17:31:02 htpc kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  260.19.29  Wed Dec  8 12:08:56 PST 2010
Jan  9 17:31:02 htpc kernel: scsi 8:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:0: Attached scsi generic sg3 type 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:0: [sdc] Attached SCSI removable disk
Jan  9 17:31:02 htpc kernel: scsi 8:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:1: Attached scsi generic sg4 type 0
Jan  9 17:31:02 htpc kernel: scsi 8:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:2: Attached scsi generic sg5 type 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:1: [sdd] Attached SCSI removable disk
Jan  9 17:31:02 htpc kernel: sd 8:0:0:2: [sde] Attached SCSI removable disk
Jan  9 17:31:02 htpc kernel: scsi 8:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:3: Attached scsi generic sg6 type 0
Jan  9 17:31:02 htpc kernel: sd 8:0:0:3: [sdf] Attached SCSI removable disk
Jan  9 17:31:02 htpc kernel: saa7164_downloadimage() Image downloaded, booting...
Jan  9 17:31:02 htpc kernel: saa7164_downloadimage() Image booted successfully.
Jan  9 17:31:02 htpc kernel: starting firmware download(2)
Jan  9 17:31:02 htpc kernel: saa7164_downloadimage() Image downloaded, booting...
Jan  9 17:31:02 htpc kernel: saa7164_downloadimage() Image booted successfully.
Jan  9 17:31:02 htpc kernel: firmware download complete.
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: Hauppauge model 88061, rev C4F2, serial# 7122356
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: MAC address is 00:0d:fe:6c:ad:b4
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: tuner model is NXP 18271C2_716x (idx 152, type 4)
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: audio processor is SAA7164 (idx 43)
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: decoder processor is SAA7164 (idx 40)
Jan  9 17:31:02 htpc kernel: tveeprom 0-0000: has radio, has IR receiver, has no IR transmitter
Jan  9 17:31:02 htpc kernel: saa7164[0]: Hauppauge eeprom: model=88061
Jan  9 17:31:02 htpc kernel: tda18271 1-0060: creating new instance
Jan  9 17:31:02 htpc kernel: TDA18271HD/C2 detected @ 1-0060
Jan  9 17:31:02 htpc kernel: DVB: registering new adapter (saa7164)
Jan  9 17:31:02 htpc kernel: DVB: registering adapter 0 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
Jan  9 17:31:02 htpc kernel: tda18271 2-0060: creating new instance
Jan  9 17:31:02 htpc kernel: TDA18271HD/C2 detected @ 2-0060
Jan  9 17:31:02 htpc kernel: tda18271: performing RF tracking filter calibration
Jan  9 17:31:02 htpc kernel: tda18271: RF tracking filter calibration complete
Jan  9 17:31:02 htpc kernel: DVB: registering new adapter (saa7164)
Jan  9 17:31:02 htpc kernel: DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
Jan  9 17:31:02 htpc kernel: Adding 4104596k swap on /dev/sda2.  Priority:-1 extents:1 across:4104596k SSD
Jan  9 17:31:02 htpc kernel: fuse init (API version 7.13)
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [732953 851578 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [732953 851560 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [732953 851050 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [732953 851028 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [147 281607 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [147 281572 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [147 281503 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [147 281498 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): Removing [147 281492 0x0 SD]..done
Jan  9 17:31:02 htpc kernel: REISERFS (device sda5): There were 9 uncompleted unlinks/truncates. Completed
Jan  9 17:31:02 htpc kernel: lp0: using parport0 (interrupt-driven).
Jan  9 17:31:02 htpc kernel: lp0: console ready
Jan  9 17:31:02 htpc kernel: REISERFS (device sda1): found reiserfs format "3.6" with standard journal
Jan  9 17:31:02 htpc kernel: REISERFS (device sda1): using ordered data mode
Jan  9 17:31:02 htpc kernel: REISERFS (device sda1): journal params: device sda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan  9 17:31:02 htpc kernel: REISERFS (device sda1): checking transaction log (sda1)
Jan  9 17:31:02 htpc kernel: REISERFS (device sda1): Using r5 hash to sort names
Jan  9 17:31:02 htpc kernel: REISERFS (device sda6): found reiserfs format "3.6" with standard journal
Jan  9 17:31:02 htpc kernel: REISERFS (device sda6): using ordered data mode
Jan  9 17:31:02 htpc kernel: REISERFS (device sda6): journal params: device sda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan  9 17:31:02 htpc kernel: REISERFS (device sda6): checking transaction log (sda6)
Jan  9 17:31:02 htpc kernel: REISERFS (device sda6): Using r5 hash to sort names
Jan  9 17:31:02 htpc kernel: REISERFS (device sdb5): found reiserfs format "3.6" with standard journal
Jan  9 17:31:02 htpc kernel: REISERFS (device sdb5): using ordered data mode
Jan  9 17:31:02 htpc kernel: REISERFS (device sdb5): journal params: device sdb5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Jan  9 17:31:02 htpc kernel: REISERFS (device sdb5): checking transaction log (sdb5)
Jan  9 17:31:02 htpc kernel: REISERFS (device sdb5): Using r5 hash to sort names
Jan  9 17:31:02 htpc kernel: r8169: eth0: link up
Jan  9 17:31:02 htpc kernel: r8169: eth0: link up
Jan  9 17:31:06 htpc kernel: NET: Registered protocol family 10
Jan  9 17:31:06 htpc kernel: lo: Disabled Privacy Extensions
Jan  9 17:31:07 htpc kernel: svc: failed to register lockdv1 RPC service (errno 97).
Jan  9 17:31:13 htpc kernel: tda18271: performing RF tracking filter calibration
Jan  9 17:31:15 htpc kernel: tda18271: RF tracking filter calibration complete
Jan  9 17:31:16 htpc kernel: tda18271: performing RF tracking filter calibration
Jan  9 17:31:17 htpc kernel: eth0: no IPv6 routers present
Jan  9 17:31:18 htpc kernel: tda18271: RF tracking filter calibration complete
So is it what you were expecting to see??

Regarding the kernel compilation, I did it once on my laptop, shouldnt be a problem...
 
Old 01-09-2011, 09:41 PM   #66
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by lpallard View Post
So is it what you were expecting to see??
Well, it looks like a normal kernel log so far, containing much of the usual sort of stuff you see shortly after bootup. Nothing out of the ordinary that I can see.

In this file, you should see all kernel output during debugging of suspend, and actually, even without debugging turned on, you'll see the kernel's output during actual suspends too.
 
Old 01-09-2011, 09:43 PM   #67
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
OK so you think the kernel might be OK? The problem I have might not be related to the kernel?
 
Old 01-09-2011, 10:18 PM   #68
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Umm, well, I never thought or said there was necessarily anything "wrong" with the kernel - the recompile stuff is only for if you wish to enable "PM Debugging" (power management debugging) so that you can test the various stages of suspend. If you don't want/need to do that debugging, you don't need to rebuild. The debugging can help figure out if it's the kernel, or a specific driver or application, or a hardware problem, making the resume fail.

Now, to be clear, I may have overlooked something above, so I ask:

In your log output posted above, was there a suspend done anytime during that period of logging? Did you have any of the debugging lines uncommented in the script? If so, then I was wrong above about where I said you'll see stuff in the log even with debugging not turned on; I thought we would still get *some* output from the kernel..

If that data you showed was from a timeframe when a suspend happened (successfully or otherwise), AND you DID have one of the debug lines in the script uncommented, then as we can see, there's no record of any suspend in that log, therefore, you WILL need to enable PM debugging if you want to see it all in the log (which means rebuild the kernel).

But, if you did NOT suspend the machine during the time of that logging, then in order to look for signs of trouble with the failed resumes, you need to enable debug in the script, and do a suspend. Then upon resume (or if resume fails, upon reboot) you examine the log and see what went wrong.


So:

0) enable a debug line in the script.
1) Note the time of day on your machine.
2) Hit your suspend button or whatever.
3) resume the machine. Note the time again.
4) Examine the log, between the time you suspended, till the time it was back up & running.
 
Old 01-10-2011, 01:04 PM   #69
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
Quote:
The debugging can help figure out if it's the kernel, or a specific driver or application, or a hardware problem, making the resume fail.
I will try the recompilation and see if debugging mode helps to narrow down the issue. Since the beginning of that machine, I have suspicions that the RAM might be bad. I checked with memtest86+ and no errors, but...

Quote:
In your log output posted above, was there a suspend done anytime during that period of logging?
yes, just before. When I activated the suspend script, the machine went to sleep (actually halted) and created this kernel log file. Before I activated the suspend script, this kernel lof file was not existing. The last line (the most invasive => core) was uncommented.

So I guess I need recompilation of the kernel. Now this brings me a few more questions:

1-I need to re-install my lirc modules (they are gone missing and I dont know why!) and have the lirc drivers source files. If I recompile & reinstall these modules, should I do that BEFORE I recompile the kernel or after?

2-Should I backup and How should I backup before I attempt such critical procedure?

3-What about the modules that I installed AFTER the slackware installation (the infamous saa7164 & tveeprom, the nvidia modules, etc)??

I might put this machine in a museum by the time it is done..
 
Old 01-10-2011, 05:00 PM   #70
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by lpallard View Post
...Now this brings me a few more questions:

1-I need to re-install my lirc modules (they are gone missing and I dont know why!) and have the lirc drivers source files. If I recompile & reinstall these modules, should I do that BEFORE I recompile the kernel or after?
After you rebuild the kernel.
Quote:
2-Should I backup and How should I backup before I attempt such critical procedure?
A backup is always wise to have, whether you're about to rebuild your kernel, or at any other time - always have a backup. Now, specifically in preparation for building your kernel, there's no need to make a backup just for this. You should have a backup(s) around anyways, just because you're smart and keep regular backups.
Quote:
3-What about the modules that I installed AFTER the slackware installation (the infamous saa7164 & tveeprom, the nvidia modules, etc)??
Again, do this after you build the kernel. Any modules or drivers that are not part of the kernel source tree, such as nvidia for example, will always need to be rebuilt for your new kernel.
Quote:
I might put this machine in a museum by the time it is done..
Cool I will like to see it!
 
Old 01-12-2011, 06:48 PM   #71
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
Quote:
Cool I will like to see it!
Never said Id put the machine intact in the museum... !

Due to sound issues with my GT430, I will need to upgrade my kernel, confirmed by nvidia. I was looking at the kernel.org site and latest stable is 2.6.37

Would you see any problems upgrading to this release? is it too recent? any pitfalls I should know but most importantly, how do you know if there is?

So lets say I upgrade to 2.6.37, every time I play around with kernel upgrades I am always sitting down in front of the menuconfig or gconfig utility for hours to configure the options and adjust the parameters to optimize.... What are you doing to speed up or optimize the options before you start the compilation?

Re-compiling a brand new kernel, might as well optimize the settings for my specific hardware...

Also should I treat the drivers as modules or integrate them in the kernel?

Last edited by lpallard; 01-12-2011 at 06:51 PM.
 
Old 01-13-2011, 10:09 AM   #72
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551Reputation: 551
Quote:
Originally Posted by lpallard View Post
Due to sound issues with my GT430, I will need to upgrade my kernel, confirmed by nvidia. I was looking at the kernel.org site and latest stable is 2.6.37

Would you see any problems upgrading to this release? is it too recent? any pitfalls I should know but most importantly, how do you know if there is?
Well, whatever is the latest stable release on kernel.org is never too recent for me, and I usually run the latest or close to it. Other folks have their own reasons for staying a ways behind the latest, or for avoiding fresh major number versions until the first minor bugfix version is released (that'd be 2.6.37.1 in this case).
Pitfalls? I can't say - best thing you can do is read the ChangeLog that is released accompanying every kernel release, and decide for yourself if there are potential pitfalls to a particular version. However, understanding enough of what you ought to understand before delving into this sort of discussion, is not something you'll glean from reading a changelog or two; kernel development is happening around the clock, every day, so unless you've been following particular aspects of it, a single changelog or two, or even a dozen, won't really learn you anything much.. If you need a newer kernel version for some compelling reason, such as you need a driver that is in a newer version, then great - recompile for that reason while leaving the remainder of the kernel as it is - don't try to understand everything else possible about the kernel, nor try to "get fancy" nor "let's see what this does" or you'll end up wasting a load of your time, and possibly get a broken kernel.
Quote:
So lets say I upgrade to 2.6.37, every time I play around with kernel upgrades I am always sitting down in front of the menuconfig or gconfig utility for hours to configure the options and adjust the parameters to optimize.... What are you doing to speed up or optimize the options before you start the compilation?
Yes, the first few times I did it, I took 3+ hours going through EVERYTHING, reading and Googling and whatnot. However, once you have a routine (as I do now) you could rebuild your kernel to make some particular change or two, in a very short time - something like 15 or 20 minutes (depending how fast your machine can compile the new kernel once you've made your change(s) and saved the config file) and you are ready to reboot.
The key to getting a starting point for each build, is to begin with your existing kernel's configuration file. In short - unless you are experimenting, or playing around just to learn & fiddle, there's no reason to configure the whole entire kernel from scratch every time.
Your existing kernel's config file is stored in one or more of several places. One easy way to grab it is like so:
Code:
root# zcat /proc/config.gz > /path/to/my_default_config_file
What does that do? Your kernel has a copy of its own config file, built into itself. It is gzip-compressed, and stored in the virtual file /proc/config.gz so the command I give above, will uncompress and cat the file, creating a new file uncompressed, called my_default_config_file or whatever you call it. Save the file in your kernel sources folder. Now, when you fire up menuconfig or xconfig or whatever you use, you will load that file as a starting point. Then make your small changes, save the file as a new name, and build your new kernel using that file. NOTE that the final filename MUST BE ".config", and saved in your kernel sources, for the kernel to find the file and use it. Any other name and it will not be found.

If you ultimately optimize your kernel for your hardware, and/or make a load of other changes, than make sure you keep saving your config files with names you understand, so that next time you want to start from that point, you know what file to load and start with.
Quote:

Also should I treat the drivers as modules or integrate them in the kernel?
That's up to you, but: you MUST build in (integrate) your module for your disk controller and for the root filesystem type you use (or use an initrd, an "initial randisk" which contains stuff the kernel needs to boot & start loading the OS), or your kernel won't be able to read your root filesystem when it boots. Most or all other modules you can make your own decision whether to integrate it or make it a module - there are arguments for both methods, and it's up to you which you choose. You'll maybe want to research a little bit the difference between modular or statically compiled kernel modules, and decide which is best for you for a particular module.

Please allow me to suggest again that if you want to discuss the kernel recompilation subject in detail, and/or you need answers and haven't found them elsewhere, then it would be a good idea to make a dedicated thread for it where we can help you without risking taking this thread too far off track from the suspend issues, into compilation of the kernel; it's not a tiny subject, so a new thread will provide the space to talk, while staying on topic.

Kind regards & good luck!
 
Old 01-13-2011, 11:16 PM   #73
lpallard
Member
 
Registered: Nov 2008
Posts: 987

Original Poster
Rep: Reputation: Disabled
Ok good news! (FINALLY!!)

I upgraded kernel to 2.6.37 and all went fine. Installed all drivers and basically back to normal, except I notice a large performance improvement. Its overall more responsive and fluid...

Anyways, I activated the suspend debug flags in the .config file and attached is my /var/log/kernel log file. The file was originally too long. I deleted the log, issued the suspend command, and the machine halted (it was still running but no sound no images..) and I reset the machine and got whats in the attached log.

Let me know what you think or wanna try!

Thanks!!!
Attached Files
File Type: log kernel.log (90.8 KB, 6 views)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problems after resuming from suspend to ram chessonly Linux - General 1 08-10-2012 08:55 AM
Plz explain Suspend to Disk and Suspend to Ram pkhera_2001 Linux - Newbie 2 02-18-2008 08:23 AM
Suspend to RAM problems broxtor Ubuntu 0 03-31-2007 03:40 AM
How to suspend to ram ? I have problems. gkiagia Linux - Laptop and Netbook 3 09-09-2006 04:45 AM
modem usability problems after starting from "suspend to RAM" pusrob Linux - Networking 1 06-17-2006 03:54 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:53 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration