Re: xserver-xfree86 4.3.0.dfsg.1-7 glint on UltraSparc 60 with Linux 2.6.8.1: Unresolved Symbols
Patrick, 1) Anything from the kernel driver in dmesg before/after you try to start X? I'd expect a line like: fb0: ... frame buffer device, memory = ...K 2) Have you tried using the 'fbdev' device in you XF86config? What happens with that driver? Martin
Re: :::TeleVision Hacking:::Superb HardWare Support:::FreeLiveHelpForums::: www.
Question on extended LBA (48Bit) adressing of HDD
Dear listmembers, does anyone of you know how to get a 400 GByte AT - drive formatted to it's full capacity? I am limited to 137GByte, whatever I try to do. My main problem is to understand what is the root cause for this limitation. fdisk does not allow me to assign values crossing this limit. hdparm returns this limit - even though I know exactly that the device is larger than that. Is this a controler issue? A driver issue? Many thanks for helping, take care Dieter Jurzitza -- HARMAN BECKER AUTOMOTIVE SYSTEMS Dr.-Ing. Dieter Jurzitza Manager Hardware Systems ESI Industriegebiet Ittersbach Becker-Göring Str. 16 D-76307 Karlsbad / Germany Phone: +49 (0)7248 71-1577 Fax: +49 (0)7248 71-1216 eMail: [EMAIL PROTECTED] Internet: http://www.becker.de *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. ***
Re: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Jurzitza, Dieter um 14:51: Dear listmembers, does anyone of you know how to get a 400 GByte AT - drive formatted to it's full capacity? I am limited to 137GByte, whatever I try to do. My main problem is to understand what is the root cause for this limitation. fdisk does not allow me to assign values crossing this limit. hdparm returns this limit - even though I know exactly that the device is larger than that. Is this a controler issue? A driver issue? Many thanks for helping, under ggole i found something like this Linux 2.6.0-test4* ide: limit drive capacity to 137GB if host doesn't support LBA48 this looks for me that if you host does not support lba48 the you can not use drives bigger than 137gb so no its up to you. does your host support lba48? regards daniel take care Dieter Jurzitza signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
RE: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Jurzitza, Dieter um 16:42: Dear listmembers, dear Daniel, the formatting works now, this has been my fault (as always ...). However, I am running into severe file-system corruption. I have been initializing a 40GByte Maxtor hdd, copied files to it, and I could boot. Everything runs just smooth. Doing the same with the new 400G Hitachi drive results in massive file-system corruption. Copying seems to work ok, but after trying to boot from this disk I get a total mess. DMA is turned off in all cases (at the boot prompt). This ought to be a pickyness of the controler, isn't it (Promise 133 TX2 PCI-Device) i use the promise 133 ultra tx2 with chipset pdc20269 works here really fine with some 200GB and 160GB Hardrives connected one thing you can check is if you need to enable lba48 somwhere in the drive with a manufacter tool. example: i recived a set of samsung sp1604n wich is udma6/133 capable. but my controller tells me that all my drives are only using udma5 so i contacted the manufacter and the told me that i need hutil from samsung-website to set the harddrive(bios inside HD) to enable udma6. i know udma is not responsible for size but just as example regards daniel Any ideas? Again, many thanks for your help, take care Dieter Jurzitza -Original Message- From: Daniel J. Priem [mailto:[EMAIL PROTECTED] *** ide: limit drive capacity to 137GB if host doesn't support LBA48 this looks for me that if you host does not support lba48 the you can *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. *** signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
RE: Question on extended LBA (48Bit) adressing of HDD
Am Fr, den 10.09.2004 schrieb Daniel J. Priem um 17:05: Am Fr, den 10.09.2004 schrieb Jurzitza, Dieter um 16:42: Dear listmembers, dear Daniel, the formatting works now, this has been my fault (as always ...). However, I am running into severe file-system corruption. I have been initializing a 40GByte Maxtor hdd, copied files to it, and I could boot. Everything runs just smooth. Doing the same with the new 400G Hitachi drive results in massive file-system corruption. Copying seems to work ok, but after trying to boot from this disk I get a total mess. DMA is turned off in all cases (at the boot prompt). This ought to be a pickyness of the controler, isn't it (Promise 133 TX2 PCI-Device) ah. forgot something important what is the bios revision on your controller? if its before 2.20.0.12( was mine) then you need to flash it to a newer version i use the promise 133 ultra tx2 with chipset pdc20269 works here really fine with some 200GB and 160GB Hardrives connected one thing you can check is if you need to enable lba48 somwhere in the drive with a manufacter tool. example: i recived a set of samsung sp1604n wich is udma6/133 capable. but my controller tells me that all my drives are only using udma5 so i contacted the manufacter and the told me that i need hutil from samsung-website to set the harddrive(bios inside HD) to enable udma6. i know udma is not responsible for size but just as example regards daniel Any ideas? Again, many thanks for your help, take care Dieter Jurzitza -Original Message- From: Daniel J. Priem [mailto:[EMAIL PROTECTED] *** ide: limit drive capacity to 137GB if host doesn't support LBA48 this looks for me that if you host does not support lba48 the you can *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. *** signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Kernel 2.6.8 - SILO/initrd problems
(warning newbie alert ) Now that i've got that over with... I've just installed Debian (sarge-testing release) (no, not for the first time) on a Sparc Ultra 5 machine, I wanted to upgrade to the new kernel (2.6.8), so I naturally did the following like a good Debian user: apt-get install linux-kernel-image-package-name-for-sparc64-2.6.8 It installed, and warned me about setting up the boot loader properly (I thought nothing of it at the time, which, of course, I should have). I continued through, and rebooted, only to be greeted with 2 things I didnt expect: First: after SILO boot: the white screen was cleared, and a whole lot of loading info came up on the screen, still apparently in openprom (white background, large black text), the cursor scanned rapidly across the entire screen several times (is that normal?) and ends withg the line Console: switching to mono PROM 80x66, and then the regular linux boot started.. then I encountered the following three lines: VFS: cannot open root device hda1 or unknown -block(0,0) Please append a correct root= boot option Kernel panic: VFS: unable to mount root fs on unknown-block(0,0) booting into openprom, I cat'd the /boot/silo.conf and found: root=/dev/hda1 partition=1 default=Linux read-only timeout=100 image=/boot/vmlinuz label=Linux image=/boot/vmlinuz.old label=LinuxOLD booting LinuxOLD works (as it did previously) and is version 2.4.26 Does the new kernel need something I'm not giving it ? is there something painfully obvious I should do ? and I hate to ask this.. but if it's obvious... why do I need to do it ? (shouldnt it be done for me ?) P.S I tried adding initrd=/boot/initrd.img to the /boot/silo.conf file.. and while linux then booted to my login prompt, the keyboard mapping was incredibly messed up (tried lots of different keyboards, too), when I stop back into openprom the keyboard works (but only in openprom) For instance, a is mapped to 1 and s is mapped to 2 and d is mapped to 3 and CapsLock is mapped to t. Sounds like something got royally messed up in some crucial memory area ideas? Thanks, Adam Lesser
Re: Kernel 2.6.8 - SILO/initrd problems
[...installed debian kernel-image 2.6.8 package...] [...didn't work...] P.S I tried adding initrd=/boot/initrd.img to the /boot/silo.conf file.. and while linux then booted to my login prompt, the keyboard mapping was incredibly messed up (tried lots of different keyboards, too), when I stop back into openprom the keyboard works (but only in openprom) For instance, a is mapped to 1 and s is mapped to 2 and d is mapped to 3 and CapsLock is mapped to t. Sounds like something got royally messed up in some crucial memory area ideas? AFAIK you need to have the initrd line in your silo.conf. However 2.6.x kernels appear to be broken under debian ATM - the reason that I'm not using 2.6.x :( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269405 kernel-image-2.6.8-1-sparc64: keyboard problem [bug in console-data] -- Neil
Re: Kernel 2.6.8 - SILO/initrd problems
On Sat, 11 Sep 2004 01:00:18 +0100 Neil Pilgrim [EMAIL PROTECTED] wrote: AFAIK you need to have the initrd line in your silo.conf. However 2.6.x kernels appear to be broken under debian ATM - the reason that I'm not using 2.6.x :( I do all of my 2.6.x kernel development, and I mean all of it even kernel networking maintainence, on sparc64. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269405 kernel-image-2.6.8-1-sparc64: keyboard problem [bug in console-data] If you simply, as the bug report recommends, run dpkg-reconfigure on console-data package and tell it to simply use the kernel keymap things will work perfectly fine for both 2.4.x and 2.6.x kernels on sparc64. I guess tha answers your question in the bug report.
RE: Question on extended LBA (48Bit) adressing of HDD
Dear listmembers, dear Daniel, the formatting works now, this has been my fault (as always ...). However, I am running into severe file-system corruption. I have been initializing a 40GByte Maxtor hdd, copied files to it, and I could boot. Everything runs just smooth. Doing the same with the new 400G Hitachi drive results in massive file-system corruption. Copying seems to work ok, but after trying to boot from this disk I get a total mess. DMA is turned off in all cases (at the boot prompt). This ought to be a pickyness of the controler, isn't it (Promise 133 TX2 PCI-Device) Any ideas? Again, many thanks for your help, take care Dieter Jurzitza -Original Message- From: Daniel J. Priem [mailto:[EMAIL PROTECTED] *** ide: limit drive capacity to 137GB if host doesn't support LBA48 this looks for me that if you host does not support lba48 the you can *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. ***
