Re: [parisc-linux] Call for Testing
Hello Kyle, Kyle McMartin wrote: On Mon, Mar 28, 2005 at 02:42:42PM +, Joel Soete wrote: ... Mmm. Yeah, you need the initrd, as that will contain the zalon module. Could you add "zalon7xx" to /etc/mkinitrd/modules and regenerate the initrd either by reinstalling the kernel image or with a command like I finaly added all: "zalon7xx" "lasi700" "lasi_82596" so that it solved the the pb to access the external disk (lasi700) and the nic config (lasi_82596) :-) # mkinitrd -o /boot/initrd.img-2.6.8-2-32 2.6.8-2-32 Ok I will try some 'stress' test too now. Thanks, Joel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
Hello Kyle + all, I try to hack a bit more this pb but a very weird pb: > > > > On Tue, Mar 29, 2005 at 12:45:17PM +0200, Joel Soete wrote: > > > Any idae? > > > > > > > Hi Joel, > > > > Thanks again for helping me with this. I think the problem is that > > you don't have "discover1" or "hotplug" installed. I think this is > > at least the problem with lasi ethernet not getting loaded and may > > be a contributing factor for this as well. > > > ah... > # dpkg -l discover\* > > Desired=Unknown/Install/Remove/Purge/Hold > > > | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed > > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > > ||/ Name VersionDescription > > +++-==-==- > ii discover 2.0.7-2 >hardware identification system > > ii discover-data 2.2005.02.13-1 Data lists for Discover hardware detection > s > un discover1 (no description available) > > un discover1-data (no description available) > > > Better to remove 'discover' to reinstall 'discover1' ? > I install hotplug: no help :-( Well, (even thought that discover seems more recent) I purge the discover pkg and install discover1 in place: no help :_( I log more the boot the b180 and this looks like: sym0:8: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15) scsi(0:0:8:0): Domain Validation skipping write tests scsi(0:0:8:0): Ending Domain Validation Attached scsi generic sg0 at scsi0, channel 0, id 5, lun 0, type 0 Attached scsi generic sg1 at scsi0, channel 0, id 6, lun 0, type 0 Attached scsi generic sg2 at scsi0, channel 0, id 8, lun 0, type 0 SCSI device sda: 17773524 512-byte hdwr sectors (9100 MB) SCSI device sda: drive cache: write through /dev/scsi/host0/bus0/target5/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 > Attached scsi disk sda at scsi0, channel 0, id 5, lun 0 SCSI device sdb: 17773524 512-byte hdwr sectors (9100 MB) SCSI device sdb: drive cache: write back /dev/scsi/host0/bus0/target6/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 p11 > Attached scsi disk sdb at scsi0, channel 0, id 6, lun 0 SCSI device sdc: 17783112 512-byte hdwr sectors (9105 MB) SCSI device sdc: drive cache: write back /dev/scsi/host0/bus0/target8/lun0: p1 p2 p3 p4 < p5 p6 p7 p8 p9 p10 > Attached scsi disk sdc at scsi0, channel 0, id 8, lun 0 md: md1 stopped. md: bind md: bind raid1: raid set md1 active with 2 out of 2 mirrors mdadm: /devfs/mdmd: md2 stopped. /1 has been started with 2 drives. md: bind md: bind raid1: raid set md2 active with 2 out of 2 mirrors mdadm: /devfs/md/2 has been started with 2 drives. kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. INIT: version 2.86 booting Activating swap. Adding 127928k swap on /dev/md1. Priority:-1 extents:1 Checking root file system... fsck 1.37 (21-Mar-2005) /dev/md2: clean, 64824/215936 files, 293120/431840 blocks EXT3 FS on md2, internal journal System time was Wed Mar 30 08:46:42 UTC 2005. Setting the System Clock using the Hardware Clock as reference... System Clock set. System local time is now Wed Mar 30 08:46:44 UTC 2005. Cleaning up ifupdown...done. Calculating module dependencies... done. Loading modules... All modules loaded. device-mapper: 4.1.0-ioctl (2003-12-10) initialised: [EMAIL PROTECTED] Creating device-mapper devices...done. Creating device-mapper devices...done. Starting raid devices: md: md0 stopped. md: bind md: bind raid1: raid set md0 active with 2 out of 2 mirrors mdadm: /dev/md0 has been started with 2 drives. md: md3 stopped. md: bind md: bind raid1: raid set md3 active with 2 out of 2 mirrors mdadm: /dev/md3 has been started with 2 drives. md: md4 stopped. md: bind md: bind raid1: raid set md4 active with 2 out of 2 mirrors mdadm: /dev/md4 has been started with 2 drives. md: md5 stopped. md: bind md: bind raid1: raid set md5 active with 2 out of 2 mirrors mdadm: /dev/md5 has been started with 2 drives. md: md6 stopped. md: bind md: bind raid1: raid set md6 active with 2 out of 2 mirrors mdadm: /dev/md6 has been started with 2 drives. md: md7 stopped. md: bind md: bind raid1: raid set md7 active with 2 out of 2 mirrors mdadm: /dev/md7 has been started with 2 drives. md: md8 stopped. md: bind md: bind raid1: raid set md8 active with 2 out of 2 mirrors mdadm: /dev/md8 has been started with 2 drives. done. Setting up LVM Volume Groups... Reading all physical volumes. This may take a while... No volume groups found No volume groups found No volume groups found Checking all file systems... fsck 1.37 (21-Mar-2005) /dev/md0: clean, 72/32000 files, 110376/127936 blocks /dev/md3: clean, 4521/64000 files, 151291/255872 blocks /dev/md4: clean, 14/32000 files, 8179/127872 blocks (check in 3 mounts) /dev/
Re: [parisc-linux] Call for Testing
On Mon, Mar 28, 2005 at 12:31:02PM -0600, James Bottomley wrote: > Actually, you need to tell the system that eth0 should load module > lasi_82596 > > so /etc/modprobe.conf needs to contain the line > > alias eth0 lasi_82596 > > However, debian has a strange way of generating this file, so this line > actually has to go in some debian specific file. The line should go in a new file under /etc/modprobe.d/ -- if you modify an existing file in that directory, you'll have to edit it whenever module-init-tools is upgraded. You needn't run /sbin/update-modules with 2.6. /etc/modprobe.conf is optional, and modprobe reads each file in /etc/modprobe.d/ (except for those in the arch/ directory). FWIW, with Debian and a 2.4 kernel, /etc/modutils/ contains similar files to /etc/modprobe.d/. The main difference is that you have to run /sbin/update-modules to generate /etc/modules.conf so that your changes take effect. HTH, -- Stuart Brady -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
> -- Original Message -- > Date: Tue, 29 Mar 2005 12:19:17 -0500 > From: Kyle McMartin <[EMAIL PROTECTED]> > To: Joel Soete <[EMAIL PROTECTED]> > Cc: debian-hppa@lists.debian.org, [EMAIL PROTECTED] > Subject: Re: [parisc-linux] Call for Testing > > > On Tue, Mar 29, 2005 at 12:45:17PM +0200, Joel Soete wrote: > > Any idae? > > > > Hi Joel, > > Thanks again for helping me with this. I think the problem is that > you don't have "discover1" or "hotplug" installed. I think this is > at least the problem with lasi ethernet not getting loaded and may > be a contributing factor for this as well. > ah... # dpkg -l discover\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii discover 2.0.7-2 hardware identification system ii discover-data 2.2005.02.13-1 Data lists for Discover hardware detection s un discover1 (no description available) un discover1-data (no description available) Better to remove 'discover' to reinstall 'discover1' ? But 'hotplug' is not install at all. > Could you, at your leisure, try installing either or both of these > packages and giving it another boot? > No pb (i will try tomorrow) Thanks, Joel btw: my b180 has the same kind of disk organization (i.e. md + ext3 with just a more ext disk as chroot) and no pb to boot the initrd.img? (just another thought ;-)
Re: [parisc-linux] Call for Testing
On Tue, Mar 29, 2005 at 12:45:17PM +0200, Joel Soete wrote: > Any idae? > Hi Joel, Thanks again for helping me with this. I think the problem is that you don't have "discover1" or "hotplug" installed. I think this is at least the problem with lasi ethernet not getting loaded and may be a contributing factor for this as well. Could you, at your leisure, try installing either or both of these packages and giving it another boot? Thanks! Cheers, Kyle. -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
On Tue March 29 2005 04:45, Joel Soete wrote: > > devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED]) > devfs: boot_options: 0x0 > Hmm... devfs is enabled (on Debian?) and configured to mount at boot. > fsck 1.37 (21-Mar-2005) > /dev/md2: clean, 75757/200096 files, 344879/3998EXT3 FS on md2, 40 blocks > internal journal You are using ext3 filesystems... > Loading modules... > All modules loaded. Be certain ext3 module got loaded here... > Checking all file systems... > fsck 1.37 (21-Mar-2005) > fsck.ext3: Invalid argument while trying to open /dev/md0 And then this should work. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: [parisc-linux] Call for Testing
Hello Kyle,
>
> Hi,
>
> I've backported some more patches to 2.6.8 for possible[1] inclusion in
> sarge (they fix some possibly important bits).
>
> You can find kernels here:
> http://www.parisc-linux.org/~kyle/debian-kernel/2005-03-27/
>
Hope you will be also interested by those additional test:
a. a b180 booting fine its initrd.img :-) (from your pkg
kernel-image-2.6.8-2-32_2.6.8-7_hppa.deb)
b. a b2k trying first the same pkg all seems to works fine until 'cechecking
all fs :-( (here is the full boot log:)
Current command line:
2/vmlinux initrd=2/initrd.img root=/dev/md2 HOME=/ panic=120 profile=2
console=ttyS0
TERM=vt102
0: 2/vmlinux
1: initrd=2/initrd.img
2: root=/dev/md2
3: HOME=/
4: panic=120
5: profile=2
6: console=ttyS0
7: 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/md2 HOME=/ panic=120 profile=2
console=ttyS0
TERM=vt102 palo_kernel=2/vmlinux'
Selected kernel: /vmlinux from partition 2
Selected ramdisk: /initrd.img from partition 2
ELF32 executable
Entry 0010 first 0010 n 2
Segment 0 load 0010 size 2242736 mediaptr 0x1000
Segment 1 load 00324000 size 1056902 mediaptr 0x225000
Loading ramdisk 4714496 bytes @ 0fb6f000...
Branching to kernel entry point 0x0010. If this is the last
message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org
Linux version 2.6.8-2-32 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian
1:3.3.5-12))
#1 Sun Mar 27 06:04:08 EST 2005
FP[0] enabled: Rev 1 Model 16
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model 5d00 0481 0002 77e93910 10f0 0008 00b2
00b2
vers 0301
CPUID vers 17 rev 11 (0x022b)
capabilities 0x3
model 9000/785/B2000
Total Memory: 256 Mb
initrd: 1fb6f000-1ffee000
initrd: reserving 0fb6f000-0ffee000 (mem_max 1000)
LCD display at f05d0008,f05d registered
Built 1 zonelists
Kernel command line: root=/dev/md2 HOME=/ panic=120 profile=2 console=ttyS0
TERM=vt102 palo_kernel=2/vmlinux
kernel profiling enabled
PID hash table entries: 16 (order 4: 128 bytes)
Console: colour dummy device 160x64
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 262144k available
Calibrating delay loop... 799.53 BogoMIPS
Security Scaffold v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (ungzip failed); looks like an
initrd
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. Astro BC Runway Port at 0xfed0 [10] { 12, 0x0, 0x582, 0xb }
2. Elroy PCI Bridge at 0xfed3 [10/0] { 13, 0x0, 0x782, 0xa }
3. Elroy PCI Bridge at 0xfed32000 [10/1] { 13, 0x0, 0x782, 0xa }
4. Kazoo W+ at 0xfffa [32] { 0, 0x0, 0x5d0, 0x4 }
5. Memory at 0xfed10200 [49] { 1, 0x0, 0x09d, 0x9 }
CPU(s): 1 x PA8600 (PCX-W+) at 400.00 MHz
SBA found Astro 2.1 at 0xfed0
lba version TR4.0 (0x5) found at 0xfed3
PCI: Enabled native mode for NS87415 (pif=0x8f)
lba version TR4.0 (0x5) found at 0xfed32000
SCSI subsystem initialized
TC classifier action (bugs to netdev@oss.sgi.com cc [EMAIL PROTECTED])
STI GSC/PCI core graphics driver Version 0.9a
STI PCI graphic ROM found at f494 (128 kB), fb at fb00 (16 MB)
id 35acda16-9a02587, conforms to spec rev. 8.0c
graphics card name: HPA4982A
stifb: 'HPA4982A' (id: 0x35acda16) not supported.
unwind_init: start = 0x10325720, end = 0x103468b0, entries = 8473
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
Initializing Cryptographic API
SuperIO: Found NS87560 Legacy I/O device at :00:0e.1 (IRQ 64)
SuperIO: Serial port 1 at 0x3f8
SuperIO: Serial port 2 at 0x2f8
SuperIO: Parallel port at 0x378
SuperIO: Floppy controller at 0x3f0
SuperIO: ACPI at 0x7e0
SuperIO: USB regulator enabled
Soft power switch enabled, polling @ 0xf0400804.
Generic RTC Driver v1.07
Serial: 8250/16550 driver $Revision: 1.90 $ 25 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 99) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 100) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
sticon: Initializing STI text console.
Console: switching to colour STI console 160x64
mice: PS/2 mouse device common for all mice
HP SDC: No SDC found.
HP SDC MLC: Registering the System Domain Controller's HIL MLC.
HP SDC MLC: Request for raw HIL ISR hook denied
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
RAMDISK: cramfs filesystem found at block 0
RAMDISK: Loading 4604 blocks [1 disk] into ram disk... done
Re: [parisc-linux] Call for Testing
> -- Original Message -- > Date: Mon, 28 Mar 2005 11:34:12 -0700 > From: Grant Grundler <[EMAIL PROTECTED]> > To: Joel Soete <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], debian-hppa@lists.debian.org > Subject: Re: [parisc-linux] Call for Testing > > > On Mon, Mar 28, 2005 at 06:18:32PM +, Joel Soete wrote: > > >>just still have a small trouble with (builtin) nic: > > >>... > > >>Configuring network interfaces...SIOCSIFADDR: No such device > > > > > > > > >The error normally means the driver didn't get loaded. > > >Several possible causes/fixes: > > >o See if module versioning is enabled and failed to load because > > > of kernel/module version mismatch > > >o if it needs to be (but wasn't) included in the initrd. > > on this c110 it's in fact: > > LASI 82596 driver - Revision: 1.30 > > Found i82596 at 0xffd07000, IRQ 18 > > eth0: 82596 at 0xffd07000, 00 60 B0 07 1E EA IRQ 18. > > zalon_probe: Zalon version 1, IRQ 66 > > > Two more thougths crossed my mind: > o Could you try adding "noudev" to the palo boot commandline? I will try > o Possible that /etc/network/inferfaces is using a different > name (e.g. eth1) for autoconfigure? > need to check > > well build as a module (CONFIG_LASI_82596=m in config-2.6.8-2-32 :) > > So I think I have to do the same thing as for zalon driver > > > > >o install hotplug package to autoload PCI drivers > > would it help in this case (even if no pci on this box)? > > Oh...sorry. I was thinking later systems where tulip is built-in LAN. > Np I just put the question in case I missed something (so much thing are developed, extended in so may field that I am always afraid to miss intresting stuf :-) ) Thanks, Joel PS: I just don't have access to the system right now, I will come back asap)
Re: [parisc-linux] Call for Testing
On Mon, 2005-03-28 at 18:18 +, Joel Soete wrote: > > o install hotplug package to autoload PCI drivers > would it help in this case (even if no pci on this box)? No, not in this case. > > o add driver to /etc/modules if you don't like hotplug package > > or want explicitly control over the order drivers get loaded. > > Actually, you need to tell the system that eth0 should load module lasi_82596 so /etc/modprobe.conf needs to contain the line alias eth0 lasi_82596 However, debian has a strange way of generating this file, so this line actually has to go in some debian specific file. James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
Grant Grundler wrote: On Mon, Mar 28, 2005 at 05:21:36PM +, Joel Soete wrote: just still have a small trouble with (builtin) nic: ... Configuring network interfaces...SIOCSIFADDR: No such device The error normally means the driver didn't get loaded. Several possible causes/fixes: o See if module versioning is enabled and failed to load because of kernel/module version mismatch o if it needs to be (but wasn't) included in the initrd. on this c110 it's in fact: LASI 82596 driver - Revision: 1.30 Found i82596 at 0xffd07000, IRQ 18 eth0: 82596 at 0xffd07000, 00 60 B0 07 1E EA IRQ 18. zalon_probe: Zalon version 1, IRQ 66 well build as a module (CONFIG_LASI_82596=m in config-2.6.8-2-32 :) So I think I have to do the same thing as for zalon driver o install hotplug package to autoload PCI drivers would it help in this case (even if no pci on this box)? o add driver to /etc/modules if you don't like hotplug package or want explicitly control over the order drivers get loaded. Thanks I will try it later, Joel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
On Mon, Mar 28, 2005 at 06:18:32PM +, Joel Soete wrote: > >>just still have a small trouble with (builtin) nic: > >>... > >>Configuring network interfaces...SIOCSIFADDR: No such device > > > > > >The error normally means the driver didn't get loaded. > >Several possible causes/fixes: > >o See if module versioning is enabled and failed to load because > > of kernel/module version mismatch > >o if it needs to be (but wasn't) included in the initrd. > on this c110 it's in fact: > LASI 82596 driver - Revision: 1.30 > Found i82596 at 0xffd07000, IRQ 18 > eth0: 82596 at 0xffd07000, 00 60 B0 07 1E EA IRQ 18. > zalon_probe: Zalon version 1, IRQ 66 Two more thougths crossed my mind: o Could you try adding "noudev" to the palo boot commandline? o Possible that /etc/network/inferfaces is using a different name (e.g. eth1) for autoconfigure? > well build as a module (CONFIG_LASI_82596=m in config-2.6.8-2-32 :) > So I think I have to do the same thing as for zalon driver > > >o install hotplug package to autoload PCI drivers > would it help in this case (even if no pci on this box)? Oh...sorry. I was thinking later systems where tulip is built-in LAN. grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
Kyle McMartin wrote: On Mon, Mar 28, 2005 at 02:42:42PM +, Joel Soete wrote: ... That's very strange, I'll look into it. It might be caused by the zalon module not being loaded. See below. TCP: Hash tables configured (established 131072 bind 65536) Root-NFS: No NFS server available, giving up. VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "md2" or unknown-block(2,0) Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0) well my custom config is CONFIG_SCSI_ZALON=y while your CONFIG_SCSI_ZALON=m so should be loaded? Mmm. Yeah, you need the initrd, as that will contain the zalon module. Could you add "zalon7xx" to /etc/mkinitrd/modules and regenerate the initrd either by reinstalling the kernel image or with a command like # mkinitrd -o /boot/initrd.img-2.6.8-2-32 2.6.8-2-32 That nake the trick ;-) : _sudZUZ#Z#XZo=_ EE II NN NN _jmZZ2!!~---~!!X##wa DD DD EE BB BBII AA AA NNN NN . -]Xb/~__#2(One 120MHz PA-RISC Raven 120 T' Processor, 512M -Zo; +!4ZwuZZXY' 119.60 Bogomips Total *#[,~-?!!-~hpalin XUb;. )YXL,, +3#bc, -)SSL,, ~ Updating the linuxlogo... linuxlogo. Debian GNU/Linux 3.1 hpalin ttyS0 hpalin login: root Password: Last login: Mon Mar 28 18:30:13 2005 on ttyS0 Linux hpalin 2.6.8-2-32 #1 Sun Mar 27 06:04:08 EST 2005 parisc GNU/Linux The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. No mail. [EMAIL PROTECTED]:~# uname -a Linux hpalin 2.6.8-2-32 #1 Sun Mar 27 06:04:08 EST 2005 parisc GNU/Linux Cool :-) just still have a small trouble with (builtin) nic: ... Configuring network interfaces...SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Failed to bring up eth0. done. ... but no more time today :-( This may not be the exact line you need, I'm sorry I don't have time to look what it precisely is. np this was the right one :-) Thanks for testing! Welcome, Joel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
On Mon, Mar 28, 2005 at 05:21:36PM +, Joel Soete wrote: > just still have a small trouble with (builtin) nic: > ... > Configuring network interfaces...SIOCSIFADDR: No such device The error normally means the driver didn't get loaded. Several possible causes/fixes: o See if module versioning is enabled and failed to load because of kernel/module version mismatch o if it needs to be (but wasn't) included in the initrd. o install hotplug package to autoload PCI drivers o add driver to /etc/modules if you don't like hotplug package or want explicitly control over the order drivers get loaded. grant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
On Mon, Mar 28, 2005 at 02:42:42PM +, Joel Soete wrote: > mdadm: cannot open device /dev/scsi/sdh0-f3f8c800c0i5l0p2: No such device > or adsmdadm: /dev/scsi/sdh0-f3f8c800c0i5l0p2 has wrong uuid. > mdadm: cannot open device /dev/smd: md2 stopped. > csi/sdh0-f3f8c800c0i6l0p2: No such device or address > mdadm: /dev/scsi/sdh0-f3f8c800c0i6l0p2 has wrong uuid. > mdadm: no devices found for /devfs/md/1 > mdadm: cannot open device /dev/scsi/sdh0-f3f8c800c0i5l0p5: No such device > or adsmdadm: /dev/scsi/sdh0-f3f8c800c0i5l0p5 has wrong uuid. > mdadm: cannot open device /dev/scsi/sdh0-f3f8c800c0i6l0p5: No such device > or adsmdadm: /dev/scsi/sdh0-f3f8c800c0i6l0p5 has wrong uuid. > mdadm: no devices found for /devfs/md/2 > EXT3-fs: unable to read superblock > EXT2-fs: unable to read superblock > isofs_fill_super: bread failed, dev=md2, iso_blknum=16, block=32 > pivot_root: No sKernel panic: Attempted to kill init! > uch file or dire ctory > /sbin/ini<0>Rebooting in 120 seconds..t: 431: cannot open dev/console: No > such e > That's very strange, I'll look into it. It might be caused by the zalon module not being loaded. See below. > TCP: Hash tables configured (established 131072 bind 65536) > Root-NFS: No NFS server available, giving up. > VFS: Unable to mount root fs via NFS, trying floppy. > VFS: Cannot open root device "md2" or unknown-block(2,0) > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0) > > well my custom config is CONFIG_SCSI_ZALON=y while your CONFIG_SCSI_ZALON=m > so should be loaded? > Mmm. Yeah, you need the initrd, as that will contain the zalon module. Could you add "zalon7xx" to /etc/mkinitrd/modules and regenerate the initrd either by reinstalling the kernel image or with a command like # mkinitrd -o /boot/initrd.img-2.6.8-2-32 2.6.8-2-32 This may not be the exact line you need, I'm sorry I don't have time to look what it precisely is. Thanks for testing! Cheers, -- Kyle McMartin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [parisc-linux] Call for Testing
Hello Kyle,
I test it on a up 32bit c110 model, ...
Kyle McMartin wrote:
Hi,
I've backported some more patches to 2.6.8 for possible[1] inclusion in
sarge (they fix some possibly important bits).
You can find kernels here:
http://www.parisc-linux.org/~kyle/debian-kernel/2005-03-27/
so i consider kernel-image-2.6.8-2-32_2.6.8-7_hppa.deb, ok?
I tried for the first time to boot an initrd.img but unfortunaltely it failed
to complete the boot (boot log):
Current command line:
3/vmlinux-2.6.8-2-32 root=/dev/md2 initrd=3/initrd.img HOME=/ panic=120
profile2 0: 3/vmlinux-2.6.8-2-32
1: root=/dev/md2
2: initrd=3/initrd.img
3: HOME=/
4: panic=120
5: profile=2
6: console=ttyS0
7: 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/md2 HOME=/ panic=120 profile=2
console=ttyS'Selected kernel: /vmlinux-2.6.8-2-32 from partition 3
Selected ramdisk: /initrd.img from partition 3
ELF32 executable
Entry 0010 first 0010 n 2
Segment 0 load 0010 size 2242736 mediaptr 0x1000
Segment 1 load 00324000 size 1056902 mediaptr 0x225000
Loading ramdisk 4714496 bytes @ 1fb6d000...
Branching to kernel entry point 0x0010. If this is the last
message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org
Linux version 2.6.8-2-32 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian 1:3.3.5-125FP[0] enabled: Rev 1 Model 11
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model 58e0 0481 0002 77e47570 10f1 0004 008a 0avers 000d
CPUID vers 11 rev 13 (0x016d)
model 9000/777/C110
Total Memory: 512 Mb
initrd: 2fb6d000-2ffec000
initrd: reserving 1fb6d000-1ffec000 (mem_max 2000)
LED display at f0190001 registered
Built 1 zonelists
Kernel command line: root=/dev/md2 HOME=/ panic=120 profile=2 console=ttyS0 TER2kernel profiling enabled
PID hash table entries: 16 (order 4: 128 bytes)
Console: colour dummy device 160x64
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 524288k available
Calibrating delay loop... 119.60 BogoMIPS
Security Scaffold v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (ungzip failed); looks like an initrd
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. U2-IOA BC Runway Port at 0xfff88000 [8] { 12, 0x7, 0x580, 0xb }
2. SkyHawk 100/120 FW-SCSI at 0xf3f8c000 [8/12] { 4, 0x0, 0x01f, 0x00089 }
3. Raven T' Core BA at 0xffd0 [8/16] { 11, 0x0, 0x032, 0x00081 }, addition
4. Raven T' Core Centronics at 0xffd02000 [8/16/0] { 10, 0x0, 0x032, 0x00074 },
5. Raven T' Audio at 0xffd04000 [8/16/1] { 10, 0x0, 0x032, 0x0007b }
6. Raven T' Lasi Core RS-232 at 0xffd05000 [8/16/4] { 10, 0x0, 0x032, 0x0008c }
7. Raven T' Core SCSI at 0xffd06000 [8/16/5] { 10, 0x0, 0x032, 0x00082 }
8. Raven T' Core LAN (802.3) at 0xffd07000 [8/16/6] { 10, 0x0, 0x032, 0x0008a }
9. Raven T' Core PS/2 Port at 0xffd08000 [8/16/7] { 10, 0x0, 0x032, 0x00084 }
10. Raven T' Core PS/2 Port at 0xffd08100 [8/16/8] { 10, 0x0, 0x032, 0x00084 }
11. Raven T' Core PC Floppy at 0xffd0a000 [8/16/10] { 10, 0x0, 0x032, 0x00083 }
12. Raven T' Wax BA at 0xffe0 [8/20] { 11, 0x0, 0x01e, 0x0008e }, addition
13. Raven T' Wax HIL at 0xffe01000 [8/20/1] { 10, 0x0, 0x01e, 0x00073 }
14. Raven T' Wax RS-232 at 0xffe02000 [8/20/2] { 10, 0x0, 0x01e, 0x0008c }
15. Raven T' Wax EISA BA at 0xfc00 [8/20/5] { 11, 0x0, 0x01e, 0x00090 }, a
16. U2-IOA BC GSC+ Port at 0xf3fbf000 [8/63] { 7, 0x1, 0x501, 0xc }, addit
17. U2-IOA BC Runway Port at 0xfff8a000 [10] { 12, 0x7, 0x580, 0xb }
18. Raven T' GSC Core Graphics at 0xf400 [10/16] { 10, 0x0, 0x032, 0x00085
19. U2-IOA BC GSC+ Port at 0xf3fff000 [10/63] { 7, 0x1, 0x501, 0xc }
20. Raven 120 T' at 0xfffa [32] { 0, 0x0, 0x58e, 0x4 }
21. Memory at 0xfffb1000 [49] { 1, 0x0, 0x049, 0x9 }
CPU(s): 1 x PA7200 (PCX-T') at 120.00 MHz
Found U2 at 0xfff88000
Found U2 at 0xfff8a000
Lasi version 0 at 0xffd0 found.
Wax at 0xffe0 found.
Wax EISA Adapter found at 0xfc00
EISA EEPROM: cannot register misc device.
Enumerating EISA bus
EISA: Probing bus 0 at parisc8:20:5
EISA: Mainboard HWPC0E1 detected.
EISA: Detected 0 cards.
SCSI subsystem initialized
TC classifier action (bugs to netdev@oss.sgi.com cc [EMAIL PROTECTED])
STI GSC/PCI core graphics driver Version 0.9a
id 2b4ded6d-40a00499, conforms to spec rev. 8.04
graphics card name: HPA208LC1024
fb0: stifb 1024x768-8 frame buffer device, HPA208LC1024, id: 2b4ded6d, mmio: 0x0unwind_init: start = 0x10325720, end = 0x103468b0,
entries = 8473
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
devfs: 2004-01-31 Richard
