RE: Latest Sarge netboot failing...
Yes, 101% positive. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Joshua Kwan Sent: Sunday, May 23, 2004 6:35 AM To: debian-sparc@lists.debian.org Subject: Re: Latest Sarge netboot failing... This is funktastic. rootskel | 0.76 | unstable/debian-installer | alpha, arm, i386, m68k, mips, mipsel, powerpc, s390, sparc rootskel | 0.75 | testing/debian-installer | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc The framebuffer default was set to false for sparc back in 0.74. Are you sure you were using a current daily? -- Joshua Kwan
RE: Latest Sarge netboot failing...
Hooray. The first time I saw b4 working on non-x86... until got to the base-system component, which failed because the scsi-cd module could not be loaded (what the heck ?). Anyway, I went for the woody netinst now and did a dist-upgrade. Working like a charme. I just have one slightly OT question: Has anyone had problems with mp3s skipping in xmms mpg321 ? It's like timewarped playback. The card is a CS4231a. (Note, using plain alsa in xmms gives scrambled output, sounds like I'm listening to some capacitors having a party. xmms-esd works in the way mentioned above. mpg321 works straight out of the box with no parameters). -Alex -Original Message- From: Blars Blarson [mailto:[EMAIL PROTECTED] Sent: Thursday, May 20, 2004 11:52 PM To: [EMAIL PROTECTED]; debian-sparc@lists.debian.org Subject: Re: Latest Sarge netboot failing... In article [EMAIL PROTECTED] you write: Gives the exact same effect as the b4 image: VFS: mounted root (ext2 filesystem) Setting up filesystem, please wait ... Unimplemented SPARC system call 188 Unimplemented SPARC system call 188 Unimplemented SPARC system call 188 Unimplemented SPARC system call 188 Unimplemented SPARC system call 188 Unimplemented SPARC system call 188 umount: /initrd: invalid argument Segmentation fault Segmentation fault Segmentation fault [endless loop while producing screen distortions] That problem is with bterm and sbus or upa bus framebuffers. debian-installer/framebuffer=false is the workaround. -- Blars Blarson [EMAIL PROTECTED] http://www.blars.org/blars.html With Microsoft, failure is not an option. It is a standard feature. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Latest Sarge netboot failing...
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: Hooray. The first time I saw b4 working on non-x86... until got to the base-system component, which failed because the scsi-cd module could not be loaded (what the heck ?). Known bug, fixed in the sid daily builds. The fixed busybox hadn't made to to sarge last time I checkd, but the fix should make it to beta 5. Anyway, I went for the woody netinst now and did a dist-upgrade. Working like a charme. I just have one slightly OT question: Has anyone had problems with mp3s skipping in xmms mpg321 ? It's like timewarped playback. The card is a CS4231a. (Note, using plain alsa in xmms gives scrambled output, sounds like I'm listening to some capacitors having a party. xmms-esd works in the way mentioned above. mpg321 works straight out of the box with no parameters). Some sound programs assume little-endian. I haven't tried hooking speakers to a sparc running debian yet. -- Blars Blarson [EMAIL PROTECTED] http://www.blars.org/blars.html With Microsoft, failure is not an option. It is a standard feature.
Re: Latest Sarge netboot failing...
In article [EMAIL PROTECTED] you write: I just tried the daily netboot image, of course with negative outcome... I thought I'd tell the list, to maybe get some pointers or help someone fix it ;) here's the kernel's last few burps : VFS: Mounted root (ext2 filesystem) attempt to access beyond end of device 01:00: rw=0 want=5246, limit=4096 It looks like the initrd is exceeding 4MB again, try adding ramdisk_size=8192 to the silo boot options. The beta4 release fails with a segmentation fault. The machine is an Ultra60, 1x450 MHz CPU, 512mb of mem, Creator 3D, SCSI only Maybe I'm also just doing something wrong - any ideas ? It looks like this may have been figured out, but the fixes have not yet been applied. (cramfs bug with large page sizes, workaround is to not use cramfs or build it into the kernel.) In other words, I expect the current images to fail on your system. -- Blars Blarson [EMAIL PROTECTED] http://www.blars.org/blars.html With Microsoft, failure is not an option. It is a standard feature.
