Love5 - The Sardine Release

[nepenthe]

Can you put the drivers for the ACX100 (wireless card) in love-sources?

It's not exactly a patch per se, but I'll make one out of it if you would put it in.

It's at acx100.sourceforge.net.

I would love that as well =)

Does someone have an ebuild with those patches in for gcc 3.4?

[neenee]

i compiled it yesterday and apart from the
problem of some video4linux files having
doubled contents, it runs fine.

keep up the good work

[steel300]

Can you put the drivers for the ACX100 (wireless card) in love-sources?

It's not exactly a patch per se, but I'll make one out of it if you would put it in.

It's at acx100.sourceforge.net.

I would love that as well =)

Does someone have an ebuild with those patches in for gcc 3.4?

I'll check the sourceofrge site to see what's going on. If it follows kernel standards, I see no problem with putting it in in the next release.

[IvoryTiger]

Made the mistake of upgrading to module-init-tools-3.0presomething and it broke modprobe so I backed that down. Other than that, nice solid release steel300!

[skion]

Hmm, i'm getting this with the latest release:

Code: Select all

CC [M]  drivers/scsi/sr.o
drivers/scsi/sr.c: In function `get_capabilities':
drivers/scsi/sr.c:889: parse error at end of input
drivers/scsi/sr.c:74: warning: `sr_remove' used but never defined
drivers/scsi/sr.c:97: warning: `sr_packet' used but never defined
make[2]: *** [drivers/scsi/sr.o] Error 1
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2

I'm using gcc version 3.2.3 20030422, maybe thats the problem?

Thanks for all the great builds so far!

[Wedge_]

@skion:

2. drivers/scsi/sr fails to compile. the following patch fixes it:

--- drivers/scsi/sr.c 2004-01-17 10:44:19.773744944 +0100
+++ ../linux-2.6.1-love2/drivers/scsi/sr.c 2004-01-10 19:23:18.000000000 +0100
@@ -798,6 +798,7 @@
if ((buffer[n + 3] & 0x20) == 0) {
/* can't write DVD-RAM media */
cd->cdi.mask |= CDC_DVD_RAM;
+ }
if ((buffer[n + 3] & 0x10) == 0)
/* can't write DVD-R media */
cd->cdi.mask |= CDC_DVD_R;

If the patch won't apply, just do it by hand - you only need to add the "}" in the middle.

[J0rus]

I was getting that SCSI error as well. Went back and looked at the sr.c code from previous 2.6.1_r2-love1 and it showed

Code: Select all

} else

on line 801.
Manually added the above and got a clean complie. Haven't tested the functionality as of yet, but the kernel boots fine and loads the sr module without error...

~J0rus

[Chaosite]

Actually, the ACX100 drivers do have a big down-side: They are not SMP proof 100% yet.

Apparently they run and everything, but there are many possible (and unlikely, but still possible) race conditions.

I think letting go of hyper-threading for a while is better than not having Internet access for a while...

EDIT: Written a informative post in the appropriate section at the love-sources forum. Go and see.

[Strom]

I just would like to say that i succesfully complied and booted using gcc 3.2.3 but w/o SCSI support for i don't need it

[PrakashP]

So, I gave love5 a try, and I don't know why. No lock-ups yet. Not that I want to complain... Whatever steel300 did with mm4, he did it well! Nice.

[skion]

Thanks for the sr.c patch guys! Although i really should have figured that one out by myself

Keep up the good work!

[fschneider]

after compiling I get this one:

if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.1-love5; fi
WARNING: /lib/modules/2.6.1-love5/kernel/fs/nfsd/nfsd.ko needs unknown symbol dnotify_parent

From my .config:

#
# Network File Systems
#
CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_NFSD_V4=y
# CONFIG_NFSD_TCP is not set
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
# CONFIG_SUNRPC_GSS is not set

I don't know why it breaks now, while it worked with love2, but I didn't investigate. I'll take a look at it tomorrow, since it is 2 am.

[Evil Dark Archon]

for some reason if you compile it into the kernel it will work.

[IvoryTiger]

Okay everything works, except, CD audio.

I can verify xmms, kscd can read/play the CD, but I get no audio.

I have both digital and analog outputs running from my cdrom to my SB card. I have verified the sound works both through alsa (aplay in X and at console), and that arts sound works (through the KDE configure panel).

The only error I'm seeing in /var/log/messages is this:

Code: Select all

request_module: failed /sbin/modprobe -- sound-slot-1. error = 256

But I don't know if that even has anything to do with it.

I have tried

amixer set Master 100 unmute
amixer set PCM 100 unmute
amixer set CD 100 unmute

Heck I even fired up alsamixer itself and pushed everything to 100 that I could.

Any suggestions?

[Halanegri]

For those of you who don't know, libaal and reiser4progs have been in portage for over a week.

[cwt137]

I would like to use the love-sources because I have a laptop that could benefit from the igp and powernow patches. It is a compaq 2195us notebook and is very picky in linux. This could be just the kernel I need to get it to work properly. I dont see the love-sources in the portage tree. How do i install this thing?

[puck3d]

acx100 2.6 patch -- http://math.kernelpanic.net/acx100/acx1 ... 0.diff.bz2

Just apply it in the drivers/net/wireless directory and it should apply cleanly, only affects one file in the kernel, works fine for me with all teh past love sources.

[fca]

OK, whats the score with gcc3.4? Currently I'm on 3.2.3. Firstly I'm a bit of a pussy went it comes to upgrading these sorts of core things. What impact if any would it make to the rest of my system i.e. should I emerge -U system/world after upgrading gcc? What's the benefit e.g. a faster kernel?
The other thing is that I've just emerge sync'ed and can't see gcc3.4 anyway (not it /usr/portage/sys-devel/gcc that is)

First of all, it's not in portage yet. I hacked together an ebuild (based on the gcc 3.3 ebuild) and use that.
Second: it is a major upgrade. You wouldn't unmerge gcc 3.2, but there is a C++ binary incompatibility, and many programs which compile with gcc 3.2 / 3.3 do not compile with gcc 3.4 (yet).
Short advice: If you don't like testing out pre-beta versions of a compiler, working around compiler/program bugs, then don't use it. On the other hand, if you want super performance (10% better or so on average AFAICT) then by all means, try it out, see this thread

[Chaosite]

acx100 2.6 patch -- http://math.kernelpanic.net/acx100/acx1 ... 0.diff.bz2

Just apply it in the drivers/net/wireless directory and it should apply cleanly, only affects one file in the kernel, works fine for me with all teh past love sources.

Actually, I've been using this one for quite a while, then I started getting kernel panics related to it in my new install.

So I got a newer version, and it worked.

[steel300]

The acx100 patches will go in the next release. However, there will be a huge disclaimer regarding there use. The code is incomplete, but that's the spirit of love-sources. Experimental ideas thrive here, so in it goes.

[fca]

BTW, I´m now testing reiser4. Seems impressive so far.
Using it as a temp directory now.

[stefanwa]

BTW, I´m now testing reiser4. Seems impressive so far.
Using it as a temp directory now.

I'm using it as my root(!) since 2 days and no problems so far! Performance is really impressive!!

[darkless]

I'm using it as my root(!) since 2 days and no problems so far! Performance is really impressive!!

Damn, you must have ice in your stomach

[TheCoop]

ill probably change my root partiton to reiser4 ina month or so when the code has reasonably stabiised

[stefanwa]

Damn, you must have ice in your stomach

Seems like!!

Of course I did a full backup in advance so I can go back anytime I want to. And it's a fact that I have no single important files on my Linux partitions, so when everything would get lost it won't really matter.
I'm lovin the risk...