2.6.7-love8 aka back from the hols

Message

boroshan · Post by **boroshan** » Sat Jul 10, 2004 6:08 pm

All right,

I rebuilt the R4 file system containing my root partition, and tried to reboot

I still can't boot from it - it says it can't load the interpreter, prompts for a run level, and then says there are no more processes for that runlevel. If I try to chroot into it, I get

Code: Select all

/bin/bash: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Error 28

So: qpkg reveals that the file belongs to glibc, and both /lib/libdl.so.2 and the file to which it points exist on the partition. I'd look up error 28 if I was sure what generated it

I'm busy updating my R3 partition using the distfiles from R4. If anyone has an easy way to salvage my R4 root, I'd greatly apprecieate it.

HydroSan · Post by **HydroSan** » Sat Jul 10, 2004 7:07 pm

I've managed to trace my lockups on boot not to Bootsplash, but to the USB section of bootup. It seems to hang when I boot up right at that section. Fortunately, unplugging my mouse during then and plugging it back in during the init scripts seems to work but... wtf?

All modules are compiled in. Any suggestions?

HydroSan · Post by **HydroSan** » Sat Jul 10, 2004 7:31 pm

Okay, a little update. I looked again at my dmesg and it stalled right near where it appears to be loading the USB Printer section. So I disabled that, and all is good with Love.

However, a quick question. For RENICING, so I do that every time when I boot up, or do I just do it once? Also, would I have to do it for each Reiser4 partition, or would just the once work fine?

Thanks.

TPC · Post by **TPC** » Sat Jul 10, 2004 7:36 pm

The Love-Sources crew had a staff meeting. Here is the log for anyone who is interested:

http://www.love-sources.org/info/love-s ... eeting.txt

Isaiah · Post by **Isaiah** » Sat Jul 10, 2004 7:52 pm

tatesworld wrote:dont forget to

renice -10 `pidof X`

from the man himself with those new np patches apparantly

This is a bit confusing - what happened to doing "pgrep hdb7 | xargs renice -19"

boroshan · Post by **boroshan** » Sat Jul 10, 2004 8:31 pm

This is a bit confusing - what happened to doing "pgrep hdb7 | xargs renice -19"

Different issue - renice X to make`sure the desktop is responsive - else you may get lags. Renice the reiser4 demons to get around some lockup problems. the R4 processes should be reniced to a higher priority (ie a more negative number) or it won't work. Don't ask me why as to that last bit...

Ignis · Post by **Ignis** » Sat Jul 10, 2004 8:55 pm

hey, I have a problem loading the kernel, it's something with vesa frame buffer, but I don't really know what it is

when loading somethng like this appears and it stops, and freezes

Code: Select all

<6>note Vesafb[27] exited with preempt_count2

Should I try 8kb kernel stackings? or that has nothing to do with it?
I have an nVidia RIVA TNT 2
Please, help

Psiuyo · Post by **Psiuyo** » Sat Jul 10, 2004 10:00 pm

I'm having trouble doing anything with the latest love... when I use any make command it craps out with the following:

Code: Select all

HOSTCC  scripts/basic/fixdep
In file included from /usr/include/bits/posix1_lim.h:130,
                 from /usr/include/limits.h:144,
                 from /usr/lib/gcc/i686-pc-linux-gnu/3.4.1/include/limits.h:122,
                 from /usr/lib/gcc/i686-pc-linux-gnu/3.4.1/include/syslimits.h:7,
                 from /usr/lib/gcc/i686-pc-linux-gnu/3.4.1/include/limits.h:11,
                 from scripts/basic/fixdep.c:113:
/usr/include/bits/local_lim.h:36:26: linux/limits.h: No such file or directory
In file included from /usr/include/sys/socket.h:35,
                 from /usr/include/netinet/in.h:24,
                 from scripts/basic/fixdep.c:115:
/usr/include/bits/socket.h:305:24: asm/socket.h: No such file or directory
scripts/basic/fixdep.c: In function `use_config':
scripts/basic/fixdep.c:201: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:201: error: (Each undeclared identifier is reported only once
scripts/basic/fixdep.c:201: error: for each function it appears in.)
scripts/basic/fixdep.c:201: warning: unused variable `s'
scripts/basic/fixdep.c: In function `parse_dep_file':
scripts/basic/fixdep.c:297: error: `PATH_MAX' undeclared (first use in this function)
scripts/basic/fixdep.c:297: warning: unused variable `s'
make[1]: *** [scripts/basic/fixdep] Error 1
make: *** [scripts_basic] Error 2

