Menu
▾
▴
linuxconsole-dev
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
(235) |
Apr
(30) |
May
(32) |
Jun
(86) |
Jul
(81) |
Aug
(108) |
Sep
(27) |
Oct
(22) |
Nov
(34) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(78) |
Feb
(10) |
Mar
(81) |
Apr
(27) |
May
(13) |
Jun
(105) |
Jul
(78) |
Aug
(52) |
Sep
(59) |
Oct
(90) |
Nov
(127) |
Dec
(49) |
| 2002 |
Jan
(102) |
Feb
(72) |
Mar
(54) |
Apr
(98) |
May
(25) |
Jun
(23) |
Jul
(123) |
Aug
(14) |
Sep
(52) |
Oct
(65) |
Nov
(48) |
Dec
(48) |
| 2003 |
Jan
(22) |
Feb
(25) |
Mar
(29) |
Apr
(12) |
May
(16) |
Jun
(11) |
Jul
(20) |
Aug
(20) |
Sep
(43) |
Oct
(84) |
Nov
(98) |
Dec
(56) |
| 2004 |
Jan
(28) |
Feb
(39) |
Mar
(41) |
Apr
(28) |
May
(88) |
Jun
(17) |
Jul
(43) |
Aug
(57) |
Sep
(54) |
Oct
(42) |
Nov
(32) |
Dec
(58) |
| 2005 |
Jan
(80) |
Feb
(31) |
Mar
(65) |
Apr
(41) |
May
(20) |
Jun
(34) |
Jul
(62) |
Aug
(73) |
Sep
(81) |
Oct
(48) |
Nov
(57) |
Dec
(57) |
| 2006 |
Jan
(63) |
Feb
(24) |
Mar
(18) |
Apr
(9) |
May
(22) |
Jun
(29) |
Jul
(47) |
Aug
(11) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Hugo V. <hvw...@ya...> - 2004-12-24 20:03:29
|
--- Aivils <ai...@un...> wrote: > On Friday 24 December 2004 01:04, Hugo Vanwoerkom > wrote: > > Hi! <snip> > > No. 2.4.XX ruby is totaly freezy. > Someone should edit this lines > decvte.c:1107: > kd_mksound(vc->display_fg->keyboard, bell_pitch, > bell_duration); > vt_ioctl.c:697: > kd_mksound(vc->display_fg->keyboard, arg, 0); > vt_ioctl.c:714: > kd_mksound(vc->display_fg->keyboard, count, ticks); > > Relace vc->display_fg->keyboard with > vc->display_fg->beeper > There are some beauty blemishes: I used to be able to give a bell-duration of 1 and get a "tick". That now does nothing. When I change it to a 10, I get a short "beep" which is not the idea. Also exiting from the window-manager to gdm turns on the beeper and never turns it off. Hugo > I cannot recall how correct works VGA under 2.4.XX, > because > it stay unused in my end. > > Aivils > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail |
|
From: Hugo V. <hvw...@ya...> - 2004-12-24 18:22:40
|
--- Aivils <ai...@un...> wrote: > On Friday 24 December 2004 01:04, Hugo Vanwoerkom > wrote: <snip> > > No. 2.4.XX ruby is totaly freezy. > Someone should edit this lines > decvte.c:1107: > kd_mksound(vc->display_fg->keyboard, bell_pitch, > bell_duration); > vt_ioctl.c:697: > kd_mksound(vc->display_fg->keyboard, arg, 0); > vt_ioctl.c:714: > kd_mksound(vc->display_fg->keyboard, count, ticks); > > Relace vc->display_fg->keyboard with > vc->display_fg->beeper > And it works! Got a beeper again! Thanks! Hugo > I cannot recall how correct works VGA under 2.4.XX, > because > it stay unused in my end. > > Aivils > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > __________________________________ Do you Yahoo!? Send holiday email and support a worthy cause. Do good. http://celebrity.mail.yahoo.com |
|
From: Hugo V. <hvw...@ya...> - 2004-12-24 17:23:05
|
Hi Team! Yesterday I was watching the one video I watch on xine, The Pianist, on the secondary PCI MX-440 monitor. And I noticed that xine was not complaining the system was too slow! Googling I found this: http://groups.google.com.au/groups?hl=en&lr=&selm=34eU2-fv-17%40gated-at.bofh.it (on the still sane google!) Sure enough: modifying wmcpuload to log its results, which calculates the total CPU load, I get: 2.6.9 2.4.29 09:28:04 CPU=85% 09:20:15 CPU=48%...........-37% 09:28:05 CPU=84% 09:20:16 CPU=48% ...........-36% 09:28:06 CPU=84% 09:20:17 CPU=47%...........-37% 09:28:07 CPU=83% 09:20:18 CPU=51%...........-32% 09:28:08 CPU=85% 09:20:19 CPU=52%...........-33% 09:28:09 CPU=83% 09:20:20 CPU=53%...........-30% 09:28:10 CPU=89% 09:20:21 CPU=61%...........-28% 09:28:11 CPU=96% 09:20:22 CPU=61%...........-35% 09:28:12 CPU=93% 09:20:23 CPU=63%...........-30% 09:28:13 CPU=92% 09:20:24 CPU=62%...........-30% 09:28:14 CPU=88% 09:20:25 CPU=63%...........-25% 09:28:15 CPU=89% 09:20:26 CPU=62%...........-27% 09:28:16 CPU=88% 09:20:27 CPU=60%...........-28% 09:28:17 CPU=89% 09:20:28 CPU=62%...........-27% 09:28:18 CPU=88% 09:20:29 CPU=63%...........-25% 09:28:19 CPU=93% 09:20:30 CPU=63%...........-30% 09:28:20 CPU=91% 09:20:31 CPU=61%...........-30% 09:28:21 CPU=90% 09:20:32 CPU=61%...........-29% 09:28:22 CPU=87% 09:20:33 CPU=61%...........-26% 09:28:23 CPU=91% 09:20:34 CPU=63%...........-28% 09:28:24 CPU=87% 09:20:35 CPU=61%...........-26% 09:28:25 CPU=90% 09:20:36 CPU=62%...........-28% 09:28:26 CPU=91% 09:20:37 CPU=63%...........-28% 09:28:27 CPU=91% 09:20:38 CPU=63%...........-28% 09:28:28 CPU=93% 09:20:39 CPU=60%...........-33% 09:28:29 CPU=92% 09:20:40 CPU=61%...........-31% 09:28:30 CPU=89% 09:20:41 CPU=61%...........-28% 09:28:31 CPU=89% 09:20:42 CPU=63%...........-26% 09:28:32 CPU=91% 09:20:43 CPU=62%...........-29% 09:28:33 CPU=92% 09:20:44 CPU=62%...........-30% 09:28:34 CPU=92% 09:20:45 CPU=61%...........-31% 09:28:35 CPU=94% 09:20:46 CPU=64%...........-30% 09:28:36 CPU=94% 09:20:47 CPU=62%...........-32% An average of 30% less CPU load on 2.4.29! This is all the same: Debian Sarge, nothing running but xine, except for the kernel differences! Hugo. __________________________________ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 |
|
From: Aivils <ai...@un...> - 2004-12-24 10:53:50
|
On Friday 24 December 2004 01:04, Hugo Vanwoerkom wrote: > Hi! > > Since I started using bruby and 2.4.x the speaker > never worked. > > Then I switched to ruby and 2.6.9 and by turning on > pcspkr and loading the module, the speaker worked. > > Now with 2.4.29 I find the kernel code there to use > pcspkr as a module (probably was in earlier kernels > too) but loading pcspkr produces not a beep. > > Anybody has a pcspeaker working with 2.4.x? And how > did they do it? No. 2.4.XX ruby is totaly freezy. Someone should edit this lines decvte.c:1107: kd_mksound(vc->display_fg->keyboard, bell_pitch, bell_duration); vt_ioctl.c:697: kd_mksound(vc->display_fg->keyboard, arg, 0); vt_ioctl.c:714: kd_mksound(vc->display_fg->keyboard, count, ticks); Relace vc->display_fg->keyboard with vc->display_fg->beeper I cannot recall how correct works VGA under 2.4.XX, because it stay unused in my end. Aivils |
|
From: Hugo V. <hvw...@ya...> - 2004-12-23 23:04:29
|
Hi! Since I started using bruby and 2.4.x the speaker never worked. Then I switched to ruby and 2.6.9 and by turning on pcspkr and loading the module, the speaker worked. Now with 2.4.29 I find the kernel code there to use pcspkr as a module (probably was in earlier kernels too) but loading pcspkr produces not a beep. Anybody has a pcspeaker working with 2.4.x? And how did they do it? I can program the speaker timewise but not frequency-wise, for some reason. Hugo __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com |
|
From: Aivils <ai...@un...> - 2004-12-22 10:49:50
|
On Wednesday 22 December 2004 06:06, James van Zeeland wrote: > The only machine I've got dual head gaming running well on is a Dual > 2800+ AthlonMP box. > > A 2.4Ghz P4 gets all choppy with Quake3; unplayable. Tuxracer works well > with both consoles on this box though. > > These are all 2.6 Should run with command nice -n 19 game-bin +19 nice value tell kernel use only 10msec timeslices for that process. This trick will return back Linux native games, but is useless for Winex. By default 2.6.XX will use 100msec timeslice for each process, which value is not acceptable for gamers. > re: schedulers -- I would be interested in running a direct kernel > comparison. > Numbers and real testing rather than just observation has a lot of > merit. > I am very happy with current 2.6 kernel, and observed real improvements > under RH9 over 2.4 kernels, but don't really know what benchtest numbers > would say, because I haven't done any. > > I have an RH9 box that should still take 2.4 kernels fine, to keep the > hardware identical... > > Perhaps someone can point me at a resource for this kind of > benchtesting/comparison? > benchtesting does not exist (or exist?). Trouble is "how even CPU is distributed between tasks in short time (20-30msec)". Unfortunately i have not ideas test subject without interference from tester. 20msec means 50 Hz - this is very subjective value. Someone can feel game screen update from 50 Hz someone from 10 Hz and lower rate. Another troble - single game runs smooth, so developers reject my requests for help. > J > > > Thank You. I'm still under Your 2.4.27. > > > Mine dislikes 2.6.XX because of poor task scheduler. > > > > > > > Absolutely right. Forget gaming: I don't even run 2 > > users right. Perhaps a stronger CPU? I got only > > 850MHz. My Celeron 366 is capable run two tuxracers even, as video 2 x TNT2M64. Athlon 1600+ rocks 3 x Quake3. That is true under 2.4.XX and is wrong under 2.6.XX Aivils |
|
From: James v. Z. <ja...@dv...> - 2004-12-22 04:27:58
|
> I have one stable FC3 kernel tree/build. I am going to look closely at > it and see if I can find out what makes it stable because it's not an FC3 kernel tree, it was built from kernel.org 2.6.9 On Wed, 2004-12-22 at 13:50, James van Zeeland wrote: > > In my case oops oft (1 time per 24h) happens in the nvidia module. > > As result specific head dies until full system restart. > > re: GLX -- I also had such GLX issues with older Xorg on FC2; newest > update with 6629 driver solved them all for me. Days/weeks uptime with > recent ruby.vz kernels, play games, any console, all works, all stable! > Have been going from one kernel update to the next with no reset or > crash inbetween. > > >From my experiments I feel FC2 with most recent Xorg best for ruby > > FC3 is obviously another story : > > This is not a ruby problem either, as I tried removing ruby and kernel > remains unstable. It's a mystery. > > I have one stable FC3 kernel tree/build. I am going to look closely at > it and see if I can find out what makes it stable while five other FC3 > based kernels are unstable all with the same symptoms. > > I would need serial port debug output or crash dump patch to provide > debugging info, yes? I can't get to a console to see output. > > J > > http://members.westnet.com.au/vanzeeland > > > On Wed, 2004-12-22 at 00:22, Aivils wrote: > > On Tuesday 21 December 2004 14:08, James van Zeeland wrote: > > > Confirmed FC3 kernel issue. > > > > > > Compiling 32bit Athlon fc3 kernel with ruby patch results in an unstable > > > kernel that crashes inconsistently on launch of X. > > > > > Are You capable determine where oops happens? > > > > In my case oops oft (1 time per 24h) happens in the nvidia module. > > As result specific head dies until full system restart. Oops may never > > happen if GLX applications is not used :) Unfortunately in the my end > > GLX applications will be run everyday. Next head runs as nothig > > happened even if reman 1 head from 3. > > > > Aivils > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > Linuxconsole-dev mailing list > > Lin...@li... > > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > |
|
From: James v. Z. <ja...@dv...> - 2004-12-22 04:00:05
|
The only machine I've got dual head gaming running well on is a Dual 2800+ AthlonMP box. A 2.4Ghz P4 gets all choppy with Quake3; unplayable. Tuxracer works well with both consoles on this box though. These are all 2.6 re: schedulers -- I would be interested in running a direct kernel comparison. Numbers and real testing rather than just observation has a lot of merit. I am very happy with current 2.6 kernel, and observed real improvements under RH9 over 2.4 kernels, but don't really know what benchtest numbers would say, because I haven't done any. I have an RH9 box that should still take 2.4 kernels fine, to keep the hardware identical... Perhaps someone can point me at a resource for this kind of benchtesting/comparison? J On Wed, 2004-12-22 at 03:47, Hugo Vanwoerkom wrote: > --- Aivils <ai...@un...> wrote: > > > On Sunday 19 December 2004 19:18, Jean-Daniel Pauget > > wrote: > > > > > > as kernel 2.4.29 provides several interesting > > harware improvement, not to > > > say also some igmp security flawness > > corrections, I put a cosmetic > > > bruby patch targeted to 2.4.29-pre2 on my site > > : > > > > > > http://disjunkt.com.local/dualhead/ > > > > > > the patch itself : > > > > > > http://disjunkt.com.local/dualhead/bruby-2.4.29-pre2-20041217.bz2 > > > > Thank You. I'm still under Your 2.4.27. > > Mine dislikes 2.6.XX because of poor task scheduler. > > > > Absolutely right. Forget gaming: I don't even run 2 > users right. Perhaps a stronger CPU? I got only > 850MHz. > > H. > > > > > > > Aivils > > > > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide > > Read honest & candid reviews on hundreds of IT > > Products from real users. > > Discover which products truly live up to the hype. > > Start reading now. > > http://productguide.itmanagersjournal.com/ > > _______________________________________________ > > Linuxconsole-dev mailing list > > Lin...@li... > > > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - now with 250MB free storage. Learn more. > http://info.mail.yahoo.com/mail_250 > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > |
|
From: James v. Z. <ja...@dv...> - 2004-12-22 03:43:59
|
> In my case oops oft (1 time per 24h) happens in the nvidia module. > As result specific head dies until full system restart. re: GLX -- I also had such GLX issues with older Xorg on FC2; newest update with 6629 driver solved them all for me. Days/weeks uptime with recent ruby.vz kernels, play games, any console, all works, all stable! Have been going from one kernel update to the next with no reset or crash inbetween. >From my experiments I feel FC2 with most recent Xorg best for ruby FC3 is obviously another story : This is not a ruby problem either, as I tried removing ruby and kernel remains unstable. It's a mystery. I have one stable FC3 kernel tree/build. I am going to look closely at it and see if I can find out what makes it stable while five other FC3 based kernels are unstable all with the same symptoms. I would need serial port debug output or crash dump patch to provide debugging info, yes? I can't get to a console to see output. J http://members.westnet.com.au/vanzeeland On Wed, 2004-12-22 at 00:22, Aivils wrote: > On Tuesday 21 December 2004 14:08, James van Zeeland wrote: > > Confirmed FC3 kernel issue. > > > > Compiling 32bit Athlon fc3 kernel with ruby patch results in an unstable > > kernel that crashes inconsistently on launch of X. > > > Are You capable determine where oops happens? > > In my case oops oft (1 time per 24h) happens in the nvidia module. > As result specific head dies until full system restart. Oops may never > happen if GLX applications is not used :) Unfortunately in the my end > GLX applications will be run everyday. Next head runs as nothig > happened even if reman 1 head from 3. > > Aivils > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > |
|
From: Hugo V. <hvw...@ya...> - 2004-12-21 17:47:17
|
--- Aivils <ai...@un...> wrote: > On Sunday 19 December 2004 19:18, Jean-Daniel Pauget > wrote: > > > > as kernel 2.4.29 provides several interesting > harware improvement, not to > > say also some igmp security flawness > corrections, I put a cosmetic > > bruby patch targeted to 2.4.29-pre2 on my site > : > > > > http://disjunkt.com.local/dualhead/ > > > > the patch itself : > > > http://disjunkt.com.local/dualhead/bruby-2.4.29-pre2-20041217.bz2 > > Thank You. I'm still under Your 2.4.27. > Mine dislikes 2.6.XX because of poor task scheduler. > Absolutely right. Forget gaming: I don't even run 2 users right. Perhaps a stronger CPU? I got only 850MHz. H. > Aivils > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > __________________________________ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250 |
|
From: Hugo V. <hvw...@ya...> - 2004-12-21 14:16:15
|
--- Jean-Daniel Pauget <jd...@di...> wrote: > > as kernel 2.4.29 provides several interesting > harware improvement, not to > say also some igmp security flawness > corrections, I put a cosmetic > bruby patch targeted to 2.4.29-pre2 on my site : > > http://disjunkt.com.local/dualhead/ You meant: http://disjunkt.com/dualhead/ > > the patch itself : > > http://disjunkt.com.local/dualhead/bruby-2.4.29-pre2-20041217.bz2 and: http://disjunkt.com/dualhead/bruby-2.4.29-pre2-20041217.bz2 H. > > -- > Jean-Daniel Pauget > > Tél: +33 (0) 676 952 746 > 2, rue André PELCA > 50580 Denneville-Plage > France > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT > Products from real users. > Discover which products truly live up to the hype. > Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > __________________________________ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com |
|
From: Aivils <ai...@un...> - 2004-12-21 13:20:39
|
On Tuesday 21 December 2004 14:08, James van Zeeland wrote: > Confirmed FC3 kernel issue. > > Compiling 32bit Athlon fc3 kernel with ruby patch results in an unstable > kernel that crashes inconsistently on launch of X. > Are You capable determine where oops happens? In my case oops oft (1 time per 24h) happens in the nvidia module. As result specific head dies until full system restart. Oops may never happen if GLX applications is not used :) Unfortunately in the my end GLX applications will be run everyday. Next head runs as nothig happened even if reman 1 head from 3. Aivils |
|
From: Aivils <ai...@un...> - 2004-12-21 13:09:07
|
On Sunday 19 December 2004 19:18, Jean-Daniel Pauget wrote: > > as kernel 2.4.29 provides several interesting harware improvement, not to > say also some igmp security flawness corrections, I put a cosmetic > bruby patch targeted to 2.4.29-pre2 on my site : > > http://disjunkt.com.local/dualhead/ > > the patch itself : > http://disjunkt.com.local/dualhead/bruby-2.4.29-pre2-20041217.bz2 Thank You. I'm still under Your 2.4.27. Mine dislikes 2.6.XX because of poor task scheduler. Aivils |
|
From: James v. Z. <ja...@dv...> - 2004-12-21 12:01:26
|
Confirmed FC3 kernel issue. Compiling 32bit Athlon fc3 kernel with ruby patch results in an unstable kernel that crashes inconsistently on launch of X. This is duplicated using another standalone box without configuring multiple consoles, just installing ruby kernel only. What can I do to provide some debugging info? I shall test further to confirm ruby patch against fc3 kernel as source of issue. Anyone aware of FC3 quirks that might impact ruby? such as gcc3.4.2-6.fc3? recalling the inlining issue : One can't just patch vanilla 2.6.9 with ruby and expect it to compile under FC3, it will fail with inlining errors, as do a small handful of other modules. However, patch the FC3 kernel and it compiles, but does it compile correctly? Perhaps I should just wait for 2.6.10-ruby. J On Mon, 2004-12-20 at 12:00, James van Zeeland wrote: > Just not stable. (for me) > > Applying the same process that I've applied to rh9, fc1 and fc2, I have > not yet succeeded in producing a stable fc3 replica of an fc2 ruby > configuration. > > I have applied the ruby-2.6.9-20041021.diff to the latest fc3 kernel > tree. It applied and compiled cleanly. > > I have patched Xorg-6.8.1 most recent for fc3 with the mandrake > isolate_device patch. > > I have compiled the kernel and X both with cpu-specific (athlon) > optomizations, something I have done with every other ruby config that > is working here. > > I use nVidia cards exclusively, no TNT2 in service, all MX440, MX4000, > and FX5200. For this machine 1x FX5200, 2x MX440. > > Symptoms are as follows, under 6111 or 6629 nV drivers, the system will > boot but experience a kernel oops/panic not long after X has started. It > is not consistent. I might crash while starting an Xinimera session with > rhgb graphical boot, or it might complete boot, give me three login > prompts, and crash soon after. I can login on any console if it doesn't > crash first. > > If I don't start X, everything is stable. If I boot runlevel3 and start > X as Xinimera session, seems stable. I haven't done a long test of this, > but it doesn't lockup within seconds as it sometimes does with rhgb and > almost always does at runlevel 5 as gdm starts the consoles. > > I also applied the following correction hunk to ruby, just in case, > although discussion suggested x86-64 problem that doesn't impact 32-bit > units. Doesn't solve any problems for me. > > ------------------------------------------------------------------ > diff -Nurp --exclude-from=exclude linux-2.6.9/fs/compat_ioctl.c > r269/fs/compat_ioctl.c > --- linux-2.6.9/fs/compat_ioctl.c 2004-10-19 00:55:27.000000000 > +0300 > +++ r269/fs/compat_ioctl.c 2004-10-20 19:31:58.000000000 +0300 > @@ -1609,8 +1611,10 @@ static int do_fontx_ioctl(unsigned int f > get_user(data, &user_cfd->chardata)) > return -EFAULT; > op.data = compat_ptr(data); > - return con_font_op(fg_console, &op); > + return con_font_op(vc, &op); > case GIO_FONTX: > + if (!user_cfd->chardata) > + return 0; > op.op = KD_FONT_OP_GET; > op.flags = 0; > op.width = 8; > ------------------------------------------------------------------ > > I am currently suspecting Xorg to be unstable in this configuration, I > am wondering what success others have had with similar 32 bit FC3 > configurations. > > This same configuration was 100% stable under FC2 on the same machine. > > Should I double check my kernel config ?-- it has changed from fc2 to > fc3, now having less built in and more modular and based on the fc3 > kernel distribution. Should I avoid athlon optimizations? > > Are there any known issues that I might not be aware of that would > produce such behaviour? > > J > > http://members.westnet.com.au/vanzeeland > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > |
|
From: James v. Z. <ja...@dv...> - 2004-12-20 01:54:12
|
Just not stable. (for me)
Applying the same process that I've applied to rh9, fc1 and fc2, I have
not yet succeeded in producing a stable fc3 replica of an fc2 ruby
configuration.
I have applied the ruby-2.6.9-20041021.diff to the latest fc3 kernel
tree. It applied and compiled cleanly.
I have patched Xorg-6.8.1 most recent for fc3 with the mandrake
isolate_device patch.
I have compiled the kernel and X both with cpu-specific (athlon)
optomizations, something I have done with every other ruby config that
is working here.
I use nVidia cards exclusively, no TNT2 in service, all MX440, MX4000,
and FX5200. For this machine 1x FX5200, 2x MX440.
Symptoms are as follows, under 6111 or 6629 nV drivers, the system will
boot but experience a kernel oops/panic not long after X has started. It
is not consistent. I might crash while starting an Xinimera session with
rhgb graphical boot, or it might complete boot, give me three login
prompts, and crash soon after. I can login on any console if it doesn't
crash first.
If I don't start X, everything is stable. If I boot runlevel3 and start
X as Xinimera session, seems stable. I haven't done a long test of this,
but it doesn't lockup within seconds as it sometimes does with rhgb and
almost always does at runlevel 5 as gdm starts the consoles.
I also applied the following correction hunk to ruby, just in case,
although discussion suggested x86-64 problem that doesn't impact 32-bit
units. Doesn't solve any problems for me.
------------------------------------------------------------------
diff -Nurp --exclude-from=exclude linux-2.6.9/fs/compat_ioctl.c
r269/fs/compat_ioctl.c
--- linux-2.6.9/fs/compat_ioctl.c 2004-10-19 00:55:27.000000000
+0300
+++ r269/fs/compat_ioctl.c 2004-10-20 19:31:58.000000000 +0300
@@ -1609,8 +1611,10 @@ static int do_fontx_ioctl(unsigned int f
get_user(data, &user_cfd->chardata))
return -EFAULT;
op.data = compat_ptr(data);
- return con_font_op(fg_console, &op);
+ return con_font_op(vc, &op);
case GIO_FONTX:
+ if (!user_cfd->chardata)
+ return 0;
op.op = KD_FONT_OP_GET;
op.flags = 0;
op.width = 8;
------------------------------------------------------------------
I am currently suspecting Xorg to be unstable in this configuration, I
am wondering what success others have had with similar 32 bit FC3
configurations.
This same configuration was 100% stable under FC2 on the same machine.
Should I double check my kernel config ?-- it has changed from fc2 to
fc3, now having less built in and more modular and based on the fc3
kernel distribution. Should I avoid athlon optimizations?
Are there any known issues that I might not be aware of that would
produce such behaviour?
J
http://members.westnet.com.au/vanzeeland
|
|
From: Jean-Daniel P. <jd...@di...> - 2004-12-19 17:19:06
|
as kernel 2.4.29 provides several interesting harware improvement, not =
to
say also some igmp security flawness corrections, I put a cosmetic
bruby patch targeted to 2.4.29-pre2 on my site :
http://disjunkt.com.local/dualhead/
the patch itself :
http://disjunkt.com.local/dualhead/bruby-2.4.29-pre2-20041217.bz2
--
Jean-Daniel Pauget
T=E9l: +33 (0) 676 952 746
2, rue Andr=E9 PELCA
50580 Denneville-Plage
France
|
|
From: vineesh k. <vi...@hc...> - 2004-12-17 07:16:45
|
I saw ur 6 headed PC set up. can u send the hardware details?.
is ur setup supports independent speakers(ie, one speaker for each
user). If yes how can we accomplish the same.
regards
vineesh
On Mon, 2004-12-06 at 13:34, Aivils wrote:
> On Saturday 04 December 2004 19:09, Hugo Vanwoerkom wrote:
> >
> > --- Aivils <ai...@un...> wrote:
> >
> > > Hi All!
> > >
> > > X - X windows system
> > > K - Linux kernel
> > > E - Events as well
> > >
> > > INTRODUCTION
> > > ------------
> > >
> > > xke is userspace program which is capable read
> > > and recognize Linux
> > > kernel generated events of input devices. xke
> > > translate Linux kernel
> > > events and send to X windows system. Main goal is
> > > keyboar multimedia key
> > > utilization.
> >
> > <snip>
> >
> > Aivils, since nobody seemed to react to your note
> > which you certainly sent to enough places, some
> > questions. Keep in mind I am one of the clueless.
>
> I am not intoxicated by high technologies. Replay
> inside 30 days is good enough.
>
> > You wrote xke? Googling gets me foreign language
> > syntax and an automobile made by Jaguar.
>
> Yes i am author.
>
> > I read your report and it theoretically makes sense,
> > but practically what does it mean? I mean what can I
> > do with xke that I cannot do now with Ruby?
>
> As far as know actualy You are very consrevative and use
> onl IBM PS/2 keyboards. Nowadays we have keyboards with
> lots of additional , extented keys (me have 22 multimedia keys).
> During year 2000 one of this project administrator
> create Linux input event system. This event system
> up to this day is used very rarely by some Xfree86 drivers
> only. Exists keyboard tracker too. I decided create "one key
> press launcher". In production system we use only 3 keys:
> Power - launch netscape,
> Sleep - launch xmms,
> Weekup - launch xterm, that is on PS/2 kbd.
> Exists lots of small utils what cat do lots of "multimedia"
> jobs. Sample: aumix for sound adjusting.
>
> Nothing is ruby related, just historical bonds with this
> project.
>
> Aivils
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Linuxconsole-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
|
|
From: Hugo V. <hvw...@ya...> - 2004-12-16 16:36:44
|
Hi List! The problem with TNT2 cards and nVidia driver 6629 has "been identified internally": http://www.nvnews.net/vbulletin/showpost.php?p=480653&postcount=5 Presumably the next version will have a fix. Those with TNT2 cards will have to stick with 6111. HTH H __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com |
|
From: Aivils <ai...@un...> - 2004-12-15 07:15:12
|
On Tuesday 14 December 2004 23:47, Helge Hafting wrote:
> On Mon, Dec 13, 2004 at 12:00:57AM +0100, Zoltan Boszormenyi wrote:
> > Helge Hafting =EDrta:
> > >On Sat, Dec 11, 2004 at 04:49:53PM +0100, Zoltan Boszormenyi wrote:
> > >
> > >>There's a chunk in ruby-2.6.9-20041021, that's wrong.
> > >>It causes the compile error in line 1616. Here's the correct chunk.
> > >>It's the line after 'case GIO_FONTX:'.
> > >>
> > >
> > >Thanks a lot, this compiled fine! :-)
> > >
> > >Helge Hafting
> >=20
> > And I hope it works on your machines, at least it works on mine. ;-)
>=20
> Thanks for all the help so far.
> The kernel works in the sense that it boots.
> Unfortunately, 2.6.9 for amd64 has exactly the same problem as
> 2.6.9 for i386, it hangs the machine when the xserver tries to
> utilize the radeon 9200SE PCI card.
>=20
> So I tried compiling 2.6.8.1, as that one works for i386 for me.
> I got this:
>=20
> CC arch/x86_64/kernel/setup.o
> arch/x86_64/kernel/setup.c: In function `setup_arch':
> arch/x86_64/kernel/setup.c:582: error: `conswitchp' undeclared (first use=
in=20
> this function)
> arch/x86_64/kernel/setup.c:582: error: (Each undeclared identifier is rep=
orted=20
> only once
> arch/x86_64/kernel/setup.c:582: error: for each function it appears in.)
> arch/x86_64/kernel/setup.c:582: error: `vga_con' undeclared (first use in=
this=20
> function)
> make[1]: *** [arch/x86_64/kernel/setup.o] Error 1
> make: *** [arch/x86_64/kernel] Error 2
>=20
> Is there a trick to get this going, or will I have to wait
> for 2.6.10 and the next ruby release?
CVS-ed 2.6.9 arch/x86_64/kernel/setup.c and
ruby-2.6.9-20041021.diff.bz2
does not contain these lines :)
You should manualy delete some lines
from arch/x86_64/kernel/setup.c , if You will use versions below 2.6.9=20
diff -Nurp --exclude-from=3Dexclude linux-2.6.9/arch/x86_64/kernel/setup.c =
r269/arch/x86_64/kernel/setup.c
=2D-- linux-2.6.9/arch/x86_64/kernel/setup.c 2004-10-19 00:53:07.00000=
0000 +0300
+++ r269/arch/x86_64/kernel/setup.c 2004-10-21 21:04:27.000000000 +0300
@@ -596,14 +596,6 @@ void __init setup_arch(char **cmdline_p)
#ifdef CONFIG_GART_IOMMU
iommu_hole_init();
#endif
=2D
=2D#ifdef CONFIG_VT
=2D#if defined(CONFIG_VGA_CONSOLE)
=2D conswitchp =3D &vga_con;
=2D#elif defined(CONFIG_DUMMY_CONSOLE)
=2D conswitchp =3D &dummy_con;
=2D#endif
=2D#endif
}
static int __init get_model_name(struct cpuinfo_x86 *c)
Aivils
|
|
From: Helge H. <hel...@ai...> - 2004-12-14 21:39:53
|
On Mon, Dec 13, 2004 at 12:00:57AM +0100, Zoltan Boszormenyi wrote: > Helge Hafting írta: > >On Sat, Dec 11, 2004 at 04:49:53PM +0100, Zoltan Boszormenyi wrote: > > > >>There's a chunk in ruby-2.6.9-20041021, that's wrong. > >>It causes the compile error in line 1616. Here's the correct chunk. > >>It's the line after 'case GIO_FONTX:'. > >> > > > >Thanks a lot, this compiled fine! :-) > > > >Helge Hafting > > And I hope it works on your machines, at least it works on mine. ;-) Thanks for all the help so far. The kernel works in the sense that it boots. Unfortunately, 2.6.9 for amd64 has exactly the same problem as 2.6.9 for i386, it hangs the machine when the xserver tries to utilize the radeon 9200SE PCI card. So I tried compiling 2.6.8.1, as that one works for i386 for me. I got this: CC arch/x86_64/kernel/setup.o arch/x86_64/kernel/setup.c: In function `setup_arch': arch/x86_64/kernel/setup.c:582: error: `conswitchp' undeclared (first use in this function) arch/x86_64/kernel/setup.c:582: error: (Each undeclared identifier is reported only once arch/x86_64/kernel/setup.c:582: error: for each function it appears in.) arch/x86_64/kernel/setup.c:582: error: `vga_con' undeclared (first use in this function) make[1]: *** [arch/x86_64/kernel/setup.o] Error 1 make: *** [arch/x86_64/kernel] Error 2 Is there a trick to get this going, or will I have to wait for 2.6.10 and the next ruby release? Helge Hafting |
|
From: Alexandre T. <ate...@in...> - 2004-12-14 13:42:01
|
Hi all, I am using kernel 2.4.25 and got success with the adapters of usb for PS/2 (mouse and keyboard). To put I had problem with keyboards and mouses usb, to solve this I am moving for kernel 2.6.9 that he functioned perfectly and am working in the packages. I am developing the new packages of kernel 2.6.9 and of X.org 6.8.1 for multi-head and you can you find them in the URL: http://oraculo.insignesoftware.com/current/Six-System/Six-2.0/ Regards Alexandre PS: X.org I'm working. Em Ter, 2004-12-14 às 08:04, vineesh kumar escreveu: > Hi, > Now i am running a 3 headed PC with redhat Linux and 2.4.22-bruby > kernel. I wan't to extend it to four terminals. for that i tested with a > intel 865 MB. But the problem is that when the kernel is booting up the > USB devices are getting disabled. I tested the setup on an Asus/Nvidia > MB and there is the problem that when the kernel boots up one of the USB > devices getting disabled. wat is the problem? > Thanks > > vineesh > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > > |
|
From: vineesh k. <vi...@hc...> - 2004-12-14 13:04:41
|
Hi,
Now i am running a 3 headed PC with redhat Linux and 2.4.22-bruby
kernel. I wan't to extend it to four terminals. for that i tested with a
intel 865 MB. But the problem is that when the kernel is booting up the
USB devices are getting disabled. I tested the setup on an Asus/Nvidia
MB and there is the problem that when the kernel boots up one of the USB
devices getting disabled. wat is the problem?
Thanks
vineesh
|
|
From: James v. Z. <ja...@dv...> - 2004-12-14 11:18:15
|
I've had no troubles with the 6629 driver, in fact it seems to have solved an issue under ruby where OpenGL would crash the machine intermittently if used on the AGP console while the PCI console could run OpenGL without fear of lockup. Having said that I had no end of trouble with FC3 and nvidia cards with open and closed drivers and that seems now to be nearly completely fixed with the latest Xorg update, I can still crash it asking for an Xchooser based remote session. No such issues under RH9, FC1, FC2 J On Tue, 2004-12-14 at 04:20, Hugo Vanwoerkom wrote: > Hi List! > > I tried the 6629 nVidia driver and it's a mess. Gdm > starts and shows a more or less black screen. Went > back to 6111. > > Lots of negative comments in the forum. > > Anybody tried that here? > > H. > > > > __________________________________ > Do you Yahoo!? > Send holiday email and support a worthy cause. Do good. > http://celebrity.mail.yahoo.com > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev > |
|
From: Arne G. G. <ar...@li...> - 2004-12-14 08:20:24
|
* Hugo Vanwoerkom > I still use XFree 4.3.0 with a Debian option of > IsolateDevice (=prefbusid). I have an MX-440 PCI and a > TNT2 AGP. You don't use anything similar with Xorg > 6.8.1? To be frank, I don't know. My xorg.conf is derived from my XF86Config-4, and still has my "SingleCard"-directives in. However, grepping the sources does not indicate that this should have any effect. I am enabling the /proc/bus/pci/hackvideo stuff, though. Arne. |
|
From: Hugo V. <hvw...@ya...> - 2004-12-13 23:52:11
|
--- Arne Georg Gleditsch <ar...@li...> wrote: > * Hugo Vanwoerkom > > Hi List! > > > > I tried the 6629 nVidia driver and it's a mess. > Gdm > > starts and shows a more or less black screen. Went > > back to 6111. > > > > Lots of negative comments in the forum. > > > > Anybody tried that here? > > Works for me with two FX5200 cards. 2.6.9 and Xorg > 6.8.1. I'm > experiencing occasional, sporadic X resets, but I > upgraded from XFree > 4.4 til Xorg 6.8.1 at about the same time as I > upgraded the nVidia > drivers. > > I still use XFree 4.3.0 with a Debian option of IsolateDevice (=prefbusid). I have an MX-440 PCI and a TNT2 AGP. You don't use anything similar with Xorg 6.8.1? H. __________________________________ Do you Yahoo!? Dress up your holiday email, Hollywood style. Learn more. http://celebrity.mail.yahoo.com |
1998 messages has been excluded from this view by a project administrator.
