Re: 3ware 9550 SATA RAID controller problems
On Wed, 04 Jan 2006 20:39:30 -0500, Stephen Woodbridge <[EMAIL PROTECTED]> wrote: > > After finally getting Sarge installed on my SuperMicro X6DHT-G > motherboard system, I am having a problem recognizing the 3ware 9550 > SATA Raid Controller card. I have loaded the 3w-9xxx module but that is > not getting me anywhere yet. This system boots from a separate SATA disk > so the system is running, just without the 1.6TB raid array :( > > Thoughts and suggestions would be greatly appreciated. I can't comment on the 9550, but I'm using a 3Ware 9500 on a dual-Opteron 250 setup, and it works fine with 4x400Gb as hardware RAID5 (1.2TB). I used the 2.6.12 kernel for the install (I did a tftp install as the box has no CD drive - it's a 1U rackmount server with all drive bays full). The installer saw it as a single 1.2TB drive. Regards, Ozz. pgpAEwcPhocmj.pgp Description: PGP signature
Strange network probes on UDP port: 161
Ever since I have brought my new system on line I have been getting the following reports from other server: Jan 4 20:47:49 maps portsentry[1117]: attackalert: Connect from host: 192.168.1.113/192.168.1.113 to UDP port: 161 Jan 4 20:47:49 maps portsentry[1117]: attackalert: Host: 192.168.1.113 is already blocked. Ignoring Since all these systems are behind a firewall device and my local network is all configured on the 10.1.1.x network this is a little strange. I'm pretty sure it is coming from the new hardware, but I'm not sure how to confirm it other than to turn off the new server and see if the messages stop. I do have an IPMI card in the new server that I have not figured out how to setup and configure because I have been focused on other issues first. port 161 is an snmp port but I can find no reference to anything like that in the motherboard user's guide for the SuperMicro X6DHT-G motherboard. Any thoughts on this? -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to use 2.4 kernel on EMT64 machine
Thanks for your reply Lennart Sorensen wrote: On Wed, Jan 04, 2006 at 06:51:28PM +0900, "Terry Li(?)" wrote: I've got a Dell PowerEdge SC430 server with Celeron D CPU(EMT64) and Intel ICH7 SATA interface. I have installed sarge on this machine using a customed install CD, which has kernel 2.6.12-1-amd64-generic. It works fine. For some reasons, I need to use 2.4 kernel. So I download official 2.4.32 kernel and patch it by http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.4.32-libata1.patch.bz2 in order to get ICH7 support. I didn't find any problem on compiling. But the machine stop booting on the startup message, "Booting the kernel.". Does anyone successfully run 2.4 kernel with ICH7 support on EMT64 machine? The 2.4 kernel predates amd64 pretty much entirely, and does not really support it. Since there is no new major development on 2.4 and hasn't been in years (just bug fixes mainly), so puting full amd64 support in 2.4 will never happen. I think redhat is the only ones that have made a lot of amd64 patches for 2.4 for RHEL. No one else bothers. It just isn't worth it. If you absolutely need 2.4 kernel, run the system in i386 mode since you obviously want legacy support rather than modern. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
3ware 9550 SATA RAID controller problems
Hi Again, After finally getting Sarge installed on my SuperMicro X6DHT-G motherboard system, I am having a problem recognizing the 3ware 9550 SATA Raid Controller card. I have loaded the 3w-9xxx module but that is not getting me anywhere yet. This system boots from a separate SATA disk so the system is running, just without the 1.6TB raid array :( lspci is reporting: :03:02.0 RAID bus controller: 3ware Inc: Unknown device 1003 So, I think what needs to happen next is one or more of the following: 1) upgrade to the 2.6.12 kernel 2) compile the updated vendor source for 3w-9xxx module on either 2.6.8-11 or 2.6.12 3) something simpler that I am missing. Ideally, I would like to use a stock kernel which was why I was thinking of getting 2.6.12 from etch otherwise I will need to try and figure out how to use the kernel-package system and long term maintenance becomes a bigger problem. Thoughts and suggestions would be greatly appreciated. Best regards, -Steve I've included the system details below. Linux carto 2.6.8-11-em64t-p4-smp #1 SMP Mon Oct 3 00:07:51 CEST 2005 x86_64 GNU/Linux [EMAIL PROTECTED]:~$ lsmod Module Size Used by ipv6 280552 16 3w_9xxx36100 0 ext3 121616 5 jbd64176 1 ext3 mbcache11400 1 ext3 tsdev 9472 0 mousedev 12628 0 evdev 11648 0 psmouse20108 0 genrtc 11516 0 sd_mod 22400 7 usb_storage69184 0 e1000 83588 0 ide_cd 42784 0 cdrom 39848 1 ide_cd ide_disk 21504 0 ide_generic 2816 0 generic 6528 0 ide_core 154688 5 usb_storage,ide_cd,ide_disk,ide_generic,generic floppy 65104 0 fbcon 32164 70 vga16fb14464 1 vgastate 10240 1 vga16fb usbserial 33008 0 usbkbd 8960 0 ehci_hcd 32132 0 uhci_hcd 33056 0 thermal15116 0 processor 15224 1 thermal fan 5512 0 ata_piix9988 6 libata 42888 1 ata_piix scsi_mod 131072 4 3w_9xxx,sd_mod,usb_storage,libata unix 32032 12 font 10112 1 fbcon vesafb 7984 0 cfbcopyarea 5120 2 vga16fb,vesafb cfbimgblt 4352 2 vga16fb,vesafb cfbfillrect 5248 2 vga16fb,vesafb [EMAIL PROTECTED]:~$ lspci :00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 0c) :00:00.1 ff00: Intel Corp. Memory Controller Hub Error Reporting Register (rev 0c) :00:01.0 System peripheral: Intel Corp. Memory Controller Hub DMA Controller (rev 0c) :00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 0c) :00:04.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B0 (rev 0c) :00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 (rev 0c) :00:1c.0 PCI bridge: Intel Corp. 6300ESB 64-bit PCI-X Bridge (rev 02) :00:1d.0 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02) :00:1d.1 USB Controller: Intel Corp. 6300ESB USB Universal Host Controller (rev 02) :00:1d.4 System peripheral: Intel Corp. 6300ESB Watchdog Timer (rev 02) :00:1d.5 PIC: Intel Corp. 6300ESB I/O Advanced Programmable Interrupt Controller (rev 02) :00:1d.7 USB Controller: Intel Corp. 6300ESB USB2 Enhanced Host Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 0a) :00:1f.0 ISA bridge: Intel Corp. 6300ESB LPC Interface Controller (rev 02) :00:1f.2 IDE interface: Intel Corp. 6300ESB SATA Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 6300ESB SMBus Controller (rev 02) :01:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09) :01:00.1 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller A (rev 09) :01:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09) :01:00.3 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller B (rev 09) :03:02.0 RAID bus controller: 3ware Inc: Unknown device 1003 :06:01.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) :06:02.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) :07:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27) [EMAIL PROTECTED]:~$ dmesg Bootdata ok (command line is root=/dev/sda1 ro console=tty0 ) Linux version 2.6.8-11-em64t-p4-smp ([EMAIL PROTECTED]) (gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13)) #1 SMP Mon Oct 3 00:07:51 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009b000 (usable) BIOS-e820: 0009b000 - 000a (res
Re: Install problem on Supermicro X6DHT-G system
Hi all, I have made some significant progress! After a million reboots and BIOS changes I found the right combination to get the installer to work. Unfortunately your good comments about how to not reinstall came in after I failed to deduce that myself and wiped the disk. But I have been able to get it to recognize the CD and the SATA Disk. The CD is still on the Slave channel because it has no jumpers to force it to Master and chipset/BIOS seem to want it to be a Slave regardless. But it works so I'm not complaining. In the BIOS, there is an option to force a channel to be parallel only and once I set this for the CD and set Native Mode Operation to Auto, things got better. I still had to limit the modules that got loaded to eliminate all the devices that I didn't have so I suspect there is a device conflict somewhere in there. So I'm closing this problem out with a big THANK YOU! And will start the next issue in a new thread :) -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: new kernel too big for lilo
On 1/1/06, Hamish Moffatt <[EMAIL PROTECTED]> wrote: > If you do it ALL the Debian way, it's just fine. You should see your new > kernels added into the LILO configuration automatically, or at least the > GRUB configuration (preferred to LILO these days). > > Another part of the Debian way is that you rarely need to compile your > own kernel these days. What did you need to change? > Sorry for the delayed response - just got back from a few days snowboarding in the Japanese alps! As another poster mentioned I was compiling a kernel because DMA wasn't enabled. Another reason was that fancontrol and sensors report "no sensors found". lm_sensors DOES seem to be working (CPU runs slower under low load) and with a previous Debian installation on this motherboard sensors DID work. I figured it must be a missing kernel option. Unfortunately none of the options I selected seem to have done the job. (I'll continue this in a new thread.) Hamish said that there is rarely a need to compile your own kernel with Debian. I think I must have missed something. Is there a ways to do a simple 'apt-get install new_kernel'? I did a google search for something like 'debian kernel install', but all of the hits described compiling your own new kernel. Craig
Re: Mount USB memory stick in 32 bit chroot as well
> > The directory is created after inserting the stick, but there is only > > one file in there (.created_by_pmount). Following your recipe didn't > > change anything, unfortunately. > > I can't tell if you answered the question or not. Does the directory show > up in the chroot environment? If so, then your problem lies elsewhere, > like maybe a permissions thing. I have not had time to completely figure it out yet, but you might want to look into "rbind" mounts instead of plain bind mounts. When I set up my chroot I bind mounted /home into the chroot, but then found that when I mounted files from my fileserver (mounted to /home/daniel/Remote), I couldn't see them in the chroot. (ie, "ooffice ~/Remote/foo.odt" fails with "File not Found". ooffice is symlinked to the do_chroot script) Unmounting /chroot/home and remounting it as "-o rbind" did the trick. I attempted to make this permanent with a change in fstab, but it didn't seem to work there - only when I did it manually. When I get time I'll have another look at it and see if I can't make it work. There is some magic to the mounting to make it work. You can apparently do it as a "bind" mount if the original mounpoint is "shared" (but not if it's not). There is some documentation: http://lwn.net/Articles/159092/ . This would also explain why you can mount /media in the chroot, but then not see any submounts. Hope this helps... Daniel. (Apologies to Andrew; you'll get two of these. I keep forgetting to "reply to all" instead of "reply".)
Re: System Monitor shows only 1 CPU (2 present)
use top the cli is best anyway ;) Dean Andrew Sharp wrote: On Wed, Jan 04, 2006 at 03:04:01PM -0600, Russ Cook wrote: Hi all, I'm running an AMD64 dual core processor, debian64 stable. Sources.list is attached. My problem is that System Monitor 2.8.1 lists only 1 CPU. I have a dual core processor, and kernel 2.6.14.4 is compiled with smp enabled. The system logs show that both processors are detected and enabled. I briefly was running etch, and System Monitor did show both CPUs. I don't remember what version System Monitor was at the time under Etch. I have since done a clean reinstall of stable. Might this be a problem from running stable? If not, can anyone offer a suggestion? If I had to guess, which I do, then I'd guess the version of "System Monitor" [whatever that is] is stable is not capable of dealing with SMP under 2.6, but the newer version in etch (2.10.1-3) is. Possible? a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mount USB memory stick in 32 bit chroot as well
On Wed, Jan 04, 2006 at 09:14:12PM +, Koen Vermeer wrote: > On Wed, 2006-01-04 at 11:23 -0800, Andrew Sharp wrote: > > When you have bind mounted /media into your chroot, and after inserting > > the stick, does the directory media/Kingston exist inside the chroot? > > I'm not a gnome user, thank 5od, but I'm guessing that that directory > > gets created on the fly by gnomadness when you insert the stick. So, > > without anything inserted, she said, verify that the Kingston directory > > doesn't exist anywhere, then do the bind mount, then insert your > > memory, and see if the Kingston directory is created and exists inside > > the chroot. If so, then you have solved your basic problem. If not, > > then back to the drawing board. > > The directory is created after inserting the stick, but there is only > one file in there (.created_by_pmount). Following your recipe didn't > change anything, unfortunately. I can't tell if you answered the question or not. Does the directory show up in the chroot environment? If so, then your problem lies elsewhere, like maybe a permissions thing. Cheers, a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: System Monitor shows only 1 CPU (2 present)
On Wed, Jan 04, 2006 at 03:04:01PM -0600, Russ Cook wrote: > Hi all, > I'm running an AMD64 dual core processor, debian64 stable. > Sources.list is attached. My problem is that System Monitor 2.8.1 lists > only 1 CPU. I have a dual core processor, and kernel 2.6.14.4 is > compiled with smp enabled. The system logs show that both processors > are detected and enabled. I briefly was running etch, and System > Monitor did show both CPUs. I don't remember what version System > Monitor was at the time under Etch. I have since done a clean reinstall > of stable. > Might this be a problem from running stable? If not, can anyone offer > a suggestion? If I had to guess, which I do, then I'd guess the version of "System Monitor" [whatever that is] is stable is not capable of dealing with SMP under 2.6, but the newer version in etch (2.10.1-3) is. Possible? a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 64/32 with DRI
On Wed, Jan 04, 2006 at 03:36:42PM -0600, Stephen Olander Waters wrote: > On Wed, 2006-01-04 at 10:58 -0800, Andrew Sharp wrote: > > I think this started over DRI support for the ancient 7000 Radeon. > > However, I haven't seen any testing results posted. I know there is a > > comment in the code that it's experimental, but have you actually tried > > it and found it to be buggy? > > I believe this is the bug I am experiencing: > https://bugs.freedesktop.org/show_bug.cgi?id=5104 Hmm, is it possible to downgrade to X.org 6.7? Er, 6.8.2 is the version even in etch, so downgrading would be difficult. It looks to me to be 64-bit specific, like, it's iterating through a 4294967295 planes trying to do something the chip doesn't even support, instead of skipping that feature. So if you can live without DRI for a little while, they will probably have this fixed, or at least a patch available. Cheers, a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 64/32 with DRI
On Wed, 2006-01-04 at 10:58 -0800, Andrew Sharp wrote: > Geez you guys sound like a couple of teenagers who just found their > favorite football team. If the open source ATI Radeon driver has bugs > you don't like, you are free to jump in and fix them. It works quite > well for me on multiple systems including my amd64. As I understand it, the problem is localized to the R100 series of GPUs which includes the Radeon 7000/VE I have installed on my box. > I think this started over DRI support for the ancient 7000 Radeon. > However, I haven't seen any testing results posted. I know there is a > comment in the code that it's experimental, but have you actually tried > it and found it to be buggy? I believe this is the bug I am experiencing: https://bugs.freedesktop.org/show_bug.cgi?id=5104 Also, having dug around some, I believe it has to do with the dynamic clocking patch but I'm not a C coder, don't have access to a serial console, etc. There are no messages in the logs -- just a hard freeze of the system. I'm not using any driver options. I have turned off MTRR, which is also buggy, in the Screen section. I tried setting SWCursor as suggested in another bug in the Free Desktop bugzilla but that didn't help. -s signature.asc Description: This is a digitally signed message part
Re: USB
How about the dirty trick of instead of having /dev/sdc1/media/usb autorw,user,noauto 0 0 in /etc/fstab you have /dev/sdc1/etch32/media/usb autorw,user,noauto 0 0 and make /media a symbolic link to /etch32/media/usb This should work. /Gudjon Þann Miðvikudagur 4. janúar 2006 22:28 skrifaði Koen Vermeer: > On Wed, 2006-01-04 at 20:07 +0100, Gudjon I. Gudjonsson wrote: > > Hi > > If you do > > mkdir /var/chroot/sid-sarge-etch/media/Kingston > > cd /media > > rmdir Kingston > > ln -s /var/chroot/sid-sarge-etch/media/Kingston . > > and then insert your USB-stick, it should be visible in both places. > > I just tried it and it seems to work for me. Please post it if it works. > > It works in that I can see the contents in the normal system and the > chroot. But now the filenames aren't consistent anymore. My chroot is > in /etch32. In /media, I now have > > lrwxrwxrwx 1 root root 22 2006-01-04 21:17 Kingston > -> /etch32/media/Kingston > > If I open a document by double-clicking on it, I get the error > '/etch32/media/Kingston/filename.ext does not exist'. So, from within > the 64 bit system, the filename points to the chroot. Ofcourse, from the > chroot, /etch32 does not exist, and so the file isn't found. Still some > more work to do, I guess... > > Koen
System Monitor shows only 1 CPU (2 present)
Hi all, I'm running an AMD64 dual core processor, debian64 stable. Sources.list is attached. My problem is that System Monitor 2.8.1 lists only 1 CPU. I have a dual core processor, and kernel 2.6.14.4 is compiled with smp enabled. The system logs show that both processors are detected and enabled. I briefly was running etch, and System Monitor did show both CPUs. I don't remember what version System Monitor was at the time under Etch. I have since done a clean reinstall of stable. Might this be a problem from running stable? If not, can anyone offer a suggestion? Thanks much, Russ #deb file:///cdrom/ sarge main deb http://mirror.espri.arizona.edu/debian-amd64/debian/ stable main contrib non-free deb-src http://mirror.espri.arizona.edu/debian-amd64/debian/ stable main contrib non-free deb http://security.debian.org/ stable/updates main contrib non-free
Re: USB
On Wed, 2006-01-04 at 20:07 +0100, Gudjon I. Gudjonsson wrote: > Hi > If you do > mkdir /var/chroot/sid-sarge-etch/media/Kingston > cd /media > rmdir Kingston > ln -s /var/chroot/sid-sarge-etch/media/Kingston . > and then insert your USB-stick, it should be visible in both places. > I just tried it and it seems to work for me. Please post it if it works. It works in that I can see the contents in the normal system and the chroot. But now the filenames aren't consistent anymore. My chroot is in /etch32. In /media, I now have lrwxrwxrwx 1 root root 22 2006-01-04 21:17 Kingston -> /etch32/media/Kingston If I open a document by double-clicking on it, I get the error '/etch32/media/Kingston/filename.ext does not exist'. So, from within the 64 bit system, the filename points to the chroot. Ofcourse, from the chroot, /etch32 does not exist, and so the file isn't found. Still some more work to do, I guess... Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to use 2.4 kernel on EMT64 machine
On Wed, Jan 04, 2006 at 06:51:28PM +0900, "Terry Li(?)" wrote: > I've got a Dell PowerEdge SC430 server with Celeron D CPU(EMT64) and > Intel ICH7 SATA interface. I have installed sarge on this machine using > a customed install CD, which has kernel 2.6.12-1-amd64-generic. It > works fine. For some reasons, I need to use 2.4 kernel. So I download > official 2.4.32 kernel and patch it by > http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.4.32-libata1.patch.bz2 > > > in order to get ICH7 support. I didn't find any problem on compiling. > But the machine stop booting on the startup message, "Booting the > kernel.". Does anyone successfully run 2.4 kernel with ICH7 support on > EMT64 machine? The 2.4 kernel predates amd64 pretty much entirely, and does not really support it. Since there is no new major development on 2.4 and hasn't been in years (just bug fixes mainly), so puting full amd64 support in 2.4 will never happen. I think redhat is the only ones that have made a lot of amd64 patches for 2.4 for RHEL. No one else bothers. It just isn't worth it. If you absolutely need 2.4 kernel, run the system in i386 mode since you obviously want legacy support rather than modern. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mount USB memory stick in 32 bit chroot as well
On Wed, 2006-01-04 at 11:23 -0800, Andrew Sharp wrote: > When you have bind mounted /media into your chroot, and after inserting > the stick, does the directory media/Kingston exist inside the chroot? > I'm not a gnome user, thank 5od, but I'm guessing that that directory > gets created on the fly by gnomadness when you insert the stick. So, > without anything inserted, she said, verify that the Kingston directory > doesn't exist anywhere, then do the bind mount, then insert your > memory, and see if the Kingston directory is created and exists inside > the chroot. If so, then you have solved your basic problem. If not, > then back to the drawing board. The directory is created after inserting the stick, but there is only one file in there (.created_by_pmount). Following your recipe didn't change anything, unfortunately. Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nforce 410 MCP chipset & ne2k-pci error
On Wed, Jan 04, 2006 at 09:39:43PM +0530, janarthanam ramalingam wrote: > I am using a kernel.org 2.6.14 kernel on debain sarge 3.1 for amd. > this on a Asrock K8NF4G-SATA2 mob. > > i earlier mentioned in this mailing list that my inbuilt network card wasn't > identified by linux and told that this chipset nforce 401 is not yet > supported. > > http://lists.debian.org/debian-amd64/2005/12/msg00633.html > > i plug my realtek ethernet card in the pci slot and modprobed ne2k-pci which > says: "no I/O resource at pci bar #0" which i make from the driver code that > my pci ioport is disabled. i donot see a way to enable the io port from my > bios settings > > is this only due to lack of nforce 410 chipset as marked in the reply for > the bug, or is it something else? Sounds like a bios bug, but could be a kernel bug too. Not sure very many people have used an ne2k-pci on an amd64 system (like why would anyone bother with something so slow and so old). It is possible a bios upgrade will fix it, some obscure bios setting, using a different pci slot, or using a different kernel, or just using a different type of network card. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mount USB memory stick in 32 bit chroot as well
On Wed, Jan 04, 2006 at 06:51:51PM +, Koen Vermeer wrote: > Hi, > > I'm still trying to integrate the 32 bit chroot and the normal system as > much as possible, so that, from a user's point of view, it's just like > running a full 64 bits system. > > Currently, when I insert an USB memory stick, it gets mounted > automatically in /media/Kingston. This is done by gnome-volume-manager, > hal, dbus, pmount, and maybe even more programs are involved. Anyway, > I'd like to have it linked to /chroot32/media/Kingston as well. I can > easily mount /media as /chroot32/media, just like /tmp and /home, but > unfortunately, I don't see anything in /chroot32/media/Kingston after > inserting the memory. When you have bind mounted /media into your chroot, and after inserting the stick, does the directory media/Kingston exist inside the chroot? I'm not a gnome user, thank 5od, but I'm guessing that that directory gets created on the fly by gnomadness when you insert the stick. So, without anything inserted, she said, verify that the Kingston directory doesn't exist anywhere, then do the bind mount, then insert your memory, and see if the Kingston directory is created and exists inside the chroot. If so, then you have solved your basic problem. If not, then back to the drawing board. Cheers, a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 64/32 with DRI
On Tue, Jan 03, 2006 at 09:36:04AM -0600, Stephen Olander Waters wrote: > On Mon, 2006-01-02 at 20:35 +1100, Hamish Moffatt wrote: > > On Mon, Jan 02, 2006 at 01:45:16AM -0600, Stephen Olander Waters wrote: > > > Radeon 7000 DRI in xorg 6.8.2 is "unstable" apparently. See this > > > message: > > [...] > > > Man that sucks. > > > > That's ATI for you. > > I'm not using ATI's proprietary driver. I'm using the buggy open source > driver maintained by X.org which used to work just fine... Geez you guys sound like a couple of teenagers who just found their favorite football team. If the open source ATI Radeon driver has bugs you don't like, you are free to jump in and fix them. It works quite well for me on multiple systems including my amd64. I think this started over DRI support for the ancient 7000 Radeon. However, I haven't seen any testing results posted. I know there is a comment in the code that it's experimental, but have you actually tried it and found it to be buggy? a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Mount USB memory stick in 32 bit chroot as well
Hi, I'm still trying to integrate the 32 bit chroot and the normal system as much as possible, so that, from a user's point of view, it's just like running a full 64 bits system. Currently, when I insert an USB memory stick, it gets mounted automatically in /media/Kingston. This is done by gnome-volume-manager, hal, dbus, pmount, and maybe even more programs are involved. Anyway, I'd like to have it linked to /chroot32/media/Kingston as well. I can easily mount /media as /chroot32/media, just like /tmp and /home, but unfortunately, I don't see anything in /chroot32/media/Kingston after inserting the memory. Again: I'm sure others have had this problem as well, and maybe they also fixed it. If so, I'd be more than happy to know how! Koen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.6.14-7 instability?
Am Mittwoch, 4. Januar 2006 19:29 schrieb Gudjon I. Gudjonsson: > Hi >I changed some time ago to kernel version 2.6.14 but then I found it not > stable enough so I switched back to 2.6.12. A few days ago I did another > attempt and installed linux-image-2.6-amd64-k8-smp version 2.6.14-7. Today > the top command behaved quite strangely, it seemed like top was using 100% > of CPU and the other simulation program 99%. Then I rebooted to kernel > version 2.6.12 again some inodes where deleted but everything seems to be > working perfectly now. >Has anyone else had problems with this kernel? Yes, I did. But I thought, it might be my hard drive, and changed it. Since I changed, no errors were found. Before I had some weird things, just like you: Changed to 2.6.14, then lost inodes. Booted with Kanotix and did an e2fsck -y /dev/hdax. Everything seemed to be fine. Then started again, no errors. But, when I shut down as usula, and started again, therer were lost inodes again. This is gone, since I changed my harddrive. The old harddrive is now in use for backups, but now it has no errors any more. Really weird. I do not think , the old harddrive is defect. Best regards Hans > Sincerely > Gudjon -- Firma Ullrich-IT-Consult Inh.: Hans-J. Ullrich Münstedter Weg 10 31246 Oberg Tel.: 0160 8156 079 www: http://www.ullrich-it.de Ihr Berater für Ihre IT-Probleme ! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
kernel 2.6.14-7 instability?
Hi I changed some time ago to kernel version 2.6.14 but then I found it not stable enough so I switched back to 2.6.12. A few days ago I did another attempt and installed linux-image-2.6-amd64-k8-smp version 2.6.14-7. Today the top command behaved quite strangely, it seemed like top was using 100% of CPU and the other simulation program 99%. Then I rebooted to kernel version 2.6.12 again some inodes where deleted but everything seems to be working perfectly now. Has anyone else had problems with this kernel? Sincerely Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
nforce 410 MCP chipset & ne2k-pci error
I am using a kernel.org 2.6.14 kernel on debain sarge 3.1 for amd. this on a Asrock K8NF4G-SATA2 mob.i earlier mentioned in this mailing list that my inbuilt network card wasn't identified by linux and told that this chipset nforce 401 is not yet supported. http://lists.debian.org/debian-amd64/2005/12/msg00633.htmli plug my realtek ethernet card in the pci slot and modprobed ne2k-pci which says: "no I/O resource at pci bar #0" which i make from the driver code that my pci ioport is disabled. i donot see a way to enable the io port from my bios settings is this only due to lack of nforce 410 chipset as marked in the reply for the bug, or is it something else?thanksjana
Re: [EMAIL PROTECTED] gfp.h & BUG_ON
On Wed, Jan 04, 2006 at 06:49:05PM +0900, "Terry Li(?)" wrote: > Hi all, > > I've got a Dell PowerEdge SC430 server with Celeron D CPU(EMT64) and > Intel ICH7 SATA interface. I have installed sarge on this machine using > a customed install CD, which has kernel 2.6.12-1-amd64-generic. It > works fine. For some reasons, I need to use 2.4 kernel. So I download > official 2.4.32 kernel and patch it by > http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.4.32-libata1.patch.bz2 > > in order to get ICH7 support. I didn't find any problem on compiling. But > the machine stop booting on the startup message, "Booting the kernel.". > Does anyone successfully run 2.4 kernel with ICH7 support on EMT64 machine? Check initrd image for your new kernel. -- With best regards, Oleg Gritsinevich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian-amd64 AU mirrors
The listed AU mirror public.planetmirror.com is broken. The actual Packages.gz URLs return HTML pages which then refer you to another server after some time, with "yuor download should begin shortly" type text. This mirror has been pretty slow for me anyway. The other (mirror.pacific.net.au) seems reliable, though not very fast from my ISP. Ideally, mirror.aarnet.edu.au would mirror Debian-AMD64. They have Debian already, and it's blindingly fast because it's on my ISP's network (only 8 hops from here, 40ms pings). Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install problem on Supermicro X6DHT-G system
On Tuesday 03 Jan 2006 18:44, Stephen Woodbridge wrote:
> This list rocks! Thank you all for the ideas and suggestions. I will
> reinstall tonight and try moving the CD to a master channel and try
> changing the BOIS settings and see if any of these help. I'll report
> back with my findings.
>
> -Steve
You probably do not even need to reinstall anything. After all, the files are
still there; it's only the names of the drives that have changed. If you
could somehow persuade the machine that the files are in the new locations,
it would find them.
Power off, move the CD to master, make sure nothing is conflicting with it,
power up straight into BIOS and make the appropriate changes. In other
words, the stuff you were going to do anyway. But don't reinstall just yet.
Boot up from your Debian installer CD. Let it get as far as asking you the
first question {by which time it will have loaded all necessary drivers},
then press ctrl+alt+f2 for another console. Make a directory /target {don't
worry, the root filesystem is on a ramdisk}, and mount the root partition
your hard drive {note that the debian installer CD uses devfs, so it'll be
something like /dev/scsi/bus0/target0/lun0/part1} there. A modern enough
install disc will have a shell with tab-completion, which will help a lot.
Mount any other partitions beneath /target. Optionally, enable your swap
partition using
# swapon /dev/some/stupidly/long/path
Then
# nano /target/etc/fstab
and change all the drive names appropriately {your SATA hard disk probably
will be /dev/sda and your IDE CD-ROM will be /dev/hda or /dev/hdc}. Then
# nano /target/etc/lilo.conf
and change the drive names there too.
Finally,
# chroot /target
{this creates a new root file system; what used to be /target now becomes /
and so forth}
# /sbin/lilo
{this writes the new bootstrap loader code into the MBR. At boot time, no
drivers have been loaded [obviously], not even a file system driver; so the
physical location of the kernel on the disk needs to be hard-coded into the
bootstrap loader, which has to use BIOS calls to load up the kernel.}
IMPORTANT: press ctrl+D to exit from the chroot; this forces decaching of all
the changes you made while you were inside the chroot.
You should now be able to remove the CD and reboot your system.
--
AJS
delta echo bravo six four at earthshod dot co dot uk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems installing on AMD Athlon 64 system
Austin (Ozz) Denyer wrote: On Sun, 18 Dec 2005 15:03:58 -0800, lordSauron <[EMAIL PROTECTED]> wrote: noo!!! another one lost to Gnome! I really hope you meant Kubuntu, since KDE is really much nicer than Gnome for people who need to get something done (working with Gnome is like having your neck amputated!) Even Linus himself recently stated that people should use KDE rather than Gnome. I won't repeat what Linus called the people behind the Gnome interface for fear of invoking Godwin's Law #;-D I have to say that Gnome has been dumbed down to the point of being virtually useless. So even Linus seems to think the choice is between KDE and Gnome? :-/ There is a third alternative - use neither and be much more efficient. Go for icewm or some other simple window manager - and start X, login, get the window manager up and running in a few seconds only. No long wait for KDE to start (what the heck is it spending time on? Half a minute on an otherwise nice fast machine? Is it compiling itself first?) No insanely stupid "hardware detect" that lock up some machines. (Why, oh why do a _GUI_ do hardware detection at all? That is the job of the kernel - or sometimes the xserver. ) I don't mind the look of KDE, but the startup time (and hangs) offset any benefit for me. Helge Hafting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How to use 2.4 kernel on EMT64 machine
Hi all, I've got a Dell PowerEdge SC430 server with Celeron D CPU(EMT64) and Intel ICH7 SATA interface. I have installed sarge on this machine using a customed install CD, which has kernel 2.6.12-1-amd64-generic. It works fine. For some reasons, I need to use 2.4 kernel. So I download official 2.4.32 kernel and patch it by http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.4.32-libata1.patch.bz2 in order to get ICH7 support. I didn't find any problem on compiling. But the machine stop booting on the startup message, "Booting the kernel.". Does anyone successfully run 2.4 kernel with ICH7 support on EMT64 machine? Thanks, Terry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] gfp.h & BUG_ON
Hi all, I've got a Dell PowerEdge SC430 server with Celeron D CPU(EMT64) and Intel ICH7 SATA interface. I have installed sarge on this machine using a customed install CD, which has kernel 2.6.12-1-amd64-generic. It works fine. For some reasons, I need to use 2.4 kernel. So I download official 2.4.32 kernel and patch it by http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.4.32-libata1.patch.bz2 in order to get ICH7 support. I didn't find any problem on compiling. But the machine stop booting on the startup message, "Booting the kernel.". Does anyone successfully run 2.4 kernel with ICH7 support on EMT64 machine? Thanks, Terry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Matrox 550 / Debian Etch/ X.Org 6.8.2 / Xinerama not working??
Joost Kraaijeveld wrote: Hi, After an update of XFree86 to X.org my Xinerama setup stopped working. I cannot get my two screens working at the same time, except when I use the second screen (an LCD screen, the little inferior one) as my main (or first, the one with the menubar) screen, and my first screen ( a beautiful 21 inch CRT screen) as my second screen. Is that a known feature or a plain bug? Is there a workaround for it? Looks like a bug. What bad happens if you switch the vga connectors around? Helge Hafting -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Install problem on Supermicro X6DHT-G system
On Tuesday 03 January 2006 18:44, Stephen Woodbridge wrote: > This list rocks! Thank you all for the ideas and suggestions. I > will reinstall tonight and try moving the CD to a master channel > and try changing the BOIS settings and see if any of these help. > I'll report back with my findings. no need to reinstall, just change your /etc/fstab, turn off, change the hardware to use the correct channels and turnn back on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] gfp.h & BUG_ON
On Wed, Jan 04, 2006 at 08:56:11AM +0100, fred wrote:
> I try to compile kernel 2.6.15-rc7 on a P4 630 EM64T.
>
> 1) kernel 2.6.15-rc7 compiles fine on my debian i686 distro.
>
> 2) compliling kernel 2.6.15-rc7 fails on the same linuxbox
> but for my amd64 distro.
> kernel crashes at bootime with this message :
>
> Kernel BUG at /include/linux/gfp.h:80
> invalid operand : [1]
> CPU 0
> .../...
You snipped the most interesting part: the function backtrace.
gfp_zone() crashed cause one of its callers called it with a wrong
argument. The interesting part is what caller it was.
> Looking line 80, one can see :
>
> static inline int gfp_zone(gfp_t gfp)
> {
> int zone = GFP_ZONEMASK & (__force int) gfp;
> BUG_ON(zone >= GFP_ZONETYPES);
> return zone;
> }
>
> 3) kernel 2.6.14 compiles fine on my debian amd64 distro.
> gfp.h differs from above : there is no BUG_ON symbol.
Yeah, that happens with development: things change :)
> 4) Any idea ?
There were quite some changes in the memory zone handling in 2.6.15. If
you have a linux git repository, run this to see what really happened:
git whatchanged -p v2.6.14..v2.6.15-rc7 include/linux/gfp.h
You might want to try linux-2.6.15 to see if the problem is already
solved. If not, the fastes way to get this solved is to report it to
the linux-kernel mailing list (see the file REPORTING-BUGS in your
kernel tree for details).
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