I suspect this actually has nothing to do with love since no one else is complaining, but I figured maybe someone here could point me in the right direction?
(GCC-3.4.1)

*****EDIT*****
Nevermind, looks like something broke when I emerged the linux26-headers. I re-emerged then (same version) and it seems to have fixed it.

Ignore this post

agrippa_cash · Post by **agrippa_cash** » Sat Jul 10, 2004 10:59 pm

I tried to patch it myself, but I got a rejected hunk so if you do try to include it there will be some work. The patch allows you to use a KVM switch without your wheelmouse wigging out. The bug and patch are described here:http://bugzilla.kernel.org/show_bug.cgi?id=2082.

HomerSimpson · Post by **HomerSimpson** » Sat Jul 10, 2004 11:25 pm

HydroSan wrote:I've managed to trace my lockups on boot not to Bootsplash, but to the USB section of bootup. It seems to hang when I boot up right at that section. Fortunately, unplugging my mouse during then and plugging it back in during the init scripts seems to work but... wtf?

All modules are compiled in. Any suggestions?

I tried to boot 2.6.7-love8, the first time it dumped to the screen during bootup. Somewhere around when cups was starting. The second time it just stalled right after cups started. I didn't think to unplug my printer. I just gave up. It must be a USB thing as apcupsd reported that there was no UPS connected as well before the boot stalled.

I will wait for a fix and stick with rc3 love1 for now

phlashback · Post by **phlashback** » Sun Jul 11, 2004 12:09 am

finally got vesa-tng to work... kinda
need to pass noedid and nocrtc as options, but I am now getting oops win the framebuffer changes
there are too oops's here, the first is when bootsplash sets my other consoles up, and the second when I startx

I am running SMP because I have SMP. so disabling is not an option

also I have to poweroff for a couple minutes, or the system hangs when it initializes the framebuffer after a reboot, displaying the last contents of my screen before the reboot

switching from X back to a Virtual Terminal, I get a hard lock
exiting X causes a hard lock as well and a scrabled Frambuffer

my kernel option is
video=vesafb:vram16,ywrap,mtrr,noedid,nocrtc,1280x1024-16@60

Code: Select all

vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
c00ce395
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in: e100 mii joydev ohci_hcd nvidia amd_k7_agp agpgart evdev snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_rawmidi snd_ac97_codec snd_util_mem snd_hwdep snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_page_alloc snd_timer snd_mixer_oss snd soundcore usbhid usblp visor usbserial usb_storage ehci_hcd usbcore sbp2 raw1394 ohci1394 ieee1394 ide_cd sr_mod cdrom sd_mod sg scsi_mod
CPU:    1
EIP:    0060:[<c00ce395>]    Tainted: P   VLI
EFLAGS: 00010256   (2.6.7-love8)
EIP is at 0xc00ce395
eax: 00004f07   ebx: 00000000   ecx: 00000000   edx: 00000000
esi: 00000000   edi: c0525780   ebp: c00ce395   esp: f6704d0c
ds: 007b   es: 007b   ss: 0068
Process setfont (pid: 8849, threadinfo=f6704000 task=f66bc790)
Stack: c031dca2 00000001 00000000 c19cd800 c19cd808 00007fe6 c0520700 c031a05b
       c19cd808 c19cd800 c183c000 c19cd800 c0312e2d c19cd800 c19cd808 00000360
       00000000 00000000 c183c000 00000000 c02cd100 c183c000 f7fff980 f7fff960
