Re: corrupted kernel module files with 2.6.18-3 on ext3
On Wednesday 20 December 2006 18:08, Gudjon I. Gudjonsson wrote: > Sorry, I may be wrong but is it possible that you have installed libattr1 > 2.4.35? The problems seem similar to the problems I saw on my computers a > few days ago. The problem has been fixed with an emergency release of > libattr1. Thanks Gudjon, an libattr1 update solved (all) the problems . Mzzl Henk > > /Gudjon > > Þann Miðvikudagur 20. desember 2006 17:50 skrifaði henk: > > On Tuesday 19 December 2006 21:20, Stephen Olander Waters wrote: > > > I've run into this weird filesystem and/or kernel problem where my > > > kernel module files get corrupted (they live on my root partition). > > > > > > This is my root partition. To fix it (temporarily) I boot into rescue > > > mode, shutdown networking and various daemons, unmount other > > > filesystems, and issue "mount -o ro,remount /" to remount / readonly. I > > > run fsck on it and it fixes the problems, though sometimes the modules > > > are deleted and I have to reinstall the kernel package. > > > > > > Has anyone else noticed this? Should I just file a debian bug and > > > forget about it or should I report it to the ext3 maintainers or...? > > > > At work I have a sid i386 with the same sort of problem. > > ls works, ls -l gives an error message. > > On top of that I can't login into KDE, can't open new files with KDE > > programs under gnome. > > I can still work with the box, but it is sub-optimal. > > Didn't have the time to look into it, but yes i have noticed it. > > > > Mzzl > > Henk
Re: corrupted kernel module files with 2.6.18-3 on ext3
On Tuesday 19 December 2006 21:20, Stephen Olander Waters wrote: > I've run into this weird filesystem and/or kernel problem where my > kernel module files get corrupted (they live on my root partition). > > This is my root partition. To fix it (temporarily) I boot into rescue > mode, shutdown networking and various daemons, unmount other > filesystems, and issue "mount -o ro,remount /" to remount / readonly. I > run fsck on it and it fixes the problems, though sometimes the modules > are deleted and I have to reinstall the kernel package. > > Has anyone else noticed this? Should I just file a debian bug and > forget about it or should I report it to the ext3 maintainers or...? At work I have a sid i386 with the same sort of problem. ls works, ls -l gives an error message. On top of that I can't login into KDE, can't open new files with KDE programs under gnome. I can still work with the box, but it is sub-optimal. Didn't have the time to look into it, but yes i have noticed it. Mzzl Henk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: One more time, openoffice :)
On Thursday 21 September 2006 17:41, Emmanuel Fleury wrote: > Rafael Rodríguez wrote: > > Hi, > > > > there are experimental ubuntu amd64-native packages for OpenOffice > > according to [1]. Apart from that, a couple of days ago non-official > > packages (re-built from the debian unstable sources) were posted in this > > list, but I haven't had the time to test them quite a lot. In fact, I > > have a bug: the first time I start OpenOffice, it crashes, but the > > second time it works... ?¿ > > By now, you do not need to modify anymore the debian/rules file. The > amd64 architecture is compiling fine automatically and produce all the > needed packages. > > But the software is still quite unstable and need to be tested and > debugged. > > > Anyway, anyone knows the state of the former and the latter, or the > > plans? Rene, are you alive? ;) > > I guess now it's building fine and we need to fix all these pointers > problems (last time I ran it I was hitting a double free problem). > > Just to recall the process to compile it: > > First of all, few links about OpenOffice: > http://www.openoffice.org/ > http://wiki.services.openoffice.org/wiki/Porting_to_x86-64_(AMD64,_EM64T) > http://openoffice.debian.net/ > http://packages.qa.debian.org/o/openoffice.org.html > > Preparing to compile (to be done once): > > 1) Add the following line to your /etc/apt/sources.list: > deb-src ftp://ftp.debian.org/debian/ experimental main contrib > > 2) Update: > su -c 'apt-get update' > > 3) Get the packages needed to compile openoffice.org: > su -c 'apt-get build-dep -t experimental openoffice.org' > > Note: The package boost-build is needed but might not be in the list > of the build-dep (install it by hand if needed) At this point i get: c64:~# apt-get install -t experimental boost-build Reading package lists... Done Building dependency tree... Done boost-build is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. c64:~# apt-get build-dep -t experimental openoffice.org Reading package lists... Done Building dependency tree... Done E: Build-dependencies for openoffice.org could not be satisfied. Any ideas? Mzzl Henk > > Once you got all these done, we can get the source and compile it: > > 1) Get the source from the experimental Debian repository (getting the > sources from the experimental makes it sure to track bugs on the very > last version): apt-get source -t experimental openoffice.org > > 2) Move to the build directory: cd openoffice-* > > 3) Build the package (this might take quite a while): > dpkg-buildpackage -rfakeroot -us -uc > > Regards > -- > Emmanuel Fleury | Office: 261 > Associate Professor, | Phone: +33 (0)5 40 00 69 34 > LaBRI, Domaine Universitaire | Fax: +33 (0)5 40 00 66 69 > 351, Cours de la Libération | email: [EMAIL PROTECTED] > 33405 Talence Cedex, France | URL: http://www.labri.fr/~fleury
Re: fglrx: 3d-Acceleration still slow
Op zaterdag 5 augustus 2006 15:07, schreef Hans-J. Ullrich: > Hi all, > > I still have the problem, that although my fglrx-driver is correctly > installed (and 3D-functions are active) , the acceleration is still slow. > > fgl_glxgears is running, the cube and the wheel is shown, but the framerate > is about 50 FPS (sgould be much much higher !) > > glxgears -printfps > > shows > glxgears -printfps > 300 frames in 5.0 seconds = 59.905 FPS > 297 frames in 5.0 seconds = 59.396 FPS > 297 frames in 5.0 seconds = 59.396 FPS > > glxinfo |grep glx shows this: > > glxinfo |grep glx > server glx vendor string: SGI > server glx version string: 1.2 > server glx extensions: > client glx vendor string: ATI > client glx version string: 1.3 > client glx extensions: > > > And fglrxinfo shows this: > fglrxinfo > display: :0.0 screen: 0 > OpenGL vendor string: ATI Technologies Inc. > OpenGL renderer string: MOBILITY RADEON X700 Generic > OpenGL version string: 2.0.5946 (8.27.10) > > Finally glxinfo |grep direct shows this: > > glxinfo |grep direct > direct rendering: Yes > > IMO everything looks fine, but there is something, which is breaking > (braking ?) the system. What could that be ? Is there a difference between > AGP and PCIE ? > > I googled, and someone wrote about wrong MTRR. O.k., checked this: > > cat /proc/mtrr > reg00: base=0x ( 0MB), size=1024MB: write-back, count=1 > reg01: base=0xc800 (3200MB), size= 128MB: write-combining, count=1 > > This seems o.k., too ! (I have a 1GB-machine) > > Kernel an system is 64-bit, with installed ia32-libs. > > Please look at lspci: > > lspci > 00:00.0 Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 01) > 00:02.0 PCI bridge: ATI Technologies Inc RS480 PCI-X Root Port > 00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge > 00:07.0 PCI bridge: ATI Technologies Inc Unknown device 5a39 > 00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller > 00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller > 00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller > 00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 11) > 00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE > Controller ATI > 00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge > 00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge > 00:14.5 Multimedia audio controller: ATI Technologies Inc IXP SB400 AC'97 > Audio Controller (rev 02) > 00:14.6 Modem: ATI Technologies Inc ATI SB400 - AC'97 Modem Controller (rev > 02) > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > HyperTransport Technology Configuration > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > Address Map > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > DRAM Controller > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] > Miscellaneous Control > 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility > X700 (PCIE) > 06:05.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] > 802.11g Wireless LAN Controller (rev 02) > 06:06.0 CardBus bridge: Texas Instruments PCIxx21/x515 Cardbus Controller > 06:06.2 FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 > Host Controller > 06:06.3 Mass storage controller: Texas Instruments PCIxx21 Integrated > FlashMedia Controller > 06:06.4 Class 0805: Texas Instruments PCI6411, PCI6421, PCI6611, PCI6621, > PCI7411, PCI7421, PCI7611, PCI7621 Secure Digital (SD) Controller > 06:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 > Gigabit Ethernet (rev 10) > > > I do not know, where I have to look now. I suppose, there is either a > kernel-problem (the kernel agp-gart is not compiled!) or a configuration > mismatch. > > This is the part of xorg.conf. It doesn`t change anything, if I comment the > lines in or out: > > Section "Device" > Identifier "ATI X700" > Driver "fglrx" > Option "UseInternalAGPGART" "yes" > Option "KernelModuleParm" "agpclock=0" > Option "VideoOverlay" "on" > Option "OpenGLOverlay" "on" > Option "no_accel" "no" > Option "no_dri""no" > BusID "PCI:1:0:0" > # Option "Stereo" "off" > # Option "FSAAenable" "0" > # Option "UseFastTLS" "0" > # #VideroRam 65536 > > > I hope with this bunch of informations someone might have a clue. > > Thanks for any help ! > > best regards > > Hans > > P.S. Yes, I know: ATI sux ! But this notebook was exchanged by the > manufacturer as guarantee ( I former had a NVidia-card on it) , but the > manufacturer does no more built notebooks with NVidia-cards. And what about: lsmod|grep fglrx -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EM
