| View previous topic :: View next topic |
| Author |
Message |
martin.k
Guru
Joined: 28 Nov 2004
Posts: 493
Location: Wylatowo, Polska
|
 Posted: Thu Mar 01, 2007 8:55 pm Post subject: |
 |
|
Thanx 
Works fine here with latest RSDL enabled 
Done some testing with apache2/mysql combo... Works stable...
Quite fast... But I'm not sure if viper4 is faster than my default kernel -> 2.6.17-emission8
_________________
linux-2.6.17 +ck +R4 +lockless +genetic-as +... więcej nie pamiętam
LRU #299256 |
|
| Back to top |
|
 |
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Thu Mar 01, 2007 10:31 pm Post subject: |
|
|
| martin.k wrote: | Thanx
Works fine here with latest RSDL enabled
Done some testing with apache2/mysql combo... Works stable...
Quite fast... But I'm not sure if viper4 is faster than my default kernel -> 2.6.17-emission8 |
Yeah, that will be a hard one to beat for quite a while.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
ElEmperador
n00b
Joined: 08 Mar 2006
Posts: 24
|
| Posted: Fri Mar 02, 2007 2:22 am Post subject: |
|
|
hi
I've tried with RSDL, aplying the lastest patch, and all worked fine, but when I recompiled the kernel with Ingo or Starcaise, this gave me a error(I forget copy the error, sorry) and I couldn't finish. Re-emering the viper-sources, I fix the problem. Then, the patches for RSDL broken the Ingo and Starcaise compilation (for me). Are there somebody with the same problem?.
thank. (excuse my poor english) |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Fri Mar 02, 2007 5:06 am Post subject: |
|
|
| ElEmperador wrote: | hi
I've tried with RSDL, aplying the lastest patch, and all worked fine, but when I recompiled the kernel with Ingo or Starcaise, this gave me a error(I forget copy the error, sorry) and I couldn't finish. Re-emering the viper-sources, I fix the problem. Then, the patches for RSDL broken the Ingo and Starcaise compilation (for me). Are there somebody with the same problem?.
thank. (excuse my poor english) |
Try removing the kernel tree and re emerging.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
santaclaws
Apprentice
Joined: 05 Jan 2007
Posts: 161
Location: Deeper Underground
|
| Posted: Fri Mar 02, 2007 8:19 am Post subject: |
|
|
Hi Vipernicus - viper4 kernel works great! Very fast.
| Code: |
localhost santaclaws # uname -a
Linux localhost 2.6.20-viper4 #1 PREEMPT Thu Mar 1 10:28:13 CET 2007 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
|
But the cut-off dmesg problem still remains.. it is stangely only with the viper4 kernel 
| Code: |
localhost santaclaws # dmesg
ux-kernel to fix this permanently
PCI: Bus #06 (-#09) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs *9)
(..)
|
Any hint?
_________________
Software is like sex. It is better when ist is free. |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
| Posted: Fri Mar 02, 2007 8:25 am Post subject: |
|
|
got it too, but it doesn't seem to affect system stability negatively:
| Quote: | dmesg | grep Interr
[ 0.096836] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.098787] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
[ 0.099024] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT]
[ 0.099256] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
[ 0.099742] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT]
[ 0.099969] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P8._PRT]
[ 0.103658] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.103880] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15)
[ 0.104073] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 11 12 14 15)
[ 0.104266] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 *11 12 14 15)
[ 0.104459] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 10 11 12 14 15)
[ 0.104653] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 *10 11 12 14 15)
[ 0.104874] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
[ 0.105071] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 *4 5 6 7 10 11 12 14 15)
[ 0.118353] ACPI: PCI Interrupt 0000:01:03.0[A] -> GSI 21 (level, low) -> IRQ 16
[ 0.168572] ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 17
[ 0.168589] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 17
[ 0.168634] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18
[ 0.168652] ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 16 (level, low) -> IRQ 17
[ 0.312125] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 23 (level, low) -> IRQ 19
[ 3.625046] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 22 (level, low) -> IRQ 20
[ 4.558724] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 19 (level, low) -> IRQ 18
[ 8.831839] ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 23 (level, low) -> IRQ 19
[ 8.850126] ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 20 (level, low) -> IRQ 21
[ 8.996445] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 20 (level, low) -> IRQ 21
[ 9.098856] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 17 (level, low) -> IRQ 22
[ 9.200728] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 23
[ 9.302347] ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 19 (level, low) -> IRQ 18
[ 9.404220] ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 19 (level, low) -> IRQ 18
[ 9.404355] ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 17
[ 9.404528] ACPI: PCI Interrupt 0000:01:00.1[A] -> GSI 21 (level, low) -> IRQ 16
[ 9.562665] ACPI: PCI Interrupt 0000:01:00.2[A] -> GSI 21 (level, low) -> IRQ 16
[ 9.562756] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 21 (level, low) -> IRQ 16
[ 9.641444] ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 17
|
- snip -
| Quote: | [ 0.081280] ACPI: bus type pci registered
[ 0.081287] PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
[ 0.081289] PCI: Not using MMCONFIG.
[ 0.081419] PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=5
[ 0.081422] PCI: Using configuration type 1
[ 0.081424] Setting up standard PCI resources
[ 0.094620] ACPI: Interpreter enabled
[ 0.094623] ACPI: Using IOAPIC for interrupt routing
[ 0.095379] ACPI: PCI Root Bridge [PCI0] (0000:00)
[ 0.095385] PCI: Probing PCI hardware (bus 00)
[ 0.095959] PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
[ 0.095964] PCI quirk: region 0480-04bf claimed by ICH6 GPIO
[ 0.096145] Boot video device is 0000:05:00.0
[ 0.096785] PCI: Transparent bridge - 0000:00:1e.0
[ 0.096836] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
|
- snip -
- snap -
| Quote: | [ 0.168497] PCI: Bridge: 0000:00:01.0
[ 0.168500] IO window: c000-cfff
[ 0.168503] MEM window: ebe00000-efefffff
[ 0.168506] PREFETCH window: c3a00000-e39fffff
[ 0.168509] PCI: Bridge: 0000:00:1c.0
[ 0.168511] IO window: disabled.
[ 0.168515] MEM window: disabled.
[ 0.168519] PREFETCH window: c3900000-c39fffff
[ 0.168523] PCI: Bridge: 0000:00:1c.3
[ 0.168526] IO window: b000-bfff
[ 0.168530] MEM window: ebd00000-ebdfffff
[ 0.168533] PREFETCH window: disabled.
[ 0.168537] PCI: Bridge: 0000:00:1c.4
[ 0.168540] IO window: a000-afff
[ 0.168544] MEM window: ebc00000-ebcfffff
[ 0.168548] PREFETCH window: disabled.
[ 0.168552] PCI: Bridge: 0000:00:1e.0
[ 0.168554] IO window: disabled.
[ 0.168558] MEM window: e3b00000-ebbfffff
[ 0.168562] PREFETCH window: disabled.
|
- snap -
| Quote: | 0.168572] ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 17
0.168577] PCI: Setting latency timer of device 0000:00:01.0 to 64
0.168589] ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 17
0.168620] PCI: Setting latency timer of device 0000:00:1c.0 to 64
0.168634] ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 19 (level, low) -> IRQ 18
0.168639] PCI: Setting latency timer of device 0000:00:1c.3 to 64
0.168652] ACPI: PCI Interrupt 0000:00:1c.4[A] -> GSI 16 (level, low) -> IRQ 17
0.168657] PCI: Setting latency timer of device 0000:00:1c.4 to 64
0.168665] PCI: Setting latency timer of device 0000:00:1e.0 to 64
|
sorry for spamming this thread, I just thought this were the important parts, so you can faster diagnose what's wrong ...
_________________
https://github.com/kernelOfTruth/ZFS-for-SystemRescueCD/tree/ZFS-for-SysRescCD-4.9.0
https://github.com/kernelOfTruth/pulseaudio-equalizer-ladspa
Hardcore Gentoo Linux user since 2004  |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
|
| Back to top |
|
|
mbar
Veteran
Joined: 19 Jan 2005
Posts: 1990
Location: Poland
|
| Posted: Sat Mar 03, 2007 8:04 am Post subject: |
|
|
| Yep, I used to use SPA_WS during .17 or .18 series and now I returned to it on my lappy. |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
bollucks
l33t
Joined: 27 Oct 2004
Posts: 606
|
| Posted: Sun Mar 04, 2007 11:56 pm Post subject: |
|
|
This code update would only make a difference on the alpha architecture. |
|
| Back to top |
|
|
kernelOfTruth
Watchman
Joined: 20 Dec 2005
Posts: 6111
Location: Vienna, Austria; Germany; hello world :)
|
|
| Back to top |
|
|
Phlogiston
Veteran
Joined: 27 Jan 2004
Posts: 1925
Location: Europe, Swizerland
|
| Posted: Wed Mar 07, 2007 8:57 am Post subject: |
|
|
Hey vipernicus, I'm still having that suspend2 resume issue. It happens suddenly after about 4 to 7 success hibernates/resumes. I get a kernel panic at boot.
Look the picture here: http://img223.imageshack.us/my.php?image=img8592nf5.jpg
_________________
Workstation: 5.1 SurroundSound, LIRC remote control; Laptop [IBM-T43]: patched sources, s2disk/ram, fingerprint sensor |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
|
| Back to top |
|
|
kEiNsTeiN
Guru
Joined: 29 Apr 2005
Posts: 361
Location: Germany
|
| Posted: Sat Mar 10, 2007 9:03 pm Post subject: |
|
|
I have a problem, I dont know if it's related to Viper4, or to kernel 2.6.20 in general:
USB-Devices are not labeled properly, i.e. USB-Pen-Drives are recognized as "removable media", but external harddrives aren't.
So HAL cannot find them, or at least it doesnt initiiate the scripts to tell KDE that there's something new. So in consequence, I cannot see my external harddrives in KDE, neither as removable media, nor as unmounted fixed harddrives.
See this post for more about the problem. And sorry for the double-post, I didnt feel anyone saw the other one....
Here's my config: http://illhostit.com/files/e46105b3d9b53fe95e3fbc4ab2c8811c/linux-2.6.20-viper4.txt
and here one it last worked with: http://illhostit.com/files/231ec150d1fb3a8af81dfd0812b23438/linux-2.6.18-emission1.txt
thanks for any help.... |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
|
| Back to top |
|
|
kEiNsTeiN
Guru
Joined: 29 Apr 2005
Posts: 361
Location: Germany
|
| Posted: Sun Mar 11, 2007 12:42 am Post subject: |
|
|
I have hal-0.5.7.1-r5, the most recent one. And I dont have it in fstab, as it would be stupid to do so 
It's definately not a hal issue, at least not for its own. Maybe it's a hal-version in combination with 2.6.20, since the device IS recognised, just not the way hal wants it to be. So my extended hypothesis: hal uses some deprecated way to figure out how removable something is, and that got removed in 2.6.20, so hal needs to be patched to the new way... but thats just random thaught |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Sun Mar 11, 2007 1:01 am Post subject: |
|
|
| kEiNsTeiN wrote: | I have hal-0.5.7.1-r5, the most recent one. And I dont have it in fstab, as it would be stupid to do so
It's definately not a hal issue, at least not for its own. Maybe it's a hal-version in combination with 2.6.20, since the device IS recognised, just not the way hal wants it to be. So my extended hypothesis: hal uses some deprecated way to figure out how removable something is, and that got removed in 2.6.20, so hal needs to be patched to the new way... but thats just random thaught |
What makes your think it is hal and not udev? Is the device created in /dev?
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
HecHacker1
Apprentice
Joined: 26 Jun 2003
Posts: 213
Location: UCSD
|
| Posted: Sun Mar 11, 2007 1:46 am Post subject: |
|
|
I just applied the RSDL patch .28, and now my system wont boot. It hangs when it says uncompressing the kernel. I was running fine with .25.
EDIT: just realized I have my boot quiet in grub, I will uncomment and see where it hangs.
EDIT2: http://bhhdoa.org.au/pipermail/ck/2007-March/ there seems to be a patch for .28
EDIT3: nevermind.. i plug out the power cord on my laptop, and it boots fine! Going back to .28. Something is buggy here.
EDIT4: .28 works fine after all. I just have a weird bug where the kernel panics if I have the laptop plugged in during boot.
Last edited by HecHacker1 on Sun Mar 11, 2007 2:14 am; edited 2 times in total |
|
| Back to top |
|
|
kEiNsTeiN
Guru
Joined: 29 Apr 2005
Posts: 361
Location: Germany
|
| Posted: Sun Mar 11, 2007 1:58 am Post subject: |
|
|
hmm... yeah... could be udev or dbus, too
yes, it's created in /dev. udev rules work too, but problem persists if I remove the rule for the external harddrives... |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Sun Mar 11, 2007 3:06 am Post subject: |
|
|
I'm working on -viper5, based on 2.6.20.2. Will be adding hrt-dynticks, ext4 updates from -mm, and tunables for rsdl like I have for staircase. Now would be a good time for requests.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
HecHacker1
Apprentice
Joined: 26 Jun 2003
Posts: 213
Location: UCSD
|
| Posted: Sun Mar 11, 2007 4:50 am Post subject: |
|
|
| vipernicus wrote: | | I'm working on -viper5, based on 2.6.20.2. Will be adding hrt-dynticks, ext4 updates from -mm, and tunables for rsdl like I have for staircase. Now would be a good time for requests. |
any suspend2 fixes? I randomly get kernel panics when resuming. Sometimes hibernate works and i can come right back to my desktop.. and yet sometimes it just crashes. No changes to the config. It would seem that the longer it hibernates, the greater likelihood it won't resume and panic.
Perhaps RSDL is causing the problem? (although the rest of my system is perfectly stable with rsdl atm)
EDIT1: CK just released .29 on his server, no official announcement yet. Are your patches the same as his? Or do you have to change something to apply it to your kernel?
Last edited by HecHacker1 on Sun Mar 11, 2007 10:12 am; edited 2 times in total |
|
| Back to top |
|
|
vipernicus
Veteran
Joined: 17 Jan 2005
Posts: 1462
Location: Your College IT Dept.
|
| Posted: Sun Mar 11, 2007 5:01 am Post subject: |
|
|
| HecHacker1 wrote: | | vipernicus wrote: | | I'm working on -viper5, based on 2.6.20.2. Will be adding hrt-dynticks, ext4 updates from -mm, and tunables for rsdl like I have for staircase. Now would be a good time for requests. |
any suspend2 fixes? I randomly get kernel panics when resuming. Sometime hibernate works and i can come right back to my desktop.. and yet sometimes it just crashes. No changes to the config. It would seem that the longer it hibernates, the greater likelihood it won't resume and panic.
Perhaps RSDL is causing the problem? (although the rest of my system is perfectly stable with rsdl atm) |
Possibly, there was a resume bug with sdhci that I'm merging from -mm.
_________________
Viper-Sources Maintainer || nesl247 Projects || vipernicus.org blog |
|
| Back to top |
|
|
bigbob73
Guru
Joined: 31 Dec 2004
Posts: 332
Location: Under the Lone Star
|
| Posted: Sun Mar 11, 2007 1:48 pm Post subject: |
|
|
| vipernicus wrote: | | I'm working on -viper5, based on 2.6.20.2. Will be adding hrt-dynticks, ext4 updates from -mm, and tunables for rsdl like I have for staircase. Now would be a good time for requests. |
Tunables for sure!
_________________
A computers attention span is only as long as it's electrical cord (Murphy) |
|
| Back to top |
|
|
Phlogiston
Veteran
Joined: 27 Jan 2004
Posts: 1925
Location: Europe, Swizerland
|
| Posted: Sun Mar 11, 2007 1:51 pm Post subject: |
|
|
| HecHacker1 wrote: |
any suspend2 fixes? I randomly get kernel panics when resuming. Sometimes hibernate works and i can come right back to my desktop.. and yet sometimes it just crashes. No changes to the config. It would seem that the longer it hibernates, the greater likelihood it won't resume and panic.
Perhaps RSDL is causing the problem? (although the rest of my system is perfectly stable with rsdl atm)
|
I'm having the same resuming problem! As you can read in my post above, I provided a screenshot too. By the way I'm not using rsdl.
Viper could you please have a look at that?
_________________
Workstation: 5.1 SurroundSound, LIRC remote control; Laptop [IBM-T43]: patched sources, s2disk/ram, fingerprint sensor |
|
| Back to top |
|
|
|
Unsupported Software