Call Trace:
 [<c031dca2>] vesafb_pan_display+0x62/0xf0
 [<c031a05b>] fb_pan_display+0x5b/0x90
 [<c0312e2d>] fbcon_switch+0x15d/0x270
 [<c02cd100>] redraw_screen+0xd0/0x200
 [<c0313393>] fbcon_do_set_font+0x1d3/0x310
 [<c0313807>] fbcon_font_op+0x337/0x840
 [<c0148e46>] handle_mm_fault+0xf6/0x180
 [<c0119123>] find_busiest_group+0x283/0x310
 [<c027e102>] copy_from_user+0x42/0x80
 [<c02d1c67>] con_font_op+0x187/0x2c0
 [<c02c7d21>] vt_ioctl+0x13e1/0x1b80
 [<c0148e46>] handle_mm_fault+0xf6/0x180
 [<c0116be1>] do_page_fault+0x141/0x511
 [<c0119825>] scheduler_tick+0x145/0x1c0
 [<c02c6940>] vt_ioctl+0x0/0x1b80
 [<c02c053c>] tty_ioctl+0x44c/0x540
 [<c016a01d>] sys_ioctl+0xed/0x252
 [<c0116aa0>] do_page_fault+0x0/0x511
 [<c0105c5d>] sysenter_past_esp+0x52/0x71
Code: c4 f4 94 fd c5 e1 b3 81 97 85 24 6d 2d e8 b3 78 a5 ec 8d 42 90 86 b5 1a 34 e5 d9 99 af 7a a2 4d b3 3c 27 cc bb fc bd c2 dd 5a 25 <12> 0e eb 66 cc 33 2d d9 e1 f4 d9 06 eb 17 de 92 82 01 8d be a2
 <6>bootsplash 3.1.4-2004/02/19: looking for picture.... found (1280x1024, 26385 bytes, v3).
bootsplash: status on console 0 changed to on
bootsplash 3.1.4-2004/02/19: looking for picture.... found (1280x1024, 26385 bytes, v3).
bootsplash: status on console 1 changed to on
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
bootsplash 3.1.4-2004/02/19: looking for picture.... found (1280x1024, 26385 bytes, v3).
bootsplash: status on console 2 changed to on
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
bootsplash 3.1.4-2004/02/19: looking for picture.... found (1280x1024, 26385 bytes, v3).
bootsplash: status on console 3 changed to on
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
bootsplash 3.1.4-2004/02/19: looking for picture.... found (1280x1024, 26385 bytes, v3).
bootsplash: status on console 4 changed to on
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
bootsplash 3.1.4-2004/02/19: looking for picture.... found (1280x1024, 26385 bytes, v3).
bootsplash: status on console 5 changed to on
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found

after startx

Code: Select all

Unable to handle kernel paging request at virtual address ffffffc2
 printing eip:
