Red Hat

I have a lead on a short term contract for a customized Fedora serial driver

I have a lead on a short term piece of work on a customization of a serial
kernel module to meet the specs below.

Contact me offlist if you think this is something you know how to do.


=========== snip from client description of problem ==========
> I have a C program in Linux that talks to slot machine which require a
> wakeup bit be set. The protocol requiers 1 start, 8 data, 1 wakeup, 1
> stop bit.
> Essentially I need the set or 127 characters to go out with the parity
> bit set to zero. In addition I need, at least, to be able to send out
> 0x00, 0x01, 0x80, 0x81 and 0x82 out with the parity bit set to 1.

Installing Linux and the K8N-DL motherboard

Hello -

Does anyone out there have any experience or tips on installing linux onto an ASUS K8N-DL motherboard? I've tried SUSE 10.1 and RHEL 4 rel4, I've tried both on-board SATA controllers, I've tried with and without hardware RAID, but all with no luck. The system has dual AMD Opteron processors, and 4GB of RAM. I've found a number of sites that claim this can work, although linux is not officially supported by ASUS on this mobo.

When HW RAID is off, the install sees all 4 drives, and allows me to partition them and finish the install, but upon reboot it will not recognize a valid system drive and won't boot. Any suggestions would be very welcome!

LVM, Logical Volume Migraine

Migraine time. The past 3 days I've been waiting patiently for a system to finish a file system check on a couple of LVM partitions. The story is complicated by the fact that the hard drive in the system was incorrectly ghosted. The drive in question is a 120GB hard drive, but it was ghosted as if it was a 60GB hard drive.

I came into the picture about a year ago when I added the rest of the drive using LVM. Recently that drive started to fill so I added a second drive to the volume group. I got a call a few days ago saying that the drives on the server were no longer writable. I rebooted (mistake) and ever since the drive has been in a recovery shell (not a normal shell). Doing a fsck results in Illegal block #5020 (90367283) in inode 7 (example) and I have to press y to reallocate the blocks. Originally I just took a lead pipe and put it on the 'y' key before doing a fsck -h and seeing that all I had to do was fsck -y to get the same result (the lead pipe hack is cooler though).

Syndicate content Syndicate content Syndicate content