Re: Problems after dist-upgrade with kernel 2.6.17 in Sun blade 1k

2006-10-02 Thread Jurij Smakov
On Mon, Oct 02, 2006 at 08:44:37PM +0200, Luis Martinez wrote:
> Upgrading to this kernel leaves the blade unbootable, since ql2xxx
> module is used instead of qlogicfc to manage the FCAL disks.
> The module ql2xxx still does not work for the q logic controller on the
> Sun Blade 1000.

Thanks for the report, Luis. I've forwarded the problem report upstream, if it 
is 
not going to be resolved there, I guess we will just pick up the qlogicfc 
driver 
from 2.6.16 and include it in our kernel packages.

Best regards,
-- 
Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/   KeyID: C99E03CC


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Installation manual updates

2006-10-02 Thread Jurij Smakov
Hi,

I have now looked through the complete installation manual for sparc, and 
compiled 
the following list of the topics which require corrections. If you can answer 
any 
of the questions asked there, can perform the particular tests, or just would 
like 
to comment, please do so. Current version of the installation manual which I 
used 
is available at

http://d-i.alioth.debian.org/manual/en.sparc/


Table in section 2.1.1 should list only sun4m, sun4u and sun4v as
supported sparc flavours.

Sections 2.1.3 and 2.1.4 are, in my opinion, redundant, and can be
safely dropped. Information about supported graphics options and
SMP support is included in the corrected version of the 2.1.2
chapter.

In section 2.2.2: "CD-ROM based installation is supported for some
architectures" - this statement is overly generic and redundant. May
be removed?

Chapter 2.2.6 contains the list of supported SCSI devices. Does this
list only includes the drivers included in initrd? Probably needs to
be updated.

Chapter 2.4 - "Purchasing Hardware Specifically for GNU/Linux". This
is probably not useful. Also, in section 2.4.2 "Fake or Virtual Parity
RAM" there is a sentence "f you want complete information on SPARC
RAM issues, and what is the best RAM to buy, see the PC Hardware FAQ",
linking to the PC Hardware FAQ. I very much doubt that this FAQ
contains any information on SPARC RAM.

In chapter 2.5 the requirement of at least 32MB of RAM is listed. I
think that should be bumped to 64MB (or someone should really confirm
that install with 32 megs is possible).

List of the supported network hardware in section 2.6 - needs to be
updated.

Section 3.3.1.2 links to "Linux for SPARC Processors FAQ", which was
last updated in 2003. Is it still useful? Any newer sources of
information?

Section 3.3.2 mentions "BIOS setup screens of your computer". Can
we replace it with something about PROM, which would be more relevant?

It would be good to list the archives of debian-sparc list as a source
of information, perhaps with a specific query for the search engine
(like 'foo bar site:lists.debian.org inurl:debian-sparc).

Chapter 3.4 lists recommended minimum system requirements, and "no
desktop" option mentions 24MB. That does not agree with section 2.5
and I really doubt that you can install with 24MB. Anyone volunteers
to check?

3.5.1 mentions the 1GB magic boundary -- silo will sometimes refuse to
boot the kernel, if it is physically located beyond the 1GB from the
start of the disk. I believe, however that this applies only to
sparc32 machines, is that correct?

3.5.1 also mentions that silo can boot from romfs, I don't think it's
true.

Somewhere around here the bug in parted (probably) should be mentioned,
which leads to misdetection of disk sizes, if the machine has a disk
label created by Solaris. Recreating the disk label with Debian will
*not* resolved it, the only way to work around it so far is to dd the
first few kilobytes of the affected drive with zeros. Bug 384653, for
example. Anybody can try and reproduce it and provide debugging
information?

Links to "Sun Openboot Reference" in 3.6.2 does not work anymore, needs
to be updated.

There is a stray dot at the start of the line "In older revisions..."
in 3.6.2.

3.6.2 talks about the need to set different environment variables, depending
on the OpenBoot version. Probably worth to mention the 'show .version'
command to display this version. Also, I believe that neither of machines
we support is still using OpenBoot 1.x, so we can just remove instructions
for these versions. It also mentions 'eeprom' command on Solaris, this
command is available in Debian too, as a part of sparc-utils package.

Not sure what to do with section 3.6.3, pretty confident that this
information is irrelevant for sparc.

4.4.1: check that .enet-addr command really returns the MAC address of
the network card. Also it should be verified somehow that *all* commands
still work on newer Solaris versions (anybody with a working Solaris system?)

4.4.4/4.4.5: default package providing tftp server is tftpd. Default directory
from which the images are served is /srv/tftp, needs to be updated.

4.4.5.1: A bit more explanation about how image names are constructed?
On my system the requested file name is logged in /var/log/daemon.log,
for example:

Sep 28 19:16:25 debian tftpd[3620]: tftpd: trying to get file: C0A8016E.SUN4M
Sep 28 19:16:25 debian tftpd[3620]: tftpd: serving file from /srv/tftp 

Also, 'boot net' or 'boot net-tpe' has always worked for me, is mentioned
syntax 'boot net my-sparc.image' is still used?

5.1.1: Drop information relevant for older OpenBoot revisions.

5.1.2: Ditto. Also, in my experience booting from CD-ROM on sun4m simply does
not work (it would boot, but when it comes to mounting the CD-ROM, any attempt
to read the CD aborts with an error). Hendrik originally reported it in
382990.

5.1.3: Drop sun4c information.

5.1.3: Note about broken firmware for Ultra 10 - is it relevant a

Problems after dist-upgrade with kernel 2.6.17 in Sun blade 1k

2006-10-02 Thread Luis Martinez
Upgrading to this kernel leaves the blade unbootable, since ql2xxx
module is used instead of qlogicfc to manage the FCAL disks.
The module ql2xxx still does not work for the q logic controller on the
Sun Blade 1000.

Regards,

Luis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



New to Sparc Debian

2006-10-02 Thread Simon Tyler








Hi all,  

 

I will be brand new to Debian (been a suse man of
late).
However, I have aquired an ultra 60 and wondered what anyone thought of
Debian running on this machine and if you have any advise before I
trash it.

Thanks in advance
Si

 

 

Regards

Simon Tyler

Lead Design Engineer

 

Centurion Electronics PLC

Satellite House

Welwyn
 Garden
City

Herts  AL7 1LY

 

Tel: 01707 330550

Fax 01707 330866

Ext. 187

Email: [EMAIL PROTECTED]

 








Re: [D-I] mass kernel udeb update and preparations for RC1

2006-10-02 Thread Frans Pop
On Sunday 17 September 2006 14:28, Frans Pop wrote:
> There are some issues that need attention:
> * type of initrd used
>   Some arches have already switched to using initramfs for d-i initrds,
>   other arches are still using cramfs or ext2. Please check if a change
>   could/should be made for your architecture.

Sparc and HPPA have now been switched to use initramfs initrds in Debian 
Installer images.

For Sparc I have tested the installer still boots (CD and netboot) on my 
Ultra 10 and Jurij Smakov has tested it for sparc32. For HPPA I have 
tested this on my J5600.

If others have problems booting a daily image of the installer, but an 
Etch Beta 3 image does boot correctly, please let us know.

Cheers,
FJP


pgpBdluK6N60c.pgp
Description: PGP signature