c00ce400
*pde = 00003067
Oops: 0002 [#2]
SMP
Modules linked in: e100 mii joydev ohci_hcd nvidia amd_k7_agp agpgart evdev snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_rawmidi snd_ac97_codec snd_util_mem snd_hwdep snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_pcm snd_page_alloc snd_timer snd_mixer_oss snd soundcore usbhid usblp visor usbserial usb_storage ehci_hcd usbcore sbp2 raw1394 ohci1394 ieee1394 ide_cd sr_mod cdrom sd_mod sg scsi_mod
CPU:    1
EIP:    0060:[<c00ce400>]    Tainted: P   VLI
EFLAGS: 00010202   (2.6.7-love8)
EIP is at 0xc00ce400
eax: 00000000   ebx: 00000000   ecx: 00000001   edx: 00000000
esi: 00000000   edi: c0525780   ebp: c00ce395   esp: f7fe5eb0
ds: 007b   es: 007b   ss: 0068
Process events/1 (pid: 7, threadinfo=f7fe5000 task=f7f42bd0)
Stack: c031dca2 00000000 00000000 c19cd800 c19cd808 00007f80 c0520790 c031a05b
       c19cd808 c19cd800 f7f16a00 c19cd800 c0312e2d c19cd800 c19cd808 00000400
       00000006 00000006 00000001 00000001 c02cd100 f7f16a00 00000000 00000003
Call Trace:
 [<c031dca2>] vesafb_pan_display+0x62/0xf0
 [<c031a05b>] fb_pan_display+0x5b/0x90
 [<c0312e2d>] fbcon_switch+0x15d/0x270
 [<c02cd100>] redraw_screen+0xd0/0x200
 [<c02c8634>] complete_change_console+0x34/0x100
 [<c02d0474>] console_callback+0xe4/0xf0
 [<c012c513>] worker_thread+0x1a3/0x240
 [<c02d0390>] console_callback+0x0/0xf0
 [<c01198a0>] default_wake_function+0x0/0x20
 [<c01198a0>] default_wake_function+0x0/0x20
 [<c012c370>] worker_thread+0x0/0x240
 [<c01305f7>] kthread+0xb7/0xc0
 [<c0130540>] kthread+0x0/0xc0
 [<c0103eb1>] kernel_thread_helper+0x5/0x14
Code: c6 bc 04 44 96 46 95 48 41 a1 47 2c e4 90 6f 4b 64 ca 4a 23 9d 76 d4 81 e6 46 38 c5 93 61 ba 35 28 70 73 54 38 75 6d 94 f3 f0 ed <28> 70 c2 e5 d4 2f 69 43 86 c0 0a 58 c0 24 9a 3e 93 83 6d 65 d0

squeegy · Post by **squeegy** » Sun Jul 11, 2004 1:26 am

HomerSimpson wrote:
HydroSan wrote:I've managed to trace my lockups on boot not to Bootsplash, but to the USB section of bootup. It seems to hang when I boot up right at that section. Fortunately, unplugging my mouse during then and plugging it back in during the init scripts seems to work but... wtf?

All modules are compiled in. Any suggestions?
I tried to boot 2.6.7-love8, the first time it dumped to the screen during bootup. Somewhere around when cups was starting. The second time it just stalled right after cups started. I didn't think to unplug my printer. I just gave up. It must be a USB thing as apcupsd reported that there was no UPS connected as well before the boot stalled.

I will wait for a fix and stick with rc3 love1 for now

Hello fellow Ohioan, I'm not using love, but I'm using a mm7 based kernel. And in order for me to get it to work, without locking at cupsd, I had to reverse bk-acpi.patch, (and possibly bk-usb.patch, this was for a keyboard issue). You can get the patches here.

just download and patch -p1 -R < bk-acpi.patch

please let me know the results.

nmcsween · Post by **nmcsween** » Sun Jul 11, 2004 1:31 am

Any chance love9 can get swsusp2 in there? Would really help out my desktop by not having to power down every night.

X-Ryl669 · Post by **X-Ryl669** » Sun Jul 11, 2004 11:57 am

Finally got USB working by reversing bk-usb patch.

Vesatng doesn't work for me (even with noedid & nocrtc options).
I've a laptop, previous vesa fb worked nicely before, I don't know how I could fix this.

oberyno · Post by **oberyno** » Sun Jul 11, 2004 12:12 pm

Any chance of bringing back badram? I've got 4k of bad ram which of course screws up everything. I tried patching it myself, but had no idea what I was doing trying to fix the reject.

spiralvoice · Post by **spiralvoice** » Sun Jul 11, 2004 4:19 pm

Hi,

SB AWE32 ISA PNP modules seems not to load during boot
[EDIT]I just tested gentoo-dev-sources-2.6.7-r9 and snd_sbawe works with the same kernel config[/EDIT]

pnp: Device 00:01.00 activated.
Unable to handle kernel NULL pointer dereference at virtual address 000000b8
printing eip:
c010c19c
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: snd_sbawe snd_opl3_lib snd_sb16_dsp snd_pcm snd_page_alloc snd_timer snd_
sb16_csp snd_sb_common snd_hwdep snd_mpu401_uart snd_rawmidi snd usbcore ntfs hpfs nls_iso88
59_1 nls_cp437 vfat fat nls_base sbp2 ieee1394 rtc unix
CPU: 0
EIP: 0060:[<c010c19c>] Not tainted VLI
EFLAGS: 00010213 (2.6.7-love8)
EIP is at dma_alloc_coherent+0x1c/0x100
eax: 00000000 ebx: ffffffff ecx: 0000001f edx: 00010000
esi: 00010000 edi: c15b0998 ebp: 000002d0 esp: dfcdde10
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 5326, threadinfo=dfcdc000 task=c159cbb0)
Stack: 00000003 dfcdde48 0000002c 00010000 00000004 00010000 c15b0998 00020000
e0866389 00000000 00010000 c15b09a8 000002d0 c15b09a4 00010000 e0866587
00000000 00010000 c15b09a8 00010000 00010000 c15b09a4 e08febf0 c15b0998
Call Trace:
[<e0866389>] snd_malloc_dev_pages+0x59/0x80 [snd_page_alloc]
[<e0866587>] snd_dma_alloc_pages+0xc7/0xd0 [snd_page_alloc]
[<e08febf0>] preallocate_pcm_pages+0x60/0x90 [snd_pcm]
[<e08fef47>] snd_pcm_lib_preallocate_pages1+0xc7/0xd0 [snd_pcm]
[<e08ff034>] snd_pcm_lib_preallocate_pages_for_all+0x44/0x70 [snd_pcm]
[<e087b665>] snd_sb16dsp_pcm+0x135/0x160 [snd_sb16_dsp]
[<e08751b7>] snd_sb16_probe+0x1b7/0x5f0 [snd_sbawe]
[<e087a9e0>] snd_sb16dsp_interrupt+0x0/0x1b0 [snd_sb16_dsp]
[<e093b3b4>] snd_sb16_pnp_detect+0x54/0x70 [snd_sbawe]
[<c01a6239>] card_probe+0x79/0xe0
[<c01a69f1>] pnp_register_card_driver+0x91/0xb0
[<e08755f0>] snd_sb16_probe_legacy_port+0x0/0x90 [snd_sbawe]
[<e08756cb>] alsa_card_sb16_init+0x4b/0xf0 [snd_sbawe]
[<e08755f0>] snd_sb16_probe_legacy_port+0x0/0x90 [snd_sbawe]
[<c012eba9>] sys_init_module+0x119/0x230
[<c0105deb>] syscall_call+0x7/0xb
Code: ff ff ff 51 e8 d6 08 09 00 59 e9 68 ff ff ff 55 57 56 53 83 ec 10 bb ff ff ff ff 8b 4c 24 28 8b 44 24 24 8b 6c 24 30 49 c1 e9 0b <8b> b0 b8 00 00 00 89 4c 24 0c 8d 76 00 8d bc 27 00 00 00 00 43

