| View previous topic :: View next topic |
| Author |
Message |
Regor
Guru
Joined: 06 Aug 2002
Posts: 545
Location: 39° 2' 48" N, 120° 59' 2" W
|
 Posted: Sun Oct 03, 2004 6:27 pm Post subject: |
 |
|
For those of you having problems with vesafb-tng using the mode you specify on the kernel commandline:
I'm having the same problem, but discovered that the mode I wanted was available if I did "fbset". In order to get my mode (1600x1200@70) at boot I had to change the default mode in my kernel config to match.
I don't know why the kernel isn't picking up on the commandline option, but you can at least get it to work automatically that way as a workaround.
_________________
Sometimes the appropriate response to reality is to go insane.
-Philip K. Dick, Valis |
|
| Back to top |
|
 |
Pink
Veteran
Joined: 24 Jul 2003
Posts: 1062
|
| Posted: Mon Oct 04, 2004 7:02 am Post subject: |
|
|
Woot! I'll have a look at the mm patch to see how you got it stable, every time it accessed the net it froze on mine.
Thanks utpark  |
|
| Back to top |
|
|
utpark
n00b
Joined: 14 Sep 2004
Posts: 15
|
|
| Back to top |
|
|
devast
n00b
Joined: 27 Apr 2004
Posts: 29
Location: Hungary
|
| Posted: Thu Oct 07, 2004 11:40 pm Post subject: |
|
|
Well i can't burn any cd-s with any cdrecord under this kernel...  |
|
| Back to top |
|
|
brodo
Guru
Joined: 15 Apr 2003
Posts: 319
|
| Posted: Fri Oct 08, 2004 6:45 am Post subject: |
|
|
I don't think | Quote: | | dothan-speedstep.patch | Initial dothan speedstep support |
is needed any longer. Dothan speedstep support (in the way it should be handled) is in 2.6.9-rc2. |
|
| Back to top |
|
|
alctraz
Tux's lil' helper
Joined: 12 May 2004
Posts: 117
Location: belgium
|
| Posted: Fri Oct 08, 2004 1:58 pm Post subject: |
|
|
hi,
i get this error while trying to compile with vesafb-tng support:
| Code: |
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4097): In function `vesafb_init_set_mode':
: undefined reference to `vesa_modes'
make: *** [.tmp_vmlinux1] Error 1
|
any idea?
(it compile fine with vesafb) |
|
| Back to top |
|
|
marchino
n00b
Joined: 16 Dec 2002
Posts: 70
Location: /home/marchino
|
| Posted: Fri Oct 08, 2004 5:06 pm Post subject: |
|
|
| Quote: |
@MetatronX99 you need to do it everytime you restart X, if you're not a security freak and you're the only user of your computer you can chmod +s /usr/bin/renice and add renice -10 `pidof X` to your ~/.xinitrc before the exec line
|
I've found a different way to renice X: edit the file /etc/X11/startDM.sh and change the line
| Code: | | /sbin/start-stop-daemon --start --quiet --exec ${EXE} |
to
| Code: | | /sbin/start-stop-daemon --start --quiet -N "-15" --exec ${EXE} |
Then enable xdm at startup.
Cheers
marchino |
|
| Back to top |
|
|
tapted
Tux's lil' helper
Joined: 02 Dec 2003
Posts: 122
Location: Sydney, Australia
|
| Posted: Wed Oct 13, 2004 1:51 am Post subject: Nicks scheduler is fux0red |
|
|
Are there any known problems with nicks scheduler and hyperthreading??
I've got a kernel on my laptop that was patched up the wazzu to get bluetooth and reiser4 working for an external USB 2.0 HD (something like 2-6-8-gentoo-r3-reiser4-mh2) and it works fine unless you decide to shutdown without umounting the reiser4 drives (major kernel panic there)...
So I wanted a more stable resier4 kernel for my desktop.. I gave love a go, but the scheduler seems to be rather crap. X is unusable when *anything* is happening in the background -- whether it's an emerge running make -j2 or even just pdflatex running in user mode at nice -n 19.
I did the renice X thing, but whether it's at 0 or +19 or -19 seems to make no difference. And it's not just slow -- it's actually losing keystrokes and mouse clicks (especially when I've just typed a word that has repeating letters -- eg letters -> lters or worse).
I've backed off to 2.6.8-gentoo-r7 and everything runs swimmingly (except for reiser4 which doesn't exist..).
My pootah is a newish P4 3.2 GHz and the mobo has PCI Express running Marvell Yukon gigabit ethernet (sk98lin.ko had to be compiled ouside of the kernel tree) and a GeForce FX somethingorother (nvidia.ko seems to work OK).
So unless anyone has any suggestions, mine is
Vote [1] to ditch nick's scheduler. |
|
| Back to top |
|
|
the_g_cat
Tux's lil' helper
Joined: 31 Mar 2004
Posts: 117
Location: Dortmund - Germany
|
| Posted: Thu Oct 14, 2004 8:49 pm Post subject: |
|
|
| alctraz wrote: | hi,
i get this error while trying to compile with vesafb-tng support:
| Code: |
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4097): In function `vesafb_init_set_mode':
: undefined reference to `vesa_modes'
make: *** [.tmp_vmlinux1] Error 1
|
any idea?
(it compile fine with vesafb) |
Nearly the same here, only the hexadecimal value seems to change (a memory adress?) :
| Code: | drivers/built-in.o(.init.text+0x454f): In function `vesafb_init_set_mode':
: undefined reference to `vesa_modes'
make: *** [.tmp_vmlinux1] Error 1 |
Note: I didn't try 'normal' vesafb ... |
|
| Back to top |
|
|
Bagira80
n00b
Joined: 27 Dec 2003
Posts: 4
Location: Germany
|
| Posted: Thu Oct 21, 2004 9:05 pm Post subject: |
|
|
| the_g_cat wrote: | | alctraz wrote: | hi,
i get this error while trying to compile with vesafb-tng support:
| Code: |
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x4097): In function `vesafb_init_set_mode':
: undefined reference to `vesa_modes'
make: *** [.tmp_vmlinux1] Error 1
|
any idea?
(it compile fine with vesafb) |
Nearly the same here, only the hexadecimal value seems to change (a memory adress?) :
| Code: | drivers/built-in.o(.init.text+0x454f): In function `vesafb_init_set_mode':
: undefined reference to `vesa_modes'
make: *** [.tmp_vmlinux1] Error 1 |
Note: I didn't try 'normal' vesafb ... |
Same error here when trying to compile with vesafb-ng. Just the memory location is a different one. However it also worked with vesafb.
I'm using the gentoo-dev-sources (2.6.9-r1) |
|
| Back to top |
|
|
enzobelmont
Guru
Joined: 06 Apr 2004
Posts: 345
Location: Chiapas, Mexico
|
| Posted: Thu Oct 21, 2004 11:28 pm Post subject: |
|
|
is win4lin merged in this patchset now???
sorry my english...  |
|
| Back to top |
|
|
7thSphere
n00b
Joined: 28 Apr 2004
Posts: 31
|
| Posted: Fri Oct 22, 2004 3:33 pm Post subject: |
|
|
same error here....
kernel linux-2.6.9-gentoo-r1
| Code: | CHK include/linux/compile.h
UPD include/linux/compile.h
CC init/version.o
LD init/built-in.o
LD .tmp_vmlinux1
drivers/built-in.o(.init.text+0x3b34): In function `vesafb_init_set_mode':
: undefined reference to `vesa_modes'
make: *** [.tmp_vmlinux1] Error 1
|
|
|
| Back to top |
|
|
Bagira80
n00b
Joined: 27 Dec 2003
Posts: 4
Location: Germany
|
| Posted: Sat Oct 23, 2004 12:59 pm Post subject: Got it to work |
|
|
I got it to work with vesafb-tng:
I don't really know what the difference was, but I tried to compile everything into the kernel (I only have one module for my TV-card). (So if you use modules, maybe you have to put all the graphic modules into the modules.autoload.d/kernel-2.6 ?)
And after configuring I re-emerged svgalib (which had some problems compiling without a configuration file for the kernel).
| Code: | | USE="build" emerge svgalib |
Then compiling the kernel and it did without problem. And finally I even got the framebuffer to work again. |
|
| Back to top |
|
|
WaVeX
Tux's lil' helper
Joined: 15 Mar 2004
Posts: 102
Location: USA, Michigan or Ohio
|
| Posted: Sun Oct 24, 2004 11:25 pm Post subject: |
|
|
Whats the best way to renice X every time X starts? I'm getting tired of doing it manually.
Oh and I would just like to say this is the best kernel I've used so far. Stable, fast, responsive. Thx alot. |
|
| Back to top |
|
|
ExZombie
Apprentice
Joined: 29 May 2004
Posts: 170
|
| Posted: Mon Oct 25, 2004 1:58 pm Post subject: |
|
|
| WaVeX wrote: | Whats the best way to renice X every time X starts? I'm getting tired of doing it manually.
Oh and I would just like to say this is the best kernel I've used so far. Stable, fast, responsive. Thx alot. |
emerge verynice  |
|
| Back to top |
|
|
Dud3!
Tux's lil' helper
Joined: 19 Aug 2004
Posts: 93
Location: Boringville, Florida, USA
|
| Posted: Mon Nov 01, 2004 10:12 pm Post subject: |
|
|
Wow! Quite a performance difference! I was using 2.6.7-rc3-love2 and this is a lot faster.
One problem, I grabbed that nvidia ebuild and emerged it and the 6111 glx, but X won't start. I'm running X right now with the nv driver...
Here's what I get:
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
_________________
"There's no problem so large it can't be solved by killing the user off, deleting their files, closing their account and reporting their REAL earnings to the IRS" |
|
| Back to top |
|
|
Dud3!
Tux's lil' helper
Joined: 19 Aug 2004
Posts: 93
Location: Boringville, Florida, USA
|
| Posted: Tue Nov 02, 2004 1:38 pm Post subject: |
|
|
I can't get OSS (4Front OSS, not the free one) to work either.
I got the latest one and installed it, but after it compiles the module it can't load it.
--------------------------------------------------------
Building the OSS kernel module - please wait...
Failed to activate the driver
Probably caused by a technical problem.
See /usr/lib/oss/logs/soundon.log for more info.
ERROR: Module osslinux does not exist in /proc/modules
In the soundon log this is what happens:
Loading OSS/Linux module
insmod: error inserting '/usr/lib/oss/modules/osslinux': -1 Unknown symbol in module
insmod: error inserting '/usr/lib/oss/modules/osslinux': -1 Unknown symbol in module
Any ideas for this or the NVIDIA stuff?
_________________
"There's no problem so large it can't be solved by killing the user off, deleting their files, closing their account and reporting their REAL earnings to the IRS" |
|
| Back to top |
|
|
WaVeX
Tux's lil' helper
Joined: 15 Mar 2004
Posts: 102
Location: USA, Michigan or Ohio
|
| Posted: Thu Nov 04, 2004 5:34 pm Post subject: |
|
|
| Dud3! wrote: | Wow! Quite a performance difference! I was using 2.6.7-rc3-love2 and this is a lot faster.
One problem, I grabbed that nvidia ebuild and emerged it and the 6111 glx, but X won't start. I'm running X right now with the nv driver...
Here's what I get:
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found |
Did you try this package from the main post.
nvidia ebuild (in case you didnt get for love 3).
http://love-sources.q2h.com/nvidia-kernel-1.0.6111-r2.tar.bz2 |
|
| Back to top |
|
|
|
Unsupported Software
