Re: Bug#279508: Debian AMD64 installer error
I desctibed the detail information about the installation error in bug report 279508. The install image which I used is "sid-amd64-netinst.iso" that was acquired from "http://debian-amd64.alioth.debian.org/install-images/2004-10-22/";. The error will occur either express method or expert method. I can not install Debian AMD64 on my PC whose motherboard is Tyan S4880.
Re: Cool N' Quiet
Am Samstag, 13. November 2004 20:56 schrieb Slava Risenberg: > I've tried to get it working, I mean to lower the CPU frequency > automatically by loading powernow_k8 module, but without any success. > I guess I have to do something else to get it working. Any ideas? > I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. > -- > Slava Risenberg You also need to load the cpufreq_userspace module. Then powernowd works. NoB
Re: FreeBSD 5.3-AMD64 / IntelEM64T
Your post isn't on-topic for this list. Is there a NetBSD AMD64 mailing list? While I'm cluttering the list, I might as well try and help you out. Which bootloader are you using? None of the kernels for the OSes you mention are MultiBoot-compliant, so they all need information passed to them from the bootloaders in different ways. It sounds like the NetBSD kernel is not getting some of the information it requires. If you want to boot NetBSD, Linux, and WinXP on the same machine, you probably want to look into the GRUB bootloader. Please don't reply to the list with your response. -Karl On Tue, 9 Nov 2004 01:28:14 +0200, Count László de Almásy <[EMAIL PROTECTED]> wrote: > I tried to boot my off the CD I made from the 5.3 final release .iso, > and it fails with simply: > > panic: No BIOS smap info from loader! > Uptime: 1s > > Any ideas what the problem is? Installation media for other OSs such > as Debian/AMD64 and Windows XP are able to boot fine on this system. > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: Cool N' Quiet
On Saturday 13 November 2004 11:56, Slava Risenberg wrote: > I've tried to get it working, I mean to lower the CPU frequency > automatically by loading powernow_k8 module, but without any success. > I guess I have to do something else to get it working. Any ideas? > I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. Another thing to note is that some BIOS's (like the one on my COMPAQ R3000 laptop) are broken and don't have the correct frequency table. In order to get it working you have to set the ACPI cpufreq option (CONFIG_X86_ACPI_CPUFREQ). This way the kernel will get the frequency info through ACPI, which is how windoze does it... -Ted
Re: USB-Flash <-> uba?
From rom the changelog of kernel-image-2.6.9-amd64 (2.6.9-2): - Deactivated CONFIG_BLK_DEV_UB So you have to upgrade and then it will work like usual. I did use ub* to mount a usb 2.0 disk and it did not work very reliable. Daniel van Eeden <[EMAIL PROTECTED]> On Sat, 2004-11-13 at 19:29 +0100, zeeman wrote: > Hi! > > I installed a Debian64 on my laptop and it works fine. > > Even the damm acx110 works great with the new snapshot. > > My own vanilla-kernel. No problem. > > But my USB-Flash-Disk behaves very strange: > When I plug it into the USB-port, the kernel tells me that a new device > (uba) is found. > ? > On my i386-box it's called sda. > > Ok, uba or sda. I guess there where no difference in mounting. > But there is a difference: > > There is no /dev/uba1, not even a /dev/uba (The "disk" consists of 2 > Paritions, both vfat, recognized by the i386-box as sda1 and sda2). > > I found uba, uba1 and uba2 only in the /sys-tree. > But there where only informations about the flash-disk (which are right, > but useless for mounting) > > So, please, can someone tell me how to mount my litte USB-Flash-Disk? > > Greet > Sebastian > > -- Daniel van Eeden <[EMAIL PROTECTED]> smime.p7s Description: S/MIME cryptographic signature
Re: Cool N' Quiet
IMHO having ondemand in-kernel, there's no need for userspace daemons anymore... I used to have cpudyn running but now i've purged it... Rafael Rodríguez El Sábado, 13 de Noviembre de 2004 18:49, Harald Dunkel escribió: > Slava Risenberg wrote: > | I've tried to get it working, I mean to lower the CPU frequency > | automatically by loading powernow_k8 module, but without any success. > | I guess I have to do something else to get it working. Any ideas? > | I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. > > I would suggest to install the powernowd package and read the > READMEs in /usr/share/doc/powernowd. To get the current frequency, > you can try > > cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq > > > Good luck > > Harri
Re: Cool N' Quiet
Try the 2.6.9 kernel. Compile the ondemand governor (under CPU Frequency Scaling) as a module. Put the stupid script i've attached into your initscripts directory, and configure it to run... works for me! Regards, Rafael Rodríguez El Sábado, 13 de Noviembre de 2004 19:56, Slava Risenberg escribió: > I've tried to get it working, I mean to lower the CPU frequency > automatically by loading powernow_k8 module, but without any success. > I guess I have to do something else to get it working. Any ideas? > I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. > -- > Slava Risenberg cpufreq-ondemand Description: application/shellscript
Re: Cool N' Quiet
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Slava Risenberg wrote: | I've tried to get it working, I mean to lower the CPU frequency | automatically by loading powernow_k8 module, but without any success. | I guess I have to do something else to get it working. Any ideas? | I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. I would suggest to install the powernowd package and read the READMEs in /usr/share/doc/powernowd. To get the current frequency, you can try cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq Good luck Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFBllclUTlbRTxpHjcRArVGAJ4vq3Q+lOXMwabgNvBNYrsUyz1tuQCfX4lo 0zpG3ToquL4euUrFJ9DNCzk= =FBIV -END PGP SIGNATURE-
Re: Cool N' Quiet
Try the 2.6.9 kernel. Compile the ondemand governor (under CPU Frequency Scaling) as a module. Put the stupid script i've attached into your initscripts directory, and configure it to run... works for me! Regards, Rafael Rodríguez El Sábado, 13 de Noviembre de 2004 19:56, Slava Risenberg escribió: > I've tried to get it working, I mean to lower the CPU frequency > automatically by loading powernow_k8 module, but without any success. > I guess I have to do something else to get it working. Any ideas? > I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. > -- > Slava Risenberg cpufreq-ondemand Description: application/shellscript
USB-Flash <-> uba?
Hi! I installed a Debian64 on my laptop and it works fine. Even the damm acx110 works great with the new snapshot. My own vanilla-kernel. No problem. But my USB-Flash-Disk behaves very strange: When I plug it into the USB-port, the kernel tells me that a new device (uba) is found. ? On my i386-box it's called sda. Ok, uba or sda. I guess there where no difference in mounting. But there is a difference: There is no /dev/uba1, not even a /dev/uba (The "disk" consists of 2 Paritions, both vfat, recognized by the i386-box as sda1 and sda2). I found uba, uba1 and uba2 only in the /sys-tree. But there where only informations about the flash-disk (which are right, but useless for mounting) So, please, can someone tell me how to mount my litte USB-Flash-Disk? Greet Sebastian
Cool N' Quiet
I've tried to get it working, I mean to lower the CPU frequency automatically by loading powernow_k8 module, but without any success. I guess I have to do something else to get it working. Any ideas? I'm using Gigabyte GA-K8 NS motherboard with NVidia 3 250 chipset. -- Slava Risenberg
Re: evolution addressbook problem
* Kristian Kvilekval | Unfortunately there is no explanation where the address book may | lie. | | I even tried removing all my .evolution, evolution directories | with no success. | | Has anybody come across this error and/or found a solution The problem is the libdb4.1 in our repository is broken wrt mutexes. Once that's fixed, evolution will be fine. -- Tollef Fog Heen,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `-
Re: evolution addressbook problem
On Sat, Nov 13, 2004 at 01:56:15PM +0100, Kurt Roeckx wrote: > On Sat, Nov 13, 2004 at 01:33:23PM +0100, Tuure Y. Döring wrote: > > On Sat, 2004-11-13 at 14:49 +0200, Slava Risenberg wrote: > > > I have the same problem > > > > Same problem here. Neither migrating of old address book nor creation of > > a new one is possible. > > Maybe bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277489 but > > I'm not sure. (The description is not that detailed.) > > Unfortunately I didn't find a solution yet, neither myself nor on the > > net. Any ideas? > > The problem was reported in 272831. They change > evolution-data-server to link to an external libdb, which happens > to be db4.1. That one wasn't compiled with fast mutex support > either. > > I'll upload a fixed db4.1 shortly. I've uploaded a fixed version to alioth. This didn't work for me at first but after removing/purging evolution and then installing it again the problem seems to have gone away. Kurt
Re: Bug#279508: Debian AMD64 installer error
On Sat, Nov 13, 2004 at 09:26:59PM +0800, gulfstream wrote: > Who could tell me how to solve the problem? When the bug will be fixed? Could you atleast say which installation method you've used and which version you've used? Kurt
Re: Bug#279508: Debian AMD64 installer error
Who could tell me how to solve the problem? When the bug will be fixed? Thanks gulfstream
Re: evolution addressbook problem
On Sat, Nov 13, 2004 at 01:33:23PM +0100, Tuure Y. Döring wrote: > On Sat, 2004-11-13 at 14:49 +0200, Slava Risenberg wrote: > > I have the same problem > > Same problem here. Neither migrating of old address book nor creation of > a new one is possible. > Maybe bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277489 but > I'm not sure. (The description is not that detailed.) > Unfortunately I didn't find a solution yet, neither myself nor on the > net. Any ideas? The problem was reported in 272831. They change evolution-data-server to link to an external libdb, which happens to be db4.1. That one wasn't compiled with fast mutex support either. I'll upload a fixed db4.1 shortly. Kurt
Re: evolution addressbook problem
On Sat, 2004-11-13 at 14:49 +0200, Slava Risenberg wrote: > I have the same problem Same problem here. Neither migrating of old address book nor creation of a new one is possible. Maybe bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=277489 but I'm not sure. (The description is not that detailed.) Unfortunately I didn't find a solution yet, neither myself nor on the net. Any ideas? Greetz tuure
Re: evolution addressbook problem
I have the same problem -- Slava Risenberg
Re: stats for pure64 vs. gcc-3.4
Just asking... where can i learn about all this gcc-3.4 vs pure64 stuff? I read the debian-amd64-howto and installed my system, but never heard about this two-branches stuff thx in advance, Rafael Rodríguez El Viernes, 12 de Noviembre de 2004 23:32, Kurt Roeckx escribió: > On Fri, Nov 12, 2004 at 02:09:30PM -0800, kristian kvilekval wrote: > > Are there any online stats or recommendations > > when to use pure64 vs. gcc-3.4 repositories? > > > > I've noticed that some pure64 missing applications (evolution2) > > are showing up in the gcc-3.4. > > evolution 2.0.2-3 is in pure64 since today. The reason this > took longer to get in pure64 than gcc-3.4 is that I (pure64) > always wait for "upstream debian" to fix it in sid. It was > waiting for evolution-data-server which was fixed in yesterdays > upload which made building evolution (and a few other related) > package possible today. I'm trying to get the difference between > upstream sources and ours as small as possible. > > The gcc-3.4 archive on the other hand applies many more patches > itself, basicly because it has to. There are alot of packages > that fail to build using gcc-3.4, and upstream debian isn't > always that fast with applying patches. > > For the stats part. They just started their daily build cycle, > so I don't know the result of what is going to be installed when > they're done, but here are the currents stats for both archives: > > There are stats available in the "amd64.txt" file and in the > "dists/sid" version of each archive. > > Pure64: > Installed : 5531 () > Installed+all : 8466 () > Needs-Build : 43 > Building: 1 () > Uploaded: 16 () > Failed : 120 > Dep-Wait: 69 () > Failed-Removed : 0 > Dep-Wait-Removed: 0 > Not-For-Us : 94 > total : 5675 > total+all : 8715 > > gcc-3.4: > Installed : 5600 () > Installed+all : 8606 () > Needs-Build : 64 > Building: 0 () > Uploaded: 0 () > Failed : 99 > Dep-Wait: 24 () > Failed-Removed : 0 > Dep-Wait-Removed: 0 > Not-For-Us : 67 > total : 5747 > total+all : 8794 > > > Now, the most interesting part is why are they different? > > The first thing you'll notice is that gcc-3.4 seems to have 69 > pakcakges more installed. And 71 arch all packages more > installed, having a total of 140 packages more installed. > > The arch all package all seem to be related to java. I don't > know if kaffe works on the gcc-3.4 archive, but there are > currently problems with it on i386 and pure64. > > The other are mostly packages that just fail to build and have a > patch available in the bug tracking system, but isn't uploaded > yet. > > Then there are some packages that shouldn't be build on amd64 in > the first place. For instance there are mono (C#) and ada > pacakges in the gcc-3.4 archive for which upstream says amd64 is > not supported. > > > Kurt
Bug#268757: gcc-3.4-doc: x86_64 -march=*, -m64 option documentation needs clarification
[EMAIL PROTECTED] writes: > Package: gcc-3.4-doc > Severity: normal > > > http://lists.debian.org/debian-amd64/2004/08/msg00306.html > > `-m32' > `-m64' > Generate code for a 32-bit or 64-bit environment. The 32-bit > environment sets int, long and pointer to 32 bits and generates > code that runs on any i386 system. The 64-bit environment sets > int to 32 bits and long and pointer to 64 bits and generates code > for AMD's x86-64 architecture. > > It is not clear in the above paragraph whether -m64 implies -march=k8 > or what. It probably should not... I am not an expert, that's why I > went to the manual. Can you please fix it? GCC never turns something on, which you don't explicitely specify on the command line. Not sure how you want the documentation be changed. -m64 turns on the common subset for all x86-64 architectures, specifying -march=k8 turns on k8/opteron specific features, -march=nocona turns on some P4/64 Nocona specific features.
