I am trying to get an embedded pc board to run with linuxbios. The board is an arbor emcore6352 and is (almost) identical to the technoland sbc710 from the CVS tree. The onboard ethernet is an intel chipset however, and the cpu is a low power pentium iii.
* Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ... Any tips where I can start looking?
* The other thing , is that the board has it's sdram (128mb) soldered on the pcb, and there's no serial eeprom to read the stuff that usually comes from the smbus. So far the only way to get linuxbios to come up is to plug in extra sdram(in an sodimm socket) that DOES have the usual serial eeprom to do spd. I have the datasheets of the sdram components, so I guess it's a matter of hardcoding the information about those chips somewhere? Could you please give me a hint as to where would be the best place to insert this code into the source tree? Or any useful links about (basics) of sdram initialization, since I am a total newbie with this stuff.
Thanks
- Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...
Any tips where I can start looking?
It could be src/config/Config's CONFIG_COMPRESS is set to 1. Try to set it to 0.
-Andrew
On Thu, 16 Jan 2003 daniel@dmhome.net wrote:
I am trying to get an embedded pc board to run with linuxbios. The board is an arbor emcore6352 and is (almost) identical to the technoland sbc710 from the CVS tree. The onboard ethernet is an intel chipset however, and the cpu is a low power pentium iii.
did you run getpir? Run getpir under the normal bios and see if it matches what is in the bios you are building. I bet it doesn't.
I think it might be a good idea to add the emcore to the tree, so if you can help me get this worked out we will add it.
Also folks I'm trying to get the STATUS pages up to date but our web site is in transition so give us a week or so.
ron
- Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...
Send me the dmesg output.
- The other thing , is that the board has it's sdram (128mb) soldered on
the pcb, and there's no serial eeprom to read the stuff that usually comes from the smbus. So far the only way to get linuxbios to come up is to plug in extra sdram(in an sodimm socket) that DOES have the usual serial eeprom to do spd. I have the datasheets of the sdram components, so I guess it's a matter of hardcoding the information about those chips somewhere?
yes, I guess so. I would build a custom raminit.inc for this motherboard.
Let's start by getting it into the tree, this will make your life a LOT easier.
ron
On Fri, 2003-01-17 at 05:08, Ronald G. Minnich wrote:
did you run getpir? Run getpir under the normal bios and see if it matches what is in the bios you are building. I bet it doesn't.
Actually I did run getpir before , then make test, altered the checksum in pirq_tables.c , tried again, this didn't help.
The error seems to occur in verify_copy_pirq_routing_table, could that be a memory problem? Is it actually necessary that this copying pirq is verified in order for the kernel to be able to get irq's ?
I think it might be a good idea to add the emcore to the tree, so if you can help me get this worked out we will add it.
OK. The emcore 6352 is my first cut at this linuxbios - to get into it and study the code. It should be simple for this board, since all of it's chips are supported already by previous eforts. If it works out I can buy myself project time to provide more boards and work on new stuff. How would I proceed later to add stuff to the tree? CVS commit, or do I send in diffs ?
- Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...
Send me the dmesg output.
attached
Thank you,
On Thu, 2003-01-16 at 22:47, Andrew Ip wrote:
- Linuxbios is coming up and so is the kernel. The pirq table however, is not successfully copied to 0xf0000, or so the debuging message tells me. Ethernet and usb both have irq zero assigned in linux ...
Any tips where I can start looking?
It could be src/config/Config's CONFIG_COMPRESS is set to 1. Try to set it to 0.
Thank you very much, it worked ! This clears up a lot of things for me!
On 17 Jan 2003 daniel@dmhome.net wrote:
Thank you very much, it worked ! This clears up a lot of things for me!
so how far are you booting now?
ron
so how far are you booting now?
ron
The board has a plcc socket that supports up to 512kb flash + a dip doc socket mapped to the usual doc address. I have done two tests: 1. linuxbios + a minimal 2.5 kernel with kexec in the flash, that executes a 2.4 kernel from an ide harddrive. 2. linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as described in the config file of the technoland board.
I can boot into the rootfilesystem and did some network testing. The floppy drive doesn't work, but I suspect it is because it is still setup to use the winbond floppy and not the one from the chipset (??? am just guessing here now) All is over serial console. As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
And then there is still the onboard sdram issue.
Greetings,
Daniel
On Fri, 17 Jan 2003 08:37:29 -0800, daniel@dmhome.net wrote:
As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
If you search hard enough there is a fb driver for the 69000. However, last I looked it had not been worked on in a long while and it didn't really work that well. Chances are it probally won't compile anymore with the current fb stuff. But it might not be that much work to fix. The X 69000 driver works great so you might be able to get a lot of code/settings from it if you tried.
I'm intersted in helping you get the C&T video bios working since our system has 2 69000's on it and I'd like them to vga on boot rather than wait for fb or X.
Course I have to get SDRAM working first. *grin*
-- Richard A. Smith Bitworks, Inc. rsmith@bitworks.com 479.846.5777 x104 Sr. Design Engineer http://www.bitworks.com
On Fri, 17 Jan 2003 daniel@dmhome.net wrote:
- linuxbios + a minimal 2.5 kernel with kexec in the flash, that
executes a 2.4 kernel from an ide harddrive.
you got a 2.5 kernel + kexec into 512KB?
Send me kernel version and .config :-)
- linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as
described in the config file of the technoland board.
that works too?
I thiink you need to get your on-board SDRAM working first. Then let's talk about floppy etc.
I would also like to get a source tree for this board into the linuxbios cvs.
ron
On Sat, 2003-01-18 at 05:13, Ronald G. Minnich wrote:
On Fri, 17 Jan 2003 daniel@dmhome.net wrote:
- linuxbios + a minimal 2.5 kernel with kexec in the flash, that
executes a 2.4 kernel from an ide harddrive.
you got a 2.5 kernel + kexec into 512KB?
Send me kernel version and .config :-)
The latest at that time 2.5.56. Those 2.5 series are not so easy to compile without networking are they ? It took me several 2.5 versions and kexec patch combinations before I could get it to compile. -------------------------------------------------------- # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_SWAP=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y
# # Code maturity level options # CONFIG_EXPERIMENTAL=y
# # General setup # CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_LOG_BUF_SHIFT_17 is not set # CONFIG_LOG_BUF_SHIFT_16 is not set # CONFIG_LOG_BUF_SHIFT_15 is not set CONFIG_LOG_BUF_SHIFT_14=y # CONFIG_LOG_BUF_SHIFT_13 is not set # CONFIG_LOG_BUF_SHIFT_12 is not set CONFIG_LOG_BUF_SHIFT=14
# # Loadable module support # # CONFIG_MODULES is not set
# # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_PREFETCH=y # CONFIG_HUGETLB_PAGE is not set # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_KEXEC=y
# # Power management options (ACPI, APM) # # CONFIG_PM is not set
# # ACPI Support # # CONFIG_ACPI is not set # CONFIG_CPU_FREQ is not set
# # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set CONFIG_PCI_GODIRECT=y # CONFIG_PCI_GOANY is not set CONFIG_PCI_DIRECT=y # CONFIG_SCx200 is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_HOTPLUG is not set
# # Executable file formats # CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y
# # Memory Technology Devices (MTD) # # CONFIG_MTD is not set
# # Parallel port support # # CONFIG_PARPORT is not set
# # Plug and Play support # # CONFIG_PNP is not set
# # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_LBD is not set
# # ATA/ATAPI/MFM/RLL device support # CONFIG_IDE=y
# # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y
# # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y # CONFIG_IDEDISK_STROKE is not set # CONFIG_BLK_DEV_IDECD is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_IDE_TASK_IOCTL is not set
# # IDE chipset support/bugfixes # CONFIG_BLK_DEV_CMD640=y CONFIG_BLK_DEV_CMD640_ENHANCED=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_GENERIC=y # CONFIG_IDEPCI_SHARE_IRQ is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDE_TCQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y CONFIG_IDEDMA_ONLYDISK=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_PCI_WIP is not set CONFIG_BLK_DEV_ADMA=y # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_NFORCE is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_RZ1000 is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set CONFIG_IDEDMA_AUTO=y # CONFIG_IDEDMA_IVB is not set CONFIG_BLK_DEV_IDE_MODES=y
# # SCSI device support # # CONFIG_SCSI is not set
# # Multi-device support (RAID and LVM) # # CONFIG_MD is not set
# # Fusion MPT device support #
# # IEEE 1394 (FireWire) support (EXPERIMENTAL) # # CONFIG_IEEE1394 is not set
# # I2O device support # # CONFIG_I2O is not set
# # Networking support # # CONFIG_NET is not set
# # Amateur Radio support # # CONFIG_HAMRADIO is not set
# # ISDN subsystem #
# # Telephony Support # # CONFIG_PHONE is not set
# # Input device support # CONFIG_INPUT=y
# # Userland interfaces # # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set
# # Input I/O drivers # # CONFIG_GAMEPORT is not set CONFIG_SOUND_GAMEPORT=y # CONFIG_SERIO is not set
# # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_INPUT_MOUSE is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set
# # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set
# # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y # CONFIG_SERIAL_8250_EXTENDED is not set
# # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256
# # I2C support # # CONFIG_I2C is not set
# # I2C Hardware Sensors Mainboard support #
# # I2C Hardware Sensors Chip support #
# # Mice # # CONFIG_BUSMOUSE is not set # CONFIG_QIC02_TAPE is not set
# # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_INTEL_RNG is not set # CONFIG_AMD_RNG is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set
# # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set
# # Multimedia devices # # CONFIG_VIDEO_DEV is not set
# # File systems # # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # CONFIG_REISERFS_FS is not set # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EXT3_FS is not set # CONFIG_JBD is not set # CONFIG_FAT_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_TMPFS is not set CONFIG_RAMFS=y # CONFIG_ISO9660_FS is not set # CONFIG_JFS_FS is not set CONFIG_MINIX_FS=y # CONFIG_VXFS_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y CONFIG_DEVFS_FS=y CONFIG_DEVFS_MOUNT=y # CONFIG_DEVFS_DEBUG is not set # CONFIG_DEVPTS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_EXT2_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UDF_FS is not set # CONFIG_UFS_FS is not set # CONFIG_XFS_FS is not set
# # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y
# # Graphics support # # CONFIG_FB is not set
# # Console display driver support # # CONFIG_VGA_CONSOLE is not set # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y
# # Sound # # CONFIG_SOUND is not set
# # USB support # # CONFIG_USB is not set
# # Profiling support # # CONFIG_PROFILING is not set
# # Kernel hacking # # CONFIG_DEBUG_KERNEL is not set # CONFIG_KALLSYMS is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_FRAME_POINTER is not set
# # Security options # # CONFIG_SECURITY is not set
# # Cryptographic options # # CONFIG_CRYPTO is not set
# # Library routines # CONFIG_CRC32=y CONFIG_X86_BIOS_REBOOT=y -------------------------------------------------------------------
- linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as
described in the config file of the technoland board.
that works too?
Yes, it boots fine. Is it true to say that this could work with a doc2000 also? If I dd to the beginning of a doc2000 is that still offset zero , or should I skip for the (read-only) ipl?
I thiink you need to get your on-board SDRAM working first. Then let's talk about floppy etc.
I would also like to get a source tree for this board into the linuxbios cvs.
I will do my best to get the onboard ram to work as soon as possible. Or do you want to add it before that? If you do let me know, then I will clean it up and send it - cause I am going on a two-weeks vacation starting from this Thursday.
Greetings,
Daniel Toussaint
On Sat, 2003-01-18 at 01:19, Richard A. Smith wrote:
On Fri, 17 Jan 2003 08:37:29 -0800, daniel@dmhome.net wrote:
As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
If you search hard enough there is a fb driver for the 69000. However, last I looked it had not been worked on in a long while and it didn't really work that well. Chances are it probally won't compile anymore with the current fb stuff. But it might not be that much work to fix. The X 69000 driver works great so you might be able to get a lot of code/settings from it if you tried.
I'm intersted in helping you get the C&T video bios working since our system has 2 69000's on it and I'd like them to vga on boot rather than wait for fb or X.
I'm using this :
option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1
but now it doesn't compile anymore with this error:
linuxbios_c.o: In function `biosint': linuxbios_c.o(.text+0x1587): undefined reference to `pcibios'
The makefile doesn't seem to have any references to it after running NLBconfig, so I will try to add it manually. Any other tips ?
Thanks ,
Daniel
On Sat, 2003-01-18 at 05:13, Ronald G. Minnich wrote:
On Fri, 17 Jan 2003 daniel@dmhome.net wrote:
- linuxbios + a minimal 2.5 kernel with kexec in the flash, that
executes a 2.4 kernel from an ide harddrive.
you got a 2.5 kernel + kexec into 512KB?
Send me kernel version and .config :-)
The latest at that time 2.5.56. Those 2.5 series are not so easy to compile without networking are they ? It took me several 2.5 versions and kexec patch combinations before I could get it to compile. -------------------------------------------------------- # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_SWAP=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y
# # Code maturity level options # CONFIG_EXPERIMENTAL=y
# # General setup # CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_LOG_BUF_SHIFT_17 is not set # CONFIG_LOG_BUF_SHIFT_16 is not set # CONFIG_LOG_BUF_SHIFT_15 is not set CONFIG_LOG_BUF_SHIFT_14=y # CONFIG_LOG_BUF_SHIFT_13 is not set # CONFIG_LOG_BUF_SHIFT_12 is not set CONFIG_LOG_BUF_SHIFT=14
# # Loadable module support # # CONFIG_MODULES is not set
# # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_PREFETCH=y # CONFIG_HUGETLB_PAGE is not set # CONFIG_SMP is not set # CONFIG_PREEMPT is not set # CONFIG_X86_UP_APIC is not set # CONFIG_X86_MCE is not set # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_KEXEC=y
# # Power management options (ACPI, APM) # # CONFIG_PM is not set
# # ACPI Support # # CONFIG_ACPI is not set # CONFIG_CPU_FREQ is not set
# # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set CONFIG_PCI_GODIRECT=y # CONFIG_PCI_GOANY is not set CONFIG_PCI_DIRECT=y # CONFIG_SCx200 is not set # CONFIG_PCI_LEGACY_PROC is not set # CONFIG_PCI_NAMES is not set # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_HOTPLUG is not set
# # Executable file formats # CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y
# # Memory Technology Devices (MTD) # # CONFIG_MTD is not set
# # Parallel port support # # CONFIG_PARPORT is not set
# # Plug and Play support # # CONFIG_PNP is not set
# # Block devices # # CONFIG_BLK_DEV_FD is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_LOOP is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_LBD is not set
# # ATA/ATAPI/MFM/RLL device support # CONFIG_IDE=y
# # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y
# # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y # CONFIG_IDEDISK_STROKE is not set # CONFIG_BLK_DEV_IDECD is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_IDE_TASK_IOCTL is not set
# # IDE chipset support/bugfixes # CONFIG_BLK_DEV_CMD640=y CONFIG_BLK_DEV_CMD640_ENHANCED=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_GENERIC=y # CONFIG_IDEPCI_SHARE_IRQ is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDE_TCQ is not set # CONFIG_BLK_DEV_OFFBOARD is not set # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y CONFIG_IDEDMA_ONLYDISK=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_PCI_WIP is not set CONFIG_BLK_DEV_ADMA=y # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_NFORCE is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_RZ1000 is not set # CONFIG_BLK_DEV_SVWKS is not set # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set CONFIG_IDEDMA_AUTO=y # CONFIG_IDEDMA_IVB is not set CONFIG_BLK_DEV_IDE_MODES=y
# # SCSI device support # # CONFIG_SCSI is not set
# # Multi-device support (RAID and LVM) # # CONFIG_MD is not set
# # Fusion MPT device support #
# # IEEE 1394 (FireWire) support (EXPERIMENTAL) # # CONFIG_IEEE1394 is not set
# # I2O device support # # CONFIG_I2O is not set
# # Networking support # # CONFIG_NET is not set
# # Amateur Radio support # # CONFIG_HAMRADIO is not set
# # ISDN subsystem #
# # Telephony Support # # CONFIG_PHONE is not set
# # Input device support # CONFIG_INPUT=y
# # Userland interfaces # # CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set
# # Input I/O drivers # # CONFIG_GAMEPORT is not set CONFIG_SOUND_GAMEPORT=y # CONFIG_SERIO is not set
# # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y # CONFIG_INPUT_MOUSE is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set
# # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set
# # Serial drivers # CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y # CONFIG_SERIAL_8250_EXTENDED is not set
# # Non-8250 serial port support # CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256
# # I2C support # # CONFIG_I2C is not set
# # I2C Hardware Sensors Mainboard support #
# # I2C Hardware Sensors Chip support #
# # Mice # # CONFIG_BUSMOUSE is not set # CONFIG_QIC02_TAPE is not set
# # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_INTEL_RNG is not set # CONFIG_AMD_RNG is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_GEN_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set
# # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # CONFIG_DRM is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set
# # Multimedia devices # # CONFIG_VIDEO_DEV is not set
# # File systems # # CONFIG_QUOTA is not set # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # CONFIG_REISERFS_FS is not set # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EXT3_FS is not set # CONFIG_JBD is not set # CONFIG_FAT_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_TMPFS is not set CONFIG_RAMFS=y # CONFIG_ISO9660_FS is not set # CONFIG_JFS_FS is not set CONFIG_MINIX_FS=y # CONFIG_VXFS_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y CONFIG_DEVFS_FS=y CONFIG_DEVFS_MOUNT=y # CONFIG_DEVFS_DEBUG is not set # CONFIG_DEVPTS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_EXT2_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UDF_FS is not set # CONFIG_UFS_FS is not set # CONFIG_XFS_FS is not set
# # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y
# # Graphics support # # CONFIG_FB is not set
# # Console display driver support # # CONFIG_VGA_CONSOLE is not set # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y
# # Sound # # CONFIG_SOUND is not set
# # USB support # # CONFIG_USB is not set
# # Profiling support # # CONFIG_PROFILING is not set
# # Kernel hacking # # CONFIG_DEBUG_KERNEL is not set # CONFIG_KALLSYMS is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_FRAME_POINTER is not set
# # Security options # # CONFIG_SECURITY is not set
# # Cryptographic options # # CONFIG_CRYPTO is not set
# # Library routines # CONFIG_CRC32=y CONFIG_X86_BIOS_REBOOT=y -------------------------------------------------------------------
- linuxbios in flash and a 2.4 kernel at 00000 in a doc millenium as
described in the config file of the technoland board.
that works too?
Yes, it boots fine. Is it true to say that this could work with a doc2000 also? If I dd to the beginning of a doc2000 is that still offset zero , or should I skip for the (read-only) ipl?
I thiink you need to get your on-board SDRAM working first. Then let's talk about floppy etc.
I would also like to get a source tree for this board into the linuxbios cvs.
I will do my best to get the onboard ram to work as soon as possible. Or do you want to add it before that? If you do let me know, then I will clean it up and send it - cause I am going on a two-weeks vacation starting from this Thursday.
Greetings,
Daniel Toussaint
On Sat, 2003-01-18 at 01:19, Richard A. Smith wrote:
On Fri, 17 Jan 2003 08:37:29 -0800, daniel@dmhome.net wrote:
As far as understand from previous posts, the easiest way to get the vga to work would be to get the vga bios in flash? The vga chip on board is C&T69000, and I have a vga bios for it. (I did a quick test, the vga bios was found it seems, but I forgot to compile in pcibios.c , so it kept looping )
If you search hard enough there is a fb driver for the 69000. However, last I looked it had not been worked on in a long while and it didn't really work that well. Chances are it probally won't compile anymore with the current fb stuff. But it might not be that much work to fix. The X 69000 driver works great so you might be able to get a lot of code/settings from it if you tried.
I'm intersted in helping you get the C&T video bios working since our system has 2 69000's on it and I'd like them to vga on boot rather than wait for fb or X.
I'm using this :
option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1
but now it doesn't compile anymore with this error:
linuxbios_c.o: In function `biosint': linuxbios_c.o(.text+0x1587): undefined reference to `pcibios'
The makefile doesn't seem to have any references to it after running NLBconfig, so I will try to add it manually. Any other tips ?
Thanks ,
Daniel
Hello -> confused newbie here !!
The linuxbios chat, I can follow but I am very intrigued by the vgabios since it will help linux on the nanofront and advance my own thinman model ***
I am writing a glossary right now and I need to know the difference between:
vgabios, framebuffer and X
My understanding is that X is compiled into the vgabios and that a framebuffer is a vga card (sun systems)
TIA, yeah.. I know
** I have an organization called the Linux Society, right now at http://yahoogroups.com/group/linux-society. We will soon be a postnuke site and will be offering a lot of integration products based on completely new ways of booting linux. Devil-Linux is our standard OS install. The ThinMan is a trademark for a device network that seeks to collect pennies from 6 billion humans rather than thousands from a hundred million (microsoft)
On Sunday, January 19, 2003, at 09:07 PM, daniel@dmhome.net wrote:
On Sat, 2003-01-18 at 01:19, Richard A. Smith wrote:
On Fri, 17 Jan 2003 08:37:29 -0800, daniel@dmhome.net wrote: I'm intersted in helping you get the C&T video bios working since our system has 2 69000's on it and I'd like them to vga on boot rather than wait for fb or X.
I'm using this :
option CONFIG_VGABIOS=1 option CONFIG_REALMODE_IDT=1 option CONFIG_PCIBIOS=1
but now it doesn't compile anymore with this error:
linuxbios_c.o: In function `biosint': linuxbios_c.o(.text+0x1587): undefined reference to `pcibios'
The makefile doesn't seem to have any references to it after running NLBconfig, so I will try to add it manually. Any other tips ?
Thanks ,
Daniel
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Fri, Jan 24, 2003 at 01:14:53PM -0500, John van Vlaaderen wrote:
I am writing a glossary right now and I need to know the difference between:
vgabios, framebuffer and X
Wow, ok, not that this is the best place, but ok.
LinuxBIOS is currently mostly operational on what's commonly referred to as the PC platform. The last standardized graphics controller on this platform was the VGA. (Video Graphics Array) This VGA card had a BIOS that would initialize the card when the main system BIOS traversed all expansion cards looking for any BIOSes on them.
The VGA BIOS knows the details of how to program the graphics card. The VGA BIOS is closely tied to every single hardware. Different graphics chipset - different VGA BIOS. Graphics chipset makers are often reluctant to release detailed programming information for their chipsets, but a VGA BIOS is always included with the card. So if LinuxBIOS can make use of the VGA BIOS it is trivial to use the computer screen e.g. for startup debugging.
'framebuffer' has a couple of different meanings. One is the video memory on the graphics card. Another is the Linux drivers for accessing the said memory. Writing a Linux framebuffer driver requires the same detailed programming information as for a VGA BIOS. Framebuffer drivers aren't all that common, it has become sort of a niche, used frequently for Set-Top-Box and other embedded systems. (Reference: DirectFB.) Think of the framebuffer drivers as a VGA BIOS in Linux for Linux, it allows Linux to know all (or at least a lot) about the graphics controller in the system.
X is usually short for X-Windows which is the windowing system providing core GUI functionality in almost all available Unix systems. When open source people say X or X server they're often talking about XFree86, an open source X-Windows server. The X server also needs detailed knowledge about graphics chipsets, in order to provide and perform the desired functions in an efficient manner.
Short summary:
The VGA BIOS, a framebuffer driver and the X server all need detailed info on programming the graphics controller. They differ in whom they provide services for.
The VGA BIOS provides services mainly meant for MS-DOS and other "classical" textmode applications like LILO and Linux itself.
The framebuffer driver provides services mainly meant for Linux and is also a part of Linux.
The X server provides services to X clients and/or the window manager. All programs run in X are X clients.
Hope this clears it up.
//Peter
On Fri, Jan 24, 2003 at 01:14:53PM -0500, John van Vlaaderen wrote:
Hello -> confused newbie here !!
The linuxbios chat, I can follow but I am very intrigued by the vgabios since it will help linux on the nanofront and advance my own thinman model ***
I am writing a glossary right now and I need to know the difference between:
vgabios, framebuffer and X
I wonder why you didn't google for these first, btw. Would've given you a big part of what I wrote in the other mail.
//Peter
Thanks Peter, but... maybe i should have said:
...In relation to LinuxBIOS...
We know what X and a vgabios are -- what I am asking about are references on this mailing list to writing X into a vgabios -- maybe VIA -- using code from the bochs vgabios -- or something like that -- along w/ Xfree86
Framebuffers are new to me, never really thot about them, I am looking of DirectFB right now and it really seems like an acceleration process, so I am wondering why it keeps appearing in LinuxBIOS mailing lists.
What is envisioned for getting X running from LinuxBIOS ?? Clusters obviously have no need for them, but there are huge hungry embedded people out there. I would like to join the fray with some useful information.
Only part of the need is being kewl, the more important issue becomes getting proprietary code out of the PC completely, as dictated by the GNU religion, and gaining support among the youth.
On Thursday, January 23, 2003, at 08:11 PM, Peter Stuge wrote:
On Fri, Jan 24, 2003 at 01:14:53PM -0500, John van Vlaaderen wrote:
I am writing a glossary right now and I need to know the difference between:
vgabios, framebuffer and X
Wow, ok, not that this is the best place, but ok.
LinuxBIOS is currently mostly operational on what's commonly referred to as the PC platform. The last standardized graphics controller on this platform was the VGA. (Video Graphics Array) This VGA card had a BIOS that would initialize the card when the main system BIOS traversed all expansion cards looking for any BIOSes on them.
The VGA BIOS knows the details of how to program the graphics card. The VGA BIOS is closely tied to every single hardware. Different graphics chipset - different VGA BIOS. Graphics chipset makers are often reluctant to release detailed programming information for their chipsets, but a VGA BIOS is always included with the card. So if LinuxBIOS can make use of the VGA BIOS it is trivial to use the computer screen e.g. for startup debugging.
'framebuffer' has a couple of different meanings. One is the video memory on the graphics card. Another is the Linux drivers for accessing the said memory. Writing a Linux framebuffer driver requires the same detailed programming information as for a VGA BIOS. Framebuffer drivers aren't all that common, it has become sort of a niche, used frequently for Set-Top-Box and other embedded systems. (Reference: DirectFB.) Think of the framebuffer drivers as a VGA BIOS in Linux for Linux, it allows Linux to know all (or at least a lot) about the graphics controller in the system.
X is usually short for X-Windows which is the windowing system providing core GUI functionality in almost all available Unix systems. When open source people say X or X server they're often talking about XFree86, an open source X-Windows server. The X server also needs detailed knowledge about graphics chipsets, in order to provide and perform the desired functions in an efficient manner.
Short summary:
The VGA BIOS, a framebuffer driver and the X server all need detailed info on programming the graphics controller. They differ in whom they provide services for.
The VGA BIOS provides services mainly meant for MS-DOS and other "classical" textmode applications like LILO and Linux itself.
The framebuffer driver provides services mainly meant for Linux and is also a part of Linux.
The X server provides services to X clients and/or the window manager. All programs run in X are X clients.
Hope this clears it up.
//Peter
CXN, Inc. Contact: john@thinman.com President, The Linux Society http://groups.yahoo.com/group/linux-society linux society distro -> http://www.thinman.com/eLSD/readme ThinMan is a registered trademark of CXN, Inc.
On Thu, Jan 23, 2003 at 10:19:19PM -0500, John van Vlaaderen wrote:
Thanks Peter, but... maybe i should have said:
...In relation to LinuxBIOS...
We know what X and a vgabios are -- what I am asking about are references on this mailing list to writing X into a vgabios -- maybe VIA -- using code from the bochs vgabios -- or something like that -- along w/ Xfree86
XFree86 v4 have some provisions for using a VGA BIOS. If you have a VGA BIOS in the system you can get XFree86 running. (Although not at the highest possible speed with the highest possible resolution or colour depth.)
Framebuffers are new to me, never really thot about them, I am looking of DirectFB right now and it really seems like an acceleration process, so I am wondering why it keeps appearing in LinuxBIOS mailing lists.
Many people are used to having a standard keyboard and a monitor attached to their computer system, a console. Because VGA BIOSes often rely heavily on legacy BIOS services (sorry, should've mentioned this part yesterday) these VGA BIOSes cannot be utilized in LinuxBIOS (yet) because LinuxBIOS doesn't provide these legacy BIOS services (interrupt services, int 15h etc. Search Ralph Brown's interrupt.lst for the keyword BIOS. :) yet. There is work underway to add needed parts from the Bochs project's GPL legacy BIOS to LinuxBIOS, which would also allow all VGA BIOSes to work.
The VGA BIOS and the framebuffer driver serve the same purpose, to activate the monitor connected to the graphics adapter in the system. This is more relevant in some cases than other. For a GPL desktop system you'd want it. For a cluster node you couldn't care less.
The VGA BIOS has an advantage over the framebuffer in that it will be initialized somewhat earlier, on the other hand I suspect that much of LinuxBIOS's hard work will already be done when the VGA BIOS gets initialized so LinuxBIOS debugging will still be best made through the serial port. The VGA BIOS is also closed source, of course, which is to it's disadvantage.
What is envisioned for getting X running from LinuxBIOS ?? Clusters obviously have no need for them, but there are huge hungry embedded people out there. I would like to join the fray with some useful information.
If all you want is X and don't care about the Linux text console, you'll need either a VGA BIOS or a native graphics chipset driver in the X server. If all you have is the VGA BIOS the X server will have pretty poor performance.
Only part of the need is being kewl, the more important issue becomes getting proprietary code out of the PC completely, as dictated by the GNU religion, and gaining support among the youth.
It's coming. It's just taking some time. The PC architecture is about 20 years worth of kludges on top of each other.
//Peter
Many people are used to having a standard keyboard and a monitor attached to their computer system, a console. Because VGA BIOSes often rely heavily on legacy BIOS services (sorry, should've mentioned this part yesterday) these VGA BIOSes cannot be utilized in LinuxBIOS (yet) because LinuxBIOS doesn't provide these legacy BIOS services (interrupt services, int 15h etc. Search Ralph Brown's interrupt.lst for the keyword BIOS. :) yet. There is work underway to add needed parts from the Bochs project's GPL legacy BIOS to LinuxBIOS, which would also allow all VGA BIOSes to work.
It is been already done.
linuxbios supports both standard pc bios services as well as vga bios (although vga bios is in the binary only form so far).
Thanks Peter and Adam -- now I am no longer an idiot !!
Ps, going to post this on my Linux Society mailing list. I will have a PostNuke site up pretty soon to support news dicussion on this and also server side topics.
Pps, Just for reference, my star product has been a cross compiling gcc which automated security compiles of various packages, tgz packaging and ssh tar-in/tar-out delivery systems where the only OS mods were links from /etc/ startup files to local /opt/<app-name>/etc files. I have hoped to make an independent product out of it, based on the highly dependable Devil-Linux.org. (DL is text only by design)
Hence my ingnorace in PC h/w issues ;) Will anybody be at LinuxWorld today at Javits ??
john
On Friday, January 24, 2003, at 07:24 AM, Adam Sulmicki wrote:
Many people are used to having a standard keyboard and a monitor attached to their computer system, a console. Because VGA BIOSes often rely heavily on legacy BIOS services (sorry, should've mentioned this part yesterday) these VGA BIOSes cannot be utilized in LinuxBIOS (yet) because LinuxBIOS doesn't provide these legacy BIOS services (interrupt services, int 15h etc. Search Ralph Brown's interrupt.lst for the keyword BIOS. :) yet. There is work underway to add needed parts from the Bochs project's GPL legacy BIOS to LinuxBIOS, which would also allow all VGA BIOSes to work.
It is been already done.
linuxbios supports both standard pc bios services as well as vga bios (although vga bios is in the binary only form so far).
-- Adam Sulmicki http://www.eax.com The Supreme Headquarters of the 32 bit registers
CXN, Inc. Contact: john@thinman.com President, The Linux Society http://groups.yahoo.com/group/linux-society linux society distro -> http://www.thinman.com/eLSD/readme ThinMan is a registered trademark of CXN, Inc.
John van Vlaaderen john-at-thinman@nyc.rr.com writes:
Thanks Peter and Adam -- now I am no longer an idiot !!
Ps, going to post this on my Linux Society mailing list. I will have a PostNuke site up pretty soon to support news dicussion on this and also server side topics.
Pps, Just for reference, my star product has been a cross compiling gcc which automated security compiles of various packages, tgz packaging and ssh tar-in/tar-out delivery systems where the only OS mods were links from /etc/ startup files to local /opt/<app-name>/etc files. I have hoped to make an independent product out of it, based on the highly dependable Devil-Linux.org. (DL is text only by design)
Hence my ingnorace in PC h/w issues ;) Will anybody be at LinuxWorld today at Javits ??
Sorry I just got back. But there is a 10 node LinuxBIOS cluster (configure to boot verbosely at 9600 baud instead of fast) in the LinuxNetworX display at the intel booth.
Eric
Hi all,
My friends had fun there, but I was disappointed. I thought all the intensity of the past was gone, the big boys profiting what used to be an independent domain.
Bout half the cluster companies didnt know what LinuxBIOS is ...
I earned my goodies by evangelizing your work ;)
John
On Friday, January 24, 2003, at 09:56 AM, Eric W. Biederman wrote:
John van Vlaaderen john-at-thinman@nyc.rr.com writes:
Thanks Peter and Adam -- now I am no longer an idiot !!
Ps, going to post this on my Linux Society mailing list. I will have a PostNuke site up pretty soon to support news dicussion on this and also server side topics.
Pps, Just for reference, my star product has been a cross compiling gcc which automated security compiles of various packages, tgz packaging and ssh tar-in/tar-out delivery systems where the only OS mods were links from /etc/ startup files to local /opt/<app-name>/etc files. I have hoped to make an independent product out of it, based on the highly dependable Devil-Linux.org. (DL is text only by design)
Hence my ingnorace in PC h/w issues ;) Will anybody be at LinuxWorld today at Javits ??
Sorry I just got back. But there is a 10 node LinuxBIOS cluster (configure to boot verbosely at 9600 baud instead of fast) in the LinuxNetworX display at the intel booth.
Eric
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
CXN, Inc. Contact: john@thinman.com President, The Linux Society http://groups.yahoo.com/group/linux-society linux society distro -> http://www.thinman.com/eLSD/readme ThinMan is a registered trademark of CXN, Inc.
Hi, Folks :)
Frigid here in NY !! Longest cold snap since 1890 -- looks like war on the horizon -- probably be pretty quick -- Saddam hottails it to Sudan -- or some such. Market should climb out of the present hole -- leaving the likes of us to CPR the global economy.
My big question of the day:
Will LinuxBIOS be able to support several IDE cards ?? I actually used to have a PCI IDE harddrive controller. These days one would by the 3ware (linux friendly) mirroring card.
For a consumer portal and home support system, this would be fantastic -- passing down the savings on 200GB disks that are only slightly more expensive than 20GB disks.
On Friday, January 24, 2003, at 09:56 AM, Eric W. Biederman wrote:
John van Vlaaderen john-at-thinman@nyc.rr.com writes:
Thanks Peter and Adam -- now I am no longer an idiot !!
Ps, going to post this on my Linux Society mailing list. I will have a PostNuke site up pretty soon to support news dicussion on this and also server side topics.
Pps, Just for reference, my star product has been a cross compiling gcc which automated security compiles of various packages, tgz packaging and ssh tar-in/tar-out delivery systems where the only OS mods were links from /etc/ startup files to local /opt/<app-name>/etc files. I have hoped to make an independent product out of it, based on the highly dependable Devil-Linux.org. (DL is text only by design)
Hence my ingnorace in PC h/w issues ;) Will anybody be at LinuxWorld today at Javits ??
Sorry I just got back. But there is a 10 node LinuxBIOS cluster (configure to boot verbosely at 9600 baud instead of fast) in the LinuxNetworX display at the intel booth.
Eric
CXN, Inc. Contact: john@thinman.com President, The Linux Society http://groups.yahoo.com/group/linux-society linux society distro -> http://www.thinman.com/eLSD/readme ThinMan is a registered trademark of CXN, Inc.
On Tue, 28 Jan 2003, John van Vlaaderen wrote:
Will LinuxBIOS be able to support several IDE cards ?? I actually used to have a PCI IDE harddrive controller. These days one would by the 3ware (linux friendly) mirroring card.
The current complexity of the IDE drivers in Linux is something I would rather avoid in linuxbios. But demand has always been the driver, note that we can even boot over serial nowadays (!).
However it seems more sensible to Let Etherboot Do It, or Steve Jame's Forth boot code that he had at SC 2002, or even Linux with a big enough Flash. I still most prefer Linux as my boot loader as that has had the fewest hardware glitches across the 10 or so platforms I currently directly use.
ron
Hi Folks -- I am getting ready to automate a busybox/uClib nano-distro building kit.
I will be testing the distro in Bochs -- as soon as I get it working -- but I am wondering if there is some way to develop it for LinuxBIOS in an emulator as well.
Its purpose is to create a front-end boot linux to support CDs Initrd where the boot linux builds up the system safely to possibly hand-over to another linux, including a new kernel.
That would enable a snazzy step-by-step install process which uses a legitimate linux to build a more-legitimate linux from net-modules -- or other OS. The distro should be able to live in the bios as well.
The purpose of the distro would be defined by the needs of the particular users, but I would be most pleased to be able to consistently supply a fresh uClibc and Busybox environment, especially for newer developers.
Thanks, John
-
Adam Sulmicki -
Andrew Ip -
daniel＠dmhome.net -
ebiederman＠lnxi.com -
John van Vlaaderen -
Peter Stuge -
Richard A. Smith -
Ronald G. Minnich