bash-2.05b# cat /proc/modules
[...]
snd_ens1371 23048 1 - Live 0xe0943000
snd_ac97_codec 72196 1 snd_ens1371, Live 0xe095a000
snd_sbawe 33467 1 - Loading 0xe093b000
snd_opl3_lib 10432 1 snd_sbawe, Live 0xe092b000
snd_sb16_dsp 11904 1 snd_sbawe, Live 0xe087a000
snd_pcm 96840 2 snd_ens1371,snd_sb16_dsp, Live 0xe08f2000
snd_page_alloc 11688 1 snd_pcm, Live 0xe0866000
snd_timer 25892 2 snd_opl3_lib,snd_pcm, Live 0xe08ea000
snd_sb16_csp 20640 1 snd_sbawe, Live 0xe08a6000
snd_sb_common 15744 3 snd_sbawe,snd_sb16_dsp,snd_sb16_csp, Live 0xe08a1000
snd_hwdep 8804 2 snd_opl3_lib,snd_sb16_csp, Live 0xe086a000
snd_mpu401_uart 7936 1 snd_sbawe, Live 0xe081f000
snd_rawmidi 22400 2 snd_ens1371,snd_mpu401_uart, Live 0xe086e000
snd 51608 14 snd_ens1371,snd_ac97_codec,snd_sbawe,snd_opl3_lib,snd_sb16_dsp,snd_pcm,snd_timer,snd_sb16_csp,snd_sb_common,snd_hwdep,snd_mpu401_uart,snd_rawmidi, Live 0xe0893000

