Re: [D-I] Question about setting up palo/ext2 boot partition
On Tue, Apr 17, 2007 at 10:41:13AM -0400, Kyle McMartin wrote: the palo boot partition is just a regular ext2/ext3 partition, with a chunk of disk reserved with badblocks for the boot information, this could be done with mke2fs in partman the same way other flags are set (block size, etc.) FWIW, I found that fsck reclaims these blocks. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] HCRX-24 and missing consoles on my C200
On Mon, Dec 19, 2005 at 05:07:17PM +, Stuart Brady wrote:
On Mon, Dec 19, 2005 at 04:39:43PM +0100, Helge Deller wrote:
Hi all,
I just committed a patch to stifb in kernel 2.6.15-rc6-pa1.
Could you please try this one? It works for me... :-)
Stuart's hint with starting X and then switching back again pointed to
a bug in the palette handling of stifb, which I hopefully fixed now.
Ooh! I'll test this... Unfortunately, I'm compiling on a 715/100 so
bear with me for a moment. :)
Seems to work fine... except for a few black patches on Tux's feet.
I've tested using:
for n in 0 1; do
for m in 0 4 1 5 2 6 3 7; do
echo -e \033[${n};3${m}mTesting\033[m
done
done
Works as expected.
--
Stuart Brady
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] HCRX-24 and missing consoles on my C200
On Thu, Dec 08, 2005 at 11:56:32AM +0100, Andy Walker wrote: Note that the A4071B/HCRX24 gets detected just fine. Its set in PDC as the console path, and also via the sti=8/8 parameter. Nothing crashes, but the console is unusable. Most of the output is black on black, though I get bits of text in magenta, yellow and green depending on the intended colour. Tux has a bright green background and is otherwise pretty psychedelic. Back to Vis-EG for the time being. Have you tried running X, and then switching back to the console? That at least gets it working for me... I wonder which devices are affected by this? What about the A4071A? I've tried reading the stifb source but I'm quite baffled by it. :-( -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] HCRX-24 and missing consoles on my C200
On Wed, Dec 07, 2005 at 01:29:13PM -0500, Kyle McMartin wrote:
I think I have a HCRX here (A4070 with A4072), I can try and fix this
but not until at least January.
This looks like the same card that I have:
1. Coral SGC Graphics at 0xf400 [0] { 10, 0x0, 0x004, 0x00077 }
...
STI GSC/PCI core graphics driver Version 0.9a
id 2bcb015a-9a02587, conforms to spec rev. 8.04
graphics card name: HPA4071B_LZ
I tested this recently on my 715/100:
http://lists.parisc-linux.org/pipermail/parisc-linux/2005-November/027654.html
(Worked fine, except for a few small glitches.)
--
Stuart Brady
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting problem
On Sat, Sep 17, 2005 at 06:56:16PM -0400, Gabriel Avila wrote: I managed to install everything perfectly but now when i start the initial bootup the system hangs after this line: HP SDC MLC: registering the Sytem Domain Controller's HIL MLC. after this line it symply stops the booting process. I did gave it time (5hrs) so just in case it needed some time to finish the process but to no avail. Any Ideas are very welcome. TIA IIUC, the kernel that's used in the installer is a uniprocessor kernel, but I think an SMP kernel is installed. I don't know what the bug is, or whether it has been fixed in later kernels. However, you might be able to work around it. From memory, it's something like this: * Run the installer again. Answer questions until the initial question about partitioning the disk drive. _Don't_ answer that question. * Instead, press Alt-F2 and Enter. You should now get a shell. * Now do mkdir /tmpmnt, followed by something like mount /dev/scsi/discs/discN/partM /tmpmnt where N and M are the disc and partion numbers for your root device. (Although I'm not quite sure whether I've remembered that correctly. * Run chroot /tmpmnt, and mount any other important partitions. If you have a /boot partition, you'll need to mount that. You also need to mount /proc. * Run apt-get remove kernel-image-2.6.8-2-32-smp to remove the SMP kernel image, followed by apt-get install kernel-image-2.6.8-2-32 to install the uniprocessor image. * Unmount the filesystems. Provided that I've not missed anything, booting might work. I hope I've not made any mistakes. There may be a much better way of doing this, but it worked for me. You might still have this problem: http://lists.parisc-linux.org/pipermail/parisc-linux/2005-July/026884.html That seems to be fixed in later kernel images, though. Regards, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Where is the best download location for hppa sarge files ???
On Tue, May 24, 2005 at 01:13:54PM -0700, Ou Phrontis wrote: Where is the best location to download Debian hppa sarge iso images. The mirror that's closest to you is best, as long as it has the images. There's a list of mirrors at http://www.debian.org/CD/http-ftp/ It seems you should really be using Jigdo, though (but I don't use ISO images, so I don't know how well it works). If you're worried that the images you download might be corrupted, you should run md5sum on each image, and check the result against the MD5SUMS file. specifically the r3.0 r5 Some mirrors have these, some don't. They'll be in 3.0_r5/hppa unless there are some r3.1 files out there. There are testing images, but the mirrors don't have them, so it's better to use Jigdo for these. See http://www.debian.org/distrib/cd/ -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XWindow not working on HP 715/50
On Sun, May 15, 2005 at 03:30:24PM -0600, [EMAIL PROTECTED] wrote: I have recently installed Debian on a HPPA Apollo 715/50 workstation. The X server is not working, however, the text mode seems to be OK. Is this *really* text mode? Or does this draw pixels on the screen? : dd if=/dev/urandom of=/dev/fb0 count=200 /dev/null Below, I have included the contents of files XFree86.0.log and XFree86.8.log. Can you send /etc/X11/XF86Config-4 to the list, please? Also, we need the output of: cat /sys/class/graphics/fb0/modes cat /sys/class/graphics/fb0/bits_per_pixel Is it related to some limitation of the Debian system for HPPA hardware or I have not installed the Debian system properly or is it a bug?. If it is a bug, how can I find the package responsible for error. That's impossible to answer until we know why it isn't working. BTW, the stifb driver can't change the screen resolution, so what you have in /etc/XF86Config-4 has to match the current resolution (which you can change from the PDC BOOT_ADMIN prompt). (FWIW, it should be possible to fix the driver.) -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
On Mon, Mar 28, 2005 at 12:31:02PM -0600, James Bottomley wrote: Actually, you need to tell the system that eth0 should load module lasi_82596 so /etc/modprobe.conf needs to contain the line alias eth0 lasi_82596 However, debian has a strange way of generating this file, so this line actually has to go in some debian specific file. The line should go in a new file under /etc/modprobe.d/ -- if you modify an existing file in that directory, you'll have to edit it whenever module-init-tools is upgraded. You needn't run /sbin/update-modules with 2.6. /etc/modprobe.conf is optional, and modprobe reads each file in /etc/modprobe.d/ (except for those in the arch/ directory). FWIW, with Debian and a 2.4 kernel, /etc/modutils/ contains similar files to /etc/modprobe.d/. The main difference is that you have to run /sbin/update-modules to generate /etc/modules.conf so that your changes take effect. HTH, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel config for 2.6.8-2-32-smp (sarge)
On Mon, Mar 21, 2005 at 10:12:49PM +, David Pye wrote: Also, when playing any audio on my J5000 (AD1889 audio chip) I get the syslog instantly flooded with : Starting playback at 0x4dbc5000 for 57344 bytes Writing 0x1000 bytes to +0x13000 Writing 0x1000 bytes to +0x14000 Writing 0x1000 bytes to +0x15000 Writing 0x1000 bytes to +0x16000 Writing 0x1000 bytes to +0x17000 WAV interrupt Starting playback at 0x4dbd3000 for 20480 bytes WAV interrupt Any idea what causes that, and also, whether it should be turned off in the Debian kernel by default? The AD1889 drivers (for both OSS and ALSA) are experimental. Don't expect them to work just yet (although there have been some reports of the OSS driver working with 48KHz wavs, but I've not had any luck). USB audio may be your best bet for the time being. HTH, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Re: J5000 LCD heartbeat
On Sun, Mar 20, 2005 at 09:03:57PM +0100, Thibaut VARENE wrote:
it's not that simple.
If you want to have it gone, add
@reboot echo /proc/pdc/lcd
in your root crontab :)
BTW, If anyone really wants scrolling, this script should do it. It has
to use character 16 for spaces, which is a bit broken -- YMMV.
#!/bin/bash
STR=Linux $(uname -r)
END=
# Prevent the PDC from stripping leading spaces by
# using character 16 (octal 20) as a space...
STR=$(echo $STR | tr ' ' '\20')
while(true); do
echo ${STR}${END} /proc/pdc/lcd
END=${END}${STR:0:1}
STR=${STR:1}
if [ -z ${STR:-} ]; then
STR=${END}
END=
fi
sleep 0.25
done
The character set is interesting:
1-8 for the disk/network/heartbeat symbols
32-127 are the standard ascii characters, except that:
92 is a yen symbol
126 is a left arrow
127 is a right arrow
128-159 are unused
160-254 seem to be a mix of japanese, greek and accented roman letters
240 is an empty box
255 is a filled in square
Hope that helps,
--
Stuart Brady
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
On Sat, Mar 05, 2005 at 06:52:57PM -0500, Harry Cochran wrote: d. Assuming your f0 partition is on sda1, mount /dev/sda1 mnt This should have been /mnt. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /boot
On Sat, Feb 26, 2005 at 11:11:50PM -0700, Grant Grundler wrote: Could you replace --update-partition= with --init-partition=? I'm expecting palo to blow everything on f0 away and build a new ext2 file system. THen you can: o mount /dev/sda1 /mnt o copy /boot/* /mnt o edit /etc/fstab so /dev/sda1 is mounted on /boot. If that boots, then: o unmount /boot That should be: o umount /boot o rm /boot/* o mount /boot As you might guess, the order is important. :^) -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /boot
On Sun, Feb 27, 2005 at 08:55:41AM -0500, Harry Cochran wrote: On Sat, Feb 26, 2005 at 1:12AM -0500, Grant Grundler wrote: I'm expecting palo to blow everything on f0 away and build a new ext2 file system. THen you can: o mount /dev/sda1 /mnt o copy /boot/* /mnt o edit /etc/fstab so /dev/sda1 is mounted on /boot. Done. And it boots 2.6.8-2-32-smp! Great! If that boots, then: o unmount /boot No ... umount /boot or umount -f /boot comes back with: device is busy Did you do a cd /boot, by any chance? If so, you need to go out of /boot before you can unmount it. Is there a problem leaving the redundant /boot on sda3? No. In fact, you need it -- it's the mount point. The redundant /boot (on sda3) would ideally be empty, but do not delete the contents of the mounted /boot (on sda1)! If there's anything inside /boot on sda3, you simply won't see it while sda1 is mounted there, which could be confusing, but shouldn't cause any harm. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /boot
On Sun, Feb 27, 2005 at 08:55:41AM -0500, Harry Cochran wrote: On Sat, Feb 26, 2005 at 1:12AM -0500, Grant Grundler wrote: ls -l /boot SinoHub5:/# ls -l /boot total 0 The ls command assumes the f0 partition is mounted on /boot. Well I was feeling pretty good until I saw ls -l /boot come back with total 0. I assume that's bad news. You didn't say to change init-partitioned to update-partitioned, so maybe I screwed up there. Should I have just gotten rid of that line? If sda1 is mounted on /boot and it is empty, then yes, that's bad. If I understand correctly, --init-partition formats the partition, and as a result, clears any files that were it previously held... If that's right, it's better to pass --init-partition to palo, than it is to add --init-partition in palo.conf, since you won't have to worry about changing it back afterwards. You'll have to copy the files from /boot again (using /mnt for sda1, making sure you've unmounted /boot first). -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: /boot
On Sun, Feb 27, 2005 at 01:06:13PM -0500, Harry Cochran wrote: On Sun, Feb 27, 2005 at 12:37:25PM -0500, Grant Grundler wrote: No - mount /dev/sda1 /boot will overlay and hide the original contents on /dev/sda3. So you are saying that unless you can umount /boot, you can't get to /boot on sda3, right? Correct. The problem that started this thread is that I can't umount /boot. I just get device is busy. I have cd'd to /var which is on sdb1, but I still can't umount /boot. Run this before you try to unmount /boot: /etc/init.d/klogd stop (Thanks to Joel for pointing this out.) Actually apt-get remove kernel-image-2.6.8-2-32-smp and then apt-get install kernel-image-2.6.8-2-32-smp did work with a lot of complaining :-) (I did it before I got your email). Great, but remember that sda1 should be mounted as /boot when you do the install -- otherwise, you'll have to move the files across afterwards. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PA-RISC/Linux Boot HOWTO: 2.4 - 2.6
On Sun, Feb 27, 2005 at 02:05:45PM -0500, Harry Cochran wrote: 8.1 Check your 2.4 partition scheme It is relatively easy to set up a partition scheme that will work for a while, but then stop working when root starts to fill up. For example: This was due to using an incorrect partition scheme in the first place. I'm not sure that this belongs in a HOWTO that explains how to upgrade from 2.4 to 2.6. Documentation explaining how to use the palo partition as the /boot partition seems worth having, but it's surely a separate issue. I'm the conservative type, so I don't load from testing. At the time of this writing, the 2.6 kernels in unstable are 2.6.8-2-32, 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. I don't get this -- testing is safer than unstable. -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: FW: 2.4 - 2.6
On Sat, Feb 26, 2005 at 12:17:26PM -0500, Harry Cochran wrote: Thank you all very much! I now have a running 2.6.8-2-32-smp on my J6000. I repartitioned sda to have the root right next to the f0 partition (and the swap at the end) per Grant, No, that isn't what Grant said... The Boot HOWTO explains that the kernel image must be located within the first 2GB of the disk. The only sensible way to ensure this is to have a dedicated /boot partition, which is contained entirely within the first 2GB. This needn't be large -- a 64MB partition should be ample. In your case, it doesn't matter whether this is before or after the 1GB swap partition, but it must come before the large root (/) partition. AFAICS, although your new partition scheme may appear to be working, it may cease to work whenever the kernel is upgraded. (By swapping the partitions you are effectively doubling the amount of disk space from the first 2GB which is used for the root partition.) Hope that helps, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] debootstrap failure?
On Mon, Sep 20, 2004 at 07:27:05AM +0200, Matthias Klose wrote: gcc-3.0 was removed from sid. make sure you use debootstrap 0.2.44 or later. I think this means we need new debian-installer images... I'm getting the same problem with the current boot.img. -- Stuart Brady
Tag starvation with HPPA kernel
On Thu, Sep 16, 2004 at 12:31:38PM +0200, W. Borgert wrote: a colleague tried to install Debian on his HP712/60 with standard SCSI adaptor (whatever that is). He used the d-i testing image of 2004-08-20. The d-i went smoothly until the creation of file systems. The kernel output on the fourth console said: SCSI device sda: 8467200 512-bytes hdwr sectorrs (4335 MB) p6 adding swap: 191044k swap-space (priority -1) scsi0 (3:0) target is suffering from tag starvation. scsi0 (3:0) broken device is looping in contingent allegiance: ignoring After that, the system is stone dead. As he tried also with two more 712/60s and also tried other d-i versions, I believe, there must be a fundamental problem. Any ideas? I think this is a known problem. To get an idea of the numbers, can anyone who is affected by this mail me privately with the number of machines affected, please. If you can also give give me extra details, such as what machine and drive you have, and what value of NCR_700_MAX_TAGS works, that'd be great! For the time being, he may want to do what I do, which is to install woody and then upgrade to testing. The workaround requires rebuilding the kernel with NCR_700_MAX_TAGS changed to 1 in drivers/scsi/53c700.h. Perhaps this workaround should be used if a proper fix isn't found by then? Does the freeze prevent that? BTW, this only affects my machine with the 2.4 kernel (not 2.6). Does anyone have this problem with 2.6 at all? -- Stuart Brady
Re: framebuffer broken on 712 using kernel 2.6.4
On Thu, Aug 19, 2004 at 09:52:32AM +0300, Martin-Éric Racine wrote: [Snip] 2) all 2.6.x since 2.6.5 The PA-RISC Tux appears. Everything within the lines it occupies is a clean pitch black. Bootup messages start on the last line of the penguin, overlaping its legs. Messages up to Gecko-style soft power switch enabled. scroll on below. Messages following that appear on the feet of the penguin again and are all printed there, without scrolling down. Once the INIT: version 2.86 message appears at that location, things magically resume a few lines below the powerswitch kernel message, starting with the Setting disc parameters: done. message and scroll down, eventually making the penguin scroll off-screen. Try it with: STI_CONSOLE=y (STI text console) DUMMY_CONSOLE_COLUMNS=c (Initial number of console screen columns) DUMMY_CONSOLE_ROWS=r (Initial number of console screen rows) Where c is the screen width (in pixels) divided by 8 (E.g. 1024/8=128) and r is the height divided by 16 (E.g. 768/16=48). (These options are under Device Drivers - Graphics support - Console display driver support.) I don't know whether you actually need sticon itself, but you need to choose in order to set the columns/rows. Perhaps that's a bug. Hope that helps, -- Stuart Brady
Re: framebuffer broken on 712 using kernel 2.6.4
On Sat, Sep 04, 2004 at 12:45:50AM +0300, Martin-?ric Racine wrote: So I tried again with the following: source 2.6.8.1-pa7 gcc 3.4.1 binutils 2.15 Same result as before: PA Tux has its legs chopped and the bootup messages are a real mess. I have the same problem on a 715/100 with: source 2.6.8.1-pa7 gcc 3.3.4-6sarge1.2 binutils 2.15-1 It goes away once init is started. -- Stuart Brady
Re: Getting a smp kernel on my J6000
On Mon, Jun 07, 2004 at 03:03:48PM -0400, Harry Cochran wrote: I tried putting http://cvs.parisc-linux.org/download/linux-2.4/autobuild/debian-64-smp/ ./ in sources.list and doing an apt-cache search palinux-debian-64-smp-2.4.26-pa4. This returned Couldn't stat source package list (2 no such file or directory). This is the message that you get if you don't run apt-get update after editing /etc/apt/sources.list. If you miss the deb off the start of the line, then it will be ignored by apt-cache search, but apt-get update will give the error message: E: Type 'http://cvs.parisc-linux.org/download/linux-2.4/autobuild/debian-64-smp/' is not known in on line 1 in source list /etc/apt/sources.list Err, and there's a typo in the error message, by the looks of it! :-) -- Stuart Brady
