Re: postgres/shm problem

2001-01-08 Thread Narancs 1
On Mon, 8 Jan 2001, Nils Philippsen wrote: > > #define SHMALL (SHMMAX/PAGE_SIZE*(SHMMNI/16)) /* max shm system wide (pages) > */ > On my machine here, it is 2097152. It should be the same on any Intel IA32 ok thanks for it! I donwanna reboot my computer ;-) 10x4all Narancs v1 - To unsubscribe

Re: postgres/shm problem

2001-01-08 Thread Narancs 1
On Mon, 8 Jan 2001, Nils Philippsen wrote: > /proc/sys/kernel/shmall to "0" (that is the maximum number of SHM segments). yes, powertweak made it wrong. what is the good value for it? thx Narancs v1 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

postgres/shm problem

2001-01-08 Thread Narancs 1
Dear Kernel developers! Lots of things may have changed in 2.4.0-prer., because nor cdrecord neither postgressql do not run because of system v ipc / shm problem. After recompiling cdrecord with the new header files, started working. I'm just recompiling postgres too. /var/log/postgresql.log:

postgres/shm problem

2001-01-08 Thread Narancs 1
Dear Kernel developers! Lots of things may have changed in 2.4.0-prer., because nor cdrecord neither postgressql do not run because of system v ipc / shm problem. After recompiling cdrecord with the new header files, started working. I'm just recompiling postgres too. /var/log/postgresql.log:

Re: postgres/shm problem

2001-01-08 Thread Narancs 1
On Mon, 8 Jan 2001, Nils Philippsen wrote: /proc/sys/kernel/shmall to "0" (that is the maximum number of SHM segments). yes, powertweak made it wrong. what is the good value for it? thx Narancs v1 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: postgres/shm problem

2001-01-08 Thread Narancs 1
On Mon, 8 Jan 2001, Nils Philippsen wrote: #define SHMALL (SHMMAX/PAGE_SIZE*(SHMMNI/16)) /* max shm system wide (pages) */ On my machine here, it is 2097152. It should be the same on any Intel IA32 ok thanks for it! I donwanna reboot my computer ;-) 10x4all Narancs v1 - To unsubscribe

lvm: hw error or misconfig?

2001-01-05 Thread Narancs 1
Dear developers! (sorry for the long mail) We have a compaq proliant server with NO raid and 5 scsi discs: Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: COMPAQ Model: BD00911934 Rev: 3B02 Type: Direct-AccessANSI SCSI revision: 02 bounded together to a volume

agpgart problem on 2.4.0-ac1

2001-01-05 Thread Narancs 1
Dear all! wanted to try the latest stuff, but X fails to start now. dmesg part: Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 93M agpgart: agpgart: Detected an Intel i815 Chipset. Unable to handle kernel NULL pointer dereference at virtual

agpgart problem on 2.4.0-ac1

2001-01-05 Thread Narancs 1
Dear all! wanted to try the latest stuff, but X fails to start now. dmesg part: Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 93M agpgart: agpgart: Detected an Intel i815 Chipset. Unable to handle kernel NULL pointer dereference at virtual

lvm: hw error or misconfig?

2001-01-05 Thread Narancs 1
Dear developers! (sorry for the long mail) We have a compaq proliant server with NO raid and 5 scsi discs: Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: COMPAQ Model: BD00911934 Rev: 3B02 Type: Direct-AccessANSI SCSI revision: 02 bounded together to a volume

Re: so vesafb doesn't work in i815

2000-11-02 Thread Narancs 1
On Thu, 2 Nov 2000, Alan Cox wrote: > > xfree 4.0.1d supports it, but the screen flicker so hard, that is is > > unusable. > > Ah there is a trick to that bit. If you have some i810 stuff then XFree does > funnies if you have DRM enabled. I did disable loading drm/dri module from

so vesafb doesn't work in i815

2000-11-02 Thread Narancs 1
On Thu, 2 Nov 2000, Alan Cox wrote: > > It seems that the i815 is not vesa compliant? > > Cheap! > > The i810 hardware only has limited support for old style linear video modes > so that is quite possible. > Wow! So then I just cannot use this motherboard at all! xfree 3.3.6 , also with the

vesafb doesn't work in 240t10?

2000-11-02 Thread Narancs 1
Dear developers! I used to start vesafb like this: /etc/lilo.conf: vga=317 Now kernel doesn't accept this. it complains that this is not a valid mode id. So what? I want to start the kernel in 1024x768 16 bit How to do it? I've read Doc*/fb/vesafb.txt That is not true now. 10x Narancs v1 -

vesafb doesn't work in 240t10?

2000-11-02 Thread Narancs 1
Dear developers! I used to start vesafb like this: /etc/lilo.conf: vga=317 Now kernel doesn't accept this. it complains that this is not a valid mode id. So what? I want to start the kernel in 1024x768 16 bit How to do it? I've read Doc*/fb/vesafb.txt That is not true now. 10x Narancs v1 -

so vesafb doesn't work in i815

2000-11-02 Thread Narancs 1
On Thu, 2 Nov 2000, Alan Cox wrote: It seems that the i815 is not vesa compliant? Cheap! The i810 hardware only has limited support for old style linear video modes so that is quite possible. Wow! So then I just cannot use this motherboard at all! xfree 3.3.6 , also with the driver

Re: so vesafb doesn't work in i815

2000-11-02 Thread Narancs 1
On Thu, 2 Nov 2000, Alan Cox wrote: xfree 4.0.1d supports it, but the screen flicker so hard, that is is unusable. Ah there is a trick to that bit. If you have some i810 stuff then XFree does funnies if you have DRM enabled. I did disable loading drm/dri module from xf86config/kernel