bash-2.05b# grep SND /usr/src/linux/.config | grep -v "#"
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_MPU401_UART=m
CONFIG_SND_OPL3_LIB=m
CONFIG_SND_SBAWE=m
CONFIG_SND_SB16_CSP=y
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_ENS1371=m

bash-2.05b# uname -a
Linux gentoo 2.6.7-love8 #3 Sun Jul 11 17:46:16 CEST 2004 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux

kevnician · Post by **kevnician** » Mon Jul 12, 2004 1:10 am

LinuxRocks wrote:I was using Love 4 still and it worked flawlessly. However, now using this new love (Love Eight) and everythin boots fine and runs good, but when I reboot the machine, I get a Seg Fault in /etc/hotplug/usb.rc line 393: 8932 segmentation fault rmmod ohci-hcd > /dev/null 2>&1

I compiled USB into the kernel instead of as a module and it fixed the issue for me

boroshan · Post by **boroshan** » Mon Jul 12, 2004 1:42 am

well, I rolled everything back to love-2.6.6-r4 on reiser three and it all worked fine.

Then I built love-2.6.7-r7 and that worked under reiser3. Only I mistyped the gubline and booted into my R4 partition -which suddenly worked again.

I'm now using love8 on R4 with no debug stack traces at all and no lockouts. The only problem is bootsplash, which I put down to vesa-tng not playing well with LCDs, laptops, and I expect widescreen laptops in particular.

I can only assume I borked up a configuration somewhere. Still at least its working now

TPC · Post by **TPC** » Mon Jul 12, 2004 2:55 am

boroshan wrote:which I put down to vesa-tng not playing well with LCDs, laptops, and I expect widescreen laptops in particular.

Me and another person on IRC are having problems with vesa-tng.
I have a laptop, and he has a LCD. Something wierd is up with that patch.

Also, Everyone, love-sources is now hosted on sourceforge, check it out

http://love-sources.sf.net or http://www.love-sources.org

Frodg · Post by **Frodg** » Mon Jul 12, 2004 4:27 am

I need a quick fix for the following error:

Code: Select all

[ebuild  N    ] sys-kernel/love-sources-2.6.7-r8  

Do you want me to merge these packages? [Yes/No] y
>>> emerge (1 of 1) sys-kernel/love-sources-2.6.7-r8 to /
>>> md5 src_uri ;-) linux-2.6.7.tar.bz2
>>> md5 src_uri ;-) 2.6.7-mm7.bz2
>>> md5 src_uri ;-) 2.6.7-love8.bz2
>>> Preparing to unpack...
>>> Unpacking source...
>>> Unpacking linux-2.6.7.tar.bz2 to /var/tmp/portage/love-sources-2.6.7-r8/work

bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: Success
        Input file = /usr/portage/distfiles/2.6.7-mm7.bz2, output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

 * Applying 2.6.7-mm7.patch...
patch: **** unexpected end of file in patch
patch: **** unexpected end of file in patch
patch: **** unexpected end of file in patch
patch: **** unexpected end of file in patch
patch: **** unexpected end of file in patch                                                    [ !! ]

 * Please attach /var/tmp/portage/love-sources-2.6.7-r8/temp/2.6.7-mm7.err to any bug you may post.

!!! ERROR: sys-kernel/love-sources-2.6.7-r8 failed.
!!! Function unipatch, Line 513, Exitcode 0
!!! Unable to dry-run patch.

