RE: Graphics mode on my C3000 - still no joy - more info
Here is the output of dmesg and the XFree86.0.log ... sorry for the Windows cr's ... but then you probably figured out that I am a Linux newbie a long time ago ... trying hard to make the switch :-). Also Joel, I got hopeful when I saw your "is your screen is well connected to your eg/pci card?" comment because I had the eg/pci connected to the screen through a kvm. I connected the screen directly to the eg/pci through the evc to vga adapter, but unfortunately nothing changed. I did CS11:~# ls -la /dev/fb0 and got crw-rw1 root video 29, 0 Jun 26 20:47 /dev/fb0 Thanks again for all of your help!! I hope one of you can see something obvious in dmesg or XFree86.0.log. -Original Message- From: Joel Soete [mailto:[EMAIL PROTECTED] Sent: Sunday, June 27, 2004 3:18 PM To: Harry Cochran Subject: Re: Graphics mode on my C3000 - still no joy - more info Harry Cochran wrote: >I was wrong about the message "Process set to nice value 0 instead of -10 as >requested" after the "I cannot start the X server" window ... it's gone. The >next window starts out "This is apre-release of XFree86 and is not supported >in any way". > >Also, after you see this window, you get a chance to retry to start X. You >put in the root password and it goes through the process pretty quickly. By >watching it several times I was able to see two things: > >1. "Unable to open/locate file //XF86Config.new > error from xf86HandleConfigFile() > >2. Fatal Screen Error: > No Screens Found > > You would certainly find more in your /var/log/XFree86.0.log >By the way, I also tried changing the monitor to type 5 (1024x768) and >changing the mode to 1024x768 in the Display SubSection. This made no >difference. > > Stupid question (i know but that's something like this we miss :) ): is your screen is well connected to your eg/pci card? Again, please help us to help you more accurately (your dmesg and XFree86.0.log would be helpfull) Joel > Or, Helge, is that better to use another fb (eg fb1) ? No, you should cat /proc/fb which should give you "0 stifb". So, /dev/fb0 is your device. And, /dev/fb0 should look like: pa64:~# ls -la /dev/fb0 crw-rw1 root video 29, 0 Jun 27 22:02 /dev/fb0 > Please send us your dmesg and /var/log/XFree86.0.log Yes, please. Helge dCS11:/# dmesg Linux version 2.4.26-32 ([EMAIL PROTECTED]) (gcc version 3.3.4 (Debian)) #1 Sun Jun 20 19:47:18 CEST 2004 FP[0] enabled: Rev 1 Model 16 The 32-bit Kernel has started... Determining PDC firmware type: System Map. model 5bb0 0481 0002 77b36953 10f0 0008 00b2 00 b2 vers 0200 CPUID vers 17 rev 4 (0x0224) capabilities 0x3 model 9000/785/C3000 Total Memory: 512 Mb pagetable_init On node 0 totalpages: 131072 zone(0): 131072 pages. zone(1): 0 pages. zone(2): 0 pages. LCD display at f05d0008,f05d registered Kernel command line: root=/dev/sda3 HOME=/ console=tty0 sti=10/4/3/0 sti_font=VG A8x16 TERM=linux palo_kernel=1/boot/vmlinux Console: colour dummy device 160x64 Calibrating delay loop... 799.53 BogoMIPS Memory: 514516k available Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode cache hash table entries: 32768 (order: 6, 262144 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Searching for devices... Found devices: 1. Astro BC Runway Port (12) at 0xfed0 [10], versions 0x582, 0x0, 0xb 2. Elroy PCI Bridge (13) at 0xfed3 [10/0], versions 0x782, 0x0, 0xa 3. Elroy PCI Bridge (13) at 0xfed32000 [10/1], versions 0x782, 0x0, 0xa 4. Elroy PCI Bridge (13) at 0xfed38000 [10/4], versions 0x782, 0x0, 0xa 5. Elroy PCI Bridge (13) at 0xfed3c000 [10/6], versions 0x782, 0x0, 0xa 6. AllegroHigh W (0) at 0xfffa [32], versions 0x5bb, 0x0, 0x4 7. Memory (1) at 0xfed10200 [49], versions 0x86, 0x0, 0x9 CPU(s): 1 x PA8500 (PCX-W) at 400.00 MHz SBA found Astro 2.1 at 0xfed0 lba version TR2.1 (0x2) found at 0xfed3 WARNING: Ignoring enabled ELMMIO BASE 0xf800 SIZE 0xfc00 PCI: Ignoring BAR0-3 of IDE controller 00:0e.0 lba version TR2.1 (0x2) found at 0xfed32000 WARNING: Ignoring enabled ELMMIO BASE 0xf800 SIZE 0xfc00 lba version TR2.1 (0x2) found at 0xfed38000 WARNING: Ignoring enabled ELMMIO BASE 0xf800 SIZE 0xfc00 iosapic: hpa not registered for Hewlett-Packard Company A4977A Visualize EG lba version TR2.1 (0x2) found at 0xfed3c000 WARNING: Ignoring enabled ELMMIO BASE 0xf800 SIZE 0xfc00 POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Soft power switch enabled, polling @ 0xf0400804. SuperIO: Found NS87560 Legacy I/O device at 00:0e.1 (IRQ 64)
Graphics console working on my C3000!
Hi, Thanks Grant Grundler, Joel Soete and especially Helge Deller! My C3000 is now running in graphics mode. By the way, it works just fine through a Belkin OmniView kvm. One more interesting thing I learned. If you have a terminal emulation window open on another machine, Debian puts up a login prompt in serial mode even when your graphics mode login works. Cheers, Harry
RE: Problem with SCSI on HP 712/60
Hi, Sorry, I have no advice, but I want to add that if for some reason I have an abnormal shutdown on my A180 and there is a forced disk check I also get the "tag starvation" message. I did find this message chain: On Thu, Jan 24, 2002 at 11:55:01PM -0700, Grant Grundler wrote: > > Follow up to [EMAIL PROTECTED] only please. > (ie this isn't a debian linux issue) > > Vlad Markov wrote: > > I get the following message when I boot up on a 735/99: > > Jan 22 19:12:41 grumpy kernel: scsi0 (1:0) Target is suffering from tag > > starvation. > > Seems only 53c700.c prints this msg. Is this the right driver? Should be; 735 has unsupported 53c720 FWD, and 53c700 or 710 driven by 53c700.c. I assume Vlad has external narrow SE disks attached. > Normally you shouldn't see this *if* the device supports tagged commands. I used to get this a lot, until James changed the driver to only report the first occurance of it. Don't remember the exact details, but iirc it is for info only, and non-fatal. From the code it looks like it means some cmnd has been sitting in the drive unprocessed for too long, and the code rejects new cmds until those older ones have been processed or timed out. > I can never remember the SCSI driver options (the parisc-linux FAQ has > the URL to them) but one of them will either disable or limit > "queue depth" for Queue Tags and that should take care of it. Hmm, I thought that would be a feature of a specific driver, not the upper layers. 53c700.c doesn't (yet) have any boot options to disable tags. Richard <[EMAIL PROTECTED]> If anyone has more information on what tage starvation is and the consequences of this message, I would appreciate it too. Cheers, Harry Cochran -Original Message- From: W. Borgert [mailto:[EMAIL PROTECTED] Sent: Thursday, September 16, 2004 6:32 AM To: debian-hppa@lists.debian.org; debian-boot@lists.debian.org Subject: Problem with SCSI on HP 712/60 Hi, 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? Many thanks in advance! Cheers, WB Note: I can do further tests, but probably not before mid-October. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Stuck on bad change to etc/network/interfaces
Hi, I made a change to the interfaces file that is causing my A class 9000 running a 2.4.26 Debian kernel not to boot (kernel panic when bringing up the interfaces). I know there is a way to get into a limited command set and edit the interfaces file, but my brain is dead for some reason right now and I can neither remember how to do it nor can I find the answer on the Web. Could someone please remind me how to do this? Thanks, Harry
RE: Stuck on bad change to etc/network/interfaces
Thanks, I have attached the last lines from the boot crash with Kernel Panic for your information. As to why something as simple as this interfaces file: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) auto eth0 iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 # auto eth1 iface eth1 inet static address 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 #gateway 192.168.1.1 should cause a kernel panic is beyond me. Obviously, I'm trying to set the A180 up as a proxy server. The router is 192.168.0.1 and the primary switch for the LAN is 192.168.1.5. Any ideas would be appreciated. Thanks again, Harry -Original Message- From: Kyle McMartin [mailto:[EMAIL PROTECTED] Behalf Of Kyle McMartin Sent: Sunday, December 19, 2004 5:57 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: Stuck on bad change to etc/network/interfaces On Sun, Dec 19, 2004 at 05:31:52PM -0500, Harry Cochran wrote: > I made a change to the interfaces file that is causing my A class 9000 > running a 2.4.26 Debian kernel not to boot (kernel panic when bringing up > the interfaces). I know there is a way to get into a limited command set and > edit the interfaces file, but my brain is dead for some reason right now and > I can neither remember how to do it nor can I find the answer on the Web. > Could someone please remind me how to do this? If you append 'init=/bin/sh' to your PALO command line, you will get dropped at a command prompt just after the root file system is mounted. Run mount -o remount,rw / to get a read-write '/', and then you can edit /etc/network/interfaces to fix your bug. I'd be interested in seeing the kernel panic you're getting though, I can't conceive of how something in there could be causing a panic. Thanks, Kyle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] Mounting local filesystems... /dev/sdb1 on /home type ext2 (rw) /dev/sdb2 on /var type ext2 (rw) Initializing: /etc/network/ifstate. Setting up IP spoofing protection: rp_filter. Enabling packet forwarding...done. Configuring network interfaces... Stack Dump: 4f610e00: 10416810 10416b00 10416810 4f610df0: 10416810 4f610a00 00a1 000f 4f610de0: 40028030 4f610980 103ec320 4fe53960 4f610dd0: 786b 41e1 4fe53800 1037d810 4f610dc0: 4fe53960 cccd 4f610db0: 101f252c 10418010 000f Kernel addresses on the stack: [<101f252c>] [<101f14e4>] [<101058f8>] [<1013ae04>] [<10285d24>] [<101058f8>] [<103111e8>] [<10137c0c>] [<10105988>] [<103111e8>] [<10168e28>] [<101f0b40>] [<10109064>] [<1029a210>] [<10285c40>] [<10285c3c>] [<1014341c>] [<10141f50>] [<10152770>] [<101054a0>] [<101f0b40>] [<101054a0>] [<1012381c>] [<10103d7c>] [<101054a0>] [<10105d34>] [<10299f9c>] [<101f3a58>] [<1029f088>] [<101379f8>] [<102a079c>] [<102de758>] [<102a13dc>] [<1029701c>] [<10153498>] [<10109f98>] [<10109084>] [<10109d54>] [<1014341c>] [<10141f50>] [<10152770>] [<101217cc>] High Priority Machine Check (HPMC): Code=1 regs=1035d080 (Addr=) YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI PSW: 010011101110 Not tainted r00-03 1040f010 10110b8c r04-07 00010030 41e1 4fe53800 1037d810 r08-11 4fe53800 00010028 0001 0019 r12-15 faf00508 0002f5b4 r16-19 0002f158 0010 0300 r20-23 000e 10f97360 10285a3c 020e0200 r24-27 00010030 0030 10f97360 1035a010 r28-31 03e0 0384 4f610e00 10110b8c sr0-3 00a1 00a1 sr4-7 IASQ: IAOQ: 10285a68 10285a6c IIR: d27c0afcISR: 00a1 IOR: 10110b8c CPU:0 CR30: 4f61 CR31: 1040 ORIG_R28: Kernel panic: High Priority Machine Check (HPMC) In interrupt handler - not syncing
RE: Stuck on bad change to etc/network/interfaces
No dice. Both eth0 and eth1 work just fine when the router is set to 192.168.1.1 and they are give that as a gateway and addresses like 192.168.1.230 and 192.168.1.231 respectively. Thanks anyway, Harry -Original Message- From: Kyle McMartin [mailto:[EMAIL PROTECTED] Sent: Sunday, December 19, 2004 9:23 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: Stuck on bad change to etc/network/interfaces On Sun, Dec 19, 2004 at 09:15:15PM -0500, Harry Cochran wrote: > I have attached the last lines from the boot crash with Kernel Panic for > your information. As to why something as simple as this interfaces file: > > Kernel panic: High Priority Machine Check (HPMC) > In interrupt handler - not syncing OK. I guess this is a problem with whatever network card you've got in the PCI slot of your A180... What driver does the network card use? Cheers, Kyle
NIC & "searching for devices"
Hi, I have two problems I'm hoping to get help with: 1. I need to add a NIC to my C3600. I discovered that there is no driver for the 3COM 3C905C and I don't recognize the drivers that are there. Could someone please tell me if there is a driver I can download for the 3C905C (the 3COM site has a "Linux" driver, but it's only for x86 platforms), or alternatively, what's the best 10/100 NIC I can buy and put in for which there is a Debian hppa driver. 2. I upgraded my J6000 to 2.4.27 and added usb support. Now when I boot it gets to "Page-cache table entries ..." and then says "Searching for Devices" and says "Searching for Devices". This never times out ... it just sits there. I did get the machine to boot by adding an EG-PCI and a usb keyboard (it automatically went to pa con Graphics(3)), but the graphics are screwy (color dummy paints the right half of the screen with the boot lines and it dies somewhere along the way that isn't readable). I did get it to boot by brining it up in graphics mode, putting it into serial mode (pa con Serial_1) and then booting, but now when I boot again in serial mode with no keyboard and monitor attached, it says "Searching for Devices" again. I would like to get back to the point where it would just boot in serial console mode. Any help would be appreciated. Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: [parisc-linux] NIC & "searching for devices"
Hi, 2.4.27-32-smp hangs on boot on my J6000 in serial console mode with "Searching for devices" message. The only way I've found out of this is to install a vidoe card, connect to a monitor and install a usb keyboard, type in pa con SERIAL_1, complete the boot and then you are up in serial mode after the boot. Then you can symlink back to 2.4.26 and reboot in serial console mode. Regards, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 4:28 AM To: Max Grabert Cc: Harry Cochran; debian-hppa@lists.debian.org Subject: Re: [parisc-linux] NIC & "searching for devices" --- > You might want to switch to 2.6, since apparently most of the PA hackers > are no longer interested in 2.4 (the latest CVS version on cvs.p-l.org > is 2.4.27 which has known security vulnerabilities; CVS 2.4 hasn't > been touched for about half a year now. I don't know about the debian > kernels). I've updated last 2.4.27 release to be built against recent kernel-source (in 2.4.27-3), so I suppose it has less vulnerabilities than previous versions. Still, 2.4 is definitely a dead end. HTH Thibaut VARENE PA/Linux ESIEE Team http://www.pateam.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: [parisc-linux] NIC & "searching for devices"
Ag. I've been trying to find instructions on "configuring your boot loader" for an initrd kernel with the hppa version of Debian. When you load an Intel kernel that needs initrd it tells you very nicely to edit lilo.conf, what line to insert, etc. Hppa just says "read your bootloader documentation." I assume I only need to insert --initrd=/initrd.img in palo.conf since the install of 2.6.8-2-smp automatically created an initrd.img symlink in /boot for me. Could someone please confirm this for a dumb newbie. Even better would be a palo.conf for a 2.6 kernel that I could use as an example. Thanks. -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 3:06 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: [parisc-linux] NIC & "searching for devices" On Tue, 22 Feb 2005 12:59:15 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Hi, > > 2.4.27-32-smp hangs on boot on my J6000 in serial console mode > with > "Searching for devices" message. The only way I've found out of this is > to install a vidoe card, connect to a monitor and install a usb > keyboard, type in pa con SERIAL_1, complete the boot and then you are up > in serial mode after the boot. Then you can symlink back to 2.4.26 and > reboot in serial console mode. > Already reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269037 The correct answer is "use 2.6". Recent parisc workstations aren't supported in 2.4 HTH Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ -- 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: [parisc-linux] Booting 2.6
Thanks Grant,
I made it 1/boot/initrd.img and I deleted the initrd=/boot/initrd.img
line.
Same result.
My root is still sda3, but it looks to me like it's not mounted when 2.6
gets to the kernel panic. That's why I think I need a ramdisk to get the
standard 2.6 kernel booted. All I have to work with is ash, and I can't see
my /boot (sda1) when I boot off of the cd. Is there any work around you can
think of?
Thanks again,
Harry
Best regards,
Harry
-Original Message-
From: Grant Grundler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 4:41 PM
To: Harry Cochran
Cc: [EMAIL PROTECTED]
Subject: Re: [parisc-linux] Booting 2.6
On Wed, Feb 23, 2005 at 10:56:34AM -0500, Harry Cochran wrote:
> Hi,
>
> Sorry for the newbie question, but I'm trying to boot 2.6 and I don't
quite
> understand how to set up the "root=" for it.
The name of the root disk might have changed IFF you have more
than one disk installed/connected to the system.
Look through console output
>
> My palo.conf says:
> --command line=1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=/initrd.img
I expect this needs to say:
initrd=1/boot/initrd.img
I personally like to point palo/elilo/lilo directly
at the file to load by default (and not a symlink).
> console=tys0 TERM=vt102
> --recoverykernel=/boot/vmlinux
> --init-partitioned=/dev/sda
>
> Here's what my palo.conf generates on boot right now:
>
> 0 1/boot/vmlinux
> 1 root=/dev/sda3
> 2 HOME=/
> 3 initrd=/initrd.img
> 4 console=ttys0
> 5 TERM=vt102
>
> On boot I get:
>
> cannot open root device "sda3" or unknownblock(2.0)
Well, if the kernel expects devfs mounted or something else,
then you have to sort out which /dev files are needed.
I suspect more likely either the sym53c8xx driver didn't get
loaded (no initrd found possibly) or more than one disk
is installed and the device name changed.
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs or unknown-block(2.0)
>
> I have seen one document which says I have to build a ramdisk, but it
> doesn't tell me how.
mkinitrd is the command you are looking for. But I don't use an
initrd on my boxes since I'm building my own kernels. The initrd
is most useful for generic kernel builds where one wants every
possible driver available as a potential root device. Since I
build my own kernels and know which drivers are needed for root,
I don't really need an initrd.
? What's worse is that I can't get 2.4.26 to boot again
> even though I have a symlink (vmlinux.old) to it. I tried changing line 0
to
> 1/boot/vmlinux.old, but it still boots 2.6.8. I even tried inserting a
line
> saying recoverykernel=/boot/vmlinux.old but that didn't help.
>
> Sounds easy ... just go to 2.6 (the solution to a problem I'm trying to
> implement), but for this newbie, it's anything but.
*nod*
Here's my palo.conf:
ioz:~# cat /etc/palo.conf
--commandline=0/vmlinux-2.6.11-rc2-pa3-UP root=/dev/sda3 panic=5
console=ttyS1
--format-as=2
--update-partitioned=/dev/sda
[ I've also added "noudev" to the commandline on some of the machines. ]
ioz:~# fdisk -l /dev/sda
ioctl32(fdisk:4277): Unknown cmd fd(4) cmd(40081272){00} arg(faf005f0) on
/dev/sda
Disk /dev/sda: 73.4 GB, 73407865856 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 24 192748+ f0 Linux/PA-RISC boot
/dev/sda2 25 148 996030 82 Linux swap
/dev/sda3 149214016000740 83 Linux
/dev/sda42141892454492480 83 Linux
ioz:~# mount
/dev/sda3 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext3 (rw)
I hope the above should get you on the right track.
>
> Please help.
>
> Thanks,
>
> Harry
>
>
> ___
> parisc-linux mailing list
> [EMAIL PROTECTED]
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: [parisc-linux] Booting 2.6
Hi, Boy, you have a long memory ... back to a year ago when I responded without copying parisc-linux. No need to worry, I learned that lesson :-). I'm also copying debian-hppa, which I hope is a good thing (but I'm open to correction if not). Yes, I tried initrd=1/boot/initrd.img with everything else the same. I have attached the console output. On my first SCSI drive, there is a 70MB partition that gets mounted as /BOOT where all of the images are, then there is a swap partition and then / starts. Thanks again for your help. Best regards, Harry -Original Message- From: Grant Grundler [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 6:11 PM To: Harry Cochran Cc: [EMAIL PROTECTED] Subject: Re: [parisc-linux] Booting 2.6 Harry, please keep the parisc-linux cc'd. Others may be able to further help you. On Wed, Feb 23, 2005 at 05:12:48PM -0500, Harry Cochran wrote: > Thanks Grant, > > I made it 1/boot/initrd.img and I deleted the > initrd=/boot/initrd.img line. I'm hoping you mean: initrd=1/boot/initrd.img > Same result. Erm, can you capture and post the console output? (ALL of it) I'm assuming you have a serial console. Starting from firmware (BCH) prompt. > My root is still sda3, "sda" is a dynamic name that gets assigned on every boot. Change the kernel or the disk configuration and things will get scrambled if one is not really, really, really careful. > but it looks to me like it's not mounted when 2.6 > gets to the kernel panic. That's why I think I need a ramdisk to get the > standard 2.6 kernel booted. All I have to work with is ash, and I can't see > my /boot (sda1) when I boot off of the cd. Is there any work around you can > think of? the CD will not auto-mount /boot or /. And it is likely your disk has /boot as part of /. This is OK as long as the root disk does NOT cross of the 2GB boundary from the start of the disk. See palo help file for more details. grant Main Menu: Enter command > bo pri Interact with IPL (Y, N, Q)?> y Booting... Boot IO Dependent Code (IODC) revision 0 HARD Booted. palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 Partition Start(MB) End(MB) Id Type 1 1 31 f0 Palo 2 321008 82 swap 31009 17366 83 ext2 PALO(F0) partition contains: 0/vmlinux32 4968722 bytes @ 0x44000 Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial).Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=/initrd.img console=ttyS0 TERM=vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? 03 initrd=1/boot/initrd.img Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=1/boot/initrd.img console=ttyS0 TERM =vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=1/boot/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? b Command line for kernel: 'root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_ke rnel=1/boot/vmlinux' Selected kernel: /boot/vmlinux from partition 1 Selected ramdisk: /boot/initrd.img from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable Entry 0010 first 0010 n 3 Segment 0 load 0010 size 2832408 mediaptr 0x1000 Segment 1 load 003b4000 size 705472 mediaptr 0x2b5000 Segment 2 load 00464000 size 397328 mediaptr 0x362000 ERROR: failed to load ramdisk - proceeding anywayBranching 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.6.8-2-32-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5 -7)) #1 SMP Mon Feb 7 22:19:10 EST 2005 FP[0] enabled: Rev 1 Model 16 The 32-bit Kernel has started... Determining PDC firmware type: System Map. model 5d40 0491 0002 782e91ff 10f0 0008 00b2 00 b2 vers 0301 CPUID vers 17 rev 11 (0x022b) capabilities 0x3 model 9000/785/J6000 Total Memory: 2048 Mb LCD display at f05d0008,f05d registered SMP: bootstrap CPU ID is 0 Built 1 zonelists Kernel command line: root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_kernel= 1/boot/vmlinux PID hash table entries: 16 (order 4: 128 bytes) Console: colour dummy device 160x64 Dentry cache hash table entries: 524288 (order: 9, 2097152 bytes) Inode-cache hash table entri
RE: [parisc-linux] Upgrading from 2.4 to 2.6
Thanks for your input. Could it really be true that the "stable" version of 2.6 (2.6.8-2-32-smp) can't recognize an ext3 root partition? The only way I know to "load a new kernel" since I can only boot fromt he install cd is to blow away what I have spent a lot of time building. Seems like I'm missing something. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 4:46 AM To: Harry Cochran Subject: Re: [parisc-linux] Upgrading from 2.4 to 2.6 Harry Cochran wrote: > Hi, > > Could someone please help me recover from a failed attempt to upgrade my > J6000 to 2.6? > > Looks like I can't boot the 2.4 kernel I have on the system because it's > name doesn't end in 32 or 64 (it ends in smp) -><-. > > My J6000 has a cd-rom, so I thought maybe I could boot from that, but > sea > ipl doesn't find it. > > Here's my original question: > > * > > Sorry for the newbie question, but I'm trying to boot 2.6 and I don't quite > understand how to set up the "root=" for it. With palo, the partition/mount info is also important: some directories are relative to the boot-partition, others are relative to the root partition. > > My palo.conf says: > --command line=1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=/initrd.img > console=ttyS0 TERM=vt102 > --recoverykernel=/boot/vmlinux This recovery-kernel is relative to the run-time root. Be noted, this kernel is moved to the palo-partition (/dev/sda0) when running `palo`. Best to use the distro's kernel for this, alternative, a kernel that sure works for recovery purposes. Most systems have /boot/vmlinux a softlink to the prefered kernel, which most times is not the recovery kernel... > --init-partitioned=/dev/sda > > Here's what my palo.conf generates on boot right now: > > 0 1/boot/vmlinux The 1 indicates partition 1 is the boot-partition, the /boot/vmlunix is a relative path on that partition. Hence, If /dev/sda1 is your /boot partition, te line should be: "1/vmlinux". Then, the filesystem of /boot is best `ext2` since that is supported by most, if not all tools. Other filesystems might not be supported. > 1 root=/dev/sda3 The root filesystem > 2 HOME=/ > 3 initrd=/initrd.img Carefully check if the initrd parameter is relative to the root or to the boot filesystem. > 4 console=ttys0 > 5 TERM=vt102 > > On boot I get: > > cannot open root device "sda3" or unknownblock(2.0) What is the filesystem on /dev/sda3? It better be ext2 since that is understood by most systems. ext3 is possible, I would not use others. > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs or unknown-block(2.0) I think your kernel only allows ext2 and finds something else. > > I have seen one document which says I have to build a ramdisk, but it > doesn't tell me how. What's worse is that I can't get 2.4.26 to boot again > even though I have a symlink (vmlinux.old) to it. I tried changing line 0 to > 1/boot/vmlinux.old (and deleting the "initrd=/initrd.img" line, but it still > boots 2.6.8. I even tried inserting a line saying > recoverykernel=/boot/vmlinux.old but that didn't help. I've seen teh palo that comes with gentoo has an option to list the directory of the boot-device, so you can check the kernel path. Keep in mind: palo must be able to read the boot device (/dev/sd1). Try ext2. The kernel must be able to read the root device without loading a module. Most kernels have ext2 build in. My idea: once you have a proper working kernel, build a new one without any modules (all stuff build in) and configure that as a recovery kernel in palo. > > * > > I'm sure there's an easy answer and maybe everyone is tired of answering > these kind of newbie questions, but I'm desperate, so I thought I'd try one > more time. > > Thanks, > > Harry > > > ___ > parisc-linux mailing list > [EMAIL PROTECTED] > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Using install cd to recover
Hi, In the process of trying to upgrade from 2.4.26-32-smp to 2.6.8-2-32-smp, I have managed to get my J6000 to a state where the only way to boot is with the install cd. This is despite the fact that I have the 2.4.26-32-smp image in /boot with a symlink (vmlinux.old) pointing to it. Is there a way to use the install cd to recover from this debacle? Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Can't mount F0 partition as /BOOT
Hi, I am rebuilding my J6000. I boot from the official Debian hppa install cd, partition the disks, making a nice 64MB F0 partition that I mark as bootable, a swap partition and several Linux partitions, initialize the swap, and then... I hit the button to initialze a disk and low and behold the boot partition I set up is not among the partitions that pop up to be initialized. If I do "View Paritions", there is sda1 and it's marked --Not Available--. I'm sure it's something simple, but I can't see what I'm doing wrong. Your help will be appreciated. Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
FW: Can't mount F0 partition as /BOOT
Looks like things have changed since I first put Debian-hppa on my J6000. I finally got 2.4.17-32 loaded and running after realizing that someone changed things so that you no longer mount /boot at install, you just greate a bootable f0 partition and the rest happens by magic, except, of course, you have to change palo.conf to (in my case) point to 1/vmlinux instead of 1/boot/vmlinux. Next I made the mistake of loading 2.4.26-32-smp and, when I finally got that to load (you have to point the recoverykernel to the 2.4.26-32-smp image too or otherwise it just keeps loading 2.4.17-32), I got ... "Searching for devices" again. Enough for one day! -Original Message----- From: Harry Cochran [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 5:36 PM To: [EMAIL PROTECTED]; debian-hppa@lists.debian.org Subject: Can't mount F0 partition as /BOOT Hi, I am rebuilding my J6000. I boot from the official Debian hppa install cd, partition the disks, making a nice 64MB F0 partition that I mark as bootable, a swap partition and several Linux partitions, initialize the swap, and then... I hit the button to initialze a disk and low and behold the boot partition I set up is not among the partitions that pop up to be initialized. If I do "View Paritions", there is sda1 and it's marked --Not Available--. I'm sure it's something simple, but I can't see what I'm doing wrong. Your help will be appreciated. Thanks, Harry -- 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: [parisc-linux] NIC & "searching for devices"
Thanks Thibaut, However, I have been unable to upgrade to 2.6. The image in unstable, 2.6.8-2-32-smp requires initrd. Fair enough, but nothing I have tried works. I get tripped up on the root= statement (I have sent mail on this). I've been searching for days now for a simple cookbook on upgrading from 2.4 to 2.6 and I can't find one. If you could please point me to a document that goes through the process of upgrading from 2.4 to 2.6, I would really appreciate it. Thanks, Harry Cochran -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 3:06 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: [parisc-linux] NIC & "searching for devices" On Tue, 22 Feb 2005 12:59:15 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Hi, > > 2.4.27-32-smp hangs on boot on my J6000 in serial console mode > with > "Searching for devices" message. The only way I've found out of this is > to install a vidoe card, connect to a monitor and install a usb > keyboard, type in pa con SERIAL_1, complete the boot and then you are up > in serial mode after the boot. Then you can symlink back to 2.4.26 and > reboot in serial console mode. > Already reported: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269037 The correct answer is "use 2.6". Recent parisc workstations aren't supported in 2.4 HTH Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ -- 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]
Anyone know where 2.4.26-pa5-32-smp is?
Hi, Before I began trying to upgrade kernel-image-2.4.26-pa5-32-smp, I had a nice running system for many months. Now I can't find this kernel again and kernel-image-2.4.26-32-smp on stable, unstable and testing dies during boot on my J6000 at "Searching for devices" (bug# 269037). Does anyone know where I can get kernel-image-2.4.26-pa5-32-smp? Of course, I'm ultimately hoping to upgrade to 2.6, but I just wasted 4 days trying and I have to ship the J6000 off soon. Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Anyone know where 2.4.26-pa5-32-smp is?
Dear HTH, Too bad, that release actually worked on my J6000 whereas 2.4.26-32-smp does not. If you decide to limit Debian hppa usage to "genius programmers" that will ultimately limit the usefulness of all your hard work! I was actually hoping you would answer my earlier email requesting a simple cookbook for the mediocre among us to help us upgrade from 2.4 to 2.6. Thanks, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 1:03 PM To: debian-hppa@lists.debian.org Subject: Re: Anyone know where 2.4.26-pa5-32-smp is? Removed from testing, per release manager and maintainer (me) request. Happened a few months ago already HTH -- Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ It is never wise to assume that genius programmers cannot do something because the incompetent or mediocre cannot. -- Eric Raymond -- 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]
2.4 -> 2.6
Thanks Thibaut, I double checked the kernel output from my last attempt (attached) and I don't see anywhere where it tells me that sda under 2.4 has become sdb under 2.6 except that it does tell me my root is not on sda, so that doesn't leave too many other choices. One final question. My palo.conf says --command-line=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --recoverykernel=1/vmlinux.old --init-partitioned=/dev/sda (vmlinux->vmlinux-2.6.8-2-32-smp and vmlinux.old->vmlinux-2.4.17-32) What I hear you saying is that I should reboot with this palo.conf and if I get the root problem again I should change root=/dev/sda3 to root/dev/sdb3 and reboot again. I note that after the first reboot it's too late to change init-partitioned=/dev/sda to /dev/sdb, but I guess that's okay (all I can find on init-partitioned is that it tells palo to initialize the palo boot parameters on the drive rather than preserving any existing parameters). Thanks again for your help. If I get through this I will commit to trying to write down the baby steps so that no one goes through what I went through no matter how uninitiated to Debian hppa Linux they are. Cheers, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 1:42 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: [parisc-linux] NIC & "searching for devices" On Fri, 25 Feb 2005 11:16:52 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Thanks Thibaut, > > However, I have been unable to upgrade to 2.6. The image in > unstable, > 2.6.8-2-32-smp requires initrd. Fair enough, but nothing I have tried > works. I get tripped up on the root= statement (I have sent mail on > this). I've been searching for days now for a simple cookbook on > upgrading from 2.4 to 2.6 and I can't find one. If you could please > point me to a document that goes through the process of upgrading from > 2.4 to 2.6, I would really appreciate it. I don't understand your problem. apt-get install kernel-image-2.6.8-2-32-smp should work out of the box. the root issue is just a matter of having your root device name that has changed. look in the kernel output while booting, you'll see where your HD lives. For instance, on a machine of mine, /dev/sda became /dev/sdb. HTH Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ Main Menu: Enter command > bo pri Interact with IPL (Y, N, Q)?> y Booting... Boot IO Dependent Code (IODC) revision 0 HARD Booted. palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 Partition Start(MB) End(MB) Id Type 1 1 31 f0 Palo 2 321008 82 swap 31009 17366 83 ext2 PALO(F0) partition contains: 0/vmlinux32 4968722 bytes @ 0x44000 Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial).Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=/initrd.img console=ttyS0 TERM=vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? 03 initrd=1/boot/initrd.img Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=1/boot/initrd.img console=ttyS0 TERM =vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=1/boot/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? b Command line for kernel: 'root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_ke rnel=1/boot/vmlinux' Selected kernel: /boot/vmlinux from partition 1 Selected ramdisk: /boot/initrd.img from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable Entry 0010 first 0010 n 3 Segment 0 load 0010 size 2832408 mediaptr 0x1000 Segment 1 load 003b4000 size 705472 mediaptr 0x2b5000 Segment 2 load 00464000 size 397328 mediaptr 0x362000 ERROR: failed to load ramdisk - proceeding anywayBranching 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.6.8-2-32-smp ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5 -7)) #1 SMP Mon Feb 7 22:19:10 EST 2005 FP[0] enabled: Rev 1 Model 16 The 32-bit Kernel has started... Determining PDC firmware type: System Map. model 5d40 0491 0002 782e91ff 10f0 0008 00b2 00 b2 vers 0301 CPUID vers 17 rev 11 (0x
RE: Anyone know where 2.4.26-pa5-32-smp is?
Thanks Matthew, I originally had the "Searching for devices" problem on 2.4.27-32-smp. However, like you, I loaded 2.4.27-32 on my C3000 with no problem. At this point, I'm moments away from getting to 2.6.8-2-32-smp I hope. I'm just waiting to hear back from Thibaut before I do something dumb again and waste another 2 hours. Thanks, Harry -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Matthew Wilcox Sent: Friday, February 25, 2005 3:53 PM To: Harry Cochran Cc: Thibaut VARENE; debian-hppa@lists.debian.org Subject: Re: Anyone know where 2.4.26-pa5-32-smp is? On Fri, Feb 25, 2005 at 01:39:15PM -0500, Harry Cochran wrote: > Dear HTH, > > Too bad, that release actually worked on my J6000 whereas 2.4.26-32-smp does > not. Try 2.4.27-32-smp; I just tested that on my C3600 and it works. I have been able to reproduce your problem on a 2.6 upgrade from that kernel, so hopefully I'll be able to diagnose a cure soon. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
2.4 -> 2.6
Hi Kyle, Here's what I hear you saying: 1. Copy the lines below into a file and put that on the J6000. I did this and it's in a file /tmp/mkinitrd.txt. 2. cd /usr/sbin (probably not necessary, but I don't know what a/mkinitrd and b/mkinitrd mean) 3. patch -p1 mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 5:16 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: Anyone know where 2.4.26-pa5-32-smp is? On Fri, Feb 25, 2005 at 04:06:45PM -0500, Harry Cochran wrote: > I originally had the "Searching for devices" problem on 2.4.27-32-smp. > However, like you, I loaded 2.4.27-32 on my C3000 with no problem. At this > point, I'm moments away from getting to 2.6.8-2-32-smp I hope. I'm just > waiting to hear back from Thibaut before I do something dumb again and waste > another 2 hours. > Hi, Could you please apply the following patch to /usr/sbin/mkinitrd? You can copy it to your home directory, and apply it with something like # patch -p1 http://kyle.mcmartin.ca/patches/parisc-linux/mkinitrd.sym53c8xx.diff The root of the problem is that mkinitrd, which builds the initrd that loads all the drivers required to mount your root filesystem, finds modules by looking at the name the scsi driver places in /proc/scsi/. Since sym53cxx_2 was renamed to sym53cxx (and the original deleted), mkinitrd is unable to find module corresponding to the entry. This sets up a mapping from the old name (in 2.4) to the new module name (in 2.6). Hope this helps, Kyle M. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: 2.4 -> 2.6
Hi Kyle, As before, installing 2.4.27-32 after you patch ends in "Searching for devices" (see attahced). Thanks anyway, Harry -Original Message- From: Kyle McMartin [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 7:28 PM To: Harry Cochran Subject: Re: 2.4 -> 2.6 Sorry, I screwed up here. I doubt the patch will help (though it will solve a different problem). After applying the patch, install 2.4.27-32 (NOT -smp) and then boot that kernel and upgrade to 2.6.8-2-32-smp from there. Apologies for this oversight, Kyle Booting... Boot IO Dependent Code (IODC) revision 0 HARD Booted. palo ipl 1.0 [EMAIL PROTECTED] Mon Apr 1 10:02:53 MST 2002 Partition Start(MB) End(MB) Id Type 1 1 48 f0 Palo 2 492001 82 swap 32002 17366 83 ext2 PALO(F0) partition contains: 0/vmlinux32 4080672 bytes @ 0x44000 Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial).Current command line: 1/vmlinux root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 0: 1/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: console=ttyS0 4: TERM=vt102 Edit which field? (or 'b' to boot with this command line)? b Command line for kernel: 'root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_ke rnel=1/vmlinux' Selected kernel: /vmlinux from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable Entry 001000b8 first 0010 n 6 Segment 0 load 0010 size 2469456 mediaptr 0x1000 Segment 1 load 0035c000 size 398264 mediaptr 0x25c000 Segment 2 load 003c size 255804 mediaptr 0x2be000 Segment 3 load 0040 size 8192 mediaptr 0x2fd000 Segment 4 load 00408000 size 32768 mediaptr 0x2ff000 Segment 5 load 00450818 size 130080 mediaptr 0x307818 Branching to kernel entry point 0x001000b8. 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-32 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-6)) #1 Sun Jan 23 04:01:01 CET 2005 FP[0] enabled: Rev 1 Model 16 The 32-bit Kernel has started... Determining PDC firmware type: System Map. model 5d40 0491 0002 782e91ff 10f0 0008 00b2 00 b2 vers 0301 CPUID vers 17 rev 11 (0x022b) capabilities 0x3 model 9000/785/J6000 Total Memory: 2048 Mb pagetable_init On node 0 totalpages: 524288 zone(0): 524288 pages. zone(1): 0 pages. zone(2): 0 pages. LCD display at f05d0008,f05d registered Kernel command line: root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_kernel= 1/vmlinux Console: colour dummy device 160x64 Calibrating delay loop... 1101.00 BogoMIPS Memory: 2068860k available Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode cache hash table entries: 131072 (order: 8, 1048576 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 131072 (order: 7, 524288 bytes) Page-cache hash table entries: 524288 (order: 9, 2097152 bytes) Searching for devices...
FW: 2.4 -> 2.6
Well, I tried 2.6.8-2-32-smp "out of the box" and got nowhere again. When I booted with root=/dev/sda3 it didn't find it, so I changed to root=/dev/sdb3 and it still didn't find it. Could I please hear from someone who has upgraded from 2.4 to 2.6 to let me know what they did STEP BY STEP. Thanks -Original Message- From: Harry Cochran [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 2:28 PM To: Thibaut VARENE Cc: debian-hppa@lists.debian.org Subject: 2.4 -> 2.6 Thanks Thibaut, I double checked the kernel output from my last attempt (attached) and I don't see anywhere where it tells me that sda under 2.4 has become sdb under 2.6 except that it does tell me my root is not on sda, so that doesn't leave too many other choices. One final question. My palo.conf says --command-line=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --recoverykernel=1/vmlinux.old --init-partitioned=/dev/sda (vmlinux->vmlinux-2.6.8-2-32-smp and vmlinux.old->vmlinux-2.4.17-32) What I hear you saying is that I should reboot with this palo.conf and if I get the root problem again I should change root=/dev/sda3 to root/dev/sdb3 and reboot again. I note that after the first reboot it's too late to change init-partitioned=/dev/sda to /dev/sdb, but I guess that's okay (all I can find on init-partitioned is that it tells palo to initialize the palo boot parameters on the drive rather than preserving any existing parameters). Thanks again for your help. If I get through this I will commit to trying to write down the baby steps so that no one goes through what I went through no matter how uninitiated to Debian hppa Linux they are. Cheers, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 1:42 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: [parisc-linux] NIC & "searching for devices" On Fri, 25 Feb 2005 11:16:52 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Thanks Thibaut, > > However, I have been unable to upgrade to 2.6. The image in > unstable, > 2.6.8-2-32-smp requires initrd. Fair enough, but nothing I have tried > works. I get tripped up on the root= statement (I have sent mail on > this). I've been searching for days now for a simple cookbook on > upgrading from 2.4 to 2.6 and I can't find one. If you could please > point me to a document that goes through the process of upgrading from > 2.4 to 2.6, I would really appreciate it. I don't understand your problem. apt-get install kernel-image-2.6.8-2-32-smp should work out of the box. the root issue is just a matter of having your root device name that has changed. look in the kernel output while booting, you'll see where your HD lives. For instance, on a machine of mine, /dev/sda became /dev/sdb. HTH Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ Main Menu: Enter command > bo pri Interact with IPL (Y, N, Q)?> y Booting... Boot IO Dependent Code (IODC) revision 0 HARD Booted. palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 Partition Start(MB) End(MB) Id Type 1 1 31 f0 Palo 2 321008 82 swap 31009 17366 83 ext2 PALO(F0) partition contains: 0/vmlinux32 4968722 bytes @ 0x44000 Information: No console specified on kernel command line. This is normal. PALO will choose the console currently used by firmware (serial).Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=/initrd.img console=ttyS0 TERM=vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? 03 initrd=1/boot/initrd.img Current command line: 1/boot/vmlinux root=/dev/sda3 HOME=/ initrd=1/boot/initrd.img console=ttyS0 TERM =vt102 0: 1/boot/vmlinux 1: root=/dev/sda3 2: HOME=/ 3: initrd=1/boot/initrd.img 4: console=ttyS0 5: TERM=vt102 <#>edit the numbered field 'b'boot with this command line 'r'restore command line 'l'list dir ? b Command line for kernel: 'root=/dev/sda3 HOME=/ console=ttyS0 TERM=vt102 palo_ke rnel=1/boot/vmlinux' Selected kernel: /boot/vmlinux from partition 1 Selected ramdisk: /boot/initrd.img from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable Entry 0010 first 0010 n 3 Segment 0 load 0010 size 2832408 mediaptr 0x1000 Segment 1 load 003b4000 size 705472 mediaptr 0x2b5000 Segment 2 load 00464000 size 397328 mediaptr 0x362000 ERROR: failed to load ramdisk - proceeding anywayBranching to kernel entry point 0x0010. If this i
RE: FW: 2.4 -> 2.6
Dear Grant, Kyle and Thibaut: 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, modified /etc/mkinitrd/modules per Kyle and added Kyle's patch to mkinitrd just for luck, rebooted and everything just worked. sda did not become sdb. I will write this up to point out the pitfalls newbies like me can hit, but I'm afraid I'm out of time to figure out if, for instance, it works without Kyle's mods. It's great to be back among the living Debian hppa users! This J6000 is going into production in China to run Web and mail services for my company there. Cheers, Harry -Original Message- From: Grant Grundler [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 1:30 AM To: Harry Cochran Cc: Thibaut VARENE; debian-hppa@lists.debian.org Subject: Re: 2.4 -> 2.6 On Fri, Feb 25, 2005 at 02:27:52PM -0500, Harry Cochran wrote: > HARD Booted. > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 This is an invalid partition scheme. It's just luck that it worked with 2.4 kernel. I'm assuming partition 3 is the root partition. Re-read http://en.tldp.org/HOWTO/PA-RISC-Linux-Boot-HOWTO/index.html. In particular "4.3.3. Making a bootable partition". grant -Original Message- From: Kyle McMartin [mailto:[EMAIL PROTECTED] Sent: Friday, February 25, 2005 11:27 PM To: Harry Cochran Subject: Re: FW: 2.4 -> 2.6 On Fri, Feb 25, 2005 at 10:20:28PM -0500, Harry Cochran wrote: > Well, I tried 2.6.8-2-32-smp "out of the box" and got nowhere again. When I > booted with root=/dev/sda3 it didn't find it, so I changed to root=/dev/sdb3 > and it still didn't find it. Could I please hear from someone who has > upgraded from 2.4 to 2.6 to let me know what they did STEP BY STEP. > The problem is 2.4 sucks, and with 2.6 we moved to doing things exactly like the other architectures Debian supports. One last thing to try that I can think of, is to add "sym53c8xx" to /etc/mkinitrd/modules. This is how it looks on my C3000: % cat /etc/mkinitrd/modules # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 tulip sym53c8xx Hope this helps, Regards, Kyle M. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6
Hi, I don't know if this has any value or not, but I am happy to contribute it to PA-RISC/Linux Boot HOWTO with approval of those explicitly copied on this E-mail whose contributions I copied. Cheers, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 1:32 PM To: Harry Cochran Cc: Grant Grundler; Kyle McMartin; debian-hppa@lists.debian.org Subject: Re: 2.4 -> 2.6 On Sat, 26 Feb 2005 12:17:26 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Dear Grant, Kyle and Thibaut: > > 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, modified /etc/mkinitrd/modules per Kyle > and added Kyle's patch to mkinitrd just for luck, rebooted and > everything just worked. sda did not become sdb. I will write this up to > point out the pitfalls newbies like me can hit, but I'm afraid I'm out > of time to figure out if, for instance, it works without Kyle's mods. If you wanna send patch for the PA-RISC/Linux Boot HOWTO, I'd certainly look at them :) Glad you got it to work Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] 8. Upgrading from a Debian hppa 2.4 Kernel to a 2.6 kernel 8.1 Check your 2.4 partition scheme 8.2 First Steps 8.3 Edit /etc/palo.conf 8.4 Before you reboot 8.5 Conclusion 8.1 Check your 2.4 partition scheme It may come as a surprise, but it is possible (I know, I did it) to have a partition scheme that by some fluke "works" under 2.4 but is invalid and will not work under 2.6. For example: > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 root The problem here is that the large swap partition pushes /boot under the root out past the 2GB limit for booting. There is no ready cure for this. You will have to save your data, re-partition your hard drive and then reload your applications and data. The example in 4.3: Disk /dev/sda: 133 heads, 62 sectors, 1017 cylinders Units = cylinders of 8246 * 512 bytes Device BootStart EndBlocks Id System /dev/sda1 * 1 4 16461 f0 Linux/PA-RISC boot /dev/sda2 534123690 82 Linux swap /dev/sda3 *35 277 1001889 83 Linux is fine, because the small swap partition doesn't push root out too far. It's a better idea, however, to put the swap partition at the end of the disk. By the way, don't forget to make both the f0 partition and the root partition bootable. 8.2 First steps 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. Even though the PA-Risc cpu's in my machine are 64 bit, hppa Debian can't take advantage of the 64 bit instruction length, so I just stick with the 32 bit versions. So, now it is to begin to install a 2.6 kernel. Step 1 For example, apt-get install kernel-image-2.6.7-2-32-smp. When you get near the end of the install, you will get messages telling you that this is an initrd kernel and asking you if you want to abort. At this point say, "Yes". Now it's time for: Step 2 you need to add "sym53c8xx" to /etc/mkinitrd/modules. "modules" is created from /etc/mkinitrd/modules-new? Help, I don't remember the name the aborted load leaves behind. This is how it looks after editing: % cat /etc/mkinitrd/modules-new?? # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 tulip sym53c8xx Okay. Now we are ready for: Step 3 apt-get install kernel-image-2.6.7-2-32-smp again, but this time when asked if you want to abort, say, "No". 8.3 Edit /etc/palo.conf Edit /etc/palo.conf and insert on the --commandline initrd=x/boot/initrd.img where x is the number of the disk partition where /boot lives. Here's an example of a palo.conf that works: --commandline=3/boot/vmlinux initrd=3/boot/initrd.img HOME=/ root=/dev/sda3 --recoverykernel=/boot/vmlinux.old --init-partitioned=/dev/sda Then run palo! 8.4 Before you reboot On some machines installing the 2.6 kernel fl
RE: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6
Thanks Grant, Looks like I'm going around one more time. I don't see how to get to the -e2 option in the standard installer. I guess you are suggesting I just drop into the ash shell and run fdisk. Of course, being a newbie, I would prefer to just create the f0 partition with -e2 in the standard install disk partitioner. Is there a way to do that? Best regards, Harry -Original Message- From: Grant Grundler [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 7:14 PM To: Harry Cochran Cc: Thibaut VARENE; debian-hppa@lists.debian.org Subject: Re: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6 On Sat, Feb 26, 2005 at 04:52:58PM -0500, Harry Cochran wrote: > Hi, > > I don't know if this has any value or not, but I am happy to > contribute it to PA-RISC/Linux Boot HOWTO with approval of those > explicitly copied on this E-mail whose contributions I copied. You have my permission to contribute everything you learned. :^) Though I don't see why you explicitly need my permission. I'm not the maintainer. Some comments below. ... > 8. Upgrading from a Debian hppa 2.4 Kernel to a 2.6 kernel > > 8.1 Check your 2.4 partition scheme > 8.2 First Steps > 8.3 Edit /etc/palo.conf > 8.4 Before you reboot > 8.5 Conclusion > > 8.1 Check your 2.4 partition scheme > > It may come as a surprise, but it is possible (I know, I did it) to have a partition scheme that by some fluke "works" under 2.4 but is invalid and will not work under 2.6. For example: > > > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > > > Partition Start(MB) End(MB) Id Type > > 1 1 31 f0 Palo > > 2 321008 82 swap > > 31009 17366 83 ext2 root > > The problem here is that the large swap partition pushes /boot under the root out past the 2GB limit for booting. There is no ready cure for this. You will have to save your data, re-partition your hard drive and then reload your applications and data. The example in 4.3: > > Disk /dev/sda: 133 heads, 62 sectors, 1017 cylinders > Units = cylinders of 8246 * 512 bytes > >Device BootStart EndBlocks Id System > /dev/sda1 * 1 4 16461 f0 Linux/PA-RISC boot This should be bigger: 100-200MB about. With "-e2" option, palo can create an ext2 file system that can be mounted as /boot. i.e. files will be accessed with 1/vmlinux instead of 1/boot/vmlinux > /dev/sda2 534123690 82 Linux swap > /dev/sda3 *35 277 1001889 83 Linux > > is fine, because the small swap partition doesn't push root out too far. It's a better idea, however, to put the swap partition at the end of the disk. By the way, don't forget to make both the f0 partition and the root partition bootable. Swap, if needed, is best on the lowest numbered block possible since those typically have the highest bitrate. "bootable" flag doesn't mean anything to PA-RISC PDC. We use the DOS partition table format becuase it's trivial. > 8.2 First steps > > 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. Ok. > Even though the PA-Risc cpu's in my machine are 64 bit, hppa Debian can't take advantage of the 64 bit instruction length, so I just stick with the 32 bit versions. Drop this sentence (run-on sentence at that). It's not entirely correct in this context (user vs kernel space). > So, now it is to begin to install a 2.6 kernel. > > Step 1 For example, apt-get install kernel-image-2.6.7-2-32-smp. When you get near the end of the install, you will get messages telling you that this is an initrd kernel and asking you if you want to abort. At this point say, "Yes". Now it's time for: Please wrap long lines to 72 or fewer characters per line. But it's up to thibaut (or whoever is maintaining) if they can add this as-is. > Step 2 you need to add "sym53c8xx" to /etc/mkinitrd/modules. "modules" is created from /etc/mkinitrd/modules-new? Help, I don't remember the name the aborted load leaves behind. > > This is how it looks after editing: > > % cat /etc/mkinitrd/modules-new?? > # /etc/mkinitrd/modules: Kernel modules to load for initrd. > # > # This file should contain the names of kernel modules and their arguments > # (if any) that are needed to mount the root file system, one per line. > # Comments begin with a `#', and everything on the line after them are ignored. > # > # You must run mkinitrd(8) to effect this change. > # > # Examples: > # > # ext2 >
RE: FW: 2.4 -> 2.6
Thanks Stuart, When I started this whole process, I had a nice f0 /boot partition of 100MB that occupied the beginning sectors of my disk. When I did the reinstall, I couldn't get the installer to let me mount the f0 partition as /boot. Grant just told me about -e2. Onwards and upwards. Cheers, Harry -Original Message- From: Stuart Brady [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 5:55 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6
-Original Message- From: Grant Grundler [mailto:[EMAIL PROTECTED] Sent: Saturday, February 26, 2005 8:37 PM To: Harry Cochran Cc: debian-hppa@lists.debian.org Subject: Re: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6 On Sat, Feb 26, 2005 at 08:05:23PM -0500, Harry Cochran wrote: > The real question is "with the -e2 option" on what? Guess I'm tired because > I know ask doesn't have fdisk. Yes, you must be tired because you are "top posting". :^) -e2 is either a palo parameter (when invoked from user shell) or --format-as=2 to /etc/palo.conf file. See "palo -?" output. grant Okay. Now I learned something else about parisc-linuxers ... add comments at the bottom. Who knew? So, here's question 1: Why did you say: > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 "This is an invalid partition scheme." Is it just that the f0 partition is too small? Can one not have a swap partition this big? and here's question number 2: Why do none of the examples I've seen show --format-as=2 being used in palo.conf and can you please show me a complete example (recommended partition layout for an 18GB hard drive on a machine with 2GB of memory and a palo.conf that goes along with it)? I can't look at palo -? right now because I just blew my partitions away so I can re-partition and try it all one more time. Sorry. Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
/boot
Hi, Is an easier way to do this just to have a 50MB f0 partition and then a 50-200MB e2 partition that you mount as /boot? Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6
On Sat, Feb 26, 2005 at 09:15PM -0500, Grant Grundler wrote: >The ext2 partition must be /. >And it is 17GB. >ie. /boot and /boot contents are not guaranteed to be within >the first 2GB of disk blocks. >I suggest at least 4-6GB for / If / is 6GB how can /boot be graranteed to be within the first 2GB of disk blocks? >then /var or /home for the rest depending on the use of the machine. I have a 2nd 18BG drive for /var >Key thing is part1 (type f0) is /boot I feel like I'm going around in circles. Seems like you are saying /boot is in "part3 is /" in your example and it's also part1. Does --format-as=2 make part1 /boot? If so, why does it matter if / is 6GB or 17GB? Finally, in your example, why do you use --update-partitioned=/dev/sda instead of --init-partitioned=/dev/sda? Thanks for your patience with newbie's. I think you can sense how hard I'm trying to understand. Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: /boot
>On Sat, Feb 26, 2005 at 09:05:34PM -0500, Harry Cochran wrote: >> Hi, >> >> Is an easier way to do this just to have a 50MB f0 partition and then a >> 50-200MB e2 partition that you mount as /boot? On Sat, Feb 26, 2005 at 09:16:34PM -0500, Grant Grundler wrote: >no. >grant Okay. Trying it your way one more time. However ... first palo.conf SinoHub5:/etc# cat palo.conf --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --format-as=2 --update-partition=/dev/sda --recoverykernel=/boot/vmlinux-2.4.17-32 SinoHub5:/etc# palo palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 ELF32 executable For ext2/3-formatted palo partitions, you cannot specify a kernel or a ramdisk. 2nd try to identify error: SinoHub5:/etc# cat palo.conf --commandline=0/vmlinux root=/dev/sda3 HOME=/ --format-as=2 --update-partition=/dev/sda --recoverykernel=/boot/vmlinux-2.4.17-32 SinoHub5:/etc# palo palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 ELF32 executable For ext2/3-formatted palo partitions, you cannot specify a kernel or a ramdisk. 3rd try to identify error: SinoHub5:/etc# cat palo.conf --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --format-as=2 --update-partition=/dev/sda SinoHub5:/etc# palo palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 OK we're doing a format as ext2 ipl: addr 16384 size 36864 entry 0x0 Warning! Boot loader header version is 3, I only know how to handle version 4. It MIGHT work anyway. ko 0x44000 ksz 3687647 k64o 0x0 k64sz 0 rdo 0 rdsz 0 <1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/> Fourth try to identify error: SinoHub5:/etc# cat palo.conf --commandline=0/vmlinux root=/dev/sda3 HOME=/ --format-as=2 --update-partition=/dev/sda SinoHub5:/etc# palo palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 OK we're doing a format as ext2 ipl: addr 16384 size 36864 entry 0x0 Warning! Boot loader header version is 3, I only know how to handle version 4. It MIGHT work anyway. ko 0x44000 ksz 3687647 k64o 0x0 k64sz 0 rdo 0 rdsz 0 <0/vmlinux root=/dev/sda3 HOME=/> This, plus 10 tries at booting, all tells me that: 1. You can't specify a recovery kernel with this method (not very comforting ... but palo "finds" 2.4.27-32 every time anyway). I was wondering why you didn't specify one in your example. Now I know. 2. initrd has nothing to do with the v3 vs. v4 problem 3. I can't find the magic in front of the symlinks vmlinux and initrd.img to get 2.6 to load. I get "failed to load ram disk" every time with 10 tries at initrd=x, where x is 0/initrd.img, 1/initrd.img, 1/boot/initrd.img, /boot.initrd.img, etc. Or maybe it's something else entirely. Having an f0 partition and an e2 /boot is looking pretty good right now! No joy tonight, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6
Thanks, I will send an update as for you to use as a starting point as soon as I get through the -e2 business. If I had the money I would buy the newest, sexiest hppa box possible and give it to Dave Sill, author of "Life with qmail". That's a guy who knows how to write documentation! Cheers, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Sunday, February 27, 2005 6:30 AM To: Harry Cochran Cc: Grant Grundler; Kyle McMartin; debian-hppa@lists.debian.org Subject: Re: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6 On Sat, 26 Feb 2005 16:52:58 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Hi, > > I don't know if this has any value or not, but I am happy to > contribute it > to PA-RISC/Linux Boot HOWTO with approval of those explicitly copied on > this E-mail whose contributions I copied. > > Cheers, This looks interesting, I'll wrap up something a bit shorter probably (some of what is said is already in my recent changes in other sections), with the comments of Grant and others and will post it here for review, then I'll merge it with my current set of changes to the HOWTO for later publishing on TLDP. Thanks Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: /boot
>On Sat, Feb 26, 2005 at 11:55:19PM -0500, Harry Cochran wrote: >> Fourth try to identify error: ... On Sat, Feb 26, 2005 at 1:12AM -0500, Grant Grundler wrote: >How about reading "palo --help"? I have it pasted on my wall :-). >> SinoHub5:/etc# cat palo.conf >> --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ >> --format-as=2 >> --update-partition=/dev/sda >> SinoHub5:/etc# palo >> palo version 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:17 MDT 2004 >> OK we're doing a format as ext2 >> ipl: addr 16384 size 36864 entry 0x0 >> Warning! >> Boot loader header version is 3, I only know how >> to handle version 4. It MIGHT work anyway. >Could you replace "--update-partition=" with "--init-partition="? Done. Now palo doesn't give an error. >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! >If that boots, then: >o unmount /boot No ... umount /boot or umount -f /boot comes back with: "device is busy" >o rm /boot/* >o mount /boot Is there a problem leaving the redundant /boot on sda3? >As you might guess, the order is important. :^) >> This, plus 10 tries at booting, all tells me that: >> >> 1. You can't specify a recovery kernel with this method (not very comforting >> ... but palo "finds" 2.4.27-32 every time anyway). I was wondering why you >> didn't specify one in your example. Now I know. >One isn't needed. palo can list the contents of an ext2 directory. >So any vmlinux/initrd can be used if palo can list it. >> 2. initrd has nothing to do with the v3 vs. v4 problem >right >> 3. I can't find the magic in front of the symlinks vmlinux and initrd.img to >> get 2.6 to load. I get "failed to load ram disk" every time with 10 tries at >> initrd=x, where x is 0/initrd.img, 1/initrd.img, 1/boot/initrd.img, >> /boot.initrd.img, etc. Or maybe it's something else entirely. >Can you dump the following info (cut/paste to a shell): >fdisk -l /dev/sda SinoHub5:/# fdisk -l /dev/sda Disk /dev/sda: 64 heads, 32 sectors, 17366 cylinders Units = cylinders of 2048 * 512 bytes Device BootStart EndBlocks Id System /dev/sda1 * 195 97264 f0 Linux/PA-RISC boot /dev/sda296 1072 1000448 82 Linux swap /dev/sda3 1073 17366 16685056 83 Linux >mount SinoHub5:/# mount /dev/sda3 on / type ext2 (rw,errors=remount-ro) proc on /proc type proc (rw) /dev/sda1 on /boot type ext2 (rw) /dev/sdb1 on /var type ext3 (rw) >cat /etc/palo.conf SinoHub5:/# cat /etc/palo.conf --commandline=1/vmlinux initrd=1/initrd.img root=/dev/sda3 HOME=/ --update-partition=/dev/sda >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? >> Having an f0 >> partition and an e2 /boot is looking pretty good right now! >/boot on f0 partition definitely works. >I'm certainly not the only one using it. >hth, >grant Thanks again Grant. This is very close now. I just need one more push to complete. I hope you have time to reply today. Best regards, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6
Hi Thibaut, Here is an update, but it's not final. Grant's step 8.3 i. doesn't work (device is busy). I'm waiting to hear back from him. Cheers, Harry -Original Message- From: Thibaut VARENE [mailto:[EMAIL PROTECTED] Sent: Sunday, February 27, 2005 6:30 AM To: Harry Cochran Cc: Grant Grundler; Kyle McMartin; debian-hppa@lists.debian.org Subject: Re: PA-RISC/Linux Boot HOWTO Section 8, Draft 1, 2.4 -> 2.6 On Sat, 26 Feb 2005 16:52:58 -0500 "Harry Cochran" <[EMAIL PROTECTED]> wrote: > Hi, > > I don't know if this has any value or not, but I am happy to > contribute it > to PA-RISC/Linux Boot HOWTO with approval of those explicitly copied on > this E-mail whose contributions I copied. > > Cheers, This looks interesting, I'll wrap up something a bit shorter probably (some of what is said is already in my recent changes in other sections), with the comments of Grant and others and will post it here for review, then I'll merge it with my current set of changes to the HOWTO for later publishing on TLDP. Thanks Thibaut VARENE The PA/Linux ESIEE Team http://www.pateam.org/ 8. Upgrading from a Debian hppa 2.4 Kernel to a 2.6 kernel 8.1 Check your 2.4 partition scheme 8.2 First Steps 8.3 Set up f0 as /boot if necessary 8.4 Edit /etc/palo.conf 8.5 Before you reboot 8.6 Conclusion 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: > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 root Don't despair. There is a way to tell palo to format your f0 partition, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot (See 8.3). Here's an example that works: Disk /dev/sda: 73.4 GB, 73407865856 bytes 255 heads, 63 sectors/track, 8924 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 *1 24 192748+ f0 Linux/PA-RISC boot /dev/sda2 25 148 996030 82 Linux swap /dev/sda3 149 214016000740 83 Linux /dev/sda4 2141 892454492480 83 Linux and here's the palo.conf that goes with it: --commandline=0/vmlinux-2.6.11-rc2-pa3-UP root=/dev/sda3 panic=5 console=ttyS1 --update-partitioned=/dev/sda 8.2 First steps 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. Step 1 For example, apt-get install kernel-image-2.6.7-2-32-smp. When you get near the end of the install, you will get messages telling you that this is an initrd kernel and asking you if you want to abort. At this point say, "Yes". Now it's time for: Step 2 you need to add "sym53c8xx" to /etc/mkinitrd/modules. "modules" is created from /etc/mkinitrd/modules.dpkg-new. This is how it looks after editing: % cat /etc/mkinitrd/modules.dpkg-new # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 tulip sym53c8xx Okay. Now we are ready for: Step 3 apt-get install kernel-image-2.6.8-2-32-smp again, but this time when asked if you want to abort, say, "No". Step 4 Run apt-get upgrade Step 5 Run palo -? and make sure your palo has -format-as=type 8.3 Set up f0 as /boot if necessary One of the weaknesses of the current hppa installer is that it won't let you mount the f0 partition as /boot. If you created a small (50MB-200MB) ext2 partition and mounted it as /boot during the install process, you can skip this section and go to 8.4. If not, and you have a / that goes out beyond 2GB from the beginning of your disk, here is your salvation. Of course, if you're starting from scratch, you can set up an f0 and an ext2 partition that you mount as /boot, but the preferred partitioning scheme is to just set up one f0 partition during installation (at least 50MB for a production system and say 200MB for a development system) and then use palo to format it, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot. Here's what to do: a. Edit /etc/palo.conf, on the --commandline change your pointer to vmlinux to 1/vmli
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? On Sun, Feb 27, 2005 at 11:46:41AM -0500, Stuart Brady wrote: >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... Am I right that with /dev/sda1 mounted as /boot, if I am at say /var a cd /boot should go to the /dev/sda1 partition? If so, that /boot is empty as shown above. Now for the bad news ... cd / and then cd boot which should bring me to the boot directory under the root is also empty. Arrrg. Will an apt-get install kernel-image-2.6.8-2-32-smp reload /dev/sda1 with the files I need to boot? >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. Assuming I can get a loadable kernel and initrd.img back on the /boot on /dev/sda1/, I guess I don't need --update-partitioned /dev/sda in palo.conf. Can you please confirm that? >You'll have to copy the files from /boot again (using /mnt for sda1, >making sure you've unmounted /boot first). >-- >Stuart Brady Also I did cd /var and then tried umount /boot and got "device is busy" still. What am I doing wrong? Thanks for your help Stuart! Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: /boot
>On Sun, Feb 27, 2005 at 12:00:25PM -0500, Harry Cochran wrote: >> Am I right that with /dev/sda1 mounted as /boot, if I am at say /var a >> cd /boot should go to the /dev/sda1 partition? If so, that /boot is empty as >> shown above. >> >> Now for the bad news ... cd / and then cd boot which should bring me to the >> boot directory under the root is also empty. 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? 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. >That's why we keep telling you to "mount /dev/sda1 /mnt" and then copy >the /boot contents to /mnt. >> Arrrg. Will an apt-get install >> kernel-image-2.6.8-2-32-smp reload /dev/sda1 with the files I need to boot? >Probably not. But "dpkg -i kernel-image-2.6.8-2-32-smp.deb" will. >(just get the name of the .deb file right) 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). >> Assuming I can get a loadable kernel and initrd.img back on the /boot on >> /dev/sda1/, I guess I don't need --update-partitioned /dev/sda in palo.conf. >> Can you please confirm that? >You do need --update-partitioned /dev/sda in palo.conf. Thanks ... glad I got at least one thing right :-). >> Also I did cd /var and then tried umount /boot and got "device is busy" >> still. What am I doing wrong? >It sounds like /boot is the original directory on /dev/sda3. >No one uses /boot for anything *except* palo to load vmlinux/initrd. Bottom line is I can't umount /boot or umount /dev/sda1 ... I always get "device is busy". I know I'm missing something here, but I don't know what it is. Thanks, Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: /boot
Harry Cochran wrote: >> >>Also I did cd /var and then tried umount /boot and got "device is busy" >>still. What am I doing wrong? >> Joel Soete wrote: >I encounter the same pb a time ago: if /boot is a fs mounted at boot >time iirc you would have to stop klog daemon >(iirc too "fuser -c /boot" would have to show you the process(es) using >your fs). That was it. Thanks so much Joel!! Harry -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: PA-RISC/Linux Boot HOWTO Section 8, Final Draft, 2.4 -> 2.6
Hi Thibaut, Okay. As far as I'm concerned, it's soup. I will be interested to see what you come up with out of this. Thanks to all for your help and patience! Cheers, Harry 8. Upgrading from a Debian hppa 2.4 Kernel to a 2.6 kernel 8.1 Check your 2.4 partition scheme 8.2 First Steps 8.3 Set up f0 as /boot if necessary 8.4 Edit /etc/palo.conf 8.5 Before you reboot 8.6 Conclusion 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: > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 root Don't despair. There is a way to tell palo to format your f0 partition, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot (See 8.3). Here's an example that works: Disk /dev/sda: 73.4 GB, 73407865856 bytes 255 heads, 63 sectors/track, 8924 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 *1 24 192748+ f0 Linux/PA-RISC boot /dev/sda2 25 148 996030 82 Linux swap /dev/sda3 149 214016000740 83 Linux /dev/sda4 2141 892454492480 83 Linux and here's the palo.conf that goes with it: --commandline=0/vmlinux-2.6.11-rc2-pa3-UP root=/dev/sda3 panic=5 console=ttyS1 --update-partitioned=/dev/sda 8.2 First steps 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. Step 1 For example, apt-get install kernel-image-2.6.7-2-32-smp. When you get near the end of the install, you will get messages telling you that this is an initrd kernel and asking you if you want to abort. At this point say, "Yes". Now it's time for: Step 2 you need to add "sym53c8xx" to /etc/mkinitrd/modules. "modules" is created from /etc/mkinitrd/modules.dpkg-new. This is how it looks after editing: % cat /etc/mkinitrd/modules.dpkg-new # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 tulip sym53c8xx Okay. Now we are ready for: Step 3 apt-get install kernel-image-2.6.8-2-32-smp again, but this time when asked if you want to abort, say, "No". Step 4 Run apt-get upgrade Step 5 Run palo -? and make sure your palo has -format-as=type 8.3 Set up f0 as /boot if necessary One of the weaknesses of the current hppa installer is that it won't let you mount the f0 partition as /boot. If you created a small (50MB-200MB) ext2 partition and mounted it as /boot during the install process, you can skip this section and go to 8.4. If not, and you have a / that goes out beyond 2GB from the beginning of your disk, here is your salvation. Of course, if you're starting from scratch, you can set up an f0 and an ext2 partition that you mount as /boot, but the preferred partitioning scheme is to just set up one f0 partition during installation (at least 50MB for a production system and say 200MB for a development system) and then use palo to format it, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot. Here's what to do: a. Edit /etc/palo.conf, on the --commandline change your pointer to vmlinux to 1/vmlinux and insert initrd=1/initrd.img. Add a line that says --format-as=2 Leave the line that says --init-partitioned=/dev/sda (or similar) Remove the line that says --recoverykernel=/boot/vmlinux.old (or similar) b. Now run palo. This will format your f0 partition. c. Assuming your f0 partition is on sda1, mount /dev/sda1 mnt d. cp /boot/* /mnt e. edit /etc/fstab so that /dev/sda1 is mounted as /boot by adding this line: # /dev/sda1 /boot ext2defaults 0 2 f. Edit /etc/palo.conf and remove the --format-as=2 line and change the --init-partitioned=/dev/sda to --update-partitioned=dev/sda. g. Now run palo. h. Reboot. If this fails, look at 8.4, go back over the steps above and try again. If it works, i. Run /etc/init.d/klogd stop (if you dont stop klogd, youll get device is busy when you try to umount /boot in the next step) j. umount /boot k. rm /boot/* l. mount /boot If you get through step l., you're done. 8.4 Edit /etc/palo.conf Edit /etc/palo.conf and insert on the --commandline initrd=x/boot/initrd.img where x is the number of the disk
RE: 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: On Sun, Feb 27, 2005 at 07:36:45PM -0500, Stuart Brady wrote: >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. >From a newbie point of view, I think it's important to know that you might have a partition scheme where you are booting something like 3/boot/vmlinux that might just stop working if root starts to fill up and because of format-as=2 you have a chance to fix it on a 2.6 upgrade. >> 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. Thanks Stuart, I finally sat down and read the explanation of unstable and testing. Someone else told me that unstable was more reliable that testing which clearly isn't the case. Sorry for putting my misunderstanding in the document. Regards, Harry -- 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]
PA-RISC/Linux Boot HOWTO: 2.4 -> 2.6
Hi, I'm sure you're way beyond my rough scrawl, but I found one small baby step that I left out (8.3 c) and I want to make sure that whatever goes out is complete to the lowest level of detail. Thanks, Harry 8. Upgrading from a Debian hppa 2.4 Kernel to a 2.6 kernel 8.1 Check your 2.4 partition scheme 8.2 First Steps 8.3 Set up f0 as /boot if necessary 8.4 Edit /etc/palo.conf 8.5 Before you reboot 8.6 Conclusion 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: > palo ipl 1.5 [EMAIL PROTECTED] Tue Sep 21 15:14:05 MDT 2004 > > Partition Start(MB) End(MB) Id Type > 1 1 31 f0 Palo > 2 321008 82 swap > 31009 17366 83 ext2 root Don't despair. There is a way to tell palo to format your f0 partition, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot (See 8.3). Here's an example that works: Disk /dev/sda: 73.4 GB, 73407865856 bytes 255 heads, 63 sectors/track, 8924 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 *1 24 192748+ f0 Linux/PA-RISC boot /dev/sda2 25 148 996030 82 Linux swap /dev/sda3 149 214016000740 83 Linux /dev/sda4 2141 892454492480 83 Linux and here's the palo.conf that goes with it: --commandline=0/vmlinux-2.6.11-rc2-pa3-UP root=/dev/sda3 panic=5 console=ttyS1 --update-partitioned=/dev/sda 8.2 First steps I'm the conservative type, so I don't load from "unstable". At the time of this writing, the 2.6 kernels in "testing" are 2.6.8-2-32, 2.6.8-2-32-smp, 2.6.8-2-64 and 2.6.8-2-64-smp. Step 1 For example, apt-get install kernel-image-2.6.8-2-32-smp. When you get near the end of the install, you will get messages telling you that this is an initrd kernel and asking you if you want to abort. At this point say, "Yes". Now it's time for: Step 2 you need to add "sym53c8xx" to /etc/mkinitrd/modules. "modules" is created from /etc/mkinitrd/modules.dpkg-new. This is how it looks after editing: % cat /etc/mkinitrd/modules.dpkg-new # /etc/mkinitrd/modules: Kernel modules to load for initrd. # # This file should contain the names of kernel modules and their arguments # (if any) that are needed to mount the root file system, one per line. # Comments begin with a `#', and everything on the line after them are ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 tulip sym53c8xx Okay. Now we are ready for: Step 3 apt-get install kernel-image-2.6.8-2-32-smp again, but this time when asked if you want to abort, say, "No". Step 4 Run apt-get upgrade Step 5 Run palo -? and make sure your palo has -format-as=type 8.3 Set up f0 as /boot if necessary One of the weaknesses of the current hppa installer is that it won't let you mount the f0 partition as /boot. If you created a small (50MB-200MB) ext2 partition and mounted it as /boot during the install process, you can skip this section and go to 8.4. If not, and you have a / that goes out beyond 2GB from the beginning of your disk, here is your salvation. Of course, if you're starting from scratch, you can set up an f0 and an ext2 partition that you mount as /boot, but the preferred partitioning scheme is to just set up one f0 partition during installation (at least 50MB for a production system and say 200MB for a development system) and then use palo to format it, copy everything from /boot over too it and the modify fstab to make the f0 partition mount as /boot. Here's what to do: a. Edit /etc/palo.conf, on the --commandline change your pointer to vmlinux to 1/vmlinux and insert initrd=1/initrd.img. Add a line that says --format-as=2 Leave the line that says --init-partitioned=/dev/sda (or similar) Remove the line that says --recoverykernel=/boot/vmlinux.old (or similar) b. Now run palo. This will format your f0 partition. c. cd / d. Assuming your f0 partition is on sda1, mount /dev/sda1 mnt e. cp /boot/* /mnt f. edit /etc/fstab so that /dev/sda1 is mounted as /boot by adding this line: # /dev/sda1 /boot ext2defaults 0 2 g. Edit /etc/palo.conf and remove the --format-as=2 line and change the --init-partitioned=/dev/sda to --update-partitioned=dev/sda. h. Now run palo. i. Reboot. If this fails, look at 8.4, go back over the steps above and try again. If it works, j. Run /etc/init.d/klogd stop (if you dont stop klogd, youll get device is busy when you try to umount /boot in the next step) k. umount /boot l. rm /boot/* m. mount /boot If you get through step m., you're done. 8.4 Edit /etc/palo.conf Edit /etc/palo.conf and insert on the --commandline initrd=x/boot/initrd.img w
RE: PA-RISC/Linux Boot HOWTO: 2.4 -> 2.6
Thanks Stuart, Got it. Either mount /dev/sda1 /mnt or cd / and then mount /dev/sda1 mnt obviously do it, but rather than "fixing" my mistake with a cd, it's certainly better to just mount /dev/sda1 /mnt. Cheers, Harry -Original Message- From: Stuart Brady [mailto:[EMAIL PROTECTED] Sent: Sunday, March 06, 2005 6:32 AM To: debian-hppa@lists.debian.org Subject: 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] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Clam AV Crashes on 2.6.8-2-32-smp
Hi, I am running a J6000 with 2GB of memory as a production E-mail server for my company with netqmail, clamav, razor and spam assassin. I am experiencing problems with clamav. The log entires look like: clamav.log.5.gz:Sat Apr 9 00:11:13 2005 -> Segmentation fault Is there anyone else running clamav who is experiencing this problem? Could the maintainer of clamav please tell me what I can do to help pin down the problem. This is a very serious problem for us, because if the crash occurs outside business hours, an order with an attachment will be rejected because it can't be virus scanned. Thanks, Harry Cochran -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Unable to get Visualize C3000 to see CDROM from BOOT_ADMIN
Hi, I have several hppa boxes from a project a few years ago that I would like to be able to use with Debian Linux. I downloaded debian-30r2-hppa-binary-1 and burned the iso with Nero (someone said Nero preserved the 512 byte sectors needed for the C3000). I can see the cd fine from HPUX, but when I try to boot /dev/dsk/c0t0d0, I get "ERROR: Not a boot path". Can anyone tell me how to boot from the cdrom on my C3000? Thanks, Harry
Depmod unresolved symbols when upgrading to 2.4.18-32-smp on J6000
Hi, I installed Debian on my J6000. Very smooth install ... congratulations to all on the hppa team. However, when I tried to install kernel-image-2.4.18-32-smp, I got a jillion unresolved symbols in Depmod (including things like aic7xxx.o). Can someone please tell me what I did wrong and how to resolve this please? Message says "you may have versioned symbol names" ... no, not to my knowledge ... "or this could be an error. depmod exited with a return value of 1." I aborted the install. Thanks, Harry
Unable to get PALO to install on A180 Debian install
Hi, I'm sure it's something simple, but I' stuck, sorry. I am installing Debian off of the official cd (the same thing happens installing from ftp site using the cd I burned with Nero as a starting point); I get all the way through the install to "Make the system bootable" and then it comes back and says "Unable to install Palo, you may still be able to remote boot by pointing at the installed system ..." (or something like that). When I reboot and go into BOOT_ADMIN and enter boot and then yes to the ipl question, it comes back and says "SOFT Booted" and then hangs (never gets to ipl). If I restart the machine and go through the same proceedure it says "HARD Booted" and then hangs. If I just let it try to auto boot it does the same thing (obviously). If anyone can tell me how to get out of this catch 22, I would appreciate it. I'm planning to use the A180 as a Proxy Server. Thanks, Harry
Getting a smp kernel on my J6000
Hi, Thibaut VARENE was kind enough to point me to http://cvs.parisc-linux.org/download/linux-2.4/ to get a smp kernel for my J6000. I'm sorry to say that I can't figure out how to apt-get the right 2.4.26 kernel for my J6000 by just looking at this page. 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). Truth be told I'm really not sure if debian-64-smp is the right choice for the pa-risc 8500. If someone has installed a smp kernel for a J6000 before (or just understands how to figure out what to do based on what's on the page), I would really appreciate some help. Thanks, Harry
Getting a smp kernel on my J6000
My thanks to Kyle McMartin and Stuart Brady. vmlinux-2.4.26-pa4-debian-64-smp seems to run just fine on my J6000!
Getting a smp kernel on my J6000
Hi, Well, newbie that I am, I just learned about "uname -a" and I've discovered that even though the /boot/vmlinux symlink points to the correct kernel (vmlinux-2.4.26-pa4-debian-64-smp), palo loaded 2.4.17-32. Looking back at the palo output, here's what happened: Selected kernel: /boot/vmlinux from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable ... Looks like the -smp won't work. Could someone please tell me tell me what's going on? Does palo have this "32 or 64" check to keep you from runnning a smp kernel? Can I just rename the new kernel to end in 64, modify the symlink and boot the smp kernel? By the way, my apologies to all for replies that didn't include [EMAIL PROTECTED] Some orgs try to minimize list traffic ... glad to see you have the opposite viewpoint :-). Thanks, Harry
Getting a smp kernel on my J6000
Hi, I loaded a smp kernel on my J6000 and made the /boot/vmlinux symlink point to the new kernel (vmlinux-2.4.26-pa4-debian-64-smp), however palo loaded 2.4.17-32. Looking back at the palo output, here's what happened: Selected kernel: /boot/vmlinux from partition 1 Warning: kernel name doesn't end with 32 or 64 -- Guessing... This box can boot either 32 or 64-bit kernels...Only see a 32-bit kernel, using thatELF32 executable ... Could someone please tell me tell me why palo has this "32 or 64" check which keeps you from runnning a kernel that ends in smp? Can I just rename the new kernel to end in 64, modify the symlink and boot the smp kernel? Thanks, Harry
Graphics mode on my C3000
Hi,
I have installed Debian hppa on my C3000. I had to use a serial console
to
do it. I installed X with tasksel. When I change back to graphics mode (pa
con GRAPHICS(2)), the system boots, and at the end when it tries to go into
X ("Starting X display manager: xdm."), the screen flashes 3 times and the
system dies. I've seen comments from several people that they got their
C3000 going. I'm hoping someone can tell me how to get my console into
graphics mode. Also, if I special instructions in palo.conf to get the usb
keyboard and the usb mouse going, I would appreciate a pointer on what I
should put in. Interestingly, when you go into ipl on boot, it says
"console=tty0" (I was expecting "console=GRAPHICS(2)" ... tried change to
this, but it didn't help).
Thanks,
Harry
Questions on C3000 install
Hi, First question on the Debian C3000 install: I had to go to a serial console because I couldn't figure out how to get the usb keyboard working with the graphics console after a boot from the ide cd-rom. If someone knows howto get the keyboard working for a graphics consoile install, that would be great. Also when you are asked to configure the mouse, I don't see an option to select a usb mouse which is standard on the C3000. Could someone please tell me how to configure a usb mouse during install? Next, once you get to "install kernel and driver modules" the ide cd-rom is not mounted and, newbie that I am, I can't firgure out how to get it mounted from an ash shell. If someone could tell me how to do this, I would appreciate it (of course, you can just load using the network connection, but it would be faster to load from my official cd-roms that I paid money for :-). Thanks, Harry
RE: Graphics mode on my C3000
Hi
Dan,
Thanks for your speedy reply. I
really appreciate your answers. Where did you find a cheap visualize
EG/PCI? The only one I could find was at kam.com and they want $120 for
it!
Best regards,
Harry
-Original Message-From: Daniele Antonozzi
[mailto:[EMAIL PROTECTED]Sent: Wednesday, June 16, 2004 10:48
AMTo: debian-hppa@lists.debian.orgSubject: Re: Graphics
mode on my C3000
You can follow this link to get some hints for the graphics
cardhttp://parisc-linux.org/faq/graphics-howto.htmlWhat
graphic card do you have? X doesn't work on FX graphics cards. I have
the visualize EG/PCI and X works fine. I cheaply bought it on internet
The kernel of woody (2.4.17) does not support usb mouse and keyboard,
you need to install a recent kernel. .. For example I have
installed the kernel-image 2.4..24 . Take a look to the parisc boot howto
I use it to install debian on my c3k. It is really helpfull!!!
http://www.pateam.org/parisc-linux-boot/doc.html
the ide cd rom is not supported from debian. You have to use an external
scsi cd drive to use your cd set.
Dan- Original Message -From: "Harry Cochran"
<[EMAIL PROTECTED]>To:
<debian-hppa@lists.debian.org>Sent:
Wednesday, June 16, 2004 2:58 PMSubject: Graphics mode on my
C3000> Hi,>> I have installed Debian hppa on my
C3000. I had to use a serial console to> do it. I installed X with
tasksel. When I change back to graphics mode (pa> con GRAPHICS(2)), the
system boots, and at the end when it tries to gointo> X ("Starting
X display manager: xdm."), the screen flashes 3 times and the> system
dies. I've seen comments from several people that they got their> C3000
going. I'm hoping someone can tell me how to get my console into>
graphics mode. Also, if I special instructions in palo.conf to get the
usb> keyboard and the usb mouse going, I would appreciat e a pointer on
what I> should put in. Interestingly, when you go into ipl on boot, it
says> "console=tty0" (I was expecting "console=GRAPHICS(2)" ... tried
change to> this, but it didn't help).>>
Thanks,>> Harry>>> --> To
UNSUBSCRIBE, email to [EMAIL PROTECTED]>
with a subject of "unsubscribe". Trouble? Contact[EMAIL PROTECTED]>
Yahoo!
Companion - Scarica gratis la toolbar di Ricerca di Yahoo!
RE: Graphics mode on my C3000
Thanks Dan, With shipping to the US it's less than half the price ($50 to be exact) of kam.com! Best regards, Harry -Original Message- From: Daniele Antonozzi [mailto:[EMAIL PROTECTED] Sent: Thursday, June 17, 2004 7:49 AM To: debian-hppa@lists.debian.org Subject: RE: Graphics mode on my C3000 Ciao Harry, >Where did you find a cheap visualize EG/PCI? I live in Europe, I bought it from http://www.unixnerd.demon.co.uk/ in UK. You could try Ebay. Some time ago there were some vis eg cards starting form 10$!!! But the card was in US and the shipping cost to Europe were to hight. Bye, dan Yahoo! Companion - Scarica gratis la toolbar di Ricerca di Yahoo! http://companion.yahoo.it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Getting vmlinux-2.4.26-pa4-debian-64-smp to boot
Hi, I'm missing something really simple, but I don't seem to get able to get my J6000 to boot vmlinux-2.4.26-pa4-debian-64-smp. Okay, I did apt-get install vmlinux-2.4.26-pa4-debian-64-smp, I changed the symlink /boot/vmlinux -> vmlinux-2.4.26-pa4-debian-64-smp and I edited palo.conf to change --recoverykernel=/boot/vmlinux (the command line already said 1/boot/vmlinux and sda1 is my f0 partition). On boot up I get: Selected kernel: /boot/vmlinux from parttion 1 Warning: kernel name doesn't end with 32 or 64 --Guessing... This box can either boot 32 or 64 bit kernels...Only see a 32 bit kernel, using thatELF32 executable I would really appreciate it if someone could tell me what I'm doing wrong. Also, I'm assuming that I'm better off with a 64 bit kernel than a 32 bit kernel since the cpu is 64 bit. Is this true? Thanks, Harry
Graphics mode on my C3000 - close but no cigar
Hi Daniele, I received and installed the Visualize EG/PCI card. I reloaded Debian from scratch. I chose monitor resolution 1280x960 at 85Hz since there was no 1280x1024 choice. I chose gdm for the display manager because Grant told me xdm had problems. I installed kernel-image-2.4.26-32 and did apt-get upgrade (I had installed X on the original installation). The upgrade returned an error 1 on installing xfont-scalable and I didn't know how to fix it. Anyway, I proceeded to reboot (with pa con GRAPHICS(3) type 2) and X failed to come up. I got a dialog box asking if I wanted to see what was wrong with the X configuration and I said "Yes". This brought up a window which said "Process set to nice value 0 instead of -10 as requested" and a bunch of XFree disclaimers. I have looked at /etx/X11/XF86Config-4 (when X fails, it brings up the serial console) and I can't see anything obviously wrong. At this point I am requesting that you tell me exactly what you did to get you C3000 running in Graphics mode please. Thank you, Harry
RE: Graphics mode on my C3000 - close but no cigar
Thanks for your inputs Grant, but I still can't get it to work ... replies follow your inputs below: -Original Message- From: Grant Grundler [mailto:[EMAIL PROTECTED] Sent: Saturday, June 26, 2004 9:59 PM To: Harry Cochran Cc: Daniele Antonozzi; debian-hppa@lists.debian.org Subject: Re: Graphics mode on my C3000 - close but no cigar On Sat, Jun 26, 2004 at 09:07:34PM -0400, Harry Cochran wrote: > Hi Daniele, > > I received and installed the Visualize EG/PCI card. I reloaded Debian from > scratch. I chose monitor resolution 1280x960 at 85Hz since there was no > 1280x1024 choice. The card certainly supports it. PCI Vis-EG/PCI will support up to 1600x1200 @ 60Hz (IIRC). Did you hit key when the system was powering up? Yes it reports GRAPHICS(3) type 2 (1280x1024 at 75Hz) > I chose gdm for the display manager because Grant told me > xdm had problems. Correct. But I personally don't use any Display Manager - only a primitive window manager. Do you know if gdm works? > I installed kernel-image-2.4.26-32 and did apt-get upgrade > (I had installed X on the original installation). The upgrade returned an > error 1 on installing xfont-scalable and I didn't know how to fix it. > Anyway, I proceeded to reboot (with pa con GRAPHICS(3) type 2) and X failed > to come up. I got a dialog box asking if I wanted to see what was wrong with > the X configuration and I said "Yes". This brought up a window which said > "Process set to nice value 0 instead of -10 as requested" and a bunch of > XFree disclaimers. I have looked at /etx/X11/XF86Config-4 (when X fails, it > brings up the serial console) and I can't see anything obviously wrong. > At > this point I am requesting that you tell me exactly what you did to get you > C3000 running in Graphics mode please. Any idea about the error: "Setting up xfonts-scalable (4.3.0.dfsg.1-5) ... fmt: invalid line number increment: '0' dpkg: error processing xfonts-scalable (--configure): subprocess post-installation script returned error exit status 1 I think you have alll the basic things in place. The resolution specified for the Section "Screen"/Subsection "Display" must exactly match what fbset reports. Okay. I installed fbset and fbset --test and fbset --show both report: mode: "1280x1024" geometry 1280 1024 1280 1024 8 timings 0 0 0 0 0 0 rgba 8/0, 8/0, 8/0, 0/0 endmode I edited the Section "Screen"/Subsection "Display" of /etx/X11/XF86Config-4 and changed 1280x960 to 1280x1024 everywhere, so now the SubSection says: SubSection "Display" Depth n Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection for n=1,4,8,15,16,24 I assume the "8" fbset reports under geometry and rgba is 8 bit color. Is that right? I specfied 16bit color when I installed. Anyway I tried Default Depth 16 and Default Depth 8 and got the same result. Also, as I said, when I installed I picked 1280x960 at 85Hz because it was the closest thing on the list to 1280x1024 at 75Hz which is type 2. The Monitor Sections says: Section "Monitor" Identifier "Generic Monitor" HorizSync 30-92 VertRefresh 50-85 Option "DPMS" Do I have to do something to get XF86Config-4 registered as you have to do with palo.conf after changing it? Have you read the PA-RISC Graphics HOW-TO? http://www.parisc-linux.org/faq/graphics-howto.html Yes, I didn't find your write-up helpful beyond a certain point. hth, grant Thanks again for your help, Harry
RE: Graphics mode on my C3000 - still no joy
Thanks Helge and Joel, I edited /etc/X11/XF86Config-4 according to your recommendations. It now reads: Section "Screen" Identifer "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth 8 SubSection "Display" Depth 8 Modes "1280x1024" EndSubSection EndSection On reboot, I get the same error as before. A dialog box asking if I wanted to see what was wrong with the X configuration and I said "Yes". This brought up a window which said "Process set to nice value 0 instead of -10 as requested" and a bunch of XFree disclaimers. It feels like the changes I'm making to XF86Config-4 aren't making any difference. Is the process xinit goes through reading XFConfig-4 dynamic on every boot? Also, does anyone have any idea about the error: "Setting up xfonts-scalable (4.3.0.dfsg.1-5) ... fmt: invalid line number increment: '0' dpkg: error processing xfonts-scalable (--configure): subprocess post-installation script returned error exit status 1 Best regards, Harry -Original Message- From: Helge Deller [mailto:[EMAIL PROTECTED] Sent: Sunday, June 27, 2004 12:06 PM To: debian-hppa@lists.debian.org Cc: Harry Cochran Subject: Re: Graphics mode on my C3000 - close but no cigar On Sunday 27 June 2004 17:24, Harry Cochran wrote: > SubSection "Display" > Depth n > Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" > EndSubSection > for n=1,4,8,15,16,24 Please try this one _only_ (remove all other resolutions): SubSection "Display" Depth 8 Modes "1280x1024" EndSubSection Helge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] But the clue here, is that hppa fb doesn't support switching and so just change Modes as : Modes "1280x1024" would be enough to fix your pb and make sure the default depth is well 8 :) hth, Joel
RE: Graphics mode on my C3000 - still no joy - more info
I was wrong about the message "Process set to nice value 0 instead of -10 as requested" after the "I cannot start the X server" window ... it's gone. The next window starts out "This is apre-release of XFree86 and is not supported in any way". Also, after you see this window, you get a chance to retry to start X. You put in the root password and it goes through the process pretty quickly. By watching it several times I was able to see two things: 1. "Unable to open/locate file //XF86Config.new error from xf86HandleConfigFile() 2. Fatal Screen Error: No Screens Found By the way, I also tried changing the monitor to type 5 (1024x768) and changing the mode to 1024x768 in the Display SubSection. This made no difference. Thanks, Harry Thanks Helge and Joel, I edited /etc/X11/XF86Config-4 according to your recommendations. It now reads: Section "Screen" Identifer "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth 8 SubSection "Display" Depth 8 Modes "1280x1024" EndSubSection EndSection On reboot, I get the same error as before. A dialog box asking if I wanted to see what was wrong with the X configuration and I said "Yes". This brought up a window which said "Process set to nice value 0 instead of -10 as requested" and a bunch of XFree disclaimers. It feels like the changes I'm making to XF86Config-4 aren't making any difference. Is the process xinit goes through reading XFConfig-4 dynamic on every boot? Also, does anyone have any idea about the error: "Setting up xfonts-scalable (4.3.0.dfsg.1-5) ... fmt: invalid line number increment: '0' dpkg: error processing xfonts-scalable (--configure): subprocess post-installation script returned error exit status 1 Best regards, Harry -Original Message- From: Helge Deller [mailto:[EMAIL PROTECTED] Sent: Sunday, June 27, 2004 12:06 PM To: debian-hppa@lists.debian.org Cc: Harry Cochran Subject: Re: Graphics mode on my C3000 - close but no cigar On Sunday 27 June 2004 17:24, Harry Cochran wrote: > SubSection "Display" > Depth n > Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" > EndSubSection > for n=1,4,8,15,16,24 Please try this one _only_ (remove all other resolutions): SubSection "Display" Depth 8 Modes "1280x1024" EndSubSection Helge -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] But the clue here, is that hppa fb doesn't support switching and so just change Modes as : Modes "1280x1024" would be enough to fix your pb and make sure the default depth is well 8 :) hth, Joel
