Mainboard Compat List
Hello! I have noticed that my installation notes didn't go into the Mobo Compat List... Here they are again: System: DFI LanpartyUT nforce3 250gb AMD Athlon64 [EMAIL PROTECTED] IDE NEC 3500 DVD Burner 200GB SATA HDD For the Mainboard Compatibility list: ata: ? (probably nforce - worked right away) ata raid: I dont use it sata: sata_nv scso: - network: forcedeth (nv_net - the nvidia binary driver should also work, didnt test it though) sound: intel8x0 Installation notes: 1. I used the latest pure64 netinst iso. 2. First of all, my USB Keyboard didn't work during the installation, although my BIOS should make it usable - I could type on the boot prompt, but not in the installer. 3. The installer recognized my Firewire port as network device, but not the onchip NIC. I had to switch to a console and manually load the forcedeth driver. then I used ifconfig to start the eth1 device (not sure if the installer could have done that too..) 4. I used XFS for my root partition. 5. First I had problems with GRUB, wich seems to have trouble on XFS partitions, so I created a 20MB /boot partition with ext2 (during the second installation - grub ruined the first one) 6. After the computer was rebooted to finish the installation, I kept reading messages about sata drives being added and removed again (I forgot the actual wording of the message) - they messed up my whole screen. I found some posts about that problem in the internet and found the solution: After disabling all unused SATA channels/controllers in my BIOS, the error message was gone. regards Jonas PS: Please CC me in replies.
Re: Wine
Levi Bard schrieb: Has anyone gotten WINE to run win32 apps on amd64 yet? I have tried, but no luck. Here's what I did: 1. Installed a i386 chroot 2. installed wine 3. ran winesetup Yes, basically I followed this setup, and it works fine for me. Also cedega. Not really any special tweaking required on my part. Hmm, so what am I missing? What win32 app should I try for testing, that you others have gotten to run and is not too huge (so I have a defined test result)? regards PS: Still CC me in responses, please.
Wine
Hello! Has anyone gotten WINE to run win32 apps on amd64 yet? I have tried, but no luck. Here's what I did: 1. Installed a i386 chroot 2. installed wine 3. ran winesetup now, when I try and start a win32 app, I get [EMAIL PROTECTED]:/mnt/data/Downloads$ wine winamp505_lite.exe Invoking /usr/lib/wine/wine.bin winamp505_lite.exe ... wine: could not load LE:\\Downloads\\winamp505_lite.exe as Win32 binary Wine failed with return code 1 What can be done to fix that? regards Jonas PS: I am not on the list, so please cc me in your replies.
Problems with Kontact, KOrganizer and KMail
Hi! Now that my pure64 installation runs, I have some problems: 1. KOrganizer (either standalone or integrated in Kontact) keeps crashing on startup when the Country in KControlcenter is set to German. It perfectly works, if I set the Country to Default (C) and then manually add German as a language and change all the other settings to the german standard (date-format etc.).. What could be the reason? 2. KMail: When I use Apply Filters on about 500 Emails in my Inbox, KMail takes a LONG time (2min) to filter them. top reveals that the system load rises, and the system spends 20-30% time in waiting (? the fifth entry in the CPU(s): line). KMail is not usable during this time, but continues to work as usual after about 2-4 minutes. I hope someone can fix it or point me to people that can. regards Jonas PS: Please CC me in your replies.
Re: Boot from SATA + Network
Well, I was finally successful. Here my installation notes: System: DFI LanpartyUT nforce3 250gb AMD Athlon64 [EMAIL PROTECTED] IDE NEC 3500 DVD Burner 200GB SATA HDD For the Mainboard Compatibility list: ata: ? (probably nforce - worked right away) ata raid: I dont use it sata: sata_nv scso: - network: forcedeth (nv_net - the nvidia binary driver should also work, didnt test it though) sound: intel8x0 Installation notes: 1. I used the latest pure64 netinst iso. 2. First of all, my USB Keyboard didn't work during the installation, although my BIOS should make it usable - I could type on the boot prompt, but not in the installer. 3. The installer recognized my Firewire port as network device, but not the onchip NIC. I had to switch to a console and manually load the forcedeth driver. then I used ifconfig to start the eth1 device (not sure if the installer could have done that too..) 4. I used XFS for my root partition. 5. First I had problems with GRUB, wich seems to have trouble on XFS partitions, so I created a 20MB /boot partition with ext2 (during the second installation - grub ruined the first one) 6. After the computer was rebooted to finish the installation, I kept reading messages about sata drives being added and removed again (I forgot the actual wording of the message) - they messed up my whole screen. I found some posts about that problem in the internet and found the solution: After disabling all unused SATA channels/controllers in my BIOS, the error message was gone. The rest went pretty straight forward, this email is sent from my new system! :-) regards and thanks for the help! Jonas PS: Please CC me in any replies, I'm not on the list (yet?). Am Donnerstag 11 November 2004 06:50 schrieb Bob Proulx: Jonas Diemer wrote: PS: Please CC me in your replies, I am not subscribed to the list. I get a kernelpanic, saying that the root filesys couldn't be mounted. I guess this is because the sata driver (I believe it is sata_nv) is compiled as a module. Am I correct? Almost certainly. What would you suggest - how should I get my system installed? Boot from the DFS iso. http://people.debian.org/~jgoerzen/dfs Among other good stuff this bootable cd image provides a grub boot. At the grub boot prompt you can provide both the kernel and the initrd. The process should go something like this for your /dev/sda3 boot, assuming I transposed things properly for that. root (hd0,2) kernel /boot/vmlinuz-2.6.8-3-amd64-k8 root=/dev/sda3 ro initrd /boot/initrd.img-2.6.8-3-amd64-k8 boot Even if that does not work the bootable cd image is useful to further debugging efforts. If nothing else you can borrow the kernel and initrd from that disk and install them to your drive. Bob
