yeah we were supposed to get http working a while ago, forgot to pursue itmroconnor wrote:Sounds good rmh, I'll run those commands. Will git-http-fetch work reliably? I have no git access behind my FW.

I'm wondering the same thing. I use VMWare extensively throughout the day, but sadly I can't use 2.6.26 series kernels yet. I'm also not really that good with code, so I would have no idea where to begin to fix this. This is just kinda a Me Too Post... However, I do love the zen-sources kernels, keep up the good work!HecHacker1 wrote: Has anybody got vmware-modules to build with this kernel? It seems proc_root and some other things were removed from 2.6.26. I can build vmware fine with 2.6.25.
ahh I tested the virtualbox modules.... they do compile against .26, I didnt test vmware thoughsedorox wrote:I'm wondering the same thing. I use VMWare extensively throughout the day, but sadly I can't use 2.6.26 series kernels yet. I'm also not really that good with code, so I would have no idea where to begin to fix this. This is just kinda a Me Too Post... However, I do love the zen-sources kernels, keep up the good work!HecHacker1 wrote: Has anybody got vmware-modules to build with this kernel? It seems proc_root and some other things were removed from 2.6.26. I can build vmware fine with 2.6.25.

Code: Select all
CALL scripts/checksyscalls.sh
CC [M] drivers/acpi/toshiba_acpi.o
drivers/acpi/toshiba_acpi.c: In function 'old_driver_emulation_init':
drivers/acpi/toshiba_acpi.c:674: error: implicit declaration of function 'create_proc_info_entry'
make[2]: *** [drivers/acpi/toshiba_acpi.o] Error 1
make[1]: *** [drivers/acpi] Error 2
make: *** [drivers] Error 2well its fixed now... why were you using that on a dell anyway?drescherjm wrote:BTW with 2.6.26-rc3-zen0 the modules would not build because of the toshiba acpi module.
I disabled that module because I have a dell laptop and it compiled fine.Code: Select all
CALL scripts/checksyscalls.sh CC [M] drivers/acpi/toshiba_acpi.o drivers/acpi/toshiba_acpi.c: In function 'old_driver_emulation_init': drivers/acpi/toshiba_acpi.c:674: error: implicit declaration of function 'create_proc_info_entry' make[2]: *** [drivers/acpi/toshiba_acpi.o] Error 1 make[1]: *** [drivers/acpi] Error 2 make: *** [drivers] Error 2
i dont know whats up with hdaps, i asked dodo since he has a TP, but he is being a bum playing with his PSP and hasnt tested it, maybe i forgot to push the branch....mroconnor wrote:I hate to be a pain in the azz with this HDAPS thing but it seems to have stopped working int rc3-zen0. I tried switching from built-in to a module but the module doesn't load. Any ideas?
On another note, did something change in the SATA/PATA code? I recently went to use my DVD drive(which I hardly ever use but needed to rip a CD) and realized that it wasn't recognized. I check to see if there is a /dev/sg0 or something along that line in /dev but nope. It worked fine in the 2.6.25 zen kernels and I pretty sure i havent changed my .config.
As always thanks in advance and Dos Equis to rmh.
Code: Select all
### Gentoo ###
### Available Kernels####
#
### Gentoo ###
root (hd0,0)
title Gentoo Linux Zen-Source 2.6.25-zen2 - STABLE
kernel /boot/vmlinuz-2.6.25-zen2-07807-g099af7b root=/dev/sda3 libata.atapi_enabled=1 combined_mode=libata acpi_sleep=s3_bios,s3_mode udev
#
### Gentoo ###
root (hd0,0)
title Gentoo Linux Zen-Source 2.6.26-rc3-zen0 - EXPERIMENTAL
kernel /boot/vmlinuz-2.6.26-rc3-zen0 root=/dev/sda3 libata.atapi_enabled=1 combined_mode=libata acpi_sleep=s3_bios,s3_mode udev
#
### Gentoo ###
root (hd0,0)
title Gentoo Linux Zen-Source 2.6.26-rc2-zen2-dirty - WORKING
kernel /boot/vmlinuz-2.6.26-rc2-zen2-dirty root=/dev/sda3 libata.atapi_enabled=1 combined_mode=libata acpi_sleep=s3_bios,s3_mode udev
#
Code: Select all
CONFIG_ATA_PIIX
oh its there, cause thats the same driver I usemroconnor wrote:Ok in zen-sources-2.6.25-x I have thisbut I dont see any drivers listed in the CONFIG_ATA section of zen-sources-2.6.26-x. I think that is my issue.Code: Select all
CONFIG_ATA_PIIX
Code: Select all
Symbol: ATA_PIIX [=y] │
│ Prompt: Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support │
│ Defined at drivers/ata/Kconfig:105 │
│ Depends on: ATA && ATA_SFF && PCI │
│ Location: │
│ -> Device Drivers │
│ -> Serial ATA (prod) and Parallel ATA (experimental) drivers (ATA │
│ -> ATA SFF support (ATA_SFF [=y]) 
the mount option delalloc does not exist, so i guess this kernel doesn't have the ext4 git patches.dodo1122 wrote:Ermm, zen has stable patches from ext4-patch-queue. I also think we have delalloc/mballoc support.
dodo
i doubt you will see those patches in zen anymore till they get to stable, i think its pretty stupid for anyone to run unstable filesystems, unstable anything else im all for, but unstable fs's just cause headachesHecHacker1 wrote:the mount option delalloc does not exist, so i guess this kernel doesn't have the ext4 git patches.dodo1122 wrote:Ermm, zen has stable patches from ext4-patch-queue. I also think we have delalloc/mballoc support.
dodo
i'm back to 2.6.25 zen because i need vmware.
this page mentions it, but in another language:
http://209.85.141.104/search?q=cache:YL ... cd=1&gl=us
Code: Select all
_STR(nv)" -D"KBUILD_MODNAME=KBUILD_STR(nvidia)" -c -o /usr/portage/tmp/portage/x11-drivers/nvidia-drivers-1.0.9626/work/NVIDIA-Linux-x86-1.0-9626-pkg0/usr/src/nv/.tmp_nv.o /usr/portage/tmp/portage/x11-drivers/nvidia-drivers-1.0.9626/work/NVIDIA-Linux-x86-1.0-9626-pkg0/usr/src/nv/nv.c
/usr/portage/tmp/portage/x11-drivers/nvidia-drivers-1.0.9626/work/NVIDIA-Linux-x86-1.0-9626-pkg0/usr/src/nv/nv.c:110: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
/usr/portage/tmp/portage/x11-drivers/nvidia-drivers-1.0.9626/work/NVIDIA-Linux-x86-1.0-9626-pkg0/usr/src/nv/nv.c: In function 'nvos_create_alloc':
/usr/portage/tmp/portage/x11-drivers/nvidia-drivers-1.0.9626/work/NVIDIA-Linux-x86-1.0-9626-pkg0/usr/src/nv/nv.c:454: error: 'nv_pte_t_cache' undeclared (first use in this function)
Code: Select all
git pull git://repo.or.cz/r/linux-2.6/zen-sources.gitThen you didn't look very far. There are several passively cooled newer cards on the market. I have an MSI nVidia 8600GT passive, which I'm happy with. It's perfectly fine for occasional gaming, although it won't do Crysis at highest settings.Gentree wrote:Before anyone knocks my card it's a "NV11 [GeForce2 MX400]" . It gives great image and above all is the most recent card I could find without a FAN, ie truely silent.
i have one of those ps2/usb controller adapters as well, is that what you are talking about? i havent used it in a while but psx/ps2 controllers are the best... just post the patch here, come on irc and sent it to us, or e-mail us, we can incorporate itkaosone wrote:sorry if this is a bit offtopic... but if i have a patch for the kernel, that works pretty much only for me i guess (needed to fix an adapter psx->usb, some of my keys where mapped as axis and not to a button)
i use zen sources git, what's the best way to integrate my patch with zen-sources?
i want that every time i checkout my patch is applied to the kernel, and if there are some hunks rejected just being warned so i can fix it up, or something like that.
i'm a noob to git but i'm pretty sure it's totally possible, i just don't know how :\
well, i know that the touchscreen driver does the same type of crap, many touchscreens use the same chip but one on some screen the x axis will be inverted on others the y and on some both are inverted, i will have to dig my adapter out and see if its working or not, if your buttons were mapped to an axis, does that mean you axis were mapped to buttons, we might be able ot modify the patch to be configurable though menuconfig that way anyone could use the patchkaosone wrote:yes, it's a psx2usb adapter. i bought one, and all worked fine except for 3 buttons
with jstest came out the buttons where mapped to an axis and not to a button (well can be a bug of the adapter, i don't know)
i made a quick hack to make these button working, just creating 4 more buttons and remapping the axis to those buttons. i highly doubt this patch can be of any intrest for anyone except me, because is not a fix on the joypad handling codebase, but a dirty remap (probably most of the adapters can work just out of the box)