View previous topic :: View next topic |
Author |
Message |
Gentree Watchman
Joined: 01 Jul 2003 Posts: 5350 Location: France, Old Europe
|
Posted: Tue May 04, 2004 9:30 pm Post subject: |
|
|
Richie wrote: | Bummer, can't start X.
I have a abit nf7-s mobo (nforce2 chipset) and a GeForce4 Ti 4800 SE, I bet one of those make things hard for me. Is the "nforce2-disconnect-quirk.patch.bz2" patch in main kernel now?
I use the nvidia drivers 1.0.5336-r2
The last love-sources I tried was 2.6.4-rc1-love3, works like a charm
Also I noticed that reiser4 isn't in this kernel =/ |
Hi Richie,
did you get your Geforce4 working? I just bought a Ti 4200 before I saw your posting. I hope I have not made a bad choise in love.
Any news? (tips if you did)
Cheers.
PS what were the basic steps to get it running under 2.6.4 love3? I think I still have that one in /boot. |
|
Back to top |
|
|
Master One l33t
Joined: 25 Aug 2003 Posts: 754 Location: Austria
|
Posted: Tue May 04, 2004 10:12 pm Post subject: |
|
|
This is my first try on a love source. I didn't take a closer look until now, as I had no need for it, I was sticking with the gentoo-dev-sources for quite some time. But I am actually setting up a private fileserver using two IT8212F PCI-cards, and I couldn't find the itraid patch, as former links in ITE RAID topics on this board are of no use no more. On my search I came to the love-sources, as the itraid / GigaRaid patch is included.
I just compiled the kernel, at the end I get the following output:
Code: | if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.6-rc3-love3; fi
WARNING: /lib/modules/2.6.6-rc3-love3/kernel/drivers/acpi/button.ko needs unknown symbol acpi_fixed_sleep_button
WARNING: /lib/modules/2.6.6-rc3-love3/kernel/drivers/acpi/button.ko needs unknown symbol acpi_fixed_pwr_button |
I have compiled CONFIG_ACPI_BUTTON=m as the "HOWTO: apcupsd with USB" tells to (this server is supposed to be secured by a APC SmartUPS, I just took a look at the howto, just for kernel preparations, don't know much more about this matter until now).
Anyone any idea what this WARNING message is all about and how to fix it.
BTW I also saw a strange message when trying a "make clean" and "make mrproper" (don't remember it right now), if anyone want's to take a look at getting it smooth. _________________ Las torturas mentales de la CIA |
|
Back to top |
|
|
CaribbeanKnight Apprentice
Joined: 27 Apr 2003 Posts: 240 Location: Earth -> Europe -> Belgium -> Diest
|
Posted: Tue May 04, 2004 11:02 pm Post subject: |
|
|
running fine here too, but i have a quick question..
how can i see what io scheduler i'm running and how do i choose between them..? _________________ ...we ain't shit...
Linux User #353893 |
|
Back to top |
|
|
Skrot Tux's lil' helper
Joined: 06 Oct 2003 Posts: 141 Location: Adelaide, Australia
|
Posted: Wed May 05, 2004 12:06 am Post subject: |
|
|
I tried my first love-sources kernel last night, and at first things seemed like they were going okay. Well, except for the fact that the text in the verbose bootsplash was only in the upper left corner of my screen... But that didn't bother me too much.
I noticed that XMMS was only using like 2-5% of my cpu with this kernel, which I thought was great. But then I also noticed that my computer was pausing for a split second every now and then... I first noticed it when I was watching a DVD (Dimmu Borgir one... *very* good shit ). It doesn't seem like it's load related, because the load while playing a DVD (in totem) isn't too high, and it seemed to be happening somewhat while just sitting idle with no programs open (escept for gaim and whatever gnome has loaded).
Is there a known solution to problems like this? What is it related to?
Cheers _________________ You will release your mind. |
|
Back to top |
|
|
Rainmaker Veteran
Joined: 12 Feb 2004 Posts: 1650 Location: /home/NL/ehv/
|
Posted: Wed May 05, 2004 3:49 am Post subject: |
|
|
it's related to the scheduler (correct me if I'm wrong here), which is one of the most experimental parts in love-sources.. Also the one that makes your kernel "rock like ninja" more then anything else... _________________ If you can't dazzle them with brilliance, baffle them with bullshit. |
|
Back to top |
|
|
JoseJX Retired Dev
Joined: 28 Apr 2002 Posts: 2774
|
Posted: Wed May 05, 2004 5:22 am Post subject: |
|
|
I have an NForce2 Asus A7N8X deluxe and was getting IRQ errors on boot from the OHCI1394 driver. Turns out that I had APIC enabled in the kernel but not in the BIOS. Thought I'd let you know. Thanks for the love. |
|
Back to top |
|
|
Skrot Tux's lil' helper
Joined: 06 Oct 2003 Posts: 141 Location: Adelaide, Australia
|
Posted: Wed May 05, 2004 6:02 am Post subject: |
|
|
Oh yeah... I also got a segfault when I went to reboot and change by to my trusty old 2.6.3-gentoo kernel. It segfaulted in the USB driver someplace. Sorry, but that's all I can say without doing it again... :/ _________________ You will release your mind. |
|
Back to top |
|
|
MadEgg l33t
Joined: 06 Jun 2002 Posts: 678 Location: Netherlands
|
Posted: Wed May 05, 2004 7:53 am Post subject: |
|
|
Everything works except for yet again the bootsplash _________________ Pentium 4 Prescott 3,2 GHz
Asus P4P800 SE, i865PE chipset
1024 MB PC3200 RAM
AOpen Aeolus GeForce 6800 Ultra 256 MB DDR2
Creative Audigy2 ZS
gentoo-sources-2.6.20-r7
nVidia-drivers version 9755 |
|
Back to top |
|
|
t_2199 Tux's lil' helper
Joined: 20 Mar 2004 Posts: 146
|
Posted: Wed May 05, 2004 10:49 am Post subject: |
|
|
Im having some strange behaviour with my Wireless USB Adapter here (CNET) which I cant explain.
Usually it works but sometimes I need to power down my wireless-router and then it works again!
(I even got some kernel-panics)
Code: |
May 5 11:30:03 kiste01 drivers/usb/core/hub.c: USB device not accepting new address (error=-90)
May 5 11:30:03 kiste01 /root/at76c503a/at76c503.c: unable to get descriptor
May 5 11:30:03 kiste01 /root/at76c503a/at76c503.c: unexpected opmode 166
May 5 11:30:03 kiste01 /root/at76c503a/at76c503-fw_skel.c: eth0 disconnecting
May 5 11:30:03 kiste01 /root/at76c503a/at76c503-fw_skel.c: at76c503-rfmd disconnected |
kernel bug ?
Code: |
May 5 11:19:51 kiste01 /root/at76c503a/at76c503-fw_skel.c: using compiled-in firmware
May 5 11:19:51 kiste01 /root/at76c503a/at76c503.c: $Id: at76c503.c,v 1.53 2004/04/16 19:06:02 jal2 Exp $ compiled May $
May 5 11:19:51 kiste01 /root/at76c503a/at76c503.c: firmware version 1.101.2 #84 (fcs_len 4)
May 5 11:19:51 kiste01 /root/at76c503a/at76c503.c: device's MAC 00:08:a1:3b:cf:5e, regulatory domain ETSI (Europe - (Sp$
May 5 11:19:51 kiste01 /root/at76c503a/at76c503.c: registered eth0
May 5 11:19:54 kiste01 init: Entering runlevel: 3
May 5 11:21:45 kiste01 usb 1-2: USB disconnect, address 3
May 5 11:21:45 kiste01 /root/at76c503a/at76c503-fw_skel.c: eth0 disconnecting
May 5 11:21:45 kiste01 dhcpcd[8618]: recvfrom: Network is down
May 5 11:21:45 kiste01 dhcpcd[8618]: sendto: Network is down
May 5 11:21:45 kiste01 ------------[ cut here ]------------
May 5 11:21:45 kiste01 kernel BUG at net/core/dev.c:3040!
May 5 11:21:45 kiste01 invalid operand: 0000 [#1]
May 5 11:21:45 kiste01 PREEMPT SMP
May 5 11:21:45 kiste01 CPU: 0
May 5 11:21:45 kiste01 EIP: 0060:[<c02cbd6f>] Tainted: PFS VLI
May 5 11:21:45 kiste01 EFLAGS: 00010297 (2.6.6-rc3-love3)
May 5 11:21:45 kiste01 EIP is at free_netdev+0x3f/0x50
May 5 11:21:45 kiste01 eax: df655000 ebx: df6556bc ecx: 00000000 edx: 00000003
May 5 11:21:45 kiste01 esi: ffffffff edi: df655220 ebp: 00000296 esp: dfabbe88
May 5 11:21:45 kiste01 ds: 007b es: 007b ss: 0068
May 5 11:21:45 kiste01 Process khubd (pid: 5145, threadinfo=dfaba000 task=dfb24170)
May 5 11:21:45 kiste01 Stack: e0e53c2e df655000 00000400 e0e2214e df655220 e0e2c2e0 df8adc00 df8adc24
May 5 11:21:45 kiste01 e0e220e8 df655220 e0e221ac df655000 dee66a28 e0de410e dee66a28 dee66a28
May 5 11:21:45 kiste01 df647200 dee66a38 e0e2c300 c0211aa6 dee66a38 dee66a60 dee66a38 df8adcd0
May 5 11:21:45 kiste01 Call Trace:
May 5 11:21:45 kiste01 [<e0e53c2e>] at76c503_delete_device+0x1be/0x380 [at76c503]
May 5 11:21:45 kiste01 [<e0e220e8>] at76c50x_disconnect+0x38/0x60 [at76c503_rfmd]
May 5 11:21:45 kiste01 [<e0de410e>] usb_unbind_interface+0x6e/0x70 [usbcore]
May 5 11:21:45 kiste01 [<c0211aa6>] device_release_driver+0x66/0x70
May 5 11:21:45 kiste01 [<c0211be6>] bus_remove_device+0x56/0xa0
May 5 11:21:45 kiste01 [<c0210b99>] device_del+0x59/0xa0
May 5 11:21:45 kiste01 [<c0210bf0>] device_unregister+0x10/0x20
May 5 11:21:45 kiste01 [<e0deb163>] usb_disable_device+0x73/0xc0 [usbcore]
May 5 11:21:45 kiste01 [<e0de4cc4>] usb_disconnect+0xa4/0xf0 [usbcore]
May 5 11:21:45 kiste01 [<e0de73ef>] hub_port_connect_change+0x1cf/0x350 [usbcore]
May 5 11:21:45 kiste01 [<e0de76a3>] hub_events+0x133/0x3d0 [usbcore]
May 5 11:21:45 kiste01 [<e0de7981>] hub_thread+0x41/0xd0 [usbcore]
May 5 11:21:45 kiste01 [<c0118320>] default_wake_function+0x0/0x20
May 5 11:21:45 kiste01 [<e0de7940>] hub_thread+0x0/0xd0 [usbcore]
May 5 11:21:45 kiste01 [<c01021e5>] kernel_thread_helper+0x5/0x10
May 5 11:21:45 kiste01
May 5 11:21:45 kiste01 Code: 80 48 01 00 00 05 00 00 00 05 ac 01 00 00 89 44 24 04 e9 25 6b f4 ff 90 8d 74 26 00 2b 80 $
May 5 11:21:45 kiste01 dhcpcd[8618]: dhcpStop: ioctl SIOCSIFADDR: No such device
May 5 11:21:45 kiste01 dhcpcd[8618]: dhcpStop: ioctl SIOCSIFFLAGS: No such device
|
and another one
Code: |
May 5 11:39:48 kiste01 usbcore: registered new driver at76c503-rfmd
May 5 11:39:56 kiste01 usb 1-2: USB disconnect, address 3
May 5 11:39:57 kiste01 Unable to handle kernel NULL pointer dereference at virtual address 00000000
May 5 11:39:57 kiste01 printing eip:
May 5 11:39:57 kiste01 c01952f6
May 5 11:39:57 kiste01 *pde = 00000000
May 5 11:39:57 kiste01 Oops: 0000 [#1]
May 5 11:39:57 kiste01 PREEMPT SMP
May 5 11:39:57 kiste01 CPU: 0
May 5 11:39:57 kiste01 EIP: 0060:[<c01952f6>] Tainted: PFS VLI
May 5 11:39:57 kiste01 EFLAGS: 00010296 (2.6.6-rc3-love3)
May 5 11:39:57 kiste01 EIP is at sysfs_get_dentry+0x16/0x70
May 5 11:39:57 kiste01 eax: 00000000 ebx: df0bacd0 ecx: ffffffff edx: 00000000
May 5 11:39:57 kiste01 esi: dfd19440 edi: 00000000 ebp: dfd2c400 esp: dfadded8
May 5 11:39:57 kiste01 ds: 007b es: 007b ss: 0068
May 5 11:39:57 kiste01 Process khubd (pid: 5139, threadinfo=dfadc000 task=dfb24710)
May 5 11:39:57 kiste01 Stack: df067e40 df0cf780 00000000 c0175541 dfa219c0 dfa219c0 df0bacd0 df0bac00
May 5 11:39:57 kiste01 c019537b dfd19440 00000000 df0bacd0 e0dfafc0 c0211a68 dfd19440 00000000
May 5 11:39:57 kiste01 df0bacd0 dfd2c4d0 c0211be6 df0bacd0 df0bad28 df0bacd0 dfd2c4d0 c0210b99
May 5 11:39:57 kiste01 Call Trace:
May 5 11:39:57 kiste01 [<c0175541>] destroy_inode+0x51/0x60
May 5 11:39:57 kiste01 [<c019537b>] sysfs_hash_and_remove+0x2b/0x7f
May 5 11:39:57 kiste01 [<c0211a68>] device_release_driver+0x28/0x70
May 5 11:39:57 kiste01 [<c0211be6>] bus_remove_device+0x56/0xa0
May 5 11:39:57 kiste01 [<c0210b99>] device_del+0x59/0xa0
May 5 11:39:57 kiste01 [<c0210bf0>] device_unregister+0x10/0x20
May 5 11:39:57 kiste01 [<e0de73ef>] hub_port_connect_change+0x1cf/0x350 [usbcore]
May 5 11:39:57 kiste01 [<e0de76a3>] hub_events+0x133/0x3d0 [usbcore]
May 5 11:39:57 kiste01 [<e0de7981>] hub_thread+0x41/0xd0 [usbcore]
May 5 11:39:57 kiste01 [<c0118320>] default_wake_function+0x0/0x20
May 5 11:39:57 kiste01 [<e0de7940>] hub_thread+0x0/0xd0 [usbcore]
May 5 11:39:57 kiste01 [<c01021e5>] kernel_thread_helper+0x5/0x10
May 5 11:39:57 kiste01
May 5 11:39:57 kiste01 Code: 0c 00 00 00 00 89 44 24 08 89 54 24 04 e9 23 ff ff ff 8d 76 00 57 31 c0 b9 ff ff ff 53 83 ec 18 8b 54 24 28 89 54 24 08 89 d7 <f2> ae f7 d1 49 31 db 89 d7 89 4c 24 0c eb 1c 0f b6 07 47 89 c2 |
Anyone knows what went wrong ?? |
|
Back to top |
|
|
darksbane n00b
Joined: 15 Apr 2004 Posts: 28 Location: Fredonia, NY
|
Posted: Wed May 05, 2004 8:01 pm Post subject: |
|
|
Code: | ryan@leonhart ryan $ uname -a
Linux leonhart 2.6.6-rc3-love3 #2 Wed May 5 02:10:18 EDT 2004 i686 AMD Athlon(tm) XP 2500+ AuthenticAMD GNU/Linux |
Works beautifully. Even bootsplash this time! I was going to play with win4lin a bit, but I guess I can wait.
Thanks for this release. :) _________________ :wq |
|
Back to top |
|
|
aaearon n00b
Joined: 22 Apr 2004 Posts: 4
|
Posted: Wed May 05, 2004 11:50 pm Post subject: |
|
|
I can't get lirc_atiusb module to compile with love-sources. Im not sure if its love-sources or mm-sources itself.
Code: | mythtv linux # make
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
CC [M] drivers/char/lirc/lirc_atiusb.o
drivers/char/lirc/lirc_atiusb.c: In function `usb_remote_probe':
drivers/char/lirc/lirc_atiusb.c:374: error: structure has no member named `act_altsetting'
make[3]: *** [drivers/char/lirc/lirc_atiusb.o] Error 1
make[2]: *** [drivers/char/lirc] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2
|
|
|
Back to top |
|
|
Rainmaker Veteran
Joined: 12 Feb 2004 Posts: 1650 Location: /home/NL/ehv/
|
|
Back to top |
|
|
|