2.6.8.1-nitro2 "So creamy it's almost fattening"

Message

luqas · Post by **luqas** » Thu Aug 19, 2004 2:00 am

Here is a small fix that will allow you to compile the nitro2 without having to select software suspend in the kernel (for those that want it).

Just apply this on top of the nitro-sources...

software-suspend-fix-nitro

black hole sun · Post by **black hole sun** » Thu Aug 19, 2004 2:55 am

I get this when I compile:

Code: Select all

drivers/built-in.o(.text+0xa7b7a): In function `vesafb_check_var':
: undefined reference to `fb_validate_mode'
drivers/built-in.o(.text+0xa7cd9): In function `vesafb_check_limits':
: undefined reference to `fb_validate_mode'
drivers/built-in.o(.init.text+0x6df1): In function `vesafb_vbe_init':
: undefined reference to `fb_get_monitor_limits'
drivers/built-in.o(.init.text+0x6e26): In function `vesafb_vbe_init':
: undefined reference to `fb_create_modedb'
drivers/built-in.o(.init.text+0x6fcb): In function `vesafb_probe':
: undefined reference to `framebuffer_alloc'
drivers/built-in.o(.init.text+0x716c): In function `vesafb_probe':
: undefined reference to `fb_alloc_cmap'
drivers/built-in.o(.init.text+0x720d): In function `vesafb_probe':
: undefined reference to `vesa_modes'
drivers/built-in.o(.init.text+0x721d): In function `vesafb_probe':
: undefined reference to `fb_find_mode'
drivers/built-in.o(.init.text+0x72e9): In function `vesafb_probe':
: undefined reference to `fb_dealloc_cmap'
drivers/built-in.o(.init.text+0x72f1): In function `vesafb_probe':
: undefined reference to `framebuffer_release'
drivers/built-in.o(.init.text+0x7308): In function `vesafb_probe':
: undefined reference to `fb_destroy_modedb'
drivers/built-in.o(.init.text+0x7480): In function `vesafb_probe':
: undefined reference to `fb_get_mode'
drivers/built-in.o(.init.text+0x75d6): In function `vesafb_probe':
: undefined reference to `register_framebuffer'
drivers/built-in.o(.init.text+0x76de): In function `vesafb_probe':
: undefined reference to `fb_destroy_modedb'
drivers/built-in.o(.init.text+0x7983): In function `vesafb_probe':
: undefined reference to `fb_get_mode'
drivers/built-in.o(.init.text+0x79c2): In function `vesafb_probe':
: undefined reference to `framebuffer_release'
drivers/built-in.o(.data+0x3e474): undefined reference to `soft_cursor'
make: *** [.tmp_vmlinux1] Error 1

What option do I have to enable? I assume Framebuffer...can someone make a patch that allows a compile w/out framebuffer, my machine does NOT like FB...

jewps · Post by **jewps** » Thu Aug 19, 2004 3:44 am

just compile it in anyways, just don't put anything in your appent/kernel line in lilo/grub.

ett_gramse_nap · Post by **ett_gramse_nap** » Thu Aug 19, 2004 6:18 am

Dryre wrote:Here is a small fix that will allow you to compile the nitro2 without having to select software suspend in the kernel (for those that want it).

Just apply this on top of the nitro-sources...

software-suspend-fix-nitro

Doesn't work for me.

ett_gramse_nap · Post by **ett_gramse_nap** » Thu Aug 19, 2004 7:16 am

Kernel panic here as well. Trying to kill init.

luqas · Post by **luqas** » Thu Aug 19, 2004 10:08 am

ett_gramse_nap wrote:
Dryre wrote:Here is a small fix that will allow you to compile the nitro2 without having to select software suspend in the kernel (for those that want it).

Just apply this on top of the nitro-sources...

software-suspend-fix-nitro
Doesn't work for me.

Does it apply cleanly? Or can you not compile the kernel without swsusp2 selected? If you get the error on compile could you post it here. Thanks.

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 11:02 am

i have applied the patch but cant compile without Software Suspend 2

luqas · Post by **luqas** » Thu Aug 19, 2004 11:19 am

weird. I applied this patch to nitro last night an it let me compile without swsusp2 (of course I don't have any power management selected). What are the errors you are getting? Thanks.

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 12:10 pm

I use power management will try to disable it

be back if it works

edit. the compiling worjked wioll reboot and see if the kernel panic is gone .edit

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 1:15 pm

get same jkernel panix message as before

i think i skipped thos one and waiting for the next and hope that one will be better!!

fro5tbite · Post by **fro5tbite** » Thu Aug 19, 2004 1:30 pm

compile went ok, boot ok, nvidia wont boot x. I tried to modprobe nvidia, and it gave me error

luqas · Post by **luqas** » Thu Aug 19, 2004 1:44 pm

Robin79 wrote:get same jkernel panix message as before i think i skipped thos one and waiting for the next and hope that one will be better!!

Seppe is working hard on a new one, so hopefully you won't have to wait too long.

malloc · Post by **malloc** » Thu Aug 19, 2004 2:19 pm

Are you guys planning on putting any patch to fix the cdrecord problems?

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 2:31 pm

Dryre wrote:
Robin79 wrote:get same jkernel panix message as before i think i skipped thos one and waiting for the next and hope that one will be better!!
Seppe is working hard on a new one, so hopefully you won't have to wait too long.

Sounds great

what was the issue with 2.6.8.1-nitro1 and usb? I hope that will be fixed too

seppe · Post by **seppe** » Thu Aug 19, 2004 2:57 pm

A new nitro is in progress, but this time we'll test it a bit more

see http://sepi.be/nitro/experimental and tell us all the errors you got at #nitro-sources at irc.freenode.net

edit: vesafb-tng is still broken in that experimental release

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 3:35 pm

I give it a try!!!

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 3:57 pm

Compiled without errors

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 4:09 pm

lol ifor me the experimental version works great so long no errors when compiled no errros on boot!! I just w8 and see if anything goes unstable..

Gentii · Post by **Gentii** » Thu Aug 19, 2004 4:18 pm

Robin79, I don't think 3 posts are enough, you should have made 10 more to tell the same thing. You could write one word per post, you know. And buy a new keyboard too please.

ett_gramse_nap · Post by **ett_gramse_nap** » Thu Aug 19, 2004 4:24 pm

Gentii wrote:Robin79, I don't think 3 posts are enough, you should have made 10 more to tell the same thing. You could write one word per post, you know. And buy a new keyboard too please.

BIg deal?

neonik · Post by **neonik** » Thu Aug 19, 2004 6:51 pm

I haven't checked out the new nitro-sources, so can't tell if it's been fixed or not: the cdrecord problem. Memory overflow etc due to READ too early.

Anyway, if it's not yet been fixed, here's the patch from Andrew Morton's -mm2 patchset modified against linux-2.6.8.1-ck1: linux-2.6.8.1-ck1.bio_uncopy_user-mem-leak.patch

It should work with nitro-sources, I guess.

Edit: I've just taken a look at the list of the patches in nitro3, it's also in there, so feel free to ignore this post.

Robin79 · Post by **Robin79** » Thu Aug 19, 2004 8:46 pm

Gentii wrote:Robin79, I don't think 3 posts are enough, you should have made 10 more to tell the same thing. You could write one word per post, you know. And buy a new keyboard too please.

Whats the problem?? My keyboard works perfect just getting exited and typing faster than i can!! So sorry!! If you feel hurt please go see a shrink!
Mabey they can help you with you`r issues! against typing errors thank god im aint got dyselexi cause then i have gone mad on you!

fimbulvetr · Post by **fimbulvetr** » Thu Aug 19, 2004 11:14 pm

2.6.8.1-nitro2 #2 Thu Aug 19 16:03:08 MDT 2004 i686 Intel(R) Pentium(R) M processor 1600MHz GenuineIntel GNU/Linux

No problems here...

jewps · Post by **jewps** » Thu Aug 19, 2004 11:23 pm

A small fix for Nitro3, it basically incorporate's Dryre's swsusp fix and two minor fixes for vesafb-tng and ipw2100.

http://mobile.yingerdesign.com/other/Ni ... pw2100-fix

a little edit: the vesafb-tng bug is when you don't enable vesafb-tng, it will look for a default mode from your config file, if no default mode is set in the config, the compile craps out. the ipw2100 fix is for swsusp2, but thats only if you use ipw2100. if you don't apply this patch, ipw2100 will complain about a workqueue issue which should've been resolved in .53 of ipw2100, but for some reason it doesn't work all that well..

aka lith.

Robin79 · Post by **Robin79** » Fri Aug 20, 2004 12:06 am

Jewps: where should does errors come? i see the little cute penguin when booting and have no errors when compiling or booting?

2.6.8.1-nitro2 "So creamy it's almost fattening"

Lookin' good