Re: Call for Debian Installer testing, before D-I Beta1 release
On Wed, Feb 20, 2008 at 11:07:03AM +0100, Frans Pop wrote: On Wednesday 20 February 2008, Grant Grundler wrote: Please, go in your installed system and use the installation-report script to send us a full installation report, that way we can get more information about how things went there. I'm not near the system for the next couple of days but will do that when I get back - thanks for pointing that out. That's not really needed anymore as I've already made the necessary changes to detect smp support. They will only be uploaded after the Beta1 release though. See also my replies to your original mail (not CCed). ok - cool Grant, do you happen to know a similar trick to detect 64-bit support even when the installer is running with a 32-bit kernel? Hrm...yes. I explain the trick and also some caveats on why I would rather leave this user selectable. [EMAIL PROTECTED]:~$ fgrep PA-RISC 2.0 /proc/cpuinfo cpu family : PA-RISC 2.0 cpu family : PA-RISC 2.0 Anything with PA 2.0 CPU can run 64-bit. In general, we want to run 32-bit kernel because: o PA-RISC to date _only_ has a 32-bit usr space. So all syscalls to a 64-bit kernel go through a wrapper to convert 32-bit user space arguments to 64-bit kernel calling conventions. (some work is being done to enable 64-bit user space but it's not ready yet). o pointers are smaller and thus data structures are more compact. Simple applications are _slower_ with 64-bit. We must/can run 64-bit IFF: o PAT PDC (aka BIOS) - palo boot loader detects PAT PDC and will attempt to boot a 64-bit kernel. No changes needed for this. o chunks of physical memory are mapped above 4GB. Different platforms will have different physical memory maps. /proc/meminfo is of no help here. But /proc/iomem might be helpful: [EMAIL PROTECTED]:~$ fgrep System RAM /proc/iomem -efff : System RAM 1-1 : System RAM 10f000-10 : System RAM These are the physical addresses of RAM for an A500 (aka rp2470) with 8GB of RAM: [EMAIL PROTECTED]:~$ cat /proc/meminfo MemTotal: 8239436 kB MemFree:414672 kB Buffers: 1812020 kB Cached:4587320 kB SwapCached: 72 kB Active:4434600 kB Inactive: 2115708 kB ... This is really only a problem for Astro (e.g. C3000) chipset workstations. They have PA2.0 CPUs and can have physical RAM above 4GB address. Currently the installer will only select a 64-bit kernel if the user changed to the 64-bit D-I kernel when the installer was booted (which can be done by answering Yes to the question asked by the firmware whether you want to interact with the boot loader). Unless someone wants to code up the above rules, my preference would be to leave this up to the user. We can revisit this issue when 64-bit user space is working. thanks, grant Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Call for Debian Installer testing, before D-I Beta1 release
On Mon, Feb 18, 2008 at 09:54:22AM -0300, Otavio Salvador wrote: ... And this is my installation report. I didn't see any other guidance on where/how to submit the installation reports. Please, go in your installed system and use the installation-report script to send us a full installation report, that way we can get more information about how things went there. I'm not near the system for the next couple of days but will do that when I get back - thanks for pointing that out. I've checked base-installer code and it has code to handle hppa smp machines. Probably 2.6.22 had a problem to enable your second processor and then this might be fixed once we go to 2.6.24. Well, historically, hppa has had problems with SMP kernels. AFAIK, the worst of those have been fixed and SMP seems (in general) stable. Filling a full installation report will allow us to check if this code has issues or if it wasn't properly detected. ok - will do. Expect that within a week. thanks, grant -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://otavio.ossystems.com.br - Microsoft sells you Windows ... Linux gives you the whole house. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Call for Debian Installer testing, before D-I Beta1 release
On Mon, Feb 04, 2008 at 08:34:54PM -0200, Otavio Salvador wrote:
We're starting the work for D-I Beta1 release and we would like ask to
everyone to test the installer as much as possible, especially in not
so common architectures where we receive less general testing.
Otavio,
On Feb 9, I pulled the 150MB net install ISO image, burned a CD
and tested that today on my j6000 (hppa, aka parisc). Install
options selected were /home and used dhcp to config the network.
(I had to setup a dhcpd on my laptop, which was a NAT'd gateway).
Install succeeded and system rebooted to a 32-bit UP kernel.
(2.6.22-3-parisc #2 Mon Nov 12 20:42:16 CET 2007). This box only
has 2GB of RAM installed and 2 CPUs.
So despite ability to run 64-bit kernel, 32-bit kernel is fine.
SMP would have been appropriate though. Installing SMP kernel is not
a critical issue. Folks can easily figure out how to install an SMP
kernel and SMP kernel might not be as stable for some configurations.
So leaving that to the user is fine with me. I just want to share how
detection might be implemented.
Kernel at boot time signals the additional CPUs in two ways:
...
Searching for devices...
Found devices:
...
6. Duet W+ at 0xfffa [32] { 0, 0x0, 0x5d4, 0x4 }
7. Duet W+ at 0xfffa2000 [34] { 0, 0x0, 0x5d4, 0x4 }
8. Memory at 0xfed10200 [49] { 1, 0x0, 0x00a, 0x9 }
Enabling regular chassis codes support v0.05
CONFIG_SMP=n ignoring additional CPUs
CPU: probe of 34 failed with error 1
...
First, the probe failure and then the fact that multiple CPUs are listed.
Runtime test for the hppa installer might be to scrounge in
/sys/bus/parisc/devices for hw_type contains 0x00.
e.g.:
j6k:~# fgrep 0x00 /sys/bus/parisc/devices/*/hw_type
/sys/bus/parisc/devices/32/hw_type:0x00
/sys/bus/parisc/devices/34/hw_type:0x00
In the current timeline, we will stop to accept fixes for the
installer in few days so any important issues need to be fixed _now_.
You can find the latest installer, for your pet architecture, at
http://www.debian.org/devel/debian-installer/ and if you find any
issues file a installation report.
BTW, the News section of that web page needs love. :)
[21 Jul 2007] Support for sparc32 dropped
[20 Jul 2007] Experimental support for Serial ATA RAID
isn't exactly news anymore ;)
And this is my installation report. I didn't see any other guidance
on where/how to submit the installation reports.
Thanks in advance and let's make Lenny the best release ever made!
thanks too!
grant
Cheers,
Otavio Salvador
on behalf of Debian Installer Team
- --
O T A V I OS A L V A D O R
- -
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
- -
Microsoft sells you Windows ... Linux gives
you the whole house.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ http://mailcrypt.sourceforge.net/
iD8DBQFHp5L1LqiZQEml+FURAm5PAKCf8IPsN9zFHhth5pio7NY3MpEgdQCeIIn5
RAYua80aQbLTjk9BDfupWRU=
=cTEq
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
testing 20070705 Lenny on ia64 (rx3600)
Hi! I tried debian-testing-ia64-netinst.iso last week: 2df367739e7ee1e8a01ecc357b78aee9 debian-testing-ia64-netinst.iso IIRC, it's from 20070507. Not useable because network drivers are completely missing from the initrd. Drop into a shell and look at /lib/modules/*/kernel/drivers/net/. It's not there. It should be there because zcat /proc/config.gz | fgrep E1000 shows E1000 is compiled in as a module. I was able to install with Debian 4.0 r0 etch. But I'm hopeful the testing release could sort out one nit with the etch installer. HP IA64 setup CD suggests two EFI partitions be created: One for boot and the other hidden partition for System diags. The guided (IIRC) partition completely ignores the existing partitions and only creates a boot partition - ie overwritting the diags. If disk is already partitioned, I'd prefer the automatic partitioning code ask if it should repartition (clobber existing) or exit guided mode and force user to manually select the remaining partitions. thanks and hth, grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [D-I] mass kernel udeb update and preparations for RC1
On Fri, Sep 22, 2006 at 02:31:43PM +0200, Frans Pop wrote: (Reply-to set to debian-boot; please only add relevant port if needed.) [ offlist ] /me wonders why there have been almost no reactions to this mail The first part is mostly information (though a cool or thanks would be appreciated), Thanks! :) I don't respond to every mail just because it feels like noise to get back a ton a short emails. But I do appreciate the effort you've put into it and am very impressed that mass uploads are even possible. but the second part has some issues that need attention. I didn't see anything for parisc (HPPA). I don't know of any problems with initramfs on parisc. but I don't expect any surprises from the kernel on that. Have D-I porters actually read the mail? Yes - I did. Is it useful that I send such mails at all? Yes. kudos and thanks! grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [hardware-donation] HP 9000 D220 (France)
On Sun, Mar 26, 2006 at 10:59:16PM +0100, Martin Michlmayr wrote: If anyone is interested in the following machine for development, please get in contact with [EMAIL PROTECTED] * Christophe Lucas [EMAIL PROTECTED] [2006-03-25 19:26]: RotomaLUG(http://www.rotomalug.org/) is LUG of Rouen area (France). We have had a donation of HP9000 machines. We have HP9000 D220. We have one of this machine to give to you. I also have two more B180s (also PA-7300LC CPU) and some faster 3000/J6000 machines here if someone is interested. Must pick up or arrange pick up. thanks, grant Matthew Wilcox says that the ``D220 should be totally supported, except for the EISA slots'' and that `` he 7300LC is quite acceptably fast; it's the last 32-bit PA processor, but quite nice.'' See also http://www.parisc-linux.org/hardware/supported.html -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [hardware-donation] HP 9000 D220 (France)
On Sun, Mar 26, 2006 at 10:23:15PM -0700, Matthew Wilcox wrote: On Sun, Mar 26, 2006 at 10:30:05PM -0700, Grant Grundler wrote: I also have two more B180s (also PA-7300LC CPU) and some faster 3000/J6000 machines here if someone is interested. Must pick up or arrange pick up. ... from the Silicon Valley area ;-) yes - thanks willy! :) grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Detect HW step UI broken
Hi, I tested this netinstall ISO image on HP lt6000r/700 Netserver: grundler 504ls -l debian-testing-i386-netinst.iso -rw-r--r-- 1 grundler grundler 120643584 2006-03-14 09:03 debian-testing-i386-netinst.iso grundler 505md5sum debian-testing-i386-netinst.iso 8213f19c9c7b7b4cd14d4b6e3e704a28 debian-testing-i386-netinst.iso HP lt6000r/700 Netserver is PIII 700Mhz/2MB cache, 6-way, 2GB RAM, serverworks/broadcom chipsets, 64-bit/66Mhz PCI slots, and 4 hotplug Ultra2 SCSI disks. I had upgraded all the firmware and configured the built-in SCSI controller to LVD SCSI mode (it can be configured as NetRAID too). (BTW, Detect Disks step could not find any disks until I restored the LVD LSI 53c896 BIOS parameters to default. No clue what was wrong before.) The issues with Detect HW steps are: 1) enables _all_ drivers to be loaded at each of the three Detect HW step. System would hang when trying to load VIA IDE driver. This box has a serverworks chipset and serverworks IDE driver was already loaded. 2) UI hides the drivers that are already loaded. I want to see which driver it has already loaded and _only_ those should be marked in the list. That way additional drivers can be marked/loaded. 3) UI only presents IDE drivers - no LAN/USB/etc drivers are listed. I got the same list for each of the different Detect Network and Detect Disks steps. In expert mode, I was able to deselect _all_ of the drivers manually each time and make forward progress. udev support will automatically load the correct PCI drivers. Normally, no other interface drivers need to be loaded. Some high level drivers (e.g. sd_mod or ide_cd) might need to be loaded manually. Base system install completed and then after selecting Web Server in addition to the default option (I forget what it is) in tasksel, the system locked up completely 76% of the way into the install. I then went manual, reset the machine, rebooted the CD, did some of the basic steps, entered the shell, chroot /target and finished the install by editing sources.list and running dselect to download/install testing bits. Took three passes of Install in dselect until all the packages were happily installed. Probably would have been better for you guys if I had specified etch. Oh well. BTW, why is 2.6.15-1-686 kernel not offered as an option? I only saw 386 and 486 kernels on the very first pass. Since the network is working, can the 686 kernel be offered as an option as well? I picked that one up when using dselect and it booted (as expected) just fine via grub. hth, grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: D-I Etch Beta2 - Status update (4)
On Tue, Mar 07, 2006 at 02:17:02PM +0100, Frans Pop wrote: To avoid confusion, the direct link to the correct images is: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/$arch/iso-cd/ Frans, thanks for pulling this together and posting the message. I tested the 2006.03.07 image for HPPA on my B2600: -rw-r--r-- 1 grundler grundler 126896128 Mar 7 23:54 debian-testing-hppa-netinst.iso grundler 168cksum debian-testing-hppa-netinst.iso 3532889647 126896128 debian-testing-hppa-netinst.iso The install had some nits and a major bug: o initramfs package failed to install. Retrying got past that. o kernel package installed failed on the second try. Retrying got past that. o I went into the shell to snoop, noted that /sys and /proc was mounted 3 times. I was looking in /proc, not mount output. Makes sense if it doesn't get cleaned up after a failure. After the install reported success and rebooted, the system did not reboot: Firmware Version 1.0 Duplex Console IO Dependent Code (IODC) revision 1 -- (c) Copyright 1995-2000, Hewlett-Packard Company, All rights reserved -- Processor SpeedState Coprocessor State I/D Cache - - - - 0 500 MHzActive Functional 512 kB/1 MB Central Bus Speed: 120 MHz Available memory: 1073741824 bytes Good memory required: 85463040 bytes Primary boot path:FWSCSI.5.0 Alternate boot path: FWSCSI.5.0 Console path: GRAPHICS(2) Keyboard path:USB - Main Menu - Command Description --- --- BOot [PRI|ALT|path] Boot from specified path PAth [PRI|ALT|CON|KEY [path]] Display or modify a path SEArch [DIsplay|[[IPL] [path]]] Search for boot devices COnfiguration [command] Access Configuration menu/commands INformation [command] Access Information menu/commands SERvice [command] Access Service menu/commands DIsplay Redisplay the current menu HElp [menu|command] Display help for menu or command RESET Restart the system - Main Menu: Enter command sea fwscsi Searching for potential boot device(s)... on Path FWSCSI This may take several minutes. To discontinue search, press any key (termination may not be immediate). Path NumberDevice Path Device Type ------- P0 FWSCSI.6.0 QUANTUM ATLAS10KII-9LVD P1 FWSCSI.5.0 SEAGATE ST336704LC
hppa net boot attempt w/2004.09.30 boot.img
Hi all, I tried to netboot the boot.img from 2004.09.30 on an A500 (aka rp2470) parisc machine: http://people.debian.org/~jbailey/d-i/hppa/2004-09-30/boot.img System hangs after last console output. I let the system sit for ~20 minutes and it made no forward progress in that time. I then TOC'd the system to get IP/RP. But I don't have a System.map to lookup which function the CPU spinning/hung in. I need to know what (GR02) 0x10108070 and (IOAQ) 0x1010e06c point at in the kernel. Console output and TOC state is appended. CPU 0 TOC state looks valid. CPU 1 TOC state looks like it's still in firmware rendevous. (ie the linux kernel didn't attempt to talk to it, normal for a UP kernel). hth, grant Information Menu: Enter command la LAN Station Address: 00306e-090174 Information Menu: Enter command pr Model:9000/800/A500-5X PROCESSOR INFORMATION HVERSION SVERSION Processor Processor Speed ModelModel/Op CVERSION State - - 0 550 MHz 0x05d50x0491 3. 1 Active 1 550 MHz 0x05d50x0491 3. 1 Idle Central Bus Speed (in MHz) :111 Software ID (dec) : 1501750558 Software ID (hex) : 0x5982e51e Software Capability : 0x01f0 Information Menu: Enter command maea___ Main Menu --- Command Description --- --- BOot [PRI|ALT|path] Boot from specified path PAth [PRI|ALT] [path] Display or modify a path SEArch [DIsplay|IPL] [path] Search for boot devices COnfiguration menuDisplays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [menu|command] Display help for menu or command RESET Restart the system Main Menu: Enter command or menu sea lan Searching for potential boot device(s) - on Path 0/0/0/0 This may take several minutes. To discontinue search, press any key (termination may not be immediate). Path# Device Path (dec) Device Path (mnem) Device Type - - -- --- P0 0/0/0/0lan.192.168.0.61 LAN Module Main Menu: Enter command or menu bo p0 Interact with IPL (Y, N, or Cancel)? n Booting... Network Station Address 00306e-090174 System IP Address 192.168.0.40 Server IP Address 192.168.0.61 Boot IO Dependent Code (IODC) revision 2 HARD Booted. palo ipl 1.5 [EMAIL PROTECTED] Fri May 14 16:17:38 MDT 2004 Boot image contains: 0/vmlinux32 4078989 bytes @ 0x9800 0/vmlinux64 5849062 bytes @ 0x3ed800 0/ramdisk 2152390 bytes @ 0x981800 Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial). Command line for kernel: 'root=/dev/ram0 console=ttyS0 TERM=vt102 palo_kernel=0/linux' Selected kernel: /linux from partition 0 Selected ramdisk: /ramdisk from partition 0 Warning: kernel name doesn't end with 32 or 64 -- Guessing... Choosing 64-bit kernelELF64 executable Entry 0010 first 0010 n 4 Segment 0 load 0010 size 3263232 mediaptr 0x1000 Segment 1 load 0041e000 size 1098344 mediaptr 0x31e000 Segment 2 load 0052c000 size 327680 mediaptr 0x42b000 Segment 3 load 0058 size 32768 mediaptr 0x47b000 Loading ramdisk 2152390 bytes @ 3fde1000... Branching to kernel entry point 0x0010. If this is the last message you see, you may need to switch your console. This is a common symptom -- search the FAQ and mailing list at parisc-linux.org Linux version 2.4.27-64 ([EMAIL PROTECTED]) (gcc version 3.0.4) #1 Mon Aug 30 01:06:19 CEST 2004 FP[0] enabled: Rev 1 Model 16 The 64-bit Kernel has started... Determining PDC firmware type: 64 bit PAT. model 5d50 0491 0001 5982e51e 10f0 0008 00b2 00b2 vers 0301 CPUID vers 18 rev 11 (0x024b) capabilities 0x1 model 9000/800/A500-5X Total Memory: 3840 Mb initrd: 4fde1000-4ffee7c6 initrd: reserving 3fde1000-3ffee7c6 (mem_max f000) pagetable_init On node 0 totalpages: 983040 zone(0): 983040 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/ram0 console=ttyS0 TERM=vt102 palo_kernel=0/linux Console: colour dummy device 160x64 Calibrating delay loop... 1097.72 BogoMIPS Memory: 3832684k available Dentry cache hash table entries: 131072 (order: 9, 2097152 bytes) Inode cache hash table entries: 131072 (order: 9, 2097152 bytes) Mount cache hash table entries: 256 (order: 0, 4096 bytes) Buffer cache hash table entries: 262144
Bug#254073: [parisc-linux] Re: Bug#254073: tc1 fail on hppa
On Sun, Jun 13, 2004 at 12:41:47PM -0400, Kyle McMartin wrote: Hmm. It's a problem because the firmware of some machines will only boot 64-bit kernels, some will only boot 32-bit, and some will boot either. correct. The best thing to do, would be to always install 32bit by default. No. The best would be to look at uname -m output. Install 32-bit if it's parisc and install 64-bit if it's parisc64. As when a person tries to boot on a machine that only has 64-bit firmware, they will have to manually edit the PALO commandline to use vmlinux64, which will result in them having a parisc64 uname -m entry. So I'd think install based on the uname -m entry would work. Correct, it will. As long as palo can select which kernel to boot from the install media (CD, HD, network), a working kernel will get booted/installed by default. I'm going to copy the parisc-linux list with this, for comments. thanks, grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#247725: installation-reports - hppa c3600 graphical/usb
Package: installation-reports Debian-installer-version: Beta4 5/6/2004 uname -a: Linux debian 2.4.25-32 #1 Mon Apr 19 18:11:19 UTC 2004 parisc unknown Date: 5/6/2004 Method: booted CD from sarge-hppa-netinst.iso http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/hppa/beta4/sarge-hppa-netinst.iso Machine: HP C3600 workstation with PCI VIs-EG/USB console Processor: PA8600 Memory: 4GB Root Device: fwscsi.5.0 Root Size/partition table: n/a Output of lspci: n/a Base System Installation Checklist: Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [?] Detect hard drives: [O] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it [?] = No clue if that was done or worked Comments/Problems: Using the HP USB keyboard (Model SK-2502U, P/N A4983-60401) on an HP C3600, the regular 4 arrow keys (seperate from the numeric keypad) do NOT work. They select instead of moving the highlight up/down. Use the numeric keypad instead - it has arrow keys on it as well. It's more natural to use the regular arrow keys and it should be trivial for the right person to fix. I gather the numeric pad sends out a different scan code than the four arrow keys. I only needed to boot the system to recover a palo (v1.4 built with gcc 3.3.3) which fails to boot. grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