Obviously I can't get any further... I have downloaded fresh linux-2.6.7.tar.bz2 kernel but I still get the same "bzip2: Compressed file ends unexpectedly;" error

Any Ideas?

phlashback · Post by **phlashback** » Mon Jul 12, 2004 5:00 am

# rm /usr/portage/distfiles/2.6.7-love8.bz2
dowload and #cp 2.6.7-love8 /us r/portage/distfiles/
#emerge love-sources --digest

HTH

Ricky · Post by **Ricky** » Mon Jul 12, 2004 5:26 am

LinuxRocks wrote:
Ricky wrote:
TecHunter wrote:i got the similar message...
but it seems everything works fine.
gmichels wrote:Lots of debugging stuff while booting up, although everything looks just fine.
<snip>
Never had anything similar.
ditto
Sounds like you have Sleep-inside-spinlock checking enabled in Kernel Hacking.

Dissable that and see if it does away...

Joe

Cool, that worked! Now that I've actually got useful text in dmesg, I can post about my other problem.

vesafb-tng doesn't seem to want to play nicely with my monitor. Once it kicks in, my monitor blanks out as if it went into sleep mode. The kernel doesn't hang or anything, cuz I can log in blind and start X.

I tried the noedid and nocrtc options and they don't seem to do anything, as well as taking out the video= part altogether. Here's what seem to be the relevant bits from dmesg:

Code: Select all

Kernel command line: root=/dev/hdk3 video=vesafb:mtrr,ywrap,vram:16,noedid,nocrtc,1280x1024-16@60 splash=silent elevator=cfq

Code: Select all

vesafb: ATI Technologies Inc., RG6 , 01.00 (OEM: ATI RADEON)
vesafb: VBE version: 2.0
vesafb: protected mode interface info at c000:49dd
vesafb: pmi: set display start = c00c4a71, set palette = c00c4abd
vesafb: pmi: ports = 9010 9016 9054 9038 903c 905c 9000 9004 90b0 90b2 90b4 
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: total memory: 16777216
vesafb: scrolling: ywrap using protected mode interface, yres_virtual=6553
vesafb: framebuffer at 0xd0000000, mapped to 0xe0880000, size 16384k
fb0: VESA VGA frame buffer device

<snip>

bootsplash 3.1.4-2004/02/19: looking for picture.... silentjpeg size 285204 byte
s, found (1280x1024, 353426 bytes, v3).
vesafb: mode 1400x105016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1400x105016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1600x120016bpp not found
vesafb: mode 1800x144016bpp not found
vesafb: mode 1800x144016bpp not found
Console: switching to colour frame buffer device 153x58

So, basically, it doesn't seem to be paying attention to the resolution I'm passing to it. Any suggestions on what to try? (I got this w/ love7 too, btw) Thanks

Frodg · Post by **Frodg** » Mon Jul 12, 2004 5:48 am

Thanks phlashback

But I get exaclty the same error:

Code: Select all

> Unpacking linux-2.6.7.tar.bz2 to /var/tmp/portage/love-sources-2.6.7-r8/work

bzip2: Compressed file ends unexpectedly;
        perhaps it is corrupted?  *Possible* reason follows.
bzip2: Success
        Input file = /usr/portage/distfiles/2.6.7-mm7.bz2, output file = (stdout)

Any other Ideas ?

Pink · Post by **Pink** » Mon Jul 12, 2004 7:17 am

phlashback wrote:# rm /usr/portage/distfiles/2.6.7-love8.bz2
dowload and #cp 2.6.7-love8 /us r/portage/distfiles/
#emerge love-sources --digest

HTH

Check the link, that is to love7 not love8

Frodg · Post by **Frodg** » Mon Jul 12, 2004 7:33 am

PickledOnion wrote:
Check the link, that is to love7 not love8

Yes - noticed that so I went back to the original link (page 1) and got that one.... I assume it is OK - I have not seen others with this problem.

Still.... thanks

Anything else ?

2.6.7-love8 aka back from the hols

Ack! and thrice ack!

renicing

problem loading

WARNING: Patch Request