| View previous topic :: View next topic |
| Author |
Message |
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
 Posted: Mon Jul 04, 2005 7:59 pm Post subject: |
 |
|
Working perfectly here! | Code: | | Linux drizzt 2.6.12-nitro2 #3 Sun Jul 3 22:52:58 PDT 2005 x86_64 AMD Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux |
Had some hiccups w/ my initrd (said /dev/hda3 wasn't a valid root device), but I switched to a more standard grub.conf, and it is fine. Running nvidia w/ no problems.
Thanks for all the hard work!
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
 |
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Mon Jul 04, 2005 8:49 pm Post subject: |
|
|
Would the ppl with NFORCE4 problem try this temporary maybe-fix:
add the
to your kernel boot parameters in grub/lilo .....
i hope it helps *hopes*
Cinder6: what chipset do you have?
cheers
T
_________________
Retired gentoo user |
|
| Back to top |
|
|
bbkr
n00b
Joined: 04 Jul 2005
Posts: 22
|
| Posted: Mon Jul 04, 2005 9:03 pm Post subject: NVidia weird problem |
|
|
got '6 in the morning'.
emerged nvidia 7174
modprobe nvidia
...
everything fine so far.
but xinit won't start. here's log:
| Code: |
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV10GL [Quadro] rev 16, Mem @ 0xed000000/24, 0xf0000000/27, BIOS @ 0xefff0000/16
(--) PCI: (2:14:0) Brooktree Corporation Bt878 Video Capture rev 17, Mem @ 0xef000000/12
(II) Addressable bus resource ranges are
[0] -100x00000000 - 0xffffffff (0x0) MX[B]
[1] -100x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -100xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -100x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -100x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -100x000c0000 - 0x000effff (0x30000) MX[B]
[4] -100x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -100x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -100x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf8000000 from 0xfbffffff to 0xf7ffffff
(II) Active PCI resource ranges:
[0] -100xee800000 - 0xee800fff (0x1000) MX[B]
[1] -100xec000000 - 0xec0000ff (0x100) MX[B]
[2] -100x20000000 - 0x200003ff (0x400) MX[B]
[3] -100xec800000 - 0xec8003ff (0x400) MX[B]
[4] -100xf8000000 - 0xf7ffffff (0x0) MX[B]O
[5] -100xef000000 - 0xef000fff (0x1000) MX[B](B)
[6] -100xefff0000 - 0xefffffff (0x10000) MX[B](B)
[7] -100xf0000000 - 0xf7ffffff (0x8000000) MX[B](B)
[8] -100xed000000 - 0xedffffff (0x1000000) MX[B](B)
[9] -100x0000b000 - 0x0000b01f (0x20) IX[B]
[10] -100x0000b400 - 0x0000b4ff (0x100) IX[B]
[11] -100x0000b800 - 0x0000b8ff (0x100) IX[B]
[12] -100x0000e800 - 0x0000e81f (0x20) IX[B]
[13] -100x0000f000 - 0x0000f00f (0x10) IX[B]
[14] -100x0000d000 - 0x0000d01f (0x20) IX[B]
[15] -100x0000d400 - 0x0000d41f (0x20) IX[B]
[16] -100x0000d800 - 0x0000d81f (0x20) IX[B]
(II) Active PCI resource ranges after removing overlaps:
[0] -100xee800000 - 0xee800fff (0x1000) MX[B]
[1] -100xec000000 - 0xec0000ff (0x100) MX[B]
[2] -100x20000000 - 0x200003ff (0x400) MX[B]
[3] -100xec800000 - 0xec8003ff (0x400) MX[B]
[4] -100xf8000000 - 0xf7ffffff (0x0) MX[B]O
[5] -100xef000000 - 0xef000fff (0x1000) MX[B](B)
[6] -100xefff0000 - 0xefffffff (0x10000) MX[B](B)
[7] -100xf0000000 - 0xf7ffffff (0x8000000) MX[B](B)
[8] -100xed000000 - 0xedffffff (0x1000000) MX[B](B)
[9] -100x0000b000 - 0x0000b01f (0x20) IX[B]
[10] -100x0000b400 - 0x0000b4ff (0x100) IX[B]
[11] -100x0000b800 - 0x0000b8ff (0x100) IX[B]
[12] -100x0000e800 - 0x0000e81f (0x20) IX[B]
[13] -100x0000f000 - 0x0000f00f (0x10) IX[B]
[14] -100x0000d000 - 0x0000d01f (0x20) IX[B]
[15] -100x0000d400 - 0x0000d41f (0x20) IX[B]
[16] -100x0000d800 - 0x0000d81f (0x20) IX[B]
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -100xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -100x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[2] -100x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -100x000c0000 - 0x000effff (0x30000) MX[B]
[4] -100x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -100x0000ffff - 0x0000ffff (0x1) IX[B]
[6] -100x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -100xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -100x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[2] -100x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -100x000c0000 - 0x000effff (0x30000) MX[B]
[4] -100x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -100xee800000 - 0xee800fff (0x1000) MX[B]
[6] -100xec000000 - 0xec0000ff (0x100) MX[B]
[7] -100x20000000 - 0x200003ff (0x400) MX[B]
[8] -100xec800000 - 0xec8003ff (0x400) MX[B]
[9] -100xf8000000 - 0xf7ffffff (0x0) MX[B]O
[10] -100xef000000 - 0xef000fff (0x1000) MX[B](B)
[11] -100xefff0000 - 0xefffffff (0x10000) MX[B](B)
[12] -100xf0000000 - 0xf7ffffff (0x8000000) MX[B](B)
[13] -100xed000000 - 0xedffffff (0x1000000) MX[B](B)
[14] -100x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -100x00000000 - 0x000000ff (0x100) IX[B]
[16] -100x0000b000 - 0x0000b01f (0x20) IX[B]
[17] -100x0000b400 - 0x0000b4ff (0x100) IX[B]
[18] -100x0000b800 - 0x0000b8ff (0x100) IX[B]
[19] -100x0000e800 - 0x0000e81f (0x20) IX[B]
[20] -100x0000f000 - 0x0000f00f (0x10) IX[B]
[21] -100x0000d000 - 0x0000d01f (0x20) IX[B]
[22] -100x0000d400 - 0x0000d41f (0x20) IX[B]
[23] -100x0000d800 - 0x0000d81f (0x20) IX[B]
(II) LoadModule: "glx"
(II) Loading /usr/lib/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.7174
Module class: XFree86 Server Extension
ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension GLX
(...)
(II) NVIDIA dlloader X Driver 1.0-7174 Tue Mar 22 06:46:47 PST 2005
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(--) Chipset NVIDIA GPU found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -100xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -100x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[2] -100x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -100x000c0000 - 0x000effff (0x30000) MX[B]
[4] -100x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -100xee800000 - 0xee800fff (0x1000) MX[B]
[6] -100xec000000 - 0xec0000ff (0x100) MX[B]
[7] -100x20000000 - 0x200003ff (0x400) MX[B]
[8] -100xec800000 - 0xec8003ff (0x400) MX[B]
[9] -100xf8000000 - 0xf7ffffff (0x0) MX[B]O
[10] -100xef000000 - 0xef000fff (0x1000) MX[B](B)
[11] -100xefff0000 - 0xefffffff (0x10000) MX[B](B)
[12] -100xf0000000 - 0xf7ffffff (0x8000000) MX[B](B)
[13] -100xed000000 - 0xedffffff (0x1000000) MX[B](B)
[14] -100x0000ffff - 0x0000ffff (0x1) IX[B]
[15] -100x00000000 - 0x000000ff (0x100) IX[B]
[16] -100x0000b000 - 0x0000b01f (0x20) IX[B]
[17] -100x0000b400 - 0x0000b4ff (0x100) IX[B]
[18] -100x0000b800 - 0x0000b8ff (0x100) IX[B]
[19] -100x0000e800 - 0x0000e81f (0x20) IX[B]
[20] -100x0000f000 - 0x0000f00f (0x10) IX[B]
[21] -100x0000d000 - 0x0000d01f (0x20) IX[B]
[22] -100x0000d400 - 0x0000d41f (0x20) IX[B]
[23] -100x0000d800 - 0x0000d81f (0x20) IX[B]
(II) resource ranges after probing:
[0] -100xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -100x00100000 - 0x1fffffff (0x1ff00000) MX[B]E(B)
[2] -100x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -100x000c0000 - 0x000effff (0x30000) MX[B]
[4] -100x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -100xee800000 - 0xee800fff (0x1000) MX[B]
[6] -100xec000000 - 0xec0000ff (0x100) MX[B]
[7] -100x20000000 - 0x200003ff (0x400) MX[B]
[8] -100xec800000 - 0xec8003ff (0x400) MX[B]
[9] -100xf8000000 - 0xf7ffffff (0x0) MX[B]O
[10] -100xef000000 - 0xef000fff (0x1000) MX[B](B)
[11] -100xefff0000 - 0xefffffff (0x10000) MX[B](B)
[12] -100xf0000000 - 0xf7ffffff (0x8000000) MX[B](B)
[13] -100xed000000 - 0xedffffff (0x1000000) MX[B](B)
[14] 000x000a0000 - 0x000affff (0x10000) MS[B]
[15] 000x000b0000 - 0x000b7fff (0x8000) MS[B]
[16] 000x000b8000 - 0x000bffff (0x8000) MS[B]
[17] -100x0000ffff - 0x0000ffff (0x1) IX[B]
[18] -100x00000000 - 0x000000ff (0x100) IX[B]
[19] -100x0000b000 - 0x0000b01f (0x20) IX[B]
[20] -100x0000b400 - 0x0000b4ff (0x100) IX[B]
[21] -100x0000b800 - 0x0000b8ff (0x100) IX[B]
[22] -100x0000e800 - 0x0000e81f (0x20) IX[B]
[23] -100x0000f000 - 0x0000f00f (0x10) IX[B]
[24] -100x0000d000 - 0x0000d01f (0x20) IX[B]
[25] -100x0000d400 - 0x0000d41f (0x20) IX[B]
[26] -100x0000d800 - 0x0000d81f (0x20) IX[B]
[27] 000x000003b0 - 0x000003bb (0xc) IS[B]
[28] 000x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Option "NvAGP" "1"
(**) NVIDIA(0): Use of NVIDIA internal AGP requested
(--) NVIDIA(0): Linear framebuffer at 0xF0000000
(--) NVIDIA(0): MMIO registers at 0xED000000
(EE) NVIDIA(0): Failed to load the NVIDIA kernel module!
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(EE) Screen(s) found, but none have a usable configuration.
|
module IS loaded into memory, everything works fine on 'Frozen hell' (same xorg, same nvidia driver version, same kernel .config).
(i cannot check 766x drivers, since they gave up Quadro 1/2 support). |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Mon Jul 04, 2005 9:09 pm Post subject: |
|
|
my best bet is that the older nvidia drivers cant take the recently happening changes
in the development trees being merged into mainline anytime soon....
Sorry i cant be much of help, but i cant see any kernel-side error in your debug output.... :S
T
_________________
Retired gentoo user |
|
| Back to top |
|
|
Cinder6
l33t
Joined: 05 Aug 2004
Posts: 767
Location: California
|
| Posted: Mon Jul 04, 2005 11:47 pm Post subject: |
|
|
Tiger, I am using K8T800Pro, so I am afraid I can't be of much help with NF4.
_________________
Knowledge is power.
Power corrupts.
Study hard.
Be evil.
Ugly Overload |
|
| Back to top |
|
|
miedo95
n00b
Joined: 21 Apr 2005
Posts: 9
Location: Mexicali, Mexico
|
| Posted: Tue Jul 05, 2005 6:43 am Post subject: SWSUSP2 work ok!!! |
|
|
 SWSUSP2 work, laptop presario 2100 for hibernate-script
_________________
La informacion es poder!!! |
|
| Back to top |
|
|
tagwar
Tux's lil' helper
Joined: 11 Aug 2004
Posts: 147
Location: Karlsruhe
|
| Posted: Tue Jul 05, 2005 6:55 am Post subject: swsusp only kinda workin.. |
|
|
Hi,
first of all, thanks for the new nitro.
I had a hell of a weekend, so I've only tried it on my laptop so far. What I have found is, that I can't get lzf-compression to work with swsusp2. If I disable lzf, everything works fine, but a bit slower than before... is it a pibkac or a bug, I don't know. Perhaps someone can help?
Besides that, I will try it on my ivtv/zaptel box now, so I will return with infos on if these drivers work soon.
Greets
Tom |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Jul 05, 2005 8:24 am Post subject: |
|
|
For those who got swsusp2 working: would you please
post the SWSUSP2 part of your .config so that people who cant get
it working are able to test the working settings?
thx
T
_________________
Retired gentoo user |
|
| Back to top |
|
|
tagwar
Tux's lil' helper
Joined: 11 Aug 2004
Posts: 147
Location: Karlsruhe
|
| Posted: Tue Jul 05, 2005 8:44 am Post subject: swsusp2 |
|
|
.config:
| Code: |
CONFIG_SUSPEND2=y
CONFIG_SUSPEND2_SWAPWRITER=y
CONFIG_SUSPEND2_USERSPACE_UI=y
CONFIG_SUSPEND2_TEXT_MODE=y
CONFIG_SUSPEND2_DEFAULT_RESUME2="/dev/sda2"
CONFIG_SUSPEND2_CHECK_RESUME_SAFE=y
|
It's pretty standard... 
I had to make some changes in /etc/hibernate/hibernate.conf... basically throw away all things about lzf-compression and so....
remember... this is without lzf-compression, so it's a bit slow...  |
|
| Back to top |
|
|
priestjim
Tux's lil' helper
Joined: 09 Jan 2005
Posts: 100
Location: Never never land
|
| Posted: Tue Jul 05, 2005 10:16 am Post subject: |
|
|
Plus there is still the inotify/ntfs problem. Only this time there is no kernel oops. The system just freezes! Totally! Haven't seen one of those since I had Windows installled!
_________________
My soul is my antenna, I am the instrument + the guitar is my amplifier.
-- Ottmar Liebert |
|
| Back to top |
|
|
ToeiRei
Veteran
Joined: 03 Jan 2005
Posts: 1191
Location: Austria
|
| Posted: Tue Jul 05, 2005 10:36 am Post subject: |
|
|
Reporting Problems with the ipw2100 driver (built as a module):
Needed: Generic IEEE 802.11 Networking Stack (else you can't select the driver)
| Code: |
CC [M] net/ipv4/netfilter/ipt_length.o
CC [M] net/ipv4/netfilter/ipt_ttl.o
drivers/net/wireless/ipw2100.c:6405:45: macro "create_workqueue" requires 2 arguments, but only 1 given
drivers/net/wireless/ipw2100.c: In function `ipw2100_alloc_device':
drivers/net/wireless/ipw2100.c:6405: error: `create_workqueue' undeclared (first use in this function)
drivers/net/wireless/ipw2100.c:6405: error: (Each undeclared identifier is reported only once
drivers/net/wireless/ipw2100.c:6405: error: for each function it appears in.)
make[3]: *** [drivers/net/wireless/ipw2100.o] Error 1
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
|
If you compile the driver into the kernel:
| Code: |
CC fs/reiser4/plugin/node/node40.o
drivers/net/wireless/ipw2100.c:6405:45: macro "create_workqueue" requires 2 arguments, but only 1 given
drivers/net/wireless/ipw2100.c: In function `ipw2100_alloc_device':
drivers/net/wireless/ipw2100.c:6405: error: `create_workqueue' undeclared (first use in this function)
drivers/net/wireless/ipw2100.c:6405: error: (Each undeclared identifier is reported only once
drivers/net/wireless/ipw2100.c:6405: error: for each function it appears in.)
make[3]: *** [drivers/net/wireless/ipw2100.o] Error 1
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
--
LD fs/udf/udf.o
|
same with the ipw2100 package from portage (net-wireless/ipw2100-1.1.0) - with nitro1 they worked.
Rei
_________________
Please stand by - The mailer daemon is busy burning your messages in hell... |
|
| Back to top |
|
|
tagwar
Tux's lil' helper
Joined: 11 Aug 2004
Posts: 147
Location: Karlsruhe
|
| Posted: Tue Jul 05, 2005 10:54 am Post subject: re: ipw2100 |
|
|
Hi,
haven't had that problem with the ipw2100, but I know it from ivtv. A workaround ( I don't know if you're supposed to do it that way!!!) is to edit ipw2100.c and change all occurences of
| Code: | | create_workqueue(foo) |
to
| Code: | | create_workqueue(foo,0) |
that solved it for me...
once again, I don't know if you're supposed to do it like that. I don't know if it will blow up your box... |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Jul 05, 2005 11:34 am Post subject: |
|
|
This is almost impossible, since i have built everything before releasing + i didnt change anything in the ipw drivers.
Anyways, the tagwar's workaround is totally correct.
For such breakage, you guys should say thanks to SWSUSP2-guys who think they could shamelessly
change the internal kernel API without any repercussions.
This is one of the reasons why SWSUSP2 is broken by design and will _never_
make it into mainstream....
cheers
T
_________________
Retired gentoo user
Last edited by Tiger683 on Tue Jul 05, 2005 11:36 am; edited 1 time in total |
|
| Back to top |
|
|
ToeiRei
Veteran
Joined: 03 Jan 2005
Posts: 1191
Location: Austria
|
| Posted: Tue Jul 05, 2005 11:36 am Post subject: |
|
|
This part in ipw2100.c should take care of it.
| Code: |
#ifdef CONFIG_SOFTWARE_SUSPEND2_BUILTIN
priv->workqueue = create_workqueue(DRV_NAME, 0);
#else
priv->workqueue = create_workqueue(DRV_NAME);
#endif
|
I left out software-suspend first. Think I should switch from newspaper to source code.
Rei
_________________
Please stand by - The mailer daemon is busy burning your messages in hell... |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Jul 05, 2005 11:39 am Post subject: |
|
|
I am sure there is something REALLY wrong going on in the swsusp2 patches lately...
might be the second time they forgot that they've changed the config name
and still use the deprecated one in #ifdefS.
interesting....
_________________
Retired gentoo user |
|
| Back to top |
|
|
ToeiRei
Veteran
Joined: 03 Jan 2005
Posts: 1191
Location: Austria
|
| Posted: Tue Jul 05, 2005 12:07 pm Post subject: |
|
|
agreed, Tiger...
For me it looks like they do not really test those patches. But with some tweaking we'll be able to fix nearly everything here.
Good distro, good people, great sources.
Rei
_________________
Please stand by - The mailer daemon is busy burning your messages in hell... |
|
| Back to top |
|
|
notz
n00b
Joined: 31 Aug 2004
Posts: 15
Location: Graz, Austria
|
| Posted: Tue Jul 05, 2005 1:19 pm Post subject: |
|
|
great work tiger!!
but please update the sk98lin driver to the latest 8.23 (released on 30.6).
my network card only works with driver version >= 8.18 (beta) |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Jul 05, 2005 2:10 pm Post subject: |
|
|
will do
T
PS: im probably back on internet@home... but next two weeks with very limited bandwidth...
Enough though to download patches and monitor kernel.org etc....
_________________
Retired gentoo user |
|
| Back to top |
|
|
miedo95
n00b
Joined: 21 Apr 2005
Posts: 9
Location: Mexicali, Mexico
|
| Posted: Tue Jul 05, 2005 2:49 pm Post subject: SWSUSP2 Compressor lzf enable |
|
|
| Code: |
- SUSPEND core : 2.1.9.5
- Kernel Version : 2.6.12-nitro2
- Compiler vers. : 3.4
- Attempt number : 2
- Pageset sizes : 8849 (8849 low) and 37754 (37754 low).
- Parameters : 0 0 0 0 0 5
- Calculations : Image size: 46808. Ram to suspend: 1162.
- Limits : 114416 pages RAM. Initial boot: 111710.
- Overall expected compression percentage: 0.
- Compressor lzf enabled.
Compressed 190885888 bytes into 92457676 (51 percent compression).
- Swapwriter active.
Swap available for image: 124501 pages.
- Preemptive kernel.
- Max extents used: 8
- I/O speed: Write 48 MB/s, Read 18 MB/s.
|
----------------------------- ------------------------
active in kernel
------>Cryptographic API
<*> -------> LZF compression algorithm
_________________
La informacion es poder!!! |
|
| Back to top |
|
|
tagwar
Tux's lil' helper
Joined: 11 Aug 2004
Posts: 147
Location: Karlsruhe
|
| Posted: Tue Jul 05, 2005 3:00 pm Post subject: Re: SWSUSP2 Compressor lzf enable |
|
|
| miedo95 wrote: |
----------------------------- ------------------------
active in kernel
------>Cryptographic API
<*> -------> LZF compression algorithm |
aargh... damn... I must've had tomatoes on my eyes... Thanks a lot!!
Once again it is prooved, that reading gentoo-forums is more effective than try and error...  |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Jul 05, 2005 3:31 pm Post subject: |
|
|
Regarding ipw2100:
| ipw2100_fix_sws2_workqueues-12_nitro2.patch wrote: | | Code: |
diff -pruN linux-2.6.12-nitro2_orig/drivers/net/wireless/ipw2100.c linux-2.6.12-nitro2/drivers/net/wireless/ipw2100.c
--- linux-2.6.12-nitro2_orig/drivers/net/wireless/ipw2100.c 2005-06-30 16:30:27.000000000 +0200
+++ linux-2.6.12-nitro2/drivers/net/wireless/ipw2100.c 2005-07-05 17:22:43.000000000 +0200
@@ -6399,11 +6399,9 @@ static struct net_device *ipw2100_alloc_
INIT_STAT(&priv->fw_pend_stat);
-#ifdef CONFIG_SUSPEND2
priv->workqueue = create_workqueue(DRV_NAME, 0);
-#else
- priv->workqueue = create_workqueue(DRV_NAME);
-#endif
+
+
INIT_WORK(&priv->reset_work,
(void (*)(void *))ipw2100_reset_adapter, priv);
INIT_WORK(&priv->security_work,
|
|
cheers,
T
_________________
Retired gentoo user |
|
| Back to top |
|
|
ToeiRei
Veteran
Joined: 03 Jan 2005
Posts: 1191
Location: Austria
|
| Posted: Tue Jul 05, 2005 3:39 pm Post subject: |
|
|
thanks, tiger - that was simmilar to the way I fixed it in the external ipw2100 ebuild
Rei
_________________
Please stand by - The mailer daemon is busy burning your messages in hell... |
|
| Back to top |
|
|
Tiger683
Veteran
Joined: 08 Jan 2005
Posts: 1347
Location: Heffner's House
|
| Posted: Tue Jul 05, 2005 5:30 pm Post subject: |
|
|
So:
since there won't be much happening in the world of 2.6.12 from now on, i wanted to ask what you people would like better:
A) continue the 2.6.12 branch of nitro, starting some things from scratch -> removing a few troublemaking patches
which basically dont bring any visible gain
B) take a look at 2.6.13-rc and start a little more carefully than with previous releases to avoid total breakage
As usual: It'S your choice guys
_________________
Retired gentoo user |
|
| Back to top |
|
|
Zephyrus
Apprentice
Joined: 01 Sep 2004
Posts: 204
|
| Posted: Tue Jul 05, 2005 6:07 pm Post subject: |
|
|
| Tiger683 wrote: | Would the ppl with NFORCE4 problem try this temporary maybe-fix:
add the
to your kernel boot parameters in grub/lilo .....
i hope it helps *hopes*
Cinder6: what chipset do you have?
cheers
T |
I've tried to boot with that parameter, but i've got the same errors as before.
I don't know if this is a useful information, but i'm able to boot with 2.6.12-cko. |
|
| Back to top |
|
|
r0bertz
Retired Dev
Joined: 13 Sep 2004
Posts: 257
Location: HKSAR,China
|
| Posted: Tue Jul 05, 2005 6:10 pm Post subject: |
|
|
also check my most recent post on my blog
there is an analysis of this problem
http://zhllg.blogspot.com
| ToeiRei wrote: |
| Code: |
drivers/net/wireless/ipw2100.c:6405:45: macro "create_workqueue" requires 2 arguments, but only 1 given
drivers/net/wireless/ipw2100.c: In function `ipw2100_alloc_device':
drivers/net/wireless/ipw2100.c:6405: error: `create_workqueue' undeclared (first use in this function)
drivers/net/wireless/ipw2100.c:6405: error: (Each undeclared identifier is reported only once
drivers/net/wireless/ipw2100.c:6405: error: for each function it appears in.)
make[3]: *** [drivers/net/wireless/ipw2100.o] Error 1
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
|
|
|
|
| Back to top |
|
|
|
Unsupported Software
