View previous topic :: View next topic |
Author |
Message |
Psiuyo n00b
Joined: 22 Apr 2004 Posts: 50 Location: Calgary
|
Posted: Thu Jul 08, 2004 12:43 am Post subject: |
|
|
theonlymcc wrote: | I still get a kernel crash using vesafb:tng. Here is part of the trace that I can see.
Code: | kernel BUG at arch/i386/kernel/smp.c: 358!
invalid operand: 0000 [#1]
PREEMPT SMP
... blah blah
<6> note: vesafb[43] exited with preempt_count 2 |
|
Same here. I have yet to get any kernel with vesafb-tng to boot on my machine. I get the same error msg, but I think mine is .... vesafb[34]... but I could be wrong.
Removing bootsplash,initrd,video=*** have no effect on this error
Just out of curiosity, what video card are you running?
I'm using an SIS (650 I believe), with 64MB used for video mem.
(P4 non-hyperthreaded if it makes a difference) |
|
Back to top |
|
|
L124RD n00b
Joined: 01 Mar 2004 Posts: 23
|
Posted: Thu Jul 08, 2004 12:46 am Post subject: vesafb-tng |
|
|
Edit: the error above is what I was getting before I reconfigured. I think the main things I changed were turning off SMP since I only had one processor, and changing the processor from Pentium 4 to pentium M (since it has a pentium M I don't know why all my past kernels have been configured to pentium 4 0o )
vesafb seems to be failing. When I set it up originally I wasn't able to boot my computer, vesafb gave stack and call traces. I deleted the config and configured it from the defaults, booted the second time around. My kernel command line looks like: Quote: | root=/dev/hda3 video=vesafb:ywrap,mtrr,1280x1024@62 splash=verbose initrd=/boot/initrd-1280x1024 |
the lines from vesafb loading in dmesg look like: Quote: | vesafb: ATI Technologies Inc., M9 , 01.00 (OEM: ATI MOBILITY RADEON 9000)
vesafb: VBE version: 2.0
vesafb: protected mode interfaces info at c000:57f3
vesafb: pmi: set display start = c00c5861, set palette = c00c589b
vesafb: pmi: ports = c010 c016 c054 c038 c03c c05c c000 c004 c0b0 c0b2 c0b4
vesafb: hardware supports DCC2 transfers
vesafb: EDID vendor sign: SHP
vesafb: monitor limits: vf = 61 Hz, hf = 67 kHz, clk = 108 MHz
vesafb: total memory: 67043328
vesafb: fb_get_mode failed
vesafb: probe of vesafb0 failed with error -22 |
|
|
Back to top |
|
|
Evil Dark Archon Guru
Joined: 21 Dec 2002 Posts: 562 Location: Santa Rosa, CA
|
Posted: Thu Jul 08, 2004 1:08 am Post subject: |
|
|
this is my vesafb dmesg output:
Quote: |
vesafb: NVIDIA Corporation, NV34 Board - p162-11n, Chip Rev (OEM: NVIDIA)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:e2e0
vesafb: pmi: set display start = c00ce316, set palette = c00ce380
vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
vesafb: hardware doesn't support DCC transfers
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: total memory: 268435456
vesafb: scrolling: ypan using protected mode interface, yres_virtual=65536
vesafb: abort, cannot ioremap video memory 0x10000000 @ 0xc0000000
vesafb: probe of vesafb0 failed with error -5
|
_________________ This post has been over explained for newb-informing purposes.
Registered Linux user 347334
Abit AV8-3rd eye, AMD Athlon64 3500+ 90nm, ATI Radeon x850 pro |
|
Back to top |
|
|
jou n00b
Joined: 29 Apr 2004 Posts: 6 Location: Pasadena, CA
|
Posted: Thu Jul 08, 2004 1:56 am Post subject: |
|
|
@SATA problems:
there is a new option in mm:
Device Drivers: ATA/ATAPI/MFM/RLL support: Support for SATA (deprecated...) etc etc.
If you don't enable this, SATA won't work with normal ATA drivers (not SCSI). Happened to me on my boot drive (-_-)
the thing to add to your config would be:
Code: | CONFIG_BLK_DEV_IDE_SATA: y |
cheers. |
|
Back to top |
|
|
luqas Guru
Joined: 02 Jan 2004 Posts: 588 Location: /US/Texas/Beaumont
|
Posted: Thu Jul 08, 2004 2:01 am Post subject: |
|
|
I can't get bootsplash to run either. It doesn't even try. I even did rc-update add bootsplash default and it shows, but it doesn't even try to start. Below is my dmesg for vesafb and below that my grub.conf.
On a good note, I finally got / on reiser4!!!!
Code: |
Kernel command line: root=/dev/hda2 video=vesafb:ywrap,1024x768@60 elevator=cfq splash=silent
vesafb: ATI Technologies Inc., R300, 01.00 (OEM: ATI R300)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:57ce
vesafb: pmi: set display start = c00c5862, set palette = c00c58ae
vesafb: pmi: ports = c010 c016 c054 c038 c03c c05c c000 c004 c0b0 c0b2 c0b4
vesafb: hardware supports DCC2 transfers
vesafb: EDID vendor sign: SAM
vesafb: monitor limits: vf = 160 Hz, hf = 69 kHz, clk = 110 MHz
vesafb: total memory: 134217728
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=131072
vesafb: framebuffer at 0xd0000000, mapped to 0xe0800000, size 131072k
|
Code: |
default 0
timeout 10
splashimage=(hd1,0)/boot/grub/tux.xpm.gz
#Windows XP
title=Windows XP
root (hd0,0)
chainloader +1
#Linux
title=Linux
root=(hd1,0)
kernel=/boot/kernel-2.6.7-love7-norfs root=/dev/hda2 video=vesafb:ywrap,1024x768@60 elevator=cfq splash=silent
initrd=/boot/initrd-1024x768
|
|
|
Back to top |
|
|
o0the_llama0o Tux's lil' helper
Joined: 10 May 2004 Posts: 89 Location: santa cruz
|
Posted: Thu Jul 08, 2004 4:39 am Post subject: |
|
|
"lucky 7" breaks vim watch out (Segmentation Fault)
--fix? |
|
Back to top |
|
|
CaribbeanKnight Apprentice
Joined: 27 Apr 2003 Posts: 240 Location: Earth -> Europe -> Belgium -> Diest
|
Posted: Thu Jul 08, 2004 5:19 am Post subject: |
|
|
doctord: you're talking about that i2c error, right? if so, can you tell me what stardust-sources you're using..? and what i2c options you enabled in your kernel or your .config? i have an nforce2 too and that way i can have a look at what's wrong.. _________________ ...we ain't shit...
Linux User #353893 |
|
Back to top |
|
|
Mafteah Apprentice
Joined: 30 May 2003 Posts: 265 Location: IL
|
Posted: Thu Jul 08, 2004 5:45 am Post subject: |
|
|
If someone having problems with vesafb-tng
And he read the doc about it.
He can reverse the patch and use the orginal vesafb _________________ http://www.mafteah.co.il |
|
Back to top |
|
|
Pink Veteran
Joined: 24 Jul 2003 Posts: 1062
|
Posted: Thu Jul 08, 2004 6:46 am Post subject: |
|
|
for all those with:
1 segmentation faults
2 sensors problems
1. This has been a running theme since mm4 was brought out.
Some ppl get seg faults with the same setup and other ppl don't. we are not sure why. It happens (we also don't know of a fix).
2. Reverse the bk-acpi.patch, this will fix the sensor problem, again, this has been happening since mm4 when it was put in the mm patch set.
HTH |
|
Back to top |
|
|
adrenalin Tux's lil' helper
Joined: 29 Dec 2002 Posts: 129
|
Posted: Thu Jul 08, 2004 7:06 am Post subject: |
|
|
dryre:
for bootsplash to work try to explicitly state 16 bit color depth so that your kernel command line looks like
Code: | kernel=/boot/kernel-2.6.7-love7-norfs root=/dev/hda2 video=vesafb:ywrap,1024x768-16@60 elevator=cfq splash=silent |
hth |
|
Back to top |
|
|
seppe Guru
Joined: 01 Sep 2003 Posts: 431 Location: Hove, Antwerp, Belgium
|
Posted: Thu Jul 08, 2004 7:17 am Post subject: |
|
|
How can I patch this kernel to use the StairCase scheduler? Staircase gives me much better results than Nick's.
Anyone? _________________ nitro-sources, because between stable and experimental there exists only speed
Latest release I made: 2.6.13.2-nitro1 |
|
Back to top |
|
|
Pink Veteran
Joined: 24 Jul 2003 Posts: 1062
|
Posted: Thu Jul 08, 2004 7:36 am Post subject: |
|
|
seppe wrote: | How can I patch this kernel to use the StairCase scheduler? Staircase gives me much better results than Nick's.
Anyone? |
Like we said to you yesterday in #love-sources, you need to reverse nick's scheduler (fix the rejects) and then apply the staircase patch from con (fix the many many many rejects).
Not an easy task I'm afraid. |
|
Back to top |
|
|
adrenalin Tux's lil' helper
Joined: 29 Dec 2002 Posts: 129
|
Posted: Thu Jul 08, 2004 8:14 am Post subject: |
|
|
PickledOnion wrote: | for all those with:
2 sensors problems
2. Reverse the bk-acpi.patch, this will fix the sensor problem, again, this has been happening since mm4 when it was put in the mm patch set.
HTH |
thank you, that fixed the sensor problem, but unfortunately broke bootsplash again. still wondering why the sensors are working with plain mm6. |
|
Back to top |
|
|
Rainmaker Veteran
Joined: 12 Feb 2004 Posts: 1650 Location: /home/NL/ehv/
|
Posted: Thu Jul 08, 2004 8:25 am Post subject: |
|
|
Mafteah wrote: | vertigo_ wrote: | will the config file from gentoo-sources will work on it 2? |
just:
cp .config to the love
make oldconfig
and compile |
make oldconfig is ugly.
Just do make clean, then cp the .config to the dir, and say make menuconfig.
It will use the default values of the already present .config _________________ If you can't dazzle them with brilliance, baffle them with bullshit. |
|
Back to top |
|
|
petrjanda Veteran
Joined: 05 Sep 2003 Posts: 1557 Location: Brno, Czech Republic
|
Posted: Thu Jul 08, 2004 8:37 am Post subject: |
|
|
Is reiser4 still unstable as flowing water? _________________ There is, a not-born, a not-become, a not-made, a not-compounded. If that unborn, not-become, not-made, not-compounded were not, there would be no escape from this here that is born, become, made and compounded. - Gautama Siddharta |
|
Back to top |
|
|
neenee Veteran
Joined: 20 Jul 2003 Posts: 1786
|
Posted: Thu Jul 08, 2004 8:40 am Post subject: |
|
|
reiser4 seems stable to me. |
|
Back to top |
|
|
Frodg l33t
Joined: 11 Feb 2004 Posts: 761
|
Posted: Thu Jul 08, 2004 9:12 am Post subject: |
|
|
A quick question with love 7:
I can get bootsplash to work but when I log in as any user (either to text or graphics) the bootsplash screen refreshes itself (is that the right term?) and the system hangs
I am left looking at a lovely bootsplash theme but a non functioning screen...
Disabling bootsplash the system works perfectly (and very quick )
So is there a solution or do I give up on bootstrap for the time being ? _________________ Aerosolo ergo sum - I spray therefore I am
Gentoo - Registered Linux User # 361400 |
|
Back to top |
|
|
ryszardzonk Apprentice
Joined: 18 Dec 2003 Posts: 225 Location: Rzeszów, POLAND
|
Posted: Thu Jul 08, 2004 9:16 am Post subject: vesa-tng && bootsplash |
|
|
There seems to be many people having trouble setting up new vesa patch and/or getting bootsplash to work. There has been a lot of coverage about this subjects in the forums already. The best I can do is to point out to the right directions
vesa-tng thread:
https://forums.gentoo.org/viewtopic.php?t=71570
bootsplash setup thread:
https://forums.gentoo.org/viewtopic.php?t=49036
warning: it has some info relating to old vesa setup, so be sure to use vesa related setup as in previous thread
example lilo.conf would be:
image="/boot/bzImage"
root="/dev/hda2"
label="2.6.7-love-7"
read-only # read-only for checking
append="video=vesafb:ywrap,mtrr splash=silent"
initrd=/boot/initrd-1024x768
INSTEAD OF: (OLD WAY)
image="/boot/bzImage"
vga=0x317
root="/dev/hda2"
label="2.6.7"
read-only # read-only for checking
append="video=vesafb:ywrap,mtrr splash=silent"
initrd=/boot/initrd-1024x768
vram:16 -- this option limits amount of memory video card would use for framebuffer to 16 MB, old patch use to do it by default, this one may create problems if this is not set
mtrr -- speeds up graphics drawing, always use on desktop, very recomended
ywrap -- speeds up scrolling, use this or "ypan" (slower). I have Riva TNT 2 which is quite old this days and faster method works for me without the glich, so I recomend it as well
My personal advice would be to try to set up each one by one. May take little more time that way, but eventually would lead to success.
GOOD LUCK ALL _________________ Sky is not the limit... |
|
Back to top |
|
|
DocterD Tux's lil' helper
Joined: 15 May 2004 Posts: 129
|
Posted: Thu Jul 08, 2004 9:26 am Post subject: |
|
|
CaribbeanKnight wrote: | doctord: you're talking about that i2c error, right? if so, can you tell me what stardust-sources you're using..? and what i2c options you enabled in your kernel or your .config? i have an nforce2 too and that way i can have a look at what's wrong.. |
yep, it also happens with the Latest Stardust Themes (haven't testet any other release)
here is my config
http://home.arcor.de/collinso/config
Edit:
here is the exactly Error:
Quote: | i2c /dev entries driver
: Error requesting region 5000 .. 5007 for SMB1
nForce2 SMBus 0000:00:01.1: Error probing SMB1.
: Error requesting region 5040 .. 5047 for SMB2
nForce2 SMBus 0000:00:01.1: Error probing SMB2. |
Just now i'm using CK-Sources-r5 without any problem. My Board is a MSI K7N2-Delta. |
|
Back to top |
|
|
ryszardzonk Apprentice
Joined: 18 Dec 2003 Posts: 225 Location: Rzeszów, POLAND
|
Posted: Thu Jul 08, 2004 9:48 am Post subject: problems, and more problems |
|
|
Quote: | PickledOnion wrote:
for all those with:
2 sensors problems
2. Reverse the bk-acpi.patch, this will fix the sensor problem, again, this has been happening since mm4 when it was put in the mm patch set.
HTH Very Happy
adrenalin wrote:
thank you, that fixed the sensor problem, but unfortunately broke bootsplash again. still wondering why the sensors are working with plain mm6. |
Hmm i didn't even notice, sinse I dont even remeber when is last time I started gkrellm to see my sensors readings, but yes there is a problem and it would be great to fix it. It works, shows all the readings, but takes up 99% of CPU time...
I would reverse bk-acpi.patch, but my question is why it breaks bootsplash I do not really fell as trying to fix something, breaking something else.
Other issue is segfaulting of some apps. Cause of that is using new nvidia-driver. Examples are mplayer, xine, xmms, wine (if using opengl).
EDIT : To solve problem with new nvidia-driver all that is nessesery is to do cp /usr/lib/tls/libnvidia-tls.so.1.0.6106 /usr/lib/opengl/nvidia/lib
No restart of X serwer, or reloading of drivers is nessesery
P.S. New java form Sun works great jdk-1_5_0-beta3-bin-b57-linux-i586-23_jun_2004.bin
if someone needs I can provide them with an ebuild for it _________________ Sky is not the limit... |
|
Back to top |
|
|
Dinini Apprentice
Joined: 11 Jun 2003 Posts: 236
|
Posted: Thu Jul 08, 2004 10:57 am Post subject: Re: bootsplash |
|
|
Tazok wrote: | Cool, bootsplash is working again.
But I don't get more than 60Hz using this line:
video=vesafb:ywrap,vram:16,1024x768-16@75 |
When bootsplash is initialized it is resetting the vesafb so you're getting the same resolution and color depth but reverting to the default refresh rate for your card
This doesn't happen with 2.6.7 + vesafb-tng + bootsplash
but it does happen with 2.6.7-mm6 + vesafb-tng + bootsplash
I've been tearing my hair out for hours trying to track the problem. If anyone has a clue of precisely which of the framebuffer changes in mm6 is responsible please let me know. |
|
Back to top |
|
|
neenee Veteran
Joined: 20 Jul 2003 Posts: 1786
|
Posted: Thu Jul 08, 2004 11:00 am Post subject: Re: problems, and more problems |
|
|
ryszardzonk wrote: | P.S. New java form Sun works great jdk-1_5_0-beta3-bin-b57-linux-i586-23_jun_2004.bin
if someone needs I can provide them with an ebuild for it |
why don't you submit the ebuild to bugzilla?
that way everyone can benefit from it |
|
Back to top |
|
|
Mafteah Apprentice
Joined: 30 May 2003 Posts: 265 Location: IL
|
Posted: Thu Jul 08, 2004 11:05 am Post subject: Re: bootsplash |
|
|
Dinini wrote: | Tazok wrote: | Cool, bootsplash is working again.
But I don't get more than 60Hz using this line:
video=vesafb:ywrap,vram:16,1024x768-16@75 |
When bootsplash is initialized it is resetting the vesafb so you're getting the same resolution and color depth but reverting to the default refresh rate for your card
This doesn't happen with 2.6.7 + vesafb-tng + bootsplash
but it does happen with 2.6.7-mm6 + vesafb-tng + bootsplash
I've been tearing my hair out for hours trying to track the problem. If anyone has a clue of precisely which of the framebuffer changes in mm6 is responsible please let me know. |
i fixed it in love7 _________________ http://www.mafteah.co.il |
|
Back to top |
|
|
luqas Guru
Joined: 02 Jan 2004 Posts: 588 Location: /US/Texas/Beaumont
|
Posted: Thu Jul 08, 2004 11:16 am Post subject: |
|
|
adrenalin wrote: | dryre:
for bootsplash to work try to explicitly state 16 bit color depth so that your kernel command line looks like
Code: | kernel=/boot/kernel-2.6.7-love7-norfs root=/dev/hda2 video=vesafb:ywrap,1024x768-16@60 elevator=cfq splash=silent |
hth |
That did it adrenalin. Thanks for you help. |
|
Back to top |
|
|
placeholder Advocate
Joined: 07 Feb 2004 Posts: 2500
|
Posted: Thu Jul 08, 2004 11:26 am Post subject: Re: 2.6.7-love7 aka lucky 7 |
|
|
Mafteah wrote: |
New in love7
Code: | bootsplash-3.1.4-2.6.7-love6-fix.patch
alsafix.patch
lircfix.patch
2.6.7-mm6-np5.gz
reiser4-2004.07.06-19.36-linux-2.6.7-mm4.diff.gz
|
Bootsplash works!
Alsamixer works!
Lirc works! |
All that stuff (not sure about Lirc since I don't use it) works fine for me in 2.6.7-love5. Are there any more reasons why I should upgrade my love sources? Any hightened security to be gained over 2.6.7-love5? |
|
Back to top |
|
|
|