Re: USB support
> > note that a usb floppy is not usb mass storage - your bios must have > > support for usb mass storage to boot from the key chain, and this > > is more rare than supporting usb floppy boot. > > Most usb floppy disks have support for a legacy mode, in which the USB > and the floppy disk together emulate a 'normal' floppy disk. That > doesn't mean a usb floppy disk isn't a USB mass storage device; at the > very least, it's supported by the usb-storage module under Linux. > How does that mode work then ? Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Default bootloader
On Wed, Nov 19, 2003 at 12:25:15AM +0100, Robert Millan wrote: > > Hi there! > > Time to talk a bit about which is going to be the default bootloader for i386 > in next Debian release. > > I (as GRUB co-maintainer) have discussed with Jason the possibility of GRUB > being the default bootloader for i386 in Debian 3.1, and we agree that GRUB is > now mature enough for that. > > Let me summarise the reasons why I believe GRUB is a good option: > > - Clean dessign. While GRUB's dessign is far from perfect, it is still a >very flexible one. GRUB understands filesystems and network protocols, >making it able to load kernels dynamicaly from the disk or the network, >without need to reinstall into the MBR with every kernel update. > The current grub has by no means a clean design. It lacks platform independence, correct bus abstraction layers and ROMeable code to start with. But it works, so it's probably not too bad to use it as the standard bootloader. Cheers, Peter. signature.asc Description: Digital signature
non IA32 d-i
Hi, Andreas suggested me I could help in getting d-i to work on non-IA32 architectures. I was wondering which arch you need the most help on. I have access to most of the debian supported archs except for sparc64 and real s390 hardware. Thanks, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#203852: busybox-cvs: FTBFS on alpha
On Sat, Aug 02, 2003 at 08:07:53AM +0100, Alastair McKinstry wrote: > Package: busybox-cvs > Version: 0.60.99.cvs20030426 (not installed) > Severity: serious > > > Fails to build from source on Alpha: > > > gcc -I./include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE > -D_FILE_OFFSET_BITS=64 -Wall -Wstrict-prototypes -Wshadow -Os > -fomit-frame-pointer -D_BSD_SOURCE -DNDEBUG-D_GNU_SOURCE > -I./modutils/obj/ -c -o util-linux/fdisk.o util-linux/fdisk.c > util-linux/fdisk.c:860: warning: declaration of `fd' shadows a global > declaration > util-linux/fdisk.c:214: warning: shadowed declaration is here > util-linux/fdisk.c: In function `_llseek': > util-linux/fdisk.c:862: error: `__NR__llseek' undeclared (first use in > this function) > util-linux/fdisk.c:862: error: (Each undeclared identifier is reported > only once > util-linux/fdisk.c:862: error: for each function it appears in.) > util-linux/fdisk.c: In function `my_llseek': > util-linux/fdisk.c:873: warning: passing arg 4 of `_llseek' from > incompatible pointer type > > Due to a lacking ___NR_llseek on Alpha. I think defining it as == > __NR_lseek should do, as the alpha is 64-bit. > > This bug is serious as it breaks debian-installer on the Alpha. > Yep. using __NR_lseek instead works fine. Runs here for almost a week now. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#203852: llseek bug
tag 203852 + patch
This patch fixes the compile problem of fdisk.c
diff -ur -x '*.o' -x '*.a' busybox-cvs-0.60.99.cvs20030426/util-linux/fdisk.c
my-busybox-cvs-0.60.99.cvs20030426/util-linux/fdisk.c
--- busybox-cvs-0.60.99.cvs20030426/util-linux/fdisk.c 2003-08-03 16:20:21.0
+0200
+++ my-busybox-cvs-0.60.99.cvs20030426/util-linux/fdisk.c 2003-07-26
04:19:24.0
+0200 @@ -859,7 +859,11 @@
static int _llseek( unsigned int fd, unsigned long offset_high,
unsigned long offset_low, loff_t *result, unsigned int whence)
{
+#ifndef __alpha__
return(syscall(__NR__llseek, fd, offset_high, offset_low,
result, whence));
+#else
+ return(syscall(__NR_lseek, fd, offset_high, offset_low, result,
whence));
+#endif
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
aboot
Hi,
Attached you will find a patch for aboot which fixes the following
problems :
- compile with gcc 3.3
- initrd netboot support with cmdline. The patch expects the following
data after net_aboot.nh :
4 bytes : kernel size
4 bytes : initrd size
kernel commandline (zero terminated) only first 255 chars are
actually used due to kernel limitations
gzipped kernel image
gzipped initrd image
Note that the kernel image has to be linked at 0xfc81 or
higher otherwise the aboot stack will be overwritten by the kernel
image.
Cheers,
p2.
diff -wur -x '*.o' -x '*.a' aboot-0.9/Makefile my-aboot-0.9/Makefile
--- aboot-0.9/Makefile 2003-08-03 20:00:37.0 +0200
+++ my-aboot-0.9/Makefile 2003-08-03 22:03:02.0 +0200
@@ -12,6 +12,8 @@
KSRC = /usr/src/linux
VMLINUX= $(KSRC)/vmlinux
VMLINUXGZ = $(KSRC)/arch/alpha/boot/vmlinux.gz
+INITRD = netboot-initrd.gz
+CMDLINE= cmdline
# for userspace testing
#TESTING = yes
@@ -109,8 +111,11 @@
$(CC) $(ABOOT_OBJS) $(DISK_OBJS) -o $@ $(LIBS)
endif
-vmlinux.bootp: net_aboot.nh $(VMLINUXGZ) net_pad
- cat net_aboot.nh $(VMLINUXGZ) net_pad > $@
+vmlinux.bootp: net_aboot.nh net_aboot.lds
+ $(LD) -Tnet_aboot.lds -o $@
+
+net_aboot.lds: net_aboot.lds.in Makefile
+ $(CPP) -xc -P net_aboot.lds.in -o net_aboot.lds -DCMDLINE=\"$(CMDLINE)\"
-DINITRD=\"$(INITRD)\" -DVMLINUXGZ=\"$(VMLINUXGZ)\" -DNET_ABOOT=\"net_aboot.nh\"
net_aboot.nh: net_aboot tools/objstrip
tools/objstrip -vb net_aboot $@
diff -wur -x '*.o' -x '*.a' aboot-0.9/aboot.c my-aboot-0.9/aboot.c
--- aboot-0.9/aboot.c 2001-10-17 00:46:07.0 +0200
+++ my-aboot-0.9/aboot.c2003-08-03 21:10:55.0 +0200
@@ -95,15 +95,15 @@
int i;
/* looks like an ELF binary: */
if (elf->e_type != ET_EXEC) {
- printf("aboot: not an executable ELF file\n");
+ xprintf("aboot: not an executable ELF file\n");
return -1;
}
if (!aboot_elf_check_arch(elf)) {
- printf("aboot: ELF executable not for this machine\n");
+ xprintf("aboot: ELF executable not for this machine\n");
return -1;
}
if (elf->e_phoff + elf->e_phnum * sizeof(*phdrs) > (unsigned)
blocksize) {
- printf("aboot: "
+ xprintf("aboot: "
"ELF program headers not in first block (%ld)\n",
(long) elf->e_phoff);
return -1;
@@ -114,7 +114,7 @@
start_addr = phdrs[0].p_vaddr; /* assume they are sorted */
entry_addr = elf->e_entry;
#ifdef DEBUG
- printf("aboot: %d program headers, start address %#lx, entry %#lx\n",
+ xprintf("aboot: %d program headers, start address %#lx, entry %#lx\n",
nchunks, start_addr, entry_addr);
#endif
for (i = 0; i < elf->e_phnum; ++i) {
@@ -122,7 +122,7 @@
chunks[i].offset = phdrs[i].p_offset;
chunks[i].size = phdrs[i].p_filesz;
#ifdef DEBUG
- printf("aboot: segment %d vaddr %#lx offset %#lx size %#lx\n",
+ xprintf("aboot: segment %d vaddr %#lx offset %#lx size %#lx\n",
i, chunks[i].addr, chunks[i].offset, chunks[i].size);
#endif
}
@@ -131,7 +131,7 @@
bss_size = (phdrs[elf->e_phnum - 1].p_memsz -
phdrs[elf->e_phnum - 1].p_filesz);
#ifdef DEBUG
- printf("aboot: bss at 0x%p, size %#lx\n", bss_start, bss_size);
+ xprintf("aboot: bss at 0x%p, size %#lx\n", bss_start, bss_size);
#endif
} else {
/* Fail silently, it might be a compressed file */
@@ -164,14 +164,14 @@
#else
result = cons_getenv(ENV_BOOTED_FILE, boot_file, sizeof(boot_file));
if (result < 0) {
- printf("aboot: warning: can't get ENV_BOOTED_FILE "
+ xprintf("aboot: warning: can't get ENV_BOOTED_FILE "
"(result=%lx)!\n", result);
strcpy(boot_file, "vmlinux.gz");
}
result = cons_getenv(ENV_BOOTED_OSFLAGS,
kernel_args, sizeof(kernel_args));
if (result < 0) {
- printf("aboot: warning: can't get ENV_BOOTED_OSFLAGS "
+ xprintf("aboot: warning: can't get ENV_BOOTED_OSFLAGS "
"(result=%lx)!\n", result);
strcpy(kernel_args, "i");
}
@@ -187,7 +187,7 @@
void unzip_error(char *x)
{
- printf("unzip: %s\n", x);
+ xprintf("unzip: %s\n", x);
}
@@ -199,7 +199,7 @@
get_boot_args();
r
Re: aboot
On Sun, Aug 03, 2003 at 11:14:40PM +0200, Peter 'p2' De Schrijver wrote:
> Hi,
>
> Attached you will find a patch for aboot which fixes the following
> problems :
>
Oops. I forgot 1 file in the patch. Note that I will be away from my
alpha hw coming 2 weeks.
Cheers,
peter
diff -wur -x "*.o" -x "*.a" -N /dev/null my-aboot-0.9/net_aboot.lds.in
--- /dev/null 2003-03-08 19:13:42.0 +0100
+++ my-aboot-0.9/net_aboot.lds.in 2003-07-30 23:02:48.0 +0200
@@ -0,0 +1,17 @@
+OUTPUT_FORMAT("binary")
+TARGET("binary")
+INPUT(NET_ABOOT)
+INPUT(VMLINUXGZ)
+INPUT(INITRD)
+INPUT(CMDLINE)
+SECTIONS {
+ output : {
+NET_ABOOT
+LONG(endkernel - beginkernel);
+LONG(endinitrd - endkernel);
+CMDLINE
+BYTE(0)
+beginkernel = . ; VMLINUXGZ ; endkernel = . ;
+INITRD ; endinitrd = . ;
+ }
+}
Re: Initial d-i success on alpha
Hi, On Wed, Sep 17, 2003 at 11:40:47PM -0500, Steve Langasek wrote: > 3PI'm pleased to report that, thanks to the help of Santiago Garcia > Mantinan, a bootable d-i netinst CD is now available for linux-alpha at > http://gluck.debian.org/cdimage/testing/netinst/alpha/ alongside the > existing i386 images. The CD should be bootable on any SRM-capable > alpha system; if anyone has an experience to the contrary, I'd > appreciate knowing. > Which kernel do you use ? do you have everything in modules ? my 2.4.22 builds with all modules still seem to have DMA problems. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB support
On Fri, Oct 10, 2003 at 09:05:34PM -0400, Joey Hess wrote: > I've been working on d-i usb support today. Current status is that it > works (boots) here, and it will work in the archive once we get a new > busybox and kernel-modules. > > I have only tested booting from a floppy, as none of the 6 or 10 > computers I have tried can boot direct from a non-floppy usb device[1]. What do you exactly mean with a 'non-floppy usb device' ? I have a USB keychain of 256MB with partitions and 2 machines which boot just fine from it. They both recognize the keychain as a USB HD and boot from the active partition using grub. Cheers, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: USB support
On Fri, Oct 10, 2003 at 09:16:53PM -0400, Joey Hess wrote: > Peter 'p2' De Schrijver wrote: > > On Fri, Oct 10, 2003 at 09:05:34PM -0400, Joey Hess wrote: > > > I've been working on d-i usb support today. Current status is that it > > > works (boots) here, and it will work in the archive once we get a new > > > busybox and kernel-modules. > > > > > > I have only tested booting from a floppy, as none of the 6 or 10 > > > computers I have tried can boot direct from a non-floppy usb device[1]. > > > > What do you exactly mean with a 'non-floppy usb device' ? I have a USB > > keychain of 256MB with partitions and 2 machines which boot just fine > > from it. They both recognize the keychain as a USB HD and boot from the > > active partition using grub. > > I have a 128 mb usb keychain that I have never seen boot anywhere. Glad > to know someone has one that works, do you know where I can buy your > model from? I bought mine at a trade show in belgium. So I can't really give you a good shop to buy it from. It's marked 'tiny disk'. usbview tells me Manufacturer: Prolific Technology Inc. It came with a 12cm CD containing manuals in English and Chinese and some software for windows. I also tried a 64MB keychain from a friend which works as well on both machines. So I think it's more a question of proper USB support in the BIOS. Hope it helps, Peter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#276942: installation-reports: d-i uses wrong graphics card on ultra 10 with creator 3D
Package: installation-reports Severity: important Debian-installer-version: 2004-09-29. URL of installer image: http://people.debian.org/~joshk/d-i/images/2004-09-29/sparc64/netboot/2.6/boot.img uname -a: Linux 2.4.26-sparc64 #1 Fri Jun 18 02:04:50 PDT 2004 sparc64 unknown (done on another image. Using the image mentioned I don't get a shell). Date: Sun, 17 Oct 2004 18:42:44 +0200 Method: netboot using bootp. boot server IA32 box running sid. Machine: Sun Ultra 10 Processor: TI Ultrasparc IIi (Sabre) Memory: 128MB Root Device: IDE Root Size/partition table: NA lspci: lspci -n: Base System Installation Checklist: Initial boot worked:[E] Configure network HW: [ ] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: The machine has an UPA creator 3d graphics board in addition to the onboard ATI graphics. The installer boots, but the console display likely ends up at the wrong video card. The last message to appear on the creator 3D output is 'using PROM console'. The kernel doesn't seem to detect the creator 3d board. The ATI video card is not initialized correctly as attaching a monitor doesn't give an image. The keyboard leds do function though, so the machine did not panic. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#276944: installation-reports: d-i segfaults at startup
Package: installation-reports Severity: important Debian-installer-version: 2004-09-20. URL of installer image: http://people.debian.org/~joshk/d-i/images/2004-09-29/sparc64/netboot/boot.img uname -a: Linux 2.4.26-sparc64 #1 Fri Jun 18 02:04:50 PDT 2004 sparc64 unknown (done on another image. Using the image mentioned I don't get a shell). Date: Sun, 17 Oct 2004 18:58:27 +0200 Method: netboot using bootp. boot server IA32 box running sid. Machine: Sun Ultra 10 Processor: TI Ultrasparc IIi (Sabre) Memory: 128MB Root Device: IDE Root Size/partition table: NA lspci: lspci -n: Base System Installation Checklist: Initial boot worked:[E] Configure network HW: [ ] Config network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: The kernel boots and intializes the creator 3d fb console correctly. After the 'VFS: Mounted root ...' and the init version message I get an endless series of 'Segmentation fault' messages. I guess the /sbin/debian-installer program crashes and is respawned ad infinitum by init. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-rc2 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: please test new quik with initrd-support
On Sun, Nov 28, 2004 at 11:40:36AM +0100, Simon Vallet wrote: > On Fri, 26 Nov 2004 10:58:48 +0100 > Holger Levsen <[EMAIL PROTECTED]> wrote: > > > and, better not to forget, the new quik.deb is available at > > http://www.ulyssis.org/~p2/debjes/ > > It doesn't seem to help on a Beige G3 Rev II, using > kernel-image-2.6.9-powerpc and initrd : I get stuck at > VFS : Unable to mount root fs on unknown-block (1,0), > which is what I experienced with previous quik versions. > > Here are the relevant quik.conf options I used : > > image=/boot/vmlinux-2.6.9-powerpc > append="root=/dev/ram0 initrd=/boot/initrd.img-2.6.9-powerpc > video=radeonfb:1024 [EMAIL PROTECTED]" > Label=Test > > Are there other kernel command-line options to try ? The quik.conf should be : image=/boot/vmlinux-2.6.9-powerpc append="root=/dev/ram video=radeonfb:[EMAIL PROTECTED]" initrd=/boot/initrd.img-2.6.9-powerpc Label=test Could you send me the boot log ? Does the kernel recognize the initrd image ? Does the kernel get the correct commandline ? Thanks, Peter (p2). signature.asc Description: Digital